feat: add kusion module apis for server

What type of PR is this?

/kind feature
What this PR does / why we need it:
This PR adds the implementation of module-related apis for kusion server.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Additional documentation e.g., design docs, usage docs, etc.:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

32 of 302 (10.6%)  changed or added relevant lines in 10 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.6%) to 51.526%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/infra/persistence/util.go
0
3
0.0%

pkg/server/route/route.go
12
15
80.0%

pkg/domain/entity/module.go
0
5
0.0%

pkg/domain/request/module_request.go
0
6
0.0%

pkg/infra/persistence/module_model.go
0
41
0.0%

pkg/infra/persistence/module.go
0
62
0.0%

pkg/server/handler/module/handler.go
10
81
12.35%

pkg/server/manager/module/module_manager.go
0
79
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/infra/persistence/util.go
1
71.62%

Totals

Change from base Build<PHONE_NUMBER>9:
-0.6%

Covered Lines:
10470

Relevant Lines:
20320

💛  - Coveralls


voiceConnection.stopPlaying() throws Error: write EPIPE

Hi. For some reason voiceConnection.destroy() as well as stopPlaying() both throw
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: write EPIPE
    at exports._errnoException (util.js:870:11)
    at Socket._writeGeneric (net.js:681:26)
    at Socket._write (net.js:700:8)
    at doWrite (_stream_writable.js:301:12)
    at clearBuffer (_stream_writable.js:404:7)
    at onwrite (_stream_writable.js:340:7)
    at Socket.stream.onwrite (_stream_writable.js:89:5)
    at WriteWrap.afterWrite (net.js:781:12)

I am calling it like this:
      this.discordClient.voiceConnection.stopPlaying();

The error gets thrown by this.streamProc.stdin in stopPlaying.
Hooking the error event onto it will prevent the entire process from crashing.

what are you passing to playXXX()?

that.discordClient.voiceConnection.playRawStream(stream, { volume: that.currentVolume });

Stream is a raw stream from another library called node-spotify-web. The playback is working perfectly.

Possibly similar to the ytdl error, where the stream still tries to send data to discord.js after discord.js closed its receiving stream.


Purpose of nodeos resource-monitor-not-shutdown-on-threshold-exceeded not clear

in nodeos --print-default-config it says
# Used to indicate nodeos will not shutdown when threshold is exceeded. (eosio::resource_monitor_plugin)
# resource-monitor-not-shutdown-on-threshold-exceeded =

It is not clear what actually this option is doing and what are the acceptable values.
Also, the entire documentation is missing for eosio::resource_monitor_plugin, (issue is https://github.com/EOSIO/eos/issues/9839), so I can't look there either.

2.1.0-rc3


[Thumbnail] BlackNight.com

BlackNight is a domain registrant in Ireland.
Name: BlackNight
Website: blacknight.com
Link to SVG or EPS image:
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" version="1.1" baseProfile="full" width="60px" height="60px" viewBox="0 0 60 60" preserveAspectRatio="xMidYMid meet" id="svg_document" style="zoom: 1; background-color: #000000;">
<path d="M14.6,44 l0.7,-1.6 l1,-1.6 l2.2,-2.5 l1.9,-2.1 l0.9,-1.3 l0.7,-1.3 l0.4,-1.5 v-1.3 L22,29.3 l-0.8,-1.1 l-1.8,0.7 L18.2,29 L17,29 l-1.6,-0.4 l-1.6,-0.6 l-0.8,0.4 l-0.8,0.2 l-2.4,0.8 l-0.6,0.5 l-0.4,1.3 l-0.3,0.6 L8,32 L7.5,32 H6.3 l-1.4,-0.2 l-3.5,-1.5 l-0.6,-0.7 l-0.4,-1.1 l-0.2,-1.4 L0,25.4 L0.1,25 L1,24.1 v-0.9 l11.6,-8.8 v-0.9 l0.3,-0.9 l5.6,-3.5 l-0.2,-0.6 l0.1,-0.4 l0.8,-1.6 V6.2 l-1,-0.5 l-1.1,-0.1 l-0.7,0.1 L15,6.1 l-0.4,-0.2 l0.2,-0.6 l0.3,-0.5 l0.7,-1 l0.5,-0.7 l0.6,-0.5 l1.1,-0.7 l1.7,-0.8 l1.4,-0.4 l1.3,0.8 L23,0.3 l1.6,-0.2 L26.2,0 l1.6,0.1 l1.3,0.2 l2,0.8 L31,2.7 l1.2,-1.2 l1.5,0.6 l2,0.9 L37.1,4 l1.9,1.5 l2,2.3 L41,9 l1.5,-0.1 l1,0.7 l1.9,1.8 l1,1.3 l0.8,1.4 l1,2.3 L46.9,18 l1.6,0.4 L49,20 l0.2,1.7 l0.2,2.4 l-0.1,3.4 l-0.3,3.2 l-1.4,0.9 l1.2,0.9 l-0.3,3.8 l-0.7,2.3 L46,41 l-3.1,3 L14.6,44 " id="path1" fill="#ffffff"></path>
</svg>

Preview:
https://www.blacknight.com/wp-content/themes/blacknight/favicons/android-icon-192x192.png

Icon added. Issue closed.
The new ...F release version will not be uploaded to the Galaxy Store. But you can get it from the release tab as signed .apk (uses the same signature as the Galaxy Store version, hence can be updated without data loss).
Since Samsung changes their requirements for android developers (basically require to be a business), as hobby developer I will not put up with that and not use the store any longer for android apps.
Do you need it in tizotp for a Tizen watch as well? (maybe I can still use the Galaxy Store for non-android apps)


Ctrl+M minimizes the windows in Windows 11 = impossible to select code

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS:windows 11
- Continue:0.9.32
- IDE: vscode 1.85.2
- Ollama 0.1.22

Description
In Windows 11, the standard behavior of the Ctrl-M key is to send the window back. So, it is impossible for me to select code for Continue.
To reproduce

install continue in vscode on a windows 11 machine
open a file containing code and select some lines of code
see the tip saying "^M to select code, ^shift L to edit
hit Ctrl-M and see the window go behind other windows  and not select the code
ask continue to explain the code selected w/ the mouse only and see it answering on some code you've never seen

Log output
No response

Well, after some other trials, I realized that the right key is Ctrl-Shift-M which works so the bug is on the tip itself

@leolivier thanks for sharing this. ctrl-M actually is supposed to do something in Continue as well (selects code and restarts the session). It might be that the only reason we've gone so long without seeing tons of issues opened such as this is that its common for people to use full-screen mode.
Regardless, we're planning on switching up the keyboard shortcuts soon so that there won't be silly conflicts like this one. I'll keep the issue open until we've made the change!

@leolivier Continue now uses ctrl-L instead of ctrl-M


Add Github secret option

This implements a very minor yet powerful change:
Using Github actions workflow, it is possible to define a secret password, then make it accessible as an environment variable that the plugin can use instead of writing the expected password directly in the mkdocs.yml file.
The added description in the README should be pretty straightforward to follow.
Note that this requires a requirements.txt file in order for the Github worker to build the docs.
Note also that I added some minor changes such as flake8 compliance with smaller max line length (100) and  a .gitignore file. Thoses changes are obviously not required.

Hey,
Thanks already for the PR :)
I 100% agree with the idea, for a while I thought that it should integrate a password entry via the env. Good idea.
However, I would like to "normalize" 3 things with respect to your PR.
1- The true|false variable with "PASSWORD" by default which is used for this feature.
I think there must be some environments where this variable could already be used.
I would like to use your "use_secret" variable to, if set, to target the "name" of the environment variable used.
This would allow the user to choose the variable name themselves.
It may also be necessary to add a control of this variable which could (by accident, error) not be defined and lead to the accidental revelation of the encrypted articles. Stopping the build process in this case makes sense to me.
2- The README part, which is very detailed/explicit.
My opinion it's "a bit too much" and very focused on git actions, while some will probably want to do the same with more classic CI/CD pipelines (Jenkins for example).
In order to keep a README as concise as possible, it seems to me more appropriate to only explain how to use of the environment variable, without describing the configuration, setting up a specific case.
3 - The creation of a "requirement.txt" with hard fixed versions.
Probably I should define the compatible versions a little better in my setup.py, but the requirement proposed here is extremely related to your integration environment. This could lead to forcing other users to use these versions (undesirable).
Finally, i don't like formatting lines at 100 char max, it's more complicated to read, but who reads the code?!
So I would do with. Thanks for the scan and corrections. :)
Do you want to make the changes yourself and redo a PR.
Or change the destination branch to "experimental" (which I sync with master now) so that I can make the changes and create a 2.2.0 version?
Thanks for your contribution :)

Hi !
Thanks for your quick reply ! I can do the changes myself and redo a PR. Let me just process your answers to be sure I got it right.
1.a use_secret: boolean to string:
Yes that is obviously a lot better. It's embarrassing I didn't think of that haha.
1.b use_secret being a potential risk:
I'm not sure what you mean ? In which context could it happen ? Let's say I update the lines 157 & 158 of plugin.py to
if self.config['use_secret'] is not None:
    self.config['global_password'] = os.environ[self.config['use_secret']]

How could that be a security issue ? If the secret name doesn't match the use_secret value, that would throw a KeyError because I'm not using the os.environ.get() method.
I agree that this not a good behavior though, and stopping the build process would be better. How would you implement that without requiring anything from the user CI/CD pipeline ?
2. README being to detailed:
I kinda agree but I'm not sure. Do you suggest to only say something like "an environment variable named as use_secret must be set" ? I feel like many users could be interested in using this features without being familiar with any form of CI/CD (I'm a deep learning PhD student, and I can tell you it's a field where lots of people may want to secure their docs without knowing anything about Jenkins or Github actions). That's why i thought something like a minimal working example could be valuable.
3. "requirement.txt" with hard fixed versions:
Yes that's completely my bad, I have some auto API reference generation from docstrings that seem to be pretty sensible to versions, I just forgot to change it before submitting, sorry. How would you like it ? No requirements at all, or loosen up the version, in which case I'm not sure which minimal versions are acceptable ?
4. max line length:
My screen is in portrait format, that's why it was triggering me haha. Do you want me to revert it ? That's no big deal.
Let me know what you think about all that, and I'll do the PR asap.
Thanks !


Setup DataBinder for arguments to access fields with DirectFieldBindingResult

Hello,
just wondering if DataBinder for arguments could be instrumented to use DirectFieldBindingResult instead of BeanPropertyBindingResult?
Now for inputs setters must be exposed which leaks to business layer. kickstart works on direct field access and this produces more elegant approach where arguments are read only for the user code/busines layer.
Thank you.

I'm not sure I'm getting the whole picture here.
Could you give an example of a binding use case that's not supported currently?

Please find it here - https://github.com/ptrbojko/feature-152-spring-grapqhql
Look at the schema and demo.ProjectController.
createProjectWithWorkingInput will work because @Argument'ed class WorkingProjectInput has setters(and DataBinder through BeanPropertyBinding... uses those setters).
createProjectWithBadInput wont work because BadProjectInput has only getters. Setters are not needed in business code and should not been used because input should not be mutable.

Cool! I don't think we want to advertize private members without setters/constructor arguments - this would not be in line with data classes and records anyway. I'll close this issue for now and we can revisit if other use cases are found. Thanks!


Fix to junit timestamp string format:

I'm testing version 2.0.rc11-0 and having an issue with the junit output handler crashing lua.
After a little digging, I found it's related to the call to os.date to format the junit timestamp.  The date format string is '!%Y-%m-%dT%T', however the %T format specifier doesn't seem to be available on my platform. Changing the %T to %H:%M:%S in accordance to the strftime documentation resolves the issue.

Seems reasonable; as an aside, what OS and version of lua are you using?

Sure, my current configuration is this:
OS: Windows 7 x86_64
Compiler: MSVC 2010
Lua: v 5.1.5
Luarocks: v 2.3.0

Thanks mate.
I guess my comment that %T doesn't work on my platform is not technically correct.  It's actually the MSVC 2010 runtime that doesn't support the %T format.  My other configuration using MSVC 2015 does support %T.


Add assistant guidelines markdown for Issue #134

The content looks good, thank you! I did some formatting and renamed the file. One thing to be added to this guide could be a small explanation of the new parameters the assistant now has. These mostly mimic the OpenAI API Parameters as described here: https://platform.openai.com/docs/api-reference/chat/create
Would be nice to have concise descriptions for these so that non-developers get an idea how to tweak the output.

Thanks, the new descriptions are looking good! One last thing that came to my mind: Could you add some more information the the two example workflows based on your experience (i.e., which types of texts work good for generating the entire graph, which ones would require the user to perform the steps individually and correct potential errors). Thank you!


Graph files on zenodo

Hi, thank you again for sharing the code.
I am trying to use the train_model.py script along with the dataset downloaded from https://zenodo.org/record/6623202#.Y0aQwtJBxH4. The files required are not there, e.g. v2020_train_p.bin. Can you help on this?
Thank you in advance,
Pietro

You can find the file at https://zenodo.org/record/6859325#.Y0aU38hPoyg. It is because a updated version has been uploaded when revising the manuscript.

Thank you!


Cache display property for slideDown/fadeIn?

By default, an element's display is set to its native type after a slideDown or fadeIn.
Compare this to jQuery, which caches the initial display value and is able to restore it regardless of whether it started as its native display.
http://jsfiddle.net/darrylyeo/bpf4f1um/3/
Can Velocity achieve a similar functionality, without having to manually override the display on a case by case basis?

Maybe when we first set the display value to "none" it should getComputerStyle the current one if it's not already cached (and only cache the non-"none" value) - not sure what it's doing right, but definitely not that at least ;-)

The ui-pack animations have been rewritten


GS readiness

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/15532/merge
Test environment:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15532/merge/index.html
To test a playground add it to the URL, for example:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15532/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/15532/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/15532/merge
https://gui.babylonjs.com/?snapshot=refs/pull/15532/merge
https://nme.babylonjs.com/?snapshot=refs/pull/15532/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/15532/merge#BCU1XR#0

WebGL2 visualization test reporter:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15532/merge/testResults/webgl2playwright/index.html

Visualization tests for WebGL 1 have failed. If some tests failed because the snapshots do not match, the report can be found at
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15532/merge/testResults/webgl1/index.html
If tests were successful afterwards, this report might not be available anymore.

Visualization tests for WebGPU (Experimental)
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15532/merge/testResults/webgpuplaywright/index.html

Visualization tests for WebGL 1 have failed. If some tests failed because the snapshots do not match, the report can be found at
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15532/merge/testResults/webgl1/index.html
If tests were successful afterwards, this report might not be available anymore.


Update Set-OwnerlessGroupPolicy.md

Chris please review and update accordingly.

Docs Build status updates of commit 5c16e27:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Set-OwnerlessGroupPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit b049546:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Set-OwnerlessGroupPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


jSuites.mask.render error

Hello, we are using the jSuites library in a project of ours, and just today we've lost functionality, and we are seeing the following error:
Uncaught TypeError: jSuites.mask.render is not a function     at Object.obj.parseValue (jexcel.js:7150)     at Object.obj.createCell (jexcel.js:7266)     at Object.obj.createRow (jexcel.js:7126)     at Object.obj.setData (jexcel.js:6849)     at Object.obj.createTable (jexcel.js:6698)     at Object.obj.prepareTable (jexcel.js:6431)     at Object.obj.init (jexcel.js:12865)     at jexcel (jexcel.js:13142)     at Function.jexcel.tabs (jexcel.js:14184)     at a36716cf-4746-47c3-b5a7-a2be7ccfc81d:388
We are using jSuites by importing the following script:
<script src="https://jsuites.net/v3/jsuites.js"></script>
It appears that the most recent commit 504d8086ef39f14771064b3f50e8176923e1f831 has made changes to the mask.js file. Could this be causing these errors?
Regards,

Change to v4
On Friday, August 13, 2021, HemDogz @.***> wrote:

Hello, we are using the jSuites library in a project of ours, and just
today we've lost functionality, and we are seeing the following error:
Uncaught TypeError: jSuites.mask.render is not a function at
Object.obj.parseValue (jexcel.js:7150) at Object.obj.createCell
(jexcel.js:7266) at Object.obj.createRow (jexcel.js:7126) at
Object.obj.setData (jexcel.js:6849) at Object.obj.createTable
(jexcel.js:6698) at Object.obj.prepareTable (jexcel.js:6431) at
Object.obj.init (jexcel.js:12865) at jexcel (jexcel.js:13142) at
Function.jexcel.tabs (jexcel.js:14184) at a36716cf-4746-47c3-b5a7-
a2be7ccfc81d:388
We are using jSuites by importing the following script:
<script src="https://jsuites.net/v3/jsuites.js"></script>
It appears that the most recent commit 504d8086ef39f14771064b3f50e8176923e1f831 has made changes to the mask.js file. Could this be causing these errors?
Regards,
[image: Screen Shot 2021-08-13 at 1 02 19 pm]
https://user-images.githubusercontent.com/59714461/129302892-02bf064b-6724-40eb-812f-44c55176a3be.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jsuites/jsuites/issues/91, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABN5VAP7HVHKTBW77RQ7FI3T4SJ27ANCNFSM5CCZGA4Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.


Documented deployCode signatures with value

Documentation of the two new deployCode signatures which consider values.
Fix #461

Sure! I'm gonna do it now!

Done!


Python extension does not show on status bar

Type: Bug
After installing the Python extension, it does not show up on the status bar
VS Code version: Code 1.80.1 (74f6148eb9ea00507ec113ec51c489d6ffb4b771, 2023-07-12T17:22:07.651Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Extensions (2)

Extension
Author (truncated)
Version

python
ms-
2023.12.0

vscode-pylance
ms-
2023.7.30

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
py29gd2263:30792226
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30610679
282f8724:30602487
89544117:30613380
vscrpc:30673769
showlangstatbar:30737416
vsctsb:30748421
a2ce3375:30757347
pythonfmttext:30731395
pythoncmv:30756943
fixshowwlkth:30771522
showindicator:30785052
pythongtdpath:30769146
i26e3531:30792625
pythonnosm12tcf:30779713
pythonidxpt:30784022
pythonnoceb:30776495
e537b577:30795824
dsvsc013:30795093

/extPython

It looks like this is caused by the Python extension. Please file the issue to the Python extension repository. Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our issue reporting guidelines for more information.
Happy Coding!


When we can use Casbin 1.4.0 into EFCore-Adapter?

When we can use Casbin 1.4.0 into EFCore-Adapter code?
because whenever in NuGet package manager EF Core1.3.0 is the latest version, when will be the latest version comes?

@Sagilio

@Sagilio

When we can use Casbin 1.4.0 into EFCore-Adapter code?
because whenever in NuGet package manager EF Core1.3.0 is the latest version, when will be the latest version comes?

I am trying to implement the new interface，It will be released in a few days.

When we can use Casbin 1.4.0 into EFCore-Adapter code?
because whenever in NuGet package manager EF Core1.3.0 is the latest version, when will be the latest version comes?

I am trying to implement the new interface，It will be released in a few days.

@Sagilio plz make a new release.

@Sagilio plz make a new release.

@Sagilio plz make a new release.

Already released.

@Sagilio plz make a new release.

Already released.

@kbsiva see: https://github.com/casbin-net/EFCore-Adapter/releases/tag/v1.3.1

@kbsiva see: https://github.com/casbin-net/EFCore-Adapter/releases/tag/v1.3.1

Thank you. Taken latest..
On Tue, 12 Jan 2021 at 08:39, Yang Luo<EMAIL_ADDRESS>wrote:

@kbsiva https://github.com/kbsiva see:
https://github.com/casbin-net/EFCore-Adapter/releases/tag/v1.3.1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/casbin-net/EFCore-Adapter/issues/31#issuecomment-758364974,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGTE4TW73MWKOSNJYS4I7WLSZO4OLANCNFSM4VUPTLHQ
.

Thank you. Taken latest..
On Tue, 12 Jan 2021 at 08:39, Yang Luo<EMAIL_ADDRESS>wrote:

@kbsiva https://github.com/kbsiva see:
https://github.com/casbin-net/EFCore-Adapter/releases/tag/v1.3.1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/casbin-net/EFCore-Adapter/issues/31#issuecomment-758364974,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGTE4TW73MWKOSNJYS4I7WLSZO4OLANCNFSM4VUPTLHQ
.


[WIP] Remove the old templates which have been replaced by Helm charts

The old Kubernetes templates have been replaced by Helm charts and aren't being used anymore nor maintained.

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

Needs approval from an approver in each of these files:

OWNERS

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

@ymesika: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
5335db0a46d7d9ce7ac1a1ae1fed31e3bc9a588c
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

lgtm, make sure all tests pass

@ymesika: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
77684f9caa5ee1c4aad546df547095331c1afb33
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ymesika: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
afe65e3cd868e35a20e8710cfa6b25457e032386
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Japanese README

I localized README.md into Japanese.

 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.:x: ayatokura sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Thanks!


What is the mqtt topic? v1.3.1

Those are the new features.
Added
[firmware] Support for Door Status tracking with log and mqtt options @nardev
[firmware] adding mqtt_publish_info, generateUid functions @nardev
[firmware] MQTT functionality is greatly improved, thanks to @marelab
But I don't know what the topic is can someone help me? And the acces loggin is not working.

in 1.3.3: it is a JSON string. doorip ist the ip of the ESP-RFID:
mosquitto_pub -h mastermind -t testrfid -m '{"doorip":"<IP_ADDRESS>","cmd":"opendoor"}'

@ingeninge tested? should we merge it?

Yes tested it just a few minutes before with a fresh installation on the Node-MCU.
Mit freundlichem Gruß, Kind regards,
Ingmar Joern
Von: nardev<EMAIL_ADDRESS>Gesendet: Freitag, 11. September 2020 20:02
An: esprfid/esp-rfid<EMAIL_ADDRESS>Cc: Joern, Ingmar<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Betreff: Re: [esprfid/esp-rfid] What is the mqtt topic? v1.3.1 (#392)
@ingeningehttps://github.com/ingeninge tested? should we merge it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/esprfid/esp-rfid/issues/392#issuecomment-691236234, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL6PZC5FDPFAPI6OBUOPFY3SFJQ3BANCNFSM4PHMYFZQ.


Closes #4

Closes #4
In addition to removing the Google Drive links from the references, this pull request includes several minor changes:

Removing the bullet points from references, which caused links to appear twice on the page
Renaming circuit_schematic.adoc to ibd-system-electronic-sensing-system-dataflow.adoc, matching the diagram's naming structure.
Links added to the UML diagram of the splitter assembly, as well as @Burhan-Q 's hardware requirement's list
-Minor capitalization/ description changes

Sorry for the wait; should be good to go now @capsulecorplab!


Benchmark Script/Dataset for ANTs?

Similar to the TravisCI, is there anything around to test whether ANTs is getting faster/slower with commits?
I'm investigating some compiler things so I was wondering if anyone had looked into this before.

No.  The closest thing we have are the timing tests that are done as part of the ITKv4 regression platform.  For example, you can see timing for a specific test which exercises N4 bias correction
https://open.cdash.org/testDetails.php?test=373086722&build=4114509
and then select "Display graphs:  Test time."


configFileNotFound bug?

I was just reviewing the code, and I found a part that looks a little suspect..
https://github.com/sagikazarmark/modern-go-application/blob/master/cmd/modern-go-application/main.go?ts=4#L89
if ReadInConfig does not return an error, then configFileNotFound would be false, right? since the type assert from nil to viper.ConfigFileNotFoundError would fail?
err := v.ReadInConfig()
_, configFileNotFound := err.(viper.ConfigFileNotFoundError)
if !configFileNotFound {
	emperror.Panic(errors.Wrap(err, "failed to read configuration"))
}

# more stuff, including configuring the logger

if configFileNotFound {
	logger.Warn("configuration file not found")
}

it seems like the code will either always panic, or log a warning.
The viper shows the correct way: https://github.com/spf13/viper?ts=4#reading-config-files
if err := viper.ReadInConfig(); err != nil {
    if _, ok := err.(viper.ConfigFileNotFoundError); ok {
        // Config file not found; ignore error if desired
    } else {
        // Config file was found but another error was produced
    }
}

// Config file found and successfully parsed

Additionally, I don't think this is best practice anyway, since a configuration file should not be required if ENV variables are also an alternative. Maybe I'm also reading the code wrong...

@ghostsquad I was just looking at this too, and it is correct, just hard to read.
If you switch the order of the if statements, you will see that it is actually the same as the viper example.
If you want to avoid the error, change it to this (with explanatory comments added):
usingConfigFile := false

if c, _ := p.GetString("config"); c != "" {
	v.SetConfigFile(c)
	usingConfigFile = true
}

err := v.ReadInConfig()
// This sets `configFileNotFound` to `true` if the file does not exist
// or `false` if the file exists but there is some other problem with it.
_, configFileNotFound := err.(viper.ConfigFileNotFoundError)
if !configFileNotFound {
	// Since there was a file and it was bad, show an error.
	emperror.Panic(errors.Wrap(err, "failed to read configuration"))
}

# more stuff, including configuring the logger

// Only do this is `usingConfigFile` is true
if usingConfigFile && configFileNotFound {
	// A path was provided to a nonexistent file, warn the user
	logger.Warn("configuration file specified but not found")
}

(That is what I did)

Admittedly, this kind of assertion is always hard to read, especially with errors (or pointers in generic).
Whether warning is a correct level for a missing config file or not depends on how you operate your applications: most of the time I deploy them to Kubernetes using Helm, so YAML comes as a first class citizen in Helm values, translated into a config file.
But that's just how I do things, I don't consider it a best practice. If you strictly want to follow Twelve Factor apps, using env vars is perfectly fine.
I can think of two possible improvements (not touching the assertion though):

log the fact that config file was not available as Info instead of Warn. Since Viper will look for a config file automatically and you might want to rely on that behavior, logging only when a config flag is explicitly provided might not be the best option
invert the condition: write log (with config file path) whenever a config file is loaded. There is a similar behavior in Viper actually, but I'm not a huge fan of it TBH, so I prefer avoiding it. In Viper 2 we might be able to improve these things.

One could also argue that this is actually not really relevant during normal operations and only has a value during debugging, so we could make it a debug log as well.
WDYT?

One could also argue that this is actually not really relevant during normal operations and only has a value during debugging, so we could make it a debug log as well.

There is one production case in which it makes sense to be a warning (or maybe even an error). I am considering the following four cases:

The user is using env vars to configure or is using the default config file location. In this case, there is no need to log anything.
The config file (either user-specified or default) is invalid. In this case, it will panic with an error message.
The user has specified a config file and it is valid. In this case there is also no need to log anything.
The user has specified a config file, but the file does not exist. This is the case in which we really need to warn the user.


Adds simulated sensor

Description:
This sensor reproducibly generates simulated data with configured properties, including a mean level, a periodic component, and a noise term. This is useful if you are doing a demo and wish to quickly generate some data to display, but don’t have physical devices or internet connection (the current random sensor only generates white noise, not very interesting!). Another use is debugging an automation, if you want to generate a repeatable signal.  Another motivation for writing this component is for testing filter components. Example usage here.
Note this can be re-written without numpy if required.
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<4712>
Example entry for configuration.yaml (if applicable):
  - platform: simulated

Checklist:

[ x] The code change is tested and works locally.

If user exposed functionality or configuration variables are added/changed:

[x ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ x] New files were added to .coveragerc.

If the code does not interact with devices:

[x ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x ] Tests have been added to verify that the new code works.

I wonder if this should be its own platform or that we just add it to the demo platform.

I would say Demo platform, makes the demo more realistic too :)

I’m not too familiar with the demo platform. Does that mean it wouldn’t be available on a production install?
Btw I do have a demo planned for a conference in April at the pydata London event

We ship demo platforms in prod.

So I am still not convinced that this needs to be a platform on its own. Should this be added to the demo sensor platform?
If you want to show fake data, the demo platforms are the way to go. Every entity component has them.
light:
  platform: demo

switch:
  platform: demo

# etc, etc

@balloob I'm happy to make it a demo, but there might be uses outside demo, for example this guy wants to use the sine wave to ramp the brightness of a light

I'm not sure why the config is failing on Travis, works fine locally

Just the 3.4 python failing each time now

@balloob have made a pull for adding to the demo platform on 12637

Will close for now as adding to demo seems better

Reopening as perhaps demo isn't the correct place for this

Sorry about that… let's stick with signal, you win 😉

few minor comments and then this is ok to merge.


Fix dynamodb stream event decoder

This slipped through the cracks somehow...

yeah, but end to end 😅


Update snap revision to 91 (MySQL v8.0.35)

Issue
We release a new snap to the edge channel (revision 91) which has MySQL v8.0.35. However, our charm is using the snap revision 69 with MySQL v8.0.34
Solution
Update snap revision to use the revision with MySQL v8.0.35

Additionally, for consistency, we should update pyproject.toml
- mysql-connector-python = "~8.0.33"
+ mysql-connector-python = "~8.0.35"


Sticky headers are not pushing one another from screen when using grid layout manager.

Hi,
I am testing 5.0.0-b5 and found a bug in StickyHeaderHelper#translateHeader() on row 151. You are expecting next potential header on position 1. But if for example I use 3 columns in my grid, you will always get current header until all items in section are off the screen.
So you won't get this nice pushing of one header off the screen by another header.
I was able to reproduce this in your demo app, when I changed span count of grid to 3 and span size of all items except header to 1.
Anyway, thanks for great work.

Hello @MartinRajniak, I've reproduced the issue using the fragment ExpandableSection using 3 for span count and size for non header items.
Indeed, it should enter in the if at line 155 to calculate the translation, but it doesn't.
Logging the item cotent with adapterPos it shows:
SubItem[id=E1S1, title=Sub Item 1 in expandable section]
SubItem[id=E1S2, title=Sub Item 2 in expandable section]
but not the sub Item 3, then it swap the header, so it doesn't see where the section ends
swapHeader newPosition=5
SubItem[id=E2S2, title=Sub Item 2 in expandable section]
I will try to fix it.
Thanks.

I think this issue should be resolved, available with the SNAPSHOT of 2017-04-17.


Installation fails

Synology DS218Play, DSM 7

Homebridge is installed and works
Other plugins work fine
Installation of Loxone Connect returns error messages (when installed via plugin UI)
Installation via terminal returns minor warnings, no errors.
Plugin installed via terminal does not show up in plugin UI.

Questions:

How to see the installed plugin in the plugin UI?
If not possible, how to configure and start plugin from the terminal?

Error messages when installed via plugin UI:
USER: homebridge
DIR: /volume1/homebridge
CMD: npm install --save<EMAIL_ADDRESS>[##################] / reify:es-abstract: timing reifyNode:node_modules/homebridge-lox

<EMAIL_ADDRESS>install
node-gyp-build

gyp ERR! build error | reify:es-abstract: timing reifyNode:node_modules/homebridge-lox
gyp ERR! stack Error: not found: make
gyp ERR! stack     at getNotFoundError (/volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/which/which.js:10:17)
gyp ERR! stack     at /volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/which/which.js:57:18
gyp ERR! stack     at new Promise ()
gyp ERR! stack     at step (/volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/which/which.js:54:21)
gyp ERR! stack     at /volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/which/which.js:71:22
gyp ERR! stack     at new Promise ()
gyp ERR! stack     at subStep (/volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/which/which.js:69:33)
gyp ERR! stack     at /volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/which/which.js:80:22
gyp ERR! stack     at /volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/isexe/index.js:42:5
gyp ERR! stack     at /volume1/@appstore/homebridge/app/lib/node_modules/npm/node_modules/isexe/mode.js:8:5
gyp ERR!   Please review log for details.

Solved - sorry for the issue. I found the appropriate directory and moved it to the other plugin folders and then it showed up.

Hi, no problem!
Glad to see that you were able to solve this issue.


Huge battery consumption

Expected behavior
The battery consumption should be a magnitude order below the screen that it is the most battery drying source of a smartphone.
Actual behavior
K-9 Mail has even more battery consumption that the screen by far, so much that it reduces the battery life from 4:30 h of screen use to around 3:00 hours.
Steps to reproduce
I don't have done anything special, average usage, move email to IMAP folders, archive, delete,and so on.
Environment
K-9 Mail version: 5.115
Android version: 6.01
Account type (IMAP, POP3, WebDAV/Exchange): 2 IMAP accounts

Logs would be useful here. K-9 does not normally use so much battery.

@philipwhiuk could you tell me please how could I log the behavior, I would like to contribute somehow. Power consumption remains very high. I use to have a lot of email every day, I handle all my subscriptions over the email and I move tons of emails through different folders, but I don't use the application so much to have a consumption that sometimes is over than the screen's.

Logging information can be found here https://github.com/k9mail/k-9/wiki/LoggingErrors.
I had huge battery drains like that, my problem was that my IMAP server had a timeout of 30 seconds or less. So it was reconnecting all the time.

Hi
I recognized high battery consumption from k9 as well
I used K9 version 5.208.
Android Version 6.0.1
Wake Lock Detector showed quite wakeup number >1500 over night.
I uninstalled k9 and there was really a big difference of battery consumption over night.

Same here on Android 7, it's classified as "power-intensive app". I've just enabled debugging.

I just looked at the logs and there is nothing really interesting. It only shows stuff when I manually synced. Auto-sync is off. The bits where it wastes battery are probably not logged.
https://git.io/vFfN5

Seems to be same issue as https://github.com/k9mail/k-9/issues/3027
Is there a way to link the issues here?

Not actionable.

Not actionable.

Lol what? Does that make it less of a bug? :)


continuous syncing service

Syncing from kakfa and doing ETL should run as a continuous service so we don't need to poll and recompute progress state on each run.
Step 1 is to get from-kafka to provide a continuous service where it listens on each configured topic and syncs data as it arrives.  There should be two parameters to drive commits: a data limit and a timeout.  When data arrives but does not exceed the data limit, a timeout triggers processing.
Step 2 is to automate ETL based on from-kafka commits.  Here the service is running continuously and whenever data arrives that could be consumed by an ETL, the logic is run automatically.  This way, we don't need to run ETLs on a polling loop as they are run only when they have new data to process.

Step 1 is complete, and Step 2 remains to be done.


Update to bootstrap 5.1.0

This PR updates the bundled bootstrap version to 5.1.0 and updates all HTML/CSS to work with the new version.
Fixes #62

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 73.939%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1010

Relevant Lines:
1366

💛  - Coveralls


release pipeline

Since tezos-k8s now has a docker folder containing custom containers (only zerotier today, but there will be more soon), we need to deploy these containers to docker hub (or somewhere else). It's best to do it through github actions.
Then, have mkchain figure out by itself if it's a tagged released version, and in this case, go fetch zerotier container from docker hub instead of expecting the container to be built by devspace.
This removes the devspace requirement for published releases.

fixed by #44


fix(astprinter): implement transitive interface output

Just copied relevant part from EnterObjectTypeDefinition()
Also add tests
Fixes #1018

Hi @lorf
thanks for the contribution!
Wundergraph Team

Thank you!


Fixes #2105 Intermittent test failure ResourceBlame/ResourceBlame.test.tsx

Coverage: 94.326%. Remained the same when pulling 76bd699e7f75715b26b6a53015566bc8bb78b599 on tony-test-failure-resourceblame into 8c2b7f273e9ad2dc4b35479d6a5a24f31cbadd6d on main.


not hacked by china???

dear sirs
i tried to find havelin website but didn't have a china banner in browser
how i can be sure this is authentic javelin project???
from dearest friends
@tomocchino @spicyj

Every day I speak to anyone who will listen, about the wonder that is javelin. I dearly miss it.

Life is more about the journey than the destination. 🐈

Such profound wisdom. I miss your divine tutelage.

Come work for free (no money) forever (until you die). What base earthly reward could be equal to a lifetime of noble servitude?

Did someone say work for free?!?!?
On Apr 11, 2017, 9:54 AM -0700, Evan Priestley<EMAIL_ADDRESS>wrote:

Come work for free (no money) forever (until you die). What base earthly reward could be equal to a lifetime of noble servitude?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub (https://github.com/phacility/javelin/issues/50#issuecomment-293326451), or mute the thread (https://github.com/notifications/unsubscribe-auth/AA_zLwYBYMhMYmoPCsQFe_RJVCzk43cCks5ru7AdgaJpZM4M6Wwb).


[Hosted Rancher, Monitoring V1, Alerting V1] CPU spike observed when Monitoring / Alerting installed in downstream Rancher's local cluster

Rancher Server Setup

Rancher version: v2.5.9 Super Rancher cluster, v2.6.0 Downstream Rancher cluster
Installation option (Docker install/Helm Chart): Helm Chart for both

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): k3s for both

Proxy/Cert Details: N/A

Information about the Cluster

Kubernetes version: v1.20.10+k3s1 for both
Cluster Type (Local/Downstream): Impacted cluster is local to the Downstream Rancher, downstream to the Super Rancher cluster.

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): Imported (k3s)

Describe the bug

When Monitoring V1 + Alerting V1 are enabled on a local cluster which itself is added as a downstream cluster on another Rancher instance, buggy behaviors during reconcile result in a spike in CPU / memory usage across nodes in the local cluster.
This seems to be caused by a race between the managing Rancher cluster and the Rancher cluster that is being managed since one thinks Monitoring / Alerting should be enabled while the other disagrees.
This is not seen in Rancher 2.5.9 managing Rancher 2.5.9; it is only seen in Rancher 2.5.9 managing Rancher 2.6.0.
To Reproduce

Initial Setup
Note on Terminology
To replicate a Hosted Rancher setup, we will have two Ranchers:

a Super Rancher cluster, which will manage other Ranchers. This will run Rancher 2.5.9
a Downstream Rancher cluster, which will be added to the Super Rancher cluster as a downstream. This will run Rancher 2.6.0

I will refer to the Super Rancher cluster's local cluster as superlocal.
I will refer to the Downstream Rancher cluster's local cluster as local.
Both will run the last stable k8s 1.20 release: v1.20.10+k3s1
Note on Required Resources
I used 2 8GB_4vCPU Digital Ocean instances, where the first instance was used for the superlocal cluster (all roles) and the second instance was used for the local cluster.
I also provisioned DNS records that point to the superlocal host and the local host so that I could use it as the HOSTNAME below.
Setup Super Rancher Cluster

Provision a node
Install k3s on the node: curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=v1.20.10+k3s1 sh -; export KUBECONFIG=/etc/rancher/k3s/k3s.yaml
Install Helm: curl https://raw.githubusercontent.com/helm/helm/master/scripts/get-helm-3 | bash
Run the following commands before installing Rancher

RANCHER_VERSION=v2.5.9

# Set the below to a hostname that can be used to access the Rancher instance
# HOSTNAME=HOSTNAME

helm repo add rancher-latest https://releases.rancher.com/server-charts/latest
helm repo add jetstack https://charts.jetstack.io
helm repo update

kubectl create namespace cattle-system

kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.0.4/cert-manager.crds.yaml
kubectl create namespace cert-manager
helm install \
  cert-manager jetstack/cert-manager \
  --namespace cert-manager \
  --version v1.0.4

Run the following install to install Rancher

helm install rancher rancher-latest/rancher \
  --namespace cattle-system \
  --version ${RANCHER_VERSION} \
  --set hostname=${HOSTNAME} --create-namespace

Login to Rancher

Install Monitoring V1 onto the Rancher Super Cluster's local cluster

On the Rancher Super Cluster Cluster Manager UI, click on the local cluster
Go to Tools -> Monitoring
Click on Enable at the bottom of the Monitoring install page with no other changes (note: version should be 0.2.2).

Note: This step is only necessary to identify if we are seeing any spikes in the superlocal cluster as well.
Setup Downstream Rancher Cluster

Install k3s: curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=v1.20.10+k3s1 sh -; export KUBECONFIG=/etc/rancher/k3s/k3s.yaml
Install Helm: curl https://raw.githubusercontent.com/helm/helm/master/scripts/get-helm-3 | bash
Run the following commands before installing Rancher

RANCHER_VERSION=v2.6.0

# Set the below to a hostname that can be used to access the Rancher instance
# HOSTNAME=HOSTNAME

helm repo add rancher-latest https://releases.rancher.com/server-charts/latest
helm repo add jetstack https://charts.jetstack.io
helm repo update

kubectl create namespace cattle-system

kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.0.4/cert-manager.crds.yaml
kubectl create namespace cert-manager
helm install \
  cert-manager jetstack/cert-manager \
  --namespace cert-manager \
  --version v1.0.4

Run the following install to install Rancher

helm install rancher rancher-latest/rancher \
  --namespace cattle-system \
  --version ${RANCHER_VERSION} \
  --set hostname=${HOSTNAME} --create-namespace

Login to Rancher

Add Rancher Downstream Cluster to Rancher Super Cluster

On Rancher Super Cluster's Cluster Manager UI, click on Add Cluster
Under Register an existing Kubernetes cluster, click on Other Cluster
Name the cluster downstream-rancher-260 and click Create.
Run the provided kubectl command (I used the insecure command with curl) and run against the Rancher Downstream Cluster

Install Monitoring V1 onto the Rancher Super Cluster's downstream-rancher-260 cluster

On the Rancher Super Cluster Cluster Manager UI, click on the local cluster
Go to Tools -> Monitoring
Click on Enable at the bottom of the Monitoring install page with no other changes (note: version should be 0.2.2).

Install Alerting V1 onto the Rancher Super Cluster's downstream-rancher-260 cluster

On the Rancher Super Cluster Cluster Manager UI, click on the local cluster
Go to Tools -> Notifiers and configure a Notifier
Go to Tools -> Alerts and add the configured Notifier to any of the provided alert groups. As long as at least one notifier is attached to at least one alert, Alerting V1 will be enabled.

Result
CPU + memory both settle in the cluster at an average of about 60%.
Spammy logs are emitted from the local Rancher (e.g. the Rancher that is being managed by Rancher) that look like:
2021/09/20 21:18:02 [ERROR] error syncing 'cattle-prometheus/cluster-alerting.v1': handler helm-app: failed to delete cattle-prometheus/cluster-alerting catalog.cattle.io/v1, Kind=App for helm-app cattle-prometheus/cluster-alerting.v1: apps.catalog.cattle.io "cluster-alerting" not found, requeuing

Logs are also emitted from the cluster-agent that look like:
time="2021-09-20T21:19:15Z" level=error msg="error syncing 'cattle-prometheus/cluster-monitoring': handler helm-app-status: Operation cannot be fulfilled on apps.catalog.cattle.io \"cluster-monitoring\": StorageError: invalid object, Code: 4, Key: /registry/catalog.cattle.io/apps/cattle-prometheus/cluster-monitoring, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 7502104d-3720-4e93-84d8-3acb1adbd124, UID in object meta: , requeuing"

Expected Result

No CPU / memory spike should happen. It should be the same as managing any other downstream cluster, with some caveats.
Expected CPU should be around 20% average and expected memory should be around a 40% average.
Screenshots

Additional context

SURE-3301

On the same cluster in which I was able to reproduce this issue, using Monitoring V2 instead of Monitoring V1 results in back-to-normal memory / CPU usage. This confirms that the issue here is with the Monitoring / Alerting V1 reconcile logic in a Rancher-in-Rancher setup.

Both of the above logs seem to come from the Dashboard App controller here:
https://github.com/rancher/rancher/blob/7e7db270d9ac87355d063638929fd712c6616b72/pkg/controllers/dashboard/helm/apps.go#L38-L57
downstream rancher server log
2021/09/20 21:18:02 [ERROR] error syncing 'cattle-prometheus/cluster-alerting.v1': handler helm-app: failed to delete cattle-prometheus/cluster-alerting catalog.cattle.io/v1, Kind=App for helm-app cattle-prometheus/cluster-alerting.v1: apps.catalog.cattle.io "cluster-alerting" not found, requeuing

This error message stems from processSingleItem in rancher/lasso, which wraps the error returned from (*desiredSet).process when an object is marked for deletion.
(*desiredSet).process is called when (*desiredSet).apply is called, which is called when (*desiredSet).Apply is called.
In turn, (*desiredSet).Apply is called when (*desiredSet).ApplyObjects is called, which is exactly the call that we see at the end of OnConfigMapChange in the appHandler here:
https://github.com/rancher/rancher/blob/7e7db270d9ac87355d063638929fd712c6616b72/pkg/controllers/dashboard/helm/apps.go#L135-L167
super cluster-agent logs
time="2021-09-20T21:19:15Z" level=error msg="error syncing 'cattle-prometheus/cluster-monitoring': handler helm-app-status: Operation cannot be fulfilled on apps.catalog.cattle.io \"cluster-monitoring\": StorageError: invalid object, Code: 4, Key: /registry/catalog.cattle.io/apps/cattle-prometheus/cluster-monitoring, ResourceVersion: 0, AdditionalErrorMsg: Precondition failed: UID in precondition: 7502104d-3720-4e93-84d8-3acb1adbd124, UID in object meta: , requeuing"

This error seems to indicate that the app does not exist, but the appStatus function was still called on a non-existent object. I suspect this would occur if a controller were to enqueue a non-existent app, which would cause the appStatus function to get triggered since it is watching for changes to apps:
https://github.com/rancher/rancher/blob/7e7db270d9ac87355d063638929fd712c6616b72/pkg/controllers/dashboard/helm/apps.go#L49
My suspicion is that this is being triggered by (*AppStateCalculator).sync, which is triggered anytime a workload is changed within the cluster:
https://github.com/rancher/rancher/blob/7e7db270d9ac87355d063638929fd712c6616b72/pkg/controllers/managementuserlegacy/helm/state.go#L36
https://github.com/rancher/rancher/blob/7e7db270d9ac87355d063638929fd712c6616b72/pkg/controllers/managementuserlegacy/helm/state.go#L51-L79
Based on the above code, if the Rancher cluster-agent were to see a workload (e.g. Prometheus) associated with the Monitoring V1 app deployed by the Rancher super cluster, it would still be able to:

Get the app label, which seems to exist on the Prometheus deployment since it was added by the super Rancher cluster
Get the deployment's namespace
Get the project label from the deployment namespace, which seems to exist since it was added by the super Rancher cluster
Get the app based on the projectNS and label: since the lister here is the management apps lister, this will work.

https://github.com/rancher/rancher/blob/7e7db270d9ac87355d063638929fd712c6616b72/pkg/controllers/dashboard/helm/apps.go#L155-L158
Since the app is not nil and the deletion timestamp is not nil, we will proceed to enqueue the apps controller, which will fail since we omitted to create the app in the first place since it was Helm 2 in 2.6.x (this code did not get backported to 2.5.x):
https://github.com/rancher/rancher/blob/7e7db270d9ac87355d063638929fd712c6616b72/pkg/controllers/dashboard/helm/apps.go#L155-L158

Further investigation has confirmed that this issue was caused by https://github.com/rancher/rancher/pull/33661.
Specifically, the issue here is that a Super Rancher-2.5 creates a app.catalog.cattle.io/v1 resource that is owned by the Helm 2 ConfigMap on enqueuing ConfigMap by executing the following code:
https://github.com/rancher/rancher/blob/6238e47b2198956ba59330bc171995aacbda1c08/pkg/controllers/dashboard/helm/apps.go#L155-L161
On the other hand, the Downstream Rancher-2.6 destroys any resources owned by the Helm 2 ConfigMap on enqueueing the ConfigMap by executing the following code:
https://github.com/rancher/rancher/blob/b24724f3eed83901ca02a67fd52d7a3fb3bc44c9/pkg/controllers/dashboard/helm/apps.go#L155-L158
As a result, the apps.catalog.cattle.io perpetually flaps, creating and destroying the resources every second, which is why we see logs like the above seen in the cattle-cluster-agent or rancher pods since the resources are created (resulting in enqueue) and then immediately destroyed before they are finished being processed. This also results in the CPU / Memory spikes seen.
P.S. Thanks @StrongMonkey for helping me figure this out!

Tested this with upstream rancher v2.6.1-rc5 and downstream rancher v2.6.1-rc5 with monitoring v1 enabled and did not see these error messages. Did not test upstream rancher v2.5.9 w/ downstream v2.6.1-rc5 since that is not a supported configuration (upstream must be v2.6 for v2.6 downstream clusters).


Fix keys export

Codecov Report

Merging #180 into develop will decrease coverage by 1.03%.
The diff coverage is 0%.

@@             Coverage Diff             @@
##           develop     #180      +/-   ##
===========================================
- Coverage    41.77%   40.74%   -1.04%
===========================================
  Files           11       11
  Lines           79       81       +2
  Branches         7        8       +1
===========================================
  Hits            33       33
- Misses          45       46       +1
- Partials         1        2       +1

Impacted Files
Coverage Δ

src/models/TranslationKey/index.js
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Add missing indefinite article

This typo was found in the introduction to the "Workspaces API" section.

Thanks @DasAllFolks. Appreciated.


Separate email for order confirmation

I want to merge this change because it sends an email after order has been confirmed.
This is a PR to feature branch.
Related ticket: SALEOR-1389

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-1389 Separate email for order created and confirmed


node_rsync option is not described in documentation.

Hi.
I found this code:
https://github.com/machinezone/mzbench/blob/3e5a35f21f0c30509f07379504332c13cd067aeb/server/src/mzb_api_bench.erl#L556
so i think it is very useful option, and it must be described in documentation.
Thanks.

fixed: https://github.com/machinezone/mzbench/commit/2011e866466853b9140e6858dbc4d8f9a3757668
Thank you!

When it will be available on https://machinezone.github.io/mzbench/deployment ?

updated

closing, feel free to re-open if something more needs to be done here


Update introduction and add details to installation guide

So the details we need in there is about how to install the binaries in different platforms. for example linux, windows etc. Also, if we have docker distros that needs to be added there as well.
For the introduction we have a fairly decent introduction in gitbook but we can add more items in there. Maybe a call to action for a quickstart page

We could take some stuff from https://www.makeareadme.com/ for the introduction. I suppose for usage a YAML + CLI konduit serve example will do nicely.


How do the world positions of AnchorNode and Node determine the drift of the location marker?

when using ARCore-Location to implement an app which places  AR labels at specific gps locations,I meet some issues.
1、when the phone is still,the location marker pops on the screen sometimes,with the world position of the AnchorNode changing.
2、when I move the phone(but the pose of the phone does not change,just hold the phone and walk straight on the path),the world position of the AnchorNode does not change,but the location marker moves along with the phone.it does not pop,it seems like that it sticks on the screen and moves with the phone.
I am confused that by logging i find world position of the node presenting the gps location is consistent over the session,because the position is set just as below when the node is the child of the anchorNode:
            n.setWorldPosition(new Vector3(n.getWorldPosition().x, getHeight(), n.getWorldPosition().z));
            //Log.i("LocationScene","node x:"+n.getWorldPosition().x+" y:"+direction.y+" z:"+n.getWorldPosition().z);

            Quaternion lookRotation = Quaternion.lookRotation(direction, Vector3.up());
            n.setWorldRotation(lookRotation);
            n.setWorldScale(new Vector3(scale, scale, scale));

when the getHeight() returns the constant the world position of the node does not change.
while I log the world position of the AnchorNode,I find it changes when anchorsNeedRefresh is true.
I am confused that I find description like this:
placing an anchor that is not associated with a Trackable object is usually not a good experience. The trackable object (planes, augmented images, oriented points) are update by ARCore to represent the connections between the real world image and the augmented, virtual images. If you place an anchor in the "air", it will drift and move relative to the real world.
in the https://github.com/google-ar/sceneform-android-sdk/issues/185,so the implementation like this is just creating an anchor not attached to a trackable object but in the "air",and thus the location marker will drift with the phone?
I do not understand the significance of the code,and why does the world position of anchorNode change over time.If the world coordinate frames is set definite(the origin is on the camera at the start of the session),then to understand the relationship between the node and the camera,the coordinate of AnchorNode should change every time?
Why does the locationMarker moves with phone when the pose and the world position of the anchorNode do not change,just like the locationMarker sticking on the screen?How can i resolve it?
Thanks for any help.

Anther issue is that i find the world position of camera changes every frame even when the phone is still.I log the value like this:
```
final Vector3 cameraPosition = getScene().getCamera().getWorldPosition();
Vector3 direction = Vector3.subtract(cameraPosition, n.getWorldPosition());
Log.i("LocationScene","Camera:x:"+cameraPosition.x+"  y:"+cameraPosition.y+"  z:"+cameraPosition.z+"
node:x:"+n.getWorldPosition().x+"  y:"+n.getWorldPosition().y+"  z:"+n.getWorldPosition().z);
Why does this happen?


[XLA] utility functions and more/better logging

Add a few utility functions and some update to the logging system.
This will be needed for the following PR.
@sanjoy @thomasjoerg

Ok. But what difference you see between the 2 utilities functions here that make you have different preference between them?

Ok. But what difference you see between the 2 utilities functions here that make you have different preference between them?

One of them is exercised (albeit only via a unit test) while the other one isn't.
In this specific case this isn't a big deal at all, the added methods are very simple.  But for more complicated helpers it is nice to introduce both the helpers and some code using the helpers so that if the helper is buggy then the CL won't pass unit tests.

ok. thanks.


Allow updating GitHub reusable workflows

This PR fixes #4327
It changes how the "uses" key is searched for and found.  Reusable workflows do not have the "steps" key, this fix no longer make the assumption that a "steps" key exists, however it still processes the "steps" key if it does exist.
The fix also allows for a mix of reusable or standard workflows to exist in the same directory.
New logic to find and update "uses":
Check for "jobs" key and provide that section to the search.
Recursively search for "uses" key.
If it is a hash and has "uses" key, then add the "uses" value to the found_uses array.
If it is a hash and has "steps" key, then send the "steps" value recursive search function.
If neither "steps" or "uses" are found, then send each item in the current hash/array into the recursive search function.
Once the entire jobs section has been searched return the found_uses and build a dependency set out of them.
Adds the following tests:
empty File
semver Reusable Workflow
standard Reusable Workflow

In addition to the added specs, I also ran against a test repo.
Two files define non-reusable actions (lint and release yml files)
Reusable workflow defined in test.yml
An empty.yml was also created, to ensure that empty files do not cause an exeception
yml files here:
https://github.com/dwc0011/test-old-actions-wf/tree/master/.github/workflows
PRs created:
https://github.com/dwc0011/test-old-actions-wf/pulls

Thanks @deivid-rodriguez for the style changes and the approval.
Any thoughts on when this will be merged and released?

I'll try to merge and deploy this soon™.

I do have one question. In the linked issue I referenced this piece of code:
https://github.com/dependabot/dependabot-core/blob/3846a60c18074d6b52f6d05c33a554e6a1b6ff31/github_actions/lib/dependabot/github_actions/file_fetcher.rb#L69-L72
My understanding now is that implementing this would be a separate feature that would allow dependabot to also update actions' dependencies of reusable workflows that live in the same repository being updated but in non-standard locations. Is this correct?

My understanding now is that implementing this would be a separate feature that would allow dependabot to also update actions' dependencies of reusable workflows that live in the same repository being updated but in non-standard locations. Is this correct?

Are reusable workflows allowed to live in "non-standard" locations in a repo? All the examples I see in the docs point at paths under .github/workflows...
Ref: https://docs.github.com/en/actions/using-workflows/reusing-workflows

I have no idea, I assumed since they are pointed to directly by file path, that they could live anywhere. But you're totally right that the docs seem to indicate the opposite. Well, that's great then, less work for us. Should we remove the TODO then?

I have no idea, I assumed since they are pointed to directly by file path, that they could live anywhere. But you're totally right that the docs seem to indicate the opposite. Well, that's great then, less work for us. Should we remove the TODO then?

I would think removing it would be appropriate.  The files are correctly being fetched from the ".github/workflows" directory, the only issue is it was looking for the "steps" hash for "uses", where with the new reusable actions the "uses" key can be many places under "jobs" including "steps".

Are reusable workflows allowed to live in "non-standard" locations in a repo? All the examples I see in the docs point at paths under .github/workflows...

Yes. Reusable workflows work from any location.

🤣 Ok, I'll remove the latest commit and reticket support that then.

Are reusable workflows allowed to live in "non-standard" locations in a repo? All the examples I see in the docs point at paths under .github/workflows...

Yes. Reusable workflows work from any location.

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iduses
Do you have a reference for this? the docs indicate differently, if there is documentation that says otherwise please link.
Calling a reusable workflow
You call a reusable workflow by using the uses keyword. Unlike when you are using actions within a workflow, you call reusable workflows directly within a job, and not from within job steps.
jobs.<job_id>.uses
You reference reusable workflow files using one of the following syntaxes:
{owner}/{repo}/.github/workflows/{filename}@{ref} for reusable workflows in public and private repositories.
./.github/workflows/{filename} for reusable workflows in the same repository.

Are reusable workflows allowed to live in "non-standard" locations in a repo? All the examples I see in the docs point at paths under .github/workflows...

Yes. Reusable workflows work from any location.

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iduses Do you have a reference for this? the docs indicate differently, if there is documentation that says otherwise please link.
Calling a reusable workflow You call a reusable workflow by using the uses keyword. Unlike when you are using actions within a workflow, you call reusable workflows directly within a job, and not from within job steps.
jobs.<job_id>.uses
You reference reusable workflow files using one of the following syntaxes:
{owner}/{repo}/.github/workflows/{filename}@{ref} for reusable workflows in public and private repositories. ./.github/workflows/{filename} for reusable workflows in the same repository.

Tested it out and turns out I'm wrong. I swear I had done this previously, but I guess not.

Are reusable workflows allowed to live in "non-standard" locations in a repo? All the examples I see in the docs point at paths under .github/workflows...

Yes. Reusable workflows work from any location.

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iduses Do you have a reference for this? the docs indicate differently, if there is documentation that says otherwise please link.
Calling a reusable workflow You call a reusable workflow by using the uses keyword. Unlike when you are using actions within a workflow, you call reusable workflows directly within a job, and not from within job steps.
jobs.<job_id>.uses
You reference reusable workflow files using one of the following syntaxes:
{owner}/{repo}/.github/workflows/{filename}@{ref} for reusable workflows in public and private repositories. ./.github/workflows/{filename} for reusable workflows in the same repository.

Tested it out and turns out I'm wrong. I swear I had done this previously, but I guess not.

Thanks for testing it and letting us know.  @deivid-rodriguez I think we are good and due diligence has been done at this point.

Alright, I will move this forward in the following days.

Alright, this is now live! Let me know if you find any issues and thanks for the fantastic contribution ❤.

Alright, this is now live! Let me know if you find any issues and thanks for the fantastic contribution ❤.

Thank you for the quick reviews, refactors and merge!


update /packages/@vue/cli-plugin-unit-mocha README

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[x] Docs
[ ] Underlying tools
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

Other information:
Update pacakge name from "unit-mocha" to "@vue/cli-plugin-unit-mocha"

vue add unit-mocha is available since Vue CLI 3.11+.


dwarf: missing type: type.runtime.eface

What version of Go are you using (go version)?

$ go version
go version go1.15.2 linux/amd64

What operating system and processor architecture are you using (go env)?

Tried to compile snapd.
What did you expect to see?
Build successful.
What did you see instead?
# github.com/snapcore/snapd/cmd/snap
/usr/lib/go/pkg/tool/linux_amd64/link: dwarf: missing type: type.runtime.eface

I am unable to reproduce this on my work machine (Debian/amd64) using Go 1.15.2.  Is there anything unusual about your configuration?  The error in question seems very improbable; "eface" is a key type used in the Go runtime -- if the linker can't find a type descriptor for it, this suggests a damaged/corrupted installation (bad runtime.a).


nixos/kanata: test enabling kanata using nixos-rebuild switch

This is a minimal reproducible example for https://github.com/NixOS/nixpkgs/issues/317282.
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg test kanata
The test is indented to fail.  A proper fix is under discussion.

Merge conflicts are resolved.


More graphQL

Required for https://github.com/opencollective/frontend/pull/98

Coverage increased (+0.09%) to 77.064% when pulling 2f9b8cbcfa3ae637af9c9cb1d3a975c31662b86d on moreGraphQL into 7aee4ffea55b4ebf6b0a97fb9ef9c0951300fe0c on master.


#391 add parameter to lifecycle controller

fixes #391

Current coverage is 46.84%

Merging #393 into master will increase coverage by +0.24% as of 819ef40

@@            master    #393   diff @@
======================================
  Files          127     127
  Stmts         2935    2952    +17
  Branches       238     239     +1
  Methods          0       0
======================================
+ Hit           1368    1383    +15
  Partial         57      57
- Missed        1510    1512     +2

Review entire Coverage Diff as of 819ef40

Powered by Codecov. Updated on successful CI builds.

👍

👍

:+1:

👍 but link the new readme to the main readme plz

@mrandi done via #394

:+1:


Error when extracting from Ground Zero (Emercom and Nakatami)

General information:
Project issue is for:
Server
Expected result:
Successful exfil
Actual result:
Error shown
"In response to http://127,0,0,1:6969/client/items:
Object reference not set to an instance of an object"
How to reproduce:

Unclear, still trying to reproduce, happened twice within about 4 raids
Best guess is having a backpack and vest inside another backpack caused the issue

Attachments

server-2024-02-03.log (951 KiB)
LogOutput.log (8 KiB)
2024.02.03_14-25-22_<IP_ADDRESS>.28476 traces.log (39 KiB)
20240203_152208.jpg (3491 KiB)
profile.txt (308 KiB)

Originally written by Hupfi

Extracted at least 50 times through one or another. Didn't get that error.

Originally written by ItsRenke

Unable to reproduce currently

Originally written by chomp

Unable to reproduce currently

I've been trying to reproduce it till yesterday. Wasn't successful. I dunno, tried in a lot of ways, can't repro.

Originally written by ItsRenke

Also tried yesterday to reproduce, without sucess.

Originally written by halik92


utf8 parsing allows numbers larger that a Float to be "successfully" parsed.

I noticed testFloat fails on my local machines (M1 & Intel, Big Sur 11.3 Betas, release Xcode):
    input = "1234567890123456789012345678901234567890 Hello"[...].utf8
    XCTAssertEqual(nil, parser.parse(&input))
    XCTAssertEqual("1234567890123456789012345678901234567890 Hello", String(input))

Parsing consumes the number, returning: Optional(inf).
It doesn't appear to fail on CI…?
Maybe something like this to protect against overflows: https://github.com/pointfreeco/swift-parsing/pull/25

UInt8("1234567890123456789012345678901234567890") // nil
Float("1234567890123456789012345678901234567890") // inf

I'm only seeing this in Xcode 12.5 Betas at the moment. Probably worth ignoring for now. :)

Closed in favour of following Apple and letting inf be successfully parsed.


[Do Not Merge] Added question to select location of business

:rotating_light: Do not merge until Mark Woods approves :rotating_light:
What

Adds a new question, dependent on "owning a business" the user will be asked where their business is located
Adds new criteria to criteria tab (allows checks to pass)
Updates integration tests
Updates wording

Why
It will allow for more targeted advice and fewer irrelvant results where guidance differs based on business location.
https://trello.com/b/ZPYiKNQV/doing-govuk-brexit-content-team

Was coopted into https://github.com/alphagov/finder-frontend/pull/2136, thanks @huwd


Fix a link to Underscore.

Fixed in https://github.com/baconjs/bacon.js/commit/0e535ee56112110bac860dd4719a108f1dc10525


Add the possibility of not managing bridges

Create 2 new vars MANAGE_PRO_BRIDGE and MANAGE_INT_BRIDGE. If those
are set to n, the scripts won't try to recreate the bridges, but
leave the ones that are already created on the host.
This is useful for specific configurations where settings
cannot be overwritten.

Build SUCCESS, see build http://<IP_ADDRESS>:8080/job/dev-tools/481/

Looks fine to me - I saw some discussion with @celebdor so wanted to give him the chance to review, but if he's happy then lgtm.


I can't see my maze in the list

Hi,
I tried your plugin, I partially built a maze, I drawed the path around it. When I try to open the menu of the mod, I just cannot see my maze in the list.

Thanks!

Hey, thank for trying my plugin.
I cannot replicate this bug tho. Can I have the save file?

Hi,
Fun fact, I tried a few things and I found the glitch. I switched my game from french to english and now I see my maze in the list.
I tried to switch back again to french, it diseappeared (whether my maze is called "maze 1" or "labyrinthe 1".

So yeah, maybe it comes from the way your plugin searchers for mazes.

I did use "ride object name" to filter maze. Thank for info.


RTL Support

Describe the Feature
The slider works but in LTR on RTL forced apps. It would be great to support RTL.

try this:
import { I18nManager } from 'react-native';
const styles = StyleSheet.create({
    ttb: { transform: [{ rotate: '90deg' }] },
    btt: { transform: [{ rotate: '-90deg' }] },
    rtl: { transform: [{ scale: -1 }] },
    auto: I18nManager.isRTL ? { transform: [{ scale: -1 }] } : {},
    sliderContainer: {
        flex: 1,
        justifyContent: "center"
    },
});

<View style={[styles.auto, styles.sliderContainer]}><Slider /></View>

If you'd like to have this functionality supported out of the box, please consider sending a PR. As for now, you can use this workaround:
import { I18nManager } from 'react-native';
...
<Slider inverted={I18nManager.isRTL} />

The inverted prop didn't work for me.
I added  style={{direction:"ltr"}} to the  Slider component .


feat(linter) eslint plugin unicorn: prefer includes

Current dependencies on/for this PR:

main

PR #1463

PR #1464

PR #1465

PR #1466

PR #1467

PR #1469

PR #1470

PR #1471   👈

This stack of pull requests is managed by Graphite.

Merge activity

Nov 20, 9:02 PM: @Boshen started a stack merge that includes this pull request via Graphite.


Fix compilation with CPython 3.12a6

CPython 3.12a6 made PyThreadState an opaque structure thus the fast thread state optimization cannot be employed anymore.
Fixes #5286.

That's what we did in 0.29.x. However, for 3.0, I'd rather have a more efficient solution.

That said, we can still disable it until we have a better solution. That unblocks users who want to test with Py3.12.

Thanks

Thanks @scoder I haven't recently tried the 0.29.x branch tip, but till recently 0.29 did not work on CPython 3.12: some fixes present only on master were necessary. Now I see that the equivalent of this fix was applied to the 0.29.x branch over a year ago. It seems that the CPython compatibility state of the two branches diverged a bit over time.
I would be happy to work on the better solution, but I'm not sure about what kind of dirty tricks is allowed to play in Cython to get access to the CPython internals. I can have a look at this if you point me to some "prior art" in this domain.

One more thing: it seems that CI was passing on CPython 3.12a6 without this patch. Do the tests need to be tightened up somehow to catch this kind of issues?

One more thing: it seems that CI was passing on CPython 3.12a6 without this patch. Do the tests need to be tightened up somehow to catch this kind of issues? Without this patch the compilation of very simple code fails for me.

3.12 is deliberately set as an allowed failure until it's released (so looks like it passed). The tests will almost certainly not be passing if you look in more details. We expect it to get broken multiple times before release and don't really want that to block things like the recent Cython beta release

It seems that the CPython compatibility state of the two branches diverged a bit over time.

In the sense that 0.29.x is the legacy, boring, conservative branch where we avoid changes if possible and prefer disabling optimisations over risking breakage of existing code or requiring new releases all the time. 3.0 has a different goal where we try to improve the performance and adapt to changes in CPython.


Create lpr engine file

Hi, I am working on License plate recognition problem. When I run deepstream app i am facing following issue.
**Starting pipeline
0:00:00.209260524   226      0x1a87b20 INFO                 nvinfer gstnvinfer.cpp:638:gst_nvinfer_logger: NvDsInferContext[UID 3]: Info from NvDsInferContextImpl::buildModel() <nvdsinfer_context_impl.cpp:1914> [UID = 3]: Trying to create engine from model files
WARNING: [TRT]: onnx2trt_utils.cpp:364: Your ONNX model has been generated with INT64 weights, while TensorRT does not natively support INT64. Attempting to cast down to INT32.
WARNING: [TRT]: ShapedWeights.cpp:173: Weights td_dense/kernel:0 has been transposed with permutation of (1, 0)! If you plan on overwriting the weights with the Refitter API, the new weights must be pre-transposed.
WARNING: [TRT]: Tensor DataType is determined at build time for tensors not marked as input or output.
WARNING: [TRT]: Detected invalid timing cache, setup a local cache instead
python3: /dvs/p4/build/sw/rel/gpgpu/MachineLearning/myelin_trt8/src/compiler/optimizer/cublas_impl.cpp:477: void add_heuristic_results_to_tactics(std::vector<cublasLtMatmulHeuristicResult_t>&, std::vectormyelin::ir::tactic_attribute_t&, myelin::ir::tactic_attribute_t&, bool): Assertion `false && "Invalid size written"' failed.
Aborted (core dumped)**
I am using DS 6.0. Can anyone please help me on how to solve this issue?

@vinodbukya6 @sujitbiswas
0:00:01.256299095 30248      0x3a1bca0 WARN                 nvinfer gstnvinfer.cpp:635:gst_nvinfer_logger: NvDsInferContext[UID 3]: Warning from NvDsInferContextImpl::deserializeEngineAndBackend() <nvdsinfer_context_impl.cpp:1889> [UID = 3]: deserialize engine from file :/opt/nvidia/deepstream/deepstream-6.0/sources/deepstream_python_apps/deepstream_lpr_app/models/LP/LPR/us_lprnet_baseline18_deployable.etlt_b16_gpu0_fp16.engine failed
0:00:01.256360773 30248      0x3a1bca0 WARN                 nvinfer gstnvinfer.cpp:635:gst_nvinfer_logger: NvDsInferContext[UID 3]: Warning from NvDsInferContextImpl::generateBackendContext() <nvdsinfer_context_impl.cpp:1996> [UID = 3]: deserialize backend context from engine from file :/opt/nvidia/deepstream/deepstream-6.0/sources/deepstream_python_apps/deepstream_lpr_app/models/LP/LPR/us_lprnet_baseline18_deployable.etlt_b16_gpu0_fp16.engine failed, try rebuild
0:00:01.256391192 30248      0x3a1bca0 INFO                 nvinfer gstnvinfer.cpp:638:gst_nvinfer_logger: NvDsInferContext[UID 3]: Info from NvDsInferContextImpl::buildModel() <nvdsinfer_context_impl.cpp:1914> [UID = 3]: Trying to create engine from model files
WARNING: [TRT]: onnx2trt_utils.cpp:364: Your ONNX model has been generated with INT64 weights, while TensorRT does not natively support INT64. Attempting to cast down to INT32.
WARNING: [TRT]: ShapedWeights.cpp:173: Weights td_dense/kernel:0 has been transposed with permutation of (1, 0)! If you plan on overwriting the weights with the Refitter API, the new weights must be pre-transposed.
WARNING: [TRT]: Tensor DataType is determined at build time for tensors not marked as input or output.
WARNING: [TRT]: Detected invalid timing cache, setup a local cache instead
python3: /dvs/p4/build/sw/rel/gpgpu/MachineLearning/myelin_trt8/src/compiler/optimizer/cublas_impl.cpp:477: void add_heuristic_results_to_tactics(std::vector<cublasLtMatmulHeuristicResult_t>&, std::vectormyelin::ir::tactic_attribute_t&, myelin::ir::tactic_attribute_t&, bool): Assertion `false && "Invalid size written"' failed.
Aborted (core dumped)
The same error I am also facing.

In DS 6.0 when I am running make command, it is failing
root@c79ec6aed68e:/opt/nvidia/deepstream/deepstream-6.0/sources/deepstream_python_apps/deepstream_lpr_ap
p# make
make[1]: Entering directory '/opt/nvidia/deepstream/deepstream-6.0/sources/deepstream_python_apps/deepstream_lpr_app/nvinfer_custom_lpr_parser'
g++ -o libnvdsinfer_custom_impl_lpr.so nvinfer_custom_lpr_parser.cpp -Wall -Werror -std=c++11 -shared -fPIC -Wno-error=deprecated-declarations -I/opt/nvidia/deepstream/deepstream/sources/includes -Wl,--start-group -lnvinfer -lnvparsers -Wl,--end-group
/usr/bin/ld: cannot find -lnvinfer
/usr/bin/ld: cannot find -lnvparsers
collect2: error: ld returned 1 exit status
Makefile:37: recipe for target 'libnvdsinfer_custom_impl_lpr.so' failed
make[1]: *** [libnvdsinfer_custom_impl_lpr.so] Error 1
make[1]: Leaving directory '/opt/nvidia/deepstream/deepstream-6.0/sources/deepstream_python_apps/deepstream_lpr_app/nvinfer_custom_lpr_parser'
Makefile:2: recipe for target 'all' failed
make: *** [all] Error 2

Hi, edit -L -lnvinfer -L -lnvparsers in Makefile and make. It works fine.

@vinodbukya6
so after make,
it worked for you??
i.e. you are not getting this issue.
python3: /dvs/p4/build/sw/rel/gpgpu/MachineLearning/myelin_trt8/src/compiler/optimizer/cublas_impl.cpp:477: void add_heuristic_results_to_tactics(std::vector<cublasLtMatmulHeuristicResult_t>&, std::vectormyelin::ir::tactic_attribute_t&, myelin::ir::tactic_attribute_t&, bool): Assertion `false && "Invalid size written"' failed.

@vinodbukya6 we you able to resolve
python3: /dvs/p4/build/sw/rel/gpgpu/MachineLearning/myelin_trt8/src/compiler/optimizer/cublas_impl.cpp:477: void add_heuristic_results_to_tactics(std::vector<cublasLtMatmulHeuristicResult_t>&, std::vectormyelin::ir::tactic_attribute_t&, myelin::ir::tactic_attribute_t&, bool): Assertion false && "Invalid size written"' failed.`

Yeah, I am also facing the same issue. Not solved.

Hi @imSrbh, Any updates on the issue. Got any leads?

Hi, LPR engine file created using tlt-converter and followed mentioned steps.
Deepstream 5.1, cuda 11.1, TensorRT 7.2.
It's working fine for command:
python3 deepstream_lpr_app.py 1 2 0 file:///opt/nvidia/deepstream/deepstream-5.1/samples/streams/lpr-test1.mp4 out.mp4
Thank you so much.


xDS Interop Client changes for PSM security tests

Add a cmd line flag --security which if set to secure should make the client use XdsCredentials

Thanks for reviewing!


[docs/rfcs] Aligned Timestamps

Rendered

Current coverage is 44.73% (diff: 100%)

Merging #208 into master will not change coverage

@@             master       #208   diff @@
==========================================
  Files           622        622
  Lines         16167      16167
  Methods           0          0
  Messages          0          0
  Branches       1636       1636
==========================================
  Hits           7233       7233
  Misses         8470       8470
  Partials        464        464

Powered by Codecov. Last update caf70b3...350b206

LGTM


nRF5 SDK for Thread example does not work with nrf_cc310 lib

Hi,
I cannot run openthread example with change (add cryptocell support (#2628)):
https://github.com/openthread/openthread/commit/996be6e1474d405fdb10e83ce7d50c2a80fad6db
Example from nRF5 SDK for Thread (nRF5_SDK_for_Thread/examples/thread/experimental/freertos_coap_server) does not work when linking with openthread/third_party/NordicSemiconductor/libraries/nrf_cc310/lib/libnrf_cc310_0.9.9.a
The change I've made in example's Makefile:
removed lines:
$(SDK_ROOT)/external/openthread/lib/gcc/libmbedcrypto-cc310.a \ $(SDK_ROOT)/external/nrf_cc310/lib/libcc310_gcc_0.9.0.a \
added lines:
$(SDK_ROOT)/../openthread/build-node/nrf52840/third_party/mbedtls/libmbedcrypto.a \ $(SDK_ROOT)/../openthread/third_party/NordicSemiconductor/libraries/nrf_cc310/lib/libnrf_cc310_0.9.9.a \
The program hangs on call to PlatformInit
Any ideas how to make it working?

Hello @kbogucki.
The new version of nRF5 SDK for Thread is going to be released in a few days maybe tomorrow) with your specific example fixed.
For the time being, can you try move all platform initialization out of FreeRTOS task, and call it from the main function, before FreeRTOS's thread is created?

Hi @LuDuda,
Moving platform init to main function solved the problem.
Thanks for your help.
Waiting for new SDK.
Regards,
Krzysztof


[Loc] sql xlf update 9-21-2022

This PR fixes #

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 42.442%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
29239

Relevant Lines:
64081

💛  - Coveralls


backend_test.py remove scipy.sparse

remove scipy.sparse as it doesn't appear to be utilized in this file

🎉 🍾 Travis passes again! Merging


Quoted alias_maps fail on RHEL6/postfix 2.6.6

Quotes around alias_maps on RHEL6/postfix 2.6.6 don't work. Do they on other OSes?

-alias_maps = hash:/etc/aliases
+alias_maps = "hash:/etc/aliases, ldap:/etc/postfix/ldap-aliases.cf"

Postfix error in /var/log/maillog:

Feb  4 16:26:07 ncc16405 postfix/smtpd[9529]: fatal: unsupported dictionary type: "hash
Feb  4 16:26:08 ncc16405 postfix/master[9523]: warning: process /usr/libexec/postfix/smtpd pid 9529 exit status 1
Feb  4 16:26:08 ncc16405 postfix/master[9523]: warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling

http://www.postfix.org/postconf.5.html:
alias_maps (default: see "postconf -d" output)
The alias databases that are used for local(8) delivery. See aliases(5) for syntax details. Specify zero or more "type:name" lookup tables, separated by whitespace or comma. Tables will be searched in the specified order until a match is found. Note: these lookups are recursive.
The default list is system dependent. On systems with NIS, the default is to search the local alias database, then the NIS alias database.
If you change the alias database, run "postalias /etc/aliases" (or wherever your system stores the mail alias file), or simply run "newaliases" to build the necessary DBM or DB file.
The local(8) delivery agent disallows regular expression substitution of $1 etc. in alias_maps, because that would open a security hole.
The local(8) delivery agent will silently ignore requests to use the proxymap(8) server within alias_maps. Instead it will open the table directly. Before Postfix version 2.2, the local(8) delivery agent will terminate with a fatal error.
Examples:
alias_maps = hash:/etc/aliases, nis:mail.aliases
alias_maps = hash:/etc/aliases

Discussion on this is in #74

@phathocker I think https://github.com/camptocamp/puppet-postfix/pull/74 fixed this bug, so I close this issue. Feel free to reopen if it is still relevant.

Thanks!


[CREATE CHART] Validation on chart name

Description
Appropriate validation messaging on Name* input :

It was an old branch..


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_d4ftcyrq_f/clone/recipe/meta.yaml:22: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_d4ftcyrq_f/clone/recipe/meta.yaml:58: missing_license_family: The recipe is missing the about/license_family key.
Errors were found


AANTS Redesign

Summary

This is just a WIP. This currently sends an email from the AntAlmanac account to itself. To test sending an email, click on the "SES Test" button next to the "Past Enrollment" button.

Tasks

[x] Set up backend endpoint.
[ ] Resolve Access Denied error. I had to add some IAM permissions for this staging instance in order to access SES, so we need to make sure everything else has SES access.
[ ] Add ability to send email to any user, not just any verified SES email address. This requires an application for a production SES account.

Test Plan
Issues
Closes #

gonna close this cause we're pivoting to web push notifications. If we ever want to add SMS later we can reference this.


"Navigation bar" setting does not survive VS restart

Set Navigation bar [x]
Nav bar appears
Restart VS
Nav bar is absent, the setting is off

@TIHan we should look at this as well.
Context: we were looking at this and #4087 as a part of making the Automatic brace completion option enabled so that you can toggle it on/off for #4049. It's awfully tricky business, since it requires some digging to find the right interface to implement. But our goal (hopefully for 15.8 if we can swing it) is:

Navigation bars and Smart on by default
Automatic brace completion enabled to be toggled
Now, making sure that this setting is respected as well.

It's a bit strange that it wouldn't be respected since VS settings should not back off to a default per session, IIRC 😕