Samples

Thanks for creating this fabulous package.
Please could you provide some samples.

Hi there. Please note that I'm not a professional developer so please be careful with any examples I provide. A year ago I started work on a small pdf viewer I never finished (or touched again), maybe it's of any help to you. (howver I'm don't really know if it still builds)
https://github.com/marcpabst/ElectricPDF


another issue

the . is missing in the following powershell command:
$domainName = "testlab"+$yourDomain
it should be : $domainName = "testlab."+$yourDomain

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

ID: f6989d21-f7a7-043b-c91a-cd019a19c0e6
Version Independent ID: 39e286bc-58fe-768e-ee65-2a2fedf1e544
Content: Simulated enterprise base configuration for Microsoft 365
Content Source: microsoft-365/enterprise/simulated-ent-base-configuration-microsoft-365-enterprise.md
Service: o365-solutions
GitHub Login: @JoeDavies-MSFT
Microsoft Alias: josephd

@wloeven  - Thank you for submitting feedback.
I will get this issue over to the Microsoft 365 writing team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

@wloeven Corrected and updated. Thanks for letting us know. Sorry for the inconvenience.


[WIP] Fix dns addon docs

Fixes #720
Implemented a quick docs fix based on the issue comment referenced in the above issue.  I have not tested these changes yet, I'll get to that soon.
If you've got some expertise in this area any and all feedback is welcome.

I'm not sure this fixes anything - or if it even fixes the root cause of #720.
#720 mentions kubernetes issue https://github.com/kubernetes/kubernetes/issues/32480 which is triggered by missing KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT variables inside the kube-dns pods.
It seems to me #720 is caused by incorrect serviceaccount tokens (re-rolling a cluster against an existing etcd dataset would do that for example) but the issue is a little too light on details to make any conclusions.

@pieterlange Thank you for the feedback.  I'll look into the issue more and see if we can figure out a fix for the root cause of #720.

Agreed - the dns addon should not need these changes (and should be able to use the service account injected into the pod). Closing this, but please let me know if this should be re-opened.


ci(root): fix deploy

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@af2e2f8). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #29   +/-   ##
=======================================
  Coverage        ?   42.75%
=======================================
  Files           ?        2
  Lines           ?      138
  Branches        ?       18
=======================================
  Hits            ?       59
  Misses          ?       70
  Partials        ?        9

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

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


Example 02-Metaballs doesn't work as expected

For the life of me, I can't find the reason why the "metaball" looks like garbage. I think my math is wrong or Nim does something funny or implicit.

If I get time I'll take a look. BTW I'm currently using this project with my nuklear bindings in my game engine. Thank you for fixing the threading code in the examples, and more importantly for the awesome bindings!

It flickers a ton between images like this:


Add a default timeout for requests

We've observed an issue where processes hang indefinitely off the back of a call to get_organization in the redbrick SDK. For example:
Thread MainThread tid:1 (most recent call first):
  File "/usr/local/lib/python3.8/ssl.py", line 1132 in read
  File "/usr/local/lib/python3.8/ssl.py", line 1274 in recv_into
  File "/usr/local/lib/python3.8/socket.py", line 669 in readinto
  File "/usr/local/lib/python3.8/http/client.py", line 277 in _read_status
  File "/usr/local/lib/python3.8/http/client.py", line 316 in begin
  File "/usr/local/lib/python3.8/http/client.py", line 1348 in getresponse
  File "/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 462 in _make_request
  File "/usr/local/lib/python3.8/site-packages/urllib3/connectionpool.py", line 715 in urlopen
  File "/usr/local/lib/python3.8/site-packages/requests/adapters.py", line 486 in send
  File "/usr/local/lib/python3.8/site-packages/requests/sessions.py", line 703 in send
  File "/usr/local/lib/python3.8/site-packages/requests/sessions.py", line 589 in request
  File "/usr/local/lib/python3.8/site-packages/requests/sessions.py", line 637 in post
  File "/usr/local/lib/python3.8/site-packages/redbrick/common/client.py", line 81 in execute_query
  File "/usr/local/lib/python3.8/site-packages/tenacity/__init__.py", line 382 in __call__
  File "/usr/local/lib/python3.8/site-packages/tenacity/__init__.py", line 289 in wrapped_f
  File "/usr/local/lib/python3.8/site-packages/redbrick/repo/project.py", line 120 in get_org
  File "/usr/local/lib/python3.8/site-packages/redbrick/organization/__init__.py", line 35 in _get_org
  File "/usr/local/lib/python3.8/site-packages/redbrick/organization/__init__.py", line 32 in __init__
  File "/usr/local/lib/python3.8/site-packages/redbrick/__init__.py", line 111 in get_org
  File "/app/report_svc/annotation/redbrick/organization.py", line 20 in get_organization

... our stack follows ...

While it would be good to understand the root cause of this issue, I would suggest as a interim measure HTTP requests should have some timeout. By default, the requests library does not timeout so there always some possibility you'll hang forever, which is not ideal!
It's not easy for users to customise this as it's internal to the redbrick SDK, but I'd suggest some reasonably long default timeout passed into the request.Session initialization: https://github.com/redbrick-ai/redbrick-sdk/blob/master/redbrick/common/client.py#L35
Perhaps 30 or 60 seconds if you wanna be really safe. If you can expose this for users to be able to customise even better.

Published v2.13.21 with 30s timeout


allows source in ProxyRequest to accept string

Closes #3

@leobeal BTW You can run make doit to check linting, formatting and imports.

@leobeal BTW You can run make doit to check linting, formatting and imports.


MM-28882: Add config setting to ignore guest ldap sync

Summary
Adds a configuration setting for SAML to ignore Guests when Sync'ing LDAP users.
Ticket Link
https://mattermost.atlassian.net/browse/MM-28882
Related Pull Requests

Has server changes
https://github.com/mattermost/mattermost-server/pull/15936

Screenshots

/update-branch


Fixup rename main branch

needs: https://github.com/ros2-dotnet/dotnet_cmake_module/pull/6

@hoffmann-stefan sorry about the mess! I thought I had updated everything related to the main/master branch rename.

@hoffmann-stefan sorry about the mess! I thought I had updated everything related to the main/master branch rename.

No worries :)


Update/release docs

Updating release docs for 1.22. Would like an approval so I can merge it midnight.

Pull Request Test Coverage Report for Build 265993285

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 38.176%

Totals

Change from base Build 265885210:
0.0%

Covered Lines:
19146

Relevant Lines:
45823

💛  - Coveralls


Problem installing this plugin

In a new vagrant installation, I cloned this repo and following instructions, I tried to install goodhosts plugin.
Installing the 'vagrant-goodhosts' plugin. This can take a few minutes...
Vagrant failed to properly resolve required dependencies. These
errors can commonly be caused by misconfigured plugin installations
or transient network issues. The reported error is:
conflicting dependencies net-ssh (>= 2.6.5) and net-ssh (= 6.2.0.rc1)
Activated net-ssh-6.2.0.rc1
which does not match conflicting dependency (>= 2.6.5)
Conflicting dependency chains:
net-ssh (= 6.2.0.rc1), 6.2.0.rc1 activated
versus:
net-scp (= 1.2.1), 1.2.1 activated, depends on
net-ssh (>= 2.6.5)
Gems matching net-ssh (>= 2.6.5):
net-ssh-6.2.0.rc1
My system is Manjaro on testing branch. It worked some time ago on another Manjaro testing. If I understand, maybe I need to install net-ssh 2.6.5, but my system is trying to install a newer version.
Manjaro Testing branch
Vagrant vagrant-2.2.14-1
vvv: I just clone the repo today

This doesn't involve VVV but is just an error on installing the plugin on your system.
I think that you don't have an updated Ruby version on your machine.

Thanks, I'm using Ruby 2.7.2 on Manjaro (Arch based). I see there is a 3.0 version, but don't know if that's the problem. Is that package needed or requested by this plugin?

Hi guillermo, is a long time since the last Mozilla event we met :-)
I am using ruby 1.7.1 and works on debian.
Looking on https://github.com/hashicorp/vagrant/issues/12202 seems an issue also on Archlinux and downgrading vagrant fix it. There is a pull request merged on vagrant so probably the next release will fix it.

Hi Danielle, yes, long time, and I see you more and more in different github projects I use.
I just arrived to that issue and saw that you point it. I will try with that. Has to work, because I was using vvv with an old installation. Thanks again. I will close with this comment

Ahahah yes, I am very involved with WordPress as core contributor and I am one of the VVV maintainers.
You can find me on the VVV slack instance for anything :-) https://varyingvagrantvagrants.org/docs/en-US/slack/

I will wait for VAgrant update on Arch/Manjaro. I will need it next week or so, so before downgrading I will wait. BTW I'm using your glossary plugin too

The issue is still actual and it works if you downgrade, it doesn't if you don't unfortunately.

This is a bug of vagrant and not of the plugin.
The right way is to ask to the vagrant plugin https://github.com/hashicorp/vagrant/issues/12202 to do a new release (the last one is from november 2020)


[FEA] Update regexp transpiler for breaking change in cuDF handling of negated character classes

Is your feature request related to a problem? Please describe.
Once https://github.com/rapidsai/cudf/issues/11643 is merged, we will need to make corresponding changes in the regexp transpiler, particularly in the following method:
private def negateCharacterClass(components: Seq[RegexCharacterClassComponent]): RegexAST = {
    // There are differences between cuDF and Java handling of newlines
    // for negative character matches. The expression `[^a]` will match
    // `\r` and `\n` in Java but not in cuDF, so we replace `[^a]` with
    // `(?:[\r\n]|[^a])`. We also have to take into account whether any
    // newline characters are included in the character range.

Describe the solution you'd like
Change newline handling per cudf change. Fix regressions.
Describe alternatives you've considered
None
Additional context
None

Here are some of the failing tests
- transpiler detects invalid cuDF patterns *** FAILED ***
  cuDF unexpectedly compiled expression: 	+|a (RegularExpressionTranspilerSuite.scala:62)
- cuDF unsupported choice cases *** FAILED ***
  Expected exception ai.rapids.cudf.CudfException to be thrown, but no exception was thrown (RegularExpressionTranspilerSuite.scala:107)
- sanity check: choice edge case 2 *** FAILED ***
  Expected exception ai.rapids.cudf.CudfException to be thrown, but no exception was thrown (RegularExpressionTranspilerSuite.scala:115)

Follow-on work required before we can close this issue:

Simplify the code in negateCharacterClass now that there is only one newline character (\r) that we have to handle. We should no longer need to wrap it in a character class?
Review and update docs for negateCharacterClass
Determine what the cuDF behavior is for "{2,1}" and update tests accordingly


Add single-plot rasterization capability to CairoMakie

Description
Allows the user to tell CairoMakie to rasterize individual Plots in a Scene, by setting plt.rasterize = scale::Int || true.
CairoMakie will rasterize that specific plot to an image with scale^2 pixels per Scene pixel (1 px per scene px if scale=1 or scale=true) and draw it to the main context.  The drawing order also preserves the z-order of the scene.
This has the potential to drastically decrease file sizes, which is extremely useful for publication plots and large meshes.
Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist

[x] Added an entry in NEWS.md (for new features and breaking changes)
[ ] Added or changed relevant sections in the documentation
[ ] Added unit tests for new algorithms, conversion methods, etc.
[ ] Added reference image tests for new plotting functions, recipes, visual options, etc.

That's a great feature! This will be handy for plotting maps.
It would be great to have that as a global option as well. Pluto displays pngs by default because to many svgs slow down the browser. Probably this problem could be solved by rasterizing all plots, while keeping axis decorations and text as vector graphics.

I think that this could actually be themable as it is now - if you set rasterize = true in the default themes of Heatmap and Surface, for example, that should "just work".  The only potential issue right now is having too many rasterized plots - since each one gets its own image, that would cause a lot of size bloat.  Fixing that would be a bit complicated, though.

The CI failure on Makie/Julia 1 does not appear to be related - seems related to mouse click detection.

@Datseris this may be useful if you are saving GeoMakie plots to pdf - just pass rasterize = 5 or so as a keyword argument to surface or heatmap!


Update spec to reflect more overlap between static catalogs & STAC API's

One of the biggest advances at STAC Sprint 3 was the idea that dynamic catalogs (STAC API) can implement the 'static catalog' spec - they don't have to be limited to just the 'stac api' part of the spec. This lets us layer on functionality in a more coherent way.
The core idea is that a 'level 1' (name tbd) implementation is just the link structure of the 'static catalog', but it can be implemented by a dynamic server, returning a catalog json (as defined in static catalog) at the /stac endpoint. It divides up its sub-catalogs however it wants, but this enables it to be used directly in STAC Browser. This is issue #152 and has a first pull request at #172 which defines an OpenAPI doc for the response.
So a capable server can start with implementing just the /stac link structure (catalogs and sub-catalogs) for browsing. And then it can layer on the /stac/search endpoint to enable return of items based on search criteria. And then it could choose to be WFS 3 compliant, by setting up proper /collections as well as /api and /conformance endpoints.
We should update our core documentation to reflect this. Right now a static catalog and a dynamic catalog / stac api are seen as two different implementations that share return of a STAC Item. Instead the browse link structure should be described as something that can be implemented with either an object store / online file folders, or by an API that is returning the links dynamically. And then the search API can be layered on top (and indeed a third party search could make an object store catalog searchable - it doesn't have to be the same service). This link structure should be specified in both an openapi 3 document as well as a json-schema. And a validation tool should be provided that can check a catalog and its items for conformance. Cc @jbants
This may mean we update our 'folder structure' a bit, and perhaps even name things a bit differently. Perhaps use 'browse' instead of 'static' in some way. And 'search' instead of 'dynamic...
This issue is open for ideas on how to talk about it, and once we get the bulk of open PR's merged I'll take a crack at it.
Related #152

Closed with #258


WIP: CFE-977,CFE-981: unarchiver interface and its implementation

Description
Unarchive simply untars the contents of the archive into:

working-dir (for subfolders of working-dir found in the archive)
cache folder (for subfolders of docker/v2 found in the archive)

Fixes # CFE-981
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
Unit test unarchive_test.go
This interface is not yet plugged into executor.go, but should be later, with CFE-992
Expected Outcome
Unit tests should pass

/lgtm


Remove Kubernetes v1.29 feature flag and make it the default cluster version

This PR removes the feature flag for Kubernetes v1.29 support and make it the default cluster version.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold

/approve

/unhold


Add new method to windows_registry::Key open_mut()

Suggestion
Hi,
It would be awesome if there was a way to open registry key with write access instead of only read access.
There is some case where I don't want to create it if it doesn't exist but I want to open my registry key with write access

Thanks for the suggestion - let me think about what that might look like.

How about allowing the caller to specify the desired access? It could look something like
key = CURRENT_USER.open_with_access(path, KEY_READ | KEY_WRITE);

This would make it possible to use other flags, for example to add KEY_WOW64_32KEY without needing a new method for each combination.


William/perf new

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@8b8f307). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   81.86%
=========================================
  Files             ?      122
  Lines             ?    16960
  Branches          ?     3716
=========================================
  Hits              ?    13885
  Misses            ?     2137
  Partials          ?      938

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 8b8f307...bcc492d. Read the comment docs.


CMU.CLAN version 7.50.00

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.2 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Please check the CMU.CLAN.locale.en-US.yaml
The whole project URL is https://talkbank.org/ by the Carnegie Mellon University. There, under Programs, you find a link labeled CLAN pointing to https://dali.talkbank.org/clan/. At that page you will finde the download link from the manifest.

@wingetbot waivers Add Policy-Test-1.8

@wingetbot waivers Add Validation-Domain


Update Install and Render handlers to tolerate v3 packages with optional marathon templates

Depends on #421
Fixes #419
Fixes #410
Fixes #417
When reviewing, please only look at the contents of the second commit.

@tamarrow @jsancio Please review

LGTM! :shipit:


Issues with ppci-cc backend tree generation

Hello,
I am trying to figure out the effort for writing a backend for a simple CPU. For this I compile simple functions and display the corresponding back-end tree.
For a the C function
char *strcpy(char *d, char *s) {
char *save = d;
while (*d++ = *s++);
return save;
}
This produces the following trees (to be matched by the BURG patterns) :
Generation tree : MOVU64vreg5
Generation tree : MOVU64vreg6
Generation tree : MOVU64vreg0phi_s_alloc_0
Generation tree : MOVU64vreg1phi_d_alloc_0
Generation tree : JMP[strcpy_block1:]
Generation tree : MOVU64vreg0phi_s_alloc_0
Generation tree : MOVI8vreg9load_4
Generation tree : MOVU64vreg1phi_d_alloc_0
Generation tree : STRI8(REGU64[vreg1phi_d_alloc_0], REGI8[vreg9load_4])
Generation tree : MOVU64[vreg7](ADDU64(REGU64[vreg0phi_s_alloc_0], CONSTU64[1]))
Generation tree : MOVU64[vreg8](ADDU64(REGU64[vreg1phi_d_alloc_0], CONSTU64[1]))
Generation tree : MOVU64vreg0phi_s_alloc_0
Generation tree : MOVU64vreg1phi_d_alloc_0
Generation tree : CJMPI64[('==', strcpy_block3:, strcpy_block1:)](I8TOI64(REGI8[vreg9load_4]), CONSTI64[0])
Generation tree : MOVU64vreg4retval
Generation tree : JMP[strcpy_epilog:]
This raises some issues (assuming I have correctly understood how all this works) :

Two trees are a copy of a vreg to itself (tree 6 and 8), the backend can check for such cases that but it is better if thies MOVE are not generated

This makes a lot of copies... Even if after code selection, register allocation will try to reuse the real registers, each MOVE will generate instructions whatever the final real registers are (this is reflected in the corresponding x86-64 code)

There is no way in the backend to know when a vreg is no longer needed (last use), this means that the corresponding real register will not be deallocated til the end of the function.
Precise def-use information are not necessary but the number of times a vreg is used would be nice.

When playing with the -O option, I have seen that in -O 0, the compiler assumes that function arguments come in registers and first saves them on the stack. This is OK especially for debugging.
But if the target architecture transfers the arguments thru the stack there will be a 2nd copy of the arguments. The code generator should use the results of the "determine_arg_locations" and if all args are already on the stack, should not generate another memory copy.

The CJMP instruction has 2 labels (yes/no). This is perfect at IR level. However when generating code, this often produces useless jumps to following instructions :
jmp label3
label3: ...
The x86_64 backend does this all the time. The problem is that the backend does not know what label will come just after the CJMP (blocks are not always generated from 0 to n, for example if we reverse loops). A peephole optimizer could remove this, but it would be better not to produce this at code generation.

These are several points on a single issue report but as there is no much documentation I could be wrong on the interpretation.
Anyway I am impressed by the job done! that's Python productivity at work...

The x86_64 backend does this all the time.

All other backends too. Actually, I got an impression that x86_64 code has fewer of them than less developed archs. I wondered if x86_64 exactly may have some kind of peepholer. I agree this should be done in arch-independent way, even before codegeneration.

Thanks for the thorough review!

Two trees are a copy of a vreg to itself (tree 6 and 8), the backend can check for such cases that but it is better if thies MOVE are not generated

Partly agreed, this instruction selection scheme works well with the implemented register allocator which removes moves from the code after instruction selection.

This makes a lot of copies... Even if after code selection, register allocation will try to reuse the real registers, each MOVE will generate instructions whatever the final real registers are (this is reflected in the corresponding x86-64 code)

No, the moves will be removed physically from the code by the current register allocator. Did you check the resulting code with ppci_explorer.py? Btw, it might make sense to make this tree output available in ppci_explorer.py as well.

There is no way in the backend to know when a vreg is no longer needed (last use), this means that the corresponding real register will not be deallocated til the end of the function.
Precise def-use information are not necessary but the number of times a vreg is used would be nice.

Actually, there is way for this, there is an instruction called RegisterUseDef which serves exactly the purpose of using / defining variables so that their lifetimes are limited, otherwise the variables would be used until the end of the function.

When playing with the -O option, I have seen that in -O 0, the compiler assumes that function arguments come in registers and first saves them on the stack. This is OK especially for debugging.
But if the target architecture transfers the arguments thru the stack there will be a 2nd copy of the arguments. The code generator should use the results of the "determine_arg_locations" and if all args are already on the stack, should not generate another memory copy.

Yes, fully agreed.

The CJMP instruction has 2 labels (yes/no). This is perfect at IR level. However when generating code, this often produces useless jumps to following instructions :
jmp label3
label3: ...
The x86_64 backend does this all the time. The problem is that the backend does not know what label will come just after the CJMP (blocks are not always generated from 0 to n, for example if we reverse loops). A peephole optimizer could remove this, but it would be better not to produce this at code generation.

There actually is some limited form of peephole optimization done to remove jumps to labels right after the jump. Agreed that it would be better to not generate the jump in the first place, but until now I was unable to implement this as such.


Added item of Schema privilege request level value of Access control model

Both Japanese and English correspond
002_Access_Control.html
002_Access_Control.md
Level value is
"unspecified (initial value)"
Contents is
"Inherit parent (upper directory) and apply"
Write things like

Note that the current file name has changed
002_Access_Control -> 006_Access_Control


Add primer tests

TODO List:

[x] Create branch with changes in PR and branch with merge-base (see mypy)
[x] Run pydocstringformatter with merge-base branch in write mode
[x] Checkout to changes branch
[x] Do a non-write branch to get diff
[x] Prettify diff
[x] Probably tons more...

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
405

Relevant Lines:
405

💛  - Coveralls

@Pierre-Sassoulas Small achievement! It works. There are changes on main that would lead to changes to pylint, but the new version of the primer only shows the changes that would be introduced by this PR.
I'm going to do some code cleanup and add some annotations/comments but I actually think this is almost mergeable in an alpha form for the project.
It also gave me some good insight into how to develop this in the future for pylint.

It also gave me some good insight into how to develop this in the future for pylint.

Yeap, having that in pylint will make the new checkers and every modification SO MUCH BETTER. I'm super hyped in anticipation.

Yeap, having that in pylint will make the new checkers and every modification SO MUCH BETTER. I'm super hyped in anticipation.

I have written most of the code here to be somewhat copyable to pylint as well. One of the big issues is the speed: we need to run the program twice for every package we "prime" one. For pydocstringformatter this isn't an issue. For pylint this is...
I was thinking about maybe creating a "needs-primer" label so we can only schedule primers when necessary.. Hm, first 2.13 though 😄

need to run the program twice for every package we "prime" one.

Unless we save the baseline in the repository ? We'd also need to specify the commit for each primer repository. OR maybe it's possible to make a job manual (I did not check the doc of github actions) ?

Unless we save the baseline in the repository ? We'd also need to specify the commit for each primer repository. OR maybe it's possible to make a job manual (I did not check the doc of github actions) ?

Yeah, I was thinking about that as well. But I foresee issues with fixing false-positives and comparing those etc. There is probably a reason why mypy doesn't save the baseline and runs twice for every primer test. They have more than enough knowledgeable contributors to do that optimisation if they saw a possibility/necessity to do so.
Yeah we can. We might also want to start with a smaller subset of repositories to do false positive checking for. I know that home-assistant have actually disabled pylint in some of their CI because it takes too long. So us running over them is perhaps not the best choice.

@Pierre-Sassoulas Not sure if you have the bandwidth to check this. I can merge as is, but I left it open to give you the opportunity to review (and potentially spot any errors that could be copied to pylint when I eventually copy this).


Provide schema for easy validation and authoring of config files

I have created simple RELAX NG schema. If something else is needed shout (e.g. re-open this issue).

Please add XSD so we have better tool support :)
Relax-NG is poorly supported in Java et.al.

OK. But let's wait until format is stable. Prototyping in RNC is much faster. I will provide XSD later.

lol hahaha. Oh shit....


docker help and man pages are not in sync with the command line reference documentation

Here's an example which has caused me some confusion recently:
The docker-run man page doesn't mention that an IMAGE:TAG combination is allowed

https://github.com/dotcloud/docker/blob/master/docs/man/docker-run.1.md#synopsis

Nor does the command line help:

https://github.com/dotcloud/docker/blob/master/api/client/commands.go#L1899

While the command line reference documentation does mention this:

https://github.com/dotcloud/docker/blob/master/docs/sources/reference/run.md#general-form

It would be nice if the command line help and man pages could be kept in sync with the command reference docs.
Perhaps they should be combined.

looks like this has been taken care of, and as far as automating this is covered by #2583, closing


Updating the examples-utils tag

Updating the tag for examples-utils to be latest_stable in accordance with examples

Can you re-open the PR against the upstream repo? I try to keep the history of this main branch the same. Otherwise LGTM!

Thanks, doing it now


apps do not deploy with vespa-onnx-runtime (AWS GPU)

Describe the bug
App deployment fails to converge on GPU-enabled AWS EC2 instance
To Reproduce
Steps to reproduce the behavior:
Amazon Deep Learning AMI instance with Ubuntu 20.04
docker info: Total Memory: 30.89GiB
NVIDIA-SMI 525.85.12    Driver Version: 525.85.12    CUDA Version: 12.0
NVIDIA Container Toolkit CLI version 1.13.5 commit: 6b8589dcb4dead72ab64f14a5912886e6165c079
echo "vm.max_map_count=262144" | sudo tee -a /etc/sysctl.conf
nvidia-ctk cdi generate --device-name-strategy=type-index --format=json | sudo tee /etc/cdi/nvidia.json
vespa config set target local
sudo docker run --gpus all --detach --name vespa-cuda-sss --user vespa:vespa --hostname vespa-container --publish 8080:8080 --publish 19071:19071 vespaengine/vespa:8.198.18
sudo docker exec -u 0 -it vespa-cuda-sss /bin/bash

dnf config-manager
--add-repo https://developer.download.nvidia.com/compute/cuda/repos/rhel8/x86_64/cuda-rhel8.repo
dnf -y install vespa-onnxruntime-cuda

vespa clone simple-semantic-search myapp && cd myapp
vespa deploy --wait 300

Hi.
Please look at the output of vespa-logfmt executed from within your container. It should give some indications of what is failing. If that does not indicate what needs to be done, attach the log here, and we can give you a helping hand.

vespa.log
here is an example of a log from one of the unsuccessful deployments. In variably, there is an error where libcublasLt.so.12 cannot be found. That file is installed on the machine. But it is also not listed in the /etc/cdi/nvidia.json file where it looks like a lot of similar files are essentially mapped from the machine into the container.

After reproducing this today, I have found that the CUDA library the container tries to load depends on the driver/CUDA version on the host. I reproduced your problem on Ubuntu 22.04, running with the latest Nvidia driver. If I installed an older one (version < 525) it loaded the installed CUDA library in the container (which is major version 11).
After that, I got some CUDNN initialization problems I could not solve. But I am unsure if that is some local problem on my setup or other incompatibilities between host and container.
You can give the driver downgrade a try, but keep in mind that we are testing this setup on RHEL 8 derivates, and if you can, I would advise you to try the same if you keep running into problems with the Ubuntu host / CentOS container setup.
We have tested the steps documented on https://docs.vespa.ai/en/vespa-gpu-container.html, and if you follow them, we can better provide help if any of the steps fail.

We're working on a new AMI with RHEL8 as of today. Will keep you updated on progress. Not sure which driver to install. I presume that the instructions at https://docs.vespa.ai/en/vespa-gpu-container.html dnf module install -y --enablerepo cuda-rhel8-x86_64 nvidia-driver:latest are not correct? I believe I want to install this one https://www.nvidia.com/download/driverResults.aspx/200618/en-us/ based on the G4dn instance having a Tesla T4 according to https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/install-nvidia-driver.html

We are currently running with version 530, which will support all available NVIDIA GPUs on AWS, according to the link you pasted.

Version 530 of the Nvidia driver? That is CUDA 12. We setup on Friday with RHEL8 on an AMI with a CUDA 11 compatible Nvidia driver version (470 if I recall, currently away from keyboard) and then got a version compatibility error (between container toolkit and driver). We worked through that only to get the same libcublasLt.so.12 error in the container log.
Can vespa please provide detailed step-by-step end-to-end instructions of a fresh installation starting from of Nvidia driver, podman, CUDA and container toolkit etc. We have sunk a lot of time trying but the guide on your webpage is not reproducible, even with podman and RHEL. For example, the way the device is specified in the podman run command ( --device nvidia.com... ) throws syntax errors.

I am following this up with other people on the team. Looks like there are multiple changes with newer versions of both driver and other libraries which is causing the current guide to fail.
I have been able to reproduce several of the issues you are seeing. We will get back to you with an updated guide as soon as we can.

Hi
We now have a script that does all the required configuration of a RHEL8 host to give Vespa access to the GPU inside a container. The script uses podman, which we have tested with, and not docker to run the container.
Can you give it a try?
https://gist.github.com/ean/6f485303045cfeb553bf6fdb93bf6570
This script will create a new container image with the required ONNX packages tagged with vespaengine/with-cuda, you can use that instead of manually installing vespa-onnxruntime-cuda after starting the container.
The libcublasLt.so.12 issue inside the container was related to acudnn package with a dependency on major 12 version of libcublasLt. Hence the exact version specification of libcudnn8-<IP_ADDRESS>-1.cuda11.8. The rest of the changes are configuration changes on the host.
We will also update the GPU documentation to include all required steps.

Great news, I will try it out soon and report back. Thanks.

podman run --device nvidia.com/gpu=all --detach --name vespa --hostname vespa-pod1 -p 8080:8080 -p 19071:19071 vespaengine/with-cuda
Error: setting up CDI devices: unresolvable CDI devices nvidia.com/gpu=all

We used --gpus all instead
The
vespa_ctr.log
log is attached

It looks like the shell script does actually exited prematurely (possibly at the step checkrun nvidia-modprobe?) and failed to even create the /etc/cdi directory, which could explain downstream issues. I'm trying to follow the subsequent steps in the script now, but 'nvidia-frontend' is not in /proc/devices

If nvidia-modprobe then the nvidia driver likely failed to load, that should also explain why nvidia is not presnet in /proc/devices.
You can try to run sudo modprobe nvidia, or reboot the host to retry the attempt at loading the driver. If there are still problems journalctl might give you some indication of the problem.
Btw, we have now added the script above, and one for RHEL9 to our docker-image repository: https://github.com/vespa-engine/docker-image/tree/master/experimental . These will be kept up to date as we work on documenting the GPU usage properly.

@stauntonjr - did you make any progress on this?
We have updated our documentation to contain all required steps, including some notes of things to verify to ensure everything is configured correctly.
https://docs.vespa.ai/en/vespa-gpu-container.html

Resolving this due to inactivity.


Fix multistart optimizer.py number of trials

Fixes #106

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

I am making a new pull request!


help with 2G limit

Hi, first thanks for this code.
I am using it in a 64 bit Linux, but I can't seem to get past a 2G limit when initializing the Env.
        env = new Env();
        env.setMapSize((long)(1024 * 1024 * 1024 * 1.99999));
        env.setMaxDbs(15);
        env.open(home, FIXEDMAP | WRITEMAP);

Any clues?
Can you guys help?
My dependency is:
      <dependency>
        <groupId>org.deephacks.lmdbjni</groupId>
        <artifactId>lmdbjni-linux64</artifactId>
        <version>LATEST</version>
      </dependency>

looks like it's a lmdb alone or my env.


add more to paired t test & editorial changes

Added more details to paired sample t-test (assumptions to not violate)
Changed the wording on hypothesis
Deleted repetitive parts 'questions to consider' which are actually made into the main survey questions
Minor editorial changes

Thanks for updating, @K3ra-y! :)
I'll merge your PR


Authoring Guide

Create draft pages with all our blocks (including auto blocks) to show authors what content could look like and make it easy for them to copy into whatever they are working on.

First Draft of the authoring guide : https://main--merative--hlxsites.hlx.page/drafts/authoring-guide

closing this for now. Will update the authoring guide during every phase of the project.


integrate news column in menu

Just an idea, this works nicer for narrow screens.
You can see a preview here https://dlang.dawg.eu/.

BTW, would be nice if the forum iframes were available over https.

BTW, would be nice if the forum iframes were available over https.

Both dlang.org and forum.dlang.org use self-signed certificates. The iframes will probably work via https if you first go to forum.dlang.org and accept the self-signed certificate.

Let's please not make the navigation even wider for all pages.

Is this necessary, considering the average viewport size? Over 93% of people use a resolution over 1280px wide according to this.

Lots of programmers use their monitor in vertical mode. We could do this with a media query, depending on the available width.

OK. The other side of the coin is that this puts the news "below the fold", and I'm not sure if additional media queries are worth it from the complexity perspective. But we can get a third opinion.

Let's ask @aG0aep6G who did #886.

It looks a bit weird, clutters the menu and makes it fatter and generally looks a bit unbalanced.
So I'll close this, still would like to see a good idea how to not squeeze the main content.
In general it seems like we should clean up the index, the example is horrible and the important main points are drown in details.
A brief paragraph and fanouts to http://dlang.org/convenience, http://dlang.org/power, and http://dlang.org/efficiency might work much better.


Fix unused_doc_comments lint errors

(cherry picked from commit 628fbdf9b7a831a35e948abdb97f72f071c79ba5)

Not even worth merging because it breaks on rustfmt check for this repo, but the command I learned today is interesting.
git cherry-pick -x --strategy=subtree -Xsubtree=library/portable-simd {commit_ref}


Wrap calls to time.Now in order to help in writing tests.

Risk: quality of life improvement, saves us time.
Ruby e2e tests will fail depending on the time of day they are run.
This introduces a risk regarding late night changes to the system getting blocked in CI because of failing ruby tests.
Wrapping time.Now so we can inject our own time into tests would allow us to have tests that run consistently regardless of the time of day.
AC:

[ ] Wrap all instances of time.Now that get's injected into the function
[ ] Write tests to use a consistent time

The priority for this feature just increased as one of the reasons that #428 occured was due to the time based nature of the algorithm.
This made writing tests for it difficult and so they weren't good enough.
This should be done ASAP this will help with tests.

The priority for this feature just increased as one of the reasons that #428 occured was due to the time based nature of the algorithm.
This made writing tests for it difficult and so they weren't good enough.
This should be done ASAP this will help with tests.


Jwt support

Did not mean to do this sorry, thought this was isolated on my fork (new to this sorry)


[BUG] Fixing UI of signup page

Description
the current signup page has unwanted horizontal and vertical scroll
Screenshots

Any additional information?
No response
What browser are you seeing the problem on?
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I'm a GSSoC'24-Extd contributor
[X] I'm a Hacktoberfest'24 contributor
[X] I am willing to work on this issue (optional)

###Description
The current page lacks animation effect on Sign up page, it only change to blue color when someone hover on it, I have added 3D Hover effect on Sign Up page when someone hover on it .
###Recordings
https://github.com/user-attachments/assets/6c541871-26d0-45c0-a1f0-43d82cd1bc08
I would like to work on it.
@YadavAkhileshh Please assign me this issue i want to change the sign up page with 3D animation .


PDF/A-3 support

There is missing support for PDF/A-3. Required attribute AFRelationship of attached file is missing.

3.2 PDF/A-3’s restrictions
PDF/A-3, which introduced Associated Files to PDF in 2012, imposes some additional
requirements that are not present in PDF 2.0:
• PDF/A-3 excludes external file references, so associations can be specified only for
embedded files
• Since PDF/A-3 requires the AF entry for all embedded files, each file’s MIME-type is
always required
• PDF/A-3 requires every embedded file to be an Associated File and thus requires
the AFRelationship entry in each case
• The list of objects for which the AF entry may be present is explicitly open in PDF
2.0 and an AF entry may be used anywhere in a PDF file. However, in PDF/A-3 this
list is closed and the AF entry may only be present in the locations explicitly
identified in the standard.
• PDF/A-3 has - similar to the list defined in PDF 2.0 - a list of possible objects in
which the AF entry may be present (ISO 19005-3, Table E.1). However, the list in
PDF/A-3 lacks the DPart entry

There is no expectation of qpdf supporting PDF/A-3. It is the intention that qpdf preserve PDF/A on a file that already supports it. Is there a situation in which qpdf is breaking PDF/A-3 on a file that already has it?

Yes when you will try to add an attachment to the PDF/A-3 file. PDF is invalid after this operation.

This is not likely to be fixed anytime soon. When I say qpdf preserves PDF/A, I mean that it preserves it when just rewriting files, not when mutating them with operations like adding attachments. Basically qpdf has no PDF/A support at this time. I would hope that if you added an attachment with a tool that had PDF/A awareness and then transformed the file with qpdf, the file would remain in compliance.

I, too, wish it were possible to add PDF/A-3 compliant attachments with qpdf. I can currently use the qpdf cli for most of my PDF manipulation tasks except this one thing where it seems (I'm not familiar with the format, so of course, it might in reality be supercomplicated) the only thing missing is being able to set the AFRelationship tag properly.

If someone would like to investigate what is required and it turns out to be simple, it is more likely that it would get squeezed in.

Does this document help? https://pdfa.org/wp-content/uploads/2018/10/PDF20_AN002-AF.pdf
3.1 General
In PDF 2.0, Associated Files require:
• at least one AF entry in a PDF object (which can be the catalog if the AF entry
relates to the whole PDF)
• an AFRelationship entry in the file specification dictionary specifying the nature of
the relationship between the PDF (or a PDF object), and the related content. This
entry is required to contain one of the values defined in PDF 2.0: Source, Data,
Alternative, Supplement, EncryptedPayload, FormData, Schema or Unspecified.
Custom values may be used where none of these entries is appropriate.
For embedded Associated Files, the following requirements also apply:
• a MIME type (as defined in RFC 8118) must be specified in the Subtype entry of the
embedded file stream dictionary
• if the (recommended) Params entry is present, it shall specify the latest
modification date of the embedded file.
Referenced Associated Files are permitted, but in almost all contexts, only embedded files
make sense.
3.2 PDF/A-3’s restrictions
PDF/A-3, which introduced Associated Files to PDF in 2012, imposes some additional
requirements that are not present in PDF 2.0:
• PDF/A-3 excludes external file references, so associations can be specified only for
embedded files
• Since PDF/A-3 requires the AF entry for all embedded files, each file’s MIME-type is
always required
• PDF/A-3 requires every embedded file to be an Associated File and thus requires
the AFRelationship entry in each case
• The list of objects for which the AF entry may be present is explicitly open in PDF
2.0 and an AF entry may be used anywhere in a PDF file. However, in PDF/A-3 this
list is closed and the AF entry may only be present in the locations explicitly
identified in the standard.
• PDF/A-3 has - similar to the list defined in PDF 2.0 - a list of possible objects in
which the AF entry may be present (ISO 19005-3, Table E.1). However, the list in
PDF/A-3 lacks the DPart entry (since DPart was only defined in PDF/VT when
PDF/A-3 was developed).

@warpspin Sorry for the delayed response. This is very helpful. It doesn't look trivial though, so it will have to stay on the backlog until someone has time to work it. Thanks for this though -- it is a big help.


AppService Create WebApp Failed

The AppService has Deploy Succeeded,But when Cresate new web app,then failed with "websitesextesion extendsion failed to load

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

ID: 26ee2047-e51e-cf36-1bde-6919b2c5f3cf
Version Independent ID: c4e207d0-be8b-8096-52ad-04e0d029d1e2
Content: Deploy App Services: Azure Stack
Content Source: articles/azure-stack/azure-stack-app-service-deploy.md
Service: azure-stack
GitHub Login: @apwestgarth
Microsoft Alias: anwestg

Thanks for the feedback! Can you please share the documentation you are referring to?

The document I refer to is this link      https://docs.azure.cn/zh-cn/azure-stack/
other,the asdk's version we depoly is 1802,the appservice version is 1.2

another in this document https://docs.azure.cn/zh-cn/azure-stack/azure-stack-app-service-deploy ,in the step Verify the application service installation on Azure Stack,the document said in the admin portal can open the appservice portal,but when i open,there is nothing,

when create a web app ,i got this alert "WebsitesExtension extension failed to load   "

@wploevyaya2018 We are now suggesting users to apply the 1804 update before using the 1.2 app service. Can you please install the latest update and try this process again?
Also, what extension are you trying to install?

@wploevyaya2018 Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly reopen the issue and continue the discussion.


ready: Add option to enable envoy readiness endpoint from worker

/ready endpoint used by emissary is using the admin port (8001 by
default).
This generates a problem during config reloads with large configs as the
admin thread is blocking so the /ready endpoint can be very slow to
answer (in the order of several seconds, even more).
The problem is described in this envoy issue:
https://github.com/envoyproxy/envoy/issues/16425
This change is trying to fix the /ready endpoint problem.
The /ready endpoint can be exposed in the worker pool by adding a
listener+ health check http filter.
This way, the /ready endpoint is fast and it is not blocked by any
config reload or blocking admin operation as it depends on the worker
pool.
Future changes will allow to use this endpoint with diagd and the go
code as well so they get a fast /ready endpoint and they do not use the
admin port.
This listener is disabled by default. the config "ready_port" can be used
to set the port and enable this new listener on envoy.
Related Issues
https://github.com/envoyproxy/envoy/issues/16425
Testing
Manual tests
Deployed on a local k8s cluster.

Hi @kflynn
Sorry for the delay, I finally could find some time to do a few fixes and send an updated PR.
I've added code to match the current logging config on this listener.
I've added 3 configs to enable and tune this new feature:
ready_port: -1 # (default to -1 means feature disabled by default) port used by the listener to expose the /ready endpoint
ready_ip: <IP_ADDRESS> # (default to <IP_ADDRESS>) ip to bind
ready_log: true/false # (default to true) logs the hit or not.

Hi @kflynn
I just rebased the PR on top of ambassador 2.1.0
I tested and it works fine.

Sorry, I think I have a small bug due to the latest changes for the python lint.
Working on it.

I found the problem, I'll update the review soon.

PR updated/fixed.
Thanks.

Superseded by: https://github.com/emissary-ingress/emissary/pull/4253


place furnace instant crash

java.lang.NullPointerException: Exception while updating neighbours
at net.minecraft.block.BlockDoor.func_149695_a(BlockDoor.java:337)
at net.minecraft.block.BlockDoor.func_149695_a(BlockDoor.java:371)
at net.minecraft.world.World.func_147460_e(World.java:1087)
at net.minecraft.world.World.func_147459_d(World.java:1023)
at net.minecraft.world.World.func_147444_c(World.java:988)
at pixlepix.auracascade.block.tile.AuraTile.func_145845_h(AuraTile.java:264)
at net.minecraft.world.World.func_72939_s(World.java:2487)
at net.minecraft.world.WorldServer.func_72939_s(WorldServer.java:664)
at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:943)
at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:430)
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:798)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:658)
at java.lang.Thread.run(Thread.java:745)

Yeah, imma need more info on that one ._.

sorry about that
http://pastebin.com/CheCEtTp

I mean, what were you doing to cause the crash? Can it be reproduced in a fresh world? What blocks are next to the furnace.

I'm unable to reproduced this as of right now. But i will let you know when it happens again i reset my world so i don't have the same setup i had previously. Sorry.

Fixed in latest build


cmake does not recognize icpx as a valid compiler

Summary
when running cmake configuration stage, I get the follwing error:
master) tcohen@tcohen:build $ cmake ..
-- The CXX compiler identification is IntelLLVM 2023.0.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - failed
-- Check for working CXX compiler: /opt/intel/oneapi/compiler/2023.0.0/linux/bin/icpx
-- Check for working CXX compiler: /opt/intel/oneapi/compiler/2023.0.0/linux/bin/icpx - broken
CMake Error at /usr/share/cmake-3.22/Modules/CMakeTestCXXCompiler.cmake:62 (message):
The C++ compiler
"/opt/intel/oneapi/compiler/2023.0.0/linux/bin/icpx"

is not able to compile a simple test program.
It fails with the following output:
Change Dir: /home/tcohen/code/oneAPI-samples/DirectProgramming/C++SYCL/DenseLinearAlgebra/simple-add/build/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/gmake -f Makefile cmTC_9dafe/fast && /usr/bin/gmake  -f CMakeFiles/cmTC_9dafe.dir/build.make CMakeFiles/cmTC_9dafe.dir/build
gmake[1]: Entering directory '/home/tcohen/code/oneAPI-samples/DirectProgramming/C++SYCL/DenseLinearAlgebra/simple-add/build/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_9dafe.dir/testCXXCompiler.cxx.o
/opt/intel/oneapi/compiler/2023.0.0/linux/bin/icpx    -MD -MT CMakeFiles/cmTC_9dafe.dir/testCXXCompiler.cxx.o -MF CMakeFiles/cmTC_9dafe.dir/testCXXCompiler.cxx.o.d -o CMakeFiles/cmTC_9dafe.dir/testCXXCompiler.cxx.o -c /home/tcohen/code/oneAPI-samples/DirectProgramming/C++SYCL/DenseLinearAlgebra/simple-add/build/CMakeFiles/CMakeTmp/testCXXCompiler.cxx
Linking CXX executable cmTC_9dafe
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_9dafe.dir/link.txt --verbose=1
/opt/intel/oneapi/compiler/2023.0.0/linux/bin/icpx CMakeFiles/cmTC_9dafe.dir/testCXXCompiler.cxx.o -o cmTC_9dafe
/usr/bin/ld: cannot find -lstdc++: No such file or directory
icpx: error: linker command failed with exit code 1 (use -v to see invocation)
gmake[1]: *** [CMakeFiles/cmTC_9dafe.dir/build.make:100: cmTC_9dafe] Error 1
gmake[1]: Leaving directory '/home/tcohen/code/oneAPI-samples/DirectProgramming/C++SYCL/DenseLinearAlgebra/simple-add/build/CMakeFiles/CMakeTmp'
gmake: *** [Makefile:127: cmTC_9dafe/fast] Error 2

CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
CMakeLists.txt:14 (project)
-- Configuring incomplete, errors occurred!
Version
Latest OneAPI toolkit and samples.
Environment
Ubuntu 22.04
Steps to reproduce
Install Tools kit according to Intel instructions:
https://www.intel.com/content/www/us/en/developer/tools/oneapi/base-toolkit-download.html?operatingsystem=linux&distributions=aptpackagemanager
Download the samples and run cmake config stage.
Observed behavior
cmake config stage fails
Expected behavior
came config stage is successful.

OneSmpl_Team1 working on this

(OneSmpl_Team1)
@tzachicohen
you might fix your "cannot find -lstdc++" error with install the C++ standard library, for example, "sudo apt install libstdc++6 libstdc++-11-dev" on ubuntu


Bitbucket support

Same motivation as GitLab support #313.
Also to track already ongoing efforts in https://github.com/fthomas/scala-steward/compare/master...tjheslin1:bitbucket

As I could see from the discussion in #313 the GitLab work has been based on @tjheslin1 work for Bitbucket. A colleague and I are giving it a try today to base the actual implementation for Bitbucket on @daddykotex work and see how far we will come.

@dpfeiffer Jolly good! Great news. Unfortunately I wasn't able to dedicate more time after my initial start at the problem! @daddykotex has done an excellent job!

@fthomas How do you like to proceed on integrating the generalization of the VCS? While working on this ticket, we encountered that some abstractions (that are tied towards the GitHub API) need to be reworked slightly to be more general and work as well with the Bitbucket API. Before we start to polish the code that we created on Friday it would be great to sort this out. Next week I will give it a try at work.

@dpfeiffer I think it makes the most sense to base your work on the topic/gitlab branch which contains the GitLab support from @daddykotex from #524. That branch already has generalizations for GitHub's and GitLab's API.

@fthomas I based it directly on @daddykotex refactor/vcsalg which is the one you integrated into topic/gitlab, right?
I finished a rough implementation yesterday which i would like to evaluate internally first (first trial runs seemed to work fine) and of course polish (https://github.com/fthomas/scala-steward/compare/topic/gitlab...dpfeiffer:topic/bitbucket)


Add error checking for failed snax-gen make files

This PR adds additional error checking if snax gen fails it terminates the occamygen as early as possible.
The problem arises because it calls a subprocess make -C but even when the make fails, it does not propagate an error toward the occamygen.
This PR adds a fix to it.

@IveanEx do what you told me to do. Try this by removing one config in any cluster config. Then you will see that it terminates early. Unlike without it, the occamygen still proceeds.

LOl talk about irony, it really works no because the header files cannot be generated

This PR needs SNAX cluster fix https://github.com/KULeuven-MICAS/snax_cluster/pull/333

This should work now!

@IveanEx approve?? hehe


OrientDB Adapter

I am pretty new to coding in Python, even at Github is new to me.
Does anyone know if there is a adapter for orientDB?  How can I implement this?

I believe there is not orientDB adapter, by the way, OrientDB looks awesome! To implement you should take a look at chatterbot.adapters.storage.JsonFileStorageAdapter as a example.

@davizucon is correct. There is not currently an adapter for OrientDB but this looks like something that would be awesome to add.

I can come up with many reasons to have a OrientDB adapter.
I better figure out how to do this...seems like this could worth the effort. I will start looking on how JsonFileStorageAdapter works.
I am new to Python so it may take a while....but worth the effort.  Any advice or insight would be appreciated! Thanks!

Hi @Craz3Coyote, I'm now work on integration with SQLAlchemy, instead of specific DB, the main reason have SQLAlchemy dependency is to be database agnostic. BUT OrientDB have a very specific API so, like mongoDB, must have its own  Adapter.

@davizucon I think having a Slack channel sounds like a good idea. I've added one for the project at https://chatterbot.slack.com

@gunthercox  great !!! Can  add my github mail to the team ?

@davizucon I just realized Slack doesn't have support for letting anyone join (each new member has to be explicitly invited). I think Gitter might end up being a better solution because of this.
https://gitter.im/chatter_bot/Lobby

@davizucon  I think together we can probably get it done... just a reminder I am very new to Python and even githhub.  I came from Borland Pascall an C++, I used to write real time day trading apps based on satellite many years ago. I decided to get up to speed with python by using this project as I have a lot of time on my hands. I am a disabled retired U.S. Navy.  So, if you can bear with me getting up to speed... I am more then willing to spend my time on Gunthercox awesome work and help.

@Craz3Coyote, Sure! we all learning here, don't worry about speed, the constant help is more important.
@gunthercox You are right. No problem, but I made a bot using slack Add Bot To Slack  now its off line. But will be on-line soon. Would be great letting this bot be tested by us.

Sounds good to me... I will start putting effort in orientDB and then I'm planning on filling it with data.  I'm currently adding dragonfly connected to nuance speech to ChatterBot.

What API should I go with? Tinkerpop?

Hi @Craz3Coyote , I think Tinkerpop is written in Java, I dunno if Tinkerpop act as server or as client library embed in.
If Tinkerpop running as a server, I think the effort writing to Tinkerpop or OrientDB will be the same, it`s just a matter of knowing API calls for both.
I believe if you write an adapter, especific for OrientDB, then you will be more familiar with chatterbot structure and writing for Tinkerpop should be straightforward. Sorry I dnt know well how Tinkerpop works.
Best


Project description
farge is command line tool to select pixel on the screen and return the value of the color in either HEX or RGB format. The color code is automatically saved to the clipboard. If you want to save the color, farge is able to show the color in a image viewer with the color code on it. This tool is able to use a varaiety of image viewers like feh, mpv, nsxiv and sxiv. This tool works on X11 and Wayland.
Metadata

homepage URL: https://github.com/sdushantha/farge
source URL: https://github.com/sdushantha/farge
license: MIT License
platforms: linux

nvm, there is already a PR on it. i search in the issue if there were already an issue about farge but i didn't search in the PR


support exporting an image to Docker

Signed-off-by: Akihiro Suda<EMAIL_ADDRESS>

Thanks!!!


Unable to find an entry point named ‘OrtGetApiBase’ in DLL ‘onnxruntime’

I am sorry that VS2019 give me such a reponse when I finally locate it in here:

Could you help me anyway?

I am using .Net framework 4.7.2, and I installed it from NuGet Package Manager with Microsoft.ML.OnnxRuntime 1.8.1

@cross-hello can't reproduce, just created 4.7.2 Console App (https://i.imgur.com/dnD6VLn.png). Installed the Yolov5Net 1.0.2 package from Nuget (check latest version https://www.nuget.org/packages/Yolov5Net/1.0.2), and It works. No need to install OnnxRuntime it comes with Yolov5Net package.

@cross-hello try to debug this https://drive.google.com/file/d/1k_I7gekUdWqnZoluBkwyohVi0i8K_kHk/view

@cross-hello ok, after restoring packages it doesnt copy onnxruntime.dll look at this https://github.com/microsoft/onnxruntime/issues/1699 it's known issue, you may copy always dll from packages folder (...\packages\Microsoft.ML.OnnxRuntime.1.8.1\runtimes\win-x86) or specify platform (x64, x86) as described.

Thanks for your reply, it is sorry that I may no some familar with C sharp platform. It is still a time for us= - =
Thank you


Issues with 'az network dns zone delete'

Issues with 'az network dns zone delete':

Description text must give much stronger warning.  "Deletes a DNS zone from a resource group.  All DNS records within the zone will also be deleted.  WARNING: This operation cannot be undone."
Given the potential impact of a mistake, this command ideally should include a confirmation prompt (plus --force parameter to suppress the prompt).
As with 'az network dns zone create' the CLI should not care about the presence or otherwise of terminating dots on the zone name.  Replace with "The name of the DNS zone, for example 'contoso.com'."  If the user provides a terminating dot, then just silently drop it before calling the service.
Supporting If-None-Match makes no sense for a delete operation. Remove.

add short summary
remove if-none-match

Discussion:
Why should #3 logic be in CLI and not service side?

Re #3, as discussed with Jason, this needs to be client side


Microk8s + Multipass (LXD+network bridge) launch fails at system startup

I'm going to post here the same issue (#2452) I opened in canonical/multipass.
Describe the bug
Multipass fails to start (possibly due to network issues) at system startup:
To Reproduce

I've created two multipass instances in this way:

:~# sudo snap install multipass
:~# sudo multipass set local.driver=lxd
:~# sudo snap install lxd
:~# snap connect multipass:lxd lxd

:~# multipass launch --network eno1 --name master -m 2G
:~# multipass launch --network eno1 --name worker -m 2G

Then I've installed in each instance a k8s single-node with microk8s:
:~# multipass shell master

# disable apparmor since it seems to interfere with microk8s (if not well configured)
:~# sudo systemctl disable --now apparmor.service

:~# sudo snap install microk8s --classic
:~# sudo usermod -a -G microk8s $USER
:~# sudo chown -f -R $USER ~/.kube
:~# newgrp microk8s

:~# microk8s enable dns dashboard storage

# then, same procedure in the second instance but joining the first microk8s node as worker
:~# multipass shell worker
[...]
:~# microk8s join <IP_ADDRESS>:25000/7c920ce61797b78f8796449dbc03dc3c/bd6bdd702477 --worker

Everything works fine until I shutdown or reboot the host system: sudo halt -p or sudo reboot now

When I start again the host, I get this error:

:~#  multipass ls
list failed: cannot connect to the multipass socket
Please ensure multipassd is running and '/var/snap/multipass/common/multipass_socket' is accessible

I have to start it manually:

:~# sudo systemctl start snap.multipass.multipassd.service

This error seems to corrupt microk8s installations since I'm not able to start the master node:

:~#  microk8s status
microk8s is not running, try microk8s start
:~#  microk8s start
Started.
:~# microk8s status
microk8s is not running. Use microk8s inspect for a deeper inspection.
:~# microk8s inspect
Inspecting services
  Service snap.microk8s.daemon-cluster-agent is running
  Service snap.microk8s.daemon-containerd is running
  Service snap.microk8s.daemon-k8s-dqlite is running
  Service snap.microk8s.daemon-kubelite is running
  Service snap.microk8s.daemon-apiserver-kicker is running
  Copy service arguments to the final report tarball
Inspecting AppArmor configuration
Gathering system information
  Copy processes list to the final report tarball
  Copy snap list to the final report tarball
  Copy VM name (or none) to the final report tarball
  Copy disk usage information to the final report tarball
  Copy memory usage information to the final report tarball
  Copy server uptime to the final report tarball
  Copy current linux distribution to the final report tarball
  Copy openSSL information to the final report tarball
  Copy network configuration to the final report tarball
Inspecting kubernetes cluster
  Inspect kubernetes cluster
Inspecting juju
  Inspect Juju
Inspecting kubeflow
  Inspect Kubeflow
Inspecting dqlite
  Inspect dqlite

Building the report tarball
  Report tarball is at /var/snap/microk8s/2948/inspection-report-20220220_153800.tar.gz
:~# grep microk8s /var/log/syslog | grep -i error
Feb 20 15:18:22 master microk8s.daemon-kubelite[4944]: W0220 15:18:22.779467    4944 clientconn.go:1331] [core] grpc: addrConn.createTransport failed to connect to {unix:///var/snap/microk8s/2948/var/kubernetes/backend/kine.sock:12379 kine.sock <nil> 0 <nil>}. Err: connection error: desc = "transport: Error while dialing dial unix /var/snap/microk8s/2948/var/kubernetes/backend/kine.sock:12379: connect: connection refused". Reconnecting...
Feb 20 15:18:23 master microk8s.daemon-kubelite[4944]: W0220 15:18:23.797052    4944 clientconn.go:1331] [core] grpc: addrConn.createTransport failed to connect to {unix:///var/snap/microk8s/2948/var/kubernetes/backend/kine.sock:12379 kine.sock <nil> 0 <nil>}. Err: connection error: desc = "transport: Error while dialing dial unix /var/snap/microk8s/2948/var/kubernetes/backend/kine.sock:12379: connect: connection refused". Reconnecting...
Feb 20 15:18:26 master microk8s.daemon-kubelite[4944]: W0220 15:18:26.512843    4944 clientconn.go:1331] [core] grpc: addrConn.createTransport failed to connect to {unix:///var/snap/microk8s/2948/var/kubernetes/backend/kine.sock:12379 kine.sock <nil> 0 <nil>}. Err: connection error: desc = "transport: Error while dialing dial unix /var/snap/microk8s/2948/var/kubernetes/backend/kine.sock:12379: connect: connection refused". Reconnecting...
Feb 20 15:18:27 master microk8s.daemon-kubelite[4944]: W0220 15:18:27.889640    4944 clientconn.go:1331] [core] grpc: addrConn.createTransport failed to connect to {unix:///var/snap/microk8s/2948/var/kubernetes/backend/kine.sock:12379 kine.sock <nil> 0 <nil>}. Err: connection error: desc = "transport: Error while dialing dial unix /var/snap/microk8s/2948/var/kubernetes/backend/kine.sock:12379: connect: connection refused". Reconnecting...
Feb 20 15:18:34 master microk8s.daemon-kubelite[4944]: W0220 15:18:34.318968    4944 clientconn.go:1331] [core] grpc: addrConn.createTransport failed to connect to {unix:///var/snap/microk8s/2948/var/kubernetes/backend/kine.sock:12379 kine.sock <nil> 0 <nil>}. Err: connection error: desc = "transport: Error while dialing dial unix /var/snap/microk8s/2948/var/kubernetes/backend/kine.sock:12379: connect: connection refused". Reconnecting...

I have to remove the microk8s snap package and reinstall it from scratch.

The errors in the logs (see below) are mostly related to network issues. I've already verified that those urls are reachable from within the instance with curl.

Expected behavior
After reboot or startup multipass should be up and running, also microk8s should be able to start consequently with no issues.
Logs
From the system logs I can see the following log messages:
journalctl -eu snap.multipass*
Feb 20 14:55:52 hpprodesk400g1 multipass.multipassd[1903]: [error] [daemon] Caught an unhandled exception: Remote "" is unkno>
Feb 20 14:55:52 hpprodesk400g1 systemd[1]: snap.multipass.multipassd.service: Main process exited, code=exited, status=1/FAIL>
Feb 20 14:55:52 hpprodesk400g1 systemd[1]: snap.multipass.multipassd.service: Failed with result 'exit-code'.
Feb 20 14:55:52 hpprodesk400g1 systemd[1]: snap.multipass.multipassd.service: Scheduled restart job, restart counter is at 5.
Feb 20 14:55:52 hpprodesk400g1 systemd[1]: Stopped Service for snap application multipass.multipassd.
Feb 20 14:55:52 hpprodesk400g1 systemd[1]: Started Service for snap application multipass.multipassd.
Feb 20 14:55:52 hpprodesk400g1 multipassd[1962]: Cannot retrieve headers for https://cdimage.ubuntu.com/ubuntu-core/16/stable>
Feb 20 14:55:52 hpprodesk400g1 multipassd[1962]: Could not update manifest: failed to download from 'https://cdimage.ubuntu.c>
Feb 20 14:55:52 hpprodesk400g1 multipassd[1962]: Cannot retrieve headers for https://cloud-images.ubuntu.com/buildd/releases/>
Feb 20 14:55:52 hpprodesk400g1 multipassd[1962]: Could not update manifest: failed to download from 'https://cloud-images.ubu>
Feb 20 14:55:52 hpprodesk400g1 multipassd[1962]: Error getting https://codeload.github.com/canonical/multipass-workflows/zip/>
Feb 20 14:55:52 hpprodesk400g1 multipassd[1962]: gRPC listening on unix:/var/snap/multipass/common/multipass_socket, SSL:on
Feb 20 14:55:52 hpprodesk400g1 multipassd[1962]: Cannot retrieve headers for https://cdimage.ubuntu.com/ubuntu-core/16/stable>
Feb 20 14:55:52 hpprodesk400g1 multipassd[1962]: Could not update manifest: failed to download from 'https://cdimage.ubuntu.c>
Feb 20 14:55:52 hpprodesk400g1 multipassd[1962]: Cannot retrieve headers for https://cloud-images.ubuntu.com/buildd/releases/>
Feb 20 14:55:52 hpprodesk400g1 multipassd[1962]: Could not update manifest: failed to download from 'https://cloud-images.ubu>
Feb 20 14:55:52 hpprodesk400g1 multipassd[1962]: Cannot retrieve headers for https://cdimage.ubuntu.com/ubuntu-core/16/stable>
Feb 20 14:55:52 hpprodesk400g1 multipassd[1962]: Could not update manifest: failed to download from 'https://cdimage.ubuntu.c>
Feb 20 14:55:52 hpprodesk400g1 multipassd[1962]: Cannot retrieve headers for https://cloud-images.ubuntu.com/buildd/releases/>
Feb 20 14:55:52 hpprodesk400g1 multipassd[1962]: Could not update manifest: failed to download from 'https://cloud-images.ubu>
Feb 20 14:55:52 hpprodesk400g1 multipass.multipassd[1962]: [error] [daemon] Caught an unhandled exception: Remote "" is unkno>
Feb 20 14:55:52 hpprodesk400g1 systemd[1]: snap.multipass.multipassd.service: Main process exited, code=exited, status=1/FAIL>
Feb 20 14:55:52 hpprodesk400g1 systemd[1]: snap.multipass.multipassd.service: Failed with result 'exit-code'.
Feb 20 14:55:53 hpprodesk400g1 systemd[1]: snap.multipass.multipassd.service: Scheduled restart job, restart counter is at 6.
Feb 20 14:55:53 hpprodesk400g1 systemd[1]: Stopped Service for snap application multipass.multipassd.
Feb 20 14:55:53 hpprodesk400g1 systemd[1]: snap.multipass.multipassd.service: Start request repeated too quickly.
Feb 20 14:55:53 hpprodesk400g1 systemd[1]: snap.multipass.multipassd.service: Failed with result 'exit-code'.
Feb 20 14:55:53 hpprodesk400g1 systemd[1]: Failed to start Service for snap application multipass.multipassd.
Feb 20 14:57:03 hpprodesk400g1 systemd[1]: Started snap.multipass.multipass.bcdca010-e090-46c6-b0cf-dec49ccb58aa.scope.
Feb 20 14:57:03 hpprodesk400g1 systemd[1]: snap.multipass.multipass.bcdca010-e090-46c6-b0cf-dec49ccb58aa.scope: Succeeded.
Feb 20 14:58:03 hpprodesk400g1 systemd[1]: Started snap.multipass.multipass.ab72f737-6f63-4689-93a8-d7ff43cd646a.scope.
Feb 20 14:58:03 hpprodesk400g1 systemd[1]: snap.multipass.multipass.ab72f737-6f63-4689-93a8-d7ff43cd646a.scope: Succeeded.

Plase, find attached the report file produced by microk8s inspect.
inspection-report-20220220_153800.tar.gz
Additional info

Host System info:

OS: Ubuntu 20.04 focal
Kernel: x86_64 Linux 5.4.0-100-generic
Shell: bash 5.0.17
Disk: 22G / 108G (21%)
CPU: Intel Core i5-4590T @ 4x 3GHz [41.0°C]
RAM: 1191MiB / 15935MiB
Netplan renderer: NetworkManager

multipass version:

multipass   1.8.0
multipassd  1.8.0

multipass info --all:

Name:           master
State:          Running
IPv4:           <IP_ADDRESS>
                <IP_ADDRESS>
Release:        Ubuntu 20.04.3 LTS
Image hash:     c7ae471b637a (Ubuntu 20.04 LTS)
Load:           0.36 0.34 0.21
Disk usage:     4.5G out of 9.5G
Memory usage:   216.9M out of 1.9G
Mounts:         --

Name:           worker
State:          Running
IPv4:           <IP_ADDRESS>
                <IP_ADDRESS>
Release:        Ubuntu 20.04.4 LTS
Image hash:     c7ae471b637a (Ubuntu 20.04 LTS)
Load:           0.29 0.13 0.05
Disk usage:     3.5G out of 9.5G
Memory usage:   220.4M out of 1.9G
Mounts:         --

multipass networks:

Name     Type      Description
br-eno1  bridge    Network bridge with eno1
eno1     ethernet  Ethernet device
mpbr0    bridge    Network bridge for Multipass

Additionaly, I would like to add that the very same configuration is working like a charm on my laptop (running Kubuntu), although failing this way at startup on my mini pc (running Ubuntu Server). The only big difference is that I switched from networkd to NetworkManager as netplan renderer in the mini pc (as described here). Maybe this messed up something?

I was ignoring the simple fact that the two instances of the cluster need to have a static ip:

so I appended a static ip to "addresses" in /etc/*-config.yaml file of each Multipass instance

network:
  version: 2
  renderer: networkd
  ethernets:
    ens3:
      dhcp4: yes
      addresses:
      - <IP_ADDRESS>/24

and then use this static ip joining the two nodes with microk8s add-node

Unfortunately multipassd still fails to start at boot time although lxc list --project multipass shows both instances up and running:
:~$ lxc list --project multipass
To start your first instance, try: lxc launch ubuntu:20.04

+--------+---------+----------------------------+------------------------------------------------+-----------------+-----------+
|  NAME  |  STATE  |            IPV4            |                      IPV6                      |      TYPE       | SNAPSHOTS |
+--------+---------+----------------------------+------------------------------------------------+-----------------+-----------+
| master | RUNNING | <IP_ADDRESS> (enp6s0)      | fd42:84eb:c2cd:ff6e:5054:ff:feb9:446b (enp5s0) | VIRTUAL-MACHINE | 0         |
|        |         | <IP_ADDRESS> (enp5s0)     |                                                |                 |           |
|        |         | <IP_ADDRESS> (enp5s0)       |                                                |                 |           |
|        |         | <IP_ADDRESS> (vxlan.calico) |                                                |                 |           |
+--------+---------+----------------------------+------------------------------------------------+-----------------+-----------+
| worker | RUNNING | <IP_ADDRESS> (enp6s0)      | fd42:84eb:c2cd:ff6e:5054:ff:feb4:b3a3 (enp5s0) | VIRTUAL-MACHINE | 0         |
|        |         | <IP_ADDRESS> (enp5s0)     |                                                |                 |           |
|        |         | <IP_ADDRESS> (enp5s0)       |                                                |                 |           |
|        |         | <IP_ADDRESS> (vxlan.calico) |                                                |                 |           |
+--------+---------+----------------------------+------------------------------------------------+-----------------+-----------+


DNS resolution fails on all but one node

Description
I run a 3 node cluster and have installed the HA tech preview like so:
sudo snap install microk8s --classic --channel=latest/edge/ha-preview

After having the nodes join the cluster with the join token obtained with microk8s add-node -l -1 on node 1 and enabling the DNS addon with microk8s enable dns I noticed that all pods scheduled to run on nodes 2 and 3 are unable to do DNS resolution.
I've tried restarting the services, the nodes, resetting, uninstalling + resetting etc.
All pods running on the first node work as expected. There's no apparent issue when running microks inspect.
The only odd thing about my setup is that node 3 is a Raspberry Pi 4 on Ubuntu 20.04 (ARM64) while nodes 1 and 2 are bog-standard AMD64 hosts (Fedora Server 32). But the issue happens for both one of the AMD64 and the ARM64 host.
Additional information
Test procedure
To test this issue I pinned a pod to a specific host with the following (example for "node 3"):
apiVersion: v1
kind: Pod
metadata:
  name: test-deleteme-pi48
  labels:
    env: test
spec:
  containers:
  - name: test
    image: ubuntu
    imagePullPolicy: IfNotPresent
    command: ["/bin/bash"]
    args: ["-c", "sleep infinity"]
  nodeSelector:
    kubernetes.io/hostname: pi48

microk8s inspect
Node 1:
inspection-report-20200820_115425.tar.gz
Node 2:
inspection-report-20200820_115522.tar.gz
Node 3:
inspection-report-20200820_115633.tar.gz

I found the culprit: docker 🤦
Stopping docker.service on all nodes did the trick.
Maybe this should be added to the documentation.

Im running docker with a single node microk8s, never gave me problem.  Perhaps there is some container running in docker interfering with it.

On a single host, docker is not interfering.
My bet is on the iptables rules that docker creates. But I don't know for sure.

Thanks @pschmitt 👍

It would have been great to understand how the IP table rules clash.
@pschmitt could you describe the sequence of steps I need to follow to reach your setup and how you recovered the cluster? Did you stop the docker service only? Did you stop containerd service as well? Did you get docker from the distributions repo or from docker? Did you have to restart any services or nodes? Thanks

@ktsakalozos
To get to where I was:

Docker Service enabled on all nodes + Swarm setup (no services deployed though)
Setup microk8s HA cluster

To recover (on all nodes):

sudo systemctl stop docker; sudo systemctl mask docker
microk8s stop; microk8s start

@pschmitt here is the opnened issue https://github.com/ubuntu/microk8s/issues/1511
I hope to have this merged to latest/edge soon.

Will your suggested config work is this case?

It should, yes

Should I add nic prorities at the network manager level?

I do not think this will make any difference.

@pschmitt the patched version is on latest/edge. Would you be able to take it for a test-drive to see if it fixes the connectivity issues you have?

Yup. Will totally do that. I'll try to do this today even - but I am travelling. I'll let you know. Thanks for the quick fix!

Thank you

I finally have some time to test this.
Is the patch only available on the latest/edge channel?

The patch is on latest/edge latest/beta latest/candidate and on the 1.19 track (1.19 all channels).
Thank you.

Okay, then I already tested it. I've redeployed using 1.19/stable and the DNS resolution is working fine inside pods (on any node).
Thanks again!

Thank you on your help fixing this.

I stumbled upon this as I was facing the same issue with nodes in separate networks, reachable over public IP. The can-reach was set correctly automatically. but what helped me was to open all necessary ports in the firewalls, especially 4789/udp.


Usenet sites in 3rd bar

Could you please add an option to place Usenet sites in 3rd bar? Or make it the default behavior if you prefer.

I personally don't see point in such feature, if someone wants to PR it then I don't mind.
PS
Maybe better in same bar but split to a new line with sorting func.

Unfortunately I don't have enough skills to implement it as an option. Hopefully no one will complain.

It should be optional.


Home link in TopBar NodeType should be optional

TopBar NodeType can be used in various ways. When inserted into ContentCollection we can set (or not) home link text through inspector. When this value is empty than link is not generated and this is fine.
Problem is when we define TopBar as a childNode. For example:
'TYPO3.Neos.NodeTypes:Page':
  childNodes:
    navigation:
      type: 'M12.Foundation:TopBar'

now the Home link is always generated because of this condition in TypoScript (Resources/Private/TypoScript/Prototypes/Navigation.ts2):
topBarTitle = ${isDocumentContext ? q(site).property('title') : q(node).property('topBarTitle')}
(page title is always set and we are in Document context).
Maybe some checkbox in element inspector would be a better option do define if we want or not Home link in TopBar?

I'm happy with inspector checkbox. Next PR from you? ;-) If not, I can handle that in the next couple of days.

@ryzy Sure, i can do it :)

OK, after 2nd read/thought:
Why do you insert TopBar via childNodes? It doesn't really make sense - you'll have as many menu instances as pages. You should do that from TS. And you'll hit some other configuration issues anyway with such an approach.
			menu = M12.Foundation:TopBar {
				entryLevel = 1
				topBarTitle >
            }

That works just fine.


It hasn't been updated for years!

Will there be any update for markdown-here? It hasn't been updated for years!

I also wish for an update, but I think @adam-p is busy with his real job (Psiphon). You can buy him a coffee by donating to markdown-here, but I suspect he has scratched his itch on this project. If you need a specific fix, maybe check the pull requests and see if there's a fork that works for you.

@hqgu Just check the actively maintained fork of @jfx2006:
https://gitlab.com/jfx2006/markdown-here-revival
https://addons.thunderbird.net/en-us/thunderbird/addon/markdown-here-revival/

@FroggieFrog  Thank you for your comment. It's weried that no other folks keeping updating it for chrome.

@hqgu Just check the actively maintained fork of @jfx2006: https://gitlab.com/jfx2006/markdown-here-revival https://addons.thunderbird.net/en-us/thunderbird/addon/markdown-here-revival/

Note :

This is a mail extension for Mozilla Thunderbird.
Support for browser-based email such as GMail, Outlook, or Yahoo Mail was
removed to reduce tne necessary ongoing maintenace burden from these platforms.


Add xScience

Hardcoded the author for the original author (Brodrick) and the maintainer (Z-Key Aerospace).

There's a .version file, but I doubt netkan would find it, given the unfortunate file naming.

The version file is broken because it's missing a comma

That, too? Merging with my thanks


Fix core-lro version for purview catalog version

Fix the core-lro version for purview catalog due to the issue https://github.com/Azure/azure-sdk-for-js/issues/23731

API change check
API changes are not detected in this pull request.

Could you please create an issue to undo the pinning once the service fixes the behavior on their end?

https://github.com/Azure/azure-sdk-for-js/issues/23804 Issue tracked.


Not converging in xor calculation task

when i run demo.py notebook provided in this repository, calculating xor task converges.
but when i create and run a custom notebook, it doesnot converge and it is almost 2x slower

Sorry, I am not sure what the issue is, I would recommend using our notebook and codebase though.


ARTEMIS-4259 JMS consumer + FQQN + selector not working

More specifically, auto-created 'topic consumer + FQQN + filter' queues, and expecting that only messages matching that consumers filter will get to the created queue, and ultimately the consumer?
Looks like for Core, it didnt do any filtering at all for the auto-created FQQN+filter case, as neither queue creation or consumer had a filter applied. For AMQP, it looks like the consumers are filtered, but the queue wasnt and thus would get all messages on the address and retain any that dont match the consumer(s) filter(s). If a pre-created queue existed with an appropriate filter, it seems like it would have worked for both.
This change looks like it fixes the auto-creation case, though seems like it would introduce and/or retain some oddities for working with existing queues either pre-defined or previously auto-created (plus may even prevent some niche things that worked before).
For queues that already exist and that either have no filter or have a different filter than a new consumer uses, it doesnt seem like it will be noticed since nothing is done with the queue filter when the queue already exists. For Core that seems like it could mean if the existing queue has no filter it still does no filtering even when its desired it should , and for the mismatched-filters case it might actually filter the 'wrong thing' and again allow non-matching messages to get to the consumer, since it still looks to rely solely on the hopefully-existing-and-hopefully-matching queue filter alone, with no consumer filter put in place at all. For AMQP, it seems it could once again pile up any messages that dont match the new consumers filter for the no-existing-queue-filter case (since it will still get all messages but the consumer will be filtered), and in the mismatched filter case it may not get all messages it 'should' and may pile up unmatched messages again since the queue filter doesnt match the consumers, though at least no 'non-matching' messages would get to the consumer due to its filter (note it will often be double-filtering though since both queue and consumer can have filters).
Its not clear to me what can/should be done about that. Document it and ignore? Check if queue is filtered and throw if there is a mismatch (but that might actually be deliberate for a pre-defined queue filter..)? (For regular JMS durable subs the existing sub is to be seamlessly destroyed and a fresh sub begun when filter changes..same for shared subs, if not currently in use by others).
One thing is this could prevent some existing possible niche behaviours. Previously it seems you could perhaps have had multiple filtered AMQP consumers having different filters pulling from the same FQQN (say, structured such that all messages could be consumed by someone). This will break such things for auto-created usage, since the queue would now be filtered based only on the first/creating consumers filter.  JMS specifically doesnt allow such stuff with regular shared subs though, everyone has to use same filter for this reason.

I found some additional use-cases with JMS queue consumers + FQQN + selector that weren't working as expected so I've fixed those and added a few corresponding tests.
As for the other use-cases you mentioned...I think any use-case involving a pre-created queue with a filter being accessed via FQQN by a client also defining its own filter is extremely rare if in use anywhere at all. It's certainly beyond what is documented and won't work consistently across JMS clients even now.
Generally speaking, in multicast + filtered use-cases the filtering should be done at the queue. In anycast + filtered use-cases the filtering should be done at the consumer. These basic semantics are enforced for non-FQQN use-cases and should be enforced for FQQN use-cases as well. If this breaks undocumented, untested, niche use-cases then that can be addressed in another PR if we deem it necessary.

Any idea when this PR will be merged? Any chance to include in AMQ v7.11.1?

It should be merged before 2.29.0 (upstream). Tomorrow probably.
We can talk internally about redhat releases then.

@jbertram this still in review. but the changes seem ok.. did you run the test?

a new PR was sent to replace this one https://github.com/apache/activemq-artemis/pull/4502


syntax warning in inversion.py

from bayes_drt.inversion import Inverter with python 3.9.16 throws
SyntaxWarning: "is" with a literal. Did you mean "=="?
if outliers is True or outliers is 'auto':
cause it line 1670 of inversion.py

This should also be fixed in the last commit.


AudioEngine names must be lowercase

The name assigned to a file in AudioEngine has to be only lowercase characters (I didn't try any special characters). At least, this is what it looks like to me :p
This isn't a problem, per se, but it should be documented.

There's no reason for this to be the case: The audio "names" are stored in a wren Map, which are case sensitive, so it should work for any case, so long as the string is identical.
I also can't reproduce this, so it might be a bug in Wren.


Why Sparse depth comes from MVS instead of SfM in Code?

Hi,
I found you used COLMAP's MVS pipline in your code to gennerate fused Point Cloud and then get the depth map. But you said you use COLMAP's SfM in your paper (the sparse depth in Fig.2 is also from the MVS instead of SfM). The sparse depth from SfM is actually very sparse. If you use COLMAP's MVS to reconsrtuct the point cloud, the depth from point cloud is already accurate (though a little sparse). So it confused me a lot. Why do you use nerf to generate depth? The Tab. 3 shows the depth from DepthNet is very accurate, the Nerf helps a little. I guess if you use a deeper DepthNet and a better loss you can get a better depth.

Actually, we follow the syntax convention of free view synthesiswe and have said that we acquire per-view sparse depth maps by
projecting the fused 3D point clouds after multi-view stereo. The MVS depth have many noise (See the COLMAP in Table 1) and we need fusion to get sparse but clean depths. To fairly compare, we use the same pretrained depth network with CVD and the 0.16 gap on Abs Rel metric is not marginal.

(1) However, you claimed more than three times that you use SfM' results to train DepthNet in your paper (especially in abstact). How do you explain this problem? I think you can easily distinguish them. But why you said you use SfM? This is very misleading. If you did it on purpose, it will be a big problem.

Using MVS or SfM has a big difference. You said you are handling MVS task, but you run the COLMAP's MVS pipline at first, the following steps (your main contributions) can just be regarded as refinement, right? If you indeed use SfM's sparse depth, this paper will be a nice work, but you didn't.
(2) You only use COLMAP's sparse depth as supervision (bad accuracy in Tab.1) to train DepthNet, but you get much more accurate depth priors from DepthNet(see in Tab. 3). I don't think it makes sense. How did you make it?

(1) However, we think it is also not suitable to substitute "SfM reconstruction" with "MVS reconstruction" because we only use sparse depths after fusion. A alternative one may be the "traditional 3D reconstruction". Thanks for your suggestion and we will update our arcticle.
(2) When evaluating COLMAP, we use all MVS depths. The results indicate that most of MVS depths are noisy and only the sparse depths after fusion are accurate. The traditional MVS methods cannot handle indoor scenes well and we will get many wrong depths. However, our method can tackle the issue, which is not just a refinement.

(1) The keypoint is why you use 'SfM' in paper on purpose (this is important)? We all believe that if you claimed that you use MVS's depth intead of SfM's depth, this paper won't be  accepted, let alone being selected as Oral (The reviewers must unware of the fact that you used MVS).
(2) You said 'we only use sparse depths after fusion'. Actually, the depth after fusion is much more accurate than the depth before fusion. I think that sentence should be 'we even use the accurate depth after fusion'. Further more, you use all depth(before fusion) for evaluating COLMAP, but you use the accurate depth(after fusion) in your method for evaluation. So the experiments is unfair in Tab.1 and Tab.3.
(3) Under the condition that you use MVS as depth priors, I don't understand why Nerf was presented as a key part in your method. We all believed that you are clout-chasing Nerf (蹭热点).
(4) We are in the process of contacting the committee of ICCV2021 and Prof. Lu for further information.


Shortcuts Additions and Fixes

Added windows shortcuts
Fixed a couple linux shortcuts that used cmd instead of `ctrl.

Thanks - awesome!


Wrap Link.call

Currently users directly override Link.__call__.
I propose letting users override, say, Link.call instead, and call it from Link.__call__. It's just like how Function.__call__ works.
This will introduce several benefits (At least I can think of):

Link hooks
Links will be able to be represented hierarchically in graph visualization. (See #2215)

Some candidate method names: call, __call_link__, define, define_link, any other?
Note: This will not break backward compatibility, as existing code (overriding Link.__call__) will just work, but with new features (e.g. link hooks) disabled.

It would be better to provide a context manager method or a decorator that inserts the pre/post processes. It will be used like follows.
def __call__(self, x, ...):
    with self.forward_scope():  # run preprocess in __enter__, and postprocess in __exit__
        h = F.relu(...)
        ...

or
@Link.forward_method
def __call__(self, x, ...):
    h = F.relu(...)
    ...

There are some benefits:

It is straight-forward to understand the actual interface of the link implementation.
There is no extra effort needed to support IDE correctly and provide a documentation that reflects the actual interface.
Users can provide multiple methods that do forward computations for different purposes (e.g. one for computing a loss value and another for inference).

See #2657, too.

"Link hooks" may make ONNX export feature I'm trying to create as Function hooks more easier especially for LSTM-like modules which have multiple Functions inside.

We need to list up possible applications for this feature, then we can start discussing what the interface should be. Any ideas? Here is a list of ideas proposed in the offline discussions (including those that have alread appeared in this issue):

Graph visualization improvement
Link hooks

ONNX export code injection in Link level (e.g. LSTM)
Link-level profiling code injection

I, @bkvogel and @mitmul discussed the interface.
While @beam2d's suggestions above have some advantages, we have a concern that it may be difficult for users (especially those who are novice in Python language) to understand and track the code behind Link.
In the alternative (basically it's the same as the one I proposed above), usual user-defined links look just simple (the method name is borrowed from nn.Module in PyTorch), and complicated things are required only when multiple forward methods are defined.
Usual user-defined link would look like:
def SomeLink(chainer.Link):
    def forward(self, x):
        h = F.relu(x)
        ....

If user wants another forward method (e.g. for predict), user needs to mark it in some way. We didn't come up with particular notation, but there may be some possible ways.
# (1) decorator
def SomeLink(chainer.Link):
    def forward(self, x):
        ....
    @Link.forward_method
    def predict(self, x):
        ...

# (2) manual registration
def SomeLink(chainer.Link):
    def __init__(self):
        self.add_forward_method(self.predict)
    def forward(self, x):
        ....
    def predict(self, x):
        ...

# (3) Via class attribute
def SomeLink(chainer.Link):
    extra_forward_methods = ('predict',)
    def forward(self, x):
        ....
    def predict(self, x):
        ....

# (4) Context manager
def SomeLink(chainer.Link):
    def forward(self, x):
        ....
    def predict(self, x):
        with self.forward_scope():
            ....

etc.
How do you think? @beam2d

I would like to add another use-case for link hooks: Methods such as spectral normalization (https://arxiv.org/abs/1802.05957) would be very easy to implement in a clean manner, since it could be written as a hook that normalizes the weight matrix before the link is called. Currently, it has to be implemented as SpectralNormalizationConvolution2D, SpectralNormalizationLinear, SpectralNormalizationEmbedID, which causes a lot of unnecessary duplicate code, whereas it would be cleaner to just write a single hook that can be applied to any existing link.

I'm not sure if it is relevant or not.
I want to calculate the gradient for link's parameter W and b for each example in minibatch separately.
And I think this feature can be covered if we can get a hook for backward call of function as well.

If there's no objection to the above comment of @niboshi, I'm going to start writing this feature and send a PR soon.

@mitmul
Do you mean (1) decorator?
We didn't discuss these options, but I prefer (2) for explicitness in this case, because it will be rarely used.
And I've come to think (4) is not an option because it cannot distinguish different forward methods.

@niboshi I think replacing __call__ with forward in all Linkss to enable "link hook" feature can be a separate PR from a PR to support multiple forward functions. Can I start to add "link hook" feature first? Then I think we can discuss how to support multiple forward functions.

@mitmul Got it!

Created a PR to add LinkHook feature. https://github.com/chainer/chainer/pull/4730