Potentially unify the giveBlock and giveItem commands

After the work in #2290 and what came before it we might be able to just combine giveBlock and giveItem into a single give command with variants to accept only shapes for blocks, give a sensible warning if you asked for an item that can't be shaped, and so on.
There is a fair bit of overlap between the two commands, hopefully at least we can cut down on the duplication and in the best case completely unify them both.
Main trick is probably still supporting the different method variants based on parameters. Still probably not too hard to do.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/32890733-potentially-unify-the-giveblock-and-giveitem-commands?utm_campaign=plugin&utm_content=tracker%2F5279&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F5279&utm_medium=issues&utm_source=github).

@Cervator If they were to be completely unified, in which Commands.java file should the new give command be? ItemCommands, CoreCommands?

@MaxBorsch I think ItemCommands fits the purpose better. Maybe we'll find a better name for it, the giveItem command seems to be the only thing implemented there. One could argue that the hand-held blocks are items of sort, so that should be fine.
There's always the option to change things later 😉

Closing as completed by #2613! Thanks @MaxBorsch :-)


Added localization for title and category for dacpac

Added localization for the title and category in the package.json of dacpac.
This is to start the fix for: #6326

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 41.357%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
26439

Relevant Lines:
57961

💛  - Coveralls


{Freeway-Bug}[Adaptive Cards- Import- Activity Update]: Luminosity ratio of selected date on Calendar Picker under 'Activity Update' pane is 1.2:1 which is less than 3:1.

Target Platforms
Android
SDK Version
2<IP_ADDRESS>
Application Name
Adaptive Card
Problem Description
Test Environment
Device: S21+ 5G
Screen Reader: Talkback
AdaptiveCard Android App version: 2<IP_ADDRESS>
Repro Steps:

Launch the Adaptive cards app on Android.
Navigate to 'Import' control and select it.
Navigate to 'Sample cards' and select it.
Navigate to available dropdown under 'Sample cards' and select it.
Navigate all the controls under dropdown and select 'Activity Update'.
Navigate to 'Visual' tab control and select it.
Navigate all the controls under 'Visual'.
Navigate to Date Picker and select a date.
Observe the issue for selected date issue with the tool.

Actual Result:
Luminosity ratio of selected date on Calendar Picker under 'Activity Update' pane is 1.2:1 which is less than 3:1.
Expected Result:
Luminosity ratio of selected date on Calendar Picker under 'Activity Update' pane should be greater than or equal to 3:1.
Note: Same issue is also repro for Selected Time also.
User Experience:
User with low vision might face difficulty to understand/ If the color contrast ratio is less than 3:1 for the focus indicator boundary with keyboard on selected date.
WCAG Reference:
https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast
Have feedback to share on Bugs? Please help fill Trusted Tester Bug Feedback (office.com)"
Screenshots

Card JSON
NA

Sample Code Language
No response
Sample Code
No response

it's native Android UI issue we can't fix.


zoom to a node

hi,
currently, I am trying to write a functionality for zooming to a node. Currently, am doing something like
s.cameras[0].goTo({x:node.x,y:node.y,ratio:0.0625})
but this does not seem to work. It would be great help if someone could help me with this. I am using new version of the library.
-Saurin

How do i define the nodes?

Hello @JantineD. I am not sure I understand your question. Could you develop a bit more please?

Awesome! Thanks so much for the workaround.


Nit -  reveng generated DbContext and Models violate SA1516

Steps to reproduce
Run reveng on existing database
The issue
It all works. Its just the emitted DbContext class and its models violates SA1201
To be specific the virtual DbSet properties aren't separated by a blank line and the properties of each model aren't separated by a blank line.
warning SA1516 : Elements must be seperated by blank line

Further technical details
win7 x64
rc2
vs 2015 update 2
Comments
This is debateable.  It does make the generated code more verbose but looking at other code in samples etc. it seems this rule is normally used.

This isn't something we are planning to change. There are mixed opinions around whether some SA rules actually represent the best/accepted coding patterns. For this particular case, we think that having DbSet properties without blank lines between them best represents the code that the majority of folks want.


[FLINK-21297] Support 'LOAD/UNLOAD MODULE' syntax

What is the purpose of the change
This pull request supports loading/unloading modules by LOAD/UNLOAD MODULE syntax.
Brief change log
This PR contains 3 commits

e40477c9493f14e1fa34b6de49e5241fd4dde263 Support syntax in both flink and hive parser.
5fd6643565034477afe1475561e073bab0ee6c4b Support operation transformation in both old and blink planner.
c5cdcc96806e803647e8e34be2a3a112cf16d4f0 Support syntax in SqlCli.

Verifying this change
This change added tests and can be verified as follows:

e40477c9493f14e1fa34b6de49e5241fd4dde263 Added tests in FlinkSqlParserImplTest and FlinkHiveSqlParserImplTest to verify syntax support.
5fd6643565034477afe1475561e073bab0ee6c4b Added tests in SqlToOperatorConverterTest to verify operation transforming behaves correctly, and added tests in TableEnvironmentTest to verify module discovery and module loading/unloading behave corrrectly.
c5cdcc96806e803647e8e34be2a3a112cf16d4f0 Added tests in SqlCommandParserTest and LocalExecutorITCase to verify SqlCli behaves correctly.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Docs will be updated after FLINK-21300 finish.

Hi @wuchong  can you help review this PR when you are free?

@flinkbot run azure

Many thanks to @wuchong. I wish I could address all your comments.


LICENSE doesn't have the copyright line

Need to add the copyright line with year including 2018 and the name of the organisation to avoid copyright issues.
I'd like to take this up!

closing, this repo will be archived soon


getUuids fetching lasts too long

Hi Tanelih!
I'm trying to get the UUIDs of the given mac address, but when I use the function below, it lasts too long, and I'm wondering what am I doing wrong.
window.bluetooth.getUuids(onSuccess, onFail, mac_address);
All I can see in logcat is posted below:
"
VFY: unable to resolve direct method 1783: Ljava/lang/String;. ([BLjava/nio/charset/Charset;)V
VFY: unable to resolve virtual method 99: Landroid/bluetooth/BluetoothSocket;.isConnected ()Z
VFY: unable to resolve virtual method 99: Landroid/bluetooth/BluetoothSocket;.isConnected ()Z
"
And if I want to call the function again, it says, totally logically:
"
Could not start UUID fetching because there is already one in progress.
"
Snippet:
function getUuidForDevice() {
window.bluetooth = cordova.require("cordova/plugin/bluetooth");
var mac_address = AA:BB:CC:DD:EE:FF // just an example
window.bluetooth.getUuids(onSuccess, onFail, mac_address);
}
function onSuccess(device) {
alert("Name of the device: " + device.name);
alert("Address of the device: " + device.address);
for (var i = 0; i < device.uuids.length; i++) {
alert("UUid" + i + " of the device: " + device.uuids[i]);
}
}
Can you help me to figure out, what is wrong?
Thanks in advance,
bandeye

Hi,
After googling around, it seems that this problem could be caused by having insufficient permissions in the manifest file, or having an old version of android.
Some resources also pointed to android studio being the culprit here. I'd try to clean and rebuild the project and making sure you're running a high enough version of the android sdk.
The code you posted seems to be in order. Are you sure you've "discovered" the device so that your device knows about it?

Hi Tanelih,
Thank you for getting back to me. Yes, you are right, the problem was the API version. The device supported API 8, which, as turned out, is the problem. I tried with another device, having API version 16, and it works. Thank you.


Q: Why does RePajama exist? what problem are you solving?

https://huggingface.co/datasets/togethercomputer/RedPajama-Data-1T/discussions/25

https://discord.com/channels/1082503318624022589/1097534874719625236/1143265561753686176


functions for plotting

Added a plotting.py file that has plotting functions for timeseries, FC, and PSD. The input to all are Recording objects. (tested the code and it is working locally but having issues with import to test it in examples).

can you drop snippets below of the function calls as you would want them to appear in the example files ?


Is there an effort to update the code?

The code here runs with Ubuntu 18.04, CARLA 0.9.10 and Python 3.6. Are there any current efforts to update the code?

The code runs with python 3.7 and Ubuntu you can also use newer once like 22.04.
We can't upgrade the python version because 3.7 is the newest one that CARLA <IP_ADDRESS> (the egg/pip library) supports.
The newer CARLA versions like 0.9.15 support up to python 3.8 but are not compatible with the CARLA leaderboard 1.0 code.
Since this repository is supposed to reproduce the experiments in the hidden biases paper we can't upgrade the python or CARLA version.
If you are interested in the CARLA leaderboard 2.0 this code is not so hard to adapt (see here, although you will need to introduce improvements to get a good score.
We are working on that but it will likely take a while until we have something that is actually good.


[VQC-CHALLENGE] [ObjectivityLtd] [02.11.2022]

Team members
Michal Baczyk
Peter den Haan
Submission summary
Private mode<EMAIL_ADDRESS>HAQS-2022/qml-classifier-challenge/vqc_challenge-Copy1.ipynb
Additional comments

I have just committed the changes without pushing them as suggested. I am working on the fork from ObjectivityLtd:ObjectivityTeam in the qBraid lab registed for the<EMAIL_ADDRESS>e-mail.
I used my other fork as well but it seemed to make more confusion than any real help. Sorry about that and thank you for your kind suggestion how to improve. :)

@ryanhill1 Please review two solutions to VQC challenge from 01.11 and 02.11 in the current git status. :)

@mbaczyk123 Thanks, I can see it now. Will review in the next couple hours.

@ryanhill1 Lovely, thank you very much!
Please see both of the files since the previous PR was not adequate because of the issues with synchronization:
HAQS-2022/qml-classifier-challenge/vqc_challenge.ipynb
HAQS-2022/qml-classifier-challenge/vqc_challenge-Copy1.ipynb


Await gRPC server termination.

Fixes #320.

Renamed Scala gRPC server to "omega-edit-grpc-server".
Command line arg support, "--port" defaults to 9000.
build.sh pushes Scala gRP server into bg for testing.

@scholarsmate i've updated the build.sh script to fork the scala backend, but i'm unsure if anything needs to be changed in the github actions. what do you think?

@arosien, build.sh isn't called in the CI at all.  I have the C++ RPC server being tested by server_test.cpp via CMake in the CI, but not via the TS RPC client.  If the client itself can startup and shutdown the server, then it becomes easier to integrate in CI.


[FLINK-11606] Translate the "Distributed Runtime Environment" page in to Chinese

What is the purpose of the change
This pull request completes the Chinese translation of "Distributed Runtime Environment" page from official document.
Brief change log
Translate the "Distributed Runtime Environment" page into Chinese
Verifying this change
This change is to add a new translated document.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no

Thanks @Flyangz for the impressive translation. It looks pretty good to me. And also thanks to @klion26  for the reviewing.
Do you have any more suggestions? @klion26

LGTM +1


Tracking metrics over time with metrics-util?

I was looking at updating the metrics dependency in https://github.com/ramn/metrics_cloudwatch and since the API has changed to allow for more performant metrics tracking I figured I'd try to use the types that metrics_util provides. Unfortunately I am either confused about how to use them, or they aren't quite compatible with how cloudwatch metrics works.
Basically I want to group metrics collected in either minute or second intervals and send them to cloudwatch that way, but when I look at how metrics_util is used for the prometheus exporter it looks like it only tracks metrics from the start of the program and doesn't take time into account at all? I am not familiar with prometheus but I assume that is handled by the consumer of the metric instead(?).
I could probably build a bespoke solution for cloudwatch that perhaps uses some bits from metrics_util but I figured I could ask if I am misunderstanding something or if it would be something that could be added to metrics_util.

You're generally correct that nothing in metrics-util really cares about when a metric was submitted, at least in terms of how it's stored / aggregated. Exporters are generally either exposing the absolute value of each metric in the registry (Prometheus), or they're calculating the delta of each metric, perhaps by consuming the total change, and so on.
It certainly shouldn't be a problem to have your exporter code iterate over the registry to do that aggregation, although you obviously pay a small cost in storage if you're aggregating at a granularity that is higher than how often you report the metrics, since you can't just report as you iterate.


aggregate and correlation UT code

aggregate and correlation UT code

Please use black with the right version to format your code. @afard can you please explain to Vikash how to format his code?

@mail4umar can you please review the UT as well?

Please use black with the right version to format your code. @afard can you please explain to Vikash how to format his code?

I had missed to run black formatter to conftest.py file. I have ran it now. Hopefully next run should not give any format error.

Tests are failing please look why.
@oualib - I checked this with Arash. He will have a look.
It seems that this merged PR has introduced the bug. We should never merge a PR that has not passed all its checks.
https://github.com/vertica/VerticaPy/actions/runs/6160157285/job/16716446474?pr=691
@afard

Tests are failing please look why.
@oualib - I checked this with Arash. He will have a look.
It seems that this merged PR has introduced the bug. We should never merge a PR that has not passed all its checks.
https://github.com/vertica/VerticaPy/actions/runs/6160157285/job/16716446474?pr=691
@afard

@mail4umar what happened in this PR. Did you read my comment?

All the tests of the other PRs passed. @vikash018 can you please look at your PR to see what's going on?

All the tests of the other PRs passed. @vikash018 can you please look at your PR to see what's going on?

@oualib - I have just merged the latest master to this branch and rerun it.


Make Seed lease sync/duration period configurable

How to categorize this issue?

/area scalability
/kind enhancement
What would you like to be added:
Make Seed lease sync/duration period configurable, currently the gardenlet uses hard-coded values for lease duration and sync period (see here).
Instead, there should be proper configuration fields in SeedControllerConfiguration or a similar controller configuration struct for the seed lease controller.
Why is this needed:
Updating leases for every Seed every 2 seconds generates quite some load on the garden kube-apiserver in larger landscapes with many seeds.

/exp beginner
/needs help

/assign

Thanks @hzliangbin for picking this up!
Just a small heads-up: the seed lease controller is refactored with #4503 (411992bc616fabd76ca5660ab78111a3383a1d68).
Depending on what gets merged first, you might need to rebase a bit.

@timebertt ok

sorry, just too busy recently, anyone who interested can take it.

/assign


OpenGL 3d acceleration fails on Chromebook Pro

Please paste the output of the following command here: sudo edit-chroot -all

name: xenial
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/xenial...
crouton: version 1-20170619181610~master:980f090f
release: xenial
architecture: amd64
xmethod: xiwi
targets: xfce,xiwi,extension,touch,audio,keyboard
host: version 9334.72.0 (Official Build) stable-channel caroline
kernel: Linux localhost 3.18.0-14453-g2356e6e #1 SMP PREEMPT Wed May 17 18:05:37 PDT 2017 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...

Please describe your issue:
Following this guide to install World of Warcraft. Works (poorly) using Direct3D by default. Fails to start with the following message when SET gxApi "opengl" is added to config.wtf:

If known, describe the steps to reproduce the issue:
Add SET gxApi "opengl" is added to WoW's config.wtf.

Nevermind. Switched to X11 and it runs like butter.

@sanicki,
Thanx for reporting back with your resolution, it may help others.
-DennisL


Failed to run a caffemodel obtaining AbsVal_layer

I have successfully built dynamic library of mace using tools/build_standalone.sh by adding new  code assigning with absval operator including mace/ops/absval.cpp+mace/ops/absval.h+mace/kernels/absval.h+mace/kernels/opencl/absval.cpp+mace/kernels/opencl/cl/absval.cl.
I also modified mace/python/tools/caffe_converter.py and mace/python/tools/shape_inference.py and mace/python/tools/base_converter.py to support the new absval operator, and successfully run python tools/convert.py convert --config=/path/of/my/yaml to generate library.
However, when I tried to run python tools/convert.py run --config=/path/of/my/yaml to test,
it shown  error info like below
F registry.h:45 Key not registered: AbsVal0T_DT_FLOAT
Aborted
ERROR: [Mace Run] Mace run failed.
How could solved it?

You need to register your new op.
@yejw5 ， could you complement docs (https://github.com/XiaoMi/mace/issues/145) for 'Adding new ops' session?

@peyer

Firstly, use .cc extension instead of .cpp for your source files.
And than register the new op in mace/ops/ops_register.cc. I will update the relevant docs later.

Please refer to doc https://mace.readthedocs.io/en/latest/development/adding_a_new_op.html

@liyinhgqw I am so sorry about not clearly making sense of adding new op that leading to not add corresponding code in mace/ops/ops_register.cc. I have modified. Thanks a lot!

@liyinhgqw I copied opencl kernel of addn operator to my absval operator, and changed add mode to abs mode. However, when I tried to use absval op in GPU device, the return value of  runtime->command_queue().enqueueNDRangeKernel( ) of TuningOrRun2DKernel() became CL_INVALID_KERNEL.
what about your advice?


[MM-20455] Migrate 'components/integrations/edit_incoming_webhook' module and associated tests to TypeScript

Summary

Migrates the following files to TypeScript:

components/integrations/edit_incoming_webhook/index.ts
components/integrations/edit_incoming_webhook/edit_incoming_webhook.tsx
components/integrations/edit_incoming_webhook/edit_incoming_webhook.test.tsx

Ticket Link

Fixes https://github.com/mattermost/mattermost-server/issues/15485
Related Pull Requests

None
Screenshots

None

/update-branch

Thanks for the contribution @didithilmy. Looking forward to another more :rocket:


add version

Add version to the project.  Leverage the existing pyproject.toml version without duplication.

done in 0.5.0


Live server down

http://cors-anywhere.herokuapp.com/ is either not responding or returning errors.

Seems to have recovered.


Add "Vue JS na prática" to brazilian portuguese list

What does this PR do?
Add Resource(s)
For resources
Description
Add the free ebook Vue.js na prática in the Brazilian Portuguese list
Why is this valuable (or not)
Vue.js in Portuguese has only a few options. This ebook covers how to use the framework from the scratch.
How do we know it's really free?
You can check it out on the LeanPub website 😄
For book lists, is it a book?
Yes 🚀
Checklist:

[x] Not a duplicate
[x] Included author(s) if appropriate
[x] Lists are in alphabetical order
[x] Needed indications added (PDF, access notes, under construction)

Please, consider add the hacktoberfest topic to the repository, for my PR be valid as a contribution on Hacktoberfest 2020 ✋

the repo has the keyword hacktoberfest2020 which should be enough.
for leanpub, I think this link requires an account - take a look at other leanpub links to make sure you have the right annotation.

Unfortunately is not enough, as you can see in the images below:

I've added the Leanpub account info to the description!

changed the keyword


nixos/*: even more options doc md conversions

Description of changes
once more unto the breach. as usual the final commit is generated with tool assistance to make sure the generated options.xml from which all docs are built remains the same with that commit applied.
358 options the tool can see remain unchanged. there are plenty more internal options that can't be converted like this, and a lot of options in modules that use wrapper functions to create their options. this could be the final PR that uses a conversion tool.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

changed the quote replacement to use “” after all now on request.


[Technical Question] iot-hub-device "connected" member and its behaviour.

Hi,
I'm using:
azure-iot-device==2.9.0
In my application I have a job monitoring the iot-hub-device his connection state via the read-only "connected" member.
I monitor this state every second, when changed, we emit an event.
On a number of devices I see that they often send me a disconnected event and one second later a connected event.
So this member "connected" returns False for at maximum one second, because the next iteration it's connected again.
I would like to understand why this "connected" state changes for at maximum one second to disconnected and immediately again to connected.
Is it because of the token refresh, but this should not change the "connected" state during a refresh I think?
On some devices it could be stable to 8hours, other devices send me these events every hour.
Are there other reasons?
As you can see in the image, we get disconnected and one second later a connected event. Almost always one hour in between the 2 disconnects. Token refresh issue?

Kind regards,
Robbin

@robbinvandamme
Yes, it's due to token refresh. Refreshing the token requires us to disconnect and reconnect the client, thus the connection state will briefly change - we don't hide this aspect of the functionality by suppressing the disconnection, after all, there could be failures during reconnect, etc.
If you're trying to monitor the state, I also might recommend using the .on_connection_state_change handler so you don't have to monitor the state every second.

@cartertinney
Thx for you quick reply!
Yes I'm aware of the .on_connection_state_change functionality, but the job running every second will still be there for other reasons and read the "connected" member is very cheap.
However, I could stop reading the "connected" member and use the .on_connection_state_change event if it doesn't get emitted on a token refresh.
If .on_connection_state_change is also emitted every token refresh I'll need to work around it and ignore the state changes if they are less then 5sec apart for example.
I still find it a bit strange the state is changed and emitted on a token refresh. You could also only emit a disconnect event if the token refresh fails?

@robinvandamme
Ultimately, our current design philosophy is not to try and hide what's going between the Device and the IoTHub. SAS Token renewal will cause a disconnect, and then a connect.
These disconnect/connects show up in IoTHub logs, so we want to be transparent about the behavior in order to prevent confusion.

@cartertinney
OK, I understand.
But the drawback is that, we as user of the sdk, need to figure out our-self if it was just a quick reconnect due to a token refresh or a real disconnect. I can image that there are a lot of cases where we don't want to start the "disconnect" logic or procedure due to a token refresh, because in 99% of the time we will only be disconnected for 1sec (or even less than one second.)
And one other thing:
lets say we trigger a direct method over the iot-hub towards the device at the exact same time of the token refresh.
That direct method call will fail or is that robust enough to deal with these token refreshes. I would expect it will not fail..?

@robbinvandamme
There is enough robustness to deal with that scenario. The method call will either finish before the token refresh happens, or wait until after token refresh has finished. If the token refresh fails to reconnect due to network failure, there may also be a failure on the direct method call due to the same failure.
If you're looking for a way to catch when there is some kind of failure rather than disconnect, you could try the .on_background_exception handler. However if you're using the connection_retry option (on by default) be aware that the client is going to repeatedly try to re-establish the connection in the event of failure, and so you may see multiple failures from multiple auto-reconnection attempts

@cartertinney thx!

@cartertinney
Is it allowed to call connect() when using the connection_retry option, or will this cause issues?
If this causes issues, is there a way to know if auto-reconnect is running?


astro-expressive-code not working in mdx files

hi guys,i am using astro-expressive-code in my astro.js project, i am on astro v4.8
but its not working in .mdx

when i try using <Code /> component, i get this error
08:34:05 [ERROR] [vite] Internal server error: [postcss] The argument 'path' must be a string, Uint8Array, or URL without null bytes. Received '\x00/_astro/ec.wtfda.css'
  Plugin: vite:css
  File: /_astro/ec.wtfda.css?direct:undefined:NaN
      at Object.statSync (node:fs:1659:10)
      at C:\Users\dell\Desktop\projects\node\portfolio\node_modules\.pnpm\@tailwindcss+postcss@4.0.0-alpha.14_postcss@8.4.38\node_modules\@tailwindcss\postcss\dist\index.js:1:709
      at C:\Users\dell\Desktop\projects\node\portfolio\node_modules\.pnpm\@tailwindcss+postcss@4.0.0-alpha.14_postcss@8.4.38\node_modules\@tailwindcss\postcss\dist\index.js:1:1892
      at _optionalChain (C:\Users\dell\Desktop\projects\node\portfolio\node_modules\.pnpm\@tailwindcss+postcss@4.0.0-alpha.14_postcss@8.4.38\node_modules\@tailwindcss\postcss\dist\index.js:1:687)
      at S.plugins (C:\Users\dell\Desktop\projects\node\portfolio\node_modules\.pnpm\@tailwindcss+postcss@4.0.0-alpha.14_postcss@8.4.38\node_modules\@tailwindcss\postcss\dist\index.js:1:1821)
      at LazyResult.runOnRoot (C:\Users\dell\Desktop\projects\node\portfolio\node_modules\.pnpm\postcss@8.4.38\node_modules\postcss\lib\lazy-result.js:329:16)
      at LazyResult.runAsync (C:\Users\dell\Desktop\projects\node\portfolio\node_modules\.pnpm\postcss@8.4.38\node_modules\postcss\lib\lazy-result.js:258:26)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async compileCSS (file:///C:/Users/dell/Desktop/projects/node/portfolio/node_modules/.pnpm/vite@5.2.11_@types+node@20.12.11_lightningcss@1.24.1/node_modules/vite/dist/node/chunks/dep-cNe07EU9.js:32272:25)
      at async TransformContext.transform (file:///C:/Users/dell/Desktop/projects/node/portfolio/node_modules/.pnpm/vite@5.2.11_@types+node@20.12.11_lightningcss@1.24.1/node_modules/vite/dist/node/chunks/dep-cNe07EU9.js:31583:56)
```

my config
```ts
import mdx from "@astrojs/mdx";
import sitemap from "@astrojs/sitemap";
import expressiveCode from "astro-expressive-code";
import { defineConfig } from "astro/config";
import rehypeAutolinkHeadings from "rehype-autolink-headings";
import rehypeSlug from "rehype-slug";

// https://astro.build/config
export default defineConfig({
    prefetch: {
        defaultStrategy: "tap"
    },
    integrations: [
        sitemap(),
        expressiveCode({
            themes: ["one-dark-pro"],
            frames: {
                showCopyToClipboardButton: true
            }
        }),
        mdx({
            optimize: true,
            rehypePlugins: [rehypeSlug, rehypeAutolinkHeadings],
            syntaxHighlight: "shiki",
            shikiConfig: {
                theme: "one-dark-pro"
            }
        })
    ],
    site: "https://navithecoderboi.me"
});
```

Hello! This is not an Expressive Code issue, but an unfortunate behavior of the MDX integration.
You have added rehypePlugins: [rehypeSlug, rehypeAutolinkHeadings], to the options of your mdx(...) integration call, which causes the MDX integration to replace all rehype and remark plugins configured in the global Astro markdown config with only the ones you have specified in the MDX options.
This will also disable EC's rehype integration, which astro-expressive-code adds to your global Astro markdown config.
To fix your project, move any rehypePlugins and remarkPlugins out of the MDX integration call, and into Astro's markdown: { ... } config options. The MDX integration will also find them there.


check for container termination, not state transition

fixes https://github.com/openshift/source-to-image/issues/934

[merge]

Hi, when are you planning to release this? I have the same issue as @cliveseldon and ti blocks me. :(

just published it in 1.1.13 for you, but of course you can always build your own binary from master.

Amazing, thank you for the quick response! I did build my own binary from master but then everyone in our team would have to be forced to install Go (we don't use it) and do the same or I would need to distribute binaries for several OS... Besides, it's not only for us but for the everyone in Seldon community who use MiniKube. ;-) It takes time and skills to understand the bug, find, and apply the solution.


Introducing new features and some bugfixes

it looked like the dell api only gave answer for up to 80 records at a time, so reduced the offset to 50 to be sure.
The offset increased the list of warranty checks to perform each offset increase. Moved the init of the array into the loop to clear previous list
Systems being decommissioned have had a epoch behind the serial number (don't see the reason for that being in the life_cycle event btw). The script now takes care of that and makes sure the warranty check is done against the actual serialnumber.

Hi @blafkachel, thanks for improvements, all seems good, just couple questions : why you remove 1 sec. delay at first commit ( #f611309 )? I think we need it for not to abuse Dell system with too frequent requests. And in the same commit, is it correct to assume that Dell serial numbers always uppercase?

the 1 second delay was originally there when we did an api call per serial, now we do them in batches of 50. If we would need to keep it in, then I suggest to put a sleep right after 'result = vendor_api.run_warranty_check(inline_serials)' As there is no need to lengthen the durance of creating the array of serials.
As for the uppercase I noticed the link was not made within device42 for linking the purchase to the device, though that also might have been caused by not having 'service_level_group == 99999' in #6f1143f

@blafkachel can you check how it working for you without .upper(), if all correct I will merge

Without the upper in there it fails as some systems have been registered using a lowercase serialnumber, it fails on the dictionary being build to translated between the serial used for dell warranty check and the actual serialnumber in Device42 to link the information there.
The serial is picked up from Dell API site and it always returns it as capitals. in the warranty_dell.process_results section the serial is now picked up from the API result and that servicetag is then used in data.update({'line_device_serial_nos': fullserials[serial]}) to translate it to the serialnumber registered in device42.
Not setting it to upper fails on doing the match, therefore the serial was set as upper which solved that.
It could also be placed in the 'for d42_serial in incoming_serials:' section 3 times to restrict it to purely the dell warranty checks.

@blafkachel ok, got it, thanks for feedback.

@blafkachel I've merged your changes and a bit change code, because we cannot globally uppercase serials ( it may affect other vendors processing ), also change some variables names and positions.
Please pull and run over your implementation. Thanks again for your help.


add GroupId to SecurityGroupRules

There is a small parity issue within the operation describe-security-group-rules (aws-examples-link) as it is missing the field GroupId. This appeared due to a ticket within localstack, which very nicely describes the issue.
This PR is a quick draft to resolve this - I'm not particularly familiar with ec2 or moto (:smile:) and haven't added a test to this yet. something like assert "GroupId" in rules[0] here? thx for any hints

Thank you for contributing to Moto!
To show our thanks, we'd like to share some of the donations that we've received with you. PR's like this are the big reason that Moto is as successful as it is - so it's only fair that you, as a contributor, gets to share the spoils.
We've created a companion website with more information:
https://payments.getmoto.org/
Feel free to open a bug or discussion if you run into any problems:
https://github.com/getmoto/payments


Sortable feature: only relocate until gap

For the sortable extension I have a feature request:
Assuming you have entities sorted by position with varying gaps between some numbers, e.g. 1, 2, 3, 10, 11, 20, etc.
If I add a new entity at position 4, I would like the rest of the positioning to not change.
If I add a new entity at position 3, however, the old 3 should move to 4, but the rest should stay the same.
Would also appreciate hints where to look at for trying to implement this myself.

hi, the author of sortable is not available recently, so the project is at feature freeze. if you need it working differently, fork or copy and update source to your needs, try and see when editing, you can use tests for that.

in general I doubt that this feature can be implemented without introducing much of complexity in sortable. anyway, if you want that kind of behavior you will need to hook another listener or extend the current to modify the behavior.


[ASCII-2568] Remove Meter function from telemetry component

What does this PR do?
This PR removes the Meter function from the telemetry component.
Back in 2022 when the RFC for components was created we said that we would use the Otel MeterProvider for instrument internal components. https://github.com/DataDog/architecture/blob/master/rfcs/agent-component-architecture/rfc.md#telemetry
As of today, we haven't found any internal usage.
Removing means we no longer add import many go.opentelemetry.io libraries into the different Agent binaries.
If in the future we find internal usage, we can add it 😄
Motivation
removed unused function and libraries from the codebase.
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes

/merge


Update readme.md

Some humans change the default output for azcli to tables. It might be useful to add specific output as '-o json' to az cli commands which need to be JQed. Thanks!

Thanks!  Useful tip to be explicit.


Fix librdkafka loading

Fix the case where # was present in path (for Uri) (see @cklaw issue in #133 )
Also in the case of @cklaw with the previous PR #146 , it was not possible to load librdkafka manually with the exception thrown.
I still think it's a good thing to throw if we can't load librkdkafka, but also check first if the user has loaded the lib himself (which should not be common, but I had this case and it seems other may have also)
This will also allow people to easily change the version of librdkafka used without having to hack with the content of nupkg (for example to test fix on librdkafka)
It doesn't seem to be feasible in netcoreapp, will have to do more tests on this (calling LoadLibrary on an other librdkafka seems to still use the librdkafka provided in librdkafka.redist)
As I'm not 100% sure GetModuleHandle, LoadLibraryEx or EscapeCadeBase won't throw on some specific platform using net45 (mono, PCL?) I added a try catch with silent catch (this was the case before)

thanks for this - probably some work to do around this still, but LGTM for now.


Changing get_bio() to return a dict with floats

Entering, for example, a height of 5.6 throws an error when the script compares height < 0 in line 82, so get_bio() should return floats instead of strings. Using a dictionary instead of loose variables allows for better reusability, and the dict.values() method creates an iterable set.
get_gender() and get_activities() could also be changed in a similar way.

Great catch and thanks for the suggestion of using dicts.


how to use three keys with a modifier in keymaps

i have following config that bind alt-r to c-semicolon all i want is to bind C-simicolon-j to triger Down key but all the things that i have tried have not worked
keymap:
- name: Aremap
  remap:
    super-d:
      remap:
        f:
          launch: ["firefox"]
        b:
          launch: ["brave"]
    KatakanaHiragana: [C-semicolon]
    KatakanaHiragana-j: Down

modmap:
- name: Global modemaps
  remap:
    capslock:
      alone: esc
      alone_timeout_millis: 200
      held: leftctrl
    esc: reserved

- name: right alt in pycharm
  application:
  remap:
    ALT_R : KatakanaHiragana

@Aneeqasif below is my example of binding a two key press to a three key press combo in an application specific way
  - name: Terminals
    application:
      only: [gnome-terminal-server, tilix, org.gnome.Ptyxis]
    remap:
      RIGHTCTRL-t: ctrl-shift-t

two key press to a three key press combo

i am actually trying to do a 3-key press to 1-key press combo


Add unload_table macro

WHAT
This PR adds an unload_table macro for dumping a Redshift table to S3.
WHY
Many data science applications built on top of Redshift require passing the outputs of a query along to another application. Using unload_table in a post-hook is a nice way of making the results of a dbt run accessible to other applications which can access S3.
HOW
unload_table closely follows the implementation of UNLOAD in Redshift.
unload_table includes sane defaults such as:

Requiring that the table to unload (table) and the location to unload it to (s3_path) are always set.
Requiring that IAM_ROLE or ACCESS_KEY_ID and SECRET_ACCESS_KEY are always set.
[Always escaping the DELIMITER].(http://docs.aws.amazon.com/redshift/latest/dg/r_UNLOAD.html#unload-usage-notes)
NULL AS set to  ''.
DELIMITER set to ,.

MAX_FILE_SIZE set to 6 GB.

ISSUES
Ideally, unload_table would be handled by a more generalized macro unload which would accept a query string rather than a table name. However, my attempts to implement this inside a model were unsuccessful. My idea was that I could do something like this:
-- select all from the output table
{% set query='SELECT * FROM ' + this %}
{{
  config({
    'materialized': 'table',
    'post-hook': [
      '{{ unload(query=query,
                 s3_path=var("s3_path"),
                 aws_key=var("aws_key"),
                 aws_secret=var("aws_secret") }}'
    ]
  })
}}
SELECT * FROM table

But, presumably because this is a special variable, it raised the following error:
Encountered an error:
must be str, not Relation

A second, more crude approach, attempted the following:
-- select all from the output table
{% set query='SELECT * FROM ' + this.schema + '.' + this.table %}
{{
  config({
    'materialized': 'table',
    'post-hook': [
      '{{ unload(query=query,
                 s3_path=var("s3_path"),
                 aws_key=var("aws_key"),
                 aws_secret=var("aws_secret") }}'
    ]
  })
}}
SELECT * FROM table

But this returned the following error:
Database Error in model unload_test.sql (models/unload_test.sql)
  select query cannot be empty/blank.

I assume there are a few different approaches to this macro that might address this issue, but for now i think this is extremely useful as-is!

hey @abelsonlive - This is a great macro and a great PR :)
Couple of things:

this and ref() return special Relation objects. You can render them as strings like this:

{% set query = 'select * from ' + (this | string) %}

Or alternatively, use the concatenation operator to coerce it to a string:
{% set query = 'select * from ' ~ this %}

I think that you'll have a problem getting this to work right though. When the hook is parsed, it doesn't have access to the local scope of the model, so query variable that you're creating will be None I believe.
All that is to say: I think your final implementation is a good one!
I plan on adding docs to this repo in a similar fashion to dbt-utils. Once that's ready, I think we'll be good to write some docs for this macro then get it merged in!

@abelsonlive I just updated the docs here -- can you add an entry for the unload_table macro in README.md? Otherwise LGTM

Alright! I'm going to merge this PR and then open another one for the docs.

@abelsonlive you can just make that commit in this PR if it's easier for you!

whups accidentally pressed Close and Comment


Forward Hostnames longer than 50 characters are truncated

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
YES
Are you sure you're not using someone else's docker image?
YES
If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?
N/A

Describe the bug

A clear and concise description of what the bug is.
In the admin dashboard for proxy host, if you edit/add a host with a domain longer than 50 characters in the 'Forward Hostname / IP' field, it is truncated. If you edit the full hostname manually in the database and then attempt to re-save using the UI dashboard, a popup message appears with the message: "data.forward_host should NOT be longer than 50 characters".
What version of Nginx Proxy Manager is reported on the login page?
v2.0.14

To Reproduce
Steps to reproduce the behavior:

Add a Proxy Host in the Dashbaord
Enter a long Hostname
Save Proxy Host
View the truncated hostname Destination in the Proxy Host list

Expected behavior
Longer proxy host domains should be allowed in the UI.

The issue is this setting in src/backend/schema//endpoints/proxy-hosts.json
   "forward_host": {       "type": "string",       "minLength": 1,       "maxLength": 50     },

what's the right way to change it on a running server ?

It's baked in to the image, so you either have to wait for a fix or find the file in the docker image and create your own docker image that extends from mine, overwrite the file and run that. Might be easier to wait. I'll take a look today

Actually this was fixed in 2.2.4. #mondays

I am on 2.3.0, and in the file: /var/lib/docker/overlay2/26fae2ff7dcca2d17edf07ff67ae3590c909a408ed34915151543993d53058f5/merged/app/schema/endpoints/proxy-hosts.json line seems corrected: "forward_host": { "type": "string", "minLength": 1, "maxLength": 255 },
But I cannot insert url longer than 50 characters in Forward Hostname / IP*

Is this for a proxy host or a redirection host or other? I was able to create more than 50 chars

Now it works! (from another laptop/browser) Probabily it was a browser related problem.
thanks


Cloud Foundry: Sagan app failed (crashed) when starting

Hi.
After the "cf push sagan -n tatefer-sagan -p build/libs/sagan-site.jar" command, the sagan application is unable to start succesfully.
I have stored the logs (attached) and first line with an error is:

2015-11-25T06:13:59.06-0800 [APP/0]      OUT 2015-11-25 14:13:59.067 ERROR 26 --- [ost-startStop-1] o.s.b.c.embedded.tomcat.TomcatStarter    : Error starting Tomcat context: org.springframework.beans.factory.UnsatisfiedDependencyException
2015-11-25T06:13:59.13-0800 [APP/0]      OUT 2015-11-25 14:13:59.136  WARN 26 --- [           main] ationConfigEmbeddedWebApplicationContext : Exception encountered during context initialization - cancelling refresh attempt
2015-11-25T06:13:59.13-0800 [APP/0]      OUT org.springframework.context.ApplicationContextException: Unable to start embedded container; nested exception is org.springframework.boot.context.embedded.EmbeddedServletContainerException: Unable to start embedded Tomcat

Everything before the execution of "cf push" command was ok (gradlew, etc...) and I can see the app in my Pivotal Web Services Dashboard.
logs.txt
Please, find attached log file for the "cf push" output command.
Can anyone help me?
Best Regards and thanks in advance.

Hi @tatefer
This is indeed a bug in Sagan; when deploying an application in PWS, the "cloud" Spring profile is automatically registered. This prevents the "default" profile from being activated, which means the SaganProfiles.STANDALONE profile is not triggered when the application starts.
In your case, the logs say that a Spring bean is missing (here, JestClient) although it's required by the application.
I've fixed this in #607 - could you update your git repository and try again?
Don't hesitate to ask questions by creating new issues - even if those are general questions about choice of architecture, etc.
I'll close this issue once you've confirmed it's OK.
Thanks,

Brian,  many thanks for your support.
I will follow your recommendations and will let you know.
Regards.

Hi Brian.
Many thanks, it worked!!
I downloaded the updated repository and everything was ok.
After deploying the sagan app with "cf push", the app started and is running succesfully.
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
1 of 1 instances running
App started
OK
App sagan was started using this command CALCULATED_MEMORY=$($PWD/.java-buildpack/open_jdk_jre/bin/java-buildpack-memory-calculator-2.0.1_RELEASE -memorySizes=metaspace:64m.. -memoryWeights=heap:75,metaspace:10,native:10,stack:5 -memoryInitials=heap:100%,metaspace:100% -totMemory=$MEMORY_LIMIT) && SERVER_PORT=$PORT $PWD/.java-buildpack/open_jdk_jre/bin/java -cp $PWD/.:$PWD/.java-buildpack/spring_auto_reconfiguration/spring_auto_reconfiguration-1.10.0_RELEASE.jar -Djava.io.tmpdir=$TMPDIR -XX:OnOutOfMemoryError=$PWD/.java-buildpack/open_jdk_jre/bin/killjava.sh $CALCULATED_MEMORY org.springframework.boot.loader.JarLauncher
Showing health and status for app sagan in org TateOrg / space TateSpace as<EMAIL_ADDRESS>OK
requested state: started
instances: 1/1
usage: 1G x 1 instances
urls: xxxxxx-sagan.cfapps.io
last uploaded: Fri Nov 27 11:54:40 UTC 2015
stack: cflinuxfs2
buildpack: java-buildpack=v3.3.1-https://github.com/cloudfoundry/java-buildpack.git#063836b java-main open-jdk-like-jre=1.8.0_65 open-jdk-like-memory-calculator=2.0.1_RELEASE spring-auto-reconfiguration=1.10.0_RELEASE
 state     since                    cpu      memory         disk           details

#0   running   2015-11-27 12:56:22 PM   227.0%   660.9M of 1G   248.2M of 1G

Hi Brian.
I was happy until I had to bind the app to the postgres SQL service.
I used the command "cf bind-service sagan sagan-db" and afterwards I did a "cf restage sagan".
The restage of the app failed, and same error occured than above messages.
The app failed to start. Find attached the "cf logs --recent" output
logs_sagan_restage.txt

I think you forgot to set-env a profile for your application.
When running the application in standalone mode, it's "self-contained" with an in-memory database and cache. Since you want now to bind to services and persist data to a shared datastore, use a distributed cache (and maybe run multiple instances?), you need to activate a staging or production profile. Note that this isn't enforced by CloudFoundry nor Spring Boot, but rather a convention defined in Sagan's source code.
For more details on the steps to follow, check out the wiki documentation.

Many thaks Brian, you were right.
I did the "cf restage" before set-env a profile.
But despite of set-env the profile to staging, the app doesn't start succesfully.
See logs file attached. I don't know what I'm doing wrong :-(
logs_restage_after_set_env.txt
tatefer@ubuntu:~/CloudFoundry/sagan$ cf env sagan
Getting env variables for app sagan in org TateOrg / space TateSpace as<EMAIL_ADDRESS>OK
System-Provided:
{
"VCAP_SERVICES": {
"elephantsql": [
{
"credentials": {
"max_conns": "5",
"uri": "postgres://zkdpfilp:_je62Aa2SiKupulzzL_haRJ_BQxNyTWj@pellefant-01.db.elephantsql.com:5432/zkdpfilp"
},
"label": "elephantsql",
"name": "sagan-db",
"plan": "turtle",
"tags": [
"Data Stores",
"Web-based",
"User Provisioning",
"PaaS",
"Single Sign-On",
"Windows",
"New Product",
"Mac",
"Android",
"Certified Applications",
"Data Store",
"postgresql",
"Buyable",
"relational",
"Importable",
"IT Management"
]
}
]
}
}
{
"VCAP_APPLICATION": {
"application_id": "804e9389-b321-4c56-867d-baf2cafb9fd3",
"application_name": "sagan",
"application_uris": [
"tatefer-sagan.cfapps.io"
],
"application_version": "7a1487e0-2843-4913-8d78-e49c7bc9e6bf",
"limits": {
"disk": 1024,
"fds": 16384,
"mem": 1024
},
"name": "sagan",
"space_id": "c8ee9dc5-c03b-4eeb-baa6-ffade04fe41e",
"space_name": "TateSpace",
"uris": [
"tatefer-sagan.cfapps.io"
],
"users": null,
"version": "7a1487e0-2843-4913-8d78-e49c7bc9e6bf"
}
}
User-Provided:
SPRING_PROFILES_ACTIVE: staging
No running env variables have been set
No staging env variables have been set
Regards.

Ah, I think you need to set up the ElasticSearch service as well.
Caused by: java.lang.IllegalArgumentException: ElasticSearch endpoint URI should not be null: cloud.services.sagan-search.connection.uri

This may be a requirement I can relax a bit. See that part of the wiki.

Thanks once again Brian!!
Very appreciated!!. The app is right now started and running!!
Sorry for any inconvenience and many thanks again for your help.


Date selected vs date broadcast on change is different

I have datepicker set up like this:
let initDate: Date = moment(this._data.desiredCloseDate).toDate();
let opts = {
      daysOfWeekDisabled: "0,6",
      initialDate: initDate,
      format: "yyyy-mm-dd",
      isInline: true,
      autoclose:false
    };

    picker$.fdatepicker(opts);
    picker$.on("changeDate",(e) => {
      console.log("date was changed:", e);
    });

If you look at console after selecting 10/27/16 the event is:
{ type: "changeDate", date: Wed Oct 26 2016 17:00:00 GMT-0700 (Pacific Daylight Time) ...

Notice date is day behind for some reason.

Maybe this will help someone else. Problem was date returned is in UTC
Using momentjs...
picker$.on("changeDate",(e) => {
console.log("date was changed:", e);
let m: Moment = moment.utc(e.date);
let dateString = m.format("YYYY-MM-DD");
// dateString is  correct.
});

I'm curious why this was closed, it's obviously a bug?
I'm running into the same problem where the changeDate event has the offset already applied but tells moment that is in MDT timezone


[Move] Added Move analyzer's support for multi-root workspaces #220_122

Motivation
This is another language server enhancement, this time related to supporting multi-root workspaces. This PR not only adds support for opening multiple directories within a workspace but also adds support for manifest file searching in case a single Move source file is open.
The implementation is fairly straightforward - instead of replacing existing symbolication information, augment it with additional symbols coming from additional files/directories being opened.
This PR also implements discovery of manifest files in case a Move source file is opened rather than a package directory. Previously, if the former has happened, the new features would not be available as the language server did not know where to find Move.toml file needed for compilation.
Have you read the Contributing Guidelines on pull requests?
Yes

/canary

:sunny: Canary successful

/land


missing v0.3.5

All pipelines and rails project fails for missing 0.3.5 version. It was deleted accidentally?
Your bundle is locked to mimemagic (0.3.5), but that version could not be found
       in any of the sources listed in your Gemfile. If you haven't changed sources,
       that means the author of mimemagic (0.3.5) has removed it. You'll need to update
       your bundle to a version other than mimemagic (0.3.5) that hasn't been removed
       in order to install.
       Bundler Output: Fetching gem metadata from https://rubygems.org/..........
       Your bundle is locked to mimemagic (0.3.5), but that version could not be found
       in any of the sources listed in your Gemfile. If you haven't changed sources,
       that means the author of mimemagic (0.3.5) has removed it. You'll need to update
       your bundle to a version other than mimemagic (0.3.5) that hasn't been removed
       in order to install.

@mrsangrin have you seen the internet the past few days?
https://www.theregister.com/2021/03/25/ruby_rails_code/

Welcome to the world: https://github.com/rails/rails/issues/41750?fbclid=IwAR2Z86Z9iCKPLAtrTHxeckB_qIrScZzuPxmgxYcO1fdDfGE2eH2CNyg5rnc

Many thanks! a lot of projects affected. Updated now to the latest!


jota compilation failure: Perhaps you are running on a JRE rather than a JDK?

On Window 10, following the steps in readme.md I got the following errors:
jota: Compilation failure: Perhaps you are running on a JRE rather than a JDK?
isf-jclient: Could not resolve dependencies for project com.iotaspam:isf-jclient:jar:1.0.9: Could not find artifact org.iota:jota:jar:0.9.11-SNAPSHOT ->
Installing JDK 9.04 and subsequantly running the command line:
set JAVA_HOME=C:\Program Files\Java\jdk-9.0.4
fixed the issue for me.
Hope that helps.

Thank you! We changed it from JRE to JDK in the README.md: https://github.com/mikrohash/isf-jclient#windows

please update the download link as well: http://www.oracle.com/technetwork/java/javase/downloads/jdk9-downloads-3848520.html

:)

forgot about that, corrected now. Thanks!


active_window.type doesn't work in some windows

In #10, I mentioned having issues with things like win.activate! and type. The former was actually my bad, I needed to use raise!() instead, as both activate! and focus! seem to be ignored by Xfwm when the window is minimized.
However, typing keys can sometimes fail, even when the window is focussed where it works in xdotool. For example, the editor Mousepad never receives anything when you do active_window.type "abc", even when the window is active. It's a bit more complicated unfortunately, with it being the difference between XSendEvent and XTestFakeKeyEvent; when the window is active, it should actually fall back to XTest but it doesn't, somehow: https://github.com/jordansissel/xdotool/pull/85#issuecomment-1193615057 <- This not working PR fix is was added on the last day before the previous release, so it's present in both the 2016 and 2021 version.
Normal xdotool without specifying a --window will always use XTest, but x_do.cr only ever goes the XSend route. This can be solved by specifying CURRENTWINDOW (which is 0) as window instead which xdotool understands as "use XTest to the active window".
So maybe we should add new functions inside the x_do.cr file such as
def type(text : String, delay = DEFAULT_DELAY)
    LibXDo.enter_text_window(xdo_p, 0, text, delay)
end

so  you can
XDo.act { type("abc") }

which will work fine like xdotool does. This means that the send and key functions all have to be duplicated and such

That makes sense to me; feel free to submit a PR with those new APIs.
Just to clarify: is CURRENTWINDOW a constant/macro provided by libxdo? If so we should reuse it. I'm a little bit surprised that 0 means "current window" however, since normally that means "root window" in X11 contexts. But who knows!

Just to clarify: is CURRENTWINDOW a constant/macro provided by libxdo?

Yes, it's just a plain #define. From here by the author:

... I think it's worth noting that doing key --window 0 a will send 'a' to the current window -- I don't know if this is documented, though. There's a special window value xdo uses for knowing when to act on the "current window" and that is 0.

I'll create a PR some time later.


Begin deprecation of green_or_brown

This PR begins the process of deprecating the green_or_brown dataset, in favour of increasing_or_decreasing.
Note: that these datasets are not identical stand-ins, since the names of the columns and also entries within the dataset also necessitated a change, however, the content remains conceptually identical.
We will offer one release on CRAN with these superseded datasets, before hard deprecating them.
Relates to #307

library(r2dii.data)

# deprecated dataset warns
head(green_or_brown)
#> Warning: The dataset `green_or_brown`is superseded as of r2dii.data 0.3.2.
#> Please use `increasing_or_decreasing` instead.
#>       sector    technology green_or_brown
#> 1 automotive      electric          green
#> 2 automotive        hybrid          green
#> 3 automotive           ice          brown
#> 4 automotive      fuelcell          green
#> 5      power      hydrocap          green
#> 6      power renewablescap          green

# new dataset, with new content
head(increasing_or_decreasing)
#>       sector    technology increasing_or_decreasing
#> 1 automotive      electric               increasing
#> 2 automotive        hybrid               increasing
#> 3 automotive           ice               decreasing
#> 4 automotive      fuelcell               increasing
#> 5      power      hydrocap               increasing
#> 6      power renewablescap               increasing

Created on 2023-06-02 with reprex v2.0.2


Fix autoupdate.hash in kdenlive

There was already update since last edit 😂. You can push it in this PR.


Added to the description that EmitterColorOp is an extension

This PR

Updates the Documentation

Describe the changes below:

Added to the description that EmitterColorOp is an extension of the EmitterOp class.

👍


Get Contract Request Details request does not return contract_id when contract is verified

@ehealthua-tech FYI

no description. all tickets firstly should be at Jira


Upgrade to Guava 19

has any problem if i use 16.0.1? My project depend hbase540, 16.0.1 is require

See https://github.com/lettuce-io/lettuce-core/wiki/Dependency-Compatibility-Matrix for details.


Double comment inside Template Haskell

This commit double comments a line containing a syntax error as the first comment is removed during compilation, causing a parse error when attempting to use Haddock.
Fixes: https://github.com/Wizek/hs-di/issues/3

Cool. Followup: #5


Package the output into a more readable format

The current output of the planning problem is difficult to interpret for someone who does not know what to look for. For example, the current solution provided is something like the following:
[(<PyCall.jlwrap flip_row(r1)>, 1), (<PyCall.jlwrap flip_row(r3)>, 1), (<PyCall.jlwrap flip_column(c2)>, 1)]
Computation time: 18.53

It would be more preferable to have the output in a much simpler fashion, something like :
flip_row(r1), 1
flip_row(r3), 1
flip_row(c2), 1

I think this might be easily achieved by storing the output and trimming off the unnecessary bits, but we'll see about that during implementation.

There should be a python native function to remove all iterations of a substring of a string
From that you should be able to fix this by just removing <PyCall.jlwrap  (with the trailing space) and >
Wrap this into a method of Node called __str__(self) so it overloads the string operator.
Tell me if you need an example for the overloading

<PyCall.jlwrap flip_row(r1)>
This is an action, but we have no class for that. A way to pretty print it would be:

Create an Action class
Init with a self.jlwrap_action = jlwrap_action, self.cost = cost
Add __str__ method implementing the above script to remove unreadable aspect, and add the cost too
AutomatedPlanner.get_actions_from_path would then return a pretty printed list of objects of type Action.

The problem also lies with is the attribute state of a class Node. We have a method get_states_from_path in AutomatedPlanner that returns a list of the julia states. What we should do is:

Add the __str__ method to Node to pretty print important fields: attributes state and g_cost should be enough (I don't remember what a state look like so you'll have to investigate yourself [just use get_states_from_path in main instead of get_actions_from_path I guess])
Ditch the get_states_from_path entirely
Now when we print(path) that is output of a search algorithm, it should be pretty


Minor improvements related to Enterprise Contract

It's pretty low risk, so maybe I'll merge soon.

Good enough I think. Also this removes an annoyance from #56 let's merge so @lcarva can rebase.
Thanks @zregvart for the review.


Show state meta information

Currently only the version is shown

Show additional information like number of aggregated states, last execution, etc.

now using Github's relative time element


Color contrast of hexcode text is poor

The color contrast of the hex text of the active color is sometimes poorly legible. It's simple enough to remove the text altogether, but having it is a value add for the user (eg. they can see what it is, copy to clipboard, etc.)

Caption: #c7c7c7 barely shows up in the image

Resolved by #19


test: add oci 1.0 fallback e2e test

Description
What this PR does / why we need it:
Adds e2e test and accompanying setup to use upstream distribution OCI 1.0 registry to conduct e2e cli validation of OCI fallback.
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

[x] All e2e tests pass
[x] All unit tests pass

Checklist:

[ ] Does the affected code have corresponding tests?
[ ] Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
[ ] Does this introduce breaking changes that would require an announcement or bumping the major version?
[ ] Do all new files have appropriate license header?

@binbin-li I made the updates to the azure e2e test. I verified on my local fork and all AKS tests pass too.


Querying Hive partitioning parquets is slow

What happens?
Recently, we tried this extensions instead of using a standalone duckdb instance. When we run a simple SELECT query on parquet files, it's 2-20 times slower than DuckDB.
Profiling method
SELECT duckdb_execute($$SET enable_profiling='query_tree'$$); and watch logs.
To Reproduce
Query one field : SELECT name FROM public.table1 where code1 = 3261 and code2 = '001' and code3 = '5204' and code4 = '1'
code1 and code2 are partition fields.
DuckDB runs on cli 0.0190s
DuckDB runs in this extension 0.0291s
Total time of using this extension 0.513s
Query multi fields: SELECT name, level, detxlen, detylen, downid  FROM public.table1 where code1 = 3261 and code2 = '001' and code3 = '5204' and code4 = '1'
code1 and code2 are partition fields.
DuckDB runs on cli 0.0413s
DuckDB runs in this extension 0.037s
Total time of using this extension  0.552s
OS:
Ubuntu Server 22.04.3
ParadeDB Version:
paradedb/paradedb:16-v0.11.1
Are you using ParadeDB Docker, Helm, or the extension(s) standalone?
ParadeDB Helm Chart
Full Name:
Liu Qijie
Affiliation:
Dongguan University of Technology
Did you include all relevant data sets for reproducing the issue?
Yes
Did you include the code required to reproduce the issue?

[X] Yes, I have

Did you include all relevant configurations (e.g., CPU architecture, PostgreSQL version, Linux distribution) to reproduce the issue?

[X] Yes, I have

Thanks for opening! Would love your help with debugging this, or anyone else if willing to assist here :)


Publish nuget package from Release build

Just came accross the appveyor ci config and found that it publishes nuget package from Debug build, why not Release?

I was trying to get debugging info into Nuget so that dev's could debug this library from their own app.  Never succeeded and forgot to reset to Release build.
Feel free to fix.

@richardschneider  just sent a PR to add sourcelink and symbol package (latest .snupkg which can be published to nuget)


⚠ Bofrost.be has degraded performance

In 311716e, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1545 ms

Resolved: Bofrost.be performance has improved in 17115d6 after 11 minutes.


Can't compile with ghc 7.10.1

Just tried to install CCA (as part of Euterpea), without success. Seems to be a problem with Template Haskell, which has reportedly changed, but i'm not expert enough to pinpoint it, really ... here's what it says (no matter if from hackage or from source):
Preprocessing library CCA-<IP_ADDRESS>...
[1 of 4] Compiling Language.Haskell.TH.Instances ( src/Language/Haskell/TH/Instances.hs, dist/build/Language/Haskell/TH/Instances.o )

src/Language/Haskell/TH/Instances.hs:48:9:
    Not in scope: data constructor ‘ClassP’
    Perhaps you meant one of these:
      ‘ClassD’ (imported from Language.Haskell.TH.Syntax),
      ‘ClassI’ (imported from Language.Haskell.TH.Syntax),
      ‘Clause’ (imported from Language.Haskell.TH.Syntax)

src/Language/Haskell/TH/Instances.hs:48:26:
    Not in scope: data constructor ‘ClassP’
    Perhaps you meant one of these:
      ‘ClassD’ (imported from Language.Haskell.TH.Syntax),
      ‘ClassI’ (imported from Language.Haskell.TH.Syntax),
      ‘Clause’ (imported from Language.Haskell.TH.Syntax)
    In the Template Haskell quotation [| ClassP n ts |]

src/Language/Haskell/TH/Instances.hs:49:9:
    Not in scope: data constructor ‘EqualP’

src/Language/Haskell/TH/Instances.hs:49:26:
    Not in scope: data constructor ‘EqualP’
    In the Template Haskell quotation [| EqualP t t2 |]
cabal: Error: some packages failed to install:

Looks like there is significant incompatibility to the new Template Haskell. I can look into this, but I won't promise an immediate fix because I want the package to work with older GHC too. So for now, I'd suggest you use GHC 7.8.4 for Euterpea.

Should have been fixed by new version <IP_ADDRESS>.


gulp browser-sync css injection bug fix

Fixes issue with browser-sync css injection by trimming the query
string from the fileExtension. Also extended this to trim hashes that
could potentially be equally problematic.
see pull request #23

Thanks for this, but I've just implemented a fix in #27. Rather than trim the query string (which may result in unintended side-effects), I've changed to a regex test that allows them. I also added a configurable list of file extensions to serve directly, which the regex is automatically built from.


A few suggestions.

Hello!
I have a couple of ideas:

Could you, please, add text description about difference between models, especially between b0 and b2 general types?
Please consider adding hsemotion-onnx package to the pip repository.

Hello!

EfficientNet-B0 and B2 are the architectures proposed in an excellent paper. I just trained them by my own procedure. The main difference is in scaling, b2 accepts an input image with greater resolution(260x260 vs 224x224 from EfficientNet-B0). Moreover, the depth and width, and consequently, the size of EfficientNet-B2 are larger. Hence, it is potentially possible to reach better accuracy, but the latency of EfficientNet-B0 is better. But I should say, that my internal experiments demonstrate that EfficientNet-B0 works better for typical videos. I personally recommend to use enet_b0_8_best_vgaf.pt or enet_b0_8_va_mtl.pt in practice. These models are typically more accurate for various datasets if you do not want to fine-tune them on new domain
Thanks, I will try to do it in 1 or 2 weeks. I'm overwhelmed with a lot of reports now (

I created separate hsemotion-onnx package that is available via pip. Moreover, I slightly refactored the code and moved the python packages in the separate repositories: hsemotion and hsemotion-onnx


outEdges and inEdges not working

edgeCollection.outEdges() and edgeCollection.inEdges() no longer appear to be functional after upgrading from 7.8.0 to 8.6.0.  Making a call such as await edgeCollection.outEdges('notLinks/test1') results in this error stack:
    TypeError: Cannot read properties of undefined (reading 'allowDirtyRead')
      at Collection._edges (node_modules/src/collection.ts:3914:13)
      at Collection.outEdges (node_modules/src/collection.ts:3934:17)
      at Object.outEdges (src/__tests__/arango-service.test.js:506:39)

I've reviewed the migration guide and looked at the latest API documentation, but don't see anything listed that should impact this.

The problem is definitely on collection.ts.
    _edges(selector, options, direction) {
        const { allowDirtyRead = undefined } = options;
        return this._db.request({
            path: `/_api/edges/${encodeURIComponent(this._name)}`,
            allowDirtyRead,
            qs: {
                direction,
                vertex: (0, documents_1._documentHandle)(selector, this._name, false),
            },
        });
    }
    edges(vertex, options) {
        return this._edges(vertex, options);
    }
    inEdges(vertex, options) {
        return this._edges(vertex, options, "in");
    }
    outEdges(vertex, options) {
        return this._edges(vertex, options, "out");
    }

None of these functions has a default for options so it breaks _edges because options is undefined.


add are_configs_compatible implementation for ChainConfig

Description
This pull request implements the are_configs_compatible function for the ChainConfig struct. This function allows the comparison of two chain configurations to determine compatibility. It performs various checks related to fork blocks, support flags, chain IDs, timestamps, and more.
Changes Made

Implemented the are_configs_compatible function within the ChainConfig struct.
Added comprehensive checks to verify the compatibility of two chain configurations.
Introduced error handling to address various compatibility issues between configurations.

Usage Example
// Example usage of are_configs_compatible function
let config1 = ChainConfig{/* configuration parameters */};
let config2 = ChainConfig{/* configuration parameters */};

match config1.are_configs_compatible(&config2, /* block_number */, /* timestamp */) {
    Ok(_) => println!("Configurations are compatible."),
    Err(e) => eprintln!("Compatibility check failed: {:?}", e),
}

Potential changes
As the number of hardforks is quite high and will continue to be so, we could also make a more generic error like:
/// ConfigCompatError represents errors that occur when initializing the local blockchain
/// with a ChainConfig that would affect the historical state.
#[derive(Clone, Debug, PartialEq, Eq, Error)]
pub enum ConfigCompatError {
     /// Error related to changes in block numbers in stored and new configurations
     /// requiring a rewind to correct the issue.
     #[error("Block-based forking error: {0}")]
     BlockForkError {
         #[from]
         what: String,
         stored_block: Option<u64>,
         new_block: Option<u64>,
         rewind_to_block: u64,
     },

     /// Error related to changes in timestamps in stored and new configurations
     /// requiring a rewind to correct the issue.
     #[error("Time-based forking error: {0}")]
     TimeForkError {
         #[from]
         what: String,
         stored_time: Option<u64>,
         new_time: Option<u64>,
         rewind_to_time: u64,
     },
}

but I had the feeling that a specific error per case of incompatibility was more precise and allowed later reuse (more versatile in short).

hmm, I'm not sure where this could be useful?
do you have a usecase in mind for this?

@mattsse I saw this util in the Go implementation here: https://github.com/ethereum/go-ethereum/blob/cd0770ea6855a7704059aa7c591d0e83dcb21231/core/genesis.go#L366
And I think it could be useful when doing an update or a setup of a genesis block in the database in order to check that the configs are compatible in term of blocks. But if you think this is not useful don't hesitate to close it, I've learned during the process, no worry.

appreciate it!
I'm closing this here, because we moved the genesis types to alloy-genesis since then https://github.com/alloy-rs/alloy/tree/main/crates/genesis
But since geth has this function for the chain config type, I now think it would be appropriate to move this PR over to alloy-genesis?


Styles for [input:disabled] on checkboxes and radio. Issue #17918

Fixes #17918.

If possible, exclude dist/css/bootstrap.css* and docs.min.css* from the PR.

Also, it's not required, but you might want to associate the email address you used for your commit with your GitHub account so that you'll get credit for it in your GitHub profile page.

Thanks for the Git help, @cvrebert, much appreciated.  I have added the email to my GitHub profile (and updated git config with the preferred one so this doesn't happen again).
I tried to git rm the files, then commit with the --ammend flag to correct the PR and remove those files. I think I just made a mess of my local repo though. Should I try some more?  (also, would a push following an ammended commit update the email address used for the commit?)
I'd like to get this right, but don't want to waste your time.
Thank you!

Ok I realized the commits had not been pushed. I think the commit is now correct (i.e. rm'd the dist\css files). Interested in how it looks to you, @cvrebert.  Thank you!

Ok I realized the commits had not been pushed. I think the commit is now correct (i.e. rm'd the dist\css files). Interested in how it looks to you

Doesn't quite look right. (The files I mentioned shouldn't be in the diff at all.)

Should I try some more?

Nah, that's all right. We can fix it on our end when merging this.
(We'll use "git rebase" to do the fixing; you can google around for info on rebasing if you're interested, but it's somewhat advanced.)

(also, would a push following an amended commit update the email address used for the commit?)

To update the author info, you'd need to do git commit --amend --reset-author , and then do git push --force (which should be used with caution since it can "delete" (I'm oversimplifying) commits, but should be safe in this case).

Thanks for the info, Chris.  I will have a go at updating the email tomorrow when back in the office.

I did wonder that and I'll take a look. Thanks for your patience, Chris. I have used open source software for years and this is my first meaningful contribution to a project, so I am happy to make the effort to get it right.
If I make a change to use a variable, would it be a new commit/push (referencing this issue number?)

No problem! :smile: Thanks for giving back to the community :heart:
The variable declaration should be added to _variables.scss

If I make a change to use a variable, would it be a new commit/push (referencing this issue number?)

Yes, that'd be fine.

I'll include the doc changes in the commit, but that is probably the most subjective part because you might not like the wording. Ideally, I would show you a diff of the changes for review prior to committing. How best to achieve this?

Eh, you might as well just commit your suggestion and then depending on the feedback either you can push more fixup commits or we can fix it ourselves when we go to merge it. In any case, we'll squash it into a single commit on our end when we merge this PR.

Thanks once again, Chris. I'll add the doco commit later when I can test (Jekyll setup is problematic on this machine.)

Hello Chris, me again. While I have tested every change prior to commit, I clearly haven't linted. Sorry for the hound spam. Lesson learned.
Can I just check whether you are likely to be happy with wrapping the checkbox/radio label in a span? This is in order to apply the cursor: none; style. I ask because it adds a relatively large chunk of characters to the html (every time an element is used) for what is a small detail (and only pertinent when the element is disabled). i.e.
before:

    <input type="checkbox" checked="checked">

    Can toggle this

after:

    <input type="checkbox" checked="checked">

    Can toggle this

I tend to think the cleaner the html the better, but I see the value either way. I'm curious which way you'd want to go.

Can I just check whether you are likely to be happy with wrapping the checkbox/radio label in a span?

Those sorts of design specifics regarding the custom form widgets are @mdo's department rather than mine.

Changes from here are now part of #18771 (squashed and rebased there). Thanks!

Thanks @mdo, it's great to have made even a small contribution. Will I be famous and show up as a contributor? (I'm a simple man :blush:)

Hah, yeah, you'll be on the contributors list once the v4-dev branch makes it into master :).


Unable to view the options to select the Arc Knob or Radial Knob controls for a Whole Number field.

Hi, I am unable to view the options to select the Arc Knob or Radial Knob controls for a Whole Number field. Slider control is present though. Please instruct.
Regards,
Akhil

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

ID: 5435ffcb-2f82-7513-7ffc-d5ae6529512a
Version Independent ID: 6e4f6d2a-0ed9-84c9-d680-1c1ddc732454
Content: Use custom controls for model-driven app data visualizations in Power Apps - Power Apps
Content Source: powerapps-docs/maker/model-driven-apps/use-custom-controls-data-visualizations.md
Service: powerapps
GitHub Login: @Mattp123
Microsoft Alias: matp

@akhildynamics - Sorry for the delay but wanted to wait until the fix rolled out before responding. The ability to see the slider control, which has been deprecated along with the other controls you listed, was an oversight that has now been fixed. More information about the deprecation can be found here: Model-driven app controls deprecation
Closing issue

Hello,
But if that controls are deprecated, the originating document for this issue: https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/use-custom-controls-data-visualizations shouldn't be modified to present only "current controls", or at least add a note besides the need for "classic experience" with the link to "controls deprecation" mentioned above?
Kind Regards,
Lucian

Can someone please fix the documentation? Its misleading to use images for controls that are now deprecated. @Mattp123 This is not resolved. We had to go through an endless troubleshooting only to find out this feature has been deprecated for a year but documentation does not reflect it.


Looks interesting but seems to depend on the browser environment

This library looks interesting. I work in React-Native, so the traditional browser objects are not always available. Am I correct in assuming that you depend on browser objects? One interesting way to avoid this, is to work with default methods that can be replaced through an options object. For instance, global event listeners for connect work differently in React-Native, but could easily be supplyied as a function reference.

I'm not sure of the environment React Native is running in but I have tests for WebWorkers and document and window are not available there, so no I don't depend those browser objects. I depend on CustomEvent which if missing, the polyfill for it requires document so if CustomEvent is available, I'm quite sure it'll work.

Any updates @mschipperheyn ? did you have success with React-Native?

Hi. I didn't have time to test it yet

FYI, I just tested using robust-websocket in React Native 0.39.2 and it worked successfully without issue. This is great because unfortunately reconnectingwebsocket does not work with React Native because of it's dependence on the document object for generating events.

Great to hear thanks @sachinrekhi ! I'll close this, but suggestions or a PR on how to test React Native would be welcome.

Actually I spoke to soon. Looks like it works fine in the iOS Simulator, but once I pushed to production I got "Can't find variable: CustomEvent". And as you mentioned, the polyfill requires document, which is not available in the React Native javascript environment.

That's odd... Support for CustomEvent in iOS goes back to iOS 6 according to caniuse.com how old of devices do you have to support?


fix: byte size fix

这个 PR 实现什么功能/修复什么问题:
byte size fix
是否需要 backport 到之前的 release 分支:

release/3.1

/area region
/cc @zexi

Codecov Report

Merging #6658 into master will increase coverage by 0.00%.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master    #6658   +/-   ##
=======================================
  Coverage    7.15%    7.15%
=======================================
  Files         647      647
  Lines      109345   109345
=======================================
+ Hits         7827     7829    +2
+ Misses     100918   100917    -1
+ Partials      600      599    -1

Flag
Coverage Δ

#aFlag
7.15% <0.00%> (+<0.01%)
:arrow_up:

Impacted Files
Coverage Δ

pkg/cloudprovider/objectstore.go
2.53% <0.00%> (ø)

pkg/appsrv/response.go
69.11% <0.00%> (+2.94%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f0a0eb4...5ed624d. Read the comment docs.


⚠ Samsung has degraded performance

In f3f31dc, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2307 ms

Resolved: Samsung performance has improved in 758ea8f.


Content select-over-clause-transact-sql , Not AdventureWorks, should be AdventureWorksDW2019

At https://docs.microsoft.com/en-us/sql/t-sql/queries/select-over-clause-transact-sql?view=sql-server-ver15
This code was wrong
Current:
-- Uses AdventureWorks

SELECT SalesOrderNumber AS OrderNumber, ProductKey AS Product,
       OrderQuantity AS Qty,
       SUM(OrderQuantity) OVER(PARTITION BY SalesOrderNumber) AS Total,
       CAST(1. * OrderQuantity / SUM(OrderQuantity)
        OVER(PARTITION BY SalesOrderNumber)
            *100 AS DECIMAL(5,2)) AS PctByProduct
FROM dbo.FactResellerSales
WHERE SalesOrderNumber IN(N'SO43659',N'SO43664') AND
      ProductKey LIKE '2%'
ORDER BY SalesOrderNumber,ProductKey;

should be
-- Uses AdventureWorksDW2019

SELECT SalesOrderNumber AS OrderNumber, ProductKey AS Product,
       OrderQuantity AS Qty,
       SUM(OrderQuantity) OVER(PARTITION BY SalesOrderNumber) AS Total,
       CAST(1. * OrderQuantity / SUM(OrderQuantity)
        OVER(PARTITION BY SalesOrderNumber)
            *100 AS DECIMAL(5,2)) AS PctByProduct
FROM dbo.FactResellerSales
WHERE SalesOrderNumber IN(N'SO43659',N'SO43664') AND
      ProductKey LIKE '2%'
ORDER BY SalesOrderNumber,ProductKey;

Approved fix in https://github.com/MicrosoftDocs/sql-docs/pull/7599

@donhuvy -- Do, thank you very much for your contribution here.
@VanMSFT -- Van, thank you for confirming.


fix(app): don’t fetch schedules on load for some roles

:tada: This PR is included in version 2.53.8 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Question

Hello!
How & where do we sign up for the gift cards on Microsoft?
How long do you have the wait to receive them?

Hi!
You might want to check this website out: Microsoft Rewards FAQ
If you have any more questions feel free to ask them here :)


Using ArraySlice<Substring> in a Set causes a flaky crash

Describe the bug
Using ArraySlice<Substring> in a Set or as a Dictionary key crashes sometimes with Fatal error: Duplicate elements of type 'ArraySlice<Substring>'. The crash is not stable but wrapping it in a loop makes it easy to reproduce.
In the provided reproduction example changing any of the following fixes the crash:

Mapping ArraySlice<Substring> to ArraySlice<String>
Removing 🫠 emoji
Changing import A.C to import D.C

To Reproduce

Create the following main.swift file:import Foundation

var tryCrashSwiftHashingAttempt = 0

while true {
    tryCrashSwiftHashingAttempt += 1

    let example = """
        🫠
        import A.B
        import A.C
        """

    let lines = example.components(
        separatedBy: CharacterSet(charactersIn: "\u{000A}\u{000D}")
    )

    func splitImports(contents: String) -> [ArraySlice<Substring>] {
        let importIdentifier = contents.split(separator: " ").last!
        let importedParts = importIdentifier.split(separator: ".")

        return stride(from: 0, to: importedParts.count, by: 1).map {
            importedParts[0..<importedParts.count - $0]
        }
    }

    var mySet = Set<ArraySlice<Substring>>()

    let lastLine           = lines[lines.index(lines.endIndex, offsetBy: -1)]
    let lastBeforeLastLine = lines[lines.index(lines.endIndex, offsetBy: -2)]

    [lastLine, lastBeforeLastLine].forEach { line in
        splitImports(contents: line).forEach { slice in
            mySet.insert(slice)
        }
    }

    print(tryCrashSwiftHashingAttempt)
}

Compile with swiftc main.swift or swiftc -O main.swift.
Run ./main
Within a couple of seconds the process should crash with:Fatal error: Duplicate elements of type 'ArraySlice<Substring>' were found in a Set.
This usually means either that the type violates Hashable's requirements, or
that members of such a set were mutated after insertion.

Expected behavior
The process doesn't crash
Screenshots

Environment (please complete the following information):

OS: macOS 12.5
Xcode Version:

13.4
14 beta 1

🤔 I suspect that this is related to https://github.com/apple/swift/issues/59388.


Make remote storage test less flacky

I wonder why it wasn't so flaky before? Or this is just my observational bias?

@arssher I added new checks on friday, test passed locally and in my PR but started to fail on main

Also, somewhere around that time I've created a PR that arrived in main separately: we now load all layers into pageserver's memory eagerly on startup, hence kicking off the gc and compaction threads.


Deployment Issue with<EMAIL_ADDRESS>

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the
Amplify Console GitHub Issue Tracker

Describe the bug
Version 4.29.2 causes the bug bellow when deploying an amplify project
TypeError [ERR_INVALID_ARG_TYPE]: The "original" argument must be of type function
at promisify (internal/util.js:214:11)
at Object. (/root/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/extract-zip/index.js:11:18)
Amplify CLI Version
Version 4.29.2
To Reproduce
2020-09-18T06:48:13.387Z [INFO]: ><EMAIL_ADDRESS>postinstall /root/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli
> node scripts/post-install.js
2020-09-18T06:48:13.608Z [INFO]:
2020-09-18T06:48:13.609Z [INFO]: ----------------------------------------
2020-09-18T06:48:13.609Z [INFO]: Successfully installed the Amplify CLI
----------------------------------------
JavaScript Getting Started - https://docs.amplify.aws/start
Android Getting Started - https://docs.amplify.aws/start/q/integration/android
iOS Getting Started - https://docs.amplify.aws/start/q/integration/ios
Amplify CLI collects anonymized usage data, which is used to help understand
how to improve the product. If you don't wish to send anonymized Amplify CLI
usage data to AWS, run amplify configure --usage-data-off  to opt-out.
Learn more - https://docs.amplify.aws/cli/reference/usage-data
2020-09-18T06:48:13.659Z [WARNING]: npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/@aws-amplify/cli/node_modules/chokidar/node_modules/fsevents):
npm WARN
2020-09-18T06:48:13.660Z [WARNING]: notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
2020-09-18T06:48:13.664Z [INFO]: +<EMAIL_ADDRESS>added 1064 packages from 723 contributors in 31.875s
2020-09-18T06:48:13.694Z [INFO]: # Executing command: amplifyPush --simple
2020-09-18T06:48:13.699Z [INFO]: # Getting Amplify CLI Cloud-Formation stack info from environment cache
2020-09-18T06:48:13.706Z [INFO]: # Start initializing Amplify environment: master
2020-09-18T06:48:13.706Z [INFO]: STACKINFO={
"awscloudformation": {
"AuthRoleName": "amplify-blastapplication-master-x-authRole",
"UnauthRoleArn": "arn:aws:iam::x:role/amplify-blastapplication-master-x-unauthRole",
"AuthRoleArn": "arn:aws:iam::x:role/amplify-blastapplication-master-x-authRole",
"Region": "us-east-2",
"DeploymentBucketName": "amplify-blastapplication-master-x-deployment",
"UnauthRoleName": "amplify-blastapplication-master-x-unauthRole",
"StackName": "amplify-blastapplication-master-x",
"StackId": "arn:aws:cloudformation:us-east-2:x:stack/amplify-blastapplication-master-x/2096f390-c338-11ea-adcd-06ffde09431c",
"AmplifyAppId": "1231313123213"
},
"categories": {
"auth": {
"blastAuth": {}
},
"function": {
"blastCustomApiHandler": {},
"blastOauthCallback": {},
"blastPostExecutor": {},
"S3Trigger7ead5c51": {}
}
}
}
# Importing Amplify environment: master (amplify env import)
2020-09-18T06:48:14.568Z [INFO]: Scanning for plugins...
2020-09-18T06:48:14.608Z [INFO]: Plugin scan successful
2020-09-18T06:48:14.665Z [INFO]: Successfully added environment from your project
2020-09-18T06:48:14.878Z [INFO]: # Initializing existing Amplify environment: master (amplify init)
2020-09-18T06:48:15.829Z [INFO]: Note: It is recommended to run this command from the root of your app directory
2020-09-18T06:48:16.162Z [INFO]: init failed
2020-09-18T06:48:16.164Z [INFO]: /root/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/extract-zip/index.js:1
TypeError [ERR_INVALID_ARG_TYPE]: The "original" argument must be of type function
at promisify (internal/util.js:214:11)
at Object. (/root/.nvm/versions/node/v8.12.0/lib/node_modules/@aws-amplify/cli/node_modules/extract-zip/index.js:11:18)
at Object.Module._extensions..js (module.js:664:10)
2020-09-18T06:48:16.171Z [ERROR]: !!! Build failed
2020-09-18T06:48:16.171Z [ERROR]: !!! Non-Zero Exit Code detected
2020-09-18T06:48:16.171Z [INFO]: # Starting environment caching...
2020-09-18T06:48:16.172Z [INFO]: # Uploading environment cache artifact...
2020-09-18T06:48:16.239Z [INFO]: # Environment caching completed
Expected behavior
The build should work just fine. I had to bump down to 4.29.1 in my build for the build to succeed.
Desktop (please complete the following information):

Node Version. You can use node -v to check the node version on your system

node v8.12.0 (npm v6.4.1)

Also started seeing a similar issue as of Wednesday, Sep 16.

There are multiple possible workflows on the Amplify Console, I tried to connect a new app and I was not to reproduce.
Could you give us more information on how to reproduce? Did you have an existing project deployed on Amplify Console?

There are multiple possible workflows on the Amplify Console, I tried to connect a new app and I was not to reproduce.
Could you give us more information on how to reproduce? Is this for an existing project already deployed on Amplify Console?
Node v8.x has been deprecated, could you update the node version to v12.x and try again?

It does seem like it's an issue with using Node 8. I deployed with 4.29.2 under node 12 and things seem to be working again.


Move the status icon code out of the RAMSTK controller and into a GUI module.

This issue was automatically generated from a TODO comment in the file src/ramstk/RAMSTK.py.

Fixed in commit aada8a40d266f1337b52f4d8073a67e7d53318ae


Change hyper-dark-dracula to hyper-dracula

I update npm change hyper-dark-dracula to hyper-dracula with dracula organization to maintainer.

Thanks!


Hack Series Facilitators

We're going to be running 10 different cohorts on Friday, Saturday and Sunday. In order to fill up the weekend sessions, we're going to need extra leaders.
It was agreed we would try pulling some leaders from our prospective applicant pool (which @zachlatta is also working through today, #311)
Alex and Selynna have both confirmed that they are going to take a cohort on the weekend. Alex has not specified a time, Selynna is going to do 4pm.

This is who have confirmed they can lead the sessions:
Friday

Jonathan Leung

Saturday (all sessions)

Issa
@ssun098

Sunday

Erina
Jasmine
Leila

I will be chatting with Alex B and and other Alex later

Can we close this? Seems like we have people set.

@zachlatta Looks like we are still waiting on time slots from Alex *'s

Ah, sounds good!

Closing this because Hack Series is done. Kudos to the awesome volunteer facilitators we had.


Apply new ordering implementation

Savant RS: 0.1.74
Check pass-through tests with B-frames
Check a slow pipeline (animegan)

Error Unable to find ordering info for source example.
Run license_plate_recognition using run_perf wiht multi-stream on Orin Nano, e.g. ./samples/license_plate_recognition/run_perf.sh 1
Logs
...
 INFO  insight::savant::license_plate_recognition           > Added source source-0
stty: 'standard input': Inappropriate ioctl for device
 ERROR insight::savant::deepstream::buffer_processor        > Failed to prepare output for buffer with PTS 80000000: Unable to find ordering info for source id = source-0.
Aliases for entries in sys.path:
    <distpkg>: /usr/local/lib/python3.8/dist-packages
Traceback (most recent call last):
    <distpkg> /savant/gstreamer/buffer_processor.py:82    output_probe                 for sink_message in self.prepare_output(buffer, user_data):
    <distpkg> /savant/deepstream/buffer_processor.py:377  prepare_output               yield self._delete_frame_from_pipeline(frame_idx, sink_message)
    <distpkg> /savant/deepstream/buffer_processor.py:550  _delete_frame_from_pipeline  spans = self._video_pipeline.delete(frame_idx)
ValueError: Unable to find ordering info for source id = source-0
...

The problem with license_plate_recognition on Orin has been solved.


Unable to initiate a transaction in polygon in Dapp browser and/or WalletConnect

A. AlphaWallet dapp browser only

Direct injection within alpha wallet browser gives the same error

B. AlphaWallet WalletConnect + external browser

It doesn't show any error but simply gets into wallet connect and no prompt is shown.. the website loads forever waiting for the sign

C. AlphaWallet dapp browser + WalletConnect

Same as A
Example dapp: https://app.thesmurfssociety.com/ + Polygon Chain
Could be same issue as #3082
v3.61.0 (237)

@hboon Reproduced on 3.61 and fixed in master. Should be good to close.

Thanks! 👍

Re-opening as user said:

Not solved yet.. EIP 712 transaction in polygon chain is not popping out is what the dev says

—
https://discord.com/channels/548357107267928064/548358111669256192/1076531651141697726

Almost certain #3141 closes this


Allow failures in kind cleanup and log

There have been a couple failures where kind breaks at the end of the
test, with no indiciation of any issues. We should allow these to fail,
as they are not relevant to the test, but add some debug logging so we
can track down the issues.

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
96437fa79eb0d3216bd14ec37e37b946c8c086e4
link
/test integ-new-install-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/cherry-pick release-1.4

@jwendell: new pull request created: #18748

In response to this:

/cherry-pick release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.