Support reload certs in HTTPS server.

[ ] If this is non-trivial feature, paste the links/URLs to the design doc.

[ ] Update the documentation to include this new feature.

[ ] Tests(including UT, IT, E2E) are added to verify the new feature.

[ ] If it's UI related, attach the screenshots below.

[ ] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.

[x] Update the CHANGES log.

I forget add a unit test, I will do it later.

I think usually we need a manual test. I don't think tls could be easily tested.
Wait for @kezhenxu94

I think usually we need a manual test. I don't think tls could be easily tested.
Wait for @kezhenxu94

To test the reloading mechanism, we can recreate new cert pairs with scripts and update them in test and verify the API still works before and after the update, but I'm totally ok if you don't want to test this case. But we need to add a basic case that verify the https works, the same situation exists in our gRPC agent protocol server in this repo. You can take that as an example.

I have not tested it now. I will test it after they armeria release a new version.

Armeria 1.22 is released you can continue this. https://armeria.dev/release-notes/1.22.0/

Got it , But when I was writing tests for dynamodb, I found that after loading the certificate on skywalking, aws would not successfully send data to the endpoint, while when loading the certificate on nginx and routing it to skywalking, aws could successfully send data to the endpoint. So the existing https server may have some bugs, I will test and finish this PR after the PR about dynamodb is finished

By following https://github.com/apache/skywalking/pull/10409, we don't need to support TLS.
Close this too.


The environment variable does not return the saved value as expected.

I have checked the following:

[X] I use the newest version of bruno.
[X] I've searched existing issues and found nothing related to my issue.

Describe the bug

Value shown in accessing environment variable:

Value shown in saved environment variable:

Saved environment variable is dynamically updated when requesting a get token. The response script is

// Save the extracted data to an environment variable
let data = res.getBody();
bru.setEnvVar("API_TOKEN", data.token);
bru.setEnvVar("USER_ID", data.user.id);

.bru file to reproduce the bug
No response
Screenshots/Live demo link

I had to go back to 1.24 ran into other env variable issues in latest

I think those variables that you create on script are keep into the eye icon at right

Hi you are correct they are kept as a variable but in 1.24 and 1.25 you can recall those values in the query body it doesnt appear that in later builds that is possible. just stating this is a regression and likely affects a bunch of folks. I use a query in one request, save a value from that response for another request.

I'm seeing a similar issue. I have a request where I use the Vars tab to save a post response variable. In 1.24 the variable shows up in runtime variables with the correct value, but in 1.28 the variable shows up as undefined.


steeringRatio autotuning resulting in assumingly absurd high values

Why does it seem that OP is autotuning steerRatio to, what some may say, absurdly high values? Josh's Accord is 16, my Prius is 16, Arne's Rav 4 is settling at 15.9, Bugsy's Camry Hybrid 16. Meanwhile, factory end-to-end spec on my Prius Prime is 13.4.
Is there a benefit for OP to be tuned to a much higher end to end ratio value than factory spec?
Prius tuning is commented ret.steerRatio = 15.00   # unknown end-to-end spec in interface.py . Would it be beneficial to set this to the spec of 13.4? Or would autotuning crank it up to 16 again anyway?
Trying to work on https://github.com/commaai/openpilot/issues/599
in the mock interface.py, 13 is deemed "reasonable"
ret.steerRatio = 13. # reasonable

This issue may be not applicable due to variable ratio steering
@Gernby  I'm not aware of any OP capable vehicle that doesn't have variable ratios, and the ratio is always highest in the middle.  The factory spec is usually end-to-end, which really isn't useful for anything in OP.


[BUG] Widget is not working with Jupyter Notebook (but with Jupyter Lab)

Describe the bug
When using the widget in a Jupyter Notebook (not Lab) the widget is not displayed at all.
But there are errors in the browser debug console.
Steps/Code to reproduce bug

Install Clara Viz and Jupyter Notebook
Start Jupyter Notebook server with jupyter notebook --no-browser --ip=*
Open a browser and open the Jupyter server IP address
Open and execute a example notebook
No widget is displayed

Expected behavior
The widget should work with Jupyter Notebook.
Environment details (please complete the following information)

OS/Platform: Linux
Python Version: 3.6
Clara Viz Version: 1.0.1

Additional context

Fixed with v0.1.2.


Add Type System Overview doc

I've been working on this on and off for the past month. I still don't consider it done, but maybe someone will benefit from this as-is. They will certainly not benefit if it's only on my hard drive.
I was following the CoreCLR BOTR format. I guess the "R" part of the name still makes sense if you squint hard.
The pull request has both the SVG and PNG file. Unfortunately I can't refer to the SVG file from the doc because SVG apparently opens up the document to cross site scripting attacks.

@davidwrighton Can you have a look please?

Thanks for starting this.
It might be a good idea to add a note that it refers to the type system as seen by CoreRT to generate native code and not the native implementation of reflection. The first sentence is a little bit ambiguous on this front when it refers to type system users.
Also if possible, if you could add an actual example where SignatureVariable is actually used, that would help.

Looks great to me! Thanks for writing it.


Stricter checks on both co- and contra-variant interface assignments

TypeScript Version:
2.5.3
Code
class C1 {
    a: string;
}

class C2 {
    a:string;
    b:string;
}

interface I<T> {
    m(t:T):T
}

let a:I<C1>;
let b:I<C2>;
a = b; // <-- Not a typescript compiler error
a.m({a:''}) // <-- The I<C2> instance's "m" method requires property b

b = a; // <-- However, this produces an error

Expected behavior:
I would expect that Typescript reported the a = b assignment as an error. Consider this a feature request for it.
Actual behavior:
Nothing

See #18654

Great!


Feature/filter-request

All backend is in place to filter by all necessary fields. Just needs front end to take advantage of it.

looks good, merging in


History title

support history title, all tests should be fixed

LGTM. @Samyak2 what do you think? It is a breaking change.

Codecov Report
Patch coverage has no change and project coverage change: -0.40% :warning:

Comparison is base (3a34d12) 97.95% compared to head (4a632cb) 97.55%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the GitHub App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #247      +/-   ##
==========================================
- Coverage   97.95%   97.55%   -0.40%
==========================================
  Files           5        5
  Lines         488      490       +2
  Branches      103      104       +1
==========================================
  Hits          478      478
- Misses          3        4       +1
- Partials        7        8       +1

Flag
Coverage Δ

unittests
97.34% <0.00%> (-0.40%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

browser_history/browsers.py
100.00% <ø> (ø)

browser_history/cli.py
94.66% <0.00%> (ø)

browser_history/generic.py
97.59% <0.00%> (-0.95%)
:arrow_down:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Thanks guys!


Pack command

The first (and most important) part of #521 . Still missing a convert from nuget option, but I'm slightly unsure how to proceed on that one as I have not supported (and do not plan to support) all possible nuspec options. Still, this should be usable in it's own right.
This is still very much alpha quality, but it does work for most simple cases. I'm not sure if you want to merge now with warnings or leave this pull request open for a while. It's already pretty chunky though!

I'll try and get the test passing in mono as well...

I think we should merge this and release it as prerelease in order to give people a chance to try it out.
Then we should change Paket's own build process to dogfood this. (and maybe add a push command to get rid of Nuget.CommandLine)

@forki the last travis build failed due to mono not being installed. Can we trigger a rerun to test the path changes? Either that or a helpful volunteer running some tests on *nix would be great!

Agreed it would be good to dog food this as a pre-release. We'll be doing the same thing internally here, so between the two we should iron out the bugs in a couple of different use cases.

an easy way to trigger the build is to force push a small change. Maybe
it's a good opportunity to rebase on current master ;-)
2015-02-17 17:50 GMT+01:00 Michael Newton<EMAIL_ADDRESS>
Agreed it would be good to dog food this as a pre-release. We'll be doing
the same thing internally here, so between the two we should iron out the
bugs in a couple of different use cases.
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/pull/613#issuecomment-74702248.

 Squashed a few commits for neatness as well.

...and messed up the rebase :(. I'll try again shortly.

yay we have a green build

Yeah, actual tests detecting actual (potential) bugs and everything. I feel all engineery, although I could have spotted the root cause a little quicker :)
Just spotted that it doesn't create the output directory if it doesn't already exist. I'll add that, and then it'd be good to merge to start the dog fooding process.

Basic sanity checks and build both pass.

:+1:


Scheduler: Assign participants to roles they got less

The most affected participants have a 4:1 ratio of role assignments (see: https://docs.google.com/spreadsheets/d/1-TzBe8BiMW3x2XGae5ZxLByX3yNUmKwMpneuEjy-cmw/ ; probably even worse given those metrics also include older workspaces). It's mostly bad insofar as participants prefer to vary roles, and it would probably also be good for people to evolve at a similar paste on all roles for strategy evolution (I don't think specializing is the way to go, at least not at this stage, although I'm not confident about this).
Improving role assignment based on scheduling priorities when creating trees would also help (maybe improve by up to 50%): https://github.com/oughtinc/mosaic-api-scripts/issues/17
But to solve it entirely, the scheduler would need to assign participants to roles based on what roles they've done the less so far.
@zjmiller , Jungwon and I are discussing this issue, and I would like to have your take on it as well. What do you think we should do?
An idea would be to still have the scheduler look at schedulingPriority first, and then have it look at roles less done. But then update the schedulingPriority of trees in such a way that there are ten for each levels (10 with priority 1, 10 with priority 2, etc.).
Other ways to do it:
-to look at past roles first
-do a combination of past roles and scheduling Priority
Or we could disregard this issue entirely, and just create the following feature instead: "Make it possible for participants to choose which role to get a workspace from (out of roles where there are available workspaces)" (see: https://github.com/oughtinc/mosaic/issues/625).

Hmm, I think any of these would be a significant change to the scheduler. What seems better to you all (@Mati-Roy @jungofthewon @brachbach): Having the scheduler try to balance the different roles (i.e., judge, honest, malicious) or letting participants set a preference for a certain role (that they can change in between workspaces).

I think it's much better to let participants set preferences, rather than just trying to balance between the roles.
Regardless of which way we go, we need to figure out how to balance this against other priorities in scheduling. I think this might be the time to switch to score-based scheduling a la https://github.com/oughtinc/mosaic/pull/677/files

(Note: I think my comment here is a bit scanty and doesn't move things forward as much as it should. I'm planning to revisit this issue within the next day once I have a better idea of what we should be working on dev-wise with Mosaic.)

(I haven't added more thoughts yet on this issue because I don't think it's a top priority)


improve docs: useList demo link

Added a demo link for useList

@wardoost, added rest callbacks :)

Updated, https://codesandbox.io/s/wonderful-mahavira-1sm0w

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Unicode characters in error message cause problems with LC_ALL=C

Hi,
Two things, same cause, I believe.
ubuntu@ip-172-31-65-80:~$ LC_ALL=C sacrebleu --help
Traceback (most recent call last):
  File "/usr/local/bin/sacrebleu", line 11, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.5/dist-packages/sacrebleu.py", line 762, in main
    args = arg_parser.parse_args()
  File "/usr/lib/python3.5/argparse.py", line 1735, in parse_args
    args, argv = self.parse_known_args(args, namespace)
  File "/usr/lib/python3.5/argparse.py", line 1767, in parse_known_args
    namespace, args = self._parse_known_args(args, namespace)
  File "/usr/lib/python3.5/argparse.py", line 1973, in _parse_known_args
    start_index = consume_optional(start_index)
  File "/usr/lib/python3.5/argparse.py", line 1913, in consume_optional
    take_action(action, args, option_string)
  File "/usr/lib/python3.5/argparse.py", line 1841, in take_action
    action(self, namespace, argument_values, option_string)
  File "/usr/lib/python3.5/argparse.py", line 1025, in __call__
    parser.print_help()
  File "/usr/lib/python3.5/argparse.py", line 2367, in print_help
    self._print_message(self.format_help(), file)
  File "/usr/lib/python3.5/argparse.py", line 2373, in _print_message
    file.write(message)
UnicodeEncodeError: 'ascii' codec can't encode character '\xe9' in position 454: ordinal not in range(128)

and installation with pip (not pip3, in the same enviroment with LC_ALL=C):
ubuntu@ip-172-31-65-80:~$ sudo -H pip install sacrebleu
Collecting sacrebleu
  Using cached sacrebleu-1.0.3.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-build-iHSRfo/sacrebleu/setup.py", line 13, in <module>
        import sacrebleu
      File "/tmp/pip-build-iHSRfo/sacrebleu/sacrebleu.py", line 3
    SyntaxError: Non-ASCII character '\xc3' in file /tmp/pip-build-iHSRfo/sacrebleu/sacrebleu.py on line 4, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-iHSRfo/sacrebleu/

Works fine with:
LC_ALL=en_US.UTF8 sacrebleu --help

Can't have nice things :)

What version of Python is this? I can repeat your error on 3.5.2:
$ python3 -V
Python 3.5.2
$ LC_ALL=C sacrebleu --help
Traceback (most recent call last):
  File "/usr/local/bin/sacrebleu", line 11, in <module>
    load_entry_point('sacrebleu==1.0.3', 'console_scripts', 'sacrebleu')()
  File "/usr/local/lib/python3.5/dist-packages/sacrebleu.py", line 762, in main
    args = arg_parser.parse_args()
  File "/usr/lib/python3.5/argparse.py", line 1735, in parse_args
    args, argv = self.parse_known_args(args, namespace)
  File "/usr/lib/python3.5/argparse.py", line 1767, in parse_known_args
    namespace, args = self._parse_known_args(args, namespace)
  File "/usr/lib/python3.5/argparse.py", line 1973, in _parse_known_args
    start_index = consume_optional(start_index)
  File "/usr/lib/python3.5/argparse.py", line 1913, in consume_optional
    take_action(action, args, option_string)
  File "/usr/lib/python3.5/argparse.py", line 1841, in take_action
    action(self, namespace, argument_values, option_string)
  File "/usr/lib/python3.5/argparse.py", line 1025, in __call__
    parser.print_help()
  File "/usr/lib/python3.5/argparse.py", line 2367, in print_help
    self._print_message(self.format_help(), file)
  File "/usr/lib/python3.5/argparse.py", line 2373, in _print_message
    file.write(message)
UnicodeEncodeError: 'ascii' codec can't encode character '\xe9' in position 454: ordinal not in range(128)

But it works in 3.6:
$ python3 -V
3.6.2
$ LC_ALL=C ./sacrebleu.py
sacr\xe9BLEU: I need either -t (test set) or a list of references
sacr\xe9BLEU: The available test sets are:
sacr\xe9BLEU:   wmt17/improved: Improved zh-en and en-zh translations.
sacr\xe9BLEU:   wmt17/B: Additional reference for EN-FI and FI-EN.
sacr\xe9BLEU:   wmt17: Official evaluation data.
sacr\xe9BLEU:   wmt16/B: Additional reference for EN-FI.
sacr\xe9BLEU:   wmt16: Official evaluation data.
sacr\xe9BLEU:   wmt15: Official evaluation data.
sacr\xe9BLEU:   wmt14/full: Evaluation data released after official evaluation for further research.
sacr\xe9BLEU:   wmt14: Official evaluation data.
sacr\xe9BLEU:   wmt13: Official evaluation data.
sacr\xe9BLEU:   wmt12: Official evaluation data.
sacr\xe9BLEU:   wmt11: Official evaluation data.
sacr\xe9BLEU:   wmt10: Official evaluation data.
sacr\xe9BLEU:   wmt09: Official evaluation data.
sacr\xe9BLEU:   wmt08/nc: Official evaluation data (news commentary).
sacr\xe9BLEU:   wmt08/europarl: Official evaluation data (Europarl).
sacr\xe9BLEU:   wmt08: Official evaluation data.

But I guess I should just remove that access mark anyway.

ubuntu@ip-172-31-65-80:~$ python3 -V
Python 3.5.2
ubuntu@ip-172-31-65-80:~$ python -V
Python 2.7.12

Oh, true.

I think (in short), LC_ALL=C.UTF-8 should be preferred instead of plain C with Python 3.x. Some more details here: http://click.pocoo.org/5/python3/#python-3-surrogate-handling

In other words, python3 is buggy?

I'm not an expert but as far as I understood, Python 3.7 will detect the underlying locale and warn (and even modify it to C.UTF-8) if its ascii C. Why do you want to work in an environment with C locale btw?

I don't really have a good reason. However, in my whole pipeline of tools it's only sacrebleu that needs to be somehow pacified by changing my environment.  That seems wrong, doesn't it?

I'll look into this more in hopes of solving it.

Can you try removing the é from the ArgumentParser() call and see if that fixes it for you?
When I do that, these work:
LC_ALL=C python3 ./sacrebleu.py
LC_ALL=C python3 ./sacrebleu.py --help

However, it seems to interfere more broadly. For example, I can't save the reference to STDOUT:
LC_ALL=C python3 ./sacrebleu.py -t wmt17 -l en-de --echo ref
# -> fails

Furthermore, if I score the reference with LC_ALL=C, there are problems. Normal scoring:
$ ./sacrebleu.py -t wmt17 -l en-de --echo ref > wmt17.de
$ cat wmt17.de | ./sacrebleu.py -t wmt17 -l en-de
BLEU+case.mixed+lang.en-de+numrefs.1+smooth.exp+test.wmt17+tok.13a+version.1.1.6 = 100.00 100.0/100.0/100.0/100.0 (BP = 1.000 ratio = 1.000 hyp_len = 61287 ref_len = 61287)

As expected. However if I set LC_ALL=C, I can still score (since there is no writing of unicode text to STDOUT), but the numbers are wrong:
$ cat wmt17.de | LC_ALL=C ./sacrebleu.py -t wmt17 -l en-de
BLEU+case.mixed+lang.en-de+numrefs.1+smooth.exp+test.wmt17+tok.13a+version.1.1.6 = 80.68 92.0/84.1/77.2/71.0 (BP = 1.000 ratio = 1.000 hyp_len = 61287 ref_len = 61287)

This is because tokenization works differently in a different locale.
So I think the answer is that you need to set your locale correctly, and furthermore, you might be creating problems for yourself in other areas if other tools (like tokenizers) are also sensitive to the locale.

For reference. I am actually using LC_ALL=C.UTF-8 which should not have any of the issues above. Removing the accent seems to have fixed all other problems.

Great, glad to hear it. I have also increased my prior on the advice of UN bureaucrats.

Hi, this just cost me an afternoon. For other tools, I need LC_ALL=C. After I set it globally for this purpose, sacreBLEU started to produce lower numbers, without me noticing at first. The reason I need "C" is that this is the only one that does not seem to have unpredictable equivalence classes of characters, which is a problem when e.g. creating vocabularies with tr ' ' '\n' | sort -u.
Since I am using a different shell (fish) which does not have the LC_ALL= prefix, I will have to switch the global setting of this variable, depending on which command I run, which is very error-prone. Presently, I must run it indirectly via bash:
  cat FILE \
    | bash -c 'LC_ALL= ; ~/f:/data2/fseide/marian-examples/tools/sacreBLEU/sacrebleu.py '"$SACREBLEU_OPTS"

I think it would be very desirable if the tool was locale-independent, to prevent other people from falling into this trap.
Thanks!

Oh, man, sorry this cost you so much time. Yes, LC_ALL=C is important for some tools (also for UNIX sort in certain cases). But what version of sacrebleu are you running (sacrebleu -V)? This should have been fixed in 1.2.3.

Hello,
If the locale is C, sacrebleu can not be installed too:
[lst2] ~ $ LC_ALL=C pip install --no-clean sacrebleu
Collecting sacrebleu
  Using cached sacrebleu-1.2.3.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-build-93bt_10t/sacrebleu/setup.py", line 40, in <module>
        version = get_version(),
      File "/tmp/pip-build-93bt_10t/sacrebleu/setup.py", line 31, in get_version
        init = open(os.path.join(os.path.dirname(__file__), 'sacrebleu.py')).read()
      File "/lium/buster1/caglayan/anaconda3/lib/python3.6/encodings/ascii.py", line 26, in decode
        return codecs.ascii_decode(input, self.errors)[0]
    UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 6525: ordinal not in range(128)

I repeat my claim that locale dependency if no locale-specific tasks are performed is a bug by itself.

-i <file> is broken. You need to explicitly pass  encoding=args.encoding in line 1368 otherwise it gets used as mode in smart_open().

Upgrade to 1.2.5 — I fixed that right away.

I'm closing this now, because I think the issue is resolved. Please reopen if it occurs again!


fix(time-picker): prevent event from propagating in onClear

Types of changes

[ ] New feature
[x] Bug fix
[ ] Enhancement
[ ] Component style change
[ ] Typescript definition change
[ ] Documentation change
[ ] Coding style change
[ ] Refactoring
[ ] Test cases
[ ] Continuous integration
[ ] Breaking change
[ ] Others

Background and context
日期选择器中没打开面板时 点清除不会弹出面板。而时间选择器点击清除图标时就触发了打开面板。
官网示例文档就可以复现。
Solution
考虑到真实使用场景习惯，在单时间选择时清除内容就关闭面板与日期选择器交互相同。在时间区间选择时清除内容不关闭弹窗。
Changelog

Component
Changelog(CN)
Changelog(EN)
Related issues

time-picker
修复清除事件冒泡行为
Fix the bubbling behavior of the clear event.
#2230

Checklist:

[ ] Test suite passes (npm run test)
[ ] Provide changelog for relevant changes (e.g. bug fixes and new features) if applicable.
[ ] Changes are submitted to the appropriate branch (e.g. features should be submitted to feature branch and others
should be submitted to main branch)

Other information

@LIjiAngChen8 确实是，这里点击清除按钮不应该展开面板


Atom.Object.defineProperty.get is deprecated.

atom.workspaceView is no longer available.
In most cases you will not need the view. See the Workspace docs for
alternatives: https://atom.io/docs/api/latest/Workspace.
If you do need the view, please use atom.views.getView(atom.workspace),
which returns an HTMLElement.
Atom.Object.defineProperty.get (/Applications/Atom.app/Contents/Resources/app/src/atom.js:53:11)
createCommand (/Users/lichengwu/.atom/packages/set-syntax/lib/main.coffee:16:9)

Are you using v0.2.0 of set-syntax? The latest version doesn't call atom.workspaceView.

I can't reproduce this. Let me know if you're on v0.2.0 and you can still reproduce it. Thanks!


Fails to build from source on Debian unstable (amd64)

gophernicus currently fails to build from source on Debian stable:
cc -Wl,-z,relro -Wl,-z,now  gophernicus.o file.o menu.o string.o platform.o session.o options.o -lwrap -o gophernicus
/usr/bin/ld: file.o:/usr/include/tcpd.h:115: multiple definition of `deny_severity'; gophernicus.o:/usr/include/tcpd.h:115: first defined here
/usr/bin/ld: file.o:/usr/include/tcpd.h:114: multiple definition of `allow_severity'; gophernicus.o:/usr/include/tcpd.h:114: first defined here
/usr/bin/ld: menu.o:/usr/include/tcpd.h:115: multiple definition of `deny_severity'; gophernicus.o:/usr/include/tcpd.h:115: first defined here
/usr/bin/ld: menu.o:/usr/include/tcpd.h:114: multiple definition of `allow_severity'; gophernicus.o:/usr/include/tcpd.h:114: first defined here
/usr/bin/ld: string.o:/usr/include/tcpd.h:115: multiple definition of `deny_severity'; gophernicus.o:/usr/include/tcpd.h:115: first defined here
/usr/bin/ld: string.o:/usr/include/tcpd.h:114: multiple definition of `allow_severity'; gophernicus.o:/usr/include/tcpd.h:114: first defined here
/usr/bin/ld: platform.o:/usr/include/tcpd.h:115: multiple definition of `deny_severity'; gophernicus.o:/usr/include/tcpd.h:115: first defined here
/usr/bin/ld: platform.o:/usr/include/tcpd.h:114: multiple definition of `allow_severity'; gophernicus.o:/usr/include/tcpd.h:114: first defined here
/usr/bin/ld: session.o:/usr/include/tcpd.h:115: multiple definition of `deny_severity'; gophernicus.o:/usr/include/tcpd.h:115: first defined here
/usr/bin/ld: session.o:/usr/include/tcpd.h:114: multiple definition of `allow_severity'; gophernicus.o:/usr/include/tcpd.h:114: first defined here
/usr/bin/ld: options.o:/usr/include/tcpd.h:115: multiple definition of `deny_severity'; gophernicus.o:/usr/include/tcpd.h:115: first defined here
/usr/bin/ld: options.o:/usr/include/tcpd.h:114: multiple definition of `allow_severity'; gophernicus.o:/usr/include/tcpd.h:114: first defined here
collect2: error: ld returned 1 exit status

This is Debian bug #966853. The full build log is available from: http://qa-logs.debian.net/2020/08/02/gophernicus_3.0.1-1_unstable.log

I see it failed yesterday as well: http://qa-logs.debian.net/2020/08/03/gophernicus_3.0.1-1_unstable.log
Couple questions:

What commit was built? Is it upstream master or salsa's debian/sid? Something else?
I can't reproduce locally (Ubuntu 20.04), with either of the mentioned commits. I have an idea for a fix but I can't test if it works.
Is there a way to test changes manually with Debian's QA?
Would you like to upstream the changes you made in gophernicus's Debian packaging scripts?

I think the better option is to remove the Debian packaging scripts from the repo entirely.
This is the route most other packages follow, the Debian packaging scripts were only kept as an option for people to build their own packages. If they still want to do that they should do it the official Debian way. I think I will remove the scripts with 3.1.

The Debian package builds the 3.0.1 release (your v3.0.1 tag). It (plus Debian-specific packaging changes) can be found on debian/sid branch on salsa.
If you want to test locally on Ubuntu, you should be able to use the "schroot" tool to create a Debian unstable chroot on Ubuntu without too much trouble. Alternatively, you're welcome to send me the patch and I can test it for you.
And fosslinux is right, the best option is to remove the Debian packaging scripts from the repo entirely.

This bug is already fixed as of the current commit, very recently. The patch is rather large, however, and I plan to release 3.1 soon.
I am unfamiliar with Debian's building process. If it needs to be built sooner rather than later I can release a hotfix 3.0.2.

Thanks, and sorry: I should have done the legwork of checking if it had been fixed in Git.
There is no particular rush. The archive software will automatically remove the package from the "testing" distribution (which becomes the "stable" distribution), probably in a month or so. That said, the stable freeze isn't scheduled to happen until early 2021, so we have time yet to get a fix uploaded if we're to get the package included in the next stable release.

As a heads up, Debian will enter a freeze on January 12, 2021. That means that for gophernicus to be included in the next Debian release, I need to upload it a week or more before that.

Thanks for the notice. I will have a release by mid-december.


Make the window border actually follow the user's theme

Summary of the Pull Request
One of our great contributors already hooked up all the logic for this,
we just needed a theme library that could handle the request.
PR Checklist

[x] Fixes #4980
[x] CLA signed
[x] Tests added/passed
[ ] Requires documentation to be updated

Most of the diffs here are updating the nuget package :smile:

@msftbot merge this in 5 minutes

Does this make the border follow the System theme, or the app settings JSON "RequestedTheme"

The application's currently-active theme.

The border currently follows the system theme.

Thank you @DHowett-MSFT


Balder/1 queue per thread

@vekterli Here is a stab at striping the priority Q.
There is one outstanding issue with the average time in Q metric. It needs to be per stripe or thread.
It is the 4th commit that constains the important stuff. It is not a small diff, but the file is rather complex too.
Perhaps we should discuss the overall structure before you start reviewing.

Closing as it is superceeded by #5526


Fix event server mongo uri

collection name in uri creates a bad database name error
uri was not composed correctly

Should go to master branch

Should go to master branch

Its needed in develop though as well.

Its needed in develop though as well.

Yes, but master is at first place, it should be hotfix because it's production breaking bug. These bugs should always be in master first (and with @mkolar git app it's automatically merged to develop too if branch name starts with hotfix/***)


itzg/minecraft-bedrock-server does not work with Orbstack like it does with Docker Desktop

Describe the bug
Unsure why - Everything looks like it should behave properly and when I start the container in Orbstack, the logs don't show any errors. It may be some network issue as I am trying to expose 19132:19132/udp in the docker compose? If I run the container in docker desktop, there are no issues - I can ping the IP and Port, I can connect to it on Minecraft on my iPad, Homeassistant can see the server.
When I start the exact same image/container with Orbstack, I cannot connect to anything, Homeassistant cannot see the server.
To Reproduce
Use the default docker compose file as seen on https://github.com/itzg/docker-minecraft-bedrock-server, pull the image, start the container, try and ping from a machine on your local network or try and join the server on a version of Minecraft
Expected behavior
No response
Diagnostic report (REQUIRED)
OrbStack info:
Version: 1.4.3
Commit: 75d38a2c2d9a2b42d64378a8f50f31d4d566df10 (v1.4.3)
System info:
macOS: 14.4 (23E214)
CPU: arm64, 8 cores
CPU model: Apple M2
Model: Mac14,3
Memory: 16 GiB
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2024-03-18T19-31-50.956129Z.zip

Screenshots and additional context (optional)
No response

Can't reproduce. If you just switched from Docker Desktop, reboot your Mac to make sure it didn't leave behind any background services that are taking ports.

Oh interesting, you have been able to connect to the server...! I had rebooted a couple of times since installing Orbstack and I make sure Docker Desktop doesn't open at login anymore. I even tried making a new world in case it was that. I will try and reboot again in a moment


[SPARK-17960][PySpark] [Upgrade to Py4J 0.10.4]

What changes were proposed in this pull request?

Upgrade the Py4J version on the Java side
Update the py4j src zip file we bundle with Spark

How was this patch tested?
Existing doctests & unit tests pass

Test build #67075 has started for PR 15514 at commit 70fa455.

Test build #67075 has finished for PR 15514 at commit 70fa455.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67075/
Test FAILed.

Test build #3356 has started for PR 15514 at commit 70fa455.

Test build #3356 has finished for PR 15514 at commit 70fa455.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Awesome, thanks for taking this on @jagadeesanas2, this looks pretty reasonable although it might be helpful if we mentioned briefly the PR description what the Py4J changes were in this release since that is what ends up as the commit description once its merged. But the change its self looks good to me - cc @srowen / @davies for the final review.

cc @JoshRosen

I'm OK with it. For the record, was there any fix here that impacts Spark? updating just to keep updated isn't a bad idea but wouldn't want to update through every version of everything. Maybe at least once per minor release it's worth review.

Merged to master


Add arner to GitHub fabric-token-sdk and fabric-smart-client

Please include:

GitHub ID to add: arner
Lab to be added to: fabric-token-sdk and fabric-smart-client
Role: Manage

Invites sent!


Add "bright black" and use "gray" as alias

For consistency, it would be good to have a chalk.blackBright for use.
Similarly, it'd be nice if there was a "background" color alias for gray: chalk.bgGray.

Would otherwise close since this belongs over at ansi-styles but this also requires the "English" fix for bgGrey. That alias happens in chalk proper, so this issue will serve as that to-do.

@Qix- is anything that needs to be done?

Just need to update the version of ansi-styles we use, which is something we'll do (see #300)

This is fixed in master and will be available in Chalk 3.


Prevent crash with /proc path canonicalization

Issue
Attempting to trace an executable (with either namespace relative, or /proc rooted path) that is in a different mount namespace than the one bpftrace is running in fails.
# bpftrace -e 'usdt:/proc/92493/root/home/usdt_test:tracetest:testprobe { printf("hit\n")}' -p 92493
ERROR: failed to write elf: filesystem error: cannot canonicalize: No such file or directory [/proc/92493/root/home/usdt_test] [/bcc-build/bpftrace/build]

# bpftrace -e 'usdt:/home/usdt_test:tracetest:testprobe { printf("hit\n")}' -p 92493
ERROR: failed to write elf: filesystem error: cannot canonicalize: No such file or directory [/proc/92493/root/home/usdt_test] [/bcc-build/bpftrace/build]

Cause
The reason is attempting to perform filesystem::canonical('/proc/<pid>/root/usr/bin/..') to a proc path of a pid that is in a different mount namespace fails with No such file or directory. (it looks like canonical() does an lstat on the current root instead and doesn't find the file there)
Call stack
The call originates from abs_path, and this is the call stack before it blows up:
* thread #1, name = 'bpftrace', stop reason = breakpoint 1.1
  * frame #0: 0x000055555565dd52 bpftrace`bpftrace::abs_path(rel_path="p~\xb9UUU"...) at utils.cpp:927
    frame #1: 0x00005555555c2ed6 bpftrace`_ZNK8bpftrace8BPFtrace21find_wildcard_matchesB5cxx11ERKNS_3ast11AttachPointE(this=0x00007fffffffe120, attach_point=0x0000555555b80bf0) at bpftrace.cpp:406
    frame #2: 0x000055555569250e bpftrace`bpftrace::ast::CodegenLLVM::visit(this=0x00007fffffffdd60, probe=0x0000555555b11fb0) at codegen_llvm.cpp:2139
    frame #3: 0x0000555555676ff8 bpftrace`bpftrace::ast::Probe::accept(this=0x0000555555b11fb0, v=0x00007fffffffdd60) at ast.cpp:41
    frame #4: 0x00005555556987a5 bpftrace`bpftrace::ast::CodegenLLVM::accept(this=0x00007fffffffdd60, node=0x0000555555b11fb0) at codegen_llvm.cpp:2819
    frame #5: 0x0000555555692e52 bpftrace`bpftrace::ast::CodegenLLVM::visit(this=0x00007fffffffdd60, program=0x00007fffe4015fd0) at codegen_llvm.cpp:2228
    frame #6: 0x000055555567702c bpftrace`bpftrace::ast::Program::accept(this=0x00007fffe4015fd0, v=0x00007fffffffdd60) at ast.cpp:42
    frame #7: 0x00005555556987a5 bpftrace`bpftrace::ast::CodegenLLVM::accept(this=0x00007fffffffdd60, node=0x00007fffe4015fd0) at codegen_llvm.cpp:2819
    frame #8: 0x000055555569808b bpftrace`bpftrace::ast::CodegenLLVM::generate_ir(this=0x00007fffffffdd60) at codegen_llvm.cpp:2723
    frame #9: 0x0000555555668fc8 bpftrace`main(argc=5, argv=0x00007fffffffe688) at main.cpp:787
    frame #10: 0x00007fffed11dbf7 libc.so.6`__libc_start_main(main=(bpftrace`main at main.cpp:272), argc=5, argv=0x00007fffffffe688, init=<unavailable>, fini=<unavailable>, rtld_fini=<unavailable>, stack_end=0x00007fffffffe678) at libc-start.c:310
    frame #11: 0x0000555555579aaa bpftrace`_start + 42

Fix
The fix is to give up trying to canonicalize /proc based baths. That of course means something like tracing /proc/92493/root/home/../home/usdt_test will not work (it doesn't event work now anyway), but I don't see a strong use case for trying to support canonicalization of /proc based paths.
Checklist

[x] User-visible and non-trivial changes updated in CHANGELOG.md
[x] The new behaviour is covered by tests

LGTM

Thanks for the fix!


Update local instructions

This attempts to improve the instructions to launch Kubernetes on a local machine.
I'm sure this can be improved and hopefully not expose the installation to a public IP of the machine but at the moment I don't know how to do that so help would be appreciated.
If I've missed something from the bootstrapping process, please let me know, things appear to work on my machine so far.
This has the advantage it can easily be copy-pasted into a bash script and have it up and running for the user quite easily.

In general PR looks good, but I'd like to update the PR a bit (see comments).

@idvoretskyi thank you for the feedback. I'd also like to get more feedback around how the k8s configuration is done and possibly remove the need to to point it to the external IP of the machine and use an internal (or maybe something like use flannel to make these to work.

@dlsniper Why do you want to add Flannel to the local setup? That's mainly for lightweight testing.
If you'd like a more realistic single-node cluster configuration, I suggest https://github.com/kubernetes/minikube
cc @mikedanese @dlorenc

@bgrant0607 I don't want it necessarily. As it happens, this was my first time trying to use K8s on a local machine and the docs exploded in my face as there's no way to make it work directly. Sure, the docker version works but either remove this and leave docker only or update this.

A reminder for myself, I'll need to change this to be more secure / not expose the API server to the world and use the config to set the insecure-skip-tls-verify.

@pwittrock @johndmulhausen
I would like docs/getting-started-guides/locally.md moved to kubernetes/kubernetes/docs/dev/local-up-cluster.md

@dlsniper I agree with @bgrant0607 here. This doc needs to be moved to the main Kubernetes repo because it's really a workflow for development. If you're up forward maybe you can submit a PR there that move this over?
Also I think we should just point people at minikube for running a simple local cluster. I'm closing this PR out and creating a new issue regarding the need to move this.

@kelseyhightower @bgrant0607 move or duplicate? I suppose, it has to be at the documentation repo as well.

@idvoretskyi I think for local setup we should link to minikube from here. This content was designed for locally development so lets move it back to the main repo and keep it focused. For example you don't really want flannel for local dev of core features.


Attribute based eval

https://arxiv.org/abs/2209.06103

Rationale: introduce a "true" zero-shot eval into the benchmark, based on attribute-based zero-shot task.
The task is harder, as in contrast to standard zero-shot transfer used currently for CLIP eval, it requires to deal with new classes which were never presented during pre-training by describing any entity to be recognized by a set of attributes (eg sandy yellowish, furry, four legged, fast, strong) instead of using a class label (eg lion). For more details, see https://arxiv.org/abs/2209.06103

That would be great, is the code available somewhere ? @hildekuehne

Will check and get back soon.


Log tests split to separate methods + all log fields checking

Also log checking removed from slash tests as it's sideway to check logs there.
Though slash log checking included in test_logs.py

Looks good. There is a merge conflict with some recent variable name changes. Would you mind cleaning it up?

@djrtwo done!


Issue running preprocess.lua

Hi, I got the following error when executing preprocess.lua. I already included -save_data <prefix> in my command.
preprocess.lua: invalid dependency for option -save_data: option `-save_data` is required
Try 'preprocess.lua -h' for more information, or visit the online documentation at http://opennmt.net/OpenNMT/.

I'm guessing is it related to the recently added -dry_run feature?

Thanks for reporting. It is fixed.


Problems defining variables with const/let in :on attributes

Describe problem. 🚨
When you try to set events to HTML elements, many times we find ourselves in the need to define variables to store certain information. Here is an example.
<main>
  <button :onclick="() => {
    const username = 'thebug'
    console.log(username)
  }">Click me!</button>
</main>

The problem that happens when doing is that our function will never be executed. And this happens when we use const/let
Why it happens? 🤔
Sprea has a function that is responsible for parsing expressions. That function is called parseExpr.
What happens with this function is that it evaluates when a directive is prefixed with :on, and what it does is wrap our function in a self-executing function.
Below is the source code. (Take a look at line 426)
https://github.com/dy/sprae/blob/82e2b20df496eb3a959bf4db1d08fae091fc0338/src/directives.js#L421-L427
The problem with these is that we can't use const or let to declare variables in the expression evaluated in the parseExpr function. This is because the expression is compiled into an anonymous function that is executed at runtime and does not have a block of code in which a block-scoped variable such as const or let can be declared.
Solution. 💡
We have several alternatives to solve this problem, they are shown below.
First option
Declare our values in a global variable.
<main>
  <button :onclick="() => {
    window.username = 'thebug'
    console.log(window.username)
  }">Click me!</button>
</main>

Note: that this can cause a conflict when setting new properties to the global object.

Second option
It is to store the values by referencing the element.
<main>
  <button :onclick="() => {
    this.username = 'thebug'
    console.log(this.username)
  }">Click me!</button>
</main>

Note: that this may conflict with the element's reserved attributes.

Third option
Declare variables using var
<main>
  <button :onclick="() => {
    var username = 'thebug'
    console.log(username)
  }">Click me!</button>
</main>

Conclusion. 💪🏻
In conclusion, the parseExpr function performs a check to avoid errors during the evaluation of the expression, and therefore you should declare the variable in the global scope using the window, this, or var object instead of using const/let. It is important to consider the scope implications of each type of variable declaration to avoid errors and ensure that variables are available where they are needed.

Oh, thanks for the catch! Will fix promptly

Fixed in 2.14.2.

Thanks bro, you're amazing. 👌


raidboss: default css - infoText color to white

Fixes #1352

Let's do it.  The time for comments has passed.


Example

Can you upload online example?

Hi, the best example of the serializer in use is in rich-markdown-editor, deserialize:
https://github.com/outline/rich-markdown-editor/blob/master/src/index.js#L83
serialize:
https://github.com/outline/rich-markdown-editor/blob/master/src/index.js#L113
For additional context you might look at the serializers written by the core team:
https://docs.slatejs.org/general/plugins#serializers

@tommoor merci beaucoup


New apple-touch-icon.png and logo images.

@alanshaw: how can I run node index.js locally without having to add a personal token?
This is currently untested due to the above.

Bump.


DR-> Issues on Home screen (0.1)

Scenario:

Navigate to the DR on TEST environment: https://test-data.bcparks.ca/admin/
Login as an Admin user and navigate to the Home page.
Check the UI of the page and make sure the page matches to the design mockups.

Expected:

The page should resemble the screen given below.

Issues:

The vertical lines separating the left navigation items are missing.
Inocrrect background color used in the left navigation panel.
The space between the breadcrumb "Home" and the navigation toggle open/close option.
Incorrect page heading displayed instead of "Park Name Register".
Incorrect font color has been used for the page heading.
Missing the prefix "Hello" along with the login user's name.
Incorrect colors used on the navigation card heading background and button background.
Incorrect alignment of the navigation cards on the Home page.
The height of the footer is incorrect when compared to the design mockups.
Spacing between the footer links looks incorrect.

Refer to the image given below.

Thanks for tracking these @manuji! We discussed at standup this morning that these updates should probably be part of the larger design debt surrounding the design library for admin so will likely be covered there.

@Dianadec - it looks like everything has been incorporated from this ticket. One outstanding is the "Incorrect page heading displayed instead of "Park Name Register" - but thinking that what is actually displayed makes more sense (parks Data Register Admin System). I'm thinking we can close this one.

agreed looks good to close. @LindsayMacfarlane


Feature/#31 修正など

Codecov Report

Merging #34 into develop will increase coverage by 0.06%.
The diff coverage is 92.85%.

@@             Coverage Diff             @@
##           develop      #34      +/-   ##
===========================================
+ Coverage    94.49%   94.56%   +0.06%
===========================================
  Files           27       27
  Lines          781      791      +10
===========================================
+ Hits           738      748      +10
  Misses          43       43

Impacted Files
Coverage Δ

kabutobashi/io/__init__.py
96.87% <85.71%> (-3.13%)
:arrow_down:

kabutobashi/attributes/page_content.py
88.23% <100.00%> (+1.56%)
:arrow_up:

...hi/crawler/stock_crawler/weeks_52_high_low_page.py
100.00% <0.00%> (+1.75%)
:arrow_up:

Continue to review full report at Codecov.

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


SQS Finder : Queue Url unset.

When using the SQS queue finder, the queue-url is unset. This field is necessary for the sqs resource to find the correct region to use and any attempt to change a queue found with the finder results in an error about being unable to find the queue.
$(external-query aws::sqs-queue { name: 'queue-name'}).0 outputs an arn but does not output a queue-url.
{
  "external" : true,
  "parent" : null,
  "name" : null,
  "scope" : { },
  "change" : null,
  "configuredFields" : null,
  "modifiedIn" : null,
  "modifications" : [ ],
  "arn" : "<ARN IS HERE>",
  "queueUrl" : null,
  "visibilityTimeout" : 31,
  "messageRetentionPeriod" : 345600,
  "delaySeconds" : 0,
  "maximumMessageSize" : 262144,
  "receiveMessageWaitTimeSeconds" : 0,
  "deadLetterQueueName" : null,
  "deadLetterTargetArn" : null,
  "maxReceiveCount" : null,
  "contentBasedDeduplication" : null,
  "kmsMasterKeyId" : null,
  "kmsDataKeyReusePeriodSeconds" : null,
  "policy" : "<POLICY IS HERE>"
}

Works for me.


Failed to get new registration token

Hi ,
I am getting error while deploying the new runner.
the action controller gives the below error :
│ 2021-02-18T05:46:03.475Z    ERROR    controller-runtime.controller    Reconciler error    {"controller": "runner", "request": "default/example-runner", "er │
│ github.com/go-logr/zapr.(*zapLogger).Error

2021-02-18T05:46:19.028Z    DEBUG    controller-runtime.manager.events    Warning    {"object": {"kind":"Runner","namespace":"default","name":"example-runn │
│ 2021-02-18T05:46:39.594Z    ERROR    controllers.Runner    Failed to get new registration token    {"runner": "example-runner", "error": "failed to create  │
│ github.com/go-logr/zapr.(*zapLogger).Error

I am simply trying to register a runner to a repository.

@sandeepraj-chandrakant-bhandari-db Hey! This can happen in many ways - the lack of permissions on the github app or personal access token, if it's token and you're using organisational runners the token needs to be created by a github account that has admin priv to the org, etc.
Can you give me brief overview of your setup?

@mumoshu hey.. thank you for the response. I found the issue was because I was passing api url  in enterprise URL while setting the environment.
It is now fixed and runners were registered.


verilog: error on macro invocations with missing argument lists

This would previously complain about an undefined internal macro if the unapplied macro had not already been used. If it had, it would incorrectly use the arguments from the previous invocation.
@rswarbrick

Oops, that definitely isn't what I intended it to do! What's the error message like for something like this?
`define foo(a=1) (a)

`foo

Looking at the patch quickly, it looks like you'll spit out something like Expected to find '(' to begin macro arguments for 'foo', but instead found ''. Maybe special-case the error message for end-of-line?

I've updated the error to special-case tokens which are control characters.

Thanks!


Angular-cli last version: Cannot read property 'text' of undefined

ng serve --aot command in last version of angular-cli (@angular/cli: 1.0.0-beta.32.3):
ERROR in ./~/ng2-datepicker/ng2-datepicker.ts
Module build failed: TypeError: Cannot read property 'text' of undefined

I am also getting this error, when try, ng build --aot --prod --env=prod.
I gone through your readme file. But I can't get you regarding AoT, sorry.
Can you give some more detailed instructions for AoT support?
FYI, I use
angular-cli: 1.0.0-beta.26
node: 7.5.0
os: darwin x64
@angular/common: 2.4.8
@angular/compiler: 2.4.8
@angular/core: 2.4.8

I'm also getting this issue whenever I try ng build --prod, along with:
ERROR in ./~/ng2-slimscroll/index.ts Module build failed: TypeError: Cannot read property 'text' of undefined

I am not really sure what is going on here. Will investigate when have more time.

what is the status on this?

I did a fix by re-scaffolding the app with the CLI and using a tool to build angular 2+ libraries
https://github.com/jkuri/ng2-datepicker/pull/199
If you guys need to have this running I published a built version that works with AOT
npm install --save ng2-datepicker-aot


Generating github links without git

Is there a way to generate links to Github without having the repository? Say I download a zip file of the project and try to generate the documentation. We know the github url from the package.json
  "repository": {
    "type": "git",
    "url": "git://github.com/TypeStrong/TypeDoc.git"
  },

The generated docs may not be in sync since the code will not know what branch its supposed to look at. We could by default just make it point to master. Docs and code may be out of sync but that's a risk we are willing to take. To avoid this we could add another field to package.json specifying the branch name or commit to point it to or maybe an option in the command line.
Our internal doc generation involves using docker and we no longer have the repo when we make the docs and so all the links pointing to Github are not generated.

Related to (but different from) #129

@aciccarello indeed, the other issue would solve this. Thanks.

i had the same issue and created a plugin typedoc-plugin-sourcefile-url
the plugin allows to create custom URLs to source code files.
it can be simply installed with:
npm install --save-dev typedoc-plugin-sourcefile-url


Update Catalog on stores

Update Catalog on stores
iOS

[x] Prepare build on the App Store
[ ] Change version number to 1.3 build 6
[ ] remove from www/common/index.html li item leading to Ajax page
[ ] remove from www/common/plugins.html li item leading to Location Plugin page
[ ] remove from www/common/plugins.html li item leading to Webservice Plugin page
[ ] Fix project to solde submitting issues in first comment below
[ ] Link uploaded file to the 1.3 release and submit

Android

[ ] Change version number to 1.3 build 6
[ ] remove from www/common/index.html li item leading to Ajax page
[ ] remove from www/common/plugins.html li item leading to Location Plugin page
[ ] remove from www/common/plugins.html li item leading to Webservice Plugin page
[ ] Fix project to solde submitting issues in first comment below
[ ] Publish last Catalog version to the Google Play


about command create-react-app and react-scripts

Hello guys, I just got confused that when I heard about create-react-app, and check this library, it's so cool. but when I check Redux example todos, I found from v3.6.0, it start to use react-script to handle some dev lifecycle.
Honestly I don't know the react-scripts that time, I checked finally I realized that it also comes from create-react-app library,
Why mix these two function into one? any plan to split those functions??
sorry guys if you feel this issue is unneeded, please throw it.

Please see the first item in the Usage Guide. I believe it explains the reasons for package split:
https://github.com/facebookincubator/create-react-app/blob/master/template/README.md#updating-to-new-releases

@gaearon thanks, maybe I think I knew the create-react-app firstly, so I just thought this project purpose was only generating some react basic project template, and now I think according by the react-scripts part, it helps us a lot stuff in development stage after I checked v3.6.0 version.


FLUID-6288 Add Dockerfile

This is necessary so a Docker image can be created and used to serve the website.
To test:
$ docker build -t infusion-docs .
$ docker run --rm -ti -p 8000:80 infusion-docs
$ open http://localhost:8000

This PR was submitted and closed before because it couldn't build. This is a new PR with the fix/workaround necessary to make DocPad work inside a Docker container.

CC @jobara @waharnum @cindyli @amb26 could you help review this PR? Thanks!

merged at 369bf01b66126024d94f781255d369ad45aec34c


CLOUD: Add Header & Footer

Need to add header & footer. Will work with Kristine directly on this. Fits in with other issue on getting four new pages live.

HEADER

Logo (Home)
Learn >>> https://new.threefold.io/info/cloud#/
Build >>> https://vdc.testnet.grid.tf/vdc/#/
Forum >>> https://forum.threefold.io

FOOTER
Learn

Knowledge Base >>> https://new.threefold.io/info/cloud#/cloud__evdc_marketplace
About ThreeFold >>> https://threefold.io
ThreeFold Marketplace >>> https://new.threefold.io/marketplace
ThreeFold Token >>> https://farming.threefold.io/token

Participate

Get Started >>> https://new.threefold.io/info/cloud#/cloud__evdc_getting_started
Pricing >>> https://new.threefold.io/info/cloud#/cloud__evdc_pricing
How to Get TFT >>> https://new.threefold.io/info/threefold#/threefold__how_to_buy_and_sell
Wallets >>> https://new.threefold.io/info/threefold#/threefold__storing_tft

Community

Join our Forum >>> https://forum.threefold.io
Stay Updated >>> https://t.me/threefoldnews
Contact >>><EMAIL_ADDRESS>
Legal

Terms & Conditions >>> https://new.threefold.io/info/threefold#/legal__terms_conditions_websites
Privacy Policy >>> https://new.threefold.io/info/threefold#/legal__privacypolicy
Impressum >>> N/A (needs to be created)

I don't see a footer on local for cloud


Increase --max-line-length in travis.yml

I'm submitting a ...

[x] bug report
[ ] feature request
Apologies, earlier changed the --max-line-length for HoundCI and not for Travis CI. This issue is in regards of same in Travis.

Current behavior:

Currently, --max-line-length = 85 in .travis.yml is responsible for build failing at #240
Expected behavior:

Changing --max-line-length = 85 to --max-line-length = 150 in .travis.yml will pass the build and in future too.
Steps to reproduce:
Yes, I would like to work on this issue

Shouldn't max line length be set to 79 as per PEP standards?


Ping notification when it is someones' turn

Would it at all be possible for this bot to send an @ message to a player when it is their turn via discord. I know the website has push notifications however, it can still be difficult when newer players forget to check if it is their turn. A simple @ message from the bot would be very helpful.
Thanks.

This is a good idea, but will require the bot to poll table statuses unless there's some way to receive updates from BGA itself.

This is a good idea, but will require the bot to poll table statuses unless there's some way to receive updates from BGA itself.

Yeah I am not sure about how all of this works. I have little to no coding knowledge but I just wanted to see if it could even be done.

It should be possible in principle for the bot to subscribe to the push notifications and bridge them to Discord.

Unless we have access to the user's browser, I don't think we can receive push notifications. It might be possible to do something with selenium to login and receive these? But then you'd have a bunch of active selenium sessions.

If someone was keen enough to work on it, if I understand correctly it would be technically possible for the bot to host its own endpoints for the Push API (firewalls and sufficiently stable IP address allowing).

Oh ok. So it sounds like it's technically feasible, provided BGA's push notifications are up to spec.

All your table statuses are in a single file.  I wrote a shell script that uses my PHPSESSID to get my /gameinprogress page, query the embedded JSON blob for turn info, convert the BGA user IDs to Discord IDs (manual table), and write all that to a file.  My bot uses that file to create the @mention announcements.  The script and mentions are triggered via a bot command, so the data displayed is always fresh.  One command (turns) bothers everyone with a waiting turn, and another command (myturns) only shows that person's turns.
One stat I'd hoped for is missing: the turn timer.  This would make it possible to notify users when they have a new turn to take.  I have plans to calculate this in the script but haven't been motivated.
Push would absolutely be more efficient, but this glorified screen scraping works for us.  I can share the relevant code if anyone is interested.


My first revup foo

Topic: foo

#
head
base
diff
date
summary

0
d5935003
740c5cdb
diff
Jul 11 15:54 PM
1 file changed, 1 insertion(+)

Reviews in this chain:
└https://github.com/aurimas-balciunas-skydio/revup_clone/pull/1 My first revup foo


Done adding social media icon with effect

Fixes #164
1: Add the social media icon (black and white) with hover effect
https://github.com/user-attachments/assets/0cb597c1-0dd3-4ba8-805c-4f224b4e6e97

@MOHIT-IITP You closed this PR


Don't harcode "compute-0" reference in hci_prepare

With the new unique hostname feature, we can't hardcode "compute-0"
anymore. Wile it still works in Zuul multinode, it breaks on other runs
driven by the "reproducer.yml" playbook.

/lgtm


dotnet 2.1-preview 2 test unable to load dependent project libraries

Hello,
I have a simple xunit test project that references a single .net core 2.1 app.  Both define <TargetFramework>netcoreapp2.1</TargetFramework>.  The app references System.CommandLine: <PackageReference Include="System.CommandLine" Version="0.1.0-preview2-180412-1" /> and includes the proper myget source in order to restore it.
I can build the app without issue, but when I attempt to run the tests, I get the error:

Could not load file or assembly 'System.CommandLine, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified.

If I add the PackageReference to the test .csproj, the tests are able to run correctly.  The tests work without issue with .Net Core 2.0.
I am running the tests both locally and in the docker container 'microsoft/dotnet:2.1-sdk-alpine', both have the same issue.

So the app builds and runs just fine? Its just the unit testing that doesn't work? @kendrahavens Do you know the best people to loop in to help here?

This issue was moved to Microsoft/vstest#1555


[SCIM2] type sub-attribute of member attribute is not validated when creating a Group with members

Describe the issue:
As specified in the [1] "type" sub-attribute of the "members" attribute needs canonical values as User, Group but the existing implementation accepts any value as "type" without validation when sending a post request to Groups endpoint.

How to reproduce:
1.Create 2 users with userName 'samindra' and 'lawyers-new9'.
2.Create a group using the below data and send a post request to https://localhost:9443/scim2/Groups API.
{
  "displayName": "lawyers-new16",
  "members": [
    {
      "display": "lawyers-new9",
      "type":"UnsupporteedType"
    },{
        "display":"samindra",
        "value": "17712b98-3957-48cd-bc49-c4559df817b3"
    }
  ]
}

Expected behavior:
If a unsupported type provided in the request body other than the specified canonical types '400 - Unsupported "type" provided' should be given as the response.
Environment information:

Product Version: IS 5.11.0
OS: Linux

References:
[1]https://tools.ietf.org/html/rfc7643#page-26

Nipun Thilakshan will work on this

Nipun Thilakshan will work on this

I'll be working on this

I'll be working on this


0x38 (SPXERR_AUDIO_SYS_LIBRARY_NOT_FOUND) in  .net 7.0

I'm getting the following exception:
System.ApplicationException: Exception with an error code: 0x38 (SPXERR_AUDIO_SYS_LIBRARY_NOT_FOUND)
   at Microsoft.CognitiveServices.Speech.Internal.SpxExceptionThrower.ThrowIfFail(IntPtr hr)
   at Microsoft.CognitiveServices.Speech.SpeechSynthesizer.FromConfig(SpeechConfig speechConfig)
   at Microsoft.CognitiveServices.Speech.SpeechSynthesizer..ctor(SpeechConfig speechConfig)

when using azure text to speech in  .net 7.0 console application that is deployed in kubernetes using debian 11.6 version.
Note that the application is running without any exception locally only getting this exception when deployed to kubernetes.
I have tried to add this command to docker file
RUN apt-get update && apt-get install -y build-essential libssl-dev ca-certificates libasound2 wget as stated here:  https://learn.microsoft.com/en-us/azure/cognitive-services/speech-service/quickstarts/setup-platform?pivots=programming-language-csharp&tabs=linux%2Cdebian%2Cdotnet%2Cjre%2Cmaven%2Cnodejs%2Cmac%2Cpypi:  but it didn't help

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

ID: 01b13b79-a598-c1dd-7100-1a6e4becbaae
Version Independent ID: e9376cc7-efd8-73a0-7724-1bac029e17f4
Content: Install the Speech SDK - Azure Cognitive Services
Content Source: articles/cognitive-services/Speech-Service/quickstarts/setup-platform.md
Service: cognitive-services
Sub-service: speech-service
GitHub Login: @eric-urban
Microsoft Alias: eur

@sergiu-gheorghe
Thanks for your feedback! We will investigate and update as appropriate.

Found the problem on our side, the command
RUN apt-get update && apt-get install -y build-essential libssl-dev ca-certificates libasound2 wget was not run properly from dockerfile and it wasn't installing the libasound2


Improved Install Instructions

A few changes that I think are important:

The package has now stable releases. So we should remove the version constraint on the "composer require" call.
Removed the part about making the changes to composer.json manually: having that section on the README requires unnecessary maintenance (it has to be updated with every stable release).
Running composer update to install the recently-required package is a bad idea because it will update all other packages. composer install should be used instead. Or composer update --lock at the very least.

@gabrielsomoza thanks!


Database files are incompatible with server

Hey I got the following Error when starting the container:
2019-03-01 08:46:20.785 UTC [1] FATAL:  database files are incompatible with server
2019-03-01 08:46:20.785 UTC [1] DETAIL:  The data directory was initialized by PostgreSQL version 10, which is not compatible with this version 11.2 (Debian 11.2-1.pgdg90+1).

Any idea how to resolve this?
Thanks

I solved this by doing the following:
docker-compose exec db bash
cd ~/.docker
rm -rf <database folder>

after that I restarted the db container and imported a new database dump and it works again.
Maybe this will help someone with the same problem.
Cheers


Error while calling cudaOccupancyMaxPotentialBlockSize

When I starting my script I see that:
RuntimeError: Error while calling cudaOccupancyMaxPotentialBlockSize(&num_blocks,&num_threads,K) in file /tmp/pip-build-ab7b7zjr/dlib/dlib/cuda/cuda_utils.h:186. code: 98, reason: invalid device function
My CUDA settings:
import face_recognition

def recognition(unknown_faces, known_faces):
    MODEL = "cnn"

    known_faces_encodings = []
    for known_face, unknown_face in zip(known_faces, unknown_faces):
        image = face_recognition.load_image_file(known_face)
        encoding = face_recognition.face_encodings(image)[0]
        known_faces_encodings.append(encoding)

    result = []
    for unknown_face in unknown_faces:
        image = face_recognition.load_image_file(unknown_face)
        locations = face_recognition.face_locations(image, model=MODEL)
        encodings = face_recognition.face_encodings(image, locations)
        for face_encoding in encodings:
            results = face_recognition.compare_faces(known_faces_encodings, face_encoding)
            match = None
            if True in results:
                match = unknown_face
                result.append(match)

    return result

Maybe who knows how to resolve this? Thanks in advance

Are you able to solve the issue? I am facing the same problem.

Are you able to solve the issue? I am facing the same problem.

Yas. I just bought server with another video card

Thank you for your response.
On Tue, Feb 22, 2022 at 12:05 AM Maksim @.***> wrote:

Are you able to solve the issue? I am facing the same problem.
Yas. I just bought a server with another video card
—
Reply to this email directly, view it on GitHub
https://github.com/davisking/dlib/issues/2415#issuecomment-1047143450,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACMIJXKDMTVFE4FJEN4YSYDU4KAXVANCNFSM5CGK6XXA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

--
Sudheer P
United Software
Mob:9495364761


How do i get the total duration of a mp3 file in .net core

I have a .net core web app that i am allow users to upload audio - and i want to get the duration - i have installed the Naudio.core nuget package.
I have the following code to get the duration of a wav file and this works fine:
WaveFileReader wf = new WaveFileReader(fileName);
return wf.TotalTime;
How do i do the same for .mp3 files - i went looking for Mp3FileReader but it doesnt appear to be in the Naudio.core pacakge?
I dont need to play these files - all i want is to get the duration of the audio.
Am I missing a package or what am i missing here?
Also is there a smarter way that tries to determine the encoding and return the duration without me relying on the file extension for the type?

If I remember correctly:
WaveStream mp3Stream = new Mp3FileReader("file.mp3");
TimeSpan timeSpan = mp3Stream.TotalTime;

You can also use MediaFoundationReader which should be slightly quickly
The NAudio.Core package only contains the cross-platform parts of NAudio. Reading MP3s whether by Mp3FileReader or MediaFoundationReader uses Windows-specific APIs. If you just reference the top-level NAudio NuGet package you'll get everything you need

Thanks guys


🌱 schedule on certain day, and add ok-to-test automatically

IPAM schedule:

GH actions: monday - monthly
Gomod: tuesday - weekly

Automatically add labels:

ok-to-test

We have dynamic Prow scheduling now and proper requests, we should not suffer from load failures in very basic tests anymore.
Fix indentation for comments, and make config consistent between each other as well.

/cc @kashifest
/hold
I want Kashif's opinion on this and other scheduling PRs, hence hold.

/retitle 🌱 schedule dependabot on certain day, and add ok-to-test automatically

/approve

/unhold
/override metal3-centos-e2e-integration-test-main metal3-ubuntu-e2e-integration-test-main


Report on This week in GNOME

Hi, sorry to open an issue for this. But I found this app on Flathub and I think it would be really cool to report this app on This week in GNOME. It would gain a lot of visibility.
https://matrix.to/#/#thisweek:gnome.org

@CleoMenezesJr Thanks a lot for making me aware of this channel. I would like to release the 1.0 version and run tests with different types of photometric files before I announce this application to a broader audience though.
By the way, is there any process for announcing a non-core application in the chat? Should I tag the bot and present shortly the application and its features?


Hebrew Translation Final Steps!

Congrats on almost finishing the Hebrew docs! There are just a couple more things we need to do before we can mark the core pages as complete!

[x] Change the DocSearch API key  #69 . One of the maintainers needs to sign up for DocSearch
[ ] Go over the pages of the site one last time to check for consistency

First task is done #70


accurately calculate renter spending

This PR updates the renter to accurately reflect spending for the current billing period. The previous calculation did not take into account for all contracts in the billing line. This implementation provides a new contractor method, PeriodSpending(), which iterates through every contract line in the current billing period to accurately calculate spending.

Updated with latest review comments


Train faces fails

hi,
when executing train faces it fails after a second. checking the docker-log, i`m getting the following lines when try to train faces.
/miniconda/lib/python3.8/site-packages/django/db/models/fields/__init__.py:1365: RuntimeWarning: DateTimeField LongRunningJob.finished_at received a naive datetime (2020-12-11 21:25:04.104340) while time zone support is active.
  warnings.warn("DateTimeField %s received a naive datetime (%s)"

workaround: set USE_TZ = False in /code/ownphotos/settings.py
but i got the next error in ownphotos.log...
2020-12-11 21:57:42,083 : face_classify.py : train_faces : 112 : INFO : Before fitting
2020-12-11 21:57:42,084 : face_classify.py : train_faces : 148 : ERROR : Expected 2D array, got 1D array instead:
array=[].
Reshape your data either using array.reshape(-1, 1) if your data has a single feature or array.reshape(1, -1) if it contains a single sample.

Thank you for finding the bug. You need to first label a few faces per hand. If there are no labels it throws the exception.


Feature request: set baud rate dynamically in idf_monitor.py (IDF-86)

Via https://esp32.com/viewtopic.php?f=2&t=1446#p7353

And with the baudrate: wish we could set this on demand like before (Ctrl-T Ctrl-B).

Closing as noone else has requested this, and there are now config items to sync the default monitor baud rate with the console baud rate - which is simpler than having to change it each time monitor is run.


error: expected type after 'as'

I got an error with a project that compiles with xCode. What's wrong with the Alamofire Pod?
pod 'Alamofire', :git => "git@github.com:Alamofire/Alamofire.git", :branch => 'xcode-6.3'
myprojrect/Pods/Alamofire/Source/Alamofire.swift:82:93: error: expected type after 'as'
    var mutableURLRequest: NSMutableURLRequest! = URLRequest.URLRequest.mutableCopy() as! NSMutableURLRequest

snapshot prints out the compile command it uses when running. Try copy&pasting it and run it for yourself to see a more detailed error message. If you want to provide a custom build command, you can do so using the Snapfile.
Let me know if you need more help.

xctool -sdk iphonesimulator CONFIGURATION_BUILD_DIR='/tmp/snapshot/build' -workspace 'myapp.xcworkspace' -scheme 'myapp' DSTROOT='/tmp/snapshot' OBJROOT='/tmp/snapshot' SYMROOT='/tmp/snapshot'  clean build
This produces the same error. Maybe xctool uses the wrong SDK?

Probably, you can provide your own build command if you want.


v12.5.1 is not working

Running with version that version yields:
node:internal/modules/esm/resolve:342
  return new ERR_INVALID_PACKAGE_TARGET(
         ^

Error [ERR_INVALID_PACKAGE_TARGET]: Invalid "exports" main target "dist/index.js" defined in the package config<EMAIL_ADDRESS>imported from /home/mla/work/argos/js_src/mdc2_tak_service/js_src/services/takReceiverService.js; targets must start with "./"

node,js version 20.17.0
tsc version 5.6.2
Error is also higlighted by just opening the project in vscode.
Prepending the export paths with ./ seems to fix it.

@mrtnlrsn Strange, I deployed this to production without incident, It must have been using the old style exports.
Fixed both this and the group issue in v12.5.2. Thanks as always for the reports!


Errors in trying to use this project as a library

Last release was 0.9.0 back in 2020.
At that point in time, The go.mod in this project referred to this project as,github.com/VerizonDigital/vflow. See
Go tooling tries to pull the latest tag which is 0.9.0 and then fails because it's trying to download github.com/EdgeCast/vflow but the project in that tag is still called, github.com/VerizonDigital/vflow.
emerald :: ~/hobby/netflow.test 130 » go get -u github.com/EdgeCast/vflow/vflow
go<EMAIL_ADDRESS>parsing go.mod:
	module declares its path as: github.com/VerizonDigital/vflow
	        but was required as: github.com/EdgeCast/vflow

Please create a new release. The project name in go.mod has been updated already so a new release should fix the problem.

@ishanjain28 The project's original maintainer @mehrdadrad has moved on to another company (Riot Games I believe).
I'm not sure how much he's planning on maintaining it going forward.  I'm not entirely familiar with the project or the release process, but I'll try to give the project an org update and a new release.

hey @tinselcity thank you for responding!
I had tested this out in my own fork https://github.com/ishanjain28/vflow and just creating a new release will fix this problem.
(also, I had to write my own thing for this because this project doesn't support dumping flows to ZMQ which is used by ntopng)

Thx I put up PR: https://github.com/EdgeCast/vflow/pull/162
I'm reaching out to Mehrdad as well.
I'll try to at least get some module updates and maybe a latest release out the door.
Thanks so much for bringing this to our attention!

Thanks @tinselcity! I just merged the PR and I created a new release! (v0.9.1)
@ishanjain28 Please try again!

Thx so much @mehrdadrad !

It works fine now! thank you


Fixed memory leak in iOS/MAUI

Fixed #56 in MAUI. I don't know if the leak exists in Xamarin.Forms or not.
On iOS in MAUI, it's necessary to call DisconnectHandler() to prevent the CollectionView from leaking. This is a big issue since the leak will cascade through the system.Parent property to the containing page and prevent it from being garbage collected.
This PR introduces a new BindableProperty on the CollectionView AutoDisconnectHandler, which is true by default and will call DisconnectHandler() during the Unload event.
I added the bindable property because, while automatically disconnecting the handler on unload is what most developers will want 99% of the time, you may not want this if the CollectionView is intentionally being temporarily removed from the main object tree. In these cases, the bindable property allows developers to opt out of this automatic behavior and assume responsibility for calling DisconnectHandler() themselves.

Once again a very good catch, thanks Adam!


Expected added functionality

[ ] Adsorption auxiliary wire
[ ] Copy and paste
[ ]  Context menu
[ ]  Collision detection

收到，后面会放需求墙上，让社区用户参与业务插件的开发～


Updated for Ember 2.0

Update to Data Down, Actions Up for ember 2.0+.
Remove unnecessary templates, now people can apply their own classes to the input element as they wish.
removed 2 way binding which is replaced by the on-selected action.
pick-a-time now allows a nulls-date property for more flexibility when binding to the same date with both a time and date picker.
Allow the input to be disabled by setting the disabled property to true.
Properly update the date/time when they are updated outside of the control.
add fix for bootstrap readonly inputs.
updated tests.

This looks great, thanks! :smile:
It looks like addon/components/common.js is never used, could you remove it if that's true?

Oh yeah, I was going to move all the common stuff from both time and date pickers into it. I will fix it.
Also, this is a breaking change for previous users also and would probably need a major version bump.

@chrissloey all fixed.

@chrissloey I found a bug.  When I have preselected a date you can't change the month.  I will need to investigate.

Fixed the issue above.

Great, thanks

Released as 1.0.0 @jackmatt2 :smile:


"docker-compose" is now "docker compose"

What happened?
docker-compose not a valid command any more in a fresh docker(-compose) install.
What should've happened instead?
compose is now a plugin to docker. The command changed from docker-compose to docker compose.
A update of the docs and code is needed.

Two of the three installation types detailed in the docker docs and linked in the cookiecutter-django docs result in the "new" command line (installing via Desktop, scenario one, and installing as a plugin, scenario two / with the hint of pypi being outdated). I would imagine going forward more and more people will have the new command line. So I suggest changing the commands in the docs as more people (like me, being a first time user) just copy/paste regularly from the docs. The question is for me, when is a good time, or is there even one.

Writing the docs so it serves first-time-users is a good idea. If you have the time to pull it off @sebastianelsner then the right time is there I should say.

Compose is indeed a plugin but still available as standalone and even available through pypi (but outdated).

Just a note on that PyPI version: this is compose v1 which used to be written in Python. I think the current version (v2) is written in go. You can see that in their GitHub repo by switching between v2 branch and older v1.x branches.
Even though the standalone version installs v2, it's still docker-compose, this is indeed a bit confusing.
Maybe we could update the docs to just use docker compose with a note at the beginning saying that it might be with a -. I think beginners are more likely to get the version without -at this point.

According to the docs it is indeed rewritten in Go: https://github.com/docker/compose#about-update-and-backward-compatibility

Maybe we could update the docs to just use docker compose with a note at the beginning saying that it might be with a -. I think beginners are more likely to get the version without -at this point.

This has my preferences

@sebastianelsner Hello. I'm quite new to the codebase but I'd love to work on this issue if that's okay

Yes, it's okay, and there no need to ask for permission to pick up an issue 😄 The only requirement is that there is no pull request already opened for it (which is fine here).
Feel free to fork this repo, make the changes and send us a pull request. There are more details in our contributing guide.

@browniebroke Thanks a lot. I've done a bit of digging around and found that some scripts and test files are also using docker-compose .Should I change those as well?

Probably, yes. Best to be consistent across the board.

@browniebroke thanks. I'm on it


UI improvements

Codecov Report

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

@@            Coverage Diff            @@
##             master       #6   +/-   ##
=========================================
  Coverage     91.93%   91.93%
  Complexity       55       55
=========================================
  Files            12       12
  Lines           186      186
=========================================
  Hits            171      171
  Misses           15       15

Continue to review full report at Codecov.

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


Unwrap exception (fix #54)

Codecov Report

Merging #55 into master will decrease coverage by 0.01%.
The diff coverage is 91.66%.

@@            Coverage Diff             @@
##           master      #55      +/-   ##
==========================================
- Coverage   91.18%   91.16%   -0.02%
==========================================
  Files           8        8
  Lines         601      611      +10
==========================================
+ Hits          548      557       +9
- Misses         53       54       +1

Impacted Files
Coverage Δ

pyathenajdbc/cursor.py
97.91% <100%> (ø)
:arrow_up:

pyathenajdbc/util.py
89.74% <90%> (+0.08%)
:arrow_up:

Continue to review full report at Codecov.

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


bruig: update sub/unsub actions in menu

fix #403

Getting an error when attempting to unsub from the context menu (accessible by click avatar in a GC).


Adding event-handling doc

Added explanation and exmaples on how to use
1:EnqueueRequestForObject
2:EnqueueRequestForOwner
3:EnqueueRequestsFromMapFunc
Fixes #1028

@joelanford : Finally added the doc.

@LiliC

@gaurav-dalvi Thanks for the PR.
I've been taking a look again at upstream controller-runtime docs for the event handlers pkg.
It seems to me that the documentation for each type of handler is already clear and concise enough in the godocs. Having that here in the SDK repo again would at best be repeating/rephrasing the upstream docs. I think I mentioned in a previous comment that we probably shouldn't repeat the upstream docs, but rather point out that there are different options for handler types and then just link to the upstream godocs.
However there certainly is room for improvement in illustrating the example code for the EnqueueRequestsFromMapFunc handler.
And I think that was my main motivation for this TODO. With a more detailed example we can highlight how the EnqueueRequestsFromMapFunc handler can be useful for operators that have dependencies on resources that they don't own.
That can be done through your example. Or another example that I've seen in the wild for the gardner-extensions handler where a watch event for a secret is fanned out all the CRs that are using it in the spec.
TLDR: I would suggest that we update this PR to only point to the upstream godocs for now. And then try to update the examples and godocs on the controller-runtime where lacking.

Thanks @hasbro17 . @joelanford  and me talked on operator-sdk slack channel and then came up with this. My experience in working with operator-sdk for 2-3 months tells me that Memcache example is too naive and will never get used in most of the practical implementation of operator-SDKs. It took a significant amount of time to understand the usage of EnqueueRequestsFromMapFunc  . GoDo of that is limited and as you pointed out example is also not useful. Purpose of this PR is to make use-guide single page to understand the usage of all the handlers, which is the most used thing in operator-sdk by developers.  With practical example as per this PR makes much more easy to understand the use case of EnqueueRequestsFromMapFunc . Thats why i feel this PR is more relevant in the context of operator-sdk.

The memcached example is suitable for the purposes of the user-guide, which is to demonstrate the basic workflow and APIs.
The intent is not to have users use that as a base for building their projects.
The issue I have with the doc in this PR is that the explanations and examples for EnqueueRequestForObject and EnqueueRequestForOwner are much less precise than the ones in the usptream godocs. That's why I would prefer to just link directly to them.
For example, just compare what we have here vs what's upstream for EnqueueRequestForOwner.

Our doc:This is generally used in handlling secondary resource of the operator. It will map each event to
`Reconcile()` request for the owner of deployment.

upstream godocs:EnqueueRequestForOwner enqueues Requests for the Owners of an object. E.g. the object that
created the object that was the source of the Event.

If a ReplicaSet creates Pods, users may reconcile the ReplicaSet in response to Pod Events
using:

- a source.Kind Source with Type of Pod.

- a handler.EnqueueRequestForOwner EventHandler with an OwnerType of ReplicaSet and
IsController set to true.

So at the very least I would not want to repeat the docs/examples for EnqueueRequestForObject and EnqueueRequestForOwner here in the SDK docs.

Purpose of this PR is to make use-guide single page to understand the usage of all the handlers

If we're already referring to upstream docs for two of the handlers then that's not the case anymore. So that only leaves the EnqueueRequestsFromMapFunc.

With practical example as per this PR makes much more easy to understand the use case of EnqueueRequestsFromMapFunc

Any example like the one that you've provided is going to be limited in isolation. In the case of your example it's just filtering pods events by checking if they are in the CR namespace.
It may be more practical to you since it might be from a familiar use case but it wasn't obvious to me why an operator would do that. For me it made much more sense for an operator to perhaps filter and fan out watch events for secrets that it's CRs depends on. So no example is going to be perfect.
Regardless, my point still stands that we can take this example and improve the upstream godoc since we expect users to look at that anyway.
And to further convey how it's used practically, we can point to actual operators that are using this handler so users can see the example in its full context.
In the end I would much rather improve the API docs upstream so it's more clear not just for SDK users, but for controller-runtime users in general.

@gaurav-dalvi I've added the links in the user-guide to the upstream EventHandler godocs in https://github.com/operator-framework/operator-sdk/pull/1783.
So I think we can close this for now, and try to submit a PR upstream to elaborate on the EnqueueRequestsFromMapFunc example.

Closing in favor of #1783

Thanks @hasbro17 . I will create PR against this repo to explain EnqueueRequestsFromMapFunc  with an example.


Remove duplicate must_use

Clippy emits:
warning: this function has an empty #[must_use] attribute, but returns a type already marked as #[must_use]
This is because the return type of the function legacy_encode_signing_data_to is EncodeSigningDataResult which is
already marked as must_use. There is no need to have must_use on the function also.

Hey @apoelstra, this PR is needed before any other PR can get a green CI run. The PR that introduced this warning must have had a green CI run before the 'add clippy to CI' PR merged allowing it to merge without re-running CI.

Neat -- I also added cargo clippy to my local post-merge sanity check (which is currently only cargo test)


Which category would Dorothy belong under?

Dorothy: 🧙♀ Bring your dotfile commands and configuration to any shell, including Nu, Fish, Zsh, Bash, Elvish, Xonsh.
It has hundreds of commands that work across multiple shells and operating systems, so could qualify for Bootstrap and Inspiration. It also fits the dotfile management of the general-purpose utilities. And it also provides scripts to help you write your own commands, so fits tool-specific frameworks.

I'd go with bootstrap since it includes commands.


Can't read text of a

I am trying to get text from a span
SKU: 124356
I can successfully get the span object however Text() returns empty. I can successfully get the text for other types but not for span.
This is the code I am using:
func visit(url string) {
	fmt.Println("Visiting: " + url)
	res, err := http.Get(url)
	if err != nil {
		log.Fatal(err)
	}

	defer res.Body.Close()
	if res.StatusCode != 200 {
		log.Fatalf("status code error: %d %s", res.StatusCode, res.Status)
	}
	doc, err := goquery.NewDocumentFromReader(res.Body)

	if err != nil {
		log.Fatal(err)
	}
	doc.Find(".sku").Each(func(i int, s *goquery.Selection) {
		fmt.Println("SKU is: " + s.Text())

	})
}

When I debug the code and Text() medhod, I see that Type is "TextNode" however Data shows as  "\n\t\t      \n\t            "

Any idea? Is it the doc structure that was not constructed correctly or there is another way to get a text from a span?

Hello,
I guess the html or the code is not exactly what you provided, as this works as expected:
const data = `
SKU: 124356
`

func main() {
	doc, err := goquery.NewDocumentFromReader(strings.NewReader(data))
	if err != nil {
		log.Fatal(err)
	}
	txt := doc.Find(".sku").Text()
	fmt.Println(txt)
}

// Prints:
// SKU: 124356

Please provided a minimal yet complete runnable example of code + html that reproduces the issue.
Martin

Thanks @mna
I have used this URL to get SKU
As you can see there is a span with text SKU: 3193780.
(Sorry I couldn't send the playground link as it does not support real network calls.)
The minimal code is shown below:
package main

import (
	"fmt"
	"github.com/PuerkitoBio/goquery"
	"net/http"
)

func main() {
	urlScrape := "https://www.basspro.com/shop/en/federal-champion-brass-centerfire-handgun-ammo"
	client := &http.Client{}
	req, _ := http.NewRequest("GET", urlScrape, nil)
	req.Header.Add("Accept", `text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8`)
	req.Header.Add("User-Agent", `Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.64 Safari/537.11`)
	res, _ := client.Do(req)
	defer res.Body.Close()
	doc, _ := goquery.NewDocumentFromReader(res.Body)
	doc.Find("span.sku").Each(func(i int, selection *goquery.Selection) {
		fmt.Println("SKU found: " + selection.Text())
	})
}

The output is:
/private/var/folders/jr/2_y012z902lgt8c04cww83_80000gn/T/___go_build_StockMiner_main
SKU found: [

                ]

Process finished with exit code 0

Thanks!

Adding my .02...
When I look at the source for that page, there is no span with a class of sku.  The markup for the sku is
SKU: 3193780
Such is the danger of scaping.  There is a parent div with a class that might be easy to do a selector for, but the sku is the 3rd child of that parent.  Good luck!

Thanks @vhodges
When I "inspect" the page I see the following span with class:

However If I "View Page Source" I see the tag without class as you comment

SKU: 3193780

In that case, the question is, which one should I depend on when scraping? "Inspect" or "View Page Source"?
Thanks

@ecaglar Sorry, I see what I did now.  I inspected the sku in the 'product chart'.
However, try printing the document you get back. When I try to curl (even with a valid User-Agent) that url, I get an error back from the server "Permission denied" (not sure of the status code returned is - not enough curlfu)

Yeah, as Vince mentions, the page is probably modified by javascript. What you provide to goquery is the equivalent of "View Page Source", i.e. the original html document itself. There are a couple of community-provided tips in the wiki to get javascript-modified html to goquery, but I can't help you with that, I haven't used those tools: https://github.com/PuerkitoBio/goquery/wiki/Tips-and-tricks#handle-javascript-based-pages


Pattern Issue

pattern search in
Task<IEnumerable<RedisKey>> GetKeys(string pattern = "");

in file - IDistributedUnifiedRedisCache is case sensitive.
For example - if I send keyword then any key which has KeyWord sub-string in it wont be returned as it doesn't match the case of keyword.
Please look into it and share how to ensure the keyword is checked ignoring the case of the characters.

Redis is case-sensitive by default. Hence case-sensitive search cannot be supported.


Enhancement: Search Functions

Mostly self-explanatory, but the idea is the ability to search for a particular song, which would mostly be useful for checking if you've already added a particular track, or to see if the base game contains it already.

Implemented for testing as part of 1.54b. Closing.


Support installing git-annex .deb's to a given directory instead of system-wide

Closes #71.

The test failure is due to a transient network failure while trying to download the Miniconda installer.

Let's proceed.  I think it should be safe and desired to release, thus tagged.  Thank you @jwodder!


Flatten wrapper does not work as expected

Hi authors,
First, thanks for providing a benchmark dedicated for memory-based tasks. I am trying to install and run your benchmark but meet some problems.
I'd like to use Flatten wrapper in your repo. Following your instructions.
import gymnasium as gym
import popgym
from popgym.wrappers import  Flatten

env_name = ...
env = gym.make(env_name)

Flatten(env) # cause error

It raises error of assert error https://github.com/proroklab/popgym/blob/master/popgym/core/wrapper.py#L13, when I use gym.make to create an env, but not usingpopgym.envs..
Secondly, I think there is a bug in Flatten wrapper: https://github.com/proroklab/popgym/blob/master/popgym/wrappers/flatten.py#L27 this should be on observation_space, not action_space.
Now my workaround is to use from gymnasium.wrappers import FlattenObservation instead.

Thanks for the report. I think this probably depends on the gymnasium version you are using, as they seem to love making breaking changes.
At this point, I will probably remove the gym.make capabilities as this is not the first time gymnasium updates have broken this. You can try using categories defined here instead of gym.make.
e.g.
import popgym
print(popgyms.envs.ALL)
print(popgyms.envs.CONTROL_HARD)

Closing this as the bug appears to be fixed.


Enable ARM64 builds on Feedback app.

What?
Similar to Release, this PR swaps the used GH Workflow to the multi-arch one so we can start building ARM64-based images.
Why?
ARM is the future and we'd like to start testing it. Release seems like a "low impact" app that we can safely test changes like this before rolling out a wider test.
How?
Once this is merged, we should start seeing Docker images for both AMD64 and ARM64 architecture systems - Docker is smart enough to automatically pull the correct architecture image for the system that is requesting it.
Once we have a few apps built for testing, we can begin small scale tests on Integration with Graviton "tainted" Nodes and see what happens.
Related PRs

https://github.com/alphagov/release/pull/1433

Just checking: description says Release rather than Feedback. Did you mean to open this on alphagov/release instead of this repo?
If you do wanna use Feedback as the guinea pig we should loop in the maintainers from #dev-notifications-ai-govuk team.

Ah sorry I see it's both. Cool no probs. Might be worth seeing how it goes with Release for a day or two?

If you want low(ish)-impact but still properly production app then alphagov/maslow or alphagov/transition would be good choices.
The user support folks can be pretty demanding about availability on Feedback and it's a public-facing frontend.


Theedge 3077 extend model

Description
add new field to our third party repo to store the cs references
FIXES: THEEDGE-3077
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[X New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[ ] Refactor

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[ ] I run make pre-commit to check fmt/vet/lint/test-no-fdo

Codecov Report
Patch and project coverage have no change.

Comparison is base (86c6b78) 58.28% compared to head (eded6dc) 58.28%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1946   +/-   ##
=======================================
  Coverage   58.28%   58.28%
=======================================
  Files          71       71
  Lines       10138    10138
=======================================
  Hits         5909     5909
  Misses       3708     3708
  Partials      521      521

Impacted Files
Coverage Δ

pkg/models/thirdpartyrepo.go
100.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 in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.