My Emulator Google Pixel but why does not support Google ArCore

My Emulator device Google Pixel and i am using Android 8.1 (Oreo) but this app compatible this device. (https://play.google.com/store/apps/details?id=com.google.ar.core)
I have followed all of the steps in this article -> https://developers.google.com/ar/develop/java/emulator

If install this apk then works.
Download the latest Google_Play_Services_for_AR_1.12.0_x86_for_emulator.apk from the GitHub releases page.
https://github.com/google-ar/arcore-android-sdk/releases


More parameters are required than just --id

Hi, I'm trying to run the below command, using the --id parameter only (mentioned as required). However, when running the task, it complains I also needed to provide the --organization as well as --project parameters.
Thanks, Peter

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

ID: 3bd63c4b-37f7-3641-8f15-0f5713ab71b4
Version Independent ID: 39006efa-983d-d605-ca4f-95ffd91fbec4
Content: az devops service-endpoint
Content Source: latest/docs-ref-autogen/devops/service-endpoint.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

@petender its updated
--org --organization
Azure DevOps organization URL. You can configure the default organization using az devops configure -d organization=ORG_URL. Required if not configured as default or picked up via git config. Example: https://dev.azure.com/MyOrganizationName/.
--project -p
Name or ID of the project. You can configure the default project using az devops configure -d project=NAME_OR_ID. Required if not configured as default or picked up via git config.


[ADP-3300] Add ChainPoint to read

This pull request adds the ChainPoint type to the Cardano.Wallet.Read hierarchy.
Comments

Issue Number
ADP-3300

For me it is already ready to review, not draft anymore, but maybe you want to add something more here. If yes, ping me. Approving with what we have atm though:-)

Hehe, fair enough. I'll merge as is (after rebasing) — small pull requests that do one thing and do it well.


Update UI to open bigger channels

⚠ This ticket needs some design in Figma first: https://github.com/get10101/10101/issues/1286

For example, let the user pick one of

basic: try out the app and trade up to 200k
advanced: actually trade up to 1m
expert: trade up to 10m
other: reach out

Each category has a different price.

Blocked by https://github.com/get10101/10101/issues/1286


feat: Add Vertex Vector Search Datapoints deletion, add autogenerated datapoint IDs to document metadata during ingestion

Support Vertex Vector Search Datapoints deletion via the vector_store.delete() method

@Abhishekbhagwat are you planning to finalize this one?


[proxima-core] #170 implement ThroughputLimiter

@dmvk this is ready for review. I'm still tuning the code coverage (and hence I have to touch sort of unrelated pieces of code - e.g. cassandra). I will keep these commits separate and squash the rest after review.

@dmvk checks passed

This closes O2-Czech-Republic#170

This closes O2-Czech-Republic#170


Debug collector input processing

Processing of CLI input into a config that can immediately be used by the collector to collect data.
#124, #127

I don't think we want to be tracking binaries in this repo, can those two bins be generated when needed by the tests instead?

Yes, but then those tests would require linkers for specific architectures.

I don't think we want to be tracking binaries in this repo, can those two bins be generated when needed by the tests instead?

Yes, but then those tests would require linkers for specific architectures.

We should be able to use rust-lld I would think.

We should be able to use rust-lld I would think.

Oh, ok. I'll look into that

I think we can close this in favor of #142


"SetTypingRequest" Telethon equivalent in Gramme.rs

Is there any?

I'll close this issue, as the raw API can be used and it's not too bad (it'll set the typing status for 5 seconds, if I remember correctly).
I wouldn't like the library to spawn tasks to periodically set the typing status for longer. And context expressions aren't really a thing. So maybe there's no much cleaner way than just calling set typing and having it enabled for 5 seconds.


Upstream api

Hello @AerWyn81 !
Thank you for your plugin ♥
I've updated the following API :

PlaceholderAPI : 2.11.1 → 2.11.3
DecentHolograms : 2.7.9 → 2.8.1
NBTAPI : 2.11.2 → 2.11.3
net.minecrell.plugin-yml.bukkit : 0.5.2 → 0.5.3

Other thing :

Plugin version : 2.2.6 → 2.2.7

Updated in 5a86d4
A number of side-effects were not managed by the PR
Thanks anyway ;)


breaking randomly

I've got a very strange behaviour in Ubuntu 14.04 and Atom 1.9.9 (but also tested with older versions).
Xdebug version is 2.2.3
The debugger is breaking randomly. I press on "Continue" and it just jumps to another random place.
Sometimes it jumps to the next line.
I've cleared all breakpoints and then I've added one single breakpoint, but I can not reach it.
Very strange stuff. What can be the cause?

You should be able to adjust this by unchecking break on php exceptions/warnings/notices etc. Closing this, feel free to reopen if you need additional support.


How to log artifacts on rank > 0?

Bug description
I am using a GPU to generate a result file (e.g. a video, text file, image,...).
Then I do self.logger.experiment.log_artifact(                 self.logger.run_id, artifact_path, log_folder) to log the file.
However, this does not work in  multi-gpu setup, as the logger for rank >0 is set to DummyLogger.
In the multi-GPU setup, I would like each GPU to generate one file, and log all into the same folder (I take care there is no naming collision).
How  can this be achieved?
cc @awaelchli @borda
What version are you seeing the problem on?
v1.9
How to reproduce the bug
No response
Error messages and logs
# Error messages and logs here please

Environment

Current environment
#- Lightning Component (e.g. Trainer, LightningModule, LightningApp, LightningWork, LightningFlow):
#- PyTorch Lightning Version (e.g., 1.5.0):
#- Lightning App Version (e.g., 0.5.2):
#- PyTorch Version (e.g., 2.0):
#- Python version (e.g., 3.9):
#- OS (e.g., Linux):
#- CUDA/cuDNN version:
#- GPU models and configuration:
#- How you installed Lightning(`conda`, `pip`, source):
#- Running environment of LightningApp (e.g. local, cloud):

More info
No response

At least for logging with MLflow to the local storage, I created a workaround by broadcasting the artifact folder and manually copying the data into that folder. But this will not work with other interfaces, of course.

Hey @rob-hen
The behavior you described is intentionally designed like this, so it's not a bug. Logging occurs on rank 0. In general, if results from other ranks should be included in the logs, they have to be synchronized/collected first before logging. For example, via self.all_gather() in LightningModule, or by using torchmetrics if it's a metric.

In the multi-GPU setup, I would like each GPU to generate one file, and log all into the same folder (I take care there is no naming collision).
How can this be achieved?

If you write a file on each GPU process, and take care of the naming collisions, you can replace
self.logger.experiment.log_artifact( self.logger.run_id, artifact_path, log_folder)

with
wandb.log_artifact( self.logger.run_id, artifact_path, log_folder)

(assuming you are using wandb)
But since this will run on every process, make sure the log_folder is unique to the rank of the process.
This will do what you asked for, but personally I wouldn't do this. I would create the files in the same folder and then log them on rank 0 only using self.logger.experiment for sanity.

Thanks for your answer @awaelchli
I am not using wandb. Since all workers use a shared file system, I could have each worker write into a common folder, then synchronize on the finshed result, and then have rank 0 looping through the results and store everything via self.logger.experiment.log_artifact.
Whats the best way for the synchronization? The files are created during validation_step, so I would just need to synchronize on on_validation_epoch_end.

Sure, the logger doesn't matter.

I am not using wandb but MLFlow. Since all workers use a shared file system, I could have each worker write into a common folder, then synchronize on the finshed result, and then have rank 0 looping through the results and store everything via self.logger.experiment.log_artifact.

Yes I agree. No special synchronization is needed in that case. You would just call self.logger.experiment.log_artifact in on_validation_epoch_end with a for-loop over the files listed in that folder.

It's not guaranteed to run at the same time no. So in this case it would require you to add a barrier. I forgot that sorry:
def on_validation_epoch_end(self):
    self.trainer.strategy.barrier()
    for file in listdir:
        self.logger.experiment.log_artifact(file, ...)

@awaelchli
Since only rank 0

Yes, good point. Just add another barrier at the end :)
def on_validation_epoch_end(self):
self.trainer.strategy.barrier()  # all processes must meet here and shake hands before continuing execution
for file in listdir:
self.logger.experiment.log_artifact(file, ...)
self.trainer.strategy.barrier()  # all processes must meet here and shake hands before continuing execution

I think that solution is addressing something else.
What I mean is all GPUs with rank > 0 do not have to wait. They can create the files in validation_step, go to  on_validation_epoch_end  and do some computations there without waiting that all other works have finished  validation_step.
Only for rank 0: It needs to wait until all GPUs have entered on_validation_epoch_end .

Something like:
def on_validation_epoch_end(self):

self.trainer.strategy.register_entrance() # register each worker that have entered this area without blocking.

if self.trainer.is_global_zero:
   entered_ranks = self.trainer.strategy.count_entrance() # get the number of workers that have entered this area.
   if entered_ranks < self.trainer.world_size:
       # wait

These statements don't make sense. There is only one process per GPU always. You can't have collective operations or synchronization under a guard like if self.trainer.is_global_zero:.
Also, num_ranks = self.trainer.world_size) is always True. rank is the process index, and the total count of ranks/processes is the world size by definition. Can you please try https://github.com/Lightning-AI/pytorch-lightning/issues/19453#issuecomment-1941435882?

With num_ranks = self.trainer.world_size, I meant that  stop_until_entrace  gets the information to wait until the defined number of ranks num_ranks have entered the area. So we want to wait until all self.trainer.world_size have finished. But we want to wait only on rank 0.
Each GPU that goes through self.trainer.strategy.register_entrance()  increments a counter on rank 0.
Rank 0 then checks with stop_until_entrace the value of the counter. If the counter is below num_ranks, it is blocked and waits.
I am not sure if this is possible to implement.

Sure yes, if listing the directory is expensive, then that will be a bit more efficient.

Did you manage to make it work? Did you have any further questions about this?

@awaelchli I actually found a solution to the approach I was proposing.
Since I have a shared folder, each rank creates a file in the shared folder to signal that it has gone through validation_step.
Now when rank 0 enters on_validation_epoch_end  it will look into the shared folder, count the number of files in the shared folder. If the number of files is less than the number of desired files (number of files must be self.trainer.world_size), I will send that rank for t seconds to sleep via time.sleep() and check again.
This way, only rank 0 is blocked, but not the other ranks.
May be this mechanism could be integrated into pytorch lightning?


Added subheadings to sidebars

Problem: The Old versions and Tags pages have sidebars that look different because they don't use sidebar subheadings.
Solution: Add subheadings to these sidebars. The Old versions sidebar has subheadings that group the items by alphabet letters. When we add more items to the sidebar, more letters of the alphabet will automatically appear.
Note that the Tags section is disabled so you can't check this one, but we will check everything later when we publish the tags pages.

This seems a bit funky... almost all the "DEA ..." products are clustered under D, except "DEA Waterbodies" which is somehow under W. Can we get all the D entries under their letters too? (e.g. "DEA Fractional Cover" under F?)

This seems a bit funky... almost all the "DEA ..." products are clustered under D, except "DEA Waterbodies" which is somehow under W. Can we get all the D entries under their letters too? (e.g. "DEA Fractional Cover" under F?)

@robbibt You're right... it was funky. I've now fixed this which you can see on the new preview.


Add Northport High School

Add Northport High School.
E-Mail Domain: @northport.k12.ny.us.

@NYISLANDERFAN Pull request merged. Thank you!


fix(commit format)!: change to commit order and fix for find

Change to commit order so that type, scope, and ticket number always appear in the same order.
[BREAKING CHANGE] As this is a change to the commit ordering, this may effect consumers of this repos handling in pipelines or other integrations.
fix to finder function to handle when relative resolves to "../.." or "../", by trimming string of these characters

Thanks for the PR!
Unfortunately, as this PR would introduce a breaking change for every consumer, I won't be considering it as-is.
I have previously toyed with the idea of introducing a new config option for a user to supply their own commit string template, although I haven't had the time to look into the implementation of it myself as of yet. If this sounds like something you'd be interested in doing, please feel free and I'd be very welcome to another PR! Otherwise, it's still on the roadmap for the project.
The fix for FindConfigFile is a welcome one, and if you were to include this in it's own PR I'd be happy to merge it in.

@RoderickMcLean I've just released a new version that includes support for commit message templates, let me know if this works for you!


Failed to realize renderer of type 'GskGLRenderer' for surface 'GdkWaylandToplevel' on non-NixOS systems

Describe the bug
On non-NixOS systems an error appears in the console when starting the GTK4 applications:
Gsk-Message: 11:05:21.626: Failed to realize renderer of type 'GskGLRenderer' for surface 'GdkWaylandToplevel': Failed to create EGL display

I noticed it in this packages:

Amberol
Fragments
Collision (when packaging it)
rtfm (when packaging it)
Plots (when packaging it, because of it I created the issue)

it seems that in most cases the program does not break in any way, but not in the case of Plots.
Steps To Reproduce
Steps to reproduce the behavior:

Install nix-env on non-NixOS system
Install any gtk4 application
Run it from terminal

Expected behavior
No errors and warnings.
Screenshots

Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.0-10-amd64, Debian GNU/Linux, 12 (bookworm), nobuild`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.16.1`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/home/sunder/.nix-defexpr/channels/nixpkgs`

I encoutnerd a similar issue. Does anyone know how to solve this?

There is no 3d acceleration for applications installed via nix-env on non-nixos systems. Probably you need to use nixGL to fix this issue.

@supermarin, that linked thread isn't accessible unless you're in the ghostty beta.

Sorry about that, copy-pasting the comment here:

@jcollie:  I think that something has changed on NixOS Unstable where binaries compiled with older versions of NixOS no longer work. Ghostty is by default built against NixOS 23.05. To build Ghostty against NixOS Unstable you'll need to add something like this to your configuration:
ghostty = {
url =<EMAIL_ADDRESS>inputs.nixpkgs-stable.follows = "nixpkgs-unstable";
inputs.nixpkgs-unstable.follows = "nixpkgs-unstable";
}

OOT: @supermarin, did you already create a Ghostty package for NixOS? I saw traces in https://github.com/search?q=repo%3Asupermarin%2Fdotfiles Ghostty&type=code. Does Ghostty provide a nix flake in their private repository!?

There is a flake already in the repo :)
They will release 1.0 soon and you should be able to use it. Otherwise if you need to test something see if you can get onto private beta.

Thank you! Yeah, I was now trying to get on the beta. But it's tedious. 😊


BadRequestException: Invalid OpenAPI input

Describe the Bug
Terraform apply fails with the following error
╷
│ Error: error creating API Gateway specification: BadRequestException: Invalid OpenAPI input.
│
│   with aws_api_gateway_rest_api.this[0],
│   on main.tf line 9, in resource "aws_api_gateway_rest_api" "this":
│    9: resource "aws_api_gateway_rest_api" "this" {
│
╵

Expected Behavior
The OpenApi attribute is not set so it should use the default, empty object {}.
Steps to Reproduce
Steps to reproduce the behavior:

Go to '...'
Run '....'
Enter '....'
See error

Screenshots
If applicable, add screenshots or logs to help explain your problem.
Environment (please complete the following information):
Anything that will help us triage the bug will help. Here are some ideas:

OS: Fedora
Version 3.6
Terraform apigw module version: 0.3.1

Additional Context
I am using terragrunt and I am not sure if you are willing to consider this bug report but I will include my config below regardless.
The account-settings module applies fine and returns the role_arn output.
dependency "apigw_account_settings" {
  config_path = "${get_terragrunt_dir()}/../apigw-account-settings"
  mock_outputs_allowed_terraform_commands = ["plan", "validate"]
  mock_outputs = {
    role_arn = "fake-role-arn"
  }
}

inputs = {
  stage = "test"
  stage_name =  "test"
  name = "apigw"
  tags = {
    ManagedBy    = "Terraform"
    Owner = "<masked>"
  }

  role_arn = dependency.apigw_account_settings.outputs.role_arn
  metrics_enabled = true
  xray_tracing_enabled = true
}

Update:
If I use the OpenApi example config I am able to apply.

We started out trying to use this module along with the tf resources to define methods and integrations. The hard requirement to provide the open api spec prevents us from doing that.
The details of how to configure the APIGW with the openapi spec in different scenarios are very poorly documented if the goal is to replicate something defined without a template (Chalice is what we're trying to replace with TF). This bug is forcing me to write my own module to get away from the OpenAPI spec file or figure out the exact format spec file needed to replicate.
It would be great if we could get an update to make supplying the template optional.

I also struggled with this problem for a while. The key thing is to keep that openapi version attribute in the JSON (or YAML or whatever you have) to 3.0.1 and not anything else. It will raise a BadRequestException: Invalid OpenAPI input. and even if you add a Terraform trace, it will give you nothing useful debugging wise.


Save definition files to different directory

Hi.
Is it possible to specify path where to save created .d files?
By default is it created next to .vue file.
Thanks.

I need this feature too. @ktsn , are you ok for a PR about it ?

Yeah, feel free to make a PR!


Empty or non-existent _posts folder results in "Unprocessable Entity"

Steps to reproduce:

mkdir no-posts-folder && cd no-posts-folder && reptar init
rm -rf _posts
reptar watch

Expected result:
Reptar renders _templates/index.html with an empty loop.
Actual result:
{
  "statusCode":422,
  "error":"Unprocessable Entity",
  "message":"Cannot read property 'assetProcessor' of undefined"
}

Oho! NIce find!

Fix I went with was to show a prettier error message. The default scaffold site has the index.html file derived from all the files on your page, without any files then that file doesn't exist. So to have an empty loop is actually a lot harder than it might appear.


08 24 feat sparkles add hychain metrics

I'm curious if this collector is repeating the metrics already collected by the Netdata agent running on the VM. Since it appears it's only collecting the time and status of the process related to the node? If there isn't a CLI or metric provided by the software, we might need to incorporate a API call to the blockchain and see if rewards are being collected as a proxy.


Remove empty space when no-sidebar

When I turn off the leftsidebar, like here:
https://pydata-sphinx-theme.readthedocs.io/en/stable/demo/no-sidebar.html
There is still a lot of empty space on the left side. Any way I can remove that to have it fill up the whole space?

We improved the spacing a bit recently and documented how you could make things grow to fit the screen!
https://pydata-sphinx-theme.readthedocs.io/en/latest/user_guide/customizing.html#horizontal-spacing
I'll close this one as I think it's resolved


standalone_2/io/secure_socket_renegotiate_test fails with RuntimeError

tools/test.py -n dartk-linux-release-x64 standalone_2/io/secure_socket_renegotiate_test

Client failed, stdout:

  stderr:
tests/standalone_2/io/secure_socket_renegotiate_client.dart:47:31: Error: The argument type 'Utf8Decoder' can't be assigned to the parameter type 'StreamTransformer<Uint8List, dynamic>'.
 - 'Utf8Decoder' is from 'dart:convert'.
 - 'StreamTransformer' is from 'dart:async'.
 - 'Uint8List' is from 'dart:typed_data'.
        socket.transform(utf8.decoder).transform(new LineSplitter()));
                              ^

There is a similar failure in standalone/io/secure_socket_renegotiate_test in NNBD weak mode.
If I change secure_socket_renegotiate_client.dart to use utf8.decoder.bind(socket) instead of socket.transform(utf8.decoder) (as CHANGELOG recommends), the test still fails.
--- a/tests/standalone_2/io/secure_socket_renegotiate_client.dart
+++ b/tests/standalone_2/io/secure_socket_renegotiate_client.dart
@@ -44,7 +44,7 @@ void runClient(int port) {
     expectEquals('CN=localhost', certificate.subject);
     expectEquals('CN=myauthority', certificate.issuer);
     StreamIterator<String> input = new StreamIterator(
-        socket.transform(utf8.decoder).transform(new LineSplitter()));
+        utf8.decoder.bind(socket).transform(new LineSplitter()));
     socket.writeln('first');
     input.moveNext().then((success) {
       expect(success);

Unhandled exception:
Expect.isTrue(false) fails.
#0      Expect._fail (package:expect/expect.dart:698:5)
#1      Expect.isTrue (package:expect/expect.dart:141:5)
#2      runServer.<anonymous closure>.<anonymous closure>.<anonymous closure> (file:///.../tests/standalone_2/io/secure_socket_renegotiate_test.dart:37:16)

/cc @tvolkert @lrhn @sortie @zichangg

Is there an underlying error in the StreamIterator that's not showing up in the test logs when you make that change?  What happens if you change it to socket.cast<List<int>>().transform(utf8.decoder)?

There are failing expectations on the client side of things(client is launched as a separate process) that cause this Expect.isTrue(false) to fail - those are easy to fix.
However there is bigger problem: implementation fo SSLFilter::Renegotiate seems to be doing nothing now since we migrated to boringssl here: https://github.com/dart-lang/sdk/blame/13bf8ff9f8d0f993673ac40bda08bde460ba71dd/runtime/bin/secure_socket.cc#L1009.
@whesse do you remember context for that decision? Was it just left to be implemented later? I expect we repeat handshake like we did before boringssl migration.

I'm not sure what the discussion was at that point, but renegotiation is now discontinued, and not a part of the current TLS standard.
Removing the ability to provide a named client certificate, I remember, because the use cases all included where the server specified what client certificate it wanted, and the client had it in its certificate database, so it didn't need to be passed separately.
But renegotiation to get a client certificate after the secure connection is already made is now discouraged (and not supported), according to all I can find on the Internet.  There seem to be fundamental insecurities with it, and most SSL client libraries (like Java) have removed it.
I think we should deprecate/remove the renegotiate method on our secure socket classes, and remove the tests.

Given that it was broken for last five years, yeah probably nobody will notice if renegotiate method simply disappears.
One point though is that the boringssl which we build our api on does support renegotiation https://boringssl.googlesource.com/boringssl/+/65703b45c47bb71cfcb972edea00d82218cb0f9d/PORTING.md#tls-renegotiation - it does so with particular caveats which makes it safe to use. I thought that there might have been some reasons why didn't hook it up when we switched from openssl to boringssl.

OK, I just discovered this issue independently. It looks like renegotiate never did anything
I will deprecate it and update the docs.

Fixed in cdcc221d6020f545b8a99dc3a8a8c14e3eb61949


invalid header: 0x64616873 after Flashing with ESPHome

Hardware
ESP32
Firmware version
v2.4.0
Application version
v2.4.0
What happened? What did you expect to happen?
I try to flash to a ESP32 with ESP Home. Unfortunately, it will not boot after flashing with invalid header: 0x64616873
How to reproduce it (step by step)
1.) Downlaoded SomfyController.ino.esp32.bin
2.) Go to https://web.esphome.io/
3.) Install and choose file

Logs
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
invalid header: 0x64616873
invalid header: 0x64616873
invalid header: 0x64616873
invalid header: 0x64616873
invalid header: 0x64616873
invalid header: 0x64616873
invalid header: 0x64616873

Additionally, if I try to flash it with ESPHome-Flasher. It will flash and boot, but then I get an error regarding little-fs.
Detecting chip type... Unsupported detection protocol, switching and trying again...
Connecting....
Detecting chip type... ESP32
Connecting....
Chip Info:

Chip Family: ESP32
Chip Model: ESP32-D0WD-V3 (revision 3)
Number of Cores: 2
Max CPU Frequency: 240MHz
Has Bluetooth: YES
Has Embedded Flash: NO
Has Factory-Calibrated ADC: YES
MAC Address: A0:A3:B3:A9:E7:54
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Flash Size: 4MB
Flash Mode: dio
Flash Frequency: 80MHz
Erasing flash (this may take a while)...
Chip erase completed successfully in 1.9s
Flash will be erased from 0x00001000 to 0x00004fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x0000e000 to 0x0000ffff...
Flash will be erased from 0x00010000 to 0x00146fff...
Compressed 15856 bytes to 10276...
Writing at 0x00001000... (100 %)Wrote 15856 bytes (10276 compressed) at 0x00001000 in 0.4 seconds (effective 308.6 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 144...
Writing at 0x00008000... (100 %)Wrote 3072 bytes (144 compressed) at 0x00008000 in 0.1 seconds (effective 217.6 kbit/s)...
Hash of data verified.
Compressed 8192 bytes to 47...
Writing at 0x0000e000... (100 %)Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.1 seconds (effective 596.1 kbit/s)...
Hash of data verified.
Compressed 1270720 bytes to 796772...
Writing at 0x0014298a... (100 %)Wrote 1270720 bytes (796772 compressed) at 0x00010000 in 20.8 seconds (effective 489.0 kbit/s)...
Hash of data verified.

Leaving...
Hard Resetting...
Hard resetting via RTS pin...
Done! Flashing is complete!
Showing logs:
[15:33:09]E (432) esp_core_dump_flash: ɕdump partition found!
[15:33:09]E (432) esp_core_dump_flash: No core dump partition fo
[15:33:09]Startup/Boot....
[15:33:09]Mounting File System...
[15:33:09]E (10) esp_littlefs: ./components/esp_littlefs/src/littlefs/lfs.c:1347:error: Corrupted dir pair at {0x0, 0x1}
[15:33:09]
[15:33:09]E (11) esp_littlefs: mount failed,  (-84)
[15:33:09]E (15) esp_littlefs: Failed to initialize LittleFS
[15:33:09]Error mounting file system
[15:33:09]Chip Model ESP32-
[15:33:09]Preference IP Free Entries: 621
[15:33:14]SECURITY   Type:0 Username:[] Password:[] Pin:[] Permissions:0
[15:33:14]Connection Type: 1
[15:33:14]NTP Settings
[15:33:14]pool.ntp.org TZ:
[15:33:14]WIFI Settings
[15:33:14] SSID: [] PassPhrase: []
[15:33:14]
[15:33:14]Launching web server...
[15:33:14]Creating Web MicroServices...
[15:33:15]WiFi Mode: 0
[15:33:19]Scanned 17 Networks...
[15:33:19] 0: SuperWireless (-54dBm) CH:3 MAC:46:22:54:6E:5D:21
[15:33:19]*1:  (-55dBm) CH:3 MAC:46:22:54:6E:5D:20
[15:33:19]*2:  (-64dBm) CH:3 MAC:5A:22:54:6E:6F:4D
[15:33:19] 3: SuperWireless (-65dBm) CH:3 MAC:5A:22:54:6E:6F:4E
[15:33:19] 4: FRITZ!Box 7530 FM (-80dBm) CH:11 MAC:98:9B:CB:B5:2D:68
[15:33:19]*5:  (-84dBm) CH:5 MAC:96:9A:4A:FC:8B:94
[15:33:19] 6: IlyHome (-85dBm) CH:5 MAC:90:9A:4A:FC:8B:94
[15:33:19] 7: Tenda_F4E250 (-88dBm) CH:6 MAC:50:0F:F5:F4:E2:5C
[15:33:19] 8: DIRECT-3B-HP Laser 179fnw (-89dBm) CH:11 MAC:7E:4D:8F:6F:4D:3B
[15:33:19] 9: SuperWireless (-90dBm) CH:3 MAC:4A:22:54:6E:6F:62
[15:33:19] 10: PBS-6D805D (-91dBm) CH:1 MAC:D4:D1:84:6D:80:62
[15:33:19]*11:  (-91dBm) CH:3 MAC:4A:22:54:6E:6F:61
[15:33:19]*12:  (-92dBm) CH:6 MAC:50:0F:F5:F4:E2:56
[15:33:19]*13:  (-93dBm) CH:10 MAC:EA:FA:C4:46:61:7A
[15:33:19]*14:  (-94dBm) CH:8 MAC:2E:87:BA:EC:4E:36
[15:33:19] 15: Deko_80CC (-94dBm) CH:8 MAC:28:87:BA:EC:4E:36
[15:33:19] 16: DECO (-95dBm) CH:10 MAC:E4:FA:C4:46:61:7A
[15:33:19]Socket Server Started...
[15:33:19]Max Heap: 110580
[15:33:19]Free Heap: 185836
[15:33:19]Min Heap: 183384
[15:33:19]
[15:33:19]Turning the HotSpot On
[15:33:19]Initializing AP for credentials modification
[15:33:19]
[15:33:19]SoftAP IP: <IP_ADDRESS>

I found the issue! Sorry for that, i've used the wrong bin File for flashing!


Please make the python executable configurable through cmake

On FreeBSD several versions of python can be installed at the same time, with different executable names.

@yurivict In general, HPX does not require any specific python executable to be built. We only install a python script hpx_run.py that can be helpful for running HPX applications. This script should be compatible with any Python version, so I don't think we need to make the Python executable configurable as this script will be used by the user in the end.

But you embed a specific executable name python, and this fails.

@yurivict Fair enough.

I think we have some old Python 2-style print statements hanging around, but otherwise nothing that would still require Python 2 (AFAIK). This should be a straightforward change if someone feels like having a go at this. And I don't think we need to support Python 2 anymore. It's time to let it go...

@msimberg it shouldn't be a problem to change the code such it is compatible with any Python version.

@hkaiser @msimberg pr #3761 provides the changes such that our scripts run with python3 on Fedora 29.

The question is: is there a need for the user to actually change the python executable, or is it enough that it works with both Python 2 and 3 and the user doesn't care which? @yurivict I'm guessing in your case it was actually the latter, and not that you necessarily need to be able to set the Python executable?

is there a need for the user to actually change the python executable

The package should always work with a specific version of the python executable. Reasons: 1. predictability 2. you might not be able to guess what the executable is.
This is why there should be a configuration variable for it.

@yurivict does #3803 do what you had in mind?

@yurivict I'm closing this now that #3803 has been merged. Please reopen if needed.


support for namespaced models

Hi!
This small fix makes it possible to use idy for namespaced models, such as "Namespace::Modelname".
Thanks for your amazing gem!

Hi @vzctl , thanks for your PR! :)
Could you add a context for this case on test?

Closing in favour of #10


MissingPluginException(No implementation found for method hasPermissions on channel plugins.builttoroam.com/device_calendar)

i need to retrieve Calendars events in my app
the below function i have used :
_retrieveCalendars()async{
try {
  var permissionsGranted = await _deviceCalendarPlugin.hasPermissions();
  if (permissionsGranted.isSuccess && !permissionsGranted.data) {
    permissionsGranted = await _deviceCalendarPlugin.requestPermissions();
    if (!permissionsGranted.isSuccess || !permissionsGranted.data) {
      return;
    }
  }

  final calendarsResult = await _deviceCalendarPlugin.retrieveCalendars();
  _calendars=calendarsResult.data;
  for(int c=0;c<_calendars.length;c++){
    calendarName.add(_calendars[c].name);
  }

} on PlatformException catch (e) {
  print(e);
}

}

Does this issue appear with latest dev version? And on which device?

Possible duplicate of https://github.com/builttoroam/device_calendar/issues/303. Closing since issue 303 is resolved.


feat(customer): add customer model and specs

Initial round to contribute the customer model to the repo.
This includes:

customer-draft
customer
specs
transformers
builders

Presets with addresses are not included at this time.

@valoriecarli It looks like the PR has some "bad rebase" artifacts (you can see that it contains changes that didn't belong to this branch).
Could you double check? You might need to rebase your changes again.


Proposal: TabView Parity with WCT TabView

Proposal: TabView Parity with WCT TabView

Summary

The WinUI TabView is missing two main features relative to the Windows Community Toolkit TabView:
Tab Width Behavior: Compact API Link
The unselected tabs show only their icon and no text until they are selected.

Overlay Close Button API Link
The x-to-close button is shown when the user hovers over the tab.

Rationale

The WinUI TabView is so close to being feature complete relative to the Windows Community Toolkit TabView. Once WinUI TabView is at parity, we can deprecate the WCT TabView.

Scope

Capability
Priority

Tab Width Behavior: Compact
Must

Overlay Close Button
Must

Important Notes

The proposed API for these properties is outlined in #304, which is the initial proposal for TabView.
Specifically, the following APIs are proposed:
Tab Width Behavior: Compact
Existing enum (with new value) and existing property
TabWidthMode : {Equal, SizeToContent, Compact}
<TabView TabWidthMode="Compact" />
Overlay Close Button
New enum and property
CloseButtonOverlay : {Auto, OnHover, Persistent}
<TabView CloseButtonOverlay="OnHover" />
Open Questions

Can we get Tab Placement for sides and bottom at some point too?

This issue is specifically about getting to parity with the Windows Community Toolkit version. We'd like to have alternate Tab Placement modes, but those features are tracked in #1332.

I would like to tackle this issue :)
CC @ranjeshj @jevansaks

I have already finished most features of this proposal, however there are a few questions that came up during development:

How should we handle "Compact" mode with tab items that have no icon? Should we show nothing (which looks a bit confusing in my opinion)
How should the "Auto" CloseButtonOverlayMode work?

Current status:

@chingucoding Based on a previous spec for TabView:
CloseButtonOverlayMode

Describes the behavior of the close button of unselected tabs. Values are {Auto, OnHover, Persistent}. Default is Auto. In WinUI 2.2, Auto maps to Persistent.

@stmoy can say if anything has changed since then (I'm not aware of a spec change). I think it's fine if you'll go ahead and treat Auto as mapping to Persistent.

If Auto should behave like Persistent is there any reason to have that option at all?
Having multiple options that are equivalent creates unnecessary confusion in my opinion.

@chingucoding Reading further through the spec review of TabView V1, it seems there is still room for discussion about this setting in a future TabView V2 spec. The default value itself (currently Persistent) might be up to a change. Based on this thinking, using Auto in your UI would always give you the current default button overlay mode if your app's TabView should follow the default system UI. That said...the default value shouldn't be changed back and forth multiple times over the lifetime of WinUI and its TabView control. If it does change, however, you are covered.

There are pro's and con's to that reasoning. On the one hand, yes developers always align with the system when we say "Auto will always be the default, but what Auto will actually be may change".
But what happens if we change what Auto maps to? Then, apps behaviors may become more inconsistent as the TabView has changed without the app being updated for that accordingly i.e. that there may be visual inconsistencies.
Having this "System default that might change" is not my favorite option. If devs want the default option, why not make it the initial value, instead of having a sort of wrapper for the current default.

How should we handle "Compact" mode with tab items that have no icon? Should we show nothing (which looks a bit confusing in my opinion)

In general, my philosophy is: do what WCT does (unless what WCT is bad).
WCT behavior in this case seems to be agnostic to the Icon/Content - meaning the Tab always has a fixed width for both the unselected and selected state. This results in the behavior of the Text showing when the tab is unselected, which I don't think is a great look.
The following markup produces the following visuals:
      <controls:TabViewItem Header="Home" Icon="Home">
        <TextBlock Padding="16">The TabView control has multiple uses.</TextBlock>
      </controls:TabViewItem>
      <controls:TabViewItem Header="Tab 3">
        <TextBlock Padding="16">You can enable drag-and-drop and reorder the tabs too.</TextBlock>
      </controls:TabViewItem>
      <controls:TabViewItem Header=" ">
        <TextBlock Padding="16">You can enable drag-and-drop and reorder the tabs too.</TextBlock>
      </controls:TabViewItem>

Tab 1 Selected

Tab 2 Selected

Tab 3 Selected

My preferred behavior would be that tabs without icons would show blank regardless of if their text is set.
Thoughts?

How should the "Auto" CloseButtonOverlayMode work?

The platform uses Auto as the default enum value in several situations, including places where the developer expects some automatic behavior (like TeachingTipPlacement) or places where the mode describes a visual layout that might change later. Basically all of the enums that describe UI and end in *Mode have an Auto value as their default. (CoreDragUIContentMode,ElementSoundMode,NavigationViewPanDisplayMode,TeachingTipPlacementMode,etc.)
To that end, since there is already the Persistent behavior, I think the introduction of Auto makes sense.

If devs want the default option, why not make it the initial value, instead of having a sort of wrapper for the current default.

Semantically, I think Auto actually means "I don't have an opinion, let the platform decide for me" and not "I specifically like the default value". Auto represents the platform default, meaning that apps that don't have an opinion will have consistent behavior with other apps by default even if the default changes. The alternate without Auto is that if the default changes, every app will need to update their default in order to remain consistent with the system.
CC: @MikeHillberg

My preferred behavior would be that tabs without icons would show blank regardless of if their text is set.

Thoughts?

Yes that seems to be the best way in my opinion. Showing 3 letters of the TabItem header usually isn't really helpful, so I think this is the best way to handle missing icons.

Semantically, I think Auto actually means "I don't have an opinion, let the platform decide for me" and not "I specifically like the default value". Auto represents the platform default, meaning that apps that don't have an opinion will have consistent behavior with other apps by default even if the default changes. The alternate without Auto is that if the default changes, every app will need to update their default in order to remain consistent with the system.

Oh, I see. I have updated the PR accordingly so that Auto behaves the same as Persistent .

Could it be possible to have an option making the same style and looking as WCT TabView? WCT TabView is gonna be deprecated but I really miss its reveal and acrylic effects, which, in my opinion, still looks more consistent with the current Fluent Design system. I also know some developers want to style their TabView in that way, so it would be great to provide an option such that they can update from WCT without re-designing their apps. Furthermore, I'm also wondering in the future of WinUI3, as everything will be united, in addition to matching the chromium Edge from WinUI side, can Edge also steps towards the current fluent design? It would be great to see Edge uses TabView and other WinUI components and becomes more "fluent" :)

If the WCT version has fluent, then the WinUI TabView needs fluent in order to obtain parity.


Package of version 1.7.0 is signed with the wrong private key

Besides the issue reported in https://github.com/bkuhlmann/git-cop/issues/35, there's another issue that prevents users from installing this gem.
It seems that the package of version 1.7.2 is signed with a private key that does not correspond to the public key in your certificate available at https://www.alchemists.io/gem-public.pem.
The SHA256 hashes of the public key in the  aforementioned certificate, and the one provided in the package are different.
This is the (self-signed) certificate that is provided in the signed gem/package:
-----BEGIN CERTIFICATE-----
MIIDNjCCAh6gAwIBAgIBAjANBgkqhkiG9w0BAQUFADBBMQ8wDQYDVQQDDAZicm9v
a2UxGjAYBgoJkiaJk/IsZAEZFgphbGNoZW1pc3RzMRIwEAYKCZImiZPyLGQBGRYC
aW8wHhcNMTcxMDI1MTIxMDU4WhcNMTgxMDI1MTIxMDU4WjBBMQ8wDQYDVQQDDAZi
cm9va2UxGjAYBgoJkiaJk/IsZAEZFgphbGNoZW1pc3RzMRIwEAYKCZImiZPyLGQB
GRYCaW8wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCgryPL4/IbWDcL
fnqpnoJALqj+ega7hSsvvD8sac57HPNLeKcOmSafFiQLAnTmmE132ZlFc8kyZRVn
zmqSESowO5jd+ggFuy1ySqQJXhwgik04KedKRUjpIDZePrjw+M5UJT1qzKCKL2xI
nx5cOKP1fSWJ1RRu8JhaDeSloGtYMdw2c28wnKPNIsWDood4xhbLcY9IqeISft2e
oTAHTHandHbvt24X3/n67ceNjLBbsVZPXCC1C8C8ccjHjA4Tm2uiFoDwThMcPggg
90H6fh0vLFcNAobdPEchbge8tWtfmMPz2+C4yklANn81GA+ANsBS1uwx6mxJoMQU
BNVp0aLvAgMBAAGjOTA3MAkGA1UdEwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdDgQW
BBRS85Rn1BaqeIONByw4t46DMDMzHDANBgkqhkiG9w0BAQUFAAOCAQEAJn1nVdx9
4FneO7dkqNHOuuSfhXZz05NSfZ6XLmKVeDaoUEO4k3ii8Ho9QJHDCubDZTpjB00l
lrw6XT2WCP+OKI+FLFLAe7RIqoJgZC0VpViPJS1PX28Xuv2Yvp0Aj//rTRB9vuYI
lHadnxmbYKlZCgSqFQbmKfUo1spvYX9SEGaeUkpfhHa59sq0UbIFCfLtQ3hNGPEb
Qkkb8H5hgCTGheH5NJbEfnpCNsAZM4H2lg1HoSmc03xN8ajeTB0Y8VA84U89tKP8
5CXiAU6zuRjW5Q562D7SMKZl8RVVhWxoxV4V3w/3LY922oGdOyYFEjUpp/GE3jEg
l1XwX/SFtXe76Q==
-----END CERTIFICATE-----

Find the hash of the public key in that certificate:
$ openssl x509 -in gem_cert.pem  -pubkey -noout | openssl rsa -pubin -outform der | openssl dgst -sha256

dab54a57050aa3b53aa9722192ae081b7c22bcb4980891f3f9ae6d7bfae3cded

Then find the hash of the public key that is in the certificate that is provided through the aforementioned URL:
$ curl https://www.alchemists.io/gem-public.pem | openssl x509  -pubkey -noout | openssl rsa -pubin -outform der | openssl dgst -sha256

bc613ecbbe7a9d0589a9ff91a4638ff39c26029f4daaba7a8440231037a4fd5c

Note that the public key hashes are different.

:information_source: Updated issue label to refer to 1.7.0 since 1.7.2 doesn't exist.

Sorry about this and thanks for catching this. I figured out the source of the problem. I had updated the certificates, in a previous issue you reported, but didn't replicate them across the all of the machines I use. I've resolved this now so I can build on all machines without using bad certificates.
This has been fixed in Version 1.7.1 which is available for download now.


Create settings for extensions within the settings modal

Description of the new feature / enhancement
This is an additional part of what is required in #80 for the extensions specifically.
Extensions should be able to host their own settings to help determine how the extension will behave.
Scenario when this would be used?
When extensions want to author settings and when users want to change settings for an extension
Supporting information
No response

(I'm tagging this up as the third of the work specifically for "the palette can render things spec'd by #122 and implemented in the extensions with #123"). We still need to do the work to link to these settings, if an app provides them.


Add initial test coverage

Add initial test coverage. Given the dated Clair DB docker images, should be able to get nice test verifying final output against test container images

Working in 5d8d17e


Load views from nib incorrect resize

Views loaded from nib and added to the contentView are resized incorrectly (much bigger), is there a reason for that? I canno't find why

@jillhc and I just ran into a similar issue. Ultimately, what fixed it for us was making sure the views we added to the content view had translatesAutoresizingMaskIntoConstraints = YES and autoresizingMask = UIViewAutoresizingNone.
This prevented the subviews from resizing if they were added to the content view prior to the content view's size being adjusted in -[OLEContainerScrollView layoutSubviews].
We only had this problem on devices with 480 pt-tall screens running iOS 7. The 568 pt-tall screens did not encounter the issue because the scroll view started out at the correct height when unarchived from the xib. On iOS 8, our particular usage ended up triggering layout that set the content view's height appropriately prior to when we added subviews. I'm not sure that this is guaranteed in the general case though—we may have just been "lucky".
@ole We think it would make sense for OLEContainerScrollView to ensure that all subviews added to the content view are set appropriately in this regard. Thoughts?

@macdrevx Sorry for the late reply. I pushed a fix which works in my tests, although I chose to set translatesAutoresizingMaskIntoConstraints = NO because that makes more sense in my opinion. The container scroll view does not use autolayout internally so the subviews' autoresizing masks should really not be translated into layout constraints. Anyway, I hope this works for you. Thanks for the research.

@ole We tried translatesAutoresizingMaskIntoConstraints = NO initially as well, but we ran into issues with infinite recursion (on 8.2)/infinite layout loop (on 7.1) with something related to layout. Do you have any insight into what might cause that to happen?


CI: GKE: K8sServicesTest Checks service across nodes Tests NodePort (kube-proxy)

Stacktrace
/home/jenkins/workspace/Cilium-PR-K8s-GKE@2/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:514
Cannot retrieve loadbalancer IP for test-lb
Expected
    <*errors.errorString | 0xc000324af0>: {
        s: "could not get service LoadBalancer IP addr: 30s timeout expired",
    }
to be nil
/home/jenkins/workspace/Cilium-PR-K8s-GKE@2/src/github.com/cilium/cilium/test/k8sT/Services.go:920

Standard Output
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
No errors/warnings found in logs
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
No errors/warnings found in logs
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
No errors/warnings found in logs
Cilium pods: [cilium-gr8cs cilium-kcjjp]
Netpols loaded:
CiliumNetworkPolicies loaded:
Endpoint Policy Enforcement:
Pod                                                        Ingress   Egress
kube-dns-autoscaler-645f7d66cf-l6swh
l7-default-backend-678889f899-clnb9
test-k8s2-5b756fd6c5-vxgx8
testds-jkw78
kube-dns-7c976ddbdb-fslx4
fluentd-gke-scaler-cd4d654d7-jnlp7
testclient-m96vn
testclient-z6m7g
event-exporter-gke-8489df9489-x7hcm
prometheus-d87f8f984-5nz4n
metrics-server-v0.3.6-64655c969-9ljb8
stackdriver-metadata-agent-cluster-level-84c56c4b6-dxc58
grafana-7fd557d749-drzs6
testds-5r5gx
kube-dns-7c976ddbdb-gdkqb
Cilium agent 'cilium-gr8cs': Status: Ok  Health: Ok Nodes "" ContinerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 49 Failed 0
Cilium agent 'cilium-kcjjp': Status: Ok  Health: Ok Nodes "" ContinerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 55 Failed 0

https://jenkins.cilium.io/job/Cilium-PR-K8s-GKE/2799/testReport/Suite-k8s-1/16/K8sServicesTest_Checks_service_across_nodes_Tests_NodePort__kube_proxy_/
https://jenkins.cilium.io/job/Ginkgo-CI-Tests-Pipeline-GKE/2068/testReport/junit/Suite-k8s-1/16/K8sServicesTest_Checks_service_across_nodes_Tests_NodePort__kube_proxy_/
https://jenkins.cilium.io/job/Ginkgo-CI-Tests-Pipeline-GKE/2069/testReport/Suite-k8s-1/16/K8sServicesTest_Checks_service_across_nodes_Tests_NodePort__kube_proxy_/
https://jenkins.cilium.io/job/Ginkgo-CI-Tests-Pipeline-GKE/2066/testReport/junit/Suite-k8s-1/16/K8sServicesTest_Checks_service_across_nodes_Tests_NodePort__kube_proxy_/

First failing build: https://jenkins.cilium.io/job/Ginkgo-CI-Tests-Pipeline-GKE/2059/


Admin menu items should consistently specify a name attribute

Issue Summary
Wagtail's wagtail.admin.menu.MenuItem class allows specifying the name attribute on the constructor, falling back on the slugified version of the label if not specified:
https://github.com/wagtail/wagtail/blob/530531ab62075ffcb999a9b4c1e1aa06a8d41ed3/wagtail/admin/menu.py#L19
Wagtail's own menu items do not consistently specify name, e.g.:
https://github.com/wagtail/wagtail/blob/530531ab62075ffcb999a9b4c1e1aa06a8d41ed3/wagtail/users/wagtail_hooks.py#L78C1-L80
This means that when non-English languages are active, name will be a translated version of the string - as a result, code that relies on matching against the name attribute https://docs.wagtail.org/en/stable/reference/hooks.html#construct-main-menu will not work as expected.
We should ensure that all of Wagtail's own menu items registered through register_admin_menu_item, register_settings_menu_item and register_reports_menu_item explicitly specify the English-language name as the name attribute.
Steps to Reproduce
Create a hook function in wagtail_hooks.py:
@hooks.register('construct_settings_menu')
def hide_users_menu(request, menu_items):
    menu_items[:] = [item for item in menu_items if item.name != 'users']

Change language to something other than English - the Users menu will not be hidden as intended.

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: no

Ah, I thought I had caught them all in #10270, but I only looked for register_admin_menu_item and forgot that there are separate hook names for each SubmenuMenuItem. I haven't tested it individually but I'm pretty sure it is the same issue as #6111 which I did test, so I'll remove the Unconfirmed label for now.


Clarify Whole register move characteristics - as if store/load

This really only affects vstart and specifically what byte location in the register group it represents.
More specifically if striping of SLEN across the requested register set is implicit.
This patch punts the question and states that the vstart mapping of bytes is the same as whole register load/store. Even though the load/stores do not currently allow nf > 0, it does define the memory store order for multiple register store/loads, and thus it defines vstart mapping.
There is an open question whether whole register load/stores should stripe, but that can be settled later.
relates to #336 and PR #375
Signed-off-by: David Horner<EMAIL_ADDRESS>

This wording seems confusing. It could be read as implying that e.g. vmv2r.v v0, v0 is not a nop but instead permutes the bits in v0 and v1 in the same way bits are permuted when they're transferred from memory into a register. If the intent is to only copy the meaning of vstart, then it seems less confusing to duplicate the description of that behavior (or at least, specifically reference the vstart behavior of whole register loads). But as I just wrote in #336, I don't think whole register loads are the most meaningful point of reference for whole register moves (even if the numbering would be the same in the end).

So much for "clarifying".

This wording seems confusing. ....
I don't think whole register loads are the most meaningful point of reference for whole register moves (even if the numbering would be the same in the end).

Point taken. The whole register load equivalence was the justification, but an explicit clear description needs to be the objective.
When #379 is resolved I will rework this to make the description explicit, and equivalent with whoile register store/load if that is the preferred behaviour for the move.
Perhaps you want to weigh in on #379?

Simplify and further Clarify Whole Register Move order
Establish that Whole Register Move operates on the elements of
a register group as described in section
4.2. Mapping with LMUL > 1.
This makes any other Whole Register load/store the only outliers.

We can punt on deciding the semantics of the nr>1 whole register loads and stores.  But I am left wondering, why not do the simplest thing and define them to behave like unit-stride loads and stores with LMUL=nr?

@aswaterman  why not do the simplest thing and define them to behave like unit-stride loads and stores with LMUL=nr?
That is what I proposed in  #379.
(Although I didn't specify unit-stride only implied)

Hi Andrew,
I haven't followed the whole conversation, so please forgive me if I'm
being naive here.
Your proposal certainly makes sense.
However, I can think of two reasons not to do this, and a consequence:

supporting register grouping in load/store requires extra data
rearranging along the load/store path to the memory unit; the type of
rearranging requires buffering and may introduce additional latency.
however, issuing multiple vloads (rather than a register group) will likely
not incur any extra slowdown (just text size).

some method is needed to encode/decode vectors that are stored in the
register file using different SEW & LMUL values. if this data rearrangement
is done by vector move instructions, then there is no support for this
required in the load/store interface. however, right now there is no native
support for it among vector move instructions, so this feature definitely
needs to be in the load/store interface already. hence, these two topics
are conflated.

removing byte/half/word from vload/vstore is fine, but element size
information is still needed with indexed instructions and fault-only-first
loads (assuming there is a wish to retain these features). also for strided
loads/stores, the burst length will need to be defined (a burst may be
1,2,4 bytes, or even longer).

Guy
On Sun, Feb 16, 2020 at 4:23 PM Andrew Waterman<EMAIL_ADDRESS>wrote:

We can punt on deciding the semantics of the nr>1 whole register loads and
stores. But I am left wondering, why not do the simplest thing and define
them to behave like unit-stride loads and stores with LMUL=nr?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/riscv/riscv-v-spec/pull/378?email_source=notifications&email_token=ABMAPWNGZPUECPEGZLEWSYDRDHKGNA5CNFSM4KVVVCR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL4XIWA#issuecomment-586773592,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABMAPWIBAAOFT5WEZTYNGRLRDHKGNANCNFSM4KVVVCRQ
.

Re: "supporting register grouping in load/store requires extra data rearranging" -- I'm proposing that the instructions behave the same as regular vector loads and stores with the corresponding LMUL setting, so there's no new data movement pattern.  (In fact, avoiding creating new data movement patterns is exactly why I think it makes sense to do it this way.)
Regardless, having only vl1r/vs1r instead is probably OK.

Sorry, I was making an assumption that regular loads/stores don't do LMUL>1
either; ie they ignore vtype.
This means the only way to encode/decode data for LMUL>1 would be on the
compute side, not on the load/store side.
Guy
On Sun, Feb 16, 2020 at 5:04 PM Andrew Waterman<EMAIL_ADDRESS>wrote:

Re: "supporting register grouping in load/store requires extra data
rearranging" -- I'm proposing that the instructions behave the same as
regular vector loads and stores with the corresponding LMUL setting, so
there's no new data movement pattern. (In fact, avoiding creating new data
movement patterns is exactly why I think it makes sense to do it this way.)
Regardless, having only vl1r/vs1r instead is probably OK.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/riscv/riscv-v-spec/pull/378?email_source=notifications&email_token=ABMAPWNPLOR2FMXGNXRSXWDRDHPCNA5CNFSM4KVVVCR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL4YRTI#issuecomment-586778829,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABMAPWJZNF6JKLL27RR4LQTRDHPCNANCNFSM4KVVVCRQ
.

Got it.


[Test] Eased check assertion.

Eased filecheck expectations.

@swift-ci please smoke test and merge


Njtransitdepartureapp

Description
Update URL and HTML search of station names to resolve issue where stations werent being loaded for users to select.
Copilot

🤖 Generated by Copilot at acd6267
Summary
🚉🌐🔧

Update njtransit app to use a more reliable data source. Change the URL, request, and selector to match the new format.

NJ_TRANSIT_URL
New source for station data
Autumn leaves change too

Walkthrough

Change the URL and CSS selector for scraping station names and codes from the NJ Transit stations page (apps/njtransit/nj_transit.star link, link, link)

Hey. Thanks for the PR.
As you might've noticed already, the build is failing due a performance check. I think the main culprit is the ~0.5MB page your downloading to extract departures. I don't have any immediate ideas for how to fix that, but if it's possible to download the same data in a more stripped down format, then that might get you a green build.

Fixed the profiling error

Hi, how do we move this forward?

Let's give it a try. I'm guessing caching is gonna smooth over the slow data retrieval most of the time.

Let's give it a try. I'm guessing caching is gonna smooth over the slow data retrieval most of the time.

I mean this app has been here for like a year with no issues. I will be creating another PR within the next week to fetch from a private API that got setup to host the Transit data.


[Key Vault] Drop 2.7 and 3.6 support

Description
See https://github.com/Azure/azure-sdk-for-python/pull/22224 as a reference for the steps to drop Python 2.7 and 3.6 support.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

/azp run python - keyvault


Refreshing data in table + add icon to call method

I think about opportunity refresh my data.
How to call method on demand
fetchData() {
      this.$http.get('v_sim.php').then(response => {
        this.list = response.body
      }, response => { return 'error' })
    }

Maybe some simple solutions e.g. some icon similar to sortable in first header column?
Or maybe is something similar in library?
Thanks for v2-table :+1:
And for QuickStart & Example give :100:

call method on demand？？？more details?

Something similar to :
@sort-change="handleSortChange" - when click icon of 'sorting' then method handleSortChange() does it.
  <v2-table :data="list" @sort-change="handleSortChange" >
e.g. @refresh-data="fetchData" - push icon of 'refresh' to get data and display to table.

<template>
// Maybe you should put a button or a refresh icon to trigger fetchData outside the table
<button @click="fetchData">refresh</button>
<v2-table :data="list" @sort-change="handleSortChange">
<v2-table-column label="Rej" prop="rej" sortable ></v2-table-column>
 ...
</template>

I have no idea to put refresh icon inside v2-table. The data maybe can sort, so header columns should put sorting icon.

Yeah I was thinking about it.
It's not so elegant solution.
And have problem with call method via 'dashboard-container' where table is one of piece panel-group element.
But many thanks for reply.


Updates tags in charts

Description: Update tags for release v0.5.0-rc.1

Affected area:

New Functionality      [ ]
Documentation          [ ]
Install                [ ]
Control Plane          [ ]
CLI Tool               [ ]
Certificate Management [ ]
Networking             [ ]
Metrics                [ ]
SMI Policy             [ ]
Security               [ ]
Tests                  [ ]
CI System              [ ]
Performance            [ ]
Other                  [ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution?

lgtm


Fix for latest stack

Thanks! Will this work on older Stack as well? If not maybe we should add a check that the Stack version is high enough.

No I don't think it will work so yes we should do that I'll add it in
On 10 Jun 2016 17:59, "Joe Nelson"<EMAIL_ADDRESS>wrote:

Thanks! Will this work on older Stack as well? If not maybe we should add
a check that the Stack version is high enough.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/begriffs/haskell-vim-now/pull/181#issuecomment-225237810,
or mute the thread
https://github.com/notifications/unsubscribe/ABJccxZiQWhtVtedEOiZu-fbZsDulRNaks5qKZfogaJpZM4IzIU6
.

Done

Smart, that works.
What's that new file named <IP_ADDRESS> all about?

Removed that it's redundant

Or maybe we should ask user to install latest stack version? And check that version in setup.sh.

I'm going to merge this to be on the safe side. Later on if we like we can ask the user to install the latest slack version.


BinaryViewType['ELF'].open("/") segfault

system info
Ubuntu 16, commercial dev. Headless processing. Also crashes if I run it from binja's built-in python shell.
Repro
bv = BinaryViewType['ELF'].open("/")

That sounds like one that was fixed on dev a while ago -- are you on stable?

I'll have to check when I get back. Maybe when I put the new key it reverted to stable.

yep I'm on dev

Fixed in Build 809.


Investigate adding kerberos authentication support

It may have been successfully added in this fork: https://github.com/lorenz/go-smb2
with this commit: https://github.com/lorenz/go-smb2/commit/7a091ab768e3ed62d88a4933f65969dd2f6e05e0
citation here: https://github.com/hirochachacha/go-smb2/issues/63#issuecomment-1732749715

Hi @arashpayan, I'm willing to contribute this feature (based on @lorenz's work). Would you be open to taking a dependency on https://github.com/jcmturner/gokrb5?

That commit is all that's needed, it just needs to be cherry-picked into the repo. I didn't upstream it myself as upstream was abandoned. You probably want most of my other changes too, they fix various issues with go-smb2. Sadly this fork seems kind of abandoned as well.

@lorenz I've ported your commit to work with the upstream gokrb5 as I think we should avoid replace directives when possible.
Ultimately I'd like to add Kerberos support to the smb backend of rclone, which uses this fork.

Hi @jgiannuzzi. Thank you for the offer. Adding a dependency on github.com/jcmturner/gokrb5 is fine.
@lorenz, we heavily use this package at cloudsoda.io, so we're committed to maintaining it, but we only add new features when a business need demands it. That said, we're currently working on support for reading and writing security descriptors.

Thank you @arashpayan, I've raised a PR to implement this in #24.


Fix HttpMethod bug in Connect/DisconnectNetworkAsync

ConnectNetworkAsync and DisconnectNetworkAsync were making GET request (+ body) when POST is expected. This resulted in 404 response with the error

network {network-id}/connect not found

Code has been updated to use POST

Hi @cjlpowers, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

Thanks!

Any estimate on when the NuGet package will be updated?

There is still some work to do before the rest of the v1.25 API is completed. If you just need this bug fix I can post a smaller update to NuGet ahead of the major API update?

No worries. I can run off my version until you release v1.25.
Thanks


MSID: 98900 Version: 2 DOI: 10.21203/rs.3.rs-3793919/v3

MSID: 98900
Version: 2
Preprint DOI: https://doi.org/10.21203/rs.3.rs-3793919/v3
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=98900
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.21203/rs.3.rs-3793919/v3

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/98900v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.21203/rs.3.rs-3793919/v3
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/98900/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

Hi @fred-atherden this one contains subscript


Remove install-peers

this cripples dev experience unless we find another way to install peer deps. this will work for your purposes though. i think this could be solved by swapping to npm from yarn. ill look into it soon :)


Support existingSecret for redis configuration

Introduces scaling.redis.existingSecret and scaling.redis.existingSecretKey to enable referencing an existing secret containing the Redis password. This aligns with the Bitnami Redis chart, allowing both to use the same secret.

Is there any progress with this merger? This feature is highly appreciated.

Will merge, after resolving the discussion.

https://github.com/8gears/n8n-helm-chart/pull/81#pullrequestreview-1991106198

Will merge, after resolving the discussion.

yes, see #81 (review)

So @sebastiansterk are you able to set the commenting?


MSAL Interceptor unable to find cached token issued from custom OIDC server

Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
2.37.0
Wrapper Library
MSAL Angular (@azure/msal-angular)
Wrapper Library Version
2.5.7
Public or Confidential Client?
Public
Description
We are trying to use the MSAL angular library in OIDC protocol mode with a custom OIDC server but having trouble using the MSAL interceptor.
Shortly after logging in, when I trigger an HTTP request that activates the MSAL interceptor, the trace logs show that acquireTokenSilent is rejected and it tries to acquire by redirect, but this happens every time the interceptor is activated and the HTTP request is never actually made.  Not sure if it is a problem with our implementation client side or maybe if the OIDC server is not compliant. I can see all the tokens in local storage, but the interceptor seems to not capture them and I think it may relate to failure to check the authority meta data.
MSAL Configuration
auth: {
      protocolMode: ProtocolMode.OIDC,
      clientId: 'testApp',
      authority: 'https://localhost:44334',
      knownAuthorities: ["https://localhost:44334"],
      redirectUri: '/auth',
      authorityMetadata: JSON.stringify({
        authorization_endpoint:"https://localhost:44334/connect/authorize",
        token_endpoint:"https://localhost:44334/connect/token",
        issuer: "https://localhost:44334",
        end_session_endpoint: "https://localhost:44334/connect/logout",
      })
    },
    cache: {
      cacheLocation: BrowserCacheLocation.LocalStorage,
      storeAuthStateInCookie: isIE
    },
    system: {
      loggerOptions: {
        loggerCallback(_logLevel: LogLevel, message: string) {
          console.log(message);
        },
        logLevel: LogLevel.Trace,
        piiLoggingEnabled: false
      }
    }

Relevant Code Snippets
When the app comes back from the redirect, we subscribe to the MsalBroadcast service to ensure an active account.

   let activeAccount = this.msalService.instance.getActiveAccount();
    if(!activeAccount && this.msalService.instance.getAllAccounts().length > 0){
      activeAccount = this.msalService.instance.getAllAccounts()[0];
      this.msalService.instance.setActiveAccount(activeAccount);
    }

### Identity Provider

Other

### Source

Internal (Microsoft)

@alamfsmb Can you please share Trace level MSAL logs so we can help you debug? It's worth also mentioning that we do not have explicit support for any 3rd party identity providers. We'll do our best to unblock you by pointing you in the right direction but if fixes are needed on MSAL they're unlikely to be prioritized, it would likely fall on you to open a pull request with the changes. Just FYI.

Appreciate you taking a look for us! We understand there isn't official support, but hope we can still take advantage of this library. I've attached the logs generated after initiating the API call matching with our configured protectedResourceMap.  We don't have custom scopes so I just included the default scopes in the configuration.
  {
      provide: MSAL_INTERCEPTOR_CONFIG,
      useValue: {
        interactionType: InteractionType.Redirect,
        protectedResourceMap: new Map([
          ["https://localhost:44309/api/*", ["openid", "profile", "offline_access"]],
        ])
      }
    }

console-MSAL.log

@alamfsmb Thanks, can you email me the contents of localStorage? Please remove the "secret" field from the access and refresh token entries before sending.

I'm thinking this may be due to the uppercase 'A' in your clientId. It looks like our credential filters are not normalizing case, which is a bug on us. Can you try with an all lowercase clientId and see if that works? If you can confirm, I'll mark this as a bug and add it to our backlog.

@tnorling Oh that is a good thought - I didn't consider that, but unfortunately it did not resolve it trying just now, and I had an all lowercase clientId before sending this example too. I think it is failing on the matchEnvironment filter because the trace doesn't output BrowserCacheManager.getAuthorityMetadata: at any point, but I couldn't debug why it would fail to get authorityMetadataKeys

One other thing I'm noticing is that your knownAuthorities array has https:// in it. It's not supposed to be there, but MSAL should be stripping that off anyway...Try removing it. Otherwise I don't see anything obviously wrong here, it may just be a matter of stepping through a debugger. Unfortunately without being able to repro with your custom authority on my end, I'll have to leave that to you to report back your findings :/


[BUG] upload_video.py not working?

Example file
examples/videos/upload_video.py

Describe the bug
The log does say that the video was upload. It always renames the file and adds "REMOVE ME" at the end - all the behaviour is same as photos/upload_photos.py
But, on the instagram account, it never uplaods the video.
Log
2020-04-10 13:39:41,929 - INFO - LOGIN FLOW! Just logged-in: False
2020-04-10 13:39:43,446 - INFO - Logged-in successfully as '****'!
2020-04-10 13:39:43,449 - INFO - Checking 60s.mp4
2020-04-10 13:39:43,449 - INFO - Uploading video `60s.mp4` with caption: `2`
2020-04-10 13:39:45,879 - INFO - Started uploading '/Users/kushpvo/Desktop/******/media/60s.mp4'
Analizing `/Users/kushpvo/Desktop/******/media/60s.mp4`
FOUND w:720, h:1280, rotation=0, ratio=0.5625
Vertical video
Cropping video
2020-04-10 13:40:10,063 - INFO - Video '/Users/kushpvo/Desktop/*****/media/60s.mp4' uploaded
2020-04-10 13:40:10,064 - INFO - Succesfully uploaded: 60s.mp4
2020-04-10 13:40:10,065 - INFO - Total requests: 35

To Reproduce
(EXAMPLE:) Steps to reproduce the behavior:

Run file: examples/videos/upload_video.py

Expected behavior
The video should get uploaded to the instagram account
Version
Python version (python -v): 3.7.4
Operating System :Linux and MacOS (tried on both)

@kushpvo - what version of Instabot are you running?


Fix #139. Remove old files on 'gulp update'.

Added a single line to the gulp.js file.  The directory './src/images/emoji'
is deleted when gulp update is called, and then populated from the master
branch of emoji-cheat-sheet.com as usual.
I ran gulp clean, gulp update, and gulp compile, removing 4 defunct
emoji images and a css file inside the 'src/images/emoji' folder. This also
removed these items from the 'dist/images/basic' folder, and caused each
of the sprit '.png' and '.css' files to be augmented, since 4 fewer images
were included.
I had some issues with file permissions running these commands.  The were
saved to disk with permissions rw-r--r-- (644). I had to manually change them
back to their original permissions of rwxrwxr-x (755).  Some files were
also 644 by default, including dist/css/basic/emojify[.min].css and
dist/js/emojify[.min].js.
I did not include the dist/css/data-uri/ folder, though the '.css' files
were also changed by removing sprites. For some reason, the background
attribute was replaced by background-image. I'll commit
them next, and can push them up as needed.

Hey @hassankhan, are there any issues I can repair on the pull request?  Its a small fix, but it would be nice to see it merged.

Hi sorry, hadn't had a chance to review. Thanks! :+1:

Thanks @hassankhan!


Setup Node.js CI with Actions

@acostalima please update the badges to use github and not travis

You may also remove .travis.yml from the repo as well.

Already removed .travis.yml file. Will work on the badges, thanks!

@satazor badged updated!

Added just a minor comment.

@satazor as we discussed earlier today, I've removed the cache layer for now. Please have another look. Thanks!


Update Migrate to .NET 6 /2

Migration Internal review URL

Code samples migrated from ASP.NET Core 5.0 to 6.0

@rafikiassumani-msft  @LadyNaggaga  ready for your review. @halter73  is on vac today, I'll mention him Monday.


Limiting schema visibility for introspection

We have a use-case where we need to limit schema field visibility in some cases when it comes to introspection. Some GraphQL packages have added this capability even though it's not part of the spec. A prime example is the GraphQL-Ruby package.
I am not entirely sure if this is possible to do currently, with directives and such? I haven't had enough time with GraphQL to actually use directives and we use the graphql syntax to create our schema. It would be nice if we could just add a directive to a field which in turn tells the server not to return this field during introspection:
type SingleResponse {
    id: ID
    name: String
    code: String @hidden
}

In our use case we have no need to limit the capability to actually query this field, if you know it exists, because it will by default be returned as NULL for 99% of the cases, but it would be nice to hide the field from introspection.
Can this be done?

Directives provide a way to describe alternate runtime execution and type validation behavior in a GraphQL document.
In some cases, you need to provide options to alter GraphQL’s execution behavior in ways field arguments will not suffice, such as conditionally including or skipping a field. Directives provide this by describing additional information to the executor.

So basically, directives could be interpreted as middle- or afterware? This is basically what I did. I made a parser to find both field and field definition directives. After that all I had to do was add a middleware stack to be handled before the resolver is called, and afterware stack for the response.
I pass the field names and directives (@hidden) to the stack which runs through the attached afterwards and if the directive matches it takes the response field value and removes it from the response.


Stream Analytics job inputs incompatible with Workspace-based Application Insights export format

On the page you state:
Diagnostics settings uses a different export format/schema than continuous export, migrating will break any existing integrations with Stream Analytics.
Yes it is broken but it is also not possible to make it work again.
When using Diagnostics settings in the new workspace-based Application Insights and select Archive to a storage account then the format/schema is like this:
resourceId=/SUBSCRIPTIONS/0000000-0000-0000-0000-000000000000/RESOURCEGROUPS/APPCENTERRESOURCEGROUP/PROVIDERS/MICROSOFT.INSIGHTS/COMPONENTS/APPCENTER-APPLICATIONINSIGHTS/y=2021/m=10/d=26/h=08/m=00
When I want to use the storage account in as input in a Stream Analytics job then it is not possible define the correct Path pattern. The formatting available is not sufficient.

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

ID: 3daae96b-dede-4572-e485-5bf308ed4706
Version Independent ID: cdc62f50-cfec-c43a-bdbf-76827db01aa9
Content: Migrate an Azure Monitor Application Insights classic resource to a workspace-based resource - Azure Monitor
Content Source: articles/azure-monitor/app/convert-classic-resource.md
Service: azure-monitor
Sub-service: application-insights
GitHub Login: @lgayhardt
Microsoft Alias: lagayhar

#reassign:bwren Given Lauryn has moved responsibilities.

Hi there,
Regardless of the specific issue, please note that even though we support blob/adls as a streaming input, the main use case is for history loading (point in time re-processing). If the blob/adls input can be used outside of that use case, it was not designed for that and may not behave optimally.

#reassign: @AaronMaxwell

Thanks for your dedication to our documentation. This issue has been triaged and commented on. We are closing this issue for now because it requires scoping of a technical problem. Please review the following resources available to you for technical assistance.
Microsoft Azure Monitor Q&A question page
https://docs.microsoft.com/en-us/answers/topics/24223/azure-monitor.html
StackOverflow: Application Insights tags
https://stackoverflow.com/questions/tagged/ms-application-insights

#please-close


[STATISTICS-31] Add survivalProbability function for cont. dist.

This commit adds a new function for all continuous
distributions survivalProbability.
While a naive implementation would simply be
1-cumulativeProbability, that would result
in loss of precision.
For many of the current cont. dist. a higher
precision survival probability is calculated
For others, it is simply 1-cumulativeProbability
Many tests were added to verify the following:

the precision of cumulativeProbability
the precision of survivalProbability
That survivalProbabiliy is near 1-cumulative
That survival and cumulative probabilities are
complementary

Through this development, certain distributions
were found lacking precision for their
cumulativeProbabilities and were improved.
Those were:

CauchyDistribution
ExponentialDistribution
LogNormalDistribution
PretoDistribution
WeibullDistribution

Addresses Jira: STATISTICS-31

This is currently failing the CI build on checkstyle issues. You can perform the same checks that are run by the CI build using the default maven target:
mvn

This will run the following checks:
mvn clean verify apache-rat:check clirr:check checkstyle:check pmd:check spotbugs:check javadoc:javadoc

You can run each target independently until it passes and then force push your changes to this branch. Thanks.

Ah, I bet the coverage is for survival function extreme cases, will cover those predicates.

There is a method in ContinuousDistributionAbstractTest.testOutsideSupport() where you should add the complement of the cumulative probability test for the expected values 0 and 1 at the edge of the support. That will then hit coverage.


Can't forget the chat when in multi-line mode

Also Ctrl+L does not switch back from multi-line mode to single-line mode.

Hah!
So what's happening is that when you switch to multiline mode the "textarea" widget used is listening for ctrl+x, ctrl+l and others. Here's the reference for all the bindings:
https://textual.textualize.io/widgets/text_area/#bindings
I am not sure how to deal with this. One could disable the bindings but that's not great either. Finding new bindings is also not acceptable. Any ideas?


Rename transcript functions

In retrospect, the transcript functions could have been better-named.  For 1.1, I'm planning to rename them and leave the old ones in place as #[deprecated] functions.
Renaming:

commit_bytes -> append_message (avoids concept collision between the transcript layer and some protocol's commitments)
commit_witness_bytes -> rekey_with_witness_bytes (makes rekeying explicit)

I've noticed this issue only today. Sounds good 👍

Closed by #39


Fix #1: Adding an option to print the level in String instead of Integer

This commit fixes Issue #1 by adding an option to display the level
using its String representation. Suggesting it to be the 0.2.0 version. This was first discussed at https://github.com/trentm/node-bunyan/issues/194, but since I use this module, I decided to start here... So contributing back!

modified:   lib/format-record.js

Adding a method to map the level suggested by @olsonpm at
https://github.com/trentm/node-bunyan/issues/194#issuecomment-64858117
If the option is used, just change the level.

modified:   README.md

Updating the documentation by adding the examples of outputing the
reports using the levels in String.

new file:   example/bunyan-string-level.js

Adding the new example that logs the level using the string
representation.

modified:   package.json

Bumping the version to 0.2.0

Thanks, published as 0.2


Improve Lighthouse SEO Issues of the default template

What version of Remix are you using?
1.16.0
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce

run npx create-remix and follow along as below:

? Where would you like to create your app? wherever you want...
? What type of app do you want to create? Just the basics <---- important
? Where do you want to deploy? doesn't matter...
? TypeScript or JavaScript? doesn't matter either...
? Do you want me to run npm install? Yes

cd into your created remix app
run npm run build
run npm start
open http://localhost:3000 in an incognito chromium tab
open Lighthouse and run a SEO test
Notice the yellow score!

Expected Behavior
The SEO score to be at least in the green zone.
Actual Behavior
The SEO score is in the yellow zone.

Why it matters
Though I agree this is just a starter template and nobody is gonna be actually using that, I believe first impressions are still important for better adoptability. Furthermore, fixing the reported SEO issues is quite easy.

Hey @amir-ziaei, you're 100% right.
Would you like to make a pull request to fix this?
Templates are here: https://github.com/remix-run/remix/tree/main/templates
I guess they're all affected since it's the same starter.
The PR should target the main branch.
Happy to assist if needed (and interested ofc)

Hey @amir-ziaei, you're 100% right. Would you like to make a pull request to fix this?
Templates are here: https://github.com/remix-run/remix/tree/main/templates I guess they're all affected since it's the same starter.
The PR should target the main branch. Happy to assist if needed (and interested ofc)

Thanks, I guess I can raise a PR too. But here's the thing...
Besides, in the templates, I find the following code in some fixtures too which probably should be updated all-together:
<div style={{ fontFamily: "system-ui, sans-serif", lineHeight: "1.4" }}>

What do you think?

Fixtures are used for automated internal tests as far as I know, the update is not really needed.


Pantheon wingpanel volume control widget not displaying volume information correctly & pausing media

Describe the bug
When changing the system volume via the keyboard, or by scrolling on the volume icon, the notification that pops up fails to display the volume level, and will not disappear. It will only display and disappear correctly after you change the volume two or more times.
When changing the system volume, there is also a chance that it will pause the currently playing media.
On a typical Elementary OS 7 install, neither of these happen, and the volume notification displays everything correctly the first time.
Steps To Reproduce
Steps to reproduce the behavior:

Log into Pantheon session
Change the system volume

The media pausing seems to be semi random? It's very inconsistent, and happens the most when changing the volume multiple times with the mouse, as shown in the second video below.
Screenshots
Chaning the system volume via keyboard:
https://github.com/NixOS/nixpkgs/assets/42557645/33fe2de3-cbb3-43d0-bc2d-03336a334249
Media pausing randomly (my hands are entirely off the keyboard):
https://github.com/NixOS/nixpkgs/assets/42557645/8f79d225-7ba7-4e6b-8517-f979043f624b
I have tried this both on my current computer, a desktop with an RX 6700, and a ThinkPad T420, both on Unstable. Both of them behaved the same way. However, an actual Elementary OS install did not behave this way.
Notify maintainers
@NixOS/pantheon
Metadata
[catherine@nixos:~]$ nix-shell -p nix-info --run "nix-info -m"

system: "x86_64-linux"
host os: Linux 6.1.30, NixOS, 23.11 (Tapir), 23.11pre489246.4e37b4e55b6
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.13.3
channels(root): "nixos"
channels(catherine): ""
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Probably another issue caused by GLib update :upside_down_face:,
I am thinking of this commit (related discussion) but haven't checked the code yet.


Distance to "no data"?

Hello,
I am trying to create a polygon that represents all area within the extent of a FeatureSet that does not have a polygon. That is a polygon that represents missing data within a certain extent. The purpose is to include missing data as a feasible target location when calculating certain distances.
I have managed to do so but when I have a large FeatureSet this operation takes a lot of time.
Any suggestions besides parallelization?
    private IGeometry getNoDataPolygon(IFeatureSet featureSet)
    {

            IGeometry NoDataPolygon = featureSet.Extent.ToEnvelope().ToPolygon();

            foreach (IFeature feature in featureSet.Features)
            {
                NoDataPolygon = NoDataPolygon.Difference(Geometry.FromBasicGeometry(feature.BasicGeometry));
            }

            return NoDataPolygon;

    }

Yes, you can use Parallel.ForEach instead of your foreach loop. It will give some speed improvement on multicore machines.

Ah, I missed "besides" :)

I tried using EraseFeatures in Overlay
    private IGeometry getNoDataPolygon(IFeatureSet featureSet)
    {

            featureSet.InitializeVertices();
            FeatureSet noDataFeatureSet = new FeatureSet();
            IGeometry NoDataPolygon = featureSet.Extent.ToEnvelope().ToPolygon();
            noDataFeatureSet.AddFeature(NoDataPolygon);
            noDataFeatureSet.InitializeVertices();
            noDataFeatureSet = Overlay.EraseFeatures(noDataFeatureSet, featureSet);
            return Geometry.FromBasicGeometry(noDataFeatureSet.Features[0].BasicGeometry);
    }

but this was just as slow.  The EraseFeatures method is using the Differance metod i used in previous example so I should have guessed. But instead of looping the features directly it uses the shape indices as a memory management technique.

@stenvall Have you tried to union your existing polygons before calling difference? I think Union + a single Difference call might be faster.
It might be usefull to switch to DS 2.0 to get rid of Geometry.FromBasicGeometry(feature.BasicGeometry).
In DS 2.0 you can use feature.Geometry directly and don't have to recreate it.

@jany-tenaj Thanks for the tip! I tried to union the existing polygons + a single Difference call but it was allso werry slow. It is not suitable for us to switch to DS 2.0 right now but maybe that is the only way forward. Any other suggestions?

@stenvall just found another answer for you. But I fear you'd have to switch to DS 2.0 for this, too.

I guess question is solved, and we can close it?


Tensorial analysis

This PR introduces support for

Vector valued Functions
Tensor  valued function

Staggered FD more robust and cleaner.
All finite-difference and operator are supported.

06_bis_elasitc_varying_parameters.ipynb : I think you should drop the "bis" (how would it generalize?),

No I think it makes more sense like that as it is just a small variation of 06 but still the same example.

there are no unit tests for Operator and Vector/TensorFunctions, correct?

There is examples with it, I guess can add more tests but not sure necessary

Another big missing are tests in test_derivatives.py for when taking derivatives on tensors.

There is no matricial differential operator, all FD gies through gettartr and are only done on Functions so it's already all tested.

No I think it makes more sense like that as it is just a small variation of 06 but still the same example.

"small variation" a ~900-lines completely new file ?
regardless: the name still has a typo (not sure if you fixed it already)

There is examples with it, I guess can add more tests but not sure necessary

yes they are. Unit testing are absolutely fundamental for these things.

There is no matricial differential operator, all FD gies through gettartr and are only done on Functions so it's already all tested.

Regardless of the current implementation, I don't understand why you say a test checking that (for example) vu.dx doesn't error out (but rather produces the expected thing) would be useless. The API is critical, and even though the implementation "boils down to something simple", that doesn't mean it shouldn't be tested

"small variation" a ~900-lines completely new file ?

It;'s a tutorial notebook of course it's long or it's not a tutorial. And half of it is nicer plots. Everything is still the same as 06 with the only difference being spatially varying parameters.

, that doesn't mean it shouldn't be tested

I don't mind adding tests, just feel it always comes at the cost of removing actual usable examples for the sake of fast CI.

It;'s a tutorial notebook of course it's long or it's not a tutorial. And half of it is nicer plots. Everything is still the same as 06 with the only difference being spatially varying parameters.

I assume merging the two while leaving a few lines commented out (for the symbolic coefficients) with remarks, is not on the table as an option, as it would mess everything up?

I don't mind adding tests, just feel it always comes at the cost of removing actual usable examples for the sake of fast CI.

Here I just disagree


Misleading statement regarding using Create-React-App with Typescript

In static-type-checking -> Using TypeScript with Create React App it says

Create React App supports TypeScript out of the box.
Well, it doesn't seem so.
I followed the instructions for creating a new project.
create-react-app my-app --typescript
I converted App.jsx to App.tsx. There was only 1 error - no types for React. I installed types for React
npm i @types/react
and then run npm start.
I got the following error:

While it's perfectly fine to expect a user to install "typescript" and the various type modules, i wouldn't say that it qualifies as "support out of the box" for typescript.

If you run npx create-react-app my-app --typescript it will generate your entire project using typescript, so the App file will be App.tsx, and there should be no reason to have to change it from .jsx to .tsx. I just attempted this myself and it seems to be the case. I'd recommend you try again with the command and see if you run into the same issues.
To summarize: if you run  npx create-react-app my-app --typescript it will generate create-react-app with typescript already set up, no need to install anything further or change any files.


[Accessibility] Fixed not descriptive enough link.

Related issue : https://github.com/Microsoft/pxt/issues/2647

@veler,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@ganicke could you please review this.

I don't like that we're repeating the text.


Control the GPU memory allocation

Tensorflow-gpu 1.13.1
I am using densevnet. Some days ago everything was working properly, but today I got an error message 'OOM....'   .
My total GPU memory is:
2019-08-24 16:39:21.609144: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1433] Found device 0 with properties:
name: GeForce RTX 2080 Ti major: 7 minor: 5 memoryClockRate(GHz): 1.545
pciBusID: 0000:0a:00.0
totalMemory: 11.00GiB freeMemory: 8.95GiB
2019-08-24 16:39:21.834574: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1433] Found device 1 with properties:
name: GeForce RTX 2080 Ti major: 7 minor: 5 memoryClockRate(GHz): 1.545
pciBusID: 0000:41:00.0
totalMemory: 11.00GiB freeMemory: 8.95GiB
And it seems to be allocating the following:
2019-08-24 16:41:50.719865: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1115] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 8620 MB memory) -> physical GPU (device: 0, name: GeForce RTX 2080 Ti, pci bus id: 0000:0a:00.0, compute capability: 7.5)
2019-08-24 16:41:50.727263: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1115] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:1 with 8620 MB memory) -> physical GPU (device: 1, name: GeForce RTX 2080 Ti, pci bus id: 0000:41:00.0, compute capability: 7.5)
I want to control the GPU memory allocation. By default it is pre-allocated within tensorflow. From the below guide I read that I am ought to either enable "allow_growth" or to change the percentage of memory pre-allocated, using per_process_gpu_memory_fraction config option.
https://riptutorial.com/tensorflow/example/31879/control-the-gpu-memory-allocation
Do I add the following code to dense_vnet.py?
config = tf.ConfigProto()
config.gpu_options.allow_growth = True
sess= tf.Session(config=config)
How do I do this? When I try this, nothing seems to happen.  (I have already reduced batch_size = 1).

There isn't a way currently to set this option unfortunately through config files. The config object used is defined here so you could add the config.gpu_options.allow_growth = True line below that. We should look into a better way of doing this.

There isn't a way currently to set this option unfortunately through config files. The config object used is defined here so you could add the config.gpu_options.allow_growth = True line below that. We should look into a better way of doing this.

I tried doing this, unfortunately - it did not work. Do you think adding another GPU will sort this issue?

I think you're trying to load too much into memory. Tensorflow will allocate all the memory a card has then actually use it as it creates tensors, I think you're getting the OOM because you're trying to use more memory than your card has, that is to say more than Tensorflow has pre-allocated to itself. If you can try on a card with more memory you could see if that helps.

I think you're trying to load too much into memory. Tensorflow will allocate all the memory a card has then actually use it as it creates tensors, I think you're getting the OOM because you're trying to use more memory than your card has, that is to say more than Tensorflow has pre-allocated to itself. If you can try on a card with more memory you could see if that helps.

Ok, thank you for you reply. I will look into adding more GPU memory

Adding "config.gpu_options.allow_growth = True" to the "tf_config" function does not work for me.
I have to use the method mentioned here.

Adding "config.gpu_options.allow_growth = True" to the "tf_config" function does not work for me.
I have to use the method mentioned here.

This does not work for me either, however the following worked for me:
export TF_FORCE_GPU_ALLOW_GROWTH=true