Fix the license

I think we should use GPL v3 instead, it's the future of open source.

:+1:

:+1:

:+1:

:+1:

Ridiculous.

👍🏼

💤

Good joke.

:+1:

Yeah!

:+1:

:+1:

:trollface:

:+1:

:tropical_fish:

:+1:

xD

+1

Wow - this is not a great first impression of the community.

:trollface:

@Danappelxx
I believe the lack of community support is because of the restrictive apache license.

Apple:

:+1:

How can you make that assertion when they just open sourced it? The community hasn't had a chance to form...

Do not do this

:+1:

Absolutely!

Vote to close, not constructive.

vote to close

:-1: this seems really childish

grabs popcorn

This is some quality trolling.
Bravo.

:+1:

Richard Stallman would approve.
Go GPL v3... we're making history here folks!

Lol

You've got to be kidding.

:-1:

😂

:+1:

:+1:

I mean, what other popular projects on Linux use the Apache license?
😂

👍🏻😂

:+1:

AGPLv3 :+1:

+1 to close

:+1:

:+1:

Vote to close and ban any further suggestions of this proposal.

:-1:

😱

👎

:trollface: :hankey:

:-1:

I fail to see how the Apache license is more restrictive than GPL. I'm going to assume that this is either A) a joke, or B) moronic.

I love how many people do not realize this is a joke

Everyone, don't forget - there is bright side to this proposal! It can only get better from now on.
:-1:

Please do not waste some poor Apple employee's time with a non-sense Pull Request

:trollface:

At best, this is a very bad joke, and at worst, this is an incredibly insensitive trolling attempt. Anyone who's :+1:'ing, consider that you're taking time and attention away from valuable improvements to Swift that people actually care about. Whoever has write access to this repo should lock this PR and close it.

Vote to close, not constructive.

Top kek.
:+1:

@mooman219: Territory-Marking Badge achieved!

:+1:

How dare you to say not constructive? This is GPLphobia!

Another vote to close. This isn't a good joke. We've already created a Pull Request on torvalds/linux on April Fool's to replace GPL with BSD license. Try to be more innovative, GPL guys. :-1:

I'd just like to interject for moment. What you're refering to as Linux, is in fact, GNU/Linux, or as I've recently taken to calling it, GNU plus Linux. Linux is not an operating system unto itself, but rather another free component of a fully functioning GNU system made useful by the GNU corelibs, shell utilities and vital system components comprising a full OS as defined by POSIX.
Many computer users run a modified version of the GNU system every day, without realizing it. Through a peculiar turn of events, the version of GNU which is widely used today is often called Linux, and many of its users are not aware that it is basically the GNU system, developed by the GNU Project.
There really is a Linux, and these people are using it, but it is just a part of the system they use. Linux is the kernel: the program in the system that allocates the machine's resources to the other programs that you run. The kernel is an essential part of an operating system, but useless by itself; it can only function in the context of a complete operating system. Linux is normally used in combination with the GNU operating system: the whole system is basically GNU with Linux added, or GNU/Linux. All the so-called Linux distributions are really distributions of GNU/Linux! :eggplant:

:eggplant:

https://mike-ochmann.de/occupygpl/
#justsayin

@DaKnOb: ... but... but... GPLv3 will protect Swift from Microsoft doing their own version without released source code with incompatible changes.

>all these freedom haters
disgusting
GPL a BEST

@xfix Let them do that.. That way we all benefit from more languages and improvements to existing ones.

Don't be child. :-1:

:-1: give me a break. they just open sourced. be happy apple even did that.

At least this Pull Request helped me find something awesome..

Exquisite meme my friend. :100: :+1:

:+1:

asking someone to use the GPL is #TriggerWarning

LOL :shipit:

:+1:

Present.

👎
This is insane. Vote to close!

:+1:

gr8 b8 m8 i r8 it an 8/8 plz don't h8
:-1:

What a terrible idea. Vote to close.

:innocent: :neckbeard: :+1:

Swift team right now:

:+1:

:+1:

:+1:

:+1:

lol

Vote to paginate PR comments.

:+1:

:+1:

:+1:

:+1:

let jumpingIn = "\u{1F44D}"
print(jumpingIn)

:+1:

This is a little bit immature - unless it's a joke, in which case, pretty amusing but has passed its lifetime and needs to be closed now.
Feel free to use whichever license you feel is best for your own code, whether that's GPL v2, GPL v3, MIT, etc, but allow others such as Apple to do the same. Personally, I find the Apache 2.0 license to be very permissive and give a lot of protection to both contributors and licensees, so I'm glad that Apple has taken this further step towards open-source,

:+1:

:+1:

:-1:

:D LGTM

:+1:

:+1:

:-1:

I think this vote's gonna be a close one

:+1:

![eating popcorn]
(http://gifrific.com/wp-content/uploads/2013/11/Bill-Hader-Eating-Popcorn-Smiling-SNL.gif)

:+1

:-1:
:-1:
:-1:
:-1:
:-1:

:+1:

:+1:

:-1:

:suspect:

:-1:

:-1:

:100: :8ball:

so far
:+1: 85 vs 7 :-1:

:-1:

:+1:

:+1:

:+1:

4 da GPL!
We need 'freedom'!!!!!!!!!!!!!

:+1:

4 da GPL!
We need 'freedom'!!!!!!!!!!!!!

👍

Please close this, as nonsense.

Please close this, as nonsense.

:+1:

Shit, I think I forgot to say :+1: and :eggplant:
Much better.

:+1: AGPL is preferable though

http://i.imgur.com/8FxEa.gif

Just a reminder to owners that GitHub offers the ability to mute the discussion for non-collaborators. No need to close it straight away without time for proper consideration.

@oblitum why shut down the popcorn content?^^

@miko007 no one can think reasonably in such a mess! :-D

:+1:

👎🏻

:+1:
Three hours and so much support for this feature!

GPLv3 would be preferable but hey I'm just happy open sourced something this important. :thumbsup:

GPLv3 would be preferable but hey I'm just happy open sourced something this important. :thumbsup:

I think that WTFPL is better.

I think that WTFPL is better.

I suggest the Anyone But Richard M. Stallman license https://github.com/landondyer/kasm/blob/master/LICENSE

:+1:

GPLv3 license sucks a lot.
BSD 2-clause, 3-clause or even MIT will do the work way better.

:+1:

+1 for MIT

🍄

:+1:

top tier bait

@thagabe I realize this all started as a joke, but how could GPL3 possibly be better than Apache?

Hello everyone.  Please feel free to discuss this possibility on this thread, but please keep in mind that the swift project has a code of conduct.  We expect to you treat people with respect, even if you don't agree with their position.
Thank you.
-Chris

pls go

Well, GPLv3 isn't free as speech as GPLv2 was, you can see why Linus Torvalds didn't update the Linux Kernel license.
GPLv3 it's a back-step compared with the current Apache License.

But Apache is better

:-1:

:+1:

Here is a novel idea.
Multi-license under Apachev2 AND GPLv3

@lattner

GPL v3 master race! :trollface:

:+1:

:+1:

:+1:

@lattner Don't even bother, mark it as WONTFIX and close it.

Response from Apple legal...

:+1::+1::+1::+1:

Only this way can there be freedom. It's what Stallman would want.

@EvelynSubarrow I don't think it's in Apple's best interest to side with Stallman. https://stallman.org/apple.html

:+1:

Stallman, to freedom!

I'll just give another thumbs up just in case...

Witnessed.

+1

I disagree with @mooman219, I think it should be AGPLv3+

:+1:

I wonder who really thinks this is okay.

👍🏿

hasn't gcc functioned perfectly well under the GPLv3+ license? @mooman219

@iataylor Yep.

:+1:

Plot Twist: They go Linus and uses GPLv2 instead.

Honestly I think this switch would be a lot better and help kickstart a community for Swift

woohoo! :clap: :clap:

Let's not and say we did.

:+1:

:+1:

:-1: Why? How is GPL v3 any better than Apache?

@mooman219 I don't think that this is an appropriate fix but rather a shortcut. It is obvious that a more appropriate solution would be to properly sign the copyright over to the FSF in order to make it a popper GNU project and to start extending it as the GSS, the GNU swift suit. More here: https://www.fsf.org/licensing/assigning.html
Still a good quick fix for now ;)

:-1: Not constructive.

:+1:

Not constructive.
Reminiscent of popular kids making fun of unpopular kids in grade school.
I don't really have a personal stake in microsoft/apple software projects but my personal view is that GPLv2 and later is appropriate for any project where stakeholders would like to protect their own self interest by preventing others from hiding implementation details of improvements to a community software project.

Gopher 赶来围观.
We really got enough (corporate controlled, pseudo open) languages to maintain and help to prosper - especially not for a company who is heavily aspiring to be the most "controlling" of its users. "Ja mein apple".

Apache 2.0 license is perfectly sane. Why isn't this closed yet?

Not constructive? It'll make swift relevant. Pretty constructive to me.
:+1:

:+1: :-1:

LGTM

:top: :trollface: :clap:

:+1:

JUST DO IT!! (ノಠ益ಠ)ノ

In case someone is missing the great irony: Apache License 2.0 seems to be compatible with GPLv3 as long as the result is licensed under GPLv3. So feel free to fork, relicense, and build a better open source future.

Apache 2 is GPLv3 compatible.  Why bother?

:+1: no brainer

👍🏻

Nope

Guys, you are painting the os community in the best of all colors. This is professional? Sounds more like morons...

:+1:

If GNU/FSF compatibility is what you want, Apache is compatible with GPL v3.
If you really, really want to have the GPL, you could dual-license it.

👍🏼

:+1:

5 star, would open source again.

:+1:

:+1:

Can someone please explain this joke to me? 😓

There is no joke only a wagon full of morons...

23333

:+1:

Believe or not, all these things are to be GPL :laughing:   ![agent_smith] (http://vignette4.wikia.nocookie.net/matrix/images/e/e2/SMITHCLONES.jpg/revision/latest?cb=20141209134647)

@TiaLapis Anyone who thinks this PR is actually representative of the open source community at large is an oblivious tool. I'd like to believe that the Venn diagram of people who are that out of touch and the people who actually bother to read and comment PR comment threads wouldn't even intersect, but I suppose there are outliers.
AIl I see here is people having a good chuckle, and adding a "me too" comment.
It's people like @oblitum who are far more dangerous, wishing to set a precedent of silencing the community voice. This is hardly the BumbleBee fail or Steam fail yet.  We shouldn't need to resort to restricting the conversation. We should be self policing.

:+1:

Okay Internet,, you can stop now. Let's take this seriously.
First, there's nothing wrong with keeping this Apache 2.0. [It's compatible with GPL 3.}(http://www.gnu.org/licenses/license-list.html#apache2) If someone wants to borrow the compiler source code in their GPL 3 product, they can do so.
Also if Swift requires its own runtime, it would be best to not license that runtime under the GPL, as if you do so, every single Swift program must also be GPL. I believe bison has a clause that licenses the bison-generated output code freely for this reason.
Third, the proposed change violates the GPL's own license. You are not allowed, as clearly stated at the beginning of the file, to make edits to the GPL itself. This pull request changes the file header and changes the license copyright from the Free Software Foundation to Apple.
If this is all some big joke - that is, if you're all out to just make fun of the GPL - then please, continue playing with matches.  Second, you might prevent further open source contributions by Apple themselves. Third, it makes actual legitimate free and open source software efforts look bad.
That is all.

woooow~

I lol'd


add $stateChangePermissionStart.

If server API response like below format.
{
  "id": 1,
  "name": "flyskyko",
  "role": "admin"
}

State like
$stateProvider.state({
  name: 'admin',
  data: {
    permissions: {
      only: ['owner', 'admin']
    }
  }
});

Permission like
Permission
  .defineRole('owner', function () {
    memberResource.get({id: 1}).$promise.then(function(member) {
      if (member.role === 'owner') {
        $q.resolve();
      } else {
        $q.reject();
      }
    });
  .defineRole('admin', function () {
    memberResource.get({id: 1}).$promise.then(function(member) {
      if (member.role === 'admin') {
        $q.resolve();
      } else {
        $q.reject();
      }
    });
  })

If user's role is member, angular-permission call both function of owner and admin.
It makes two request.
If I use a service for current user information, It also have a problem.
I want to check a permission every change of state that have a permissions.
But, current version of angular-permission have a no point to refresh a current user information.
Because of this, I add a $stateChangePermissionStart.

I think this is ok, though I'm seeing some merge conflicts, can you rebase your branch to the current development and update the PR?

I'm done ;)

Still seing merge conflicts, maybe because I just merged your previous PR? lol

OK, I will resolve conflicts.
나의 iPhone에서 보냄

오전 4:31 Rafael Vidaurre<EMAIL_ADDRESS>작성:

Still seing merge conflicts, maybe because I just merged your previous PR? lol
—
Reply to this email directly or view it on GitHub.

Thanks for this contribution. merging


GET /slp/txDetails/{txid} return traceback data

Call /slp/txDetails/d70af8576a059b24d831450ea9e4f6c192089212fc7469e3a51d2a771362e5d8 returns traceback data:
{
  "error": "TypeError: Cannot read property 'in' of undefined\n    at
/var/www/rest.bitcoin.com/dist/routes/v2/slp.js:1924:34\n    at step
(/var/www/rest.bitcoin.com/dist/routes/v2/slp.js:43:23)\n    at Object.next
(/var/www/rest.bitcoin.com/dist/routes/v2/slp.js:24:53)\n    at
/var/www/rest.bitcoin.com/dist/routes/v2/slp.js:18:71\n    at new Promise
(<anonymous>)\n    at __awaiter
(/var/www/rest.bitcoin.com/dist/routes/v2/slp.js:14:12)\n    at formatToRestObject
(/var/www/rest.bitcoin.com/dist/routes/v2/slp.js:1917:12)\n    at
/var/www/rest.bitcoin.com/dist/routes/v2/slp.js:1844:42\n    at step
(/var/www/rest.bitcoin.com/dist/routes/v2/slp.js:43:23)\n    at Object.next
(/var/www/rest.bitcoin.com/dist/routes/v2/slp.js:24:53)"

}

This issue needs further investigation:

Clear steps on how to reproduce this issue
What is the expected result?
How is the actual result different than the expectation?

The reason the traceback error message is displayed is because the TXID is not an SLP transaction.
Here is the endpoint which re-creates this issue:
https://rest.bitcoin.com/v2/slp/txDetails/d70af8576a059b24d831450ea9e4f6c192089212fc7469e3a51d2a771362e5d8
Here on the block explorer you can see that this is not an SLP transaction:
https://explorer.bitcoin.com/bch/tx/d70af8576a059b24d831450ea9e4f6c192089212fc7469e3a51d2a771362e5d8

The scope of this issue is update the /v2/slp/txDetails/ endpoint to return an error message like 'not an slp transaction' in this scenario. Any PR fixing this issue should include unit and integration tests for this use case.


Suppress all job files, just output to CLI

Dropbox is unwieldy without the use of its API, and this seemed like the most feature-complete tool I could find. I don't really need all the logs and reports for the operation I have in mind, which is a scheduled task that parses the json from the command line output through jq.
Could you add a new common parameter parameter to suppress the creation of all job files associated with commands it's used on?

Thank you for the request. I'll add the option in the future release.
For the temporary workaround, there is a configuration that automatically removes older job files (+7days old) at job start.
tbx config enable -key ingredient.bootstrap.opt_in_feature_autodelete

watermint toolbox 98.8.1112
===========================

© 2016-2021 Takayuki Okazaki
Licensed under open source licenses. Use the `license` command for more detail.

Removing old job data if it found.
Auto deletes old job history data if a job is older than 7 days.
Automatic delete may cause loss of your data. Please keep backup those files before enabling this feature if you needed.
YES     <--- "Type YES"

Hope this will also helps.

@watermint I'm not getting any output using tbx sharedlink file list -url URLHERE -retain-job-data none -output json
When using the same command, just without -retain-job-data none it works just fine.


how to add spaces as pairs when inside a pair?

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md

Module(s)
mini.pairs
Description
Thanks for the excellent plugin! One small question though, how do I configure mini.pairs to make a pair of spaces but only when inside another pair? For example, if I enter:
{{ |

(where | is the cursor), I want it to output:
{{ | }}

Obviously, I do not want a pair of spaces when inserting something like:
text |

Obviously, I would like this for any char that is recognized as a pair, not just {.
Is this doable as is w/ a clever mapping? Or would you have to implement this in plugin code? I feel like the sample mapping for < in the wiki comes close but I can't figure out how to alter that to this need.
Thanks!
As an aside, while looking at the wiki example for < I realized I don't know how to add additional chars to the recognized pairs. The wiki says:
The following pairs are respected: `()`, `[]`, `{}`, `""`, `''`, `\`\``.

But how would I add <> or '%%' (or some other arbitrary pairing)  to that list? Is there a config var for it that I missed?

Thank you for your kind words!
 I might rethink this in future, because coming back to it, this might be a little bit heavy on user-friendliness.
So about spaces. There are three actions supported: open(), close(), closeopen(). All of them work if cursor neighborhood (characters to left and right of cursor) is matched with supplied twochars_pattern (which is a Lua pattern). Unfortunately, Lua patterns don't seem to support alteration. So user can't say "match if neighborhood is this, or this, or this". The closest behavior to this might be "match if left character is one of these and right character is one of these". To add this behavior to space which checks for ([{ to the right and )]} to the left, make a standard Neovim mapping:

In Lua:vim.api.nvim_set_keymap('i', ' ', [[v:lua.MiniPairs.open('  ', '[%(%[{][%)%]}]')]], { expr = true, noremap = true })

In Vimscript:inoremap <expr> <space> v:lua.MiniPairs.open('  ', '[%(%[{][%)%]}]')

With <> everything is the same: make mappings. You, probably, would want something like this:

In Lua:vim.api.nvim_set_keymap('i', '<', [[v:lua.MiniPairs.open('<>', '[^\\].')]], { expr = true, noremap = true })
vim.api.nvim_set_keymap('i', '>', [[v:lua.MiniPairs.close('<>', '[^\\].')]], { expr = true, noremap = true })

In Vimscript:inoremap <expr> < v:lua.MiniPairs.open('<>', '[^\\].')
inoremap <expr> > v:lua.MiniPairs.close('<>', '[^\\].')

A big NOTE though. Currently all this does is mapping a key to an action. To make <BS> and <CR> respect new pairs, you need to remap them accordingly (supply full table of cursor neighborhoods in which those should act).

excellent, thank you! i have this working as desired now.

@hunleyd, wanted to mention that thanks to this issue I decided to slightly redesign mapping process in 'mini.pairs' to make it (hopefully) more user-friendly. Now you can make global mappings in config and they will be automatically registered for <BS> and <CR> (if not changed explicitly). Also work with pair mappings now should be done with MiniPairs.map(), MiniPairs.map_buf(), MiniPairs.unmap(), MiniPairs.unmap_buf().
For example, global mappings for  , <, and > can look something like this:
  require('mini.pairs').setup({
    mappings = {
      [' '] = { action = 'open', pair = '  ', neigh_pattern = '[%(%[{][%)%]}]' },
      ['<'] = { action = 'open', pair = '<>' },
      ['>'] = { action = 'close', pair = '<>' },
    },
  })

Also, all previous mappings (except ones with MiniPairs.bs() and MiniPairs.cr() which use custom pair list) still work as before.

Hi, I am trying to achieve auto-spacing inside a pair of $. This is essential for typst setup.
However, this setup does not work. I tried to substitute the neigh_pattern as %(%) and it just works for () pairs. Could you help me on that?
require("mini.pairs").setup({
  mappings = {
    [" "] = { action = "open", pair = "  ", neigh_pattern = "%$%$" },
    ["$"] = { action = "closeopen", pair = "$$" },
  },
})

require("mini.pairs").setup({
  mappings = {
    [" "] = { action = "open", pair = "  ", neigh_pattern = "%$%$" },
    ["$"] = { action = "closeopen", pair = "$$" },
  },
})

With this exact setup everything seems to work as expected. Here is the demo:
https://github.com/user-attachments/assets/f4273a16-4d14-4835-8915-8d2312cc719b
Does :imap <Space> show the mapping from 'mini.pairs'?

Does :imap  show the mapping from 'mini.pairs'?
Yes, it shows:

i  <Space>     * v:lua.MiniPairs.open("  ", "%$%$")
                 Open action for "  " pair

But I can't get the auto spacing work.

Does :imap  show the mapping from 'mini.pairs'?

Yes, it shows:
i  <Space>     * v:lua.MiniPairs.open("  ", "%$%$")
                 Open action for "  " pair

But I can't get the auto spacing work. I'm on neovim 0.10.1

I am not sure what to tell here. With this mapping for <Space> in Insert mode it should turn $$ into $  $ when pressing <Space> in between $$. Just like in demo.
I guess the best suggestion is to try reproducing with only 'mini.pairs' enabled. It should not reproduce. And after that try bisecting the config until you find the relevant part that makes it work as you see.

@aik2mlj I also ran into this issue with spaces. For me it was because of this and this in LazyVim. I managed to fix this by removing $ from the skip_next pattern:
{
  "echasnovski/mini.pairs",
  opts = {
    skip_next = [=[[%w%%%'%[%"%.%`]]=],
  },
}

and this was my config:
local pairs = require("mini.pairs")
pairs.map_buf(bufnr, "i", " ", { action = "open", pair = "  ", neigh_pattern = "%$%$" })
pairs.map_buf(bufnr, "i", "$", { action = "closeopen", pair = "$$" })


"IndexError: list index out of range" when attempting to run Ruby using debugger

I have recently started evaluating Sublime Text for some work we are doing in Ruby. I installed the sublime_debugger and when executing a test program (see below), I get an error in the console. "IndexError: list index out of range".
I should note that I am running a version of Ruby (2.1.2) which is technically unsupported by Sublime Text Debugger, however, the full minor (2.1.0) appears to be supported according to the contents of Ruby Debugger.sublime-settings. In order to allow 2.1.2 to be used I changed the following line in Ruby Debugger.sublime-settings
  // Which ruby version are supported, by default listed here are the versions
  // we already have checked.
  // 2.1.2 Added Oct 22 by jee
  "supported_ruby_versions": ["2.1.2","2.1.0", "2.0.0", "1.9.3"],

Here are my specs:

Item
Version

OS
Ubuntu 12.04.5 LTS

Sublime Text
<IP_ADDRESS>1

Ruby
ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-linux]

Python
2.7.3

Sublime Debugger
https://github.com/shuky19/sublime_debugger/commit/2f0ef5f56124540de26c4187628e0d0658a301da

Gems
bigdecimal (1.2.4)
bundler (1.6.2)
bundler-unload (1.0.2)
byebug (3.5.1)
clipboard (1.0.5)
coderay (1.1.0)
columnize (0.8.9)
debugger-linecache (1.2.0)
debugger-ruby_core_source (1.3.5)
diff-lcs (1.2.5)
executable-hooks (1.3.2)
gem-wrappers (1.2.4)
io-console (0.4.2)
json (1.8.1)
method_source (0.8.2)
mini_portile (0.6.0)
minitest (4.7.5)
monads (0.0.1)
nokogiri (<IP_ADDRESS>)
pry (0.10.1)
pry-byebug (2.0.0)
psych (2.0.5)
rake (10.1.0)
rdoc (4.1.0)
rspec (3.0.0)
rspec-core (3.0.4)
rspec-expectations (3.0.4)
rspec-mocks (3.0.4)
rspec-support (3.0.4)
rubygems-bundler (1.4.4)
rvm (<IP_ADDRESS>)
slop (3.6.0)
test-unit (<IP_ADDRESS>)
uri_template (0.7.0)

Test program being used:
TestMe = Struct.new(:value) do
	def repeat
		[value, value, value].join('/')
	end
end

puts "Hello World"

t = TestMe.new('hello')

puts t.repeat
puts t.repeat

Full call stack from console:
Traceback (most recent call last):
  File ".\threading.py", line 532, in __bootstrap_inner
  File ".\threading.py", line 484, in run
  File "./debug_command.py", line 92, in <lambda>
    SublimeHelper.set_timeout_async(lambda file_path=file_path,bundle=use_bundler, args=arguments: self.start_command_async(file_path, bundle, *args), 0)
  File "./debug_command.py", line 105, in start_command_async
    self.debugger.run_command(DebuggerModel.COMMAND_START, PathHelper.get_pwd(file_path), file_path, *args)
  File "./debugger/ruby_imp/ruby_debugger.py", line 47, in run_command
    RubyDebugger.COMMANDS[command_type].execute(self.connector, *args)
  File "./debugger/ruby_imp/ruby_custom_debug_command.py", line 10, in execute
    self.lambda_command(debugger_constroller, *args)
  File "./debugger/ruby_imp/ruby_debugger.py", line 25, in <lambda>
    DebuggerModel.COMMAND_START:RubyCustomDebugCommand(lambda debugger_constroller, *args: debugger_constroller.start(*args)),
  File "./debugger/ruby_imp/ruby_debugger_connector.py", line 47, in start
    self.start_process(current_directory, file_name, args)
  File "./debugger/ruby_imp/ruby_debugger_connector.py", line 106, in start_process
    directory = " '-C"+sublime.active_window().folders()[0]+"'"
IndexError: list index out of range

Value of variables extracted by adding print statements:
	def start_command(self, file_name, use_bundler=False):
		is_legal, file_path, arguments = PathHelper.get_file(file_name, self.window)
		print 'file_name={0}'.format(file_name)
		print 'file_path={0}'.format(file_path)
		print 'use_bundler={0}'.format(use_bundler)
...

file_name=/home/john/Documents/development/ruby-monads/sandbox2.rb
file_path=/home/john/Documents/development/ruby-monads/sandbox2.rb
use_bundler=False

Do you have any suggestions for resolving this issue? Do you require any further information or tests on my part?

Hi, i know this comes a year later, but did you ever resolve this issue?, i have this problem right now.
thanks


How to edit account component?

hi,
trying to edit the account components to add fields, but i cannot track the code back far enough, i have found onupdate(), but then i just hit a wall. do you have documentation that details things like this?
thanks!

See OB-10 and OB-18 for details on this
http://octobercms.com/support/article/ob-10
http://octobercms.com/support/article/ob-18
You either need to add the fields as "fillable" or roll your own handler.

@daftspunk how to "roll your own handler"?
I have extended this plugin using my custom Profile model (like in your video). Now, on the frontend, I want to add the ability to change my custom fields from related profiles table. I added relation between User and Profile, it works. But now I need to add my custom logic to update related Profile model when user change its fields. How to extend/override the onUpdate method?
Thanks!

Hi @iboved, you can extend handlers by defining a higher priority handler. So for example in your page code,
url = "/mypage"
==
// Higher priority local handler
function onUpdate()
{
    // Call the component's handler
    $this->myComponent->onUpdate();
}
==
...


Emit error event for invalid requests (instead of crashing)

Turns out this is a duplicate of #66, I guess I should probably have checked my mails first :)

Yeah no problem, was watching the stream and decided to fix it right away :+1: . Thanks for putting in this PR non the less :+1:

@clue The fixes in both are nearly identical, the only main difference are not removing listeners in your PR vs removing listeners in mine.  Lets pick one? :smile: Personally I'm in favor of mine because it stops listening, catches more exceptions (shouldn't matter though). How ever yours also emits $this with the error, could add that to mine. What do you think?

I agree, yours has been there first, which makes mine a duplicated :-)
Now let's look into getting #65 instead :shipit:


fix: Fix if condition when request failure

Hi there, I found an issue that will make the all keda connector not work as expected when the request failure. Here is the fix. 🙏

Thanks for the fix @chenjr0719 🎉 !


hover card v1.1

border let be $primary
add depth effect some like MS-DOS, ncurses ui
depth could be made by black shadow or use texture in the third picture on the floor, yet really don't know its name @XyloDrone may whisper!

I'll see what I can do!


Give option to change the key used for multi-selection

VSCode Version: 1.0.0
OS Version: Widows 10 (1511) x64

The current key, Alt conflicts with the key used for bring out menu bar.
Ref: https://github.com/Microsoft/vscode/blob/master/src/vs/editor/browser/view/viewController.ts#L109

:+1: We need to extract that if/else code into a mouse dispatching rule engine.

could the mouse commands be customised in the keybindings.json? Like:
   "command": "editor.action.insertCursorAtMousePosition",
   "when": "editorTextFocus" }```

I'm (as probably many user are) used to the sublime text keybindings and the keyboard commands are customisable, but the mouse commands are not.

Are there any progress about this? Popping out menu bar is really annoying.

This is super irritating for me since I use the alt + click functionality a lot. For now I've got a workaround in Windows using AutoHotkey that prevents the menu bar from popping up after releasing the Alt key. Just add the following to your AutoHotkey script:
#if WinActive("ahk_exe Code.exe")
	~Alt up::

Warning: you'll only be able to access the menu bar using the View: Toggle Menu Bar command in the command pane.

Related: #3130

https://github.com/Microsoft/vscode/issues/8874 is related and fixed for August.

Done via #27193


Add onInvalid to react props

What:
Adds onInvalid to list of react props to pass through.

Why:
onInvalid is a supported react event, but it isn't documented on the SyntheticEvent page (https://github.com/facebook/react/pull/10554).

How:
Added onInvalid to the react-props.js array.

Checklist:

[x] Documentation
[x] Tests
[x] Ready to be merged
[x] Added myself to contributors table

Codecov Report

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

@@          Coverage Diff          @@
##           master   #322   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          10     10
  Lines         172    172
  Branches       47     47
=====================================
  Hits          172    172

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 3751b39...c006b1f. Read the comment docs.

Right now you can pass through onInvalid through the forwardProps option like this:
glamorous('input', { forwardProps: 'onInvalid' })

But I think it'll make more sense to include this in the default component factory:
glamorous.input

Hi @tvler! Thanks for the PR. Is onInvalid an officially supported react event callback?

Hey! Yep, the event was added in v15 in the PR https://github.com/facebook/react/pull/5187.

Thank you so much!

No problem! Awesome library btw, iFixit's really diggin it 👍

Awesome! Could you add iFixit to the Users.md?


Make Protostream the default marshaller for user types

https://issues.jboss.org/browse/ISPN-10591
Builds upon the commits in https://github.com/infinispan/infinispan/pull/7264, which should be merged first.

run custom performance tests please
ispn_config https://gist.githubusercontent.com/ryanemerson/40e40efb6e73c8c19c8a5d42c3dfe32f/raw/99ded6d69066168d604705dccf9128cc564b63e2/PR-7153.xml
jdg_config https://gist.githubusercontent.com/ryanemerson/df5fd0c76241b9ced6b7d8ea92e1d924/raw/8bc5fe883060fd0a4d674e41fcf606f83e86f5cd/PR-7153-DG.xml
custom_library
entry_factor 8

run custom performance tests please
ispn_config https://gist.githubusercontent.com/ryanemerson/40e40efb6e73c8c19c8a5d42c3dfe32f/raw/99ded6d69066168d604705dccf9128cc564b63e2/PR-7153.xml
jdg_config https://gist.githubusercontent.com/ryanemerson/df5fd0c76241b9ced6b7d8ea92e1d924/raw/8bc5fe883060fd0a4d674e41fcf606f83e86f5cd/PR-7153-DG.xml
custom_library
entry_factor 8

Protostream 4.3.0.Alpha12 is now released!  ProtoStreamTypeIds.WRAPPED_MESSAGE can now be an alias of the newly introduced WrappedMessage.PROTOBUF_TYPE_ID constant to avoid a magic number :)

On hold as I will remove the notion of the user marshaller in this PR.

On hold as I will remove the notion of the user marshaller in this PR.
Does that mean I won't be able to use java serialization or jboss marshalling to my heart's desire? I hope I'm not force to use protobuf only.

@anistor See the discussion on #marshalling and this week's meeting for more details. But in summary, the idea is that if you want those things for embedded mode then you should use AdvancedCache::withEncoding

@anistor See the discussion on #marshalling and this week's meeting for more details. But in summary, the idea is that if you want those things for embedded mode then you should use AdvancedCache::withEncoding

My concern is about actually storing in cache java objects as objects, without using any protobuf at all (for reasons related to hibernate search indexing). Does withEncoding offer that or just sugar coats a byte[]? I'm not familiar with the latest status in this area.

@anistor The ability to configure a user marshaller is in place again, so this PR is good to go from my POV.

I've added some comments, that are very easy fixes. I'm happy with it and it LVVVGTM :)

Updated, thanks for the review @anistor

LGTM. Let's wait for another round of CI.

@anistor CI is good :slightly_smiling_face:

merged. thanks @ryanemerson !


Increase PHP Memory Limit?

Hi Mark,
Great job on this Repo, it's really helpful. This could be a gap in my docker knowledge but using your setup how could I go about changing the php.ini variables so that they won't reset when I upgrade from PHP 7.2-fpm to 7.3?
Many thanks again,
Adam

You can create an "images/php" directory within your project root. Then in your docker-compose.yml file, instead of referencing:
image: markoshust/magento-php:7.1-fpm-9

change it to:
build: images/php

Then within your images/php directory, create a Dockerfile with the contents:
FROM markoshust/magento-php:7.1-fpm-9

COPY conf/php.ini

Then you can define your php.ini file at images/php/conf/php.ini
You can see a similar example of how I am doing this for nginx by checking out the m1 compose setup at https://github.com/markoshust/docker-magento/tree/master/compose/magento-1


Fix some warnings

Most of it is to fix hidden anonymous lifetime that are deprecated and will be remove in rust 2021.

It does not seem to survive the CI, I'd not merge this until later.

On my end, i can't see why the Ci hit the timeout. Do you see the error that did that on your end?

It unhelpfully states
Run timed out after > 72 hours.

I'd postpone this patch till the compiler is more stable and the edition is set in stone, if it isn't something you already built upon other patches.

Can you tried to restart the CI pass on your end, to see if the result will be different?

Coverage increased (+0.009%) to 83.884% when pulling b62acaeac0a8851e82071e3aace410947b49ea33 on remilauzier:master into 45d6754f6389179fac085aedfa97af3b483aa896 on xiph:master.

I have made the CI pass.


Using react-input-mask with mui Autocomplete

Hello!
I have an almost working example of mui Autocomplete with react-input-mask.
https://codesandbox.io/s/kind-hellman-22j39?file=/src/App.tsx
Can someone help me make an example of how this combination can work?

i get the same error after 4 years


[BUG] Targetted builds destroy valid cache entries

Describe the bug
Targetted builds cause previously valid builds to be evicted from teh build cache.
To Reproduce
Steps to reproduce the behavior:

Run yarn build
Run yarn build in packages/examples/lorem-ipsum
Inspect local-build-cache.json

Expected behavior
All previously built projects remain in the build cache, so they aren't needlessly rebuilt.
Desktop (please complete the following information):

OS: Windows/WSL

The latest release changed the structure of the build cache quite a bit (mostly, just emitting a lot of what was not written out before), and as such I moved it to .yarn/yarn.build.json. Partly to make this file more obvious what it is, and where it's coming from. But also to prevent breaking.
I can't seem to replicate this on macOS. Are you able to post the before/after build cache file? And can you try with the latest version.

Aha. I didn't notice the file change and was actually quite confused why my projects refuse to be rebuild (even though I delete the file). I thought this was a new bug.
I will look into this again tonight and you'll have my report in the morning 😄

I haven't noticed any more critical issues like this. I will observe further and report again if needed.


ssh command for rancher-compose

Would be awesome to have an ssh/exec command in rancher-compose to connect to any container from command line. Something like rancher-compose ssh <container-name_index | container_ip > or rancher-compose exec <container> <command>. To have this feature in UI is really cool but when you have to constantly debugging multiple containers with browser is quite painfull

Honestly, I'm not sure if this is even feasible, but I've added it as a feature request. :)

@deniseschannon everything is possible! That's why being a hacker is like being a magician :)
Indeed it would be awesome. The WebUI is quiet poor to execute commands on a container.
I would say exec is better than ssh, because no ssh daemon will be running, and this will use docker exec api behind the scene.
For me this is a major pain point.
To convince you, here is a great talk, from one of the smartest engineer on earth!
https://www.youtube.com/watch?v=sYQ8j02wbCY

Instead of adding this into Rancher Compose, we recommend using the new Rancher CLI which supports rancher exec.


Line numbers in footnote preview misaligned, behind text

Is the bug present when using the default Obsidian theme?
Yes
Is the bug present when snippets and plugins are disabled?
Yes
Minimal theme version
7.7.18
Describe the bug

Write a footnote marker [^someName]
Bring up the footnote preview popup and click on it.
Start writing the footnote text. The line number gets stuck behind the text.

Default Theme:
https://github.com/user-attachments/assets/89bd9716-1e8b-4981-bcdd-8c1698a3bbe0
Minimal Theme:
https://github.com/user-attachments/assets/b4bf3f8a-408a-401c-bcd5-f6c8f3e6c0fb
Debug info
SYSTEM INFO:
Obsidian version: v1.7.3
Installer version: v1.5.8
Operating system: Windows 10 Home 10.0.22631
Login status: logged in
Language: en
Catalyst license: supporter
Insider build toggle: on
Live preview: on
Base theme: adapt to system
Community theme: Minimal v7.7.18
Snippets enabled: 0
Restricted mode: off
Plugins installed: 3
Plugins enabled: 0
RECOMMENDATIONS:
Custom theme and snippets: for cosmetic issues, please first try updating your theme and disabling your snippets. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.

This seems like a bug with Obsidian's new footnote editor — it shouldn't show line numbers


Zappa Undeploy Fails when you have event source as Kinesis

When you have Kinesis as event source  to trigger AWS lambda, while performing "undeploy" , we are having "Key error"  and undpeloy is failing.
We are getting below error while undeploying.
  File "/var/task/venv/local/lib/python2.7/site-packages/zappa/cli.py", line 1087, in undeploy     self.unschedule()  # removes event triggers, including warm up event.   File "/var/task/venv/local/lib/python2.7/site-packages/zappa/cli.py", line 1193, in unschedule     events=events,   File "/var/task/venv/local/lib/python2.7/site-packages/zappa/core.py", line 2460, in unschedule_events     print("Removed event " + name + " (" + str(event_source['events']) + ").") KeyError: 'events
Expected Behavior
zappa undeploy should be success
Actual Behavior
zappa undeploy Failing
Possible Fix
Permanent Solution :
This portion of the code is causing the issue. we should check 'events' before we print this below line.
print("Removed event " + name + " (" + str(event_source['events']) + ").")
https://github.com/Miserlou/Zappa/blob/7012e25e2bcfa8bd0c458622f66ee9682d78af3b/zappa/core.py#L2464
    "events": [
       {
           "function": "functions.lambda_handler",
           "event_source": {
                "arn":  "arn:aws:kinesis:*:*:stream/stream_name",
                "starting_position": "LATEST",
                "batch_size": 1,
                "enabled": true,
           },
           "name": "name_lambda"
       }
    ],

Temporary fix.
change the configuration
"events": [
{
"function": "functions.lambda_handler",
"event_source": {
"arn":  "arn:aws:kinesis:::stream/stream_name",
"starting_position": "LATEST",
"batch_size": 1,
"enabled": true,
"events"= []
},
"name": "name_lambda"
}
],
Steps to Reproduce

Have events in zappa settings like below.
"events": [
{
"function": "functions.lambda_handler",
"event_source": {
"arn":  "arn:aws:kinesis:::stream/stream_name",
"starting_position": "LATEST",
"batch_size": 1,
"enabled": true
},
"name": "name_lambda"
}
],
zappa undeploy

Your Environment

Zappa version used: zappa==0.44.3
Operating System and Python version: lambci/lambda:build-python2.7
The output of pip freeze:
Link to your project (optional):
Your zappa_settings.py:
{
"dev": {
"aws_environment_variables": {
"ENV1": "dev",
"ENV2": "dev"
},
"aws_region": "ap-southeast-2",
"debug": true,
"events": [
{
"function": "functions.lambda_handler",
"event_source": {
"arn":  "arn:aws:kinesis:::stream/stream-dev",
"starting_position": "LATEST",
"batch_size": 1,
"enabled": true,
"events" : []
},
"name": "event_name"
}
],
"keep_warm": false,
"log_level": "DEBUG",
"manage_roles": false,
"memory_size": 128,
"parameter_depth": 1,
"project_name": "project_name",
"role_name": "project_name-role",
"runtime": "python2.7",
"s3_bucket": "project_name-dev",
"timeout_seconds": 300,
"use_apigateway": false,
"use_precompiled_packages": false,
"vpc_config": {
"SecurityGroupIds": [
"sg-xyz"
],
"SubnetIds": [
"subnet-xyz1",
"subnet-xyz2"
]
}
}
}

Getting same error,
confirmed that workaround fixed it 👍

Fixed on #1617


FireOS Outdated Webview

Describe the bug:
Outdated Webview in FireOS results in card not working.  Browsers on the Fire tablet that utilize the OS Webview display an error in the card, but if you install Chrome on the device it works fine.
Use case for issue:  CCH is ideal for use on a tablet interface to Home Assistant, and because apps like Fully Kiosk Browser use the FireOS webview it will not work.  Chrome browser no longer allows a fullscreen mode so it cannot be used for a workaround.
Very possible this is not fixable until Amazon updates the webview version in a future OS update, but wanted to make you aware of it.
Config:
- type: 'custom:compact-custom-header'         main_config: true         options: clock         voice: hide         notifications: hide         clock_format: 12         clock_am_pm: true
Error:
In Fully Kiosk Browser:
Custom element doesn't exist:  compact-custom-header
In Chrome:
Works fine
Versions:
Version of this card:  Latest
Home Assistant version: 0.88.0
Browser type and version:  Fully Kiosk Browser for FireOS, latest
YAML or Storage Mode:  Storage

FireOS webview doesn't support custom elements. Would need to use babel and something like rollup.js.
e.g.
https://github.com/kalkih/mini-media-player/blob/master/package.json
https://github.com/kalkih/mini-media-player/blob/master/rollup.config.js

User pjv from the HA forums was kind enough to port this for legacy devices and he will be trying to keep it current. I do not provide support for this solution.
https://community.home-assistant.io/t/compact-custom-header-custom-user-device-views/83716/371

Legacy version worked like a charm.  Thank you!

Legacy version worked like a charm. Thank you!

Can you talk me through how you implemented this legacy version, step by step please?

If anyone was still having issues with this I just updated the legacy device version. Found here: CCH for older/unsupported devices.


Wallet tests

#4
#10

yes sorry

@gandlafbtc
Should I still work on this?
Do you now work on this?

I'll review it, i thought you're still working on it

finally finished

yeah

@BilligsterUser Since we changed the tsconfigs, have you tested if it still works for both node and browser builds?

rebased,fixed and tested

one more rebase bls :crying_cat_face:

done


Separate error for array fields

Hello. I have some complex validation on array field details[].periods[] I have to check periods do not overlap and display the error message if they do. I can't determine which period is causing the error, so I have to set this error for the entire array field. I don't want to set _error field because it's not global form error. There is an errors object passed to my form, but it's empty all the time and it's not documented so I can't just grab the error I need and pass it as a prop. Is there any way to do so without creating a faux field just for this error?

This is currently not supported, but is on the feature request list. #486

In closing this issue in favor of #486

Good news! Array validation errors in v6.0.0-alpha-7.


docs(body): add example for to_bytes()

cc #2201

Hi dear Sean.
I don't know if this PR helps. I decided to give it a try anyway :-)

Hi Sean :-)
The current state is the closest that I managed to reach executing the doc function. It is failing, but I did not manage to resolve the error no matter what I tried.
The current error is the following:
---- src/body/to_bytes.rs - body::to_bytes::to_bytes (line 21) stdout ----
error[E0433]: failed to resolve: could not find `Client` in `hyper`
  --> src/body/to_bytes.rs:30:21
     |
12 | let client = hyper::Client::new();
     |                     ^^^^^^ could not find `Client` in `hyper`

I tried to resolve it by adding # #[cfg(feature = "full")] or # #[cfg(feature = "client")], bit I did not succeed.
Either I need some guidance, or you can commit directly the changes need. It is your call :-)

@seanmonstar thanx for helping/merging this. Yet, as I stated in my previous comment, the doc tests fail. Running the doc tests locally for master has the following result:
failures:

---- src/body/to_bytes.rs - body::to_bytes::to_bytes (line 19) stdout ----
error[E0433]: failed to resolve: could not find `Client` in `hyper`
  --> src/body/to_bytes.rs:28:21
   |
12 | let client = hyper::Client::new();
   |                     ^^^^^^ could not find `Client` in `hyper`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0433`.
Couldn't compile the test.

failures:
    src/body/to_bytes.rs - body::to_bytes::to_bytes (line 19)

test result: FAILED. 3 passed; 1 failed; 2 ignored; 0 measured; 0 filtered out; finished in 0.25s

error: test failed, to rerun pass '--doc'

Doesn't it matter? Can't it be resolved?


Version 0.4.0

Description

Ordering for challenge list

Testing

[x] Added unit tests
[x] Ran unit tests successfully
[x] Added documentation for public APIs and/or Wiki

          2 Warnings

:warning:
The Pull Request summary does not contain the commit message convention

:warning:
The Pull Request title does not follow the convention [ACCSEC-0000] PR Title text

  Generated by :no_entry_sign: Danger


AsyncSsrManager + FeatureAppLoader: Module fetch error crashes rendering

When loading the serverSrc fails during server side rendering, the renderUntilCompleted of the AsyncSsrManager rejects and rendering of the whole React tree fails.
Steps to reproduce:

Take any integrator capable of SSR (e.g. the SSR demo in this repo)
Specify a URL that returns invalid JS as the serverSrc (e.g. a URL that returns a 404 page)
Render page

Actual result:
Details
:heavy_check_mark: FeatureAppLoader creates Feature App asynchronously
:heavy_check_mark: Because serverSrc is not loaded yet, FeatureAppLoader registers loading promise in AsyncSsrManager
:heavy_check_mark: serverSrc is loaded and module loader throws an error because of invalid JS in serverSrc
:heavy_check_mark: Feature App Registry rejects async creation promise
:x: AsyncSsrManager rendering loop fails

:x: None of the Feature Apps on the page are rendered on server side. Instead an error is displayed.
Expected result:
:heavy_check_mark:  Failing to load the serverSrc should be treated as any other error that occurs while rendering the Feature App. The error should only affect the failed Feature App.
:heavy_check_mark: All other Feature Apps on the page should continue with server side rendering as normal.
Note:

The same thing also happens if a loading promise registered by a Feature App itself fails. Failing data promises because the API did return an unexpected status code or takes to long is normal and from my point of view expected behavior. So a single misbehaving API can completely destroy server side rendering for a complete page.
This issue can be mitigated by rendering each Feature App in isolation. But then this issue still occurs for any nested Feature Apps that are rendered on server side.

Maybe we should use Promise.allSettled here:
https://github.com/feature-hub/feature-hub/blob/11490453001ea2628ecb9aa291d494618f429305/packages/async-ssr-manager/src/internal/async-ssr-manager.ts#L72

Additionally the client side bundle should only be preloaded if SSR succeeds:
Move (+ maybe the same block for CSS, though that doesn't hurt hydration)
https://github.com/feature-hub/feature-hub/blob/11490453001ea2628ecb9aa291d494618f429305/packages/react/src/feature-app-loader.tsx#L146-L148
inside
https://github.com/feature-hub/feature-hub/blob/11490453001ea2628ecb9aa291d494618f429305/packages/react/src/feature-app-loader.tsx#L170-L172
Otherwise there is a hydration error in the demo (which makes sense - if the CSR bundle for the failed FA is preloaded, the FA is rendered immediately during hydration, resulting in more content than what was present during SSR).

@stemey just pointed out that simply doing this would be a breaking change. His project relies on these errors to create an error page that is in turn not cached.
Current behavior could be restored using a custom error UI similar to
<FeatureAppLoader  ...>
  {({error, featureAppNode}) => {
    if (error) {
      throw error;
    }
    return featureAppNode;
  }}
</FeatureAppLoader>

Alternatively renderUntilCompleted could get an option to ignore/permit errors to avoid the breaking change.
What do you think, @unstubbable ?


Fix #10

Fixes #10

Looks like phpunit is causing the php7.0 build to fail should we lower the phpunit version?

That's perfect, thank you :+1:


ddelegation-gov-tab

This makes a new delegation tab under governance. You can search ddelegation in your text editor to more easily see the changes.

nice and simple, love that : )


Link a bank account

A user should be able to link one or more bank accounts to the portal. This would allow users to easily pay any fees they owe. Any money the citizen is owed by the government could also be wired here.

I think a big concern we should address is "auto-pay". I don't really want the government being able to dip their hands in my account at any time. A routing number/account number on file would make it easier to accomplish that.
Perhaps we should have some intermediary?

There may also be some lessons to learn from the IRS's administration of the EIP

This functionality already largely exists with the government. I can already pay the federal government any taxes owed directly from my bank account or credit card, and I get tax refunds direct deposited when I have those. In the spirit of "let's not hold any data we don't absolutely have to (especially sensitive data)" - I think the best thing to do is to see if we can find an API that lets us pass debit/credit card information to the IRS for payments, or sends the information for a specific transaction.
Regardless of whether you trust the government to have full-time direct access to all your money, if we have that kind of information any possible security breach could be catastrophic.


renaming poission into poisson (typo)

Thanks for catching this. I'll verify that everything still builds and runs correctly and merge it in.

Merging. Thank you @jgphpc for going through the trouble of fixing this everywhere.


Z3 error in symbolic testing full test-approve

When running full test for approve() with kore-repl the following error appears:
user error (Unexpected result from the SMT solver:
  Command: (assert (= true (= (ite 32 <0> ) <0> ) ) )
  Expected: success
  Result: (error "line 2674728 column 31: invalid builtin application ite" )

How to reproduce:

Latest k/kore/z3.
KEVM branch symb-testing, commit https://github.com/kframework/evm-semantics/commit/f230d6f735d51e59cb0b21865e9c655dbcdf46c2
Command:

make tests/symb-test/test-approve-spec.k.symb-prove K_OPTIONS="-v --debug --haskell-backend-command \" kore-repl --repl-script <your K_HOME>/haskell-backend/src/main/native/haskell-backend/dist/kast.kscript \"" K_SUBMODULE=<your K_HOME>

Then in kore-repl:
stepf 11000

The task has to be left overnight. The last step alone that generates the error (on node 10857) seems to run in >2h.

This isn't valid SMT-LIB syntax: (ite 32 <0> ). ite takes three arguments, and the first must be a Bool. This was changed in the frontend recently, and I might have missed something when we updated it.

Error is related to minInt/maxInt:
https://github.com/kframework/k/blob/3326d56e55547f489d2cbc7d6f2b0837794011ad/k-distribution/include/builtin/domains.k#L397-L398

The problem is that SMT.AST.nameFromSExpr is used, which discards the user-defined S-expression templates, keeping only the first symbol (in this case: ite). The arguments of the Kore symbol are applied to the S-expression symbol, rather than being used to complete the template. The transformation made by nameFromSExpr is always invalid and that function should be removed.

This isn't really blocking. I solved the issue with a lemma that was necessary anyway.


[libevent] Build error on loongarch64-linux

Copy issue body from /home/loongson/Tool/vcpkg/installed/vcpkg/issue_body.md
### Tasks

Please provide the error log, see #30604 for how to report an issue.

Thanks for posting this issue. Please reopen this issue if this is still a problem for you.


Proper Serialization of Outline View

Outline view isn't serializing/deserializing, so the pane disappears on refresh.

I started fixing this.  It's a little bit of a mess given how outline view is structured, so I've made a quick patch to at least get rid of the console errors for now.  However, the outline view isn't really serializing it's own state, so the status of the show scenes checkbox gets lost.  It would be nice to address this during #20.

I agree that it should be done.  And I'd be happy to take the ticket for it.  To be honest though, I guess I'm a little hesitant about adding more work to that branch.  My personal inclination is to get that piece in and then be able to work on smaller, preexisting issues independently.  Also, I don't know how much work the fix would be.  However, if that's a precondition of getting #20 in, then I'll do it.

If we're worried about it being a blocker for #20, I'm fine addressing it separately/later now that the plugin isn't throwing errors.

Yea, that's pretty much it for me.  I don't even mind doing it as my very next task.  It wasn't until the end there where I realized exactly what the issue was.  And I have other improvement tickets in mind if/when these are accepted... I just don't want to be presumptive.

@superlou looked like you may have fixed this.  Is this resolved now?

I sort of brute forced removed the path that generated errors due to serialization/deserialization simply not existing.  If we aren't seeing any practical issues at this point, it might be worth closing this issue and opening new ones with specific problems as they're discovered.

Well it worked for me both with and without preview open.  However, viewing only a single file in editor.  I'm not sure that the outline currently targets an editor instance by id, so I'm unclear on how it would deserialize with multiple editor panes open.  As long as atom manages focus on editor panes automatically it should appear in same state.

Not even sure that's a significant issue anyway.

Agreed.  Really, I think the outline panel should be moved to the more full featured dock API.  I'll close this issue.


[FEATURE REQUEST #32] On-Premises S3 / S3 Compatible...

Description:
This is a proposition of Polaris core storage implementation, copy of the aws, without the required arnRole parameter, replaced by endpoint, path style, and credentials.
You can choose a strategy for the client calling catalog :

Default option - "vending token" with STS assume role like aws. It is working with MinIO, and should works also with Dell ECS, NetApp StorageGRID, etc...
"vending keys" :
It will disabling Polaris credential "SubScoping", but if you do not care a lot about security

the catalog can send his own keys to the client
you can also store in catalog keys dedicated to clients. You can then revoke them externally without breaking the catalog.

There is also possiblity during creation of the catalog (cli, curl api) to choose between 2 strategies to communicate the S3 access and secret keys :

Default option - by environment name variable.
Polaris need these variables available inside is running context. A kubernetes production deployment should be suited for this configuration (envFromSecrets deployed to Polaris pods)
by direct value ( /!\ can be printed in debug logs or included inside JSON getCatalog API response.

Let me know your opinion about this design proposal.
Thank you
Included Changes:

New type of storage "S3_COMPATIBLE".
Tested against MinIO with self-signed certificate
regtests/run_spark_sql_s3compatible.sh

Type of change:

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

Checklist:
Please delete options that are not relevant.

[x]  I have performed a self-review of my code
[x]  I have commented my code, particularly in hard-to-understand areas
[ ]  I have made corresponding changes to the documentation
[x]  My changes generate no new warnings
[ ]  If adding new functionality, I have discussed my implementation with the community using the linked GitHub issue

Hello,
For reviewers, I have a security concern about this proposition of implementation.

The configurationStorage is communicated and displayed everywhere in Polaris : logs, createCatalog response, getCatalog response...

This configuration store not   a simple role_arn but also secret_keys. It should be possible to filter the sensible data in the logs and in the responses.

I have not find by myself the best place in code to do this.
Maybe it could be also intersting for other storage types to be able to mask some sensible properties.

I guess I don't understand what isn't supported today with catalog-properties. E.g., in https://github.com/apache/polaris/blob/main/polaris-service/src/test/java/org/apache/polaris/service/catalog/PolarisSparkIntegrationTest.java , we use S3MockContainer as an S3 endpoint, which requires the same path-style access and custom enpdoint configuration as what's included here. Can we not follow the same pattern for minio?

Not found how endpoint or other properties can be set from REST API create or update catalog. Only arnRole is accepted as mandatory parameter today in AWS storage type.

As a rule, I think vending static credentials is not a good idea. Some customization for how the STS client is instantiated, possibly with support for custom profiles for different catalogs could make sense. But I think, ultimately, the credentials returned should always be a temporary session token. Even if we just call GetSessionToken without requiring an IAM role, it would vastly more secure than sending raw credentials.

I agree, by default it is STS without role. Raw credentials are poor fallback scenario when STS are not available. There is enterprise context where STS, assumeRole etc are not allowed. Only pair of keys are available. By example, Dell ECS require additional policy to enable STS and assumeRole. Not activated out of the box. I tried to be explicit about this degraded security pattern.

Hello everyone this PR seems to be blocked for a month now, is there anything we can do to make it to the end ? 🙏

Hello everyone this PR seems to be blocked for a month now, is there anything we can do to make it to the end ? 🙏

Sorry for the one-month break. I tried the approaches proposed in the comments.
Refactoring performed ;)

Refactored after many comments :

SKIP_CREDENTIAL_SUBSCOPING_INDIRECTION is replacing the initial 'Strategy options' as requested by @eric-maynard

Come back of RoleARN as optional parameter, because requested in the issue #32

Added 'Region for client' to be aligned with last AWS implementation modifications

Removed the credentials parameters 'by value', only env var name are possible. If parameters are empty, it will fallback to default AWS variables

@collado-mike comments

about 'at least a session token' :
seems to be not available in the S3 compatible softwares I've tested, or I missed the information - only AssumeRole (with empty role or not) is often implemented
about the SKIP_CREDENTIAL_SUBSCOPING_INDIRECTION should be in the catalog properties and not in the storage porperties :
Polaris is not forwarding the catalog properties where it is needed. Maybe it can be adressed later in other PR ?
STS client created inside the core/storage classes, not pass via constructor  :
Looks similar  to the Azure implementation, not the AWS one. I have avoid to modify the 'Service' code in this PR, modifications are limited to REST specs, core Storage and regTest...

Thank you

Ready for review.

Not sure if this is out of scope for this PoC(?), but this PR doesn't contain the corresponding changes for the CLI, yet. This could break some CLI commands. For example, if a catalog with type S3_COMPATIBLE is created, the command polaris catalogs list won't work anymore, even if there are other catalogs with regular storage types.


Incompatibility between latest hugo and wowchemy

hugo fails with multiple errors of this kind:
WARN 2021/10/30 16:36:10 Module "github.com/wowchemy/wowchemy-hugo-modules/wowchemy/v5" is not compatible with this Hugo version; run "hugo mod graph" for more information.
Start building sites …
hugo v0.88.1-5BC54738 linux/amd64 BuildDate=2021-09-04T09:39:19Z VendorInfo=gohugoio
ERROR 2021/10/30 16:36:10 render of "page" failed: execute of template failed: template: project/single.html:5:3: executing "project/single.html" at <partial "site_head" .>: error calling partial: "/tmp/hugo_cache/modules/filecache/modules/pkg/mod/github.com/wowchemy/wowchemy-hugo-modules/wowchemy/v5@v5.0.0-20210830150813-8b6612e7631c/layouts/partials/site_head.html:206:56": execute of template failed: template: partials/site_head.html:206:56: executing "partials/site_head.html" at <resources.Concat>: error calling Concat: resources in Concat must be of the same Media Type, got "text/x-scss" and "text/css"

running hugo mod graph produces:
WARN 2021/10/30 16:36:37 Module "github.com/wowchemy/wowchemy-hugo-modules/wowchemy/v5" is not compatible with this Hugo version; run "hugo mod graph" for more information.
github.com/wowchemy/starter-hugo-academic<EMAIL_ADDRESS>github.com/wowchemy/starter-hugo-academic<EMAIL_ADDRESS>
This is with the latest version of the academic theme (v5.2, cloned today) and the latest hugo release v0.88.1-5BC54738 and go1.17.2.

I think this is because I installed the wrong hugo (didn't install the extended one.) I will close once I've confirmed.

Yup. Don't open issues when you've had very little sleep, people.


[BUG]: Expo SQLite migrations error when altering table

What version of drizzle-orm are you using?
0.29.3
What version of drizzle-kit are you using?
0.20.14
Describe the Bug
Every time I try to alter the table, the migration fails with an unclear error message

Expected behavior
The migration should work as expected without DrizzleError
I'm actually not sure if i'm missing any step, but based on the docs, for schema updates we only need to run drizzle-kit generate
Environment & setup
i have created a repo to reproduce this issues
https://github.com/bryanltobing/expo-sqlite-drizzle-migration-alter-table-issues
How to reproduce:

The working one is in the main branch
checkout to feat/add-description branch to reproduce the error encountered when running the new migration for altering the table.
npx expo start <- to start the app

We've identified an issue with it: the table name was not escaped, and the use of table as a name conflicts with the reserved SQLite word table. We will fix this.
The current workaround is to name your table differently if it's causing any issues.

i'm not sure that's the issue, since in my real app, i don't use table as the table name. and i get the same error

Could you share an sql statement that also triggers this error?

-- 0000_magenta_daredevil.sql
CREATE TABLE `transaction` (
	`id` integer PRIMARY KEY NOT NULL,
	`amount` integer NOT NULL,
	`note` text
);

-- 0001_steady_satana.sql
ALTER TABLE transaction ADD `description` text;

aah, I think I know the problem. I named my table transaction, probably detected as a reserved keyword as well. I've renamed my table to transaksi and removed the old migration SQL files containing transaction keyword. Now, the error is gone.
unfortunately, I had to remove the old migration files, as simply altering the table name didn't work. (result in the same error)
-- 0002_real_quasar.sql
ALTER TABLE `transaction` RENAME TO `transaksi`;

@bryanltobing any news? my table name is not a keyword config and is still failing :c

looks like it's not related to that after all. still failing for me as well, and i don't know why

I have the same issue. Any migrations I'm generating and trying to apply by using the useMigrations hook and I always get the error msg
[DrizzleError: Failed to run the query 'ALTER TABLE `users_table` ADD `createdAt` text NOT NULL;'] Failed to run the query 'ALTER TABLE `users_table` ADD `createdAt` text NOT NULL;'


 I know the documentation for Date says:-

Years between -100_000 and +100_000 inclusive are guaranteed to be representable. Any values outside this range may have incidental support that can change at any time without notice.

but it's not obvious from the signature nor from the documentation of that method that it can potentially overflow.

That's a risk you take when you go outside the range that has guaranteed support. If you stay in the ±100,000 year range, the behavior will work. And as it currently stands, you could actually go well beyond the age of the universe and have it work as expected (though there's no guarantee that will continue to be the case). This would fall under the "may have incidental support" part; the implication being that it also may not work.
Because this deals exclusively with data outside the supported range, I'm going to close this.

I know but considering that overflows in dates and times can have serious security consequences, IMHO it's safer to return None or an Error when one goes beyond the guaranteed times.

Sure, that's an option, but then anyone staying within the guaranteed range has to handle a case they'll never encounter. I don't want to punish people for following guarantees.
It's a guaranteed range for a reason — any values outside that may or may not work. The only thing I can guarantee in those situations is memory safety. If you're coding something that is taking user timestamps as input, you could certainly construct the maximum guaranteed OffsetDateTime, get the timestamp of that, and check. But that's an issue with user input verification, not time.
You'll need a very strong argument to convince me I'm wrong here, as I am of the opinion that anything outside the guaranteed range is the callers responsibility to ensure correctness of.

You'll need a very strong argument to convince me I'm wrong here

I'm not trying to convince you into doing anything nor do I think you are wrong. I certainly understand your point of view and I respect it. This crate is awesome as it is. As a user, I would be doing myself and the community at large a disservice if I saw a potential to make it even better and I kept quiet. I'm simply trying to explore this potential and see if it is something you and the community might see as desirable.

as I am of the opinion that anything outside the guaranteed range is the callers responsibility to ensure correctness

This is true but there is no harm in going an extra step in ensuring that users use the library safely. In fact, this is something I really appreciate about Rust's ecosystem. Take chrono, for example. from_timestamp panics instead of overflowing. If one doesn't want to risk a panic, they can use from_timestamp_opt instead, which returns an Option. I'm not saying this is what we should do. In fact, I'm not a fan of panicking in libraries. Panicking has its own issues. This is just an example of one library taking that extra step.

It's a guaranteed range for a reason — any values outside that may or may not work

This sounds like undefined behaviour and frankly it scared me a little when I read that in the Date documentation even though there are no memory safety issues involved. Ideally every user should read the documentation before using a library but we all know that's not always the case. I'm pretty sure not every user of the library knows about this guarantee. Especially since it's not prominently displayed in the README nor the overall documentation of the crate (https://docs.rs/time/0.2.6/time/index.html).

Sure, that's an option, but then anyone staying within the guaranteed range has to handle a case they'll never encounter. I don't want to punish people for following guarantees.

 One way to mitigate this is to provide a checked variant of the method like Duration does for arithmetic operations.
Personally, my proposal would be to rename this method to from_unix_timestamp_unchecked, which clearly communicates to the user that it may or may not work for certain inputs, and then re-implement from_unix_timestamp to return Result<Self, ConversionRangeError> or something like that. If this is something you would consider, I can gladly put up a pull request. I know _unchecked is usually used for unsafe APIs but while this doesn't have any memory safety issues, the name still makes sense. The input hasn't been checked to see if it's within the guaranteed range plus an overflow here potentially has dire security consequences.
PS: To explain where I'm coming from and what motivated opening this issue in the first place, I had to check the source code to see if from_unix_timestamp can overflow. With the proposed API change or other such similar variation, this wouldn't be necessary.

This is true but there is no harm in going an extra step in ensuring that users use the library safely. In fact, this is something I really appreciate about Rust's ecosystem. Take chrono, for example. from_timestamp panics instead of overflowing. If one doesn't want to risk a panic, they can use from_timestamp_opt instead, which returns an Option. I'm not saying this is what we should do. In fact, I'm not a fan of panicking in libraries. Panicking has its own issues. This is just an example of one library taking that extra step.

I considered including panicking in my previous response, but there were discussions before 0.2 was released regarding panicking methods (they're actually deprecated now).

This sounds like undefined behaviour

I mean, it is undefined. It's as much undefined as if there were a Time that had the seconds set to 98. Valid memory and consistent behavior, but still undefined.

 One way to mitigate this is to provide a checked variant of the method like Duration does for arithmetic operations.
Personally, my proposal would be to rename this method to from_unix_timestamp_unchecked, which clearly communicates to the user that it may or may not work for certain inputs, and then re-implement from_unix_timestamp to return Result<Self, ConversionRangeError> or something like that. If this is something you would consider, I can gladly put up a pull request. I know _unchecked is usually used for unsafe APIs but while this doesn't have any memory safety issues, the name still makes sense. The input hasn't been checked to see if it's within the guaranteed range plus an overflow here potentially has dire security consequences.

I wouldn't be opposed to having a method like fn try_from_unix_timestamp(timestamp: i64) -> Result<Self, ComponentRangeError>. I would have to think about the variety of use cases before making that the default though (and it would also require a major version bump). Feel free to throw together a PR if you'd like!

PS: To explain where I'm coming from and what motivated opening this issue in the first place, I had to check the source code to see if from_unix_timestamp can overflow. With the proposed API change or other such similar variation, this wouldn't be necessary.

I can certainly add a note to that method specifically, since it's the only way to construct an OffsetDateTime aside from .using_offset/.assume_offset.


Environment usage

Is there a documentation on using the environment for use with custom RL agents?

If you're interested, I've written a library with collaborators that allows you to more easily implement custom RL agents in these gridworlds.  This commit was the last one for that repo that used the pycolab-style API included here.  In particular, this file demonstrates how to use the environment in common training loops (in this case, for use with PPO and DQN style training loops).
In our more recent version of that library, we ended up wrapping the gridworlds inside a Gym API so that we could eventually drop in existing agent code written for Gym.  You can find that here.

Thanks for the prompt reply. It's much better than how I was using this work previously.
environment_name = "side_effects_sokoban"
env = factory.get_environment_obj(environment_name)
actions = [Actions.LEFT,Actions.RIGHT,Actions.UP,Actions.DOWN]
env.reset()
for action in actions:
    timestep = env.step(action)
    print(action)
    print(timestep.reward)
    print(timestep.observation)
    episode_return += timestep.reward if timestep.reward else 0

Just following up on same question, there are so many examples on gym environments but I didn't find any  example of agent applied to gridworlds.
Gridworlds are more valuable to me, would be great if anyone could share any simple example of agent use on gridworlds.


REDO_CONFIG_PATH redundant if REDO_ALIAS_PATH set

If an alias file is set, the program just creates an empty directory at REDO_CONFIG_PATH. Maybe I care a bit too much about the organization of my .config dir

That shouldn't be the case. I will fix this in the next release

I'm closing this since the redo directory can be used in the future for other configurations, so it is nice to already have it in place.


Open InMemoryEventStorageEngine for extension

Simplify implementation of custom in memory solutions by opening the private final maps.
This PR resolves #948

Moving this issue to release 4.2 as this is still under discussion, and in favor of getting 4.1 out.

Closing the pull request, as the necessity of it has been resolved (as has been discussed in #948).


[#113] Updates supported dotnet framework from 7.x to 8.x

Purpose
Updates .Net API backend part of the sample 2-Authorization/2-call-api-angular tutorial from deprecated .Net7 to supported, latest .Net8 so that new users can play, too. This addresses my issue #113
Does this introduce a breaking change?
[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?
[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[x] Other... Please describe:
   Updates codebase to support latest .Net framework

How to Test

Get the code

Run the sample 2-Authorization/2-call-api-angular/API/ToDoListAPI with the normal dotnet run

Test the code

dotnet run

What to Check
Verify that the following are valid

No messages about .Net 7 framework not found and instead a message like the following shows:

✗ dotnet run
info: Microsoft.Hosting.Lifetime[14]
      Now listening on: https://localhost:44351
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Development
info: Microsoft.Hosting.Lifetime[0]
      Content root path: /Users/bronius/projects/sandbox/ms-identity-ciam-javascript-tutorial/2-Authorization/2-call-api-angular/API/ToDoListAPI

Other Information
This only updates the code sample in the one example in this repo. There may be others.

@microsoft-github-policy-service agree


logo is not visible on iOS fullscreen

Expected Behavior
On iOS devices, I want the video logo set for the video to be visible also in fullscreen mode.
Actual Behavior
Logo dissapears in fullscreen mode, on iOS mobile deviced.
Environment

iOS, iPhone 13
iOS 16.13.1
Safari, Chrome
"react-jw-player": "^1.19.1"

It is not reproducible in Safari responsive mode on a macbook

Could you attach a screenshot?

Here's a screenshot from iOS 17, real device

And here is an Android - example of expected result


Document how to enable the option to add a new user

The documentation mentions that a new user should be created that will handle the MQTT messaging, but recent versions of Home Assistant disable the option to add new users by default. This is only available for users that have enabled "Advanced Mode".

Hi @pfrenssen,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!


[2.1.0] Initialize tenancy before executing controller constructors

Fixes #168
TODO:

[ ] Update install command?
[ ] Update docs

Just tested this in a fresh Laravel application and everything seems to work now. Central/tenant routes 404 on wrong domains and tenancy is initialized before the constructor is executed.
This is how the request lifecycle works now, top to bottom:

global middleware: if the current route is not exempt from tenancy, initialize tenancy
router
controller constructor
route middleware: PreventAccess

When visiting a central route from a tenant domain, the constructor would be executed prior to the route middleware terminating the request. As long as the constructor does what it should do -- dependency injection and controller-specific middleware -- there should be no issues with it. I can only imagine this being problematic if the constructor created some DB records prior to the request being terminated.
@drbyte Can you test the dev-controller-constructor version constraint?

Works great!


feat: add new afterFinalizeTargetMatrix hook

Ref: https://github.com/electron/forge/pull/3006

🚲🏚 hook name:

success
complete
allDone

Something along those lines.

@malept this hook is called before any packaging is actually done

this hook is called before any packaging is actually done
Hrm, I misread the Forge issue. afterTargetCalculation or something similar?


Backport Kafka access log to v0.12

Issue #1937 Backport Kafka access log to v0.12
Fixes: #1937
Kafka access log support

@raybejjani @jrajahalme I need an approval from proxy side to merge this..please take a look.


docs: Add Jupyter Notebook Meeting Mins for 20.3.22

Description
Pull request is required to add meeting minutes for Jupyter Notebook Meeting on 20.3.22. Non-code based documentation.
Fixes # (issue)
Nil
Please delete options that are not relevant.

[X] Documentation (update or new)

How Has This Been Tested?
N/A
Testing Checklist:
N/A
Checklist:
Nil apply

ISSUE with submission.
PR Re-submitted under PR 20


builkio: Add schedule control statements.

PR: https://github.com/cockroachdb/cockroach/pull/51896
From release notes:

Implemented schedule control statements to pause, resume, or delete scheduled jobs. [#51896][#51896] {% comment %}doc{% endcomment %}

New pages needed:

PAUSE SCHEDULE
RESUME SCHEDULES
DROP SCHEDULE


v. 1.1.0 disables debug mode

Hey there,
I just recognized that debug: true stops working as expected after updating to version 1.1.0, although process.NODE_ENV is set to development on my end. The console doesn't output anything. Reverting back to 1.0.4 fixes this. Anything else seems to work on version 1.1.0. If I can assist anything further in debugging please let me know.
Cheers & have a nice weekend!

Thanks for the report, I'll have a look on Monday 👍


refractor: layer0 to edgio

Hey, so I created hexo connector with Edgio to ease the deployment process: https://docs.edg.io/guides/changelog#:~:text=[5.X] Add Hexo Connector (With Integration Tests) (%231548) %40rishi-raj-jain
Updated the guide to be even shorter and easier to deploy.

Thank you 🙏🏻

and just today this went live


IE11 not working even after adding polyfills.ts

Bug, feature request, or proposal:
It works in all other except IE11 and < IE 11
What is the expected behavior?
Should load UI on IE
What is the current behavior?
Template parse errors:
Can't bind to 'state' since it isn't a known property of 'mat-pseudo-checkbox'.

If 'mat-pseudo-checkbox' is an Angular component and it has 'state' input, then verify that it is part of this module.
If 'mat-pseudo-checkbox' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message.
To allow any property add 'NO_ERRORS_SCHEMA' to the<EMAIL_ADDRESS>of this component. ("<mat-pseudo-checkbox *ngIf="multiple" class="mat-option-pseudo-checkbox" [ERROR ->][state]="selected ? 'checked' : ''" [disabled]="disabled"><span class="mat-opti"): ng:///MatOptionModule/MatOption.html@0:73
Can't bind to 'disabled' since it isn't a known property of 'mat-pseudo-checkbox'.
If 'mat-pseudo-checkbox' is an Angular component and it has 'disabled' input, then verify that it is part of this module.
If 'mat-pseudo-checkbox' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message.
To allow any property add 'NO_ERRORS_SCHEMA' to the<EMAIL_ADDRESS>of this component. ("do-checkbox *ngIf="multiple" class="mat-option-pseudo-checkbox" [state]="selected ? 'checked' : ''" [ERROR ->][disabled]="disabled"></"): ng:///MatOptionModule/MatOption.html@0:109
'mat-pseudo-checkbox' is not a known element:
If 'mat-pseudo-checkbox' is an Angular component, then verify that it is part of this module.
If 'mat-pseudo-checkbox' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message. ("[ERROR ->]<mat-pseudo-checkbox *ngIf="multiple" class="mat-option-pseudo-checkbox" [state]="selected ? 'checked"): ng:///MatOptionModule/MatOption.html@0:0
Can't bind to 'ngIf' since it isn't a known property of 'mat-pseudo-checkbox'.
If 'mat-pseudo-checkbox' is an Angular component and it has 'ngIf' input, then verify that it is part of this module.
If 'mat-pseudo-checkbox' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the<EMAIL_ADDRESS>of this component to suppress this message.
To allow any property add 'NO_ERRORS_SCHEMA' to the<EMAIL_ADDRESS>of this component. ("<mat-pseudo-checkbox [ERROR ->]*ngIf="multiple" class="mat-option-pseudo-checkbox" [state]="selected ? 'checked' : ''" [disabled]="d"): ng:///MatOptionModule/MatOption.html@0:21
Property binding ngIf not used by any directive on an embedded template. Make sure that the property name is spelled correctly and all directives are listed in the<EMAIL_ADDRESS>("[ERROR ->]<mat-pseudo-checkbox *ngIf="multiple" class="mat-option-pseudo-checkbox" [state]="selected ? 'checked"): ng:///MatOptionModule/MatOption.html@0:0
Can't bind to 'matRippleTrigger' since it isn't a known property of 'div'. ("n class="mat-option-text">
][matRippleTrigger]="_getHostElement()" [matRippleDisabled]="disabled || disableRipple">"): ng:///MatOptionModule/MatOption.html@0:257
Can't bind to 'matRippleDisabled' since it isn't a known property of 'div'. ("/ng-content>
][matRippleDisabled]="disabled || disableRipple">"): ng:///MatOptionModule/MatOption.html@0:296

What are the steps to reproduce?
Providing a StackBlitz reproduction is the best way to share your issue.
StackBlitz starter: https://goo.gl/wwnhMV
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Is there anything else we should know?

@crisbeto It works in all other browsers and i am not using mat-pseudo-checkbox
I am only using mat-select mat-options with multiple attribute internally it may using mat-pseudo-checkbox .

I am closing the issue because it turns out to be google maps script causing the issue.
If I move "https://maps.googleapis.com/maps/api/js?libraries=places&sensor..." bottom of the page everything works fine.


First MVC - MT sweep, screen shot updates, all issues fixed - Overview and 1st Tutorial

Internal review - Start MVC
Internal Review - Link changes to First MVC on ASP.NET Core Landing page
Fixes #21244
Contributes to resolving
#19801
#20528
#16991

Improvements for Machine Translation
Fix all open issues for this series that apply to the overview and 1st tutorial.
Few screen shot updates.
Removed Overview (index.md)
Added original Overview URL to redirect which pointes to start-mvc.md.
Updated links for start-mvc on ASP.NET Core Landing page.

@wadepickett @Rick-Anderson See the build warning re: the broken ToC link. How should this be fixed?

@wadepickett @Rick-Anderson See the build warning re: the broken ToC link. How should this be fixed?

I opened https://github.com/dotnet/AspNetCore.Docs/issues/21283 for it ... plz close if that was the wrong thing to do.

I opened https://github.com/dotnet/AspNetCore.Docs/issues/21283 for it ... plz close if that was the wrong thing to do.

Thanks!  On it....

Thanks!  On it....

First MVC index was removed, but I must have missed a reference to it when updating those.

First MVC index was removed, but I must have missed a reference to it when updating those.


AV-67671: support for ingress and route informers in utils for MCC

For HA feature of Multi Cluster Controller we need to get data from ingress and route informers.  Adding necessary changes, as the same utils package would be used in MCC.
This also includes necessary changes in vendor/ for openshift client to get route information.

@monotosh-avi okay - I guess we can always upgrade as needed. LGTM. Merging.


Make comments inside of MemberExpression look good

This is using the same technique as #544 and will conflict with it when we try to merge both :)
Fixes #200

Awesome, thanks!


feat: Add ClusterRoleBinding for instancetype:view ClusterRole

What this PR does / why we need it:
This adds a ClusterRolebinding which grants every authorized user read
access to VirtualMachineCluster{Instancetype,Preference} CRs.
This allows unprivileged users to make use of
VirtualMachineCluster{Instancetypes,Preferences} by default.
Also previously the wrong constant for ClusterInstancetypes was used instead, so fix that.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes https://issues.redhat.com/browse/CNV-36300
Special notes for your reviewer:
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note:

Allows unprivileged users read-only access to VirtualMachineCluster{Instancetypes,Preferences} by default.

/cc @tiraboschi
/cc @xpivarc

/retest

@0xFelix please complete the checklist.
Why is this prefixed with "feat:" isn't it rather a fix to allow cluster ITs to be viewed?

IMO you could consider it both. Isn't it a feature to provide access to something which unprivileged users didn't have access to before by adding a new ClusterRoleBinding?

I'd say that one of the inheritn goals of having ITs on the cluster level is to make them available to all usres (privileged or not) in order to align on this set of ITs.
IOW ITs which can not be accessed by unprivileged users seem to be useless.

Let's consider it a fix then.

/approve

/cherry-pick release-1.1
/cherry-pick release-1.0

Nice job @0xFelix! Thanks a lot!
/lgtm

/retest

/retest

/area instancetype

/cherry-pick release-1.1


Known issues with Telegram?

I just switched my main Display from float to bsp, all works as expected, but Telegram is just ignored.
It pops up floating over my e.g. Safari.

Works fine for me. On another note I have the problem that sometimes (very seldom) apps are just not picked up by yabai on launch. Quitting and relaunching the app usually fixes the problem immediately.

I have the same problem. In my case, all the applications started ealier than yabai cannot be managed. So the solution for me is to start these applications after yabai. I added this to .yabairc
ps -e | grep Telegram | grep -v grep || (open /Applications/Telegram.app && sleep 3 && osascript -e 'tell application "Finder" to set visible of process "Telegram" to false')

But I think "applications started before yabai cannot be managed" is a bug and should be fixed

Upgrade to v4.0.0. If you still have the problem, stop the brew service and run manually using yabai --verbose and you will see the reason why it is ignored in the startup logs.

The current version of telegram is now actually not playing nicely with yabai for me - wonder if anyone else experiences this?
EVENT_HANDLER_APPLICATION_LAUNCHED: Telegram (81218) is not finished launching, subscribing to finishedLaunching changes
-[workspace_context observeValueForKeyPath:ofObject:change:context:]: Telegram (81218) finished launching
application_observe: error 'kAXErrorCannotComplete' for application 'Telegram' and notification 'kAXCreatedNotification'
application_observe: error 'kAXErrorCannotComplete' for application 'Telegram' and notification 'kAXFocusedWindowChangedNotification'
application_observe: error 'kAXErrorCannotComplete' for application 'Telegram' and notification 'kAXWindowMovedNotification'
application_observe: error 'kAXErrorCannotComplete' for application 'Telegram' and notification 'kAXWindowResizedNotification'
application_observe: error 'kAXErrorCannotComplete' for application 'Telegram' and notification 'kAXTitleChangedNotification'
application_observe: error 'kAXErrorCannotComplete' for application 'Telegram' and notification 'kAXMenuOpenedNotification'
EVENT_HANDLER_APPLICATION_LAUNCHED: could not observe notifications for Telegram (81218) (1)

@kvndrsslr Yes, the same is happening with me. Telegram can't be recognized as a window.
$ yabai -m query --windows --window
could not retrieve window details.

Same thing here, telegram is being ignored by yabai and doesnt appear in a window list after yabai -m query --windows:(

Temporarily installed manually the old version 9.1 (238837), link - https://install.appcenter.ms/users/keepcoder/apps/telegram-swift/distribution_groups/public

Great news everyone!
Telegram 9.1.239550 fixes the problem and is getting recognized by yabai!

Great news everyone!
Telegram 9.1.239550 fixes the problem and is recognized by yabai!

@zakroma how did you get the last version? I don't see it in brew...

here

I really just pressed the update telegram button in their UI


Update for compatibility with Redmine 5.x / Rails 6.x

Hello, enclosed I would like to suggest a few changes that will allow the redmine_helpdesk plugin to be used on Redmine 5. It is tested on Remine 5.0.4, Ruby 2.7.6 (NetBSD), Rails 6.1.7 and PostgreSQL. The changes are primarily related to classloading, where there were probably a few changes in Rails 6. I'm not a Rails expert myself, but have worked this out more or less by trial and error. Nevertheless I don't want to withhold the result and hope it can at least serve as a starting point for future compatibility.
Many greetings
Matthias

Won´t merge cause I wanted the code to be a little bit different.
But thanks a lot for your support! I added you to the list of contributors.


WebSocket connection to 'ws://[my_ip]:8001/ws/progress/' failed

Describe the bug
after I updated a file to analyze, console error  WebSocket connection to 'ws://[my_ip]:8001/ws/progress/' failed, the service shutdown.
To Reproduce
Steps to reproduce the behavior:

select a file to analyze
error in WebSocket connection to 'ws://[my_ip]:8001/ws/progress/' failed:
(anonymous) @ serviceDashboard.js:103
the service shutted down but analyze docker is still running.

Expected behavior
I want the system not to be accidentally stopped after normal operation, I would appreciate if you could help me
Screenshots

Desktop (please complete the following information):

Thanks,

I'm tracking that currently.
We have a problem within our logreader, which causes the whole WSGI to crash.
Will keep you updated with a fix

Current master has a work-around for this issue.
It's not a fix, but at this moment, the only way to make the wsgi work.

Hi Team,
Thanks for update.
I will try right now.
:)

update on my side.
the good news is it works! thanks.
however it is too slow to load pages. TAT

closed with #154