Where can I find the database definition?

Hi,
I'm trying to run this project but I can't make it work. I have the application running but I can't pass the login screen because I don't have the database model. Can you guide me of where can I found the sql or anything else where is defined the database model?
I'm running it on my Windows and have configured a MySQL server for it.
Thanks

We no longer use a relational database, so starting the app should now be sufficient.


Dedicated functionality for .jks

I think it would be sensible to add dedicated functionality (without creating a project) for actions related to the generation Android jks key and also for getting SHA1/SHA256 fingerprints of the existing key.

Planned in version 1.1.1 (26)


Syntax highlighting not available

I don't know if this was caused by the move back to GIFs but syntax highlighting seems to have been lost.

The code is now inside a webview, so we will have to add syntax highlighting ourselves

Who would be in for a brainstorming (e.g. on a videocall) to get to a high-level architectural decision on this? Back go gifs would be an option with good spam filtering and make the extension much more useful with low effort. Recording text with syntax highlighting would be more "codish" - you can copy-paste stories, pipe them into whatever - probably more useful the long run to do it as text but also more difficult to get it right


fix splash screen timing

Description
prevent hiding splash screen before getting auth information

Used into https://github.com/BearStudio/start-ui-native/pull/103


Hitting Run on compound debugger changes the selected debugger

VSCode Version: Code 1.15.0 (8b95971d8cccd3afd86b35d4a0e098c189294ff2, 2017-08-09T20:16:18.034Z)
OS Version: Windows_NT x64 10.0.15063
Extensions: the listing length exceeds browsers' URL characters limit

Steps to Reproduce:

Select a compound debugger (in my case C# and Chrome)
Hit F5
Drop down changes to the first debugger in the compound list.
Next run uses that instead of the compound debugger.

Reproduces without extensions: Yes/No

duplicate of https://github.com/Microsoft/vscode/issues/32318


Put together a "Quick Start" Page/ Guide

@IlCallo - I'd like to do the Quick Start page. But, I'm now not certain if it fits in the plan, since we are making the site public to some people. Or, can we still add things?
Basically the idea is to give someone a simple path to get started with Quasar quickly. From there, I'd also send the user on their way to different parts of the docs, depending on their level of ability.
So, I guess I'm asking, should I do the Quick Start page or not now?
Scott

Reporting my answer from DM here, since I didn't had access to a PC during the weekend

As far as it doesn't involve me or Nick and the team is ok with it, there's no problem
We already discussed it 2 meetings ago and IIRC we said it's ok and we'll link it from the "get started" card directly
No problem doing changes to content in this phase, me and Nick are only against UI/UX changes until we get some feedback from the community


Background Transparency

A feature to make the background of notifications transparent would be great. I could configure picom to make the whole notification transparent, but ideally, there'd be a feature to make just the background transparent. This could be implemented as a config option inNotificationBlock.

This should be possible, and is a bug if it's not working.  I can't test right now, but will investigate more when I can.

It is? I think it's undocumented then, since I couldn't find it on the wiki pages.

Ah, I figured out that it's ARGB. Thanks for telling me this feature exists!

Looks like I overlooked actually showing how alpha is specified with hex colors.  I've changed it to use alpha in one of the NotificationBlock properties on the wiki page, hopefully this is enough.
Thanks for the issue regardless :).


FontAwesome uses different styles with same icon name

Hello,
Is it possible to distinguish different style in the FontAwesome icon family?
As the names are the same, I don't feel it is possible to distinguish between a solid and a regular icon, such as solid star and regular star.
I have tried to apply a class such as className={['fas', 'fa-star']}, without success.
node, npm, react-native, react and native-base version, expo version if used, xcode version
native-base:  2.13.12,
react: 16.11.0,
react-native: 0.62.2
Expected behaviour
Have a way to specify the style of the FontAwesome Icon.
Code
import {Icon} from 'native-base';
<Icon active type='FontAwesome5' name='star' />

Hi @mmailhos , Native Base Icons are limited to react-native-vector-icons.

Thank you @hanykumar, I have decided to use FontAwesome library directly instead, to have access to those icons


Customizing Workflow?

In the "Customizing Workflow" section, we currently have very little-- just a tiny bit about CLI plugins.
Formerly, we had extensive documentation on how each component could be customized.  I think given the complexity of some components, including all of that here might be way overkill.
I would, however, propose that we expand this section two include two things:

Links to component-specific documentation for those who really do want to dig down and tweak things.
A very brief tutorial on customizing Workflow's Helm chart.

tagging as something that needs to be done for the stable release, as right now there's no documentation for users migrating from v1 to disable user registration mode, for example.

I've started to lay down some of the groundwork in #139 but we need to add tunable settings for the other components as well.

doesn't https://github.com/deis/workflow/pull/141 also have some customization information?

punting to beta4

#141 is different, but it references #139

moving to rc1


Reduce label values hash op

[ ] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes
We are calling WithLabelValues(operation) every time to increment the counter. operation is set as a constant and only contains 2 values, postings or series.
WithLabelValues(operation) will try to hash the given label values and find the corresponding counter. In this case, we can just store the counter itself to reduce the CPU time on hashing.
This issue is identified in the store gateway CPU profile.
Verification

Good to know that hashing can have such high impact.


Add latency metrics

After #1662 (initial metrics support) and #1756 (refactoring chat endpoint), it will become practical to include latency metrics that's important to production (courtesy of @Yard1):

histogram of time to first token, and gauge of the mean, in ms
histogram of inter-token latency, and gauge of the mean, in ms
histogram of e2e time per request, and gauge of the mean, in ms
gauge of mean tokens per s per request. we currently only track the prefill and generation throughput, no request level.

A natural place to do it would be in the LLM engine or chat completion API, which ever one is less intrusive.

I am working on a PR for this

first draft https://github.com/vllm-project/vllm/pull/2316

#2764 looks to add a request level histogram of token throughput

Hi,
@Yard1 @robertgshaw2-neuralmagic
I want to use the metrics. I have exposed an API using the api_server.py
When I do a http://localhost:8075/metrics/, I get the following instead of seeing the values as described in the Metrics Class, How to see those metrics? :
# HELP python_gc_objects_collected_total Objects collected during gc
# TYPE python_gc_objects_collected_total counter
python_gc_objects_collected_total{generation="0"} 6290.0
python_gc_objects_collected_total{generation="1"} 8336.0
python_gc_objects_collected_total{generation="2"} 4726.0
# HELP python_gc_objects_uncollectable_total Uncollectable objects found during GC
# TYPE python_gc_objects_uncollectable_total counter
python_gc_objects_uncollectable_total{generation="0"} 0.0
python_gc_objects_uncollectable_total{generation="1"} 0.0
python_gc_objects_uncollectable_total{generation="2"} 0.0
# HELP python_gc_collections_total Number of times this generation was collected
# TYPE python_gc_collections_total counter
python_gc_collections_total{generation="0"} 826.0
python_gc_collections_total{generation="1"} 75.0
python_gc_collections_total{generation="2"} 6.0
# HELP python_info Python platform information
# TYPE python_info gauge
python_info{implementation="CPython",major="3",minor="10",patchlevel="12",version="3.10.12"} 1.0
# HELP process_virtual_memory_bytes Virtual memory size in bytes.
# TYPE process_virtual_memory_bytes gauge
process_virtual_memory_bytes 3.098353664e+010
# HELP process_resident_memory_bytes Resident memory size in bytes.
# TYPE process_resident_memory_bytes gauge
process_resident_memory_bytes 7.31774976e+08
# HELP process_start_time_seconds Start time of the process since unix epoch in seconds.
# TYPE process_start_time_seconds gauge
process_start_time_seconds 1.71188972784e+09
# HELP process_cpu_seconds_total Total user and system CPU time spent in seconds.
# TYPE process_cpu_seconds_total counter
process_cpu_seconds_total 18.27
# HELP process_open_fds Number of open file descriptors.
# TYPE process_open_fds gauge
process_open_fds 44.0
# HELP process_max_fds Maximum number of open file descriptors.
# TYPE process_max_fds gauge
process_max_fds 1.048576e+06

You need to make a request in order for the metrics to be populated

I am making a request with curl command and then monitoring the /metrics end point.
But I can't see the metrics like your screenshot.
I think I may need to add something to api_serve.py to point to the metrics.py but unsure what.

Are you curling either /v1/chat/completions or ,/v1/completions¿

Are you curling either /v1/chat/completions or /v1/completions?

Yes. /v1/chat/completions
curl -X 'POST' \
  'http://localhost:8075/v1/chat/completions' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -H "Authorization: Bearer lalit-1234" \
  -d '{
  "messages": [
    {
      "role": "user",
      "content": "Write an essay on plastic use"
    }
  ],
  "model": "jais-30b",
  "stream": true
}'

This debugging isn't really relevant to this thread, I'm going to move further discussion to #2850, where it is.

@hmellor hello, It seems that the discussion has moved to another place. Can this issue be closed？


bug: Execution sustained for a few seconds after promise resolution.

Describe the bug:
Given the JS file in the "Code" section, the library will temporarily hold the script open even after resolving the promise which returns the server status. For one-shot scripts like these, the delay can cause a bit of unneeded latency.
Code:
const util = require('minecraft-server-util');

(async () => {
    try {
        const response = await util.status("localhost");
        console.log(JSON.stringify(response));
    } catch (error) {
        console.log(JSON.stringify({
            message: error.message || "Unknown error during execution.",
            ...error
        }));
    }
})();

Expected behavior:
Immediate termination of script execution after promise is resolved (program should exit right after console.log calls). Instead, the script is left open a short while (around 3 to 6 seconds) after either console.log.
Additional context
Something might be messing with the Node.js event loop that causes the script to be held open for longer than expected. The temporary workaround here is to place a process.exit() at the end of the try-catch block, however I'm not informed enough of how the library works in order to determine whether or not this causes issues with the connection between the Minecraft server and the script (since it would technically be a hard exit instead of a "graceful" one). For now, it works as a way to quickly wrap things up when needed.

I've done some digging and it appears to be the timeout hackery that I have made not properly clearing the timeout when the response has been returned. I'll get it fixed sometime this week and release a fix.

Got it. Thank you very much!

I had some free time so I got to work on fixing this. Just released version 3.2.0, try updating and report back if the issue still persists. I had this same issue on my end but assumed it was Mocha hanging until you brought this to my attention.


Windows ddtray.exe shortcut needs to run as administrator

Describe what happened:

Installed Agent 6.0 on Windows 2016.
Selected the "Datadog Agent Manager" shortcut from the start menu
System tray icon has greyed out Configure option

Describe what you expected:
Configure to be enabled
How to Fix
Set the "Run this program as administrator" option on the shortcut's compatibility tab.
This is required because C:\ProgramData\Datadog is restricted to admins.

Addressed in #1370, closing! Should be fixed in the next release, thank you for reporting this
@rlaveycal

Reopening this issue.  Reverted the referenced PR due to related security concerns.

An alternative would be to create a datadog_admin group and permission the directory to give that group change access. Then an admin could add users to that group. Should avoid the need to run the tray as admin.

fixed in

https://github.com/DataDog/datadog-agent/pull/8438

systray requires admin privileges to run, however if launched unelevated it will attempt to elevate itself.


Typo with LM Fine tuning script

Typo with LM Fine tuning script

Codecov Report

Merging #1288 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1288   +/-   ##
=======================================
  Coverage   80.77%   80.77%
=======================================
  Files          57       57
  Lines        8092     8092
=======================================
  Hits         6536     6536
  Misses       1556     1556

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 0d1dad6...f0340ec. Read the comment docs.

Thanks, updated a bit to use format


prisma migrate dev --create-only executed previously created migrations

Bug description
prisma migrate dev --create-only commits migrations previously created with  --create-only. This is not exactly a bug, but it's unexpected behavior. I should be able to decide when to commit my migrations to the database.
How to reproduce

Create a migration with prisma migrate dev --create-only
Change your schema
Create another migration with prisma migrate dev --create-only
First migration is committed to the database.

Expected behavior
I expect the command --create-only to only create a migration and do nothing else.
Prisma information

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["nativeTypes"]
  binaryTargets   = ["native", "rhel-openssl-1.0.x"]
}

Environment & setup

OS: Catalina 10.15.7
Database: Postgresql
Node.js version: 12.22.1

Prisma Version
Environment variables loaded from .env
prisma                  : 3.1.1
@prisma/client          : 3.1.1
Current platform        : darwin
Query Engine (Node-API) : libquery-engine c22652b7e418506fab23052d569b85d3aec4883f (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli c22652b7e418506fab23052d569b85d3aec4883f (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine    : introspection-core c22652b7e418506fab23052d569b85d3aec4883f (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary           : prisma-fmt c22652b7e418506fab23052d569b85d3aec4883f (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash    : c22652b7e418506fab23052d569b85d3aec4883f
Studio                  : 0.423.0
Preview Features        : nativeTypes

Let's make a decision how to address this. Could we apply other "unapplied" migrations just to the shadow db and not the dev db?

Hey @jeremygottfried - could you share the use case why you want to generate multiple migrations without applying them to the database?

(See also: #5553, #9400, #11184)
Adding my own two cents, coming from a Django background I'm used to similar behaviour.
./manage.py makemigrations  # create only
./manage.py migrate         # apply only

I've also become accustomed to creating multiple migrations ahead of time, then going in to verify and edit them before applying them all. Particularly in the case of the expand and contract pattern, I like to generate my "expand" migration (add a new nullable column), an empty "populate" migration (where the data will be copied over), and a "contract" migration (deleting the old column, setting the new one not-null) ahead of time. Then I context-switch and figure out what needs to happen to populate the new column. Lastly I apply all the migrations.
I suppose it isn't a big difference between "[edit schema, edit schema], [edit migration, edit migration], [apply migration, apply migration]" and "[edit schema, edit migration, apply migration], [edit schema, edit migration, apply migration]", but there's less context-switching and the new files serve as a handy to-do list.

Could we apply other "unapplied" migrations just to the shadow db and not the dev db?

TBH this is what I naively assumed was already happening behind the scenes with --create-only.
As a Prisma novice this behaviour took me by surprise in my trial project, for a few reasons:

Migration filenames are dominated by a timestamp, so if you're giving your migrations similar names and not paying close attention, it's easy to miss that it's the previous migration being applied.
The documentation and prisma migrate dev --help don't mention this behaviour.
There's no prompt confirming that you intend to apply previous migrations, even if they contain destructive operations.
There is a prompt if there's a destructive operation in the new migration that is not being applied.

One of the things I really like about the rest of Prisma, is how interactive the CLI is. It does a good job of providing explanations and warnings and confirmations when I'm doing something new or destructive. I'd love to have an entirely new prisma migrate create command that used the shadow database and was guaranteed "safe". But I assume that would be a lot of work, and to be honest I'd still get 90% of the value out of a simple confirmation:
Warning: Before generating a new migration, all previous migrations must first be applied. Proceed (y/N)?

That alone would be enough to give the the confidence I'm not going to shoot myself in the foot. I'm sure it would help out a lot of other people coming from Rails and Django figure out the Prisma way of doing things, too.

Another reason I prefer to split "create" and "apply" into two steps: I have a little more confidence that the migration is going to behave the same when applied on the server as it does on my local machine. It's the exact same migrations being run through the exact same command.
I assume that internally, prisma migrate dev is calling the exact same code as prisma migrate deploy... but with prisma migrate dev --create-only && prisma migrate deploy, I know for sure.
This isn't because I don't trust the devs. It's because it makes a simpler mental model for me, and one less place to investigate when something that I don't understand happens.

(While I'm at it, I'd also like to address this thought from https://github.com/prisma/prisma/issues/5553#issuecomment-873588154)

This is meant to be happen in the context of your development database, applying migrations there is the bread and butter any time you run migrate dev and the way it's conceived you should even be ok with resetting the database often. Applying migrations could be unexpected perhaps but should not be perceived as danger or drama.

Yeah, it's not as dangerous as losing data on production. But a big part of my full-stack workflow involves populating my dev database in the course of developing and trialling new front-end features. I build up with bunch of new data that's directly relevant to the features I'm working on, covering the various extremes I want to handle. It's not coming from a seed script or copied from production.
If I unexpectedly lose a column or a table, it's not the end of the world. To be honest, the data is generally nonsense. But it's my nonsense data! And hey, I was using that! I'd at least like a warning so I can decide if it's worth making a quick backup copy, rather than spend half an hour generating brand new temporary nonsense.
Sure, sometimes even complete resets on dev are easier or inevitable. But when Prisma detects database drift, it suggests a reset and offers a choice... even though it's just the dev database.

Frankly, I explained the '--create-only' discussions to someone who has nothing to do with software using a metaphor.
Let's say;
We have a command called 'write text'. If you execute this command, it writes and sends text.
We have a command called 'write text --create-only'. If you execute this command, it only writes text. It does not send.
I asked the question what would you expect to happen if I did this operation twice?
1- write-text '--create-only'
2- write-text '--create-only'
Answer: "I only write text twice. I did not do any sending."
There seems to be a real fallacy here.
If we wanted to apply existing migrations, I guess we would not need an additional flag anyway.
I think the '--create-only' flag should only do the creation operation.
If we want to apply them to the database, we already have the options.


Add openra chapter

This PR adds the OpenRA chapter to the book

@rogierslag :shipit:

@pevers @jabbink @besuikerd FYI

Seems perfect :+1:
@avandeursen :smile:

Awesome guys, thanks!


App is crashing on 'Import From Gallery'.

QR > Import From Gallery:When we select an image, the app crashes immediately.
It is only happening on ios.
Tested on dev app v2.0.1(373)

We have removed this option for now.


dragon.json is what tools generate！

Thank you！

I have no idea what this request is, please provide more information.

Isn't it the Spine data file? (or Spriter? I forget :) )

Yes, I think he's looking for this : http://esotericsoftware.com/

@JiDW Thank you！


Fixed android warnings and SMT

This patches fixed all warnings and sample_multi_transcode initialization on Android

Please rebase this PR


[FR] Save screen real estate by minimizing display options bar

From @briankelly: Consider saving some screen real estate by eliminating this Display Options toggle and using a simple visual hint that this section is a drawer.
Here's some inspiration:

I don't think this is necessary to change. There's already a row in use at the top, where more controls will be added, so the toggle isn't taking up any additional vertical space (at least, it won't be when more controls are added). Adding a drawer will take away space from the entire sample grid, even when the sidebar is hidden.

I think the impetus for the request is that this UI element just looks really big. It doesn't really make sense to take up so much visual attention for a simple show/hide operation. That's why it has already been decreased in size w.r.t. the original design.
We'll have to solicit feedback from designer Claire before acting on this

I think the impetus for the request is that this UI element just looks really big.

This is accurate. I hear you regarding vertical space, @lethosor. Ideally we could get a win there, too, but if not, simply taking away a huge label [Display Options        ^] will improve the user's experience by not having so many things that are grabbing the user's attention.

Stale


Fix README typos

There are a few typos in the Installation Guide for Windows Users or Local Developement section, including command names.
Steps to reproduce the behavior:
View errors on README.md
"Developement" should be changed to "development".
px parcel src/index.pug should be changed to npx parcel src/index.pug
I can fix this, if you'd like!

Other than that can u add more things into it and make it look better?

I could add instructions on how to use the live website, like enabling browser popups and such.

Also make a Demo video of using it and place it after installation guide

Sure!


How to use it with Multi GPU

Thank you for your sharing!!! when I run with single GPU，it runs well, but when I run with multi GPU, it occur error
RuntimeError: Function CatBackward returned an invalid gradient at index 1 - expected device cuda:1 but got cuda:0
could you give some advice on this error?

@Hesene Hello Hesene, in my lab I only have one single 2080Ti, therefore I cannot replicate this issue. I'm sorry about it!

@Hesene Hello Hesene, in my lab I only have one single 2080Ti, therefore I cannot replicate this issue. I'm sorry about it!

Ok, thank you for your code, it help me a lot

I face the same problem.
Which part is the cause?

I'm seeing a similar issue when running with nn.DataParallel:
RuntimeError: Caught RuntimeError in replica 0 on device 0.
Original Traceback (most recent call last):
  File "/home/ryanstout/.local/share/virtualenvs/arsenal_train2-TlJZ47AR/lib/python3.7/site-packages/torch/nn/parallel/parallel_apply.py", line 60, in _worker
    output = module(*input, **kwargs)
  File "/home/ryanstout/.local/share/virtualenvs/arsenal_train2-TlJZ47AR/lib/python3.7/site-packages/torch/nn/modules/module.py", line 550, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/ryanstout/.local/share/virtualenvs/arsenal_train2-TlJZ47AR/lib/python3.7/site-packages/efficientunet/efficientunet.py", line 106, in forward
    x = torch.cat([x, blocks.popitem()[1]], dim=1)
RuntimeError: All input tensors must be on the same device. Received cuda:0 and cuda:1

Any ideas?
Thanks!

I'm seeing a similar issue when running with nn.DataParallel:
RuntimeError: Caught RuntimeError in replica 0 on device 0.
Original Traceback (most recent call last):
  File "/home/ryanstout/.local/share/virtualenvs/arsenal_train2-TlJZ47AR/lib/python3.7/site-packages/torch/nn/parallel/parallel_apply.py", line 60, in _worker
    output = module(*input, **kwargs)
  File "/home/ryanstout/.local/share/virtualenvs/arsenal_train2-TlJZ47AR/lib/python3.7/site-packages/torch/nn/modules/module.py", line 550, in __call__
    result = self.forward(*input, **kwargs)
  File "/home/ryanstout/.local/share/virtualenvs/arsenal_train2-TlJZ47AR/lib/python3.7/site-packages/efficientunet/efficientunet.py", line 106, in forward
    x = torch.cat([x, blocks.popitem()[1]], dim=1)
RuntimeError: All input tensors must be on the same device. Received cuda:0 and cuda:1

Any ideas?
Thanks!

Hi, bro.
Are you solved the problem?

I suspect that this problem is due to the sharing of a certain module in Efficientunet, which results in this module being only on one GPU, perhaps the encoder……

I suspect that this problem is due to the sharing of a certain module in Efficientunet, which results in this module being only on one GPU, perhaps the encoder……

I agree, I'm now facing the same problem.

@NPU-Franklin Franklin created a PR (#11 ) to support multi GPUs. I do not have multi cards therefore I cannot test it. But maybe you can give it a try.


GH-193 logs warning if failFast is false

ConfigServicePropertySourceLocator should log a warning and not an error if failFast is false

Merged in 54f76bc2


Apply yapf to pl_bolts 1/2

What does this PR do?
Follow-up PR of #509 and part of #482.
Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests? [not needed for typos/docs]
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review

[ ] Is this pull request ready for review? (if not, please submit in draft mode)

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

It looks yapf doesn't care long-name objects, so I placed noqa: E501 to ignore flake8 for better readability in https://github.com/PyTorchLightning/pytorch-lightning-bolts/pull/510/commits/51154d20a543b49e14d4ec03a9e03299f68e6ce2

It looks yapf doesn't care long-name objects, so I placed noqa: E501 to ignore flake8 for better readability in https://github.com/PyTorchLightning/pytorch-lightning-bolts/pull/510/commits/51154d20a543b49e14d4ec03a9e03299f68e6ce2

It looks yapf doesn't care long-name objects, so I placed noqa: E501 to ignore flake8 for better readability in 51154d2. I looked through the yapf docs, but they don't have any option to format this.

this may resolve the case ALLOW_SPLIT_BEFORE_DICT_VALUE = true

It looks yapf doesn't care long-name objects, so I placed noqa: E501 to ignore flake8 for better readability in 51154d2. I looked through the yapf docs, but they don't have any option to format this.

this may resolve the case ALLOW_SPLIT_BEFORE_DICT_VALUE = true

It looks yapf doesn't care long-name objects, so I placed noqa: E501 to ignore flake8 for better readability in 51154d2. I looked through the yapf docs, but they don't have any option to format this.

this may resolve the case ALLOW_SPLIT_BEFORE_DICT_VALUE = true

You're right, but it can lower readability a lot in other places:
--- a/pl_bolts/models/self_supervised/amdim/amdim_module.py
+++ b/pl_bolts/models/self_supervised/amdim/amdim_module.py
@@ -239,13 +239,20 @@ class AMDIM(pl.LightningModule):
         # CIFAR 10
         cf_root_lr = 2e-4
         cifar_10 = {
-            'dataset': 'cifar10',
-            'ndf': 320,
-            'n_rkhs': 1280,
-            'depth': 10,
-            'image_height': 32,
-            'batch_size': 200,
-            'nb_classes': 10,
+            'dataset':
+            'cifar10',
+            'ndf':
+            320,
+            'n_rkhs':
+            1280,
+            'depth':
+            10,
+            'image_height':
+            32,
+            'batch_size':
+            200,
+            'nb_classes':
+            10,

so, shall we go with noqa: E501?

It looks yapf doesn't care long-name objects, so I placed noqa: E501 to ignore flake8 for better readability in 51154d2. I looked through the yapf docs, but they don't have any option to format this.

this may resolve the case ALLOW_SPLIT_BEFORE_DICT_VALUE = true

You're right, but it can lower readability a lot in other places:
--- a/pl_bolts/models/self_supervised/amdim/amdim_module.py
+++ b/pl_bolts/models/self_supervised/amdim/amdim_module.py
@@ -239,13 +239,20 @@ class AMDIM(pl.LightningModule):
         # CIFAR 10
         cf_root_lr = 2e-4
         cifar_10 = {
-            'dataset': 'cifar10',
-            'ndf': 320,
-            'n_rkhs': 1280,
-            'depth': 10,
-            'image_height': 32,
-            'batch_size': 200,
-            'nb_classes': 10,
+            'dataset':
+            'cifar10',
+            'ndf':
+            320,
+            'n_rkhs':
+            1280,
+            'depth':
+            10,
+            'image_height':
+            32,
+            'batch_size':
+            200,
+            'nb_classes':
+            10,

so, shall we go with noqa: E501?

You're right, but it can lower readability a lot in other places:

ok, so just keep it as it is now :]

You're right, but it can lower readability a lot in other places:

ok, so just keep it as it is now :]


persist() to disk (if ram is full)

If I understand persist() correctly it loads a full dataset into ram. I am wondering what happens if the dataset does not fit into ram. It seems like dask is discarding some partitions and recomputes them later if needed. It would be great if dask would write these partitions to disk instead and reload them later if needed.
Do I understand the current implementation of persist() correctly and would such a "write-to-disk" behavior be possible?

Persist will compute the task graph up to the point where it was called and keep the result on the cluster (as opposed to returning to the client).  It will not necessarily be the case that the result will be in memory (though most likely it will be).  Dask can spill data to disk which can be configured in a number of ways.  Dask is designed to handle large than memory datasets, taking in what can be compute given resources/configuration and discarding data which is no longer need (intermediary results)
I would recommend taking this conversation to stackoverflow --typically we use the issue tracker for bugs/features.

Thanks for clarifying that!


Fix install-feature goal so you can accept the license during a build

When running the install-feature goal with the acceptLicense parameter not set, or set to false, you get a message printed out in the console to say that you need to accept the license, but it does not give you a mechanism to do so:

If you run the command manually, rather than through the plugin, it works fine giving you the option to select 1 for agree or 2 for not agreeing.

Since the acceptLicense parameter is specified as not required this behaviour is incorrect.

Hi, are you specifying the acceptLicense element. Like this:
        <execution>
            <id>install-feature</id>
            <phase>pre-integration-test</phase>
            <goals>
                <goal>install-feature</goal>
            </goals>
            <configuration>
                <features>
                    <acceptLicense>true</acceptLicense>
                    <feature>mongodb-2.0</feature>
                    <feature>ejbLite-3.2</feature>
                </features>
            </configuration>
        </execution>

The issue is more that it doesn't fail gracefully if you don't specify true

Just published new Ant tasks snapshot so this should behave like described in https://github.com/WASdev/ci.ant/issues/39.

Thanks


Backers page do not load properly

Version
2.5.8
Reproduction link
https://github.com/vuejs/vue/blob/dev/BACKERS.md
Steps to reproduce
Open the page
What is expected?
See the backers images
What is actually happening?
It is not possible to see the images

This is happening on the repository on github.
https://github.com/vuejs/vue/blob/dev/BACKERS.md

Works for me!

Op 21 nov. 2017 om 19:37 heeft Kelvin Ferreira<EMAIL_ADDRESS>het volgende geschreven:
Version
2.5.8
Reproduction link
https://github.com/vuejs/vue/blob/dev/BACKERS.md
Steps to reproduce
Open the page
What is expected?
See the backers images
What is actually happening?
It is not possible to see the images
This is happening on the repository on github.
https://github.com/vuejs/vue/blob/dev/BACKERS.md
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

For me is showing in that way

Some images are not loading.
I opened on Chrome and there the image dont show as well but dont crash.
Those prints were taken with Firefox.

I think they just don't have a logo, look at https://opencollective.com/vuejs
It would be nice if they displayed the default icon but it's not something we can fix on our end 😞

Oh, get it. Thans for taking time to investigate this :)


Add --from-to option to azcopy command

Add --from-to option to azcopy command as downloading turing-1b dataset is failing without this option.

@suri-kumkaran could you please link to the documentation of this option and why this solves the issue

I was able to reproduce the problem and confirm that @suri-kumkaran's suggestion fixed it for me.

@suri-kumkaran Thanks for the contribution.
I checked it and your proposal didn't work for the other branch that would invoke axel as download manager. Please verify that my fix works for you.

Hey @maumueller , yes this works for me.
Thanks for testing the axel branch.


Not working on FL Studio 20.8.4 on MacOS

Hello there,
I bought today a Komplete Kontrol A61 and downloaded the latest firmware on it. I read your manual fully and carefully and tried all I can to allow the FL Studio to recognize it but not a single key on the midi is recognized by the DAW. In the input section of FL's MIDI settings, it only shows KOMPLETE KONTROL A61 in both Output and Input (Doesn't show the words MIDI or DAW beside it as shown in your manual). Can you please help me fix this issue? Thank you!

The fact that not even the MIDI port appears sounds like for whatever reason the keyboard isn't being properly recognized. Try contacting Native Instruments to get hardware support  with a ticket in the lines of "My keyboard doesn't even send key presses to my DAW" about this since there's nothing I can do in my side to fix that.

No actually it shows "Komplete Kontrol A61" on both input and output. It works fine as a generic midi keyboard and all it's buttons work. However, only when I choose your custom "Komplete Kontrol A61" as a controller type rather than "generic controller". That's only the case when my controller stops working.

Then try to properly uninstall and reinstall the Komplete Kontrol software. The fact that the keys work just fine then that means the MIDI device that represents the keyboard itself is properly recognized, but the one that is needed to handle the DAW integration features doesn't which means an improper drivers installation. The drivers come bundled with the Komplete Kontrol software so uninstalling Komplete Kontrol will also uninstall the drivers for the keyboard and viceversa.
First uninstall Komplete Kontrol by following this guide from NI and deleting any Komplete Kontrol related file or folder on the paths at "Application Files" and "App-specific Data and Support Files" then reinstall it using Native Access.

Closing issue due to inactivity and no reply from user.


2-16-23 - Tweaking the setAlignment parameters

Changed the alignment for the graphics view to omit the Qt.AlignLeading flag

Spaced out the pipe characters instead of having them slammed together

Merged the changes in the WIP branch with the PySide2.QtCore.Qt import change.


Update README.md

Added cpp group

Thanks, I have just reordered to keep it alphabetically sorted. And yes, I screwed it up and force-pushed afterwards. The 3 is not an E, so C3H2 is currently still at top. :D


Helm index validation not honoring Artifactory bug which was mitigated in Helm 3.14.3

Hi,
today we ran into an issue with source controller version 1.3.0.
First we discovered that some Helm charts were missing from the index that source-controller created.
Downloading the index.yaml directly from the repository in Artifactory confirmed that the chart was present.
Then we downgraded the source-controller version to 1.2.4 and all was working as expected again.
So we started to investigate the changes between the two versions and we found it was the upgrade of the
Helm dependency from helm.sh/helm/v3 v3.13.3 to helm.sh/helm/v3 v3.14.4.
And found this issue: https://github.com/helm/helm/issues/12748
The behavior of the this validate function has changed.
version 1.13.3
https://github.com/helm/helm/blob/v3.13.3/pkg/chart/metadata.go#L131-L135
Version 1.14.4
https://github.com/helm/helm/blob/v3.14.4/pkg/chart/metadata.go#L138-L150
To mitigate the reported Helm issue check has been added:
https://github.com/helm/helm/blob/15f76cf83c670a329b62c2b5ddeb0864ec99daec/pkg/repo/index.go#L369
https://github.com/helm/helm/blob/15f76cf83c670a329b62c2b5ddeb0864ec99daec/pkg/repo/index.go#L402-L414
Which is now missing from the logic in source-controller.
Best way forward from here I currently see is to copy the the behavior from Helm to implement the level of validation.
Another option would be to ask the Helm project to change the loadIndex
to a public function and then use this directly in source-controller. (Might still be an issue with the logging and naming the source)
Cheers
Ricardo

Hi,
was wondering if any release is planned/scheduled? Last release was May 4th.

See https://github.com/fluxcd/flux2/issues/4947

Thank you. I assumed there would be a bug fix release 1.3.1 (hence the backport to the 1.3.x branch)


update build && check tool version

What this PR does / why we need it:
previous build tool had go version 1.13.8 with vulnerabilities, new one has 1.14.6 which is ok
CVEs: (details as of the time of ADV creation)
CVEID: CVE-2020-15586
Description: Go before 1.13.13 and 1.14.x before 1.14.5 has a data race in some net/http servers, as demonstrated by the httputil.ReverseProxy Handler, because it reads a request body and writes a response at the same time.
CVSS Base Score: 7.5
CVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/185446 for more information
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
CVEID: CVE-2020-14039
Description: In Go before 1.13.13 and 1.14.x before 1.14.5, Certificate.Verify may lack a check on the VerifyOptions.KeyUsages EKU requirements (if VerifyOptions.Roots equals nil and the installation is on Windows). Thus, X.509 certificate verification is incomplete.
CVSS Base Score: 5.3
CVSS Temporal Score: https://exchange.xforce.ibmcloud.com/vulnerabilities/185443 for more information
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Specify your PR reviewers:

/cc @gyliu513 @morvencao @clyang82
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

/assign @morvencao


Font won't change

I am using iterm2 on macOS. When I try to change the font by: set gfn=my\ font I get no change. I have tried a few fonts and setting the guifont in the editor too. I'm not sure what the issue is 🤷♂

me too

me too

AFAIK gfn is only for the GUI mode (e.g. desktop apps) and not the terminal. I don't think it's possible to override the terminal.


chore(default-flatpaks): Investigate if system-flatpak-setup needs to use dbus-run-session

Some Universal Blue users are affected with the issue where they don't get any system flatpak updates when using built-in auto-update service from ublue-os/config (not to be confused with ublue-update):
https://github.com/ublue-os/config/issues/168
Upstream issue:
https://github.com/flatpak/flatpak/issues/3847
Fedora Silverblue & Kinoite are known as affected.
I personally never had a problem with both ublue-os/config flatpak auto-updates & default-flatpaks module.
But in order to avoid potential upstream issue, workaround would be to use dbus-run-session before executing flatpak binary.

I think that we are not affected with this issue, so I'll close this.
If someone has this issue, please reopen.


Apple Silicon workaround in 1.2.2 does not play well with SPM

The workaround for building to simulator on Apple Silicon-based computers by setting in your podspec "EXCLUDED_ARCHS[sdk=iphonesimulator*]": "arm64" does not work for projects also using SPM. Could you create a framework with Arm64 iOS Simulator slice?

@jalmaas Thank you for filing this issue! This will be fixed in the next release of the Pod. The 1.2.2 XCFramework release includes simulator architectures for both arm64 and x86_64. However, as you pointed out, the podspec should not be excluding the arm64 arch. In the interim, a workaround might be to make a local podspec for GenesysCloudMessengerTransport pod based on the currently published podspec and remove the EXCLUDED_ARCHS lines. And then you can reference it from your Podfile like:
pod 'GenesysCloudMessengerTransport', :podspec => './GenesysCloudMessengerTransport.podspec'

We're also looking to make Messenger Transport SDK available through SPM which may also be of future interest to you.
Thanks again for taking the time to bring this to our attention.

Great! Thanks for the quick reply! That workaround will do while we wait for the updated podspec and maybe SPM-package..?


[Draft First table]: Source Recurly: Add dbt converter

Closes https://github.com/airbytehq/airbyte-dbt-models/issues/24
How

The tables from the fivetran model are analyzed for source-recurly
https://github.com/fivetran/dbt_recurly_source/tree/main/models

Fivertran's Streams were matched against Airbyte streams and differential tables were identified

Single transformation for the table account_balance is made from the account stream

Raising 1st draft PR for review

Current analysis: @marcosmarxm
URL: https://fivetran.github.io/dbt_recurly/#!/model/model.recurly_source

Fivetran
Airbyte

stg_recurly__account_balance_history.sql
Trasformation from accounts

stg_recurly__account_history.sql
accounts

stg_recurly__account_note_history.sql
account_notes

stg_recurly__billing_info_history.sql
billing_info

stg_recurly__coupon_discount.sql
coupons

stg_recurly__coupon_redemption_history.sql
❌ it doesn't exist

stg_recurly__credit_payment_history.sql
credit_payments

stg_recurly__invoice_coupon_redemption_history.sql
❌ it doesn't exist

stg_recurly__invoice_history.sql
invoices

stg_recurly__invoice_subscription_history.sql
❌ it doesn't exist

stg_recurly__line_item_history.sql
line_items

stg_recurly__plan_currency_history.sql
❌ it doesn't exist

stg_recurly__plan_history.sql
plans

stg_recurly__subscription_add_on_history.sql
❌ it doesn't exist

stg_recurly__subscription_change_history.sql
❌ it doesn't exist

stg_recurly__subscription_history.sql
subscriptions

stg_recurly__transaction.sql
transactions

stg_recurly__transaction_subscription.sql
❌ it doesn't exist

Waiting for the review @marcosmarxm with some comments :smiley_cat:

New models possible
Fivetran - coupon_redemption_history from Airbyte - account_coupon_redemptions

Currently, one transformation for account_balance from account has been done
New transformation possible, coupon_redemption_history from Airbyte - account_coupon_redemptions
Awaiting comment to verify, If I am going with the right path

@marcosmarxm, Please see the last commit, I've tried to add the account_coupon_redemptions source yaml
and do the transformation, but it shows it can't be found.
Is there anything I miss, or should I remove it,
Two possible transformations are done :heavy_check_mark:

Helloo,
I have a nested object for account id in schema account_coupon_redemptions how to add it to the source as columns?
stream: account_coupons_redemptions:
...
coupon:{
id: "123"
},
account:{
id: "345",
},
redemption_id: "12"
I've written directly like this, but not working | inside source_recurly/source/account_coupon_redemptions.yaml

Update: account_notes, billing_info, line_items, credit_payments, invoices left

Hi, @marcosmarxm, One doubt
Why is this error appearing as not found
Are my identifiers correct?

@btkcodedev try to get it runnig with postgres for snowflake/bigquery it is a small config problem.

Current Update: @marcosmarxm
URL: https://fivetran.github.io/dbt_recurly/#!/model/model.recurly_source

Fivetran
Airbyte

stg_recurly__account_balance_history.sql
:heavy_check_mark:  Trasformation from accounts

stg_recurly__account_history.sql
:heavy_check_mark:  accounts

stg_recurly__account_note_history.sql
:heavy_check_mark:  account_notes

stg_recurly__billing_info_history.sql
:heavy_check_mark:  billing_info

stg_recurly__coupon_discount.sql
NULL table

stg_recurly__coupon_redemption_history.sql
:heavy_check_mark:  Transformation from account_coupon_redemptions

stg_recurly__credit_payment_history.sql
:heavy_check_mark:  credit_payments

stg_recurly__invoice_coupon_redemption_history.sql
NULL table

stg_recurly__invoice_history.sql
NULL table

stg_recurly__invoice_subscription_history.sql
NULL table

stg_recurly__line_item_history.sql
:heavy_check_mark:  line_items

stg_recurly__plan_currency_history.sql
NULL table

stg_recurly__plan_history.sql
:heavy_check_mark:  plans

stg_recurly__subscription_add_on_history.sql
NULL table

stg_recurly__subscription_change_history.sql
:heavy_check_mark:  subscriptions

stg_recurly__subscription_history.sql
NULL table

stg_recurly__transaction.sql
:heavy_check_mark:  transactions

stg_recurly__transaction_subscription.sql
NULL table

What is the reasoning behind creating NULL tables, or is this something you're still updating?

@marcosmarxm, it would show error in Postgress as tables are not found, also there are no options for disabling it isn't it
Please correct if I am wrong

Comments resolved, Please check @marcosmarxm :bowing_man:

Oh yes, Thanks, I'll try with others the same

@marcosmarxm, After 5 hours of frying my brain, I could see SQL errors clearing slowly :partying_face:

Used your example to fill other models and Added all possible values in place of null :white_check_mark:
All the Snowflake and Bigquery SQL queries are cleared, only those that shows are tables doesn't exist, Please comment on how to clear those
In postgres, there are only two errors, but the table has those fields, Please comment on this too

Please continue to review :bowing_man:

In postgres error, user object is there and it has those fields
https://github.com/airbytehq/airbyte/blob/efd76b79d05bf96e5e66c72169c954e4639b4660/airbyte-integrations/connectors/source-recurly/source_recurly/manifest.yaml#L1126
Need comment on that

:bow Please continue to merge if it's ready.


Hide missing data in timeseries widget

We currently draw a line joining data points even if there is a hole in the data, we should not as it can be misleading, eg on the following screenshot the slopping line is actually a hole in the data:

For instance we could check if the time range between two data points is more than twice the update frequency. Can be tricky for data not regularly updated however.

We should probably insert null values for missing data according to https://github.com/chartjs/Chart.js/issues/5222.

Since we migrated to Chart.js 3, we cas use the spanGaps property (https://www.chartjs.org/docs/latest/samples/scales/time-max-span.htm).
However the spanGaps must be adapted according to the update frequency of the dataset.
The difficulty is now to define how to access the frequency when creating the chart.


bump: adal-node to 0.2.2

Fixes #3704

Bump here, while we're at it?

I thought about it, but 1) it's a more significant version bump that I don't really know how to test, and 2) we don't publish the package (it's only consumed by botframework-connector via devDependencies). My goal is to remove the tools/ sub-tree entirely as soon as we get around to removing it from botframework-connector tests. I think it's only relied on for some logic-heavy nock tests.

Thanks for doing this guys! I'm trying to finish a security vulnerability ticket for my company and would like to report when you are planning to do a new release for the 4.13.4 tag? When I update botframework-connector to 4.13.4 in my package.json it's still pulling in<EMAIL_ADDRESS>Thanks again 😄

@gbartlett 4.13.5 is now available on npm.


Retrieving a proposal status and archiving

Defender-client currently doesn't have endpoints to archive or retrieve the status of a proposal.
This is something that has been requested on the forums.

Moved to https://github.com/OpenZeppelin/defender/issues/2405


What additional steps needed to test webpart in workbench.aspx on test tenant?

I followed the tutorial of adding the workbench.aspx page to the documents library on the dev site collection in my test tenant. But I seem to be missing the extra steps to test my webpart there. What do I need to do to get the solution to deploy in the tenant. I see the instructions for testing in classic pages. What am I missing. Thanks.

If you have gulp serve  running then it's just for you to head on over to workbench.aspx, and accept "mixed content" (the little warning shield in the address bar in Chrome, use Chrome, not some other browser).
For usage in classic pages you need to package your solution, add the .spapp package to the app catalog and approve it. Still having gulp serve running, or deploy it to a CDN location somewhere.

Firefox works as well. Same restriction though (i.e. need to load mixed resources)

i guess at this time it's only possible test one web part at time, i've tried to add more webpart to the same project and fail, run multiple local serve with gulp serve and fail it again.

Thanks, stupid but not obvious mistake of trying to run workbench.aspx from a machine where the framework is not running.


Orchestration

Description
Fixes #
Note: It's a good idea to open an issue first for discussion.
Checklist

[ ] I have followed Sample Guidelines from AUTHORING_GUIDE.MD
[ ] README is updated to include all relevant information
[ ] Tests pass:   nox -s py-3.6 (see Test Environment Setup)
[ ] Lint pass:   nox -s lint (see Test Environment Setup)
[ ] These samples need a new API enabled in testing projects to pass (let us know which ones)
[ ] These samples need a new/updated env vars in testing projects set to pass (let us know which ones)
[ ] Please merge this PR for me once it is approved.
[ ] This sample adds a new sample directory, and I updated the CODEOWNERS file with the codeowners for this sample

data-science-onramp/feature-engineering/feature_engineering.ipynb


Errore since update

I just updated the Core to 2023.11 and the vacuum cleaner is gone.
Logger: homeassistant.config_entries
Source: config_entries.py:402
First occurred: 21:51:23 (2 occurrences)
Last logged: 21:52:23
Error setting up entry Greg for dreame_vacuum
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 402, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/dreame_vacuum/init.py", line 22, in async_setup_entry
coordinator = DreameVacuumDataUpdateCoordinator(hass, entry=entry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/dreame_vacuum/coordinator.py", line 125, in init
persistent_notification.EVENT_PERSISTENT_NOTIFICATIONS_UPDATED,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'homeassistant.components.persistent_notification' has no attribute 'EVENT_PERSISTENT_NOTIFICATIONS_UPDATED'

Same here :/

Same I thought it was just me and my vacuum was buggy or smth

Waiting for a solution I made a downgrade

Same issue for me.

Looks like related to this change: https://github.com/home-assistant/core/pull/101975

nevermind.. someone was faster! this is a duplicate of https://github.com/Tasshack/dreame-vacuum/issues/256

home-assistant\custom_components\dreame_vacuum\coordinator.py
change line 125
From EVENT_PERSISTENT_NOTIFICATIONS_UPDATED
TO SIGNAL_PERSISTENT_NOTIFICATIONS_UPDATED
save file.
reboot home assistant.
working good for me now


Feature Request: Dark mode for the docs

It would be really nice if DuckDB docs could also be viewed in dark mode.

Hi @csubhodeep – thanks, indeed this is a recurring request and we started looking into it in July!


ShowPublicationInfo() method is missing "Console"  class for WriteLine method

ShowPublicationInfo() method is missing "Console"  class for WriteLine method in code snippet to print Book Publication details.
Check below code snippet -
public static void ShowPublicationInfo(Publication pub)
  {
      string pubDate = pub.GetPublicationDate();
      WriteLine($"{pub.Title}, " +
                $"{(pubDate == "NYP" ? "Not Yet Published" : "published on " + pubDate):d} by {pub.Publisher}");
  }

Replace it with below code -
public static void ShowPublicationInfo(Publication pub)
  {
      string pubDate = pub.GetPublicationDate();
      Console.WriteLine($"{pub.Title}, " +
                $"{(pubDate == "NYP" ? "Not Yet Published" : "published on " + pubDate):d} by {pub.Publisher}");
  }

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

ID: 77d4fcf9-42c1-e015-798c-0c1519d77f41
Version Independent ID: 75aee013-1123-1403-b2bc-cc8b68b56de8
Content: Inheritance in C#
Content Source: docs/csharp/fundamentals/tutorials/inheritance.md
Product: dotnet-csharp
Technology: csharp-fundamentals
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

The code sample includes a using static System.Console; statement, which allows using methods from the static Console class without using the qualified syntax. Therefore, it is legal to use this simplified call syntax for the WriteLine function.
However, every other samples in this page use the Console.WriteLine syntax. To improve consistency, it might be useful to change the Write and WriteLine calls to use the qualified syntax.

Hi :wave: @smriti2901 @sputier
We've found several occurences where people miss the static using for examples when we show snippets of classes. When we show those, we've been using the class name. We should make the change @sputier recommends.
I've added the "up for grabs" label if anyone wants to make this change before we address it.

I'll create a PR in a few hours to fix this 👍


Fixes

LGTM, you just seem to have forgotten the ConditionalFilename destructor in the header file.
Also be careful of the coding style, seems like uncrustify isn't happy with your if without {} 😅

Isn't delete of nullptr safe though? Were you having any issue somewhere?
You seem to have forgotten the ConditionalFilename destructor in the header file. And uncrustify isn't happy with your if without {} seems like sweat_smile

Indeed calling delete on a nullptr is safe, I guess I'm just too used to C. You are right that I forgot to add to the header file, let me add it


Hide Error Pane

Is there any way to hide the error pane at the window bottom?
Like the search pane could be hidden with pressing ESC button.

There's a command linter:togglePanel that you can map to a key of your choice

Thanks! :+1:


fix doc error in example command

paths are mis-ordered respect to args

Thank you for your contribution!


Ability to click on menuchecklist item to apply filter

currently we have filtering using only textfield by searching for "Enter Filter Text..."], as some filtering has menuchecklist item to select.

I suspect what you mean is that you'd like the ability to filter columns that have filter types that are not string filters.
Just added support for list filters (toggling by text), and number filters.
Just have date filters to add, and probably boolean ones, although both those less common.
As part of this I have renamed filter_column to be filter_string_column though, since didn't make a lot of sense.
Not in a release yet, since will try and do the others over the coming days.

Ugh, date filters are a nightmare by the looks of it.
Not sure can devote the time to that at this stage.


client: Work around tight loop when retrying watch connection.

Add a 100ms sleep to avoid tight loop if reconnection fails quickly.
Fixes #9578

Any news on this one?

@fasaxc @caseydavenport This should be addressed by https://github.com/coreos/etcd/pull/9840. And was backported and released with 3.2 and 3.3 patch releases.


feat: add tabs and navigation

Add tabs for navigation between home, menu and options. This PR will also implement the menu (close #18) and options tab before getting merged.
Still Work in Progress.

Will merge this PR even if it is not really finished and create a new beta branch for all the new upcoming changes


Test older clang

Description
A detailed explanation of the changes in your PR.
Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive.
Checklist

[ ] Investigated and inspected CI test results
[ ] Updated documentation accordingly

Automated testing

[ ] Added unit tests
[ ] Added integration tests
[ ] Added regression tests

If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why you did not do so. (Valid reasons include "CI is sufficient" or "No testable changes")
In addition to reviewing your code, reviewers must also review your testing instructions, and make sure they are sufficient.
For more details, ref the Confluence page about this section.

Just tested the full image from this PR and it's working on 4.18.0-305.57.1.el8_4.x86_64
I guess now the problem is that we have a mismatch between required toolchain versions for kernel modules and eBPF probes for the same kernel.


Not respecting the line breaks

Describe the bug
The sorting is not respecting the line breaks to make it easy to read
Before

After

I don't think this is something headwind supports by default. Maybe you can change the regex so it treats each line as an independent group to sort?


Preact + Mitt Codepen Demo直接就是错误的

Preact + Mitt Codepen Demo 这个运行不起来

Subject: Preact + Mitt Codepen Demo is directly wrong
Body: Preact + Mitt Codepen Demo This won't work
Via Google Translate.
After some brief digging it looks like the Codepen project linked in README.md errors on load. The error appears to be caused by the @connect decorator on line 56. Near as I can tell this is caused by Babel not having babel-decorator or possibly babel-plugin-transform-decorators-legacy installed.


Build error with v8.1.1 and 404 or 500 pages

Describe the bug
I run locally development mode without an issue. But as soon I try to run build I receive following error:
> Build error occurred
Error: Export encountered errors on following paths:
        /404
        /404.html
        /500
        /de/500
        /en/500
        /fr/500
        /it/500

Occurs in next-i18next version
Most recent next-18next and NextJS version
I am not sure, do I need to add 404 or 500 pages with the language code? I currently did not configure it.

Please provide a reproducible repository.

Its related to NextJS <IP_ADDRESS>, after upgrade to latest canary the error is gone:
https://github.com/vercel/next.js/issues/22815


Issue: Illegal instruction

Thats the error I get
./Lagrange-1.1.2-x86_64.AppImage
Lagrange: A Beautiful Gemini Client
[the_Foundation] version: 1.0.0 cstd:201112
[the_Foundation] locale: en_US.UTF-8
Illegal instruction

OS: MX 19.3 (patito feo) x86_64 based Debian GNU/Linux 10 (buster)
SysV init version: 2.93
Kernel: 4.19.0-9-amd64
Xorg v1:7.7+19
WM: Spectrwm

Currently the AppImage is built with SSE 4.1 CPU instructions enabled. I'll disable that for the next build, which should help.
Thanks for reporting!

v1.1.3 is available, please test.

@skyjake v1.1.3 is working fine here. Thank you!


Can't create account, No category loaded by default🐛

Describe the bug
When creating account, No category get loaded or listed, and can't find a way to creat new ones.
To Reproduce

Account
create new
create a account name,
When try to select category, the list is empty, but is required to create an empty account.

Expected behavior
We should be able to either create new category ourself or accept to creat without it.
Screenshots

Desktop (please complete the following information):

OS: Docker
Browser Chrome
Version 121.0

This Bug is phenomenal??? the app is rendered usless if this bug isn't fixed ?


Prevent console spam when exporting a mesh with multiple texture coordinates

Signed-off-by: Nate Koenig<EMAIL_ADDRESS>Bug Report
Summary
Using the ColladaExporter can flood the console with warnings like the following:
[Wrn] [SubMesh.cc:478] Multiple texture coordinate sets exist in submesh: WallPlaster. Checking first set with index: 0

This happens when a mesh has multiple texture coordinates. The ColladaExporter can prevent this by using the SubMesh function calls that specify which texture coordinate set to use.
Checklist

[X] Signed all commits for DCO
[X] codecheck passed
[X] All tests passed
[X] While waiting for a review on your PR, please help review
another open pull request
to support the maintainers

Note to maintainers: Remember to use Squash-Merge

Focal CI failure is unrelated.


TypeError: can only concatenate str (not "ListConfig") to str

Hi, thanks for your awesome work. The commands for kitchen environment run well and training results are also reasonable. However, the command of Adroit pen task fails to run in my case.
>>> python hydra_launcher.py --multirun hydra/launcher=local hydra/output=local env=pen-v0 camera=["view_1","top","view_4"] pixel_based=true embedding=resnet50 num_demos=25 env_kwargs.load_path=r3m bc_kwargs.finetune=false proprio=24 job_name=try_r3m
/root/miniconda3/envs/r3m/lib/python3.7/site-packages/gym/spaces/box.py:84: UserWarning: WARN: Box bound precision lowered by casting to float32
  logger.warn(f"Box bound precision lowered by casting to {self.dtype}")
RS:> Registering Arms Envs
/root/miniconda3/envs/r3m/lib/python3.7/site-packages/transforms3d/quaternions.py:26: DeprecationWarning: `np.float` is a deprecated alias for the builtin `float`. To silence this warning, use `float` by itself. Doing this will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, use `np.float64` here.
Deprecated in NumPy 1.20; for more details and guidance: https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
  _MAX_FLOAT = np.maximum_sctype(np.float)
RS:> Registering Biomechanics Envs
RS:> Registering Hand Envs
RS:> Registering Kitchen Envs
/root/miniconda3/envs/r3m/lib/python3.7/site-packages/torch/utils/tensorboard/__init__.py:3: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.
  if not hasattr(tensorboard, '__version__') or LooseVersion(tensorboard.__version__) < LooseVersion('1.15'):
Error executing job with overrides: ['env=pen-v0', 'camera=[view_1,top,view_4]', 'pixel_based=True', 'embedding=resnet50', 'num_demos=25', 'env_kwargs.load_path=r3m', 'bc_kwargs.finetune=False', 'proprio=24', 'job_name=try_r3m']
Traceback (most recent call last):
  File "/root/miniconda3/envs/r3m/lib/python3.7/site-packages/hydra/_internal/utils.py", line 211, in run_and_report
    return func()
  File "/root/miniconda3/envs/r3m/lib/python3.7/site-packages/hydra/_internal/utils.py", line 389, in <lambda>
    overrides=args.overrides,
  File "/root/miniconda3/envs/r3m/lib/python3.7/site-packages/hydra/_internal/hydra.py", line 140, in multirun
    ret = sweeper.sweep(arguments=task_overrides)
  File "/root/miniconda3/envs/r3m/lib/python3.7/site-packages/hydra/_internal/core_plugins/basic_sweeper.py", line 161, in sweep
    _ = r.return_value
  File "/root/miniconda3/envs/r3m/lib/python3.7/site-packages/hydra/core/utils.py", line 233, in return_value
    raise self._return_value
TypeError: can only concatenate str (not "ListConfig") to str

The versions of the relevant packages are as follows:
hydra-core==1.1.1
hydra-submitit-launcher==1.1.5
omegaconf==2.1.1

They are the same as in your r3m_base.yaml. I also have tried other versions, but the bug is always there. Do you have any suggestions?

The error looks to be because you are passing in a list of cameras [view_1,top,view_4] when you should just pass in one.


nuxt / ssr workaround

yo @shshaw & @notoriousb1t
just wanted to share my fugly workaround for anyone else in nuxt:
html:
<template>

</template

computed:
  computed: {
    title: function() {
      const text = `split me baby`;

      if (typeof window !== `undefined` || typeof document !== `undefined`) {
        const Splitting = require("splitting");
        return Splitting.html({ content: text, by: "chars" });
      }

      return null;
    }
  },

nuxt.config.js:
  css: ["splitting/dist/splitting.css"],
  plugins: [{ src: "~/plugins/splitting.client.js", ssr: false }],
}

splitting.client.js:
import Vue from "vue";
import Splitting from "splitting";

Vue.use(Splitting);

last edit with a tip:
If you want to style this make sure you've got no scoped attribute

You can put the above in a mixin function and have text as parameter.
also figured you can do it as easy as this:
<template>

Split me baby

</template>

  mounted() {
    if (typeof window !== `undefined` || typeof document !== `undefined`) {
      const Splitting = require("splitting");
      Splitting();
    }
  },

Benefit is, that with JS disabled, the title will still show. With the previous method, it won't. If someone knows how, please reply

If someone knows how to fix showing the title in #1 case or knows how to fix the warning, please let me know 🙏

Wrapping it in a  component should fix the warning.

If you're running Nuxt with Vue 3, we've just created a lite adaptation of Splitting designed for Vue 3 which is fully SSR compatible (that's why we made it)
https://www.npmjs.com/package/vue3-splitting


feat: 🎸 adding server field in google.js

Regarding #753, I propose adding an optional server field that takes in an object which contains info about your preferred google cloud dataset. If server  is provided, the Google DICOM Store Picker modal is hidden/disabled and the studies are retrieved. Otherwise, the modal shows up normally.

Hi @omartoutounji, let me know if my feedback makes sense, or if you have pushback.

@dannyrb Your feedback made a lot of sense, thank you for taking the time to review the PR. I added all of your suggestions. Please let me know if there's more to do to get this PR merge-ready!
Also, I propose disabling the 'Change DICOM Store' button if the server prop is provided? I believe it makes sense that if a user provides a server prop then they probably don't want to ever change the DICOM store. What do you think?

@dannyrb Please let me know if this is not of satisfactory state so I can make necessary changes or close the PR, if needed.

Sorry for the delay. One last comment that should help align what you want with something that's safe to merge :+1:

@dannyrb could not load gcloud version of OHIF to manually test my changes. https://github.com/OHIF/Viewers/pull/919 is addressing this

@omartoutounji merged :+1:
Please let me know if you encounter issues.

@dannyrb as I was applying your suggestions, I realized something funny. The functionality we're trying to achieve with this PR, is already available by setting dicomWeb in google.js. Setting it also disables the modal without any of my changes being present.

@omartoutounji, ha. That may be the case. I believe I initially thought you wanted a way to change the default/preferred programmatically by setting a prop; but yes, if you're keeping the same dataset, simply using the appConfig should suffice.

@dannyrb as far as my use case goes, dicomWeb suffices. I just didn't know about it before I made this PR.
I, however, understand better what this PR is for now and will apply your suggestions with that in mind.
Re-reading our previous comments, I believe there was a mismatch in each of our goals for this PR but now it is more aligned!

Thanks for all your help!


Package sanction with client automatically

To test:
pip install -r requirements.txt
ok-publish
cp ok $ASSIGNMENT_DIR
cd $ASSIGNMENT_DIR
python3 ok --authenticate --no-update

This will require some testing but looks promising. I can't do the testing today - but will take a look on/before our next meeting.

Good news - it works. I haven't been able to test some other stuff I'd like to try yet like collaboration or using https with requests when normal SSL fails (on 32bit python etc)

Some bad news: It doesn't quite work with requests since requests has modules inside of it.
https://github.com/kennethreitz/requests/tree/master/requests/packages
(Using it without https works since it doesn't import their fork of urllib3)
It should be possible to fix with some small tweaks. I'll take a stab

^ the error was not because of the reason I mentioned earlier.
Requests started to throw requests.packages.urllib3.exceptions.SSLError: [Errno 20] Not a directory because it was trying to load a .pem from within a zipped file using the open function (which can't reading into a zipped module).
We decided the alternative is to read the .pem using the __loader__ property from the requests library and write it into the ok config folder. We can then set the REQUESTS_CA_BUNDLE environment variable.
We'll write the certfile if the file doesn't exist but set the environment variable on every run in the entry point of the ok script.
Note for future maintainers:
If there is an update to the upstream requests cacert.pem - previous users of OK would have an old file and we should update the file by publishing a new release. It is feasible to hash the file for changes or even copy over a fresh copy on every run - but we're going to consider that out of scope for this PR.


[WARNING]: - ironicbadger.ansible_role_snapraid was NOT installed successfully:

~/infra  ansible-galaxy install -r requirements.yml
Starting galaxy role install process
[WARNING]: - bertvv.samba (v2.7.1) is already installed - use --force to change version to
unspecified
[WARNING]: - geerlingguy.security (2.1.0) is already installed - use --force to change
version to unspecified
[WARNING]: - geerlingguy.ntp (2.3.1) is already installed - use --force to change version to
unspecified
[WARNING]: - geerlingguy.node_exporter (1.0.2) is already installed - use --force to change
version to unspecified
[WARNING]: - chriswayg.msmtp-mailer (master) is already installed - use --force to change
version to unspecified
[WARNING]: - stuvusit.smartd (master) is already installed - use --force to change version
to unspecified
[WARNING]: - oefenweb.dns (v1.1.32) is already installed - use --force to change version to
unspecified
[WARNING]: - notthebee.ubuntu_autoinstall (main) is already installed - use --force to
change version to unspecified

downloading role 'ansible_role_snapraid', owned by ironicbadger
[WARNING]: - ironicbadger.ansible_role_snapraid was NOT installed successfully: - sorry,
ironicbadger.ansible_role_snapraid was not found on https://galaxy.ansible.com/api/.
ERROR! - you can use --ignore-errors to skip failed roles and finish processing the list.

appears that its been removed from the site. tried manually installing it from github but its the same error

It was renamed to ironicbadger.snapraid. Also, there is a breaking change: renaming snapraid_runner_gmail_pass to snapraid_runner_email_pass.


Function process_withdrawals in beacon-chain.md may skip withdrawable validators for one sweep

While reading the beacon-chain.md spec, I have come across something which seems slightly off. Not a serious issue, but the solution seems simple, so let me explain.
Problem
The new process_withdrawals function calls get_expected_withdrawals to get a list of expected withdrawals. Suppose that the input state is satisfying:

state.next_withdrawal_validator_index == 0
len(state.validators) == MAX_VALIDATORS_PER_WITHDRAWALS_SWEEP - 1
all validators are not partially or fully withdrawable

Note, this is one of many states which can trigger the behavior of "skipping" withdrawable validators.
In this state, get_expected_withdrawals returns the empty list and  process_withdrawals proceeds to the else case in the end of the function. The else case looks like
next_index = state.next_withdrawal_validator_index + MAX_VALIDATORS_PER_WITHDRAWALS_SWEEP
next_validator_index = ValidatorIndex(next_index % len(state.validators))
state.next_withdrawal_validator_index = next_validator_index

substituting for our concrete values, it looks like
next_index = 0 + len(state.validators) + 1
next_validator_index = ValidatorIndex(1)
state.next_withdrawal_validator_index = ValidatorIndex(1)

Now update the state as follows:

2 new validators are added to the end of state.validators, such that len(state.validators) == MAX_VALIDATORS_PER_WITHDRAWALS_SWEEP + 1
validator at index 0 becomes fully withdrawable.

Note that adding any number of validators >= 2 will trigger the "skipping" behavior.
Now call process_withdrawals again. It calls get_expected_withdrawals, which returns the empty list again, since it starts with validator index state.next_withdrawal_validator_index == ValidatorIndex(1), so processes all the MAX_VALIDATORS_PER_WITHDRAWALS_SWEEP number of validators at indices > 0.
This means that we have skipped the fully withdrawable validator at index 0. This validator will get processed next time  process_withdrawals is called, but it seems wrong that it was skipped in the first place.
Possible solution
I think the "skipping" of withdrawable validators can be avoided by changing the first line of the else case in function  process_withdrawals to
next_index = state.next_withdrawal_validator_index + min(len(state.validators), MAX_VALIDATORS_PER_WITHDRAWALS_SWEEP)

Suppose that the input state is satisfying:
state.next_withdrawal_validator_index == len(state.validators)

This can never happen, we use % len(state.validators) in the code.
So the max value that this can have is len(state.validators) - 1 in which case the substitution with our concrete values would render next_validator_index = ValidatorIndex(0) instead of 1.

This means that we have skipped the fully withdrawable validator at index 0. This validator will get processed next time process_withdrawals is called, but it seems wrong that it was skipped in the first place.

So the validator at index 0 will not be "skipped" with your notation in the next sweep because of the above.
However: the general phenomenom that we may skip withdrawable validators on sweeps happens, and that's a feature of having a bounded sweep. There's no need to play with the modularity of the number of validators in the state: simply if no validator is withdrawable in one slot, and the sweep is set to start at validator x + 1, if validator x becomes withdrawable, it will take about 5 days to reach it.

This can never happen, we use % len(state.validators) in the code.

Right, changing the assumption to state.next_withdrawal_validator_index == 0 works with in the example as well. It causes the validator at index 0 to be "skipped", I think.
The reason I say the validator 0 is skipped, is that I would expect that validator to be processed in the second sweep, since we processed all validators in the previous sweep, so should start from index 0 in the second sweep in the example.

Intuitively: not starting from index 0 in the second sweep breaks the clock, since we wrap around the clock first, but then skip index 0 and start the next iteration of the clock from index 1. Does that make sense?

Intuitively: not starting from index 0 in the second sweep breaks the clock, since we wrap around the clock first, but then skip index 0 and start the next iteration of the clock from index 1. Does that make sense?

Your "fix" doesn't fix this issue (which is non fixable) simply starting before shifts the problem whatever your starting point is, if the next validator that becomes withdrawable is one index before, it will be "skipped" in the next sweep

Suppose that state is a valid state and payload a valid payload, satisfying len(get_expected_withdrawals(state)) < MAX_WITHDRAWALS_PER_PAYLOAD.
Let init_state = state.copy().
Let clock_ticks = len(state.validators).
Execute process_withdrawals(state, payload) and assume it does not throw an exception.
Now the question is which property is the most desirable.
The current property:
state.next_withdrawal_validator_index
  == (init_state.next_withdrawal_validator_index + MAX_VALIDATORS_PER_WITHDRAWALS_SWEEP) % clock_ticks

or the other property:
state.next_withdrawal_validator_index
  == (init_state.next_withdrawal_validator_index + processed_validators % clock_ticks

where processed_validators is the number of validators checked to be withdrawable
processed_validators = min(clock_ticks, MAX_VALIDATORS_PER_WITHDRAWALS_SWEEP))

I honestly think this is irrelevant, this only makes a difference if

there are less validators in the init state than MAX_VALIDATORS_PER_WITHDRAWALS_SWEEP which will arguably never happen on any network AND
the very next slot there are more validators in the state than MAX_VALIDATORS_PER_WITHDRAWALS_SWEEP, AND
one validator that was not withdrawable in the first slot became in the second and was right at the boundary

I say it's fine that under such circumstances such unlucky validator can wait 1 slot.


Import createVfm in main.ts throw error and browser too

Version
vue-final-modal: 4.0.6
vue: 3.2.42 => composition API
vite: 3.2.3
Reproduction Link

Steps to reproduce
Add VFM to main.ts, typescript throw error:

Then when a add ModalsContainer to app.vue, my browser thorw error:

I have same issue.  If check vfm instance, got undefined
import { useVfm } from 'vue-final-modal'
const vfm = useVfm() // undefined

Only created instance exist
const vfm = createVfm() // vfm-instance

Maybe some trouble with vfmSymbol
FYI: My project based on  vue-cli

There are two examples made with stackblitz and they works properly:
Vue 3: https://stackblitz.com/github/vue-final/vue-final-modal/tree/master/examples/vue3
Nuxt 3: https://stackblitz.com/github/vue-final/vue-final-modal/tree/master/examples/nuxt3
Please checkout if you register vue-final-modal correctly base on these two examples.
If it's still not working, please provide a reproduction like stackblitz or codesandbox.

I have the same problem. I've deleted the yarn.lock file in my case and I got rid of dynamicModals component


I want to extract clips from videos? How should I do? Thanks

Not sure what you are intending to do. It sounds out of the scope of our repo.
Take a look at the code to download Kinetics dataset. It has a function to trim videos with ffmpeg.
I remember other PRs for clipping.
All the best and thanks for pushing the limits of video understanding with our repo.


Implementation Request : Revisit Long Short-Term Memory

Revisit Long Short-Term Memory: An Optimization Perspective has some interesting results on using steeper (parameterised) sigmoids to make the gates in LSTM more binary. I'll soon be submitting a PR to torch/nn with nn.PSigmoid which would be needed to implement this.

@Kaixhin Yeah that seems promising. We could add a switch to the LSTM to use PSigmoid.


Add JS to calculate arbitrary responsive embed aspect ratios

Why do we use the only 16by9 and 4by3?
It is possible to use a height (calculate padding-bottom for .embed-resposive with js), based on params  of the source (e.g. iframe height="xx") if params is specified?

Why do we use the only 16by9 and 4by3?

Actually there's also 21by9 and 1by1 now.
Why these specific ratios? Well, 1by1 is square, and the others are common aspect ratios for video and photo content; see https://en.wikipedia.org/wiki/Aspect_ratio_(image)

It is possible to use a height (calculate padding-bottom for .embed-resposive with js), based on params of the source (e.g. iframe height="xx") if params is specified?

What's your specific use case?

What's your specific use case?

E.g. codepen embed iframe (example).
It's not a video or image, but iframe.
Most embed-api for iframe contain width and height params (incl. youtube. vimeo, etc.)
With width all clear: we use 100%. But height may be excessive.
And we can use this value, if it specified, for calculate padding-bottom via js.
All the more so actually we can use only one aspect ratio (except some modifications).
For example, I use the wrap and add appropriate classes to the frame via js.

Ie, using the width and height from iframe params (if it specified), we can calculate aspect ratio and set appropriate value for .embed-resposive padding-bottom.
This allows set the correct aspect ratio dynamically based on content, rather than a fixed aspect ratio.

Why not provide an option via preprocessor? I'm using this mixin in a Sass project:
@mixin aspect-ratio($width, $height) {
	padding-top: ($height / $width) * 100%;
}

It's called from within a class, like so:
.embed-responsive-3by4 {
	@include aspect-ratio(3, 4);
}

And the corresponding markup uses it just like Bootstrap's prebuilt ones:

```

Why not provide an option via preprocessor?

The outcome of this solution (involving two values) will be again an fixed ratio.
My proposal is substitute $height and $width values from iframe params (for calculate real ratio) via js.

No plans to add any JS to tackle this in v4.


Basic wayland backend input

This implements pointer/keyboard input support for the wayland backend.
Touch is not supported yet in any way (cannot test it, probably not as important).
Axis support for pointers could also be improved and it does currently not handle the received keymap (there is no way to do it, xkbcommon would have to be handled by the library).
Due to the current pointer event api, pointer movement events are only handled relatively (not sure about this, should it use wlr_event_pointer_motion_absolute and just imagine some fake mm values?).

not sure about this, should it use wlr_event_pointer_motion_absolute and just imagine some fake mm values?)

Yes

Or could use real mm values based on the wl_output's size compared to our surface's size

Looks good. I would at least take care of absolute motion before this is merged.

So far as keymaps are concerned, leave that to me. I'll be doing some refactoring in that department later.

ok thanks for the input, am working on it.

Fixed most of the issues and made the pointer example work with it.
Does not recreate the input device on leaving the window (this would introduce some new complexity of how to manage input devices, it might be better to use some additional 'visible' flag or something).
The mm values are now just the width and height in pixels of the output, trying to compute it somehow
from the remote wayland output information can probably not be done in a reliable manner (we would have to know for sure on which remote output or window is displayed).
The current implementation of motion_absolute in the shared example compositor is far from perfect, it just assumes the x and y mm values are the pixels of the output. Doing this correctly would need to keep track of the current output in the compositors pointer state and then convert from mm values to pixel coordinates but this would probably need some further changes.

Sounds good for the time being. I'll spend some time working on improvements in this domain shortly. Thanks!


New version: Exodus v0.4.0

Registering package: Exodus
Repository: https://github.com/cmhamel/Exodus.jl
Created by: @cmhamel
Version: v0.4.0
Commit: c60ec9730e1023a1d5eea627451b1583d9f6f903
Git reference: HEAD
Description: A julia interface for accessing the ExodusII data format

[noblock]
looks like zulip is failing on a lot of PRs


Solved issue of filter search list

Search results for "af" will now show only countries with "af" at beginning of their name.

Now all possible search results will be shown in results list


Click automation refactoring (#239)

\cc @AlexanderMoskovkin @AndreyBelym

@VasilyStrelyaev check comments please

FPR

/r-

\r-

FPR

lgtm

/r-

@testcafe-build-bot \retest

@testcafe-build-bot \retest

@helen-dikareva  let's use some util functions from testcafe-hammerhead: https://github.com/DevExpress/testcafe-hammerhead/pull/459

@AlexanderMoskovkin  In this commit we're using testcafe-hammerhead 6.0.0
Let's use it in https://github.com/DevExpress/testcafe/pull/383

yeah, I've forgotten about this

lgtm
/cc @AndreyBelym

What's about https://github.com/DevExpress/testcafe/pull/387#discussion-diff-55019565?

I forget about this. Now it's done.

@testcafe-build-bot \retest

FPR

lgtm

please merge


Containerizing applications with runfiles

Currently there is no obvious way to containerize applications that require the runfiles trees to be persisted in the way that Bazel lays them out. This is required for applications that use language specific runfiles libraries to locate runfiles.
Currently rules_oci relies on rules_pkg to create the layers for the container but rules_pkg does not have the capability to package the runfiles trees.
See https://github.com/bazelbuild/rules_pkg/issues/579 for the issue on the rules_pkg side.

There's a demo at https://github.com/aspect-build/bazel-examples/tree/main/oci_python_image that I've found useful for packaging up runfiles into an OCI image with these rules, due to that bug you linked.
Based on the code there, I shortened the various files into a single rule and macro combo that is close enough to a drop-in replacement to the old rules_docker py_image. It's probably broken in some subtle way, so beware, but this could be re-purposed for other languages that need runfiles bundling:
load("@rules_oci//oci:defs.bzl", "oci_image")
load("@rules_pkg//:pkg.bzl", "pkg_tar")
load("@rules_pkg//:providers.bzl", "PackageFilegroupInfo", "PackageFilesInfo", "PackageSymlinkInfo")
load("@rules_python//python:defs.bzl", "PyInfo")

def _dest_path(ctx, root, file):
    """Get the required output path under the root, such that runfiles structure is preserved."""
    return root + "/" + (
        (ctx.workspace_name + "/" + file.short_path) if not file.short_path.startswith("../") else file.short_path[3:]
    )

def _py_oci_image_layer_impl(ctx):
    """
    Build a Python OCI image tar layer provider containing the binary, its runfiles (and therefore
    also the bundled Python executable itself).

    Derived from:
      - https://github.com/aspect-build/bazel-examples/blob/d1dd2310df5ed06343eb37cf699ced5551ac476f/oci_python_image/py_image_layer.bzl
      - https://github.com/aspect-build/bazel-examples/blob/d1dd2310df5ed06343eb37cf699ced5551ac476f/oci_python_image/workaround_rules_pkg_153/runfiles.bzl

    """

    # Prohibit relative roots
    if not ctx.attr.root.startswith("/"):
        fail("root path must start with '/' but got '{root}', expected '/{root}'".format(root = ctx.attr.root))

    # Get root directory for all runfiles
    default_info = ctx.attr.binary[DefaultInfo]
    runfiles_root = "/".join([
        ctx.attr.root,
        default_info.files_to_run.runfiles_manifest.short_path.rpartition("/")[0],
    ])

    # Map files into the tar and also search for the Python binary
    mapped_files = {}
    python_binary_file = None
    for file in default_info.default_runfiles.files.to_list():
        mapped_files[_dest_path(ctx, runfiles_root, file)] = file

        if file.path.endswith("/bin/python") or file.path.endswith("/bin/python3"):
            # TODO: do this a more sensible way
            python_binary_file = file

    # Map symlinks
    symlinks = []
    for symlink in default_info.default_runfiles.symlinks.to_list():
        symlinks.append([PackageSymlinkInfo(
            target = _dest_path(ctx, runfiles_root, symlink.target_file),
            destination = "/".join([runfiles_root, ctx.workspace_name, symlink.path]),
            attributes = {"mode": "0777"},
        ), ctx.label])

    for symlink in default_info.default_runfiles.root_symlinks.to_list():
        symlinks.append([PackageSymlinkInfo(
            target = _dest_path(ctx, runfiles_root, symlink.target_file),
            destination = "/".join([runfiles_root, symlink.path]),
            attributes = {"mode": "0777"},
        ), ctx.label])

    # Put entrypoint symlink to executable at deterministic location, such that we can reference it
    # in oci_image within macro
    symlinks.append((PackageSymlinkInfo(
        target = _dest_path(ctx, runfiles_root, default_info.files_to_run.executable),
        destination = ctx.attr.root + "/" + "entrypoint",
        attributes = {"mode": "0777"},
    ), ctx.label))

    # If we found a Python binary, symlink it into PATH such that it can be used by stub script
    # generated by py_binary.
    # This allows us to use py_oci_image with base images that contain no other Python interpreter
    # binary. This is also a QoL improvement such that a Python interpreter can quickly be started
    # in a container with `docker exec ... python`
    if python_binary_file != None:
        symlinks.append((PackageSymlinkInfo(
            target = _dest_path(ctx, runfiles_root, python_binary_file),
            destination = "/usr/local/bin/python",
            attributes = {"mode": "0777"},
        ), ctx.label))
        symlinks.append((PackageSymlinkInfo(
            target = _dest_path(ctx, runfiles_root, python_binary_file),
            destination = "/usr/local/bin/python3",
            attributes = {"mode": "0777"},
        ), ctx.label))

    # Build providers of tar structure
    return [
        PackageFilegroupInfo(
            pkg_dirs = [],
            pkg_files = [
                [PackageFilesInfo(
                    dest_src_map = mapped_files,
                ), ctx.label],
            ],
            pkg_symlinks = symlinks,
        ),
        DefaultInfo(files = default_info.default_runfiles.files),
    ]

_py_oci_image_layer = rule(
    implementation = _py_oci_image_layer_impl,
    attrs = {
        "binary": attr.label(
            mandatory = True,
            providers = [PyInfo],  # To ensure we only receive a py_binary or equivalent
        ),
        "root": attr.string(
            mandatory = True,
        ),
    },
)

def py_oci_image(name, binary, root = "/opt", **kwargs):
    """
    Build an oci_image from a py_binary target.

    Args:
      - binary: The py_binary target label.
      - root: The root directory to use as a base for the files within the container.
      - **kwargs: All other args are forwarded to oci_image.
    """

    # Build a tar layer containing the py_binary runfiles
    _py_oci_image_layer(
        name = "_{}/runfiles".format(name),
        binary = binary,
        root = root,
        tags = kwargs.get("tags", None),
    )

    pkg_tar(
        name = "_{}/layer".format(name),
        srcs = [
            "_{}/runfiles".format(name),
        ],
        tags = kwargs.get("tags", None),
    )

    # Build image with sensible defaults
    env = {
        "LANG": "C.UTF-8",  # http://bugs.python.org/issue19846
    }
    env.update(kwargs.get("env", {}))
    oci_image(
        name = name,
        tars = ["_{}/layer".format(name)],
        entrypoint = kwargs.get("entrypoint", [root + "/entrypoint"]),
        env = env,
        **{k: v for k, v in kwargs.items() if k not in ["env", "entrypoint"]}
    )

this is fixed both in rules_pkg and https://github.com/aspect-build/bazel-lib/blob/main/docs/tar.md. Closing as there's no action to be taken here.

For future readers:
The rules_pkg fix needs https://github.com/bazelbuild/rules_pkg/pull/754 in the release. As the time of writing rules_pkg was at 0.9.1 released on May 2.


refactor(ES6): TestCases.test.js

What kind of change does this PR introduce?
refactor, ES5 => ES6

Did you add tests for your changes?
All existing tests pass

If relevant, link to documentation update:
N/A

Summary
Refactor TestCases.test.js to ES6

Does this PR introduce a breaking change?
No

Duplicate of [#4051]?(https://github.com/webpack/webpack/pull/4051)

Thanks