Just curious

Is there some special reason why you use bracket notation this["re"] instead of dot notationthis.re to access properties? I find the latter easier to read.

Yep, I like the latter also more, but I set these on all the attributes I want to keep as they are, when they run through closure compiler in advanced mode. I started to use the advanced mode for all my projects and so I rename the attributes after finishing a project to the bracket version. This is only a little tradeoff compared to the things closure compiler brings in advanced mode, like function inlining, and code rewriting in a more optical way.

Ah, does closure compiler mangle the property names too?! hm, that's not nice. I didn't know that

Yep, closure compiler tries to minimize them (1-2 chars) if they are not getting exported. By using this explicit syntax, you can mark them as an api. It also tries to remove objects at all. For example the P object, you don't like - if the compiler sees this object has constantly 2 attributes, it will make two variables of it (I'm not sure if in the case of P this really happens, but it tries to flatten internal objects)

Well, it makes sense of course - mangling internal variable names. But it's not handy debuging in this case, you want to see re and im.
As for P being replaced by two variables - that actually sounds like a good idea - it's just internals and will probably improve performance :D

I think not performance, as the lookup mechanism of v8 is quite advanced with it's hidden classes. Closure compiler tries to optimize for gzip, meaning building a lot of similar chunks of code, which at the end benefits performance as performance in the web means loading time.


Add hability to include/exclude the files to parse

Issue Type: Feature Request
VS code currently offers the possibility of excluding/ignoring files/dirs from being shown on the UI or from search results. However all the files found in a project are unconditionally parsed. That might be a problem in large projects, like Chromium or WebKit for example.
In those code bases there are a huge amount of files/directories that should not be parsed from the Web engine developer POV, for example most of the HTML/JS tests, most third party libraries or even large portions of the engine which are barely inspected and/or touched by the engine developer.
The parsing happens relatively fast even for those projects (order of seconds not minutes), however it'd be nice to have the possibility to restrict it to a selected group of directories. That initial parsing would be faster but also the intellisense engine would work much more faster and would provide much better results.
Does it make sense?
VS Code version: Code 1.33.0 (0dd516dd412d42323fc3464531b1c715d51c4c1a, 2019-04-04T15:08:57.775Z)
OS version: Linux x64 4.19.0-4-amd64

This is up to each extension / language provider. Please file issues against whatever extension are causing problems


Remove handlebar dependency

The handlebar file is currently not minified, and in the repo.
The PR to fix this issue should remove the dependency entirely, or at least update the file with a minified version.

Hi I am interensted in this

I'm nearly done with this issue, so I'll be closing it out soon.

Hi I am interensted in this

I'm nearly done with this issue so I'll be closing it out soon.

Fixed in #10


README.md update

Updated official website URL in README.md file and in about section.
Fixes Issue: #192
Screenshots

Current

README.md Update

LGTM

LGTM

Thanks ☺


chore: bdd-nh-1585821691 to 0.0.1

chore: Promote bdd-nh-1585821691 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


🐛  PaneItemHeader cash on compact menu. Menu scroll bar doesn't work dragging just with mouse scroll

Hi guys. When adding a PanelItemHeader and setting the menu to compact, opening an option causes the flyout window to crash. The scroll bar of the menu does not work either if you want to drag with the mouse pointer.

For the scrollbar, see #472


Updates on func tests

This PR ease adding new functionnal tests.

Codecov Report

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

@@          Coverage Diff          @@
##           master    #27   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           5      5
  Lines         250    250
=====================================
  Hits          250    250

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 739a591...c66be55. Read the comment docs.


PHPORM-172 Add test on updateOrCreate

Fix PHPORM-172
Fix #2903
I could not reproduce the issue. This test ensure we don't have regression.
Checklist

[x] Add tests and ensure they pass
[x] Add an entry to the CHANGELOG.md file
[x] Update documentation for new features

@ithuis @CaNCaNCode test updated with a criteria using a non-fillable field.


Fix the spec for users

Summery

Need o fix users specs in details

Basic Example

index spec and role based

Motivation

Better for debugging later

fixing daily before 30th September


Loading into PowerShell 5.1 (.Net Framework) environment fails with version 5.2 but works with 5.1.5

Describe the bug
When loading the Microsoft.Data.SqlClient assemblies into PowerShell 5.1, it fails on version 5.2 but works with version 5.1.5.
It fails with the error:
Exception message:  The type initializer for 'Microsoft.Data.SqlClient.SqlConnection' threw an exception.
Stack trace:
 System.TypeInitializationException: The type initializer for 'Microsoft.Data.SqlClient.SqlConnection' threw an exception. --->
                        System.TypeLoadException: Could not load type 'System.Runtime.Loader.AssemblyLoadContext' from assembly 'System.Runtime.Loader, Version=<IP_ADDRESS>,
                        Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
                           at Microsoft.Data.SqlClient.SqlDiagnosticListener..ctor(String name)
                           at Microsoft.Data.SqlClient.SqlConnection..cctor()
                           --- End of inner exception stack trace ---
                           at Microsoft.Data.SqlClient.SqlConnection..ctor()
                           at Microsoft.Data.SqlClient.SqlConnection..ctor(String connectionString)

Here are the results from $PSVersionTable
PSVersion                      5.1.19041.4291
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.4291
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

To reproduce
Include a complete code listing (or project/solution) that we can run to reproduce the issue.
Partial code listings, or multiple fragments of code, will slow down our response or cause us to push the issue back to you to provide code to reproduce the issue.
#Launch Windows PowerShell (version 5.1, 64bit)
#Download the nuget package and extract the x64 version of the dlls (or create a sample project and compile against win-64)
#In the directory where the DLLs are, run this

#Will fail for 5.2; will succeed for 5.1.5
Add-Type -Path .\Microsoft.Data.SqlClient.dll

Expected behavior
The DLL will load properly.
Further technical details
Microsoft.Data.SqlClient version: 5.2
.NET target: .NET Standard (but fails on .NET framework
SQL Server version: any
Operating system: Windows 10

@mithrandyr we will look into this and will get back to you.

@mithrandyr I have investigated this issue  However, I was not able to reproduce the issue.
These are the steps taken to try to reproduce the issue:

Created a console app targeting .Net Framework 4.8.1 (since Powershell is using .Net Framework)
Added package MDS 5.1.5
Compiled the app.
Started powershell and changed directory to the bin\debug folder of the console app
Run the Add-Type -Path .\Microsoft.Data.SqlClient.dll command.

The dll loaded without issue.
Repeat from step 2 above but reference MDS 5.2.0 instead. The dll loaded without issue as well.
This is the version of pwershell used:
Name                           Value

PSVersion                      5.1.22621.2506
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22621.2506
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

@mithrandyr this issue has been stale for a while, can you confirm if the steps mentioned above solve the issue for you?

Closing as inactive


missing type-error with enums returned from functions

this does not produce an error-message:
type Bit = 'zero' | 'one';

function getOne():Bit {
  return 'one';
}

const b1 = getOne();

if (b1 === 'wrong') {
  console.log('.');
}

this does produce an error-message:
type Bit = 'zero' | 'one';

function getOne():Bit {
  return 'one';
}

const b1:Bit = getOne();

if (b1 === 'wrong') {
  console.log('.');
}

why is there no error-message in the first case? the only difference is that in the second case i explicitly annotate b1 to be of type Bit. but it is of type Bit in the first case too, because the function getOne returns a value of type Bit. so why no error-message?
(to be clear: i think we should get an error-message in both cases)

In the first example, the type of b1 is inferred to be string,
simply because this is required to make the following code type-check.
That’s just a consequence of how inference works.
The implicit upcast in the initialization of b1 is valid because Bit
is a subtype of string.

thanks for the explanation, but is there anything that can be done to improve the situation?
in my case i had a typo in the string, so i had something like
const b1 = getOne();

if (b1 === 'zero') {
    // do something
    return;
}

if (b1 === 'oneeee') {
   // do something else
   return;
}

throw new Error('unreachable');

as you see, i had a typo in the "one" case. and when i found the bug i was wondering why flow did not catch the problem. is there perhaps some different pattern i should use?

Yes. You should ask Flow to verify that you have handled all cases by
using an empty-type assertion:
// @flow
type Bit = "zero" | "one";
declare function getOne(): Bit;

function f() {
  const b1 = getOne();
  if (b1 === "zero") {
    // do something
    return;
  }
  if (b1 === "oneee") {  // whoops!
    // do something else
    return;
  }
  (b1: empty);  // error! (good!)
  throw new Error("unreachable");
}

In the above code, Flow raises the helpful error,

Cannot cast b1 to empty because string literal one is incompatible
with empty.

indicating that we have forgotten the case one. Replacing oneee with
one in the guard properly fixes the error.
This protects you both now and in the future. If you add another case to
the type Bit, then Flow will raise an error here to indicate that you
need to handle the new case.
Personally, I usually write throw new Error((b1: empty));, which
includes both the static check and the dynamic check, and encodes the
problematic case into the error message.

The issue was fixed a while ago.


Fix html formatting for exceptions and errors

Fix #4533
Description
Changed the order of nl2br and esc
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPdocs
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[ ] Conforms to style guide

Thank you @musmanikram

@samsonasik always try to add my 2 cents 😊


Define Breakpoints

Overview
Define the breakpoints that we want to use for responsive design. We'll implement this into our component library theme and also tap into it with #229 to create responsive layouts.
Details

What do we want to set for each breakpoint? We can specifically think of the device or more generally like Chakra does:

const breakpoints = {
  sm: '30em',
  md: '48em',
  lg: '62em',
  xl: '80em',
  '2xl': '96em',
}

Can also map to the Chrome Dev Tools breakpoints, but this may be a bit too much. This is referenced in this article.

const size = {
  mobileS: '320px',
  mobileM: '375px',
  mobileL: '425px',
  tablet: '768px',
  laptop: '1024px',
  laptopL: '1440px',
  desktop: '2560px'
}

@oovg tagging you in this one since it came up during Planning today

@jonathanprozzi let's add the details about what breakpoints are needed and get it ready for design

xs - phone - maxWidth: 480px
sm - tablet - maxWidth: 768px
md - desktop - maxWidth: 1024px
lg - large desktop - maxWidth: 1200px
xl - xl screens - minWidth: 1201px


TravisCI build failing for Python 3.7-dev

This is due to PyYAML:
https://github.com/yaml/pyyaml/issues/126

Good news: PyYAML 4.1 has been released which now installs successfully on Python 3.7:
https://github.com/yaml/pyyaml/issues/126#issuecomment-400679908

Thanks ! Issues solved


script tag attributes in html

Would it make sense to add the async and defer attributes to (some of) the script tags in the main index.html?

I was using the setTimeout(function() {}, 0) to initialize in docsify. It's effect is the same as the async attribute, so you do not have to do anything.


05-hook: Add an example

Hooks episode could use at least one example (preferably not esoteric).  I don't know any good ones offhand, though.

Well, we use these in the testing session.

Well, we use these in the testing session.

Agreed, but we introduce them here and introduction by examples is
easier than introduction by abstract concepts... the presenter usually
has to come up with some examples to say here anyway.

Two examples to mention (and we mention many examples on that page):

auto-formatting before committing
running test set before committing

True, perhaps this isn't needed (I just copied the issue from the
paper I used to note stuff down during the workshop).  I can't exactly
explain it, but I feel that there should be some simple actual
code/repository example that can be shown... which is actually easier
said than done...


Add menu items for "winget list" and "winget upgrade".

These would help people not have to use the command-line as much, though they may still have to type some stuff.

Eventually there could be a way to have a "Mark all upgrades" button that uses winget upgrade to get the list of upgrades, then it marks those packages with the "Upgrade" action. The "Mark all upgrades" text is from Synaptic, but I think it would work ok here, too.

These menu items have been added, being Package list>Show available upgrades in winget and Package list>List installed packages in winget. These menu items require having the related experimental options on, but they'll probably be on by default by the time this version is out.


How do I run a query?

This is great, I don't have to spend time setting up dependencies when running random queries. But I haven't been able to run it.
After setting up my connection settings on my json config
    "rethinkdbExplorer.host": "localhost",
    "rethinkdbExplorer.port": 29025,
    "rethinkdbExplorer.database": "something",
    "rethinkdbExplorer.username": "theTopDogUser",
    "rethinkdbExplorer.password": "AVeryApproppriateAndLongAndExhaustingPassword01",
    "rethinkdbExplorer.tls": false

How do I run a query after pasting it on the new file?
r.tableList()
I tried cmd + alt + p and `rethinkdb but I don't get a choice to run that

Cheers!
Claudio

@claudiordgz Two way: One is ctrl+shift+r or cmd+shift+r for mac. The second is a small button in the status bar -

thank you @calexander3!


Added Istio installation and modified bookinfo

I addressed the code review comments, PTAL.

Sorry I was a bit late. I added a bunch of comments as well.

That link will not be there until official alpha release. But cloning from
master will always be there. The fact that people won't have git client is
precisely the reason why I was insisting on downloading archives. No curl,
no git. :).
On Fri, Apr 21, 2017 at 5:30 PM Andra Cismaru<EMAIL_ADDRESS>wrote:

@andraxylia commented on this pull request.
In docs/samples/bookinfo.md
https://github.com/istio/istio.github.io/pull/45#discussion_r112780471:

Bring up the application containers:

kubectl create -f <(istioctl kube-inject -f bookinfo.yaml)

+```bash
+kubectl apply -f <(istioctl kube-inject -f <(\

curl -s https://raw.githubusercontent.com/istio/istio/master/demos/apps/bookinfo/bookinfo.yaml

))
+```
I changed it because some people may not have github or know how to clone
our repo. And I see your point related to downloading from master. It
should be fine if for alpha we will provide an archive with the files. I
will change the instructions to “download and unpack the installation
files(link) or clone the repository.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio.github.io/pull/45#discussion_r112780471,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH0qd9_O7ujZrntJoJPVBHwpNcB4VpFuks5ryR__gaJpZM4NEmY4
.

--
~shriram

I will add the link to the future archive, so when time comes, we will only need to add the file and not change the doc site. Archive location will be in /releases/istio-alpha.gzip.

.tar.gz and .zip. Those are the formats that GH automatically creates iirc.
On Fri, Apr 21, 2017 at 5:43 PM Andra Cismaru<EMAIL_ADDRESS>wrote:

I will add the link to the future archive, so when time comes, we will
only need to add the file and not change the doc site. Archive location
will be in /releases/istio-alpha.gzip.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio.github.io/pull/45#issuecomment-296312380,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH0qd82aR3lsEjHrY4k9QKKIxR0Fp7lLks5rySMKgaJpZM4NEmY4
.

--
~shriram

Addressed @rshriram 's comments, PTAL.

I addressed all comments, but I still want to get rid of sourcing istio.VERSION. PTAL.

yes. and move files to _docs/samples/bookinfo.md and _docs/tasks/istio-installation.md


Change bots language

Hello! Didnt find any info about the ability to change the language and messages text.
Where should i start&

You can change messages text here: https://github.com/OfficeDev/microsoft-teams-apps-icebreaker/blob/main/Source/Icebreaker/Properties/Resources.resx

@SubbaReddi does this require rebuilding the solution? We made changes to Resources.resx but this didn't seem to make a change to Resources.Designer.cs after redeploying. Only after making changes in this file did we see the changes in the responses. Thanks!

When does Resgen.exe get run? During Azure deployment?

@SubbaReddi thanks a lot! read all over the documentation but did not find it:)

Sorry @gavindavies, i've re-opened issue now

@shashishailaj , @gavindavies : You can change text in Resources.resx, rebuild project and deploy the updated solution to app service.

@SubbaReddi does the build process happen as part of the deployment to Azure? or do you have to open the solution in VS and build there?

Open solution in VS and build.


Adding lambda destinations when provisioning functions

Coverage Report

Totals

Statements:
96.4% ( 4261 / 4420 )

Methods:
93.13% ( 149 / 160 )

Codecov Report

Merging #22 (224b21f) into main (19d77d9) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #22   +/-   ##
=======================================
  Coverage   96.39%   96.40%
=======================================
  Files          27       27
  Lines        4413     4420    +7
  Branches      291      291
=======================================
+ Hits         4254     4261    +7
  Misses        159      159

Impacted Files
Coverage Δ

src/lib/construct/graphQLApiLambda.ts
94.20% <100.00%> (ø)

src/lib/construct/siteWithEcsBackend.ts
97.98% <100.00%> (ø)

src/lib/construct/staticSite.ts
96.47% <100.00%> (ø)

src/lib/manager/aws/lambdaManager.ts
100.00% <100.00%> (ø)

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 19d77d9...224b21f. Read the comment docs.


Showcase Submission for challenges/24-perlin-noise-flow-field

Thank you NAGESH M H for your contribution! A member of the Coding Train team will review it shortly.

Clock + Vector Flow Field
NAGESH M H

beautiful!


Not possible to decode resources while decompiling Facebook lasted APK

Not sure I'm a fan of this patch. Are style2/3/4/5/6 real resource types? Or just fabricated and created by Facebook? Could it go up to 10? 20? 100? I think we need to properly research this, but thanks for the start!

It can go more then 3-4-5... I am currently dealing with an apk that has style12 resources as well and the interesting part is, you can't assume they are normal style resources. No matter how many handlers you add for style[number], it will not compile properly.
I'm not sure which problem this PR actually fixes.

Sorry meant to close this yesterday. I don't think this is the correct method to resolve this issue, but I thank you for making an attempt.

Review PR https://github.com/iBotPeaches/Apktool/pull/2293

He had not had time to review this until today.


create a series of affordances demonstrations, like a tutorial

For level designers, and players, create a series of Level scenes in which the player must demonstrate one ability or concept.

move.
jump over this thing
kick this thing
double jump to get to a thing
toggle a switch
navigate past some traps
lure an enemy into a trap
fight a mannequin
fight a live enemy
fight a strong enemy in a room with traps

Each scene should have very brief instruction (sign on wall) explaining the exercise.

seems complete


Add "Clean Up User Notebook" keyword

This keyword deletes all files and folders in a user's notebook PVC (excluding hidden files and folders).
It will be useful to fix test teardown in ODS-517 in PR #102, as regular "Clean Up Server" fails
to do the job because the PVC is full for that test.
Signed-off-by: Jorge Garcia Oncins<EMAIL_ADDRESS>

:+1:

Looks good to me, just a bit scared about the find command :)

Tested here: https://opendatascience-jenkins-csb-rhods.apps.ocp-c1.prod.psi.redhat.com/job/rhods-ci-pr-test/141/
3 JupyterHub tests failed for not related reasons
About the find command, I think it's safe (the list of deleted files is written in the log) but  as it is a new keyword I was thinking of using it initially only in test ODS-517. If it works well in the future maybe we can use it in Common.End Web Test


When using raw_post and Content-Type application/json rspec errors out

Failure/Error: Unable to find matching line from backtrace
 ActionDispatch::ParamsParser::ParseError:
   795: unexpected token at 'grant_type=client_credentials&client_id=d512debf7d49186443ebc27b1f50308939618859dfb37717d4b6fe2b403ae759&client_secret=50e820e5eb5a0b684112cf074cb752df799ebf7f204cd8f60dcb97377a11bddc'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.1.0/lib/action_dispatch/middleware/params_parser.rb:53:in `rescue in parse_formatted_parameters'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.1.0/lib/action_dispatch/middleware/params_parser.rb:32:in `parse_formatted_parameters'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.1.0/lib/action_dispatch/middleware/params_parser.rb:23:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.1.0/lib/action_dispatch/middleware/flash.rb:254:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:225:in `context'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:220:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.1.0/lib/action_dispatch/middleware/cookies.rb:560:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.1.0/lib/active_record/query_cache.rb:36:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/activerecord-4.1.0/lib/active_record/connection_adapters/abstract/connection_pool.rb:621:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.1.0/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.1.0/lib/active_support/callbacks.rb:82:in `run_callbacks'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.1.0/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.1.0/lib/action_dispatch/middleware/remote_ip.rb:76:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.1.0/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.1.0/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/railties-4.1.0/lib/rails/rack/logger.rb:38:in `call_app'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/railties-4.1.0/lib/rails/rack/logger.rb:20:in `block in call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.1.0/lib/active_support/tagged_logging.rb:68:in `block in tagged'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.1.0/lib/active_support/tagged_logging.rb:26:in `tagged'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.1.0/lib/active_support/tagged_logging.rb:68:in `tagged'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/railties-4.1.0/lib/rails/rack/logger.rb:20:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.1.0/lib/action_dispatch/middleware/request_id.rb:21:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rack-1.5.2/lib/rack/methodoverride.rb:21:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rack-1.5.2/lib/rack/runtime.rb:17:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/activesupport-4.1.0/lib/active_support/cache/strategy/local_cache_middleware.rb:26:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/actionpack-4.1.0/lib/action_dispatch/middleware/static.rb:64:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rack-1.5.2/lib/rack/sendfile.rb:112:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/honeybadger-1.16.5/lib/honeybadger/rack/error_notifier.rb:43:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/honeybadger-1.16.5/lib/honeybadger/rack/user_feedback.rb:24:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/honeybadger-1.16.5/lib/honeybadger/rack/user_informer.rb:13:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/railties-4.1.0/lib/rails/engine.rb:514:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/railties-4.1.0/lib/rails/application.rb:144:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rack-test-0.6.3/lib/rack/mock_session.rb:30:in `request'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rack-test-0.6.3/lib/rack/test.rb:244:in `process_request'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rack-test-0.6.3/lib/rack/test.rb:67:in `post'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec_api_documentation-4.3.0/lib/rspec_api_documentation/rack_test_client.rb:38:in `do_request'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec_api_documentation-4.3.0/lib/rspec_api_documentation/client_base.rb:42:in `process'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec_api_documentation-4.3.0/lib/rspec_api_documentation/client_base.rb:16:in `post'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec_api_documentation-4.3.0/lib/rspec_api_documentation/dsl/endpoint.rb:58:in `do_request'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec_api_documentation-4.3.0/lib/rspec_api_documentation/dsl/endpoint.rb:16:in `block in example_request'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/example.rb:148:in `instance_exec'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/example.rb:148:in `block in run'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/example.rb:208:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/example.rb:208:in `block (2 levels) in <class:Procsy>'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-rails-3.0.1/lib/rspec/rails/adapters.rb:68:in `block (2 levels) in <module:MinitestLifecycleAdapter>'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/example.rb:292:in `instance_exec'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/example.rb:292:in `instance_exec'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/hooks.rb:430:in `block (2 levels) in run'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/example.rb:208:in `call'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/example.rb:208:in `block (2 levels) in <class:Procsy>'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/hooks.rb:428:in `run'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/hooks.rb:485:in `run'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/example.rb:301:in `with_around_example_hooks'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/example.rb:145:in `run'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/example_group.rb:494:in `block in run_examples'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/example_group.rb:490:in `map'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/example_group.rb:490:in `run_examples'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/example_group.rb:457:in `run'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/example_group.rb:458:in `block in run'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/example_group.rb:458:in `map'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/example_group.rb:458:in `run'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/runner.rb:112:in `block (2 levels) in run_specs'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/runner.rb:112:in `map'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/runner.rb:112:in `block in run_specs'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/reporter.rb:54:in `report'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/runner.rb:108:in `run_specs'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/runner.rb:86:in `run'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/runner.rb:70:in `run'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/lib/rspec/core/runner.rb:38:in `invoke'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/gems/rspec-core-3.0.0/exe/rspec:4:in `<top (required)>'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/bin/rspec:23:in `load'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/bin/rspec:23:in `<main>'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/bin/ruby_executable_hooks:15:in `eval'
 # /usr/local/rvm/gems/ruby-1.9.3-p551/bin/ruby_executable_hooks:15:in `<main>'
 #
 #   Showing full backtrace because every line was filtered out.
 #   See docs for RSpec::Configuration#backtrace_exclusion_patterns and
 #   RSpec::Configuration#backtrace_inclusion_patterns for more information.

I am trying to pass a fairly large json hash to a post method.  The tests pass when I don't set the Content-Type, but if it is set I get the above error.  I would like to set the content type to json so that the output documentation can include that the body needs to be json.  Any help would be appreciated.  If you need to see my code let me know and I will post something.  Sorry for the very long stack trace.

For anyone that is having this issue in the future.  Whenever you pass params to raw_post, and set the content-type to application/json you have to call #to_json on the params that you pass.


ifcfg.default_interface() is None

Describe The Problem
When starting the dashboard I get the following errors message:
./wgd.sh debug
------------------------------------------------------------
[WGDashboard] Starting WGDashboard in the foreground.
Traceback (most recent call last):
  File "/opt/wgdashboard/src/dashboard.py", line 1412, in <module>
    DashboardConfig = DashboardConfig()
                      ^^^^^^^^^^^^^^^^^
  File "/opt/wgdashboard/src/dashboard.py", line 1121, in __init__
    "remote_endpoint": ifcfg.default_interface()['inet'],
                       ~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^
TypeError: 'NoneType' object is not subscriptable
------------------------------------------------------------

To Reproduce
I also just launched a python interpreter and executed the following:
python3
Python 3.11.2 (main, Aug 26 2024, 07:20:54) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import ifcfg
>>> print(ifcfg.default_interface())
None

Not sure how ifcfg determines a default interface but it doesn't seem to work always.
OS Information:

OS: Debian 12
Python Version: 3.11.2

This works as a workaround
diff --git a/src/dashboard.py b/src/dashboard.py
index fca6bc0..5cbd83c 100644
--- a/src/dashboard.py
+++ b/src/dashboard.py
@@ -1118,7 +1118,7 @@ class DashboardConfig:
                 "peer_global_DNS": "<IP_ADDRESS>",
                 "peer_endpoint_allowed_ip": "<IP_ADDRESS>/0",
                 "peer_display_mode": "grid",
-                "remote_endpoint": ifcfg.default_interface()['inet'],
+                "remote_endpoint": ifcfg.default_interface()['inet'] if ifcfg.default_interface() else '',
                 "peer_MTU": "1420",
                 "peer_keep_alive": "21"
             },

Will add this workaround to the fix

Fixed in v4.0.3. Thanks to @tbnobody providing the fix.


Check Please ....

Hi,
How are you?
I am using your davbackup and it's awesome. You made a great class that helped me a lot. Thanks to you for your work.
I need some information  from you....
I want to use the .rar extension and in your class you mentioned about the .rar extension and there need an another class from https://github.com/dmamontov/rararchiver
Can you please tell me that how can I integrate this class with your class that you made https://github.com/dmamontov/davbackup
and one more thing ... In your class you managed the database export system in .sql formate. If I want to use another system like(.zip, .gzip).... is it possible ??
Hope that you will got my point.... Waiting for your reply and Thanks again :) :) :)

Good afternoon! All is well!
To work with rar required by composer set 2 libraries:
composer require dmamontov/davbackup ~1.1.0
composer require dmamontov/rararchiver ~1.0.0

The class is not intended to form the base of a compressed dump. If you need this functionality. I can add. But in this case it will not work on servers where prohibited exec.

Thanks, I will try to set 2 libraries.
and one more thing ... In your class you managed the database export system in .sql formate. If I want to use another system like(.zip, .gzip).... is it possible ??
Waiting for your reply and Thanks again :) :) :)


STORM-2327 ConfigurableTopology

Squashed #1897 into a single commit.
@HeartSaVioR

+1

Thanks @HeartSaVioR


Passing custom properties to document returns Typescript error

I'm using the document-internationalization plugin from Sanity, which requires the inclusion of a i18n boolean property on all documents I want to have internationalization support for. It looks like this:
s.document({
  name: 'about',
  title: 'About',
  i18n: true, // ts error
  ...
})

But it's throwing me the following Typescript error:

Argument of type '{ name: "about"; title: string; i18n: boolean; preview: { prepare: () => { title: string; }; }; groups: { name: string; title: string; }[]; fields: [{ name: "hero"; title: string; group: string; type: SanityType<{ type: string; ... 10 more ...; fieldsets?: FieldsetDefinition[] | undefined; }, { ...; }, { ...; }, { ....' is not assignable to parameter of type '{ description?: string | ReactElement<any, string | JSXElementConstructor> | undefined; title?: string | undefined; options?: DocumentOptions | undefined; ... 17 more ...; preview?: Preview<...> | undefined; }'.
Object literal may only specify known properties, and 'i18n' does not exist in type '{ description?: string | ReactElement<any, string | JSXElementConstructor> | undefined; title?: string | undefined; options?: DocumentOptions | undefined; ... 17 more ...; preview?: Preview<...> | undefined; }'.ts(2345)
(property) i18n: boolean

Not sure if there is a better way for this, as this (and the way above with the typescript error), won't actually generate the fields you'll get from the internationalization plugin anyways
__i18n_lang:en
But an easy way to avoid the error, other than adding /* @ts-expect-error Document Internationalization */ above the error
is to add the field manually wherever you're exporting the schema into your sanity config.
export const schema: { types: SchemaTypeDefinition[] } = {
  types: [{...home.schema(), i18n: true}, settings.schema()],
}

That'll do for now @ehwarren. I created a function for this, although it would be nice to still see native support for this. Here's my function until then:
import type { SchemaTypeDefinition } from 'sanity';

import shared from './shared';
import references from './references';

import about from './about';
import blog from './blog';

const intl = (schema: SchemaTypeDefinition) => ({
  ...schema,
  i81n: true,
});

export const schemaTypes = [
  ...shared,
  ...references,
  intl(about.schema()),
  intl(blog.schema()),
];

I suppose these definitions could allow unrestricted indexed types to handle this. Honestly, not a huge fan of those, but the plugin nature of sanity might warrant it. Arguably, we might want to expose an easily overridable global type/interface that is s.document's parameter, just so we can find an easy way for plugins to mix in properly. This library is only recently coming out of "proof of concept" mode so I never considered accommodating plugins.
This is mostly a duplicate of https://github.com/saiichihashimoto/sanity-typed/issues/18. I'm going to rename this to have a short term solution before we focus too much on plugins.


Use parsed includeDefaultStyles instead of direct input

Ready for code review.
Fixes #1128 and #1115.

Great job, @kasparsd !

Is there a way to get this merged and published to NPM?

@kasparsd sorry for the delay but as @varya already mentioned we're looking for people who can maintain this project. Let us know if you're interested.

@junaidrsd Totally understand. Sure, I would love to help keep it updated and working.

@kasparsd Thank you. Great to hear that you want to contribute. I've invited you as a collaborator.


support Blob

https://github.com/github/fetch/blob/master/fetch.js#L128
Will need to run test suite in latest chrome

Fixed in https://github.com/wheresrhys/fetch-mock/pull/63


Documentation for Intelligent Document Service, Invoice Processing, Receipt Processing)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: saurabhkmx:white_check_mark: Luyao-Zhang-1:x: Saurabh KumbharSaurabh Kumbhar seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


docs(shields.io): add logos to badges

Coverage remained the same at 97.872% when pulling 5f68adb3cf20b7df89fb2ea7049dcac73b3356b4 on shield-icons into 326daef8b9ad3c5348f60fc305dd83aaa98d1c40 on master.


Reconfirmation is triggered again if email is set to current unconfirmed_email

Environment

Ruby 3.0.0
Rails <IP_ADDRESS>
Devise 4.7.3

Current behavior
user.email # =><EMAIL_ADDRESS>user.update(email<EMAIL_ADDRESS># => sends reconfirmation
user.update(email<EMAIL_ADDRESS># => sends reconfirmation again

Expected behavior
user.email # =><EMAIL_ADDRESS>user.update(email<EMAIL_ADDRESS># => sends reconfirmation
user.update(email<EMAIL_ADDRESS># => does not send reconfirmation again

background
We have a form and graphql API where users can edit all their attributes at once. When users change e.g. their name while they still have an unconfirmed_email, they unexpectedly get another confirmation mail. Our current workaround to prevent this is as follows:
new_attrs.delete(:email) if new_attrs[:email] == user.unconfirmed_email
user.update(new_attrs)

It definitely makes sense not to trigger another confirmation email if you're updating the model but not changing the email itself. I believe you are using/displaying the unconfirmed email in your form then? (based on the check you're doing to prevent the update of the email field?)

It definitely makes sense not to trigger another confirmation email if you're updating the model but not changing the email itself. I believe you are using/displaying the unconfirmed email in your form then? (based on the check you're doing to prevent the update of the email field?)


delayline() is called twice for every impulse response in ir_wfs()

This is a follow up on #115.
There @VeraE wrote that delayline() gets called several times:

when calculating the driving function,
in ir_correct_distance()

One way to improve this might be to let ir_correct_distance() return delay and weight instead of the actual shifted impulse response. The downside is that this would complicate how get_ir() works as this would then need to return the unmodified impulse response and the delay and weight. I guess in this case it would even be better to remove ir_correct_distance() from get_ir() and apply it somewhere else.
Maybe we find a good solution for this, but in my opinion it would be also ok, to stay with the current state.

The same problem applies to ssr_brs_wfs().

I would not want to change how get_ir() works either. But I have the following suggestion: The only delay that should be returned from ir_correct_distance() is the one that can be caused by delayline(), I think. So this should be returned from ir_correct_distance() to get_ir() to ir_generic() where it can be added to the delay returned by driving_function_imp_wfs(). What do you think?

Ah ok, now I see the real problem. I thought it was just a problem performance wise. But the problem is of course that delayline() can add a processing delay already inside ir_correct_distance(). So the only solution seems indeed to return that delay in ir_correct_distance() and pass it on.
I do not like that very much as it add a returning parameter to get_ir() that you would not expect there, but I have no better proposal at the moment.


[BUG]: Unable to cast uuid to a field

Report hasn't been filed before.

[X] I have verified that the bug I'm about to report hasn't been filed before.

What version of drizzle-orm are you using?
0.38.2
What version of drizzle-kit are you using?
0.31.1
Other packages
No response
Describe the Bug
Reopening https://github.com/drizzle-team/drizzle-orm/issues/1892
This issue still exists. My mistake was using drizzle push with mis matched integer/uuid ID fields. Had to wipe the database and start over to get around the error.
// Previous
export const folders = pgTable('folders', {
	id: integer('id')
		.primaryKey()
	name: text('name').notNull(),
	createdBy: integer('created_by').references(() => users.id),
	parentFolderId: integer('parent_folder_id').references((): AnyPgColumn => folders.id),
	...dateFields,
})

// Migrated to this,
export const folders = pgTable('folders', {
	id: uuid('id')
		.primaryKey()
		.$defaultFn(() => uuidv7()),
	shortId: varchar('short_id', { length: 21 })
		.notNull()
		.$defaultFn(() => createPrefixedNanoId('folder')),
	name: text('name').notNull(),
	createdBy: uuid('created_by').references(() => users.id), // pushed before changing integer to uuid
	parentFolderId: uuid('parent_folder_id').references((): AnyPgColumn => folders.id),
	...dateFields,
})

Warning  '@neondatabase/serverless' can only connect to remote Neon/Vercel Postgres/Supabase instances through a websocket
[✓] Pulling schema from database...
error: column "created_by" cannot be cast automatically to type uuid
  hint: 'You might need to specify "USING created_by::uuid".',

I came across same issue, what worked for me was deleting older migrations, no need to wipe entire database.
use npx drizzle-kit drop do delete migrations.

Closing in favor of #3322.


Need to define all Mage Arena II spawn locations

Currently there are likely some missing locations in the Mage Arena II quest. From the wiki, it looks like one near wilderness altar, and one near the Wilderness Volcano is missing.
The area that an NPC can spawn from it central spawn point is 14 squares in any direction. You can use this to work out the middle of its region by finding a corner of its spawn, then walking 14 squares diagonally to what will be the middle of the spawn region.

location submitted by user DaiChimpo on discord

There seems to be either a typo or a misrepresented location for the Demonic Ruins, see below.


redis get request timeout

I have set timeout parameter， however， redis get command will timeout anyway.

I have set read timeout is 2ms, pool timeout is 2ms, the data size is 4MB, however, the total cost of time is 111ms.

If read timeout is 2 ms and command takes 111 ms to complete - you get a read timeout. It is not clear what is the problem.


Is there a way to premine native tokens on the local Rootchain? How should one pay for gas costs?

Is there a way to premine native tokens on the local Rootchain?
Description
Before the introduction of Rootchain Stake Tokens, the ./polygon-edge rootchain fund command could be used to send native/gas tokens to addresses on the local rootchain. However, there doesn't seem to be a way to pay for gas fees over the local rootchain now.
When we run the ./polygon-edge rootchain server the local geth node has empty balance on all addresses without any premine. Let me know what can be done to pay for gas costs on the local rootchain.

In case you are using locally running rootchain (namely Geth instance in dev mode acting as a rootchain), you still should be able to run rootchain fund command.  Although it now has some additional flags, which are required.
Correct way to use it is the following:
./polygon-edge rootchain fund \
        --stake-token <address of stake token on the rootchain> \
        --mint \
        --addresses <addresses of the accounts that needs to be funded> \
        --amounts <funds in wei that are being sent to the accounts>

The stake token address is populated in the genesis.json by stake-manager-deploy command.

@Stefan-Ethernal the rootchain fund expects the rootchain-stake-token to de already deployed on the rootchain. However, the local rootchain does not have the option of premining / minting gas tokens to be used for contract deployment and transacting. Any solutions for premining / minting gas tokens on the local rootchain?
Let me know if I am missing something!
Regards.

hi, I am facing a similar issue ..
so the issue is I want to use one of my tokens from the root chain(Mumbai) as my gas token/native token of supernet. after successfully up and running my child chain/supernet and root chain. I added my chain to Metamask and it was not showing any funds, because I haven't pre-mined any funds and I want to bridge from the root chain.
here is the command I used
./polygon-edge bridge deposit-erc20 \
    --receivers 0xb1551B2b46df680E8e25E97232888a26ecdc01F5,0x3064825502cE1a5CA8D49EC9d53654b29B79eEBE \
    --amounts 100,100 \
    --root-token 0x13A2e16C0905e2CcFEE63Bf26EF859eBA3848D55 \
    --root-predicate 0x34040bdC008987Ed22659A3Df6D9cC0F88408938  \
    --json-rpc https://rpc-mumbai.maticvigil.com/ \
    --sender-key <my_private_key>

it gives the output

but when I am running my supernet again the funds are still 0 it is not showing.
what i am missing or my mistake ?

Hi @amansk2050  To solve your issue could you please explain

The steps you followed in setting up the Rootchain and Supernet.
Please mention the version of polygon-edge that you used
The addresses you used for --root-token  and --root-predicate 0x34040bdC008987Ed22659A3Df6D9cC0F88408938

@deepalt92
i am using polygon 0.9.0 version
here are the commands i used :
1. ./polygon-edge polybft-secrets --insecure --data-dir kaldi-chain- --num 4

2.

./polygon-edge genesis --block-gas-limit 10000000 --epoch-size 10 \
    --validators-path ./ --validators-prefix kaldi-chain- \
    --consensus polybft \
    --reward-wallet <address_of_any_validator_node>:1000000 \
    --name "kaldi-chain" \
    --burn-contract 100:0x3064825502cE1a5CA8D49EC9d53654b29B79eEBE \
    --native-token-config "Kaldicoin:KLDI:18"

--

3.
./polygon-edge rootchain deploy \
  --deployer-key <private_key> \
  --genesis ./genesis.json \
  --json-rpc https://rpc-mumbai.maticvigil.com/ \
  --erc20-token 0x13A2e16C0905e2CcFEE63Bf26EF859eBA3848D55 (token I going to use as native token)

-----

[ROOTCHAIN - CONTRACTS DEPLOYMENT] started... Rootchain JSON RPC address https://rpc-mumbai.maticvigil.com/.

[ROOTCHAIN - DEPLOY CONTRACT]
Name               = RootERC721
Contract (address) = 0x64F6B6Cc8658468042F4D6553D420aBD406B4089
Transaction (hash) = 0xde95965dd3a9dd13f34c6bd304d8b6bef18b75f42030a3930ac1b2b337fbe64f

[ROOTCHAIN - DEPLOY CONTRACT]
Name               = RootERC1155
Contract (address) = 0x3c15829b866B5bE6cBD688D0DB18227f4cBCCE0A
Transaction (hash) = 0xe6d2e3b01ff15d8223ea1fe33dec672576dfa44b6db2fd7713ec90d108cbd1e5

[ROOTCHAIN - DEPLOY CONTRACT]
Name               = StateSender
Contract (address) = 0x1DD69Ef23aC94640fA43AbD5376E4e58649caB7d
Transaction (hash) = 0x4a4d36928456afd91d4408f6a6127803cc39552bccff6ad0a361810caf046576

[ROOTCHAIN - DEPLOY CONTRACT]
Name               = CheckpointManager
Contract (address) = 0x6BC9BCdEdF1b62C947833e02aa0aed6D7B485F02
Transaction (hash) = 0x811323798069a4fb146a6f43c551bc3140fa55e5fa449b1873134af0a5370abb

[ROOTCHAIN - DEPLOY CONTRACT]
Name               = BLS
Contract (address) = 0xefcC845F0912CC4849fd87087Ea42Bb291284c60
Transaction (hash) = 0x9709a4043b396faa9c20d3564db31218dcd2200e8c18f0bd7bfb38eb1389b5a0

[ROOTCHAIN - DEPLOY CONTRACT]
Name               = BN256G2
Contract (address) = 0x21c8963b26C2c7dd7f666143A3D785880D797Be1
Transaction (hash) = 0x40185273cdbdcf681bbf9e068f0cd6db6e5625ab447c37b83eca20c3a7da48e0

[ROOTCHAIN - DEPLOY CONTRACT]
Name               = ExitHelper
Contract (address) = 0xE3Aef740dA056ba8Eb3De34a85248A5A19193993
Transaction (hash) = 0x94da90fa62735077d4a5a0180cc0d222460f0ecfa93178adacbac70173d0e9ff

[ROOTCHAIN - DEPLOY CONTRACT]
Name               = RootERC20Predicate
Contract (address) = 0x34040bdC008987Ed22659A3Df6D9cC0F88408938
Transaction (hash) = 0x3a0c44426b70f39e4e83e18b5ab9e58e6e9c06f6a352be58efbff7f0aad30eef

[ROOTCHAIN - DEPLOY CONTRACT]
Name               = ERC20Template
Contract (address) = 0x363C7143885fBe1183a5377072f2c417d0d5782e
Transaction (hash) = 0x6a09543f2291dced4c4e45a76adf5dd3e354aaf5883796a508e9007f570a10cb

[ROOTCHAIN - DEPLOY CONTRACT]
Name               = RootERC721Predicate
Contract (address) = 0x66Bd359D9f3F7fF22c3E33DC1e03298f14f6Aae7
Transaction (hash) = 0x570111bc5f60397840620cb4d945f63e7d746dd4e3578e24eaeb3c1b8a9c5665

[ROOTCHAIN - DEPLOY CONTRACT]
Name               = ERC721Template
Contract (address) = 0x4029140F51D5568776e5eA8F818f1C3B9f7B3A51
Transaction (hash) = 0xb67cca5a9feec5e8c3efcf69173dae4c585a385171391503088002f9a9d403d4

[ROOTCHAIN - DEPLOY CONTRACT]
Name               = RootERC1155Predicate
Contract (address) = 0x6cd668263a11b383071C2BC5a35BbC8899Eb3B21
Transaction (hash) = 0x6df263c3f69a417786ab18750b220733414ff55fd5f30d9e4db21f23590a5aaa

[ROOTCHAIN - DEPLOY CONTRACT]
Name               = ERC1155Template
Contract (address) = 0xd72B4A0f7d22aED120f039Bd2E8dFDff97500074
Transaction (hash) = 0xcb771ac7f26af3b6e0223c203a98b17ad0cc2abf5b29ec4471eeece9d45086bd

[ROOTCHAIN - DEPLOY CONTRACT]
Name               = StakeManager
Contract (address) = 0x1320Ac2f44769337F9cE36067d5471537De81872
Transaction (hash) = 0x6d9600b5ebe6821b824dda68f43051747c3627fabf97db78e9490afd8090da03

[ROOTCHAIN - DEPLOY CONTRACT]
Name               = CustomSupernetManager
Contract (address) = 0x3a4a4ca0d27C243D80011bCAf4E2f7637674919a
Transaction (hash) = 0x50342842b9702ef6334e9f22bae70cadde3d2bab19e284515ce8f7011f6d1262

[ROOTCHAIN - CONTRACTS DEPLOYMENT] StakeManager contract is initialized

[ROOTCHAIN - CONTRACTS DEPLOYMENT] CustomSupernetManager contract is initialized

[ROOTCHAIN - CONTRACTS DEPLOYMENT] [VALIDATORS]
Address=0xe2BE1ECB6246867450E2c6C15601dd060f3E7064; Balance=1000000; P2P Multi addr=/ip4/<IP_ADDRESS>/tcp/30301/p2p/16Uiu2HAm5477rqEuE1t5JpW9PkPCREs3xHHTPSKb6LVEuoPNP1F6; BLS Key=13cc39e7fe511acfeca22906da9a1899138d96f2348216ee54792877280e70a606d0d6ff1999960270c8fc80915c547184c3c6897b0d2e356ce7749ced345fae038d8d6fae8f0a1f6f71dd12f7c9e56db2835bdc95726c875d4365f75cc6820b085180219372397880a47be60245f86d064efdb935332da070032567dfb8e4b2;
Address=0x782990a8ABAD8Bfbc6C17FEfB3149469A34f1C81; Balance=1000000000000000000000000; P2P Multi addr=/ip4/<IP_ADDRESS>/tcp/30302/p2p/16Uiu2HAmJmhRYX5gFfypQsaJSsS9W4AXjZ2bZX1f9pWptdvAiYL7; BLS Key=0348d911a332e82b948cb5f1c4991d4b8c43b3d9eea20e64ca9e1baa38fafee820089fddee35b3ce7451f8e25e4fe2bd3e23f748ad4596f99295ab4d3452cab11b58c6009c36d20158a45eb6dddea8f2b3a23a7d82c80f5b6952983d367270ab0a572f3580cd15c3af192f58953aef69ac9bf0cad175eec2174886c8b81e9da1;
Address=0x1B1797e2B53D1686A702f15Ed8f94FF9CE1d62af; Balance=1000000000000000000000000; P2P Multi addr=/ip4/<IP_ADDRESS>/tcp/30303/p2p/16Uiu2HAmAYVCewhoc4QYa7wukguw4LftTw7FUK4YrVm6V777V8YE; BLS Key=080c1d3d9c7022bc43209e74bbda5b78df953693b78b31cf93de21d263ebd0f32af900283c93c97d50ae477c7b6fca66972c2778c5b126b7c95453014c6859922d4b6ad05ee0fffd68d1824477a70b11c6d9e65454939acd7ce914e3d0e8ca811d1ef806b3ad5a5625357216358e49016249458574ff6d6aa97edce8420d0714;
Address=0xbFC0533D8e92deE26BE33D4CB9332b92949Ed0F2; Balance=1000000000000000000000000; P2P Multi addr=/ip4/<IP_ADDRESS>/tcp/30304/p2p/16Uiu2HAm2voTMkW5BZeGFxVa4ZKf5cY7DoDbeiGy4AE3uxFoBNmJ; BLS Key=1882079524485a194a2f12d3c016b30a4e44269f83666bfbcc9d96c8b00402502c71af55a824afe3fdafade4476e1e5caf3bb7c2314b5e7a34733063a8675f3201b755e4bd9097fa4a3d8189bbe481ea6484f96288e58d7eab0781401cee02960a709e3eb43153225ae1720ad07a572935dac0cccdc9df66ca933ae79e9d0678;
[ROOTCHAIN - CONTRACTS DEPLOYMENT] Validators hash: 0xa476ec1213d7b0e030106f430ddb072fac3a238601ce209ffdcade08daefe1d8
[ROOTCHAIN - CONTRACTS DEPLOYMENT] CheckpointManager contract is initialized

[ROOTCHAIN - CONTRACTS DEPLOYMENT] ExitHelper contract is initialized

[ROOTCHAIN - CONTRACTS DEPLOYMENT] RootERC20Predicate contract is initialized

[ROOTCHAIN - CONTRACTS DEPLOYMENT] RootERC721Predicate contract is initialized

[ROOTCHAIN - CONTRACTS DEPLOYMENT] RootERC1155Predicate contract is initialized

[ROOTCHAIN - CONTRACTS DEPLOYMENT] finished. All contracts are successfully deployed and initialized.

---

4.

Did you use your MetaMask wallet address as your <private_key> ?

Could you try the following:
See if the bridge works in the other direction.
Try to pre-mint some MATIC in your Supernet when generating your genesis.json. Then using those MATIC and try to deploy your own ERC20 token on the Supernet. Then use the bridging "deposit" functionality to do an asset transfer from the Supernet to the RootChain. This would help me diagnose what might be happening.

@deepalt92

While deposit token for beidge , tokens ar getting deposited on the that address it is ERC20predicate addres. You can visit the address on mumbai polygon scan.
Yes i am use metamask private key

@amansk2050 Why have you used two native root tokens:
One in the fund command: 0x0BaA5a112a64087eB80CfF57fbBD0B4d8011A50B
and another in the stake command: 0x13A2e16C0905e2CcFEE63Bf26EF859eBA3848D55?
Could you verify your contracts on PolygonScan to see what these two contracts are?


DB connection failure: encryption service algorithm: 6 still not supported

When I try to connect to the database using the driver, I see this error:
"advanced negotiation error: encryption service algorithm: 6 still not supported"
Database  (on AWS RDS, Oracle 12.0) config:

SQLNET.ENCRYPTION_SERVER: REQUIRED
SQLNET.ENCRYPTION_TYPES_SERVER: RC4_256, AES256, AES192, ....

On the application server "sqlnet.ora" config:

SQLNET.ENCRYPTION_SERVER = required
SQLNET.ENCRYPTION_TYPES_SERVER = AES256

On the application server, set the environment variable "TNS_ADMIN" to point to the directory that contains "sqlnet.ora"
Did I miss anything?

BTW: I am with go-ora version v2.3.0

the driver not using sqlnet.ora and TNS_ADMIN
the error message because that the driver is not support any RC4 encryption
if you put AES256 as the first option in the server it will work
I will try to add RC4 encryption support later

I will also add some url configuration that work instead of sqlnet.ora and tns_admin

yes this is what I will do:
1- I will send to the server only the supported algorithm
2- let user select his preferred algorithm through database URL option
what happen here is that the client send an empty option thus server will select one from its side which is the first one in the list
I will leave the issue open until I finish the work and inform you

any update?

coming soon I am now working on supporting OS authentication

fixed now.
you can test it


libisds: 0.11.1 -> 0.11.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/libisds/versions.
meta.description for libisds is: "Client library for accessing SOAP services of Czech government-provided Databox infomation system"
meta.homepage for libisds is: "http://xpisar.wz.cz/libisds/"
meta.changelog for libisds is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.11.2 with grep in /nix/store/mc6xrz0fdhkzqmnpbxfz02dcz6sdh3wd-libisds-0.11.2

found 0.11.2 in filename of file in /nix/store/mc6xrz0fdhkzqmnpbxfz02dcz6sdh3wd-libisds-0.11.2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
datovka
libisds

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mc6xrz0fdhkzqmnpbxfz02dcz6sdh3wd-libisds-0.11.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libisds https://github.com/r-ryantm/nixpkgs/archive/73de9bea44571d7f3a13d4169836fe92b20f9da2.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mc6xrz0fdhkzqmnpbxfz02dcz6sdh3wd-libisds-0.11.2
ls -la /nix/store/mc6xrz0fdhkzqmnpbxfz02dcz6sdh3wd-libisds-0.11.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

datovka
libisds

Maintainer pings
cc @mmahut for testing.

Result of nixpkgs-review pr 167825 run on x86_64-linux 1

2 packages built:

datovka
libisds

Result of nixpkgs-review pr 167825 run on x86_64-linux 1

2 packages built:

datovka
libisds


[5.10][CMake] Replace early swift-syntax with FetchContent

Cherrypick #68408 (and #68388, #68527, and #68867) into release/5.10

Explanation: Build the swift-syntax host libraries using FetchContent rather than early-swiftsyntax. This simplifies the overall toolchain build process and fix the issues we've seen caused by swift-syntax not being rebuilt. We should be able to use this to fix cross-compiling on Linux
Scope: Build system
Risk: Mid, since we update the build mechanism. But removes some nasty hacks.
Testing: Passes the current test suite
Issues: rdar://115439072
Reviewer: Ben Barham (@bnbarham)

https://github.com/apple/swift-syntax/pull/2252
https://github.com/apple/llvm-project/pull/7549
@swift-ci Please test

https://github.com/apple/swift-syntax/pull/2252
https://github.com/apple/llvm-project/pull/7549
@swift-ci Please test

@swift-ci Please test Windows


Replace :pending test tag with idiomatic :skip tag

Since Elixir v1.1 the tag :skip has been used to skip tests.
If we use the standard here the students will not have to re-learn how
to skip tests when they move onto real Elixir projects. :)

I'm totally down with this - thanks for the great contribution! 👍
Since it's a rather significant change I want to leave this open for a couple of days just to make sure no one raises any issues, but I can't see any myself.

I'm :+1: on this change. I think it is great. However, it points out that the Elixir version in mix.exs is out of sync with the README and Travis. Opening an issue on that.

I can fix that. Would you like me to resolve it in this pull request or another?

Normally I'd prefer a separate PR but since you have to change it in this one anyway let's do it here. Sound good?

Thanks 🎉


Wrong link https://github.com/jsh9/pydoclint#notes-on-doc103

The link is printed in the report and mentioned here https://github.com/jsh9/pydoclint/blob/main/docs/violation_codes.md?plain=1#L30, but it leads nowhere.

Hi @kit1980 , thank you for finding this issue!
It will be fixed in https://github.com/jsh9/pydoclint/pull/62.

Fixed.
The new version (0.1.8) is published to PyPI.
Btw, the correct link is now here: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103


Add linters config files

Add Linters  (https://github.com/zeff96/catalog_of_my_things/pull/27)

Linters config files added succesfully


Use Rollup and Flattened Dist Directory

Hi! As discussed in #1, this is my take on publishing the package.
However, instead of just running npm publish, there is a custom script called publish:custom now that we have to run. yarn publish:custom for example. This results in deploying this structure to npm:
❯ ls dist
total 360
  0 drwxr-xr-x  10 sallar  staff   320B Feb 22 19:05 ./
  0 drwxr-xr-x  14 sallar  staff   448B Feb 22 18:54 ../
  0 drwxr-xr-x   5 sallar  staff   160B Feb 22 19:05 assets/
 16 -rw-r--r--   1 sallar  staff   6.9K Feb 22 19:05 main.d.ts
 80 -rw-r--r--   1 sallar  staff    39K Feb 22 19:05 main.js
160 -rw-r--r--   1 sallar  staff    79K Feb 22 19:05 main.js.map
  8 -rw-r--r--   1 sallar  staff   1.9K Feb 22 19:05 navigation.d.ts
 32 -rw-r--r--   1 sallar  staff    13K Feb 22 19:05 navigation.js
 56 -rw-r--r--   1 sallar  staff    27K Feb 22 19:05 navigation.js.map
  8 -rw-r--r--   1 sallar  staff   1.7K Feb 22 19:05 package.json

And can be imported by users like this:
import { ZStack } from 'swiftui-react-native';
import { NavigationLink } from 'swiftui-react-native/navigation';

I can also add a Github Action that automatically releases this to NPM, when a Github Release is created. Let me know if you want me to also add this!
What do you think?
Closes #1

@sallar This looks awesome! Thank you for taking the time to do this. I will take a look at this more closely later today, but at first glance this is exactly what I was thinking. As for the Github Action, that sounds like a better way to handle releases. Feel free to set that up if you would like! Is the Action a code change, or is that taken care of within github? Much appreciated, this is a big lift for me.

My pleasure @andrew-levy-
I'll setup GitHub actions and add it to the same PR. It's a YAML file that needs to be added to the project, but it's possible to visually change and update it in Github later too.

@andrew-levy I added the GitHub action. Before merging to master, add the NPM secret here:
Repo Settings > Secrets > Add Repository Secret
name of secret: NPM_AUTH_TOKEN
value: an npm token
Im using this package to publish to npm: https://github.com/marketplace/actions/automated-releases-for-npm-packages
And it uses this workflow:

Check for the latest version number published to npm.
Lookup all commits between the git commit that triggered the action and the latest publish.

If the package hasn't been published or the prior publish does not include a git hash, we'll only pull the commit data that triggered the action.

Based on the commit messages, increment the version from the lastest release.

If the string "BREAKING CHANGE" is found anywhere in any of the commit messages or descriptions the major version will be incremented.
If a commit message begins with the string "feat" then the minor version will be increased. This works for most common commit metadata for feature additions: "feat: new API" and "feature: new API".
All other changes will increment the patch version.

Publish to npm using the configured token.
Push a tag for the new version to GitHub.

@sallar Looks great. I was able to add my npm auth token of type 'automation', so I think this is ready to merge if you are done adding changes. Will the merge trigger the action?

@andrew-levy awesome. yes it will trigger the action. it might fail though as the publish part hasnt been tested from this repo. if it does, I can quickly fix it. LGTM!

@andrew-levy thanks for merging. seems like the publish was successful:
https://github.com/andrew-levy/swiftui-react-native/runs/1961900496?check_suite_focus=true
https://github.com/andrew-levy/swiftui-react-native/releases/tag/v1.8.1

@sallar  Yep looks great! I noticed two things though.

https://www.npmjs.com/package/swiftui-react-native there is no readme available for viewing it on npm. We may need to point it to the correct readme.
The npm version does not match the one in package.json. Is this okay? Going forward, should that update automatically?

@andrew-levy yes it's because the README wasn't copied to dist folder. I probably should make another PR and add that for you. Sorry about that, forgot :D
The second part, yes I noticed it just now two. The trouble is, it has to commit the resulting package.json again to the repo, which creates a new commit which in turn will trigger the github action again. But there are ways to prevent that. I will fix this in my PR too!

@andrew-levy a "cleaner" way would be to set the package.json version to 0.0.0-development, so it will be always automatic when published. What do you think? This will not create extra commits for you.

@sallar This works, I'll go ahead and merge those new changes in soon. Thanks again.
Regarding the /assets directory in this project, it currently stores the cover image for the readme, as well as some library icons like right-cheveron and check-mark. Eventually, my plan is to not use pngs for these icons, but rather something like https://github.com/birkir/react-native-sfsymbols. It has native code, so I will need to see if its a good idea to bring that in or something like it (is there a performance cost? more dependencies/setup steps? I want to keep setup relatively simple). So eventually, we won't need to copy that directory over. That should just be a small change when we cross that bridge.

@andrew-levy not bundling PNG is a good idea. You might want to give the users the option to set the image by themselves (pass in as props) so they could use whatever library they want


Suggestion: Enhance section on changing the default render mode for an app

Description
[Enter feedback here]
If you create an app from the Blazor Web App template using the Auto (Server and Client) rendering mode option and then, later, choose to manually change the render mode for the whole application, the section of this document that shows setting @rendermode on the Routes component only works correctly if you choose InteractiveServer. If you choose InteractiveWebAssembly or InteractiveAuto then an error message is generated in the console, because the Routes component cannot be found.
The Routes component needs to be moved to the Client project for this section of the document to work. That also requires moving the MainLayout and NavMenu components.
I think explaining the need for the Routes component to be in the Client project might help some people understand the error message that is written to the console, if they encounter it. I only resolved the problem by rewatching Steve Sanderson's .NET Conf session again, where he explains this during the demo.
Error: One or more errors occurred. (Root component type 'ABC.Components.Routes' is not found in project 'ABC')
Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/components/render-modes?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/components/render-modes.md
Document ID
7c9948a3-9886-8097-6014-492a4c21ea4e
Article author
guardrex

Thanks, @TheCakeMonster ... I agree. I'll try to get this resolved on Wednesday morning, as I have another high priority task that's going to be worked on Tuesday.

Actually, I think I can't knock this out quickly. It's just a few lines. I'll see if I can fix it today.

@guardrex  Thanks, that looks great.


Add spec opts for host device and privileged handling

Codecov Report

Merging #3718 into master will increase coverage by 0.3%.
The diff coverage is 75.51%.

@@            Coverage Diff            @@
##           master    #3718     +/-   ##
=========================================
+ Coverage    42.1%   42.41%   +0.3%
=========================================
  Files         129      129
  Lines       14307    14356     +49
=========================================
+ Hits         6024     6089     +65
+ Misses       7383     7362     -21
- Partials      900      905      +5

Flag
Coverage Δ

#linux
45.97% <75%> (+0.35%)
:arrow_up:

#windows
37.1% <78.57%> (+0.04%)
:arrow_up:

Impacted Files
Coverage Δ

oci/spec_opts_windows.go
74.19% <100%> (+1.77%)
:arrow_up:

oci/spec_opts_linux.go
83.07% <74.28%> (+83.07%)
:arrow_up:

oci/spec_opts.go
31.82% <75%> (+0.59%)
:arrow_up:

Continue to review full report at Codecov.

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

@crosbymichael I think for some runtime, host devices don't make sense for privileged, kata for example (see https://github.com/containerd/cri/pulls?q=is%3Apr+privileged+is%3Aclosed).

@crosbymichael SG. Thanks!

LGTM


Compiler: try to infer types from class method bodies

This is a complement to #2486 to need less type annotations in class methods.
After #2486, this is possible:
class Foo
  def initialize
    # Inferred to Bar, because Bar.create has a return type annotation
    @value = Bar.create
  end
end

class Bar
  def self.create : self
    new
  end
end

However, the self return type annotation is not really needed. If it's not there, the compiler could check the method's body and see it's a simple call to new, and from there infer the type to be Bar.
Effectively, this PR does just that: the self return type annotation is not needed anymore in this case.
This PR does more: it applies the usual guessing rules to a class method's body. So this works too:
class Foo
  def initialize
    # Inferred to Int32, because default_size's body is a literal
    @size = Foo.default_size
  end

  def self.default_size
    1
  end
end

And if inside the method a class method is invoked, and the class method has a return type, the return type is used:
class Foo
  def initialize
    # Inferred to String, because Foo.default_name's body
    # is String.build, and String.build has a self return
    # type annotation
    @name = Foo.default_name
  end

  def self.default_name
    String.build do |str|
      # some stuff...
    end
  end
end

class String
  def self.build : self
    # The implementation...
  end
end

Ultimately, as always, the goal is to reduce redundant type annotations if the compiler (and a human) can easily infer them ("easily" == no need to do type flow analysis on local vars, or depend on the type of other instance/class/global variables).
I think that the less type annotations we require from a programmer, the happier she'll be (as in Ruby).
The downside of this PR, as usual, is that it makes the rules a bit more complex. But the only moment where you'll get a "can't infer the type of ..." error is when you are defining a class and defining its constructor or adding more instance vars, and at that moment if the compiler can't infer the type for you, you can simply add a type annotation.

I'll merge this. The rules keep being intuitive, this will reduce type annotations and it will make the language closer to what we had before all these changes :-)


Slurm tests

Description
Adds in testing for slurm systems inside of a container which have come up from discussions with @benclifford in some emails and issue https://github.com/Parsl/parsl/issues/3579
Changed Behaviour
More testing on slurm code.
Fixes
Fixes #3579
Type of change

New feature

The slurm tests pass with the slurm config but it seems like it's still missing some slurm tests that could be helpful. Some helping getting a good config to test everything or the right pytest settings would be appreciated!

What you've got is a test that runs the "should work with most configs" tests against an environment using the SlurmProvider.
Are you asking about specific tests that you know exist but don't see running?
I think the only other slurm-related tests are these, which don't need a working slurm instance - they only check that the provider can set itself up correctly:
$ ls parsl/tests/test_providers/test_slurm_*.py
parsl/tests/test_providers/test_slurm_instantiate.py  parsl/tests/test_providers/test_slurm_template.py

Part of the reason there is that personally I have only really pushed on tests that are run automatically, rather than at-release testing that wasn't happening in reality. If this PR was merged, the automated tests would be in a much better place to get additional tests that might test specific SlurmProvider features, rather than running a full Parsl DFK.

Right I saw those two tests didn't run when I added the Slurm Config but if they are okay to be left off then I think this is good to go.

I saw those two tests didn't run when I added the Slurm Config

They get run in a different part of testing, because they are marked with pytest.mark.local - because they aren't tied to being run with any particular configuration.


Adding clients to supplier response + couple of tests.

Where Supplier['clients'] is either a list of client names or an empty list.
This is in contrast to the way that some of our other keys are not in the response if they have null values.
Also added a few tests because I didn't think our unit tests are taking long enough to run.

Paul and I talked yesterday about the empty array Vs missing key for those suppliers with no clients. What do others think about this model or using an empty list?

I don't mind an empty list - it feels much more descriptive than a null for some reason.  As we had in a previous discussion though - clients shouldn't be dependent on particular keys existing; it's the values of keys that do exist they should be worrying about.

:+1: All looks good to me - happy to merge if we agree to return keep empty client arrays. I think either way should be fine though.


media.ccc.de extractor broken

[X] I'm reporting a broken site support
[X] I've verified that I'm running youtube-dl version 2020.12.26
[X] I've checked that all provided URLs are alive and playable in a browser
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones

Verbose log
C:\Users\k\Downloads>youtube-dl --verbose https://media.ccc.de/v/rc3-11512-cia_vs_wikileaks
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'https://media.ccc.de/v/rc3-11512-cia_vs_wikileaks']
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, pref cp1252
[debug] youtube-dl version 2020.12.26
[debug] Python version 3.8.3 (CPython) - Windows-10-10.0.19041-SP0
[debug] exe versions: ffmpeg 4.2.3
[debug] Proxy map: {}
[media.ccc.de] rc3-11512-cia_vs_wikileaks: Downloading webpage
ERROR: Unable to extract event id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "c:\users\k\appdata\local\programs\python\python38\lib\site-packages\youtube_dl\YoutubeDL.py", line 803, in wrapper
    return func(self, *args, **kwargs)
  File "c:\users\k\appdata\local\programs\python\python38\lib\site-packages\youtube_dl\YoutubeDL.py", line 824, in __extract_info
    ie_result = ie.extract(url)
  File "c:\users\k\appdata\local\programs\python\python38\lib\site-packages\youtube_dl\extractor\common.py", line 532, in extract
    ie_result = self._real_extract(url)
  File "c:\users\k\appdata\local\programs\python\python38\lib\site-packages\youtube_dl\extractor\ccc.py", line 40, in _real_extract
    event_id = self._search_regex(r"data-id='(\d+)'", webpage, 'event id')
  File "c:\users\k\appdata\local\programs\python\python38\lib\site-packages\youtube_dl\extractor\common.py", line 1010, in _search_regex
    raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract event id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Description
Extraction fails

Maybe something changed since yesterday, because this works for me.

youtube-dl https://media.ccc.de/v/rc3-11512-cia_vs_wikileaks
[media.ccc.de] rc3-11512-cia_vs_wikileaks: Downloading webpage
[media.ccc.de] 9186: Downloading JSON metadata
[download] Destination: CIA vs. Wikileaks-9186.webm
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0  209M    0 98268    0     0  25623      0  2:23:00  0:00:03  2:22:57 33031

Can reproduce on recent manjaro with updated youtube-dl .. right now:
youtube-dl --verbose https://media.ccc.de/v/rc3-11360-careables
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'https://media.ccc.de/v/rc3-11360-careables']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.01.08
[debug] Python version 3.9.1 (CPython) - Linux-5.10.2-2-MANJARO-x86_64-with-glibc2.32
[debug] exe versions: ffmpeg 4.3.1, ffprobe 4.3.1, rtmpdump 2.4
[debug] Proxy map: {}
[media.ccc.de] rc3-11360-careables: Downloading webpage
ERROR: Unable to extract event id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 803, in wrapper
    return func(self, *args, **kwargs)
  File "/usr/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 824, in __extract_info
    ie_result = ie.extract(url)
  File "/usr/bin/youtube-dl/youtube_dl/extractor/common.py", line 532, in extract
    ie_result = self._real_extract(url)
  File "/usr/bin/youtube-dl/youtube_dl/extractor/ccc.py", line 40, in _real_extract
    event_id = self._search_regex(r"data-id='(\d+)'", webpage, 'event id')
  File "/usr/bin/youtube-dl/youtube_dl/extractor/common.py", line 1010, in _search_regex
    raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract event id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Can reproduce on recent manjaro with updated youtube-dl .. right now:
youtube-dl --verbose https://media.ccc.de/v/rc3-11360-careables
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'https://media.ccc.de/v/rc3-11360-careables']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.01.08
[debug] Python version 3.9.1 (CPython) - Linux-5.10.2-2-MANJARO-x86_64-with-glibc2.32
[debug] exe versions: ffmpeg 4.3.1, ffprobe 4.3.1, rtmpdump 2.4
[debug] Proxy map: {}
[media.ccc.de] rc3-11360-careables: Downloading webpage
ERROR: Unable to extract event id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 803, in wrapper
    return func(self, *args, **kwargs)
  File "/usr/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 824, in __extract_info
    ie_result = ie.extract(url)
  File "/usr/bin/youtube-dl/youtube_dl/extractor/common.py", line 532, in extract
    ie_result = self._real_extract(url)
  File "/usr/bin/youtube-dl/youtube_dl/extractor/ccc.py", line 40, in _real_extract
    event_id = self._search_regex(r"data-id='(\d+)'", webpage, 'event id')
  File "/usr/bin/youtube-dl/youtube_dl/extractor/common.py", line 1010, in _search_regex
    raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract event id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Well - I dived into it a bit .. seems, that the videos in the relive-area, of which there are no final recordings relased, don't have the data-id value - and therefore no event-id can be pulled insid the _real_extract function.
Solution could be to get that value e.g. from the second comma separated field inside the "meta content" header.. or to just simply wait until the final recording is released.

Well - I dived into it a bit .. seems, that the videos in the relive-area, of which there are no final recordings relased, don't have the data-id value - and therefore no event-id can be pulled insid the _real_extract function.
Solution could be to get that value e.g. from the second comma separated field inside the "meta content" header.. or to just simply wait until the final recording is released.


Update Checkbox

I didn't want to try to resolve this conflict. I wasn't sure what the syntax was supposed to be so I left it for @calebissharp to fix.


feat(qwik): add missing examples

Adding missing examples for Qwik.
There's a slight caveat with fallback content. It's not working currently with the instructions described on the documentation, this seems to be intentional with no immediate plans to bring the feature back. I made the example using some of the recommendations from the thread (and Discord). Added this as a comment on the example itself.

Thanks for that - make sure to update the main repo - as I noticed the tutorial still shows this problematic example with the slot's fallback.


Merge

This is an automatically-mergeable version of the atw-improvements branch that has been rebased onto the current master.  It has ATW working in all code paths.  It also has some minor bug fixes, a reworking of the way OpenGL/D3D works, and a change to all RenderManagers that keeps them from allocating buffers for the Render() path until an app actually calls Render().  Big GPU memory savings.

If this is what you want to release as 0.6.43, then it needs to be merged to master, or the CI won't build it, no Unity packages/plugins will get updated, no installers, etc.
I added a few notes as I skimmed through - nothing crucial, mostly just safety/clarity stuff.


Added ability for TAs to reopen queues (#161)

Ended button on queue page now triggers dropdown with option to restore queue to cutoff/open depending on status when ended.

Not totally sure why codeclimate is unhappy... But I'll figure it out tomorrow.

@athyuttamre When you get a chance could you look at this? I don't see anything in eslint docs about Resolver errors. Any idea what's up?

I can take a look EOD today!

Hey @wpovell, so I spent a while debugging this, and turns out CodeClimate's Meteor support is a bit lacking. I've filed an issue locally here (https://github.com/signmeup/signmeup/issues/186) and with them here (https://github.com/codeclimate/codeclimate-eslint/issues/200).
For now, let's ignore the CodeClimate resolution issues. I'll review the actual changes shortly. :)

@athyuttamre Thanks! Any suggestions on what to work on text? Another good-first-bug or should I go for something larger (the profiles/graph statistics page features both sound cool).

As for what to work on next, really up to you. I think you're in a good position to tackle a slightly larger feature for sure. What do you think of https://github.com/signmeup/signmeup/issues/163, https://github.com/signmeup/signmeup/issues/116, or https://github.com/signmeup/signmeup/issues/16?

#116 sounds good, would get to understand a bit how text/email sending works on server side. Also feel like #169 would be pretty straightforward after doing this issue. I'll look into both and comment on one of their respective issues a design plan. Thanks!

(I'll also get to work on the requested changes for this pull)

Fantastic, sounds good!

Okay, changes should be addressed. By the way, let me know if I'm doing something wrong, I seem to have a lot of non-fast forward merges which clutters things with extra commits. Do I just need to remember to pull before committing?

Fantastic work again, thanks so much William! Will merge now. And yes, I think it's a matter of pulling before committing.


SaaS Boost v3

Feature branch for work-in-progress on the future direction of SaaS Boost.
This work focuses on many of the items listed in our roadmap, notably a distinct split of the Control Plane API and services from the Application Plane provisioning and deployment functionality.

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

@brtrvn @PoeppingT  When can we expect the release on v3?
Does it or can include below requests -

https://github.com/awslabs/aws-saas-boost/issues/316
https://github.com/awslabs/aws-saas-boost/issues/328
https://github.com/awslabs/aws-saas-boost/issues/374
https://github.com/awslabs/aws-saas-boost/issues/323
https://github.com/awslabs/aws-saas-boost/issues/431


Update README.md

I updated the README text!
blah
blah
blah
bug fixed
test
blah blah

Is this change needed for the long-term?

yes perfect
😀

@matthewaol oh okay, good to go then.


MPA layer 2 encoding (libtwolame)

When MPEG audio layer 3 encoding was implemented the layer 2 encoding support was dropped completly (https://github.com/alfredh/baresip/pull/797) as maybe it was not clear that libmp3lame is layer 3 ONLY (and libtwolame is layer 2 only).
To support layer 2 and layer 3 encoding in MPA module both libs may need to be dynamicly used for encoding depeding on the requested layer from local config or SDP fmtp string.
Who can help me on this topic?

Reading further (https://www.iis.fraunhofer.de/content/dam/iis/de/doc/ame/conference/AES-17-Conference_mp3-and-AAC-explained_AES17.pdf and others) and looking at the features of Orban Opticodec 7600 device there might also "Layer 4" support be added on the the same way: MPEG-2 AAC ADTS by fdk-aac
Orban Opticodec 7600 Setting "AAC (MPEG2)":
#
U <IP_ADDRESS>:5060 -> <IP_ADDRESS>:42786
INVITE sip:1069155266620-0x8a63f0@<IP_ADDRESS>:42786 SIP/2.0.
Via: SIP/2.0/UDP <IP_ADDRESS>:5060;branch=z9hG4bKou5klh20cgomev4lo500.1.
From: "OPTICODEC7600" <sip:1069155242902@<IP_ADDRESS>>;tag=IxlON0mA.
To<EMAIL_ADDRESS>Call-ID: 1lTpzcGEYzie4PAG.
CSeq: 29304 INVITE.
Contact: <sip:1069155242902-rrgh531oo5664@<IP_ADDRESS>:5060;transport=udp>.
Max-Forwards: 67.
User-Agent: Opticodec7600/5.11.115.
Content-Type: application/sdp.
Allow: INVITE, ACK, CANCEL, BYE, OPTIONS.
Content-Length: 284.
.
v=0.
o=OC7600<PHONE_NUMBER> 1 IN IP4 <IP_ADDRESS>.
s=audio.
c=IN IP4 <IP_ADDRESS>.
t=0 0.
m=audio 5004 RTP/AVP 96 9 8 0.
a=rtpmap:96 MPA/90000.
a=fmtp:96 layer=4;samplerate=48000;bitrate=128000;mode=stereo.
a=rtpmap:9 G722/8000.
a=rtpmap:8 PCMA/8000.
a=rtpmap:0 PCMU/8000.
a=sendrecv.

It just would need some help on implementing the general dynamic encoder switching in MPA module as I am not that skilled on C programming language (yet?).


Rename AWS bucket

Rename the AWS s3 bucket from intake.catalyst.coop to pudl.catalyst.coop so it has a took independent name. Also, we're supposed to have a 1-month retention policy on s3 bucket logs, so we need to setup a bucket in GCP that can store our s3 logs long term.
- [x] Delete the junk tagged outputs in GCS and S3
- [x] Add `v2022.11.30.post1` to AWS
- [x] Create a new s3 bucket called `pudl.catalyst.coop`.
- [ ] Create a [log bucket called](https://docs.aws.amazon.com/AmazonS3/latest/userguide/enable-server-access-logging.html#enable-server-logging) `pudl.catalyst.coop-logs` for `pudl.catalyst.coop` bucket. AWS Open Data Program requires we set a 1 month retention policy.
- [x] Create a GCS bucket called `pudl.catalyst.coop-logs` to retain all logs from `pudl.catalyst.coop-logs` bucket in s3.
- [x] Create AWS credentials for the VM to dump outputs to s3 bucket. Test existing credentials
- [x] Create a GCS service account, give it access to gs://pudl.catalyst.coop-logs. Add keys to repo.
- [x] Create AWS credentials for a user that has access to s3://pudl.catalyst.coop-logs. Use [WIF](https://github.com/aws-actions/configure-aws-credentials)?
- [x] Create a reoccurring job that syncs the s3 logs with GCS logs. Test it's working as expected!
- [x] Update the bucket name in docs and nightly build scripts.
- [x] Update the URLs to use the new name.
- [ ] Update the aws registry repo https://github.com/awslabs/open-data-registry/pull/1998
- [x] Stop nightly builds from dumping workflow-triggered outputs into AWS bucket. Will have to pass an env var for the trigger method. Add to distribution bucket if branch is `dev` or action was triggered by a `tag`. This will exclude `workflow_dispatch` triggers.
- [x] Sync all of the buckets
- [ ] Set up retention policy on gs://pudl.catalyst.coop

### Tasks
- [ ] enable retention policy on s3://pudl.catalyst.coop
- [x] Does the new tag / dev check work in the vm
- [x] Does the vm have access to the s3 bucket with the existing credentials?
- [x] Check vm has access to gs://pudl.catalyst.coop
- [x] create keys for pudl-s3-logs-sync

Do folks have opinions on what we should rename the bucket to? Some ideas:

pudl.catalyst.coop
pudl-outputs.catalyst.coop
outputs.catalyst.coop

I like pudl.catalyst.coop because the S3 is a primary mode of access for all PUDL data.

The 2022.11.30.post1 release didn't end up going out really -- it only changed a dependency in the Python packaging, and that change couldn't be propagated to the conda packaging, and no data changes were associated with it.  So I don't think it actually needs to be updated on AWS.

Sounds good. Waiting to hear back from AWS folks on the best way to rename the bucket.

Are we concerned about breaking software that depends on the old bucket name? We could have two buckets for a bit and let the world know we'll be deprecating the old name.

  Do we have any information about what is hitting the existing bucket address(es)?

We have logs for the AWS access but I haven't added them to our metrics ETL.
It looks like we might be able to redirect requests from the old bucket.

From my cursory search, links do not seem to be supported.

It might make sense to make an alias that redirects a bucket download URL so we don't have to keep changing the URL if the bucket name/location of the data changes. For example, data.catalyst.coop/pudl.db could redirect to whatever cloud bucket we use. This would be helpful if we do another bucket name change or AWS stops covering our storage fees.

Now that #2793 is merged, is this done?

Waiting on merging this PR in the AWS repo.


Refactor main bar inputs

Aims to fix the weird behaviors experienced with the main bar width/height/ratio inputs

@sindresorhus updated 👍

These are good points. We've talked about most of them in the past and I've worked on some but last time I did was when I first started the re-write. I'll work on it a bit more, see how it goes, and if it seems like it's going to be a lot of extra work, I'll see about splitting into two PRs

This also fixes #539 now

@sindresorhus it's all of them (hopefully) 😄 I went ahead and checked them though

Also, for the ratio menu I used the itemPositioning option of the menu api to show the selected one under the cursor. I saw it was osx specific, so I'm guessing is standard osx practice?

Not cursor, but yes it's common practise to show it under the element that triggered the menu. It needs to be better aligned though. When the menu is open, the active menu item should be vertically centered to our white dropdown widget.

I'm getting this error every time I click the Kap menu bar icon:

Selecting an aspect ratio should active the width/height lock. Otherwise, what's the point of selecting aspect ratio if it's not enforced when you change width or height.

Doesn't look like this is done. If I select an item in the aspect ratio dropdown, the lock button is not highlighted.

I can't recreate the issue @sindresorhus is having when clicking the menubar icon, I can however confirm that selecting an spect ratio does not lock the dimensions, which I think it should.
Overall this is such a massive improvement, after testing the branch for a few days I haven't had a single issue with it and it feels great to use. The only thing I might add is for the inputs to only allow number input, however that's not really common practice. In a future update a nice to have would be the ability to do simple math in the inputs, e.g. 64+64 would change the input to 128 on enter/blur.

@karaggeorge Can you fix the merge conflict?

I'm no longer getting the focus error when clicking the menu bar icon. Weird...

The only thing left is https://github.com/wulkano/kap/pull/528#issuecomment-425671151

@sindresorhus I'll fix the merge conflicts when I get some down-time. About the other comment, I tried to get it as close to centered as I could. Bringing it one more pixel makes it even worse. Any idea of a consistent way to do it?

About the other comment, I tried to get it as close to centered as I could. Bringing it one more pixel makes it even worse. Any idea of a consistent way to do it?

Hmm, actually it looks enough for me now. Must have been something weird when I tried earlier as I could swear it was not aligned then.

Should be all good. Also, I found a bug where the validation was pulling the primary display screen's size instead of the one we sent through ipc. So in external displays, the cropper was limited to the primary display size. Should be fixed now

Looks great!


Conv E

[ ] Good to go

@aerask We can merge this as soon as you are ready.
If you don't have anything else to add go ahead and check "ready to go", so I know


Cylc needs wrapper on Raijin

resolution_fixed   |    by ibc599

Same problem as Rose.
Needs to have wrapper on Raijin, so calls to cylc will work without worrying about module loads in .bashrc.
This is mainly for the case when trying to kill a task from the gcylc window.

Issue migrated from trac:101 at 2024-01-31 17:33:46 +1100

<EMAIL_ADDRESS>changed owner from ibc599 to saw562

<EMAIL_ADDRESS>changed priority from major to minor

<EMAIL_ADDRESS>commented

No solution available at the moment.
Users need to continue with module load cylc in their dot file(s).
Can request Cylc feature as per what is in Rose for configuration setting on Accessdev specifying pathname for Raijin Rose.

<EMAIL_ADDRESS>changed status from new to assigned

<EMAIL_ADDRESS>removed milestone (was Future)

<EMAIL_ADDRESS>commented

Milestone Future deleted

<EMAIL_ADDRESS>changed status from assigned to closed

<EMAIL_ADDRESS>commented

This was fixed in cylc 6.1.0, http://cylc.github.io/cylc/changes.html#6.1.0 and https://github.com/cylc/cylc/pull/1166
Following http://cylc.github.io/cylc/html/single/cug-html.html#B.8.1, add
    [[raijin.*]]
        cylc executable = /projects/access/bin/cylc

to the global.rc configuration file.
OK to add this to both the cylc5 and cylc6 configuration files, though only cylc6 uses it.

<EMAIL_ADDRESS>changed _comment0 which not transferred by tractive

<EMAIL_ADDRESS>changed resolution from `` to fixed