comparison of Fixnum with nil failed

Been Trying to delete this user but keeps bugging out on me. Can't figure out why.
Is there a way around this problem? If more information need I can provide.
# If object exists then compare the two, otherwise return false
#
# @example Determine if we can compare.
#   matcher.determine("test", "$in")
#
# @param [ Object ] value The value to compare with.
# @param [ Symbol, String ] operator The comparison operation.
#
# @return [ true, false ] The comparison or false.
#
# @since 1.0.0
  def determine(value, operator)
    puts value
    puts operator
    attribute.__array__.any? {|attr|
      attr ? attr.send(operator, first(value)) : false
    }
  end

Here is the out put I get with the code I I am using above
> id = '54909ce4752d71293e320900'
> user = User.where(id: id).first
2.0.0 :010 > user.delete
{"$gt"=>1}
>
{"$gt"=>1}
>
{"$gt"=>1}
>
{"$gt"=>1}
>
{"$gt"=>1}
>
{"$gt"=>1}
>
{"$gt"=>1}
>
{"$gt"=>1}
>
{"$gt"=>1}
>
{"$gt"=>nil}
>
{"$gt"=>nil}
>
from /path/toshared/bundle/ruby/2.0.0/gems/mongoid-4.0.0/lib/mongoid/matchable/default.rb:69:in `>'
from /path/toshared/bundle/ruby/2.0.0/gems/mongoid-4.0.0/lib/mongoid/matchable/default.rb:69:in `block in determine'
from /path/toshared/bundle/ruby/2.0.0/gems/mongoid-4.0.0/lib/mongoid/matchable/default.rb:68:in `each'
from /path/toshared/bundle/ruby/2.0.0/gems/mongoid-4.0.0/lib/mongoid/matchable/default.rb:68:in `any?'
from /path/toshared/bundle/ruby/2.0.0/gems/mongoid-4.0.0/lib/mongoid/matchable/default.rb:68:in `determine'
from /path/toshared/bundle/ruby/2.0.0/gems/mongoid-4.0.0/lib/mongoid/matchable/gt.rb:17:in `matches?'
from /path/toshared/bundle/ruby/2.0.0/gems/mongoid-4.0.0/lib/mongoid/matchable.rb:58:in `block (2 levels) in matches?'
from /path/toshared/bundle/ruby/2.0.0/gems/mongoid-4.0.0/lib/mongoid/matchable.rb:57:in `each'
from /path/toshared/bundle/ruby/2.0.0/gems/mongoid-4.0.0/lib/mongoid/matchable.rb:57:in `block in matches?'
from /path/toshared/bundle/ruby/2.0.0/gems/mongoid-4.0.0/lib/mongoid/matchable.rb:55:in `each_pair'
from /path/toshared/bundle/ruby/2.0.0/gems/mongoid-4.0.0/lib/mongoid/matchable.rb:55:in `matches?'
from /path/toshared/bundle/ruby/2.0.0/gems/mongoid-4.0.0/lib/mongoid/contextual/memory.rb:152:in `block in initialize'
from /path/toshared/bundle/ruby/2.0.0/gems/mongoid-4.0.0/lib/mongoid/contextual/memory.rb:149:in `select'
from /path/toshared/bundle/ruby/2.0.0/gems/mongoid-4.0.0/lib/mongoid/contextual/memory.rb:149:in `initialize'
from /path/toshared/bundle/ruby/2.0.0/gems/mongoid-4.0.0/lib/mongoid/contextual.rb:53:in `new'
from /path/toshared/bundle/ruby/2.0.0/gems/mongoid-4.0.0/lib/mongoid/contextual.rb:53:in `create_context'
... 25 levels...
from /path/toshared/bundle/ruby/2.0.0/gems/mongoid-4.0.0/lib/mongoid/persistable/deletable.rb:23:in `delete'
from (irb):10
from /path/toshared/bundle/ruby/2.0.0/gems/railties-4.1.6/lib/rails/commands/console.rb:90:in `start'
from /path/toshared/bundle/ruby/2.0.0/gems/railties-4.1.6/lib/rails/commands/console.rb:9:in `start'
from /path/toshared/bundle/ruby/2.0.0/gems/railties-4.1.6/lib/rails/commands/commands_tasks.rb:69:in `console'
from /path/toshared/bundle/ruby/2.0.0/gems/railties-4.1.6/lib/rails/commands/commands_tasks.rb:40:in `run_command!'
from /path/toshared/bundle/ruby/2.0.0/gems/railties-4.1.6/lib/rails/commands.rb:17:in `<top (required)>'
from /path/toshared/bundle/ruby/2.0.0/gems/railties-4.1.6/lib/rails/app_rails_loader.rb:43:in `require'
from /path/toshared/bundle/ruby/2.0.0/gems/railties-4.1.6/lib/rails/app_rails_loader.rb:43:in `block in exec_app_rails'
from /path/toshared/bundle/ruby/2.0.0/gems/railties-4.1.6/lib/rails/app_rails_loader.rb:32:in `loop'
from /path/toshared/bundle/ruby/2.0.0/gems/railties-4.1.6/lib/rails/app_rails_loader.rb:32:in `exec_app_rails'
from /path/toshared/bundle/ruby/2.0.0/gems/railties-4.1.6/lib/rails/cli.rb:5:in `<top (required)>'
from /path/toshared/bundle/ruby/2.0.0/gems/railties-4.1.6/bin/rails:9:in `require'
from /path/toshared/bundle/ruby/2.0.0/gems/railties-4.1.6/bin/rails:9:in `<top (required)>'
from /path/toshared/bundle/ruby/2.0.0/bin/rails:23:in `load'
from /path/toshared/bundle/ruby/2.0.0/bin/rails:23:in `<main>'2.0.0 :011 > exit

Placed this in the wrong github repo

Sorry Clicked close button by mistake.

Can you please provide your User model?

Yes sure it is nothing uniq it is just a simple document with a id. tried to keep it super simple so as to reduce the total number of bugs that can happen. Really it is a hard bug to get to happen and I just call destroy in those cases.
class User
  include Mongoid::Document
  include Mongoid::Timestamps
end


Integrate CTDAS

Solves https://github.com/C2SM/processing-chain/issues/27

@efmkoene Can you remind me what the current status is here? What has to be done to fully integrate CTDAS? I assume that we want to have automatic testing via Jenkins for this case?

launch jenkins

Hi, sorry for the late response. The current status is not easily integrated into Jenkins as a case -- we need a lot of input data (ERA5, CAMS CO2, VPRM, TNO-GHG, a bunch of files describing the 'lambda' regions, and a specific branch of the CTDAS repository from WUR) and an ICON-ART version that is not the same as the C2SM hosted version. Is that problematic, that there would be a case that is not Jenkins-ed?

Imo, it is perfectly fine for CTDAS not to be a Jenkins case. Having a large amount of input data would indeed slow down the test pipeline. So I would suggest designing the case in such a way that you at Empa are able to manually run/test it yourself.

I'll probably push a 'final' version that can be used by Empa in the coming month.


Ref #30962 -- Added GitHub action for static code linters

Hey Joe, thanks for this. Interesting.
Can I ask you to collaborate with @orf (and everyone else) over at https://github.com/orf/django-github-actions on this?
(I saw your comment to the effect that we maybe don't need a long-running fork, but I'd be grateful if you could work that out with Tom — from my POV, it looks like it creates a space to experiment without creating a lot of noise for Mariusz and me on the main repo here, whilst it's all still Proof-of-Concept stage.)
I'm going to close this now. It may be just fine, but we're not yet at the stage where the plan is agreed.
Thanks! I'm quite optimistic about this topic. 💃

@carltongibson, I get the notion and I don't want to cause you any disturbance. But I'd like to ensure that all discussions are being archived. A for that lives only to discuss the current topic is not likely to survive past it's integration. I also don't think it's awefully intuitive for other who want to get involved. What do you think?

Errr...? I think Tom's work is looking good and that all efforts combined there is the quickest and best way for us to make progress as a group.

@carltongibson pardon my English my phone was about to die. I see your point, then again. I don't see the combined effort in @orf repo, it's only a couple commit ahead of Django HEAD all authored by @orf.

Hey @codingjoe. No problem. Your input is much appreciated at ever.
I think the think here is that Tom (and Florian and ...) are already thinking about this, so talking with them is just the best way to collaborate. I'm pretty certain there is a lot to do to get this right. 🙂
(I'd imagine that as soon as there's agreement on how it should go we will have a PR here.)

@carltongibson I guess let's just stick to the mailing list for now.


feat: textarea

Description
Adds Textarea component, following mockup and reproducing Input visual behavior.
Preview
https://user-images.githubusercontent.com/3367393/151016769-021d85f8-1636-4480-922d-5d470a9e97f4.mp4

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Feature Request Deeply type-check PEP 484 and 585 Callable[...] type hints :call_me_hand:

Callable's don't seem to be type checked, unfortunately.
from beartype import beartype
from beartype.typing import Callable

@beartype
def foo(bar: Callable[[str], None]) -> None:
    bar("Hello world")

def baz() -> None:
    pass

foo(baz)

Traceback:
Traceback (most recent call last):
  File "/Users/Moosems/Desktop/estensione/test.py", line 11, in <module>
    foo(baz)
  File "<@beartype(__main__.foo) at 0x10f4dcc20>", line 33, in foo
  File "/Users/Moosems/Desktop/estensione/test.py", line 6, in foo
    bar("Hello world")
TypeError: baz() takes 0 positional arguments but 1 was given

...heh. Just noticed that, huh? Yes. It's all true. @beartype still lies about many things. To see the exhaustive list of all things @beartype still lies about, please see our BigData™ data sheet. Note that:

The "partial support" column mostly means "@beartype only shallowly type-checks this thing."
The "full support" column mostly means "@beartype only deeply type-checks this thing."

It's best not to read or believe anything everything I write. Still, the anime-fuelled @beartype 0.19.0 changelog quietly admits that the biggest offenders that have yet to be deeply type-checked are:

Iterable[...] type hints. Not hard, so I claim. Just needs a bit of spit and polish, so I claim. I'm claiming lots of things without hard evidence here.

Callable type hints (e.g., collections.abc.Callable[...], typing.Callable[...]). Thankfully, BeartypeAI™ now provides a trivial O(1) one-liner for deeply type-checking any callable type hint hint against any arbitrary callable func:
def is_func_bearable(func: Callable, hint: object) -> bool:
    return is_subhint(infer_hint(func), hint)  # <-- lolbro

Type variables (e.g., typing.TypeVar('T'). Still no idea how to dynamically generate efficient code type-checking type variables, honestly. It's feasible, but let's avoid thinking about this until there's absolutely nothing left to do. :sweat_smile:

I actually had no idea how to even inefficiently deeply type-check Callable[...] type hints. But that was before beartype.door.infer_hint(). Now, I'm pretty sure it reduces to the trivial one-liner given above.
BeartypeAI™: what doesn't that drunken dancing bear know? :champagne: :bear:


ios refresh and loading 有问题

1、如果list数据为空，refresh 和loading 不能隐藏。
2、list数据动态变化，下拉刷新会跳屏，体验上很差

This issue is outdated for a long time and will be closed now. You can create a new one if you still have questions.


Update sponsor admin class

Create SponsorAdmin class than can do following:

list view, show fields: title, type, url
group form fields:

details: all fields can be here...
events: list of events where is sponsoring
soeakers: list of speakers that shopsor had

any other improvements, welcome...

working on it

@Redpoint1 thanks


wandb.summary.update does not upload before the end of the run

Describe the bug
I'm logging metrics with wandb.Run.log({..}) and summaries with wandb.Run.summary.update({..}).
The metrics do show ip on the UI, but not the summary.
To be exact, they do show up, but only at the end of the run. This is very unfortunate as those summary metrics are actually baselines (computed only once at the beginning of training) and I need to have access to those values to decide if I'm gonna stop the run...
Additional Files
No response
Environment
WandB version: version 0.15.0
OS: Linux
Python version: 3.9
Additional Context
No response

Hi @vict0rsch thank you for reporting this issue.
This is related to our wandb client/SDK and was introduced in v0.14.1 to address a perf issue (release notes here). The change has been reverted in our most recent release  (v0.15.3) and it should resolve this issue.
Could you please pip install --upgrade wandb and let us know if that worked for you?

Indeed thanks!


Wrong value reported in selected columns under some query conditions

System information:

Operating system:  (distribution) and version:
Edition: Windows 10 Enterprise
Version: 21H2
OS Build: 19044.1586
Windows Feature Experience Pack 120.2212.4170.0
DBeaver version:Version <IP_ADDRESS>204041542
Additional extensions:-

Connection specification:

Database name and version:PostgreSQL 13.4 on aarch64-unknown-linux-gnu, compiled by gcc (GCC) 7.3.1 20180712 (Red Hat 7.3.1-6), 64-bit
Driver name: PostgreSQL JDBC Driver 42.2.20
Do you use tunnels or proxies (SSH, SOCKS, etc)? -

Describe the problem you're observing:
If  we have two tables A and B in a join
and one of the selected columns of table A is given the name of another column of table A as an alias
and the columns of the other table are included with the "*" operator in the selected columns
then
the column of table A having the name of another column of table A as an alias is:

reported as null, even though it has a value, IF it is included AFTER  the "*" operator in the selectd columns
reported correctly,                           IF it is included BEFORE the "*" operator in the selected columns

Steps to reproduce:
create table scratch.test2
(id         bigint,
col_bigint bigint,
col_uuid   uuid,
col_a      bigint);
insert into scratch.test2
(id, col_bigint, col_uuid, col_a)
values
(10, 1, '9dd49536-1784-4c67-bfc1-20d4c9d9aede'::uuid, 14);
create table scratch.test3
(id bigint,
col_b bigint
);
insert into scratch.test3
(id, col_b)
values
(33, 14);
--Correct behavior
select test2.id,
col_uuid col_bigint,  --  reported as 9dd49536-1784-4c67-bfc1-20d4c9d9aede
test3.*,
col_uuid another_alias --  reported as 9dd49536-1784-4c67-bfc1-20d4c9d9aede
from scratch.test2,
scratch.test3
where test2.col_a = test3.col_b
-- Correct behavior
select test2.id,
col_uuid col_bigint,   --  reported as 9dd49536-1784-4c67-bfc1-20d4c9d9aede
-- test3.*,
col_uuid col_bigint    --  reported as 9dd49536-1784-4c67-bfc1-20d4c9d9aede
from scratch.test2,
scratch.test3
where test2.col_a = test3.col_b
-- Bug manifestation
select test2.id,
col_uuid col_bigint,  --  reported as 9dd49536-1784-4c67-bfc1-20d4c9d9aede
test3.*,
col_uuid col_bigint   --  reported as null
from scratch.test2,
scratch.test3
where test2.col_a = test3.col_b
-- Bug manifestation
select test2.id,
-- col_uuid col_bigint,
test3.*,
col_uuid col_bigint    --  reported as null
from scratch.test2,
scratch.test3
where test2.col_a = test3.col_b

Thanks for the bug report @george-a-g

Hello. @LonwoLonwo I"d like to work on this issue.

I can't reproduce this bug anymore. It seems that the issue has been solved.
Please, feel free to inform us if the bug is still exists for you.


Allow manually setting repo URL

Maybe we should set just SFOS version component. That is less typing on device and testing/regular type can be selected with the current settings


[Wallet] Add Japan to restricted CP-DOTO countries

Description
This PR adds Japan to the list of restricted CP-DOTO countries.
Tested
Updated tests.
Related issues

Fixes #5706

Backwards compatibility
Yes

@jeanregisser Verified with latest test flight build v1.5.0 (29) and Play store build v1.4.0<PHONE_NUMBER>) and found the following:

Japan user is not able to see Buy and Sell button CELO screen.
User is able to see only Withdraw CELO button if user has CELO balance.
User is not able to see Withdraw CELO button if user has 0 CELO or  send all CELO amount to other user.

Please let us know if we need to verify any thing else for this task.


"debug" is far too verbose

Hi,
I enabled the debug mode to get a hint at which query were runnings, but I started getting a spam of which packets were transmitted (HandshakeInitializionPacket then ClientAuthenticationPacket then OkPacket...)
My query string is the following:
mysql://root@localhost/bdiscuss?debug=true

my options:
db.settings.set('instance.autoFetchLimit', 3)
db.settings.set('instance.cache', false)

This didn't use to happen. Maybe it's a mysql package 'feature'?
I'm not sure where it came from.

Fixed in v2.1.27

thank you!


Quickly display the file shortcut "shift+ alt+r" in Explorer, which is not available on the editor's editing file

Issue Type: Bug
Quickly display the file shortcut "shift+ alt+r" in Explorer, which is not available on the editor's editing file. But when selecting the file on the sidebar and using "shift+ alt+ r"At the time of the key, you can open the file explorer and display the file in it. If you design this way, then this will not be a bug. But I hope you can add some configuration to let our users choose.
VS Code version: Code - Insiders 1.30.0-insider (241923763dbeaf3b64443187e935d55b29f6125d, 2018-12-07T22:31:41.479Z)
OS version: Windows_NT x64 10.0.17763

@usernamehw Thank you very much, this method has helped me perfectly.

/question
I'm just going to close this. Ignore the bot's message.


10657 better check for mapcaps

Not sure it fixes #10657, but it makes since anyway.
This check should be safer. Previous .exists? depends on how the relation is constructed and I don't trust it since Carto::Mapcap.exists? (so a non-scoped relation build) returns true. So theres a chance that this defaults to true in some weird RAILish situation which is not good. I prefer to fetch LIMIT 1 (i.e: .first) and check presence. For that I just reuse latest_mapcap.
See if it makes sense to you @juanignaciosl.

As I see that you ignore my suggestion about the ternary check, 👍  😅  . A comment at non_mapcapped might be nice anyway.

Sorry, didn't mean to ignore it! Since this is already a bit old, I'll review a bit and address all your comments!

@gfiorav no, I understand that it's open to discussion. Feel free to ignore it, it's something that I'd do but I understand that others disagree. Really minor, indeed :-)

As a general comment: mapcapped? now just checks for latest_mapcap.present? so it's not worth the refactor IMHO.
Thanks for the comments!


Fix output to stdout from cron job, and fix invalid default value for --timestring

1: Curator produces output to stdout for commands such as the following:
root@server:~# curator --logfile /tmp/curator.log --loglevel ERROR delete indices --prefix logstash- --older-than 30 --time-unit days --timestring %Y.%m.%d
No indices matched provided args.
This would cause email to be sent to root when run from cron.
See also
elastic/curator#428
2: Fix invalid format string for timestring flag
curator::job defaults the --timestring flag to '%Y.%m.%d'. This is invalid (in curator 3.2, at least) as it  does not expect the % characters to escaped and so rejects them.

This PR is invalid. The % characters are escaped for good reason as cron interprets them specially and changes them into newline characters. You learn something every day! I'll close this and create a new request for just the stdout redirection.


Applicant Timeline - Welcome Step

Notes:

French translations required
Zero functionality, simply has text and a button with a passable click handler

Looks good 👍
However, should decide on a naming convention for the formatted message id's and the folder structure. Chris is using different names then I on the Basic Info PR.
Example for formatted message:
id: "applicationTimeline.{name of the step}.header"
OR
id: "applicantTimeline.{name of step}.header"
Example for folder structure.
Application/files OR ApplicantTimeline/{name of step}/files for that step`
@tristan-orourke @Khristophor

Agreed, we do need a convention. I had copied @tristan-orourke 's convention for file naming, but I didn't really pay attention to the lang id. Maybe stick to the component or folder name, so application.[step name].header or similar?

Re: naming conventions
I think each step should have its own folder, since some of the steps already have many components. (eg the experience step with accordion components for each experience type.) And just Application is fine; we've mostly use the term ApplicationTimeline to distinguish it from our previous version, but the previous version has no React files anyway.
So that looks like Application/{name of step}/files for that step.
And I like application.[step name].header for message ids, since that matches the file convention. Maybe application.[component name].header for sub-components like accordions.

@yonikid15 @tristan-orourke updated files/keys to the convention.


Contributing Standards

Right now this will be a brain dump...apologize for the lack of structure.

All work must be done via PR's - even if done by a maintainer
All PRs must get two approvals from the maintainer group before merging
All PRs must pass pep8 standards

PR commits should be concise and squashed. One PR per feature, so generally 1 commit per PR (although there may be reasons to have multiple commits, as long as they make sense) imo.

Agreed. Also, we might have something like this to ensure everything is linted/PEP-8 conformant: https://github.com/markstory/lint-review

Agreed on the squashes.  Will we also be squashing when merging?

rebase for merging I think?

I think we should rebase for merging and have contributors do the squashing.

Add stuff about contributors doing squashing

GitHub team @OpenPoGo/maintainers added.  They will be tagged on every PR.

I'll take ownership of this issue to make sure it's completed

If someone could make a MAINTAINERS.md or wiki page with this information that'd be great

SGTM

:+1: from me

+1

+1

+1 from me

how can we keep track of the number of approvals?

Are we just typing approval?
what if I want to thumbs up the main post instead?
+1

@jmeyer2k If you're talking about approvals on a PR - we'll use this.
Either is fine @Reaver01

+1

yeah, let's get that setup then.

All work must be done via PR's - even if done by a maintainer
All PRs must get two approvals/👍 from@OpenPoGo/maintainers before merging
All PRs must pass CI
One PR per feature
All PR commits must be concise and squashed (done via the contributor)
All PRs should be merged via rebase

Done.

All PRs must pass pep8 standards (this will be checked automatically)
#4


Gloss names of places in the local language

World political maps and atlases by American publishers typically show well-known places in English but also gloss the name in the local language when it differs from the English name. Typically, the local name is shown in parentheses and/or italics, and sometimes on a separate line in smaller type.

I’ve seen these glosses on labels of populated places, but rarely on other kinds of features. I suppose there are a variety of reasons:

Many anglicized city names are less well-known than official English names of countries.
A waterway may form an international boundary and thus have a whole host of local names, but consistency along the length of the waterway is often prioritized.
Labels for non-place POIs are already long enough to risk getting collided out by POI labels without getting doubled in length by the gloss.
Political maps rarely label anything less significant than a populated place.

We should consider glosses for other feature types at higher zoom levels, where collision isn’t as much of a concern, but populated places seems like a good place to start.
To achieve the gloss, we can set text-field to a format expression that includes both name:en and name when the two properties differ. A collator expression can be passed into the string comparison to perform case and diacritic folding.
/ref #100 #428

The ability to choose a base language other than English (#20 #21) would complicate this feature somewhat, but even in English there are some edge cases to consider:

Since “Montreal” and “Montréal” differ by only diacritics, it’s probably fine to render it as just “Montréal” instead of “Montreal (Montréal)”.
Hong Kong’s place name labels are bilingual in both English and Chinese, so the expression would need to avoid duplicating the English name. For example, it should be “Kowloon (九龍)”, not “Kowloon (九龍 Kowloon)”.

For local names written in non-Latin writing systems, National Geographic and Rand McNally show romanizations rather than the local name verbatim. In principle, name:latin could be used for this purpose, but there are some problems with that automated approach: onthegomap/planetiler#86. Instead, it might be possible to implement an algorithm for choosing an explicitly tagged transliteration directly in the stylesheet. For example, if name matches name:ko, use name:ko-Latn, but fall back to name:latin if it isn’t available.


XAML compiler doesn't deal with leading whitespace properly

Avalonia (0.10.6 - I am currently stuck on this version so please let me know if it's fixed in a later version):

<ToolTip.Tip>
  <TextBlock>
    Returns a Domino build given a:

    - Build Number (e.g. 16.0.11217.10000)

    Returns the last 2 Domino builds given a:

    - Leave Blank for Daily Builds
  </TextBlock>
</ToolTip.Tip>

Vanilla WPF:

<StackPanel.ToolTip>
    <TextBlock>
        Returns a Domino build given a:<LineBreak />
        - Build Number (e.g. 16.0.11217.10000)<LineBreak /><LineBreak />
        Returns the last 2 Domino builds given a:<LineBreak />
        - Leave Blank for Daily Builds
    </TextBlock>
</StackPanel.ToolTip>

Expected behavior:
I would expect the visual result in Avalonia to look the same as the vanilla WPF visual result, but the Avalonia version adds a bunch of space in front of every line after the first line (probably due to the spacing in the xaml file).
Desktop (please complete the following information):

OS: Windows 10
Version 0.10.6

Also note that long lines will get cut off in the tooltip:

<ToolTip.Tip>
  <StackPanel>
    <TextBlock>
      Lorem ipsum dolor sit amet,
consectetur adipiscing elit, sed do
eiusmod tempor incididunt ut labore et dolore magna aliqua.
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur
    </TextBlock>
  </StackPanel>
</ToolTip.Tip>

Weird problem with tooltip, it's shouldn't be limited by height, and shouldn't be cut. Do you have any styles on tooltip? Or can you check in devtools what is limiting the height?

About whitespaces in the beginning of lines, I believe this PR did fixed it, but wasn't merged.
https://github.com/kekekeks/XamlX/pull/43
@kekekeks what do you think, can it be merged? I am not sure if we consider it as a breaking change.

I don't have any styles on tooltip. But I can look at devtools when I'm back at work tomorrow

@maxkatz6 any tips for investigating ToolTip size in devtools? I don't know if I can pause the app with the tooltip open & look at devtools (so I don't have to keep my cursor there) or what else I should be looking for

Works good to me. I have only a style for background.

Fixed in master https://github.com/kekekeks/XamlX/pull/43


RedPajama Pretrain Tutorial: add skipped step with converting HF checkpoint to Lit-GPT format

Hi there 👋
If someone wants to pretrain the model on RedPajama and uses for it tutorials/pretrain_redpajama.md, then he/she might get this error:

No such file or directory: lit_config.json

As it happened to the user in #718.
The reason that the tutorial tells to download the model and use it right away, but the prepare script is expecting lit_config.json
https://github.com/Lightning-AI/lit-gpt/blob/96666c3850741f7182f5c826e1528469d884829a/scripts/prepare_redpajama.py#L150
That's why the conversion code snippet is added to the tutorial.

My logic is that when a user is reading a tutorial, it should provide all the necessary steps.
And in the tutorials/pretrain_redpajama.md the first step is to download the dataset, then download the model and right after that — run scripts/prepare_redpajama.py script.
The first what the script does is trying to load lit_config.json. So without conversion it won't work at all.

I’d say let’s fix this by adding a “choosing a tokenizer” step instead.

I opened https://github.com/Lightning-AI/lit-gpt/pull/724 which adds a flag that could be used for this purpose

Although lit_config is still an issue. We could either:

Move its creation from convert_hf_checpoint.py to download.py
Create a separate step for it

For lit_config.py maybe something like:
    if (checkpoint_dir / "lit_config.json").is_file():
        config = Config.from_json(checkpoint_dir / "lit_config.json")
    elif checkpoint_dir.name in name_to_config:
        config = Config.from_name(checkpoint_dir.name)
    else:
        raise ValueError(f"For {str(checkpoint_dir)!r} neither 'lit_config.json' nor config exists.")

but prettier 😊.

I like that. You can put it in a utility function and call it from all scripts that need it

@Andrei-Aksionov Let's close this in favor of another PR that implements your lit config proposal?

Yes, you can close it.
I'll make a PR on Sunday or Monday.


Mounting only the slots of child components

What problem does this feature solve?
We currently have a helper file in our codebase we pull in to testing files, it contains this beauty:
/**
 * Create a component stub that will render all included slots from the
 * parent component. This lets you test the slots you've included in child component
 * without having to fully mount the child component.
 *
 * * Notes on implementation *
 * There is no one place this is clearly laid out. This thread gave the starting point:
 *
 * https://github.com/vuejs/vue-test-utils/issues/85
 *
 * but modifying the function requires understanding Vue's functional components
 * and the `render` function:
 *
 * https://vuejs.org/v2/guide/render-function.html
 *
 * especially the arguments that `createElement` can take:
 *
 * https://vuejs.org/v2/guide/render-function.html#createElement-Arguments
 *
 * In short, this produces a <div> with only the child components slots, but none of
 * its other functionality.
 *
 * @return {object} The functional component definition
 */
componentStubWithSlots: function (el) {
  if (!el || typeof(el) !== 'string') {
    el = 'div';
  }
  return {
    render: function (createElement) {
      return createElement(el, [Object.values(this.$slots)]);
    }
  };
}

It would be nice if there was a more elegant way of handling this, or at least better documented (not requiring links to 3 different places).
What does the proposed API look like?
That helper function gets used like so:
test('Show only mine checkbox adds showOnlyMine to the query params', async () => {
  const wrapper = shallow(reservationsList, {
    store,
    localVue,
    stubs: {
      RouterLink: RouterLinkStub,
      'base-table': helpers.componentStubWithSlots()
    },
    mocks: { $ga }
  });

  let checkbox = wrapper.find('[data-test="showOnlyMineCheckbox"]');
  checkbox.trigger('click');

  expect(wrapper.vm.paramsForGettingListItems)
    .toEqual({ showOnlyMine: true });
});

I think it would be nicer if there was something like that built in, so we could just do this:
test('Show only mine checkbox adds showOnlyMine to the query params', async () => {
  const wrapper = shallow(reservationsList, {
    store,
    localVue,
    stubs: {
      RouterLink: RouterLinkStub,
      stubComponentSlots: [ 'base-table' ]
    },
    mocks: { $ga }
  });

  let checkbox = wrapper.find('[data-test="showOnlyMineCheckbox"]');
  checkbox.trigger('click');

  expect(wrapper.vm.paramsForGettingListItems)
    .toEqual({ showOnlyMine: true });
});

https://github.com/vuejs/vue-test-utils/issues/1564#issuecomment-1424857260


Adding client capabilities to OOP client initialization data

### Summary of the changes

Pass client capabilities to OOP just once, during the initial client collection
Proffer client capabilities to other remote services via RemoteClientCapabitiliesService
Move common code for the cohost and remote ClientCapabilitiesService to a base class in Workspaces layer
Fixup tests to init necessary capabilities

Fixes: https://github.com/dotnet/razor/issues/11102

but it looks like there are test failures.

thanks, I ran and fixed cohosting tests, missed that one. just submitted a fix.

(Note that you can always check for test failures by running build.cmd -test at the command-line before submitting.)

thanks, didn't know about hat parameter

Does that do something different to just running tests in Test Explorer??

Does that do something different to just running tests in Test Explorer??

Technically, yes; practically, no. If something throws on a thread after a thread has finished running, it'll fail at the command-line, but Test Explorer will eat the exceptions. That's pretty uncommon though, so practically, there's no real difference. :smile:
Personally, I like to run them at the command-line so they run just as they do in CI. That gives me some confidence that any test failures in CI for Window-Debug or Windows-Release aren't mine. Plus, I get to see if there any warnings (such as unused using) that would break the CI build before pushing. Also, I always trip over the fact that our integration tests our included in the Test Explorer. Too often when making a compiler change, I'll forget and Ctrl+A to select all tests and accidentally start integration tests running. build.cmd -test just runs unit tests.

Also, I always trip over the fact that our integration tests our included in the Test Explorer. Too often when making a compiler change, I'll forget and Ctrl+A to select all tests and accidentally start integration tests running. build.cmd -test just runs unit tests.

May I recommend a "RazorToolingTests.playlist" playlist file, that includes everything but compiler and integration tests, so one click of the "Run All In View" button runs only the interesting things.

Also, I always trip over the fact that our integration tests our included in the Test Explorer. Too often when making a compiler change, I'll forget and Ctrl+A to select all tests and accidentally start integration tests running. build.cmd -test just runs unit tests.

May I recommend a "RazorToolingTests.playlist" playlist file, that includes everything but compiler and integration tests, so one click of the "Run All In View" button runs only the interesting things.

I do know about that, but I did say "too often when making a compiler change." :smile:


Xmc4800 automation board support and MEMC drivers for XMC4xxx

Includes MEMC drivers for XMC4xxx
The dev kit has an SDRAM connected via MEMC.

Reopen PR.
Waiting for https://github.com/zephyrproject-rtos/zephyr/pull/50880 for to get merged before rebasing.

Ping pls.
The memc driver was tested on XMC4800 automation board to interface with sd ram (tests/drivers/memc/ram) and on a custom board to interface with FPGA.

I'll rebase this when https://github.com/zephyrproject-rtos/zephyr/pull/55435 gets merged

@npal-cy, any chance you could have a look at this PR?
The main part is the EBU driver (MEMC) for external interfaces. I added XMC4800 automation board to test the EBU driver with external SDRAM.

@npal-cy thanks, for your comments. I'll update the PR once the xmc47 relax kit is merged.

I rebased to get a fresh CI run

@npal-cy, could you re-ack when you have a moment, please? The ci errors are from a different board.
It would be great to get this merged before the freeze for the next releasse

@galak, can you another look at this PR pls?

@galak, ping, can you have another look pls


feat: emsco revision create update twig

Q
A

Bug fix?
n

New feature?
y

BC breaks?
n

Deprecations?
n

Fixed tickets
n

Partial -> merge new twig function
Add docs


Bump go version to 1.14 in go.mod

Signed-off-by: Kemal Akkoyun<EMAIL_ADDRESS>I believe this has forgotten as part of https://github.com/prometheus/prometheus/pull/7100.

I don't know why proto generation fails. What am I missing?

Master broken? Not sure if Go 1.14 could brake anything. I know we fetch things from vendor... to build protos. You could try to run it locally @kakkoyun

@bwplotka Yes, I'm already on it. Trying to figure it out.

When I change the go version in go.mod. It downloads this github.com/gogo/protobuf, but it decides not to use it. It tries to use github.com/google/protobuf
As a result, the generator script is broken https://github.com/kakkoyun/prometheus/blob/7fb974ec92206c623ffdbe7ef445369a7782c1fd/scripts/genproto.sh#L28
And also I have realized this version acts as the minimum supported version, so if the project doesn't rely on any 1.14 features this change is unnecessary.
I'm gonna check out if we rely on any recent features, if so I'll try to fix the issue, otherwise I'll close this one.

Closing this for now.

And also I have realized this version acts as the minimum supported version, so if the project doesn't rely on any 1.14 features this change is unnecessary.


publish package

Configuration
This will create a config/pusher.php file in your app that you can modify to set your configuration. Also, make sure you check for changes to the original config file in this package between releases.
I was stuck with 'This' .  I found eventually to run php artisan vendor:publish  then the pusher.php file appeared in the app/config folder.  Please change the readme?

This has been updated now.


Use serialized names for Biome.MixedNoisePoint fields

A serialize method was added in 20w14∞, and we should use the names in it to match serialization output.

Serialized name
Current Yarn name

temperature
temperature

humidity
humidity

altitude
hilliness

weight
rarityPotential

weirdness
style

weight and weirdness imo doesn't make much sense...
that weight is actually a buff so as to decrease the effective distance from a sampled point to the target biome noise point, which rarity potential conveys better.
weirdness isn't as good as style. There is nothing weird, but the style can be a scalar that fluctuates and biomes with more consistent styles can reasonably be grouped together in generation.

What I find impressive is how well mine and @liach 's original guesses match the apparent actual meaning, using only our guesses based on what biomes had which values :P

I would approve of a 13b backport if it kept rarityPotential as it is.

Why was this merged? We didn't all agree and it isn't even a complete PR (there's other stuff around the world gen code that need renaming now because of this)

We didn't all agree

looks at #1106

there's other stuff around the world gen code that need renaming now because of this

Hm, I didn't know that... Sorry.


Fix self param into watcher notify

We must wrap the notify call in order to give access to this inside watcher constructor.  This is because when consumerMarkedDirty is called it is actually in the ReactiveNode context and can only pass in the node as the self argument.  The node is not useful inside notify because the main thing a user would want to do in here is use the watcher object's functions like getPending and watch.
Also, there was some discussion of removing the self param all together in favor of this.  However that does not work because in the case of an arrow function it is defined in the global context and in the case of a normal function we arent taking the steps to bind because it could possibly be an arrow function.  So update the README as well to back to the self way, it is better than before because self is actually passed in as a param this time.  Keep the self name over this in the type declaration in the case of an arrow function, Typescript doesnt like params named this.
Add unit tests to describe these cases.

The Watcher vs ReactiveNode bug is initially pointed out here: https://github.com/proposal-signals/proposal-signals/pull/99#issuecomment-2038054668
However, my solution drops this in favor of only self but would () => notify.call(this, this) be preferred to make this available to non-array functions as well?

@yeomanse
Using this in arrow-function that's created in the scope of a module doesn't work anyway. As .bind(this) is ignored on arrow functions.
I'd be in favor of just passing self for constistency.

I don't really want to pass self because usually you can just refer to the outer variable, as in https://github.com/proposal-signals/proposal-signals/pull/158 . Using this is just if you want to avoid creating a closure per watcher, which is a pretty special/unusual requirement (generally more relevant for computeds, but even then kinda special). People got confused when a previous draft passed self in (because it's not clear why that's a relevant parameter, since you can just refer to the outer lexical variable), so I switched back to this.


docs: improve grammar and readability for README.md

Formal ECDH in full with acronym.
Missing preposition between groups and hosts.
Hopefully with the preposition it reads better ;-)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Want to add more in about section and more efficient in design.

Is your feature request related to a problem? Please describe.

About section is all empty. Only contains one line. Want to add more in about section related to website. What is represents and the features, use, developed by and other information.

Describe the solution you'd like

About section of any website should be precise and clear descriptive which is not so i want to make it more concise by adding content and also it's style(UI) design good.

GSSOC21
If you would like to please assign this to me :)
@shrey27tri01 @Nidhirajput1301 @apekshamanchanda

@aashi2912 You can go ahead with the issue :)
Please show us the changes you did through screenshots or any other medium, while creating the PR.
Deadline: 22 March, 2021 11:59 PM IST

Sure. Thanks!

hey, @shrey27tri01 . I just forked the project and it's about section is not working. Something is not right. It is not displaying anything. The content which is already there. App developed by  thing and also if I am doing something my content is ready but it is not gonna show. Please look into this matter so I can work on my issue. Whenever you click on about section nothing happens.


DOMException 500 Error

@hanxiao Could you please give some advice for this issue?
`https://r.jina.ai/https://www.msn.com/en-us/news/technology/the-best-ai-search-engines-and-tools-you-can-use-to-search-the-web/ar-BB1kbzFL`

{"code":500,"status":50000,"message":"Failed to execute 'setAttribute' on 'Element': '}' is not a valid attribute name.","name":"DOMException"}

it is likely that msn.com has blocked our api fetching, turn on stream mode we can see

curl http://<IP_ADDRESS>:5001/reader-6b7dc/us-central1/crawl/https://www.msn.com/en-us/news/technology/the-best-ai-search-engines-and-tools-you-can-use-to-search-the-web/ar-BB1kbzFL -H "Accept: text/event-stream" -H 'x-no-cache: true'
event: data
data: {"title":"MSN","url":"https://www.msn.com/en-us/news/technology/the-best-ai-search-engines-and-tools-you-can-use-to-search-the-web/ar-BB1kbzFL","content":""}

event: data
data: {"title":"MSN","url":"https://www.msn.com/en-us/news/technology/the-best-ai-search-engines-and-tools-you-can-use-to-search-the-web/ar-BB1kbzFL","content":""}

event: data
data: {"title":"","url":"about:blank","content":""}

event: data
data: {"title":"","url":"about:blank","content":""}

event: data
data: {"title":"","url":"about:blank","content":""}

event: data
data: {"title":"","url":"about:blank","content":""}

event: data
data: {"title":"","url":"about:blank","content":""}

event: data
data: {"title":"","url":"about:blank","content":""}

event: data
data: {"title":"","url":"about:blank","content":""}

event: data
data: {"title":"","url":"about:blank","content":""}

event: data
data: {"title":"","url":"about:blank","content":""}

event: data
data: {"title":"","url":"about:blank","content":""}

event: data
data: {"title":"","url":"about:blank","content":""}

event: data
data: {"title":"","url":"about:blank","content":""}

event: data
data: {"title":"","url":"about:blank","content":""}

event: data
data: {"title":"","url":"about:blank","content":""}

event: data
data: {"title":"","url":"about:blank","content":""}

event: data
data: {"title":"Redirecting to MSN","url":"https://www.msn.com/staticsb/statics/latest/auth/auth-redirect-blank.html#error=interaction_required&error_description=Session+information+is+not+sufficient+for+single-sign-on.&state=eyJpZCI6IjQwMWMwYmU4LWQwZjEtNDdkYS04MTcyLTg3MTc3MjUwOTI3ZiIsIm1ldGEiOnsiaW50ZXJhY3Rpb25UeXBlIjoic2lsZW50In19","content":""}

event: data
data: {"title":"Redirecting to MSN","url":"https://www.msn.com/staticsb/statics/latest/auth/auth-redirect-blank.html#error=interaction_required&error_description=Session+information+is+not+sufficient+for+single-sign-on.&state=eyJpZCI6IjQwMWMwYmU4LWQwZjEtNDdkYS04MTcyLTg3MTc3MjUwOTI3ZiIsIm1ldGEiOnsiaW50ZXJhY3Rpb25UeXBlIjoic2lsZW50In19","content":""}

event: data
data: {"title":"The Best AI Search Engines and Tools You Can Use to Search the Web","url":"https://www.msn.com/en-us/news/technology/the-best-ai-search-engines-and-tools-you-can-use-to-search-the-web/ar-BB1kbzFL","content":"Continue reading\nMore for You\n  Continue reading\nMore for You\n© 2024 Microsoft\nYour Privacy Choices\nConsumer Health Privacy\nPrivacy & Cookies\nTerms of use\nAdvertise\nFeedback"}

let's see if we can have some workaround

solved in the latest release: https://r.jina.ai/https://www.msn.com/en-us/news/technology/the-best-ai-search-engines-and-tools-you-can-use-to-search-the-web/


Enable fallback to PATH from rbenv shims

Previously, when someone activated rbenv shim foo, rbenv would error out if RBENV_ROOT/versions/RBENV_VERSION/bin/foo did not exist.
This change allows foo to be additionally looked up in PATH as fallback. This prevents a case where one of the Ruby versions is shadowing a system-wide command of the same name, preventing the use of the global command across all other Ruby versions.
rbenv used to be strict around this: the lack of a fallback mechanism was to avoid ever falling back to system Ruby for invocations like bundle if the current Ruby version did not yet install Bundler. The current approach prevents this scenario by explicitly disallowing fallback for the following executables: ruby, rake, gem, bundle, bundler, irb, rdoc, ri.
Fixes https://github.com/rbenv/rbenv/issues/187
Fixes https://github.com/rbenv/rbenv/issues/865 /cc @jasonkarns
Closes https://github.com/rbenv/rbenv/pull/1110
Additionally, this changeset is a followup to https://github.com/rbenv/rbenv/pull/1436 by bumping up GEM_HOME so it takes precedence over executables found in PATH.
@konsolebox: Since you've previously provided helpful warnings around other potentially risky changes, does this one raise any warning flags for you? Thanks

@konsolebox: Since you've previously provided helpful warnings around other potentially risky changes, does this one raise any warning flags for you? Thanks

I'm quite ok with the fallback code so far.  I've been thinking about the GEM_HOME support rbenv will generously provide but ended up having no strong opinion about it, partially because it won't really affect me; another is because GEM_HOME will always affect the ruby instance anyway regardless if executables in ${GEM_HOME}/bin are executed or not.  I only worry about the shim noise it will allocate but it's nothing really.
Is there a reason why ${GEM_HOME}/bin is not auto-included in PATH?  Not saying it should be.
I also ideally think "version bin path" should be made sure to be only added once, and also only added exactly before the shims path to avoid getting a higher PATH priority from a directory a user may not want it to.

Is there a reason why ${GEM_HOME}/bin is not auto-included in PATH? Not saying it should be.

You mean, to include it in PATH when libexec/rbenv is preparing the final PATH before dispatching other rbenv-* commands? We could do that in theory, but I'm more comfortable of scoping any GEM_HOME behavior to just the shim dispatch mechanism.

I also ideally think "version bin path" should be made sure to be only added once, and also only added exactly before the shims path to avoid getting a higher PATH priority from a directory a user may not want it to.

Sorry, could you elaborate? I'm not sure I follow

Is there a reason why ${GEM_HOME}/bin is not auto-included in PATH? Not saying it should be.

You mean, to include it in PATH when libexec/rbenv is preparing the final PATH before dispatching other rbenv-* commands? We could do that in theory, but I'm more comfortable of scoping any GEM_HOME behavior to just the shim dispatch mechanism. If ${GEM_HOME}/bin wasn't in PATH already, I'm reluctant to automatically push it into PATH to avoid negatively affecting all rbenv commands and subprocesses (including ruby itself).

To be exact it's these lines:
if [ "$RBENV_BIN_PATH" = "${RBENV_ROOT}/versions/${RBENV_VERSION}/bin" ]; then
  export PATH="${RBENV_BIN_PATH}:${PATH}"
fi

It was originally:
if [ "$RBENV_VERSION" != "system" ]; then
...

Which seems to make sure only "${RBENV_ROOT}/versions/${RBENV_VERSION}/bin" is added to PATH and not ${GEM_HOME}/bin when RBENV_COMMAND_PATH points to an executable in it.
I have no definite opinion about it as well.  Perhaps not adding it to PATH is safer, and maybe more consistent to instances where GEM_HOME is modified somewhere during runtime.

I also ideally think "version bin path" should be made sure to be only added once, and also only added exactly before the shims path to avoid getting a higher PATH priority from a directory a user may not want it to.

Sorry, could you elaborate? I'm not sure I follow

If let's say I have a PATH with a path that comes before ${RBENV_ROOT}/shims like the ${GEM_HOME}/bin path which I explicitly add:
/home/user/project/common-gems/bin:/home/user/.rbenv/shims:/home/user/.rbenv/bin:/home/user/bin:/home/user/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:

where GEM_HOME is /home/user/project/common-gems/bin:
I would prefer ${RBENV_ROOT}/versions/${RBENV_VERSION}/bin to only be added right before /home/user/.rbenv/shims and not at the very beginning of PATH.  This is for the sake of consistency of runtime priorities.
Also if ${RBENV_ROOT}/versions/${RBENV_VERSION}/bin is already in PATH, I want that it doesn't add itself again.  This is something that may happen on a recursive call to rbenv or one of its commands.

To be exact it's these lines:

Ah, I see! I can consider allowing ${GEM_HOME}/bin to be prepended here; that would make sense. The extra conditional you noticed me adding is because I do not want to prepend the path for a system fallback. For example, if executing foo was ultimately found in /usr/bin/foo, I do not want /usr/bin to be prepended to PATH.

Ah, I see! I can consider allowing ${GEM_HOME}/bin to be prepended here; that would make sense. The extra conditional you noticed me adding is because I do not want to prepend the path for a system fallback. For example, if executing foo was ultimately found in /usr/bin/foo, I do not want /usr/bin to be prepended to PATH.

I'm starting to think that ${RBENV_ROOT}/versions/${RBENV_VERSION}/bin should not be added to PATH at all since if theoretically a grand child process (likely a shell script) changes directory to a project directory with a .ruby-version that specifies a different Ruby version, that version can be ignored since the executables in the previous ${RBENV_ROOT}/versions/${RBENV_VERSION}/bin will be called first.
Was optimization the intention for adding it?
I also think ${GEM_HOME}/bin shouldn't also be added as well since some configuration may change its value in the project as well, which could be done in the grand child process shell itself, or some hooks for rbenv which alters the variables like this one:
/etc/rbenv.d/exec/environment.bash:
{
	__=${PWD}

	while [[ $__ == /* ]]; do
		if [[ -e $__/.ruby-environment ]]; then
			[[ -r $__/.ruby-environment ]] && source "$__/.ruby-environment"
			break
		fi

		__=${__%/*}
	done

	unset -v __
}

.ruby-environment:
export GEM_HOME=${BASH_SOURCE%/*}/../common-project-gems
export PATH=${GEM_HOME}/bin:${PATH}

The GEM_HOME value example is mostly useful for examining the gems a project pulls in because they're placed in an isolated directory.  They're easy to grep, clean up and refresh.

If it's for the sake of having newly installed executables detected immediately at the same runtime, the paths should be added after the shims path instead.
For example, /home/user/.rbenv/shims:/home/user/.rbenv/bin:/sbin:/bin becomes /home/user/.rbenv/shims:/home/user/.rbenv/versions/3.0.4/bin:/home/user/.rbenv/bin:/sbin:/bin instead.

I'm starting to think that ${RBENV_ROOT}/versions/${RBENV_VERSION}/bin should not be added to PATH at all

I wanted to get away with that as well, but unfortunately, prepending the bin directory to PATH is what's needed to support ruby -S: https://github.com/rbenv/rbenv/issues/480
If shims remain in PATH, shelling out to ruby -S <command> would fail if command was found among rbenv shims, since shims are bash scripts and not ruby scripts.
ruby -S is itself a huge hack and I don't like that we have to work around this but I wasn't able to find other ways around this.


use char string template, fix bbox coordinate order

Pull request with just the CharacterString processing and BBox coordinate order updates in the XSLT that generates schema.org script in the html landing pages.

manually added to running server...
code is on workstation in office.

so should we close this without merging?

Leave open
On Sun, Jul 11, 2021 at 3:28 PM Stephen Richard @.***>
wrote:

so should we close this without merging?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/CINERGI/geoportal-server-catalog/pull/46#issuecomment-877870363,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGP6SGWBY7W3KARU7MFOI3TXILHLANCNFSM5ABFM2LA
.


Move nomad-dos-fingerprint to deps

@TLCFEM this was working last week, not sure if there was a change in metainfo?

I did not have anything related merged recently.


"skipping Messages"

when deleting a conversation with one person, it says it is "skipping messages" the entire time, what do i do?

@Zenot1cc
Logout, Clear Browser Cache, and then retry.


Diablo

Hello,
I am having an issue with Diablo 3 64-bit under DXVK.
When the game starts, the screen goes gray and does not continue. The file d3d11.log gets full of the messages:
err:   D3D11: Cannot create texture:
  Format:  44
  Extent:  32x32x1
  Samples: 1
  Layers:  1
  Levels:  1
  Usage:   48
  Flags:   0

The longer I stay on the gray screen, the more times this message is repeated.
I do not get to hear the game sound / music on the gray screen.
I get the same result if I run the game via Battle.net client or directly.
If I run Diablo 3 in windowed mode (-launch -windowed), it is the same.
The 32-bit Diablo 3 runs fine with just the Wine native libraries.
The 64-bit Diablo 3 runs with native libraries but the performance is appalling.
Software information
Diablo 3
Tried on Debian 10 Testing and Lubuntu 18.10
Tried various setting, resolutions etc. in the game, various settings in Wine, various versions of MESA drivers and DXVK, it always ends with the same gray screen and the same error.
System information

GPU: HD Graphics 4400 on Intel Haswell CPU
Driver: Mesa, 18.3.2.; 18.3.4; 19.1 (via PPA/Oibaf)
Wine version: 4.2 Staging; 4.3 Staging
DXVK version: 0.96; 1.0; latest Github master

Apitrace file(s)
apitrace_D3_x64.zip
Log files
Diablo III64_d3d11.log
Diablo III64_dxgi.log
Any help is appreciated! Thank you!

Haswell does not have good-enough Vulkan support to run DXVK.


remove API key from codeblock

the API keys for serper and openai were setup, in a awkward fashion, but were never used and are not needed here.

alternatively, we could have passed it as a crew arg. Let me know if that would be better or thats what was intended and i'll make the changes.

Hi @bassamadnan,
Thank you so much for your pull request! I just wanted to clarify that if no language model (LLM) is explicitly provided, we default to using OpenAI. We are also utilizing the Serper tool in the example, which needs the Serper API key to be set as an environment variable.
We appreciate your input and will work on making this process clearer. For now, I’ll close the PR, but please feel free to reach out if you have any questions or suggestions.
Thanks again!


Adding Navbar to the Blog section

Adding Navbar in the blog section to switch again to the main page and other page.

Please assign me this Issue under GSSOC'23.

Hey @ayushsachan123 , thanks for stepping up!
We are creating blog page through hashnode, so we won't be able to give access to everyone. If there is anything u would like to work on, pls go ahead!


Add readme file example and governance examples

Action point identified together with @zorp and @bvhme

Closing this issue as the implementation guide has governance examples and  #1 continues the work on readme examples


Generate auto-encoder architecture

There is a proper way to develop an auto encoder architecture network with subnetwork?
I tried to figure out how to generate subnetwork modules that will build a symmetric vanilla auto encoder architecture but didn't understand how to do it with this package

Hi @shimon166,
Yes it is possible. You would need to create a custom adanet.Subnetwork which implements the architecture you need.


CASM-3594: Add IMS checksum support to IUF manifest schema

Summary and Scope
This change adds support to the IUF manifest schema to allow products to specify MD5 checksums for each IMS artifact. MD5 checksums are supported for IMS recipes, and for each of the rootfs, kernel, and initrd artifacts in IMS images. MD5 checksums will be verified by the ims_upload operation prior to upload.
I don't have much experience authoring JSON Schemas, so I apologize in advance if there are issues with this change!
Issues and Related PRs
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.

Resolves CRAYSAT-3594

Testing
Tested on:

Local development environment

Test description:
Load schema and run against test schemas including IMS artifacts with MD5 checksums.
Risks and Mitigations
Are there known issues with these changes? Any other special considerations?
Pull Request Checklist

[x] Version number(s) incremented, if applicable
[x] Copyrights updated
[x] License file intact
[x] Target branch correct
[x] CHANGELOG.md updated
[x] Testing is appropriate and complete, if applicable
[x] HPC Product Announcement prepared, if applicable

@haasken-hpe, as I was addressing review comments I realized template_dictionary had the wrong type (string instead of object with string values), I have updated that as well. If you have a moment, I'd just like a quick check to make sure I've specified the types right.

@jack-stanek-hpe you need to bump the .version file as well. once it is merged we need to tag master branch with that version so the new image is released

When you rebase, please bump the version property in iuf-manifest-schema.yaml to 0.3.0 as well as the .version and Helm chart version updates.


samtools index: failed to open error

Good day,
I am using ClairS-TO using the following command:
singularity exec /apps/chpc/bio/clairs_to/clairs-to_latest.sif run_clairs_to -T BC1.sorted.bam -R GCF_000001405.40_GRCh38.p14_genomic.fna -t 8 -p ont_r10_dorado_hac_4khz --include_all_ctgs --output_dir output-BC1
I however get the following error (I don't get a final .vcf file but I do get many vcf files in the tmp folder):
samtools index: failed to open "/mnt/lustre/groups/CBBI1617/BreastCancer-fastq/SNV-analysis/input/output-BC1/tmp/phasing_output/phased_bam_output/tumor_NT_187421.1.bam": No such file or directory
ERROR in STEP 11, THE FOLLOWING COMMAND FAILED: ( parallel --joblog /mnt/lustre/groups/CBBI1617/BreastCancer-fastq/SNV-analysis/input/output-BC1/logs/phasing_log/parallel_3_haplotag_tumor.log -j 8 /opt/micromamba/envs/clairs-to/bin/longphase haplotag -o /mnt/lustre/groups/CBBI1617/BreastCancer-fastq/SNV-analysis/input/output-BC1/tmp/phasing_output/phased_bam_output/tumor_{1}.bam --reference /mnt/lustre/groups/CBBI1617/BreastCancer-fastq/SNV-analysis/input/GCF_000001405.40_GRCh38.p14_genomic.fna --region {1}  -s /mnt/lustre/groups/CBBI1617/BreastCancer-fastq/SNV-analysis/input/output-BC1/tmp/phasing_output/phased_vcf_output/tumor_phased_{1}.vcf.gz -b /mnt/lustre/groups/CBBI1617/BreastCancer-fastq/SNV-analysis/input/BC1.sorted.bam :::: /mnt/lustre/groups/CBBI1617/BreastCancer-fastq/SNV-analysis/input/output-BC1/tmp/CONTIGS ) 2>&1 | tee /mnt/lustre/groups/CBBI1617/BreastCancer-fastq/SNV-analysis/input/output-BC1/logs/phasing_log/3_tumor_haplotag.log && parallel -j 8 samtools index  -@8 /mnt/lustre/groups/CBBI1617/BreastCancer-fastq/SNV-analysis/input/output-BC1/tmp/phasing_output/phased_bam_output/tumor_{1}.bam :::: /mnt/lustre/groups/CBBI1617/BreastCancer-fastq/SNV-analysis/input/output-BC1/tmp/CONTIGS
Could I please get some assistance on this.

Hi, @DIPLOMICS-SA,
Thanks a lot for your interest on ClairS-TO. It seems that the issue was caused in the LongPhase haplotagging process, but we cannot be certain due to the lack of complete running log. Could you please provide your complete running log of run_clairs_to.log file, and we will check the issue for you further. By the way, to quickly obtain a result, you could rerun the program with your own data by adding another option --phase_tumor False and check if the issue still exists.
Lei

Hi @JasonCLEI thank you for getting back to me. please find the attached log file
Uploading run_clairs_to.log…

Hi, @DIPLOMICS-SA sorry for not seeing the attached log file. Could you please upload it again?

run_clairs_to.log
Hopefully this works @JasonCLEI

Hi, @DIPLOMICS-SA,
We have checked your complete running log and found that you are not using the latest image of ClairS-TO, which caused the issue above. You are suggested to re-pull the image and rerun the program with your own data with the latest release of ClairS-TO, and the issue may disappear. Let us know if there are any issues after that. Thanks a lot again for your interest on ClairS-TO.
Lei

Hi @JasonCLEI so I tried to re install the tool and I still get the same error?

Hi @DIPLOMICS-SA have you tried to delete the original clairs-to_latest.sif and then re-pull the latest image of ClairS-TO? If you have done so and still got the error, could you kindly provide your latest running log of run_clairs_to.log file?

Hi @DIPLOMICS-SA have you solved this problem at the moment? If you have done so and still got the error, could you kindly provide your latest running log of run_clairs_to.log file?


Failed to render and update auto layout status.

@gordoneliel when installing using pod it's saying failed to render and update auto layouts.

https://github.com/dji-sdk/Mobile-UXSDK-iOS/issues/24#issuecomment-383380822
Its is the problem with Cocoapod version 1.5.0
If you are using this you will get this error.
To remove your current version you could just run:
sudo gem uninstall cocoapods
you can install a specific version of cocoa pods via the following command:
sudo gem install cocoapods -v 1.4.0

Updated cocoapod, let me know if its still an issue


[#36] Fix Windows build

Closes #36

Coverage remained the same at 96.718% when pulling 437de4ea5d6949d95fc5fb94f61dae8075c10f9f on feature/36-fix-windows into 2278f64c294ab18bdd4360f479884a4798a72432 on master.

Coverage remained the same at 96.718% when pulling 437de4ea5d6949d95fc5fb94f61dae8075c10f9f on feature/36-fix-windows into 2278f64c294ab18bdd4360f479884a4798a72432 on master.


Warning coming:

When I run the code it shows this warning in the output result
WARNING:tensorflow:From /home/shresth/.local/lib/python3.5/site-packages/tensorflow/python/ops/nn_impl.py:1346: softmax_cross_entropy_with_logits (from tensorflow.python.ops.nn_ops) is deprecated and will be removed in a future version.
Instructions for updating:
What should I do ?

Can you just provide with the code so that i can help you?


Memory leak in fabric 1.19 version

I'm running a fabric server with a few (20-30) mods installed, and I'm running into some memory leak problems in the client.
I traced it back to this mod using Spark.
I also tried to start a single player world with only this mod, its dependencies and spark installed, and it's exibithing the same behaviour.
I don't have any clear step to reproduce this, but what I do is spawn some Luggages, fill them up with some stuff, pick them up, throw the item to the ground and spawn a couple of them again. This seems to always use up all the available JVM memory in a few minutes.
here's a spark heapsummary made right when it starts lag spiking:
https://spark.lucko.me/hx5GFp8ftE
installed mods:

fabric-api-0.57.0+1.19.jar
spark-1.9.26-fabric.jar
luggage-1.4.2-fabric.jar

let me know if you need additional information, thanks!

Thank you for reporting this, we'll look into a fix as soon as we can.
In the meantime, would you be willing to test the forge version as well? I'm curious if this is an issue on both versions or just fabric. I would do it myself but I'm gonna be unavailable for a little bit

Sure! I'll get to it as soon as I got some time.

Doesn't seem to happen in Forge
here's the spark heapsummary after about 20 minutes, tried to recreate the same conditions as in the fabric one roughly:
https://spark.lucko.me/9MpB0GsE6G
hope this helps!

Awesome, really glad to hear this isn't an issue on both versions.
 Was it just the 3 you mentioned initially, or did you have other mods loaded up as well? I'll need a whole list if there's any others. We want to identify any possible mod conflicts and fix those if it's not just the mod itself acting up.

So, I noticed the issue while playing with these mods installed (luggage currently removed):

Then I tried just leaving the three mods I mentioned in the first post and the problem remained, so I don't suppose it's a mod conflict.

Can you try the latest version I think it might possibly fix it

Gonna assume this is no longer an issue since I havent heard anything about it. If its still a problem let me know, I take stuff like this very seriously. Thanks for reporting!


Rotating the device goes back to the main page

As title says, every time.
Do you have any idea why it happens?

@avishayil I think it's related to https://github.com/facebook/react-native/issues/2716, I'll try to fix it


[minor] Update _utils.py

Fix grammar and formatting
IMPORTANT: PRs without the template will be CLOSED
Description of your pull request and other information

Code is a minor cosmetic grammar and formatting fix to the message that outputs when a download module fails.
Before submitting a pull request make sure you have:

[X] At least skimmed through contributing guidelines including yt-dlp coding conventions
[X] Searched the bugtracker for similar pull requests
[ ] Checked the code with flake8 and ran relevant tests (Errors will be upstream, this is a small cosmetic change)

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check all of the following options that apply:

[ ] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)
[X] Code is a minor change of a few characters, and cannot be copyrighted by the author.

What is the purpose of your pull request?

[ ] Fix or improvement to an extractor (Make sure to add/update tests)
[ ] New extractor (Piracy websites will not be accepted)
[X] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

Copilot Summary

🤖 Generated by Copilot at 835dac6
Summary
🐛📝🌐

Improved bug report message in yt_dlp/utils/_utils.py. Removed query string and fixed space issue in URL.

yt-dlp improves
No query string, no space
Clear URL in fall

Walkthrough

Removed the query string from the URL and fixed a space issue in the bug report message (link). This makes the URL more concise and readable, and avoids potential confusion or errors when copying and pasting the URL.

The extra spaces ae intentional

@pukkandan I don't understand why you need to keep them in?

@Atlas48, the ?q= , ' part is for a string concatenation.
compare these two case below,
print('Hello, '
'world')

Your version.
print('Hello,'
'world')

result is
Hello, world
Hello,world

Finally got around to producing the message, on my machine, it produces the following message:
WARNING: [youtube] unable to extract yt initial data; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U

That's two extra spaces, a typo, therefore, a bug.

As said they are intentional. Links, commands and similar in yt-dlp are denoted using surrounding spaces. Here I show the intention by enclosing them in <>:
WARNING: [youtube] unable to extract yt initial data; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
WARNING: [youtube] unable to extract yt initial data; please report this issue on <https://github.com/yt-dlp/yt-dlp/issues?q=>, filling out the appropriate issue template. Confirm you are on the latest version using <yt-dlp -U>

So this is where the second space comes from. on <https => on  https

y tho


refactor: Use full page forms instead of modals

Jira issue(s)
LC-324, LC-323

In CourseViewMainCard there should be <Viewer /> in course description

In lesson assigner card too, but I don't know if this should be in this PR


Test issue.

This is hashtag one.
This is hashtag two
** this is bold?**
what is this?
~and this?~

Thanks for playing.


Bulk string replacements using Spans

May need a lot of state:

Keep track of how many times the/each requested search string/ReadOnlySpan<char> occurs, their individual lengths, the length(s) of the replacement(s)
Calculate the new string's length using all of that
Fill it in a string.Create call


First set of "How to" pages

This PR includes a first set of "How to" pages in the docs, extending the basic example to perform common basic tasks, like integrating over R^d, using pre-evaluated samples, training without integrating or loading pre-trained models.

Thanks for the update Niklas. Could you please check the corrections I made in the branch ngoetz/howtos_v2? (the changes are only in the doc_build directory for now)
If you agree with these I will merge them into this branch and then merge the PR.

Yes I agree with the changes you made!


Bug / remove click events while timer runs Compare

If this works, please remove alerts in the compareMatch function!


Does code-server with security login validate ?

The code-server is very convenient coding tool on any mobile device. Does code-server with login in browser with security login validate? If yes, how to configure it.
e.g:

ip limit
login device limit
secondary confirmation
...

code-server only supports a single password and limits logins to two per minute plus twelve per hour.


Send user uid value to Google Tag Manager

Trello: https://trello.com/c/ZhLNktSm/644-add-user-id-tracking-to-content-publisher
This is so we can monitor session behaviour of particular users and see
when they're using different browsers/devices.
According to Andy it is acceptable privacy wise to send an id that has a
meaning in our internal systems but cannot be used out of context to
identify the user. I debated whether it would be better to run this
through a one way cryptographic hash function such as SHA1 but I'm not
sure that offers any actual benefits.

I see it's not introduced in this PR, but should we be using &. here to be on the safe side?

I don't think that is necessary as there are other parts of this file that rely on current_user being set and we have no scenarios considered where we anticipate unauthenticated access.
Similarly I'd say by doing that it looks like we have a clear plan of what to send if/when we did allow unathenticated access, when actually it's just a fallback and instead it might be that we'd want to send very different data to GTM if we had unauthenticated access.

@benthorner thanks 👍


ci(Mergify): configuration update

This change has been made by @bmcmanus-apex from Mergify config editor.

@mergifyio queue


Singletons

Some svelte framework components - such as svelte skeleton toast - use singletons created in top-level sveltekit files such as +layout. For example, a function is called inside the script tag of a .svelte file (not in an onMount etc callback, just inline in the script tag). I am guessing these functions create a svelte context that is referenced by other components. Needless to say, this doesn’t work with LiveSvelte unless you do something similar and have a parent svelte component with slots and/or subcomponents. Every component must have the same ancestor component in order to access the same context object. This doesn’t work very well with LiveSvelte since it locks you out of building an app consisting of a combination of live views, dead views, and live svelte components. I’m wondering whether anyone has found a work around to this. I suspect there isn’t one.

If it's just setting the context object it's possible probably. The context right here, https://github.com/woutdp/live_svelte/blob/master/assets/js/live_svelte/hooks.js#L106-L110
Currently there's no way to do it but we can expose this, just like how it's being done with props.

Ok, leaving this issue in the backlog for now. But feel free to make a PR that integrates this functionality.

Closing for now as there's not progress on this


Nested list cannot contain elements that do not exist in parent document

Example:
if my document is:
{
"id":"123",
"name":"Ely",
"contacts":[{
"id": "2323343",
<EMAIL_ADDRESS>}]
}
will return an error because the email key does not exist in the root, but when removing the email, the list will return the nested id

Sorry for the delay in answering this. I'll be reviewing everything in the next days.

I fixed the json encoding problems.
Please use version 0.1.2.
Again, I'm sorry for the delay!


1-Introduction/3-fairness/translations/assignment.es.md

I had forgotten to organize the files within the corresponding folder, check that each file is in its place.


can't upload

http://scratch.mit.edu/projects/291318377
http://phosphorus.github.io/#291318377
Error: HTTP 404:
    at XMLHttpRequest.xhr.onload (https://phosphorus.github.io/phosphorus.js:224:23)

this is my assignment. i want to convert this game to mobile apps, but can't ..


Add Support For Mapping Basic CloudFront Setup

The mapping would just need to include the distro, along with an optional parameter to have any instances it's fronting mapped as well (via #228 ).

Format should be:
FQDN -> Distro ID -> Origin IDs -> Origin Tgts


Ship Snowflake JDBC driver as soon as authorised

At the moment we ask users to download the Snowflake JDBC driver from Maven Central. As soon as we have permission to do so, ship it out of the box with Flyway.

The driver is licensed under Apache 2.0, which permits distribution. https://github.com/snowflakedb/snowflake-jdbc/blob/master/LICENSE.txt . Will be added to 6.4.1.


[Multi-agent] Init. added few non-conflicts attributes

Adding multi-agent

Added some non-conflicts attributes

Pending tasks

Handle observation and rendering in human perspective

Thank @Edwardhk for initializing the MARL development! This PR has empowered everything in PGDriveEnv with multi-agent potential. We will start developing (placing objects and dealing with the reward, observation and others) MARL envs in future PRs!


DOC-9636 PR #118787 - ui: take non-negative derivative of full scan chart

Fixes DOC-9636
(1) In ui-sql-dashboard.md, (a) modified description of Full Table/Index Scans to specify non-negative rate, (b) added link to Statements page filter, (c) fixed typo in description for the Connection Latency.
rendered preview: SQL Dashboard page

This LGTM, but I don't understand why we need to specify that a "total number" of scans is non-negative. Is that worth clarifying, or will it be clear to the user?

For most users clarifying it is a "non-negative rate" is not necessary. For users who may want to try to reproduce this graph using Advanced Debug or Prometheus, it might be helpful.


Data Science with Python : Hyperparameter Tuning

Welcome to 'DSWP' Team, good to see you here
This issue will helps readers in know all the information before working on Hyperparameter Tuning. Brief elaboration along with sample code of Hyperparameter Tuning is needed.
To get assigned to this issue, add your serial numbers mentioned in the spreadsheet of "Data Science with Python", the approach one would follow and choice you prefer (Documentation, Audio, Video). You can go with all three or any number of options you're interested to work on.
If you had referred any resources, add them up in "DS Resources". Similarly if you had used datasets, include them in "DS Datasets".
Domain : Machine Learning
Mentors Assigned : Dhruv Bajaj / Peehu Saxena
Points to Note :
The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Changes should be made inside the Datascience_With_Python/ directory & Datascience_With_Python branch.
Follow Contributing Guidelines & Code of Conduct before start Contributing.
This issue is only for 'GWOC' contributors of 'DSWP' domain.
All the best. Enjoy your open source journey ahead. 😎

I would like to work on this issue. I will add the code explaining the topic along with comments. The .ipynb notebook will have codes explaining the stuff from scratch.
I am Medini N B. Serial Number : 585, DSWP batch - 16

Hello, I am Gopinath Balaji with serial number: 315. I would like to do documentation on this issue.
I would like the explain the basics of hyperparameter selection and tuning

@imedusa, issue assigned on FCFS for documentation.
@GopinathBalaji, many more issues arriving up.

Thank you @prathimacode-hub

I would like to work on this.
Mohit kumar
Type: Doccumentation
Issue: 386
Approach: what is  Hyperparameter Tuning, how to do Hyperparameter Tuning and find the best parameter for the model

This file/issue will be mentored by me. @prathimacode-hub

Hello, I am Deepthi M with serial number:172, Batch-5. I would like to do audio on this issue.
My approach: a detailed explanation

Issue assigned to @deepthi1107 for audio contribution


Load kontena-cli gemspec on start

This PR makes lib/kontena_cli.rb load ../kontena-cli.gemspec and activate the spec.
This should prevent plugins from loading any earlier versions of CLI and prepending their paths to $LOAD_PATH. Especially when running in development from bin/kontena. Running the gem install version should already activate the CLI gem when loading.
Adding puts Gem.loaded_specs['kontena-cli'].inspect to some command's execute showed an earlier version of kontena-cli I have installed instead of the 1.3.0.dev I was running it from.
After the changes to lib/kontena_cli.rb in this PR, it showed the correct version.

I'm left wondering why we need to do this kind of low-level gemspec wrangling. Shouldn't this kind of gem 'kontena-cli' activation be standard procedure for all bin scripts corresponding to installed gems?

We are using a stanard bin wrapper:
#!/usr/local/opt/ruby/bin/ruby
#
# This file was generated by RubyGems.
#
# The application 'kontena-cli' is installed as part of a gem, and
# this file is here to facilitate running it.
#

require 'rubygems'

version = ">= 0.a"

if ARGV.first
  str = ARGV.first
  str = str.dup.force_encoding("BINARY") if str.respond_to? :force_encoding
  if str =~ /\A_(.*)_\z/ and Gem::Version.correct?($1) then
    version = $1
    ARGV.shift
  end
end

if Gem.respond_to?(:activate_bin_path)
load Gem.activate_bin_path('kontena-cli', 'kontena', version)
else
gem "kontena-cli", version
load Gem.bin_path("kontena-cli", "kontena", version)
end

Documentation for activate_bin_path says:

A side effect of this method is that it will activate the gem that contains the executable.

So, for installed kontena-cli this is no problemo, as stated in the description:

The problem this PR fixes should only occur when running bin/kontena from the cli/bin directory, because that does not activate the gem, it just does require 'kontena_cli' and does not even know that this thing is actually a gem.

I think we should maybe stop running bin/kontena directly instead of hacking in our own support for gem activation into the CLI itself.

EDIT: for development, that means running bundle exec bin/kontena instead of just bin/kontena

Which is super difficult to combine with plugins.

IMO this PR is still a bad idea, we shouldn't need to do our own gem activation... OTOH it does mean that the only currently known way to dev with plugins is using gem build kontena-cli.gemspec && gem install kontena-cli-*.dev.gem to get the standard binwrapper.


Fixed #4 and removed warnings

Fixed to_str(expr) function to correctly write exponentials
Replaced Compat.UTF8String by String to clear warnings

Thanks!


Danger

Short description 📝
Add Danger

For maintainability reasons, we'll move the Danger configuration into an organization repository that can be shared across all the repositories. https://github.com/xcodeswift/danger


Added a couple of features

@plentz I added a couple of features that helped a scenario I needed.  All tests are passing.
I also updated code in the grunt file to reflect your previous commit to fix the licesenses, https://github.com/plentz/jquery-maskmoney/commit/df01b1b6c5ebbf610f22f3b17aad5baf143463c2.
Let me know if there is anything else I need to do to get this the green light.

@abduncan l'll see later.

LGTM


Start handling default types when serialising query setting values

Refs #3024
Looks like this:
{ "type": "SettingQuery", "setting": "t/scalaVersion" }
{"type":"SettingQueryResponse","value":"2.12.1"}

{ "type": "SettingQuery", "setting": "t/baseDirectory" }
{"type":"SettingQueryResponse","value":"file:/s/t/"}

{ "type": "SettingQuery", "setting": "t/sourcesInBase" }
{"type":"SettingQueryResponse","value":true}

{ "type": "SettingQuery", "setting": "t/sourceDirectories" }
{"type":"SettingQueryResponse","value":["file:/s/t/src/main/scala-2.12","file:/s/t/src/main/scala","file:/s/t/src/main/java","file:/s/t/target/scala-2.12/src_managed/main"]}

{ "type": "SettingQuery", "setting": "t/scalaArtifacts" }
{"type":"SettingQueryResponse","value":["scala-library","scala-compiler","scala-reflect","scala-actors","scalap"]}

{ "type": "SettingQuery", "setting": "t/startYear" }
{"type":"SettingQueryResponse","value":null}

{ "type": "SettingQuery", "setting": "t/pollInterval" }
{"type":"SettingQueryResponse","value":500}

{ "type": "SettingQuery", "setting": "t/maxErrors" }
{"type":"SettingQueryResponse","value":100}

Still TODO: Supporting LM types and util types, such as ModuleID.

Is it possible to capture the type of the response as FastTypeTag or String representation of it?
{ "type": "SettingQuery", "setting": "t/sourcesInBase" }
{"type":"SettingQueryResponse","contentType":"Boolean","value":true}

Sure, we have the full Manifest of it:
scala> manifest[List[Option[Int]]]
res1: Manifest[List[Option[Int]]] = scala.collection.immutable.List[scala.Option[Int]]

@eed3si9n the question is how do we respond with failure?

The same way sbt or a database would respond on bad query.
zinc Root> show fooo
[error] Not a valid key: fooo (similar: fork)
[error] show fooo
[error]          ^

I mean in terms of the payload shipped over the socket. Or if you prefer, in terms of the contraband data type definition. Currently I have it defined as:
type SettingQueryResponse implements EventMessage {
  value: String!
}

How should it communicate "Not a valid key: fooo (similar: fork)"?

We could send another event type for errors:
{ "type": "SettingQuery", "setting": "t/fooo", "queryId": "0000-1111" }
{ "type":"SettingQueryError", "message": "Not a valid key: fooo (similar: fork)", "queryId": "0000-1111"}

blocked on the modules upgrade - #3031

and depends on sbt/util#73 being accepted, merged and released.

Here's what it looks like, before switching how to obtain the JsonWriter:
{"type":"ChannelAcceptedEvent","channelName":"channel-1"}

{ "type": "SettingQuery", "setting": "t/scalaVersion" }
{"type":"SettingQuerySuccess","value":"2.12.1","contentType":"java.lang.String"}

{ "type": "SettingQuery", "setting": "t/baseDirectory" }
{"type":"SettingQuerySuccess","value":"file:/s/t/","contentType":"java.io.File"}

{ "type": "SettingQuery", "setting": "t/sourcesInBase" }
{"type":"SettingQuerySuccess","value":true,"contentType":"Boolean"}

{ "type": "SettingQuery", "setting": "t/sourceDirectories" }
{"type":"SettingQuerySuccess","value":["file:/s/t/src/main/scala-2.12","file:/s/t/src/main/scala","file:/s/t/src/main/java","file:/s/t/target/scala-2.12/src_managed/main"],"contentType":"scala.collection.Seq[java.io.File]"}

{ "type": "SettingQuery", "setting": "t/scalaArtifacts" }
{"type":"SettingQuerySuccess","value":["scala-library","scala-compiler","scala-reflect","scala-actors","scalap"],"contentType":"scala.collection.Seq[java.lang.String]"}

{ "type": "SettingQuery", "setting": "t/startYear" }
{"type":"SettingQuerySuccess","value":null,"contentType":"scala.Option[Int]"}

{ "type": "SettingQuery", "setting": "t/pollInterval" }
{"type":"SettingQuerySuccess","value":500,"contentType":"Int"}

{ "type": "SettingQuery", "setting": "t/fooo" }
{"type":"SettingQueryFailure","message":"Expected ':' (if selecting a configuration)\nNot a valid key: fooo (similar: fork)\nt/fooo\n      ^"}

{ "type": "SettingQuery", "setting": "scalaVersion" }
{"type":"SettingQueryFailure","message":"Not a valid project ID: scalaVersion\nscalaVersion\n            ^"}

{ "type": "SettingQuery", "setting": "t/scalacOptions" }
{"type":"SettingQueryFailure","message":"Key {file:/s/t/}t/compile:scalacOptions is a task, can only query settings"}


[stable/prometheus-adapter] add new resourceRules in values

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

Enables adding resourceRules to the configMap

Tested by setting the values from the project's deploy example and then the usage example for HPA.
~* Also modified hpa-external-metrics-cluster-role-binding.yaml ServiceAccount, I could not figure out why it was hardcoded to horizontal-pod-autoscaler but let me know it it is correct and I will revert.~
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/ok-to-test

@dkoshkin I took this for a test spin locally and it looks good except for one thing. I had to change the rate interval in the example resource metrics from 1m to 3m for it to work. I'm guessing it can work at 1m for some people, but just to be safe lets bump it in the README and values to 3m. Other than that looks great and I can approve soon.

@steven-sheehy changed to 3m in both the query and window (not sure if this is what you tested with though)


:sparkles: feat(enharmonic): use pipe | in toString output

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
814

Relevant Lines:
814

💛  - Coveralls


KOGITO-5264: Create CLI tool to generate forms from tasks json schemas in Kogito Projects [WIP]

@tiagobento another WIP PR!

@pefernan Build is still failing. I think we should build for x86 on macOS. For macOS arm64 computers we would rely on Rosetta 2 for now.

As alternative, I can manually try with arm if necessary.

jenkins retest this please

@ljmotta updated!


Update user guide

Codecov Report
Base: 50.92% // Head: 50.92% // No change to project coverage :thumbsup:

Coverage data is based on head (5e37cb1) compared to base (3bd26a1).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #187   +/-   ##
=========================================
  Coverage     50.92%   50.92%
  Complexity      474      474
=========================================
  Files           108      108
  Lines          2099     2099
  Branches        239      239
=========================================
  Hits           1069     1069
  Misses          978      978
  Partials         52       52

Impacted Files
Coverage Δ

src/main/java/seedu/address/ui/HelpWindow.java
0.00% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Export kind logs in e2e tests

Talking with @BenTheElder in the context of test failures, we found out that there is a recommended way to get all the logs for kind.
We currently get the logs of a few of the components of k8 but we are missing kubelet and other logs.
kind export logs $ARTIFACTS

Can give more logs around kind and help diagnose more issues.

https://github.com/kubernetes-sigs/jobset/blob/main/hack/e2e-test.sh is the code where we export some of the kind logs.
This could probably be cleaned up to use kind directory to generate this without having to explictly call out the components we want.


Move JS resolution code and JSLibResolveException to jsdep package

They are historically in the classpath package but do really not depend on anything in it, so we should move them.

Thinking of it, it makes perfect sense where it is, since it depends on the libraries on the classpath itself.


[swift/main] Adds SPI for a NSRE compatibility mode option (#698)

NSRegularExpression matches at the Unicode scalar level, but also matches \r\n sequences with a single . when single-line mode is enabled. This adds a _nsreCompatibility property that enables both of those behaviors, and implements support for the special case handling of ..
Cherry pick of #698.

@swift-ci Please test

@swift-ci Please test Windows platform

@swift-ci Please test macOS platform
@swift-ci Please test Linux platform

@swift-ci Please test macOS platform

@swift-ci Please test Windows platform

@swift-ci Please test Windows platform


Experiencing panic on call to Client::request()

Rust: 1.28
hyper: 0.12.9
hyper-tls: 0.3.0
I am trying to use hyper + hyper-tls to query the GitHub API. I am using the following code:
let https = HttpsConnector::new(4).unwrap();
        let client = Client::builder().build(https);

        let uri: hyper::Uri = format!("https://api.github.com/repos/{}/{}/collaborators", self.owner, self.name).parse().unwrap();
        let mut req = Request::get(uri).body(hyper::Body::empty()).unwrap();
        {
            let headers = req.headers_mut();
            headers.insert(AUTHORIZATION, HeaderValue::from_static("***"));
            headers.insert(USER_AGENT, HeaderValue::from_static("github-rust"));
        }

        client.request(req)
            .and_then(|res| {
                // asynchronously concatenate chunks of the body
                println!("Status Code: {}", res.status());
                res.into_body().concat2()
            })
            .from_err::<GitHubError>()
            // use the body after concatenation
            .and_then(|body| {
                // try to parse as json with serde_json
                // let collaborators = serde_json::from_slice(&body)?;
                Ok(vec![])
            })
            .from_err()
            .wait()

This causes the following panic:
0:     0x561c7976d84e - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::h845003dfd4057b58
                               at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1:     0x561c7975dbb6 - std::sys_common::backtrace::print::he21204c91f031ba1
                               at libstd/sys_common/backtrace.rs:71
                               at libstd/sys_common/backtrace.rs:59
   2:     0x561c7975bb8d - std::panicking::default_hook::{{closure}}::h67eac88e3f053d87
                               at libstd/panicking.rs:211
   3:     0x561c7975b900 - std::panicking::default_hook::hb9cbad724f559203
                               at libstd/panicking.rs:227
   4:     0x561c7975c22c - std::panicking::rust_panic_with_hook::he4c3a67f6258a8f9
                               at libstd/panicking.rs:511
   5:     0x561c7943217e - std::panicking::begin_panic::h1b22e390639de3a8
                               at /checkout/src/libstd/panicking.rs:445
   6:     0x561c7943c1ec - github_rust::tests::repository::get_collaborators::h3972b115f6e3edbc
                               at src/tests/repository.rs:12
   7:     0x561c79410339 - github_rust::__test::TESTS::{{closure}}::hd09af2d36ae7102d
                               at src/tests/repository.rs:4
   8:     0x561c793fc40d - core::ops::function::FnOnce::call_once::h9e439894db815e0d
                               at /checkout/src/libcore/ops/function.rs:223
   9:     0x561c794be14e - <F as alloc::boxed::FnBox<A>>::call_box::h35131d468a43c8d1
                               at libtest/lib.rs:1451
                               at /checkout/src/libcore/ops/function.rs:223
                               at /checkout/src/liballoc/boxed.rs:640
  10:     0x561c7977af99 - __rust_maybe_catch_panic
                               at libpanic_unwind/lib.rs:105
  11:     0x561c794da8ad - std::sys_common::backtrace::__rust_begin_short_backtrace::h02641c0f08c89101
                               at /checkout/src/libstd/panicking.rs:289
                               at /checkout/src/libstd/panic.rs:392
                               at libtest/lib.rs:1406
                               at /checkout/src/libstd/sys_common/backtrace.rs:136
  12:     0x561c794df6a4 - std::panicking::try::do_call::h1d3083628cca3de7
                               at /checkout/src/libstd/thread/mod.rs:409
                               at /checkout/src/libstd/panic.rs:308
                               at /checkout/src/libstd/panicking.rs:310
  13:     0x561c7977af99 - __rust_maybe_catch_panic
                               at libpanic_unwind/lib.rs:105
  14:     0x561c794d0d36 - <F as alloc::boxed::FnBox<A>>::call_box::h2f7e4058ba7bf228
                               at /checkout/src/libstd/panicking.rs:289
                               at /checkout/src/libstd/panic.rs:392
                               at /checkout/src/libstd/thread/mod.rs:408
                               at /checkout/src/liballoc/boxed.rs:640
  15:     0x561c79759aca - std::sys_common::thread::start_thread::h88a639c99862a9f5
                               at /checkout/src/liballoc/boxed.rs:650
                               at libstd/sys_common/thread.rs:24
  16:     0x561c7975cdf5 - std::sys::unix::thread::Thread::new::thread_start::h7d7a420a78cfa84d
                               at libstd/sys/unix/thread.rs:90
  17:     0x7f1e48687090 - <unknown>
  18:     0x7f1e48593efe - __clone
  19:                0x0 - <unknown>

The panic, occurs before the first and_then is called.
I am probably doing something wrong on my end, and would like to be corrected if so. Thanks!

The backtrace shows that just before starting the panic steps, it got to at src/tests/repository.rs:12 in your code. What's that line?
Note that calls to unwrap() are a way of converting a fallible operation in a panic, saying "if this errors, crash me here". If it shouldn't crash, you should consider how to handle the Err case. If it should, you may want to replace them with expect("description of why this crash is appropriate").

I'm going to close this since it doesn't look like the panic is happening inside hyper. If I'm wrong, we can re-open!

Thanks Sean. I believe you were probably right. I never got a chance to go back to look at the code, as the project has started to take a different direction, but thank you for the time you gave me.


Show hidden facet filters as greyed out instead of hiding them

When selecting facets it is possible for a new facet selection to hide previous terms selected in a different facet as they are no longer exist in the result set. Currently, we remember what facets were selected, and hide the non-applicable selected facets from the user. If the facets become applicable again, we show them again as selected. This prevents selecting a facet from destroying a built-up query.
Let's look at showing the hidden non-applicable selected facets but in a way that shows they are inactive. (Greyed out and non selectable for example)

Resolved in the react rewrite


Syslog does not get send to external syslog server

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x ] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x ] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
We have configured our Opnsense router to send Syslog traffic to a central syslog server. But after configuring it to send it to that central server it does not get send there.
Tip: to validate your setup was working with the previous version, use opnsense-revert (https://docs.opnsense.org/manual/opnsense_tools.html#opnsense-revert)
To Reproduce
Steps to reproduce the behavior:

Go to system-->settings-->logging
Click on remote
Add the device there and enable it

Expected behavior
That the syslog data gets send to that IP address.
Describe alternatives you considered
We did not consider any alternatives as this is a basic part of opnsense
Screenshots
Relevant log files
If certain logs are needed please ask for them. We will try to supply them as soon as possible
Additional context
When we check the firewall on the side of the syslog server we see Syslog traffic from other hosts go in but do not see any traffic from the IP address of the Opnsense router.
I have also tried to restart the syslog-ng server multiple times but that did not solve the issue
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 24.7.3_1(amd64). This version will be updated to the lastest version tonight
AMD Ryzen 9 5950X 16-Core Processor (2 cores, 4 threads)
Virtual network(Router is hosted on Hyper-V)

After the update and a reboot it started working. So this problem is solved.


Roc 5.6.x to docs/5.6.1

Fix RHEL9 instructions
Update 5.6.0 to 5.6.1 instructions

Note: this new branch (update-561) was created due to merge conflict between roc-5.6.x and docs/5.6.1
ie: to avoid merging docs/5.6.1 into roc-5.6.x


Update collectBalance.php

Call to undefined method mysqli_stmt::get_result() Fatal error: collectBalance.php on line 6

Aww, yeah. This is mysqlnd specific. Will fix that asap.

Done.