feat: recovery from VolumeSnapshot, and kubectl-cnpg snapshot subcommand

This is a POC demonstrating what can be obtained by using CSI VolumeSnapshot resources to backup and restore CloudNativePG clusters.
A snapshot can be created with:
$ ./bin/kubectl-cnpg snapshot cluster-example -c longhorn
waiting for cluster-example-3 to be fenced
waiting for VolumeSnapshot cluster-example-3-1682433701 to be ready to use
waiting for VolumeSnapshot cluster-example-3-wal-1682433701 to be ready to use
unfencing pod cluster-example-3

And later restored with:
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
  name: cluster-restore
spec:
  instances: 3

  storage:
    size: 1Gi
  walStorage:
    size: 1Gi

  bootstrap:
    recovery:
      dataSource:
        storage:
          name: cluster-example-3-1682433701
          kind: VolumeSnapshot
          apiGroup: snapshot.storage.k8s.io

        walStorage:
          name: cluster-example-3-wal-1682433701
          kind: VolumeSnapshot
          apiGroup: snapshot.storage.k8s.io

Closes: #1968

Reviewed the documentation. This is great. I see no reason why this feature should not work for PITR or replica clusters, provided we have a valid WAL archive in a recovery object store. This is the reason why I have removed for now this kind of limitations from the proposed documentation. If they don't work, it should just be due to validation or guards put by the operator, but from a Postgres PoV they should simply work.


Unable to build shogun's python interface

Hi, I have been trying to build shogun's python interface from source code. But, I always get the following error message (I have turned on verbose for the make command. Hence the lengthy messages):
[ 74%] Built target python_doxy2swig
make -f src/interfaces/python/CMakeFiles/interface_python_src.dir/build.make src/interfaces/python/CMakeFiles/interface_python_src.dir/depend
make[2]: Entering directory '/media/Rukman/IIT_B/gumption/shogun/build_python'
cd /media/Rukman/IIT_B/gumption/shogun/build_python && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /media/Rukman/IIT_B/gumption/shogun /media/Rukman/IIT_B/gumption/shogun/src/interfaces/python /media/Rukman/IIT_B/gumption/shogun/build_python /media/Rukman/IIT_B/gumption/shogun/build_python/src/interfaces/python /media/Rukman/IIT_B/gumption/shogun/build_python/src/interfaces/python/CMakeFiles/interface_python_src.dir/DependInfo.cmake --color=
make[2]: Leaving directory '/media/Rukman/IIT_B/gumption/shogun/build_python'
make -f src/interfaces/python/CMakeFiles/interface_python_src.dir/build.make src/interfaces/python/CMakeFiles/interface_python_src.dir/build
make[2]: Entering directory '/media/Rukman/IIT_B/gumption/shogun/build_python'
[ 74%] copying SWIG files
make[2]: Leaving directory '/media/Rukman/IIT_B/gumption/shogun/build_python'
[ 74%] Built target interface_python_src
make -f src/interfaces/python/CMakeFiles/_interface_python.dir/build.make src/interfaces/python/CMakeFiles/_interface_python.dir/depend
make[2]: Entering directory '/media/Rukman/IIT_B/gumption/shogun/build_python'
[ 75%] Swig source
cd /media/Rukman/IIT_B/gumption/shogun/build_python/src/interfaces/python && /usr/bin/cmake -E make_directory /media/Rukman/IIT_B/gumption/shogun/build_python/src/interfaces/python
cd /media/Rukman/IIT_B/gumption/shogun/build_python/src/interfaces/python && /usr/bin/swig3.0  -python -builtin -modern -modernargs -threads -w473 -w454 -w312 -w325 -fvirtual -outdir /media/Rukman/IIT_B/gumption/shogun/build_python/src/interfaces/python -c++ -I/usr/include/python2.7 -I/usr/lib/python2.7/dist-packages/numpy/core/include -I/media/Rukman/IIT_B/gumption/shogun/src -I/media/Rukman/IIT_B/gumption/shogun/build_python/src -I -I/media/Rukman/IIT_B/gumption/shogun/src/gpl -I/media/Rukman/IIT_B/gumption/shogun/build_python/StanMath/src/StanMath -I -I/media/Rukman/IIT_B/gumption/shogun/build_python/StanMath/src/StanMath/lib/boost_1.66.0 -I -I/media/Rukman/IIT_B/gumption/shogun/build_python/StanMath/src/StanMath/lib/sundials_3.1.0/include -I -I/media/Rukman/IIT_B/gumption/shogun/build_python/StanMath/src/StanMath/lib/eigen_3.3.3 -I -I/media/Rukman/IIT_B/gumption/shogun/build_python/src/shogun/third_party -I -I/media/Rukman/IIT_B/gumption/shogun/build_python/src/shogun/third_party/variant -I -I/usr/include -I/usr/include/json-c -I/usr/include/libxml2 -I/usr/include/hdf5/serial -o /media/Rukman/IIT_B/gumption/shogun/build_python/src/interfaces/python/shogunPYTHON_wrap.cxx /media/Rukman/IIT_B/gumption/shogun/build_python/src/interfaces/python/shogun.i
shogun_doxygen.i:612: Error: Syntax error in input(1).
src/interfaces/python/CMakeFiles/_interface_python.dir/build.make:64: recipe for target 'src/interfaces/python/shogunPYTHON_wrap.cxx' failed
make[2]: *** [src/interfaces/python/shogunPYTHON_wrap.cxx] Error 1
make[2]: Leaving directory '/media/Rukman/IIT_B/gumption/shogun/build_python'
CMakeFiles/Makefile2:475: recipe for target 'src/interfaces/python/CMakeFiles/_interface_python.dir/all' failed
make[1]: *** [src/interfaces/python/CMakeFiles/_interface_python.dir/all] Error 2
make[1]: Leaving directory '/media/Rukman/IIT_B/gumption/shogun/build_python'
Makefile:154: recipe for target 'all' failed
make: *** [all] Error 2

I have looked at the 612 line of the shogun_doxygen.i file but I am not sure I understand the error generated. I am also posting the shogun_doxygen.i file as a gist.
Thanks in advance for the help :)

Hi, are you using the latest develop? This issue should have been fixed a few commits ago..

I was not. Thank you. Will rebase to the newest commit and try again.

Thanks alot @gf712 . I am closing this issue.

Hey, I met the same error when I run 'make' after 'cmake'. How did you solve it?

Hi, doxygen doesn't seem to support all modern c++ syntax and we don't test it in the CI.. so maybe at some point someone introduced a "bug" after this issue was fixed.
You could disable doxygen. I'll have a look into it.

Thanks a lot @gf712 ! I will have a try.

By the way, how can I disable doxygen? @gf712 I uninstall doxygen and 'cmake' command said it need doxygen.

If you uninstalled it now you need to remove CMakeCache.txt in the build folder and run cmake again. Then cmake should run fine!

@gf712 Thanks! This problem was solved. But I met a new error when I run 'make' command, here is the error message about new problem:
[ 91%] Built target cpp-kernel-auc
[ 91%] Linking CXX executable distance/cpp-distance-manhattan
[ 91%] Built target cpp-distance-manhattan
[ 91%] Linking CXX executable kernel/cpp-kernel-anova
[ 91%] Built target cpp-kernel-anova
[ 91%] Linking CXX executable kernel/cpp-kernel-chi2
[ 91%] Built target cpp-kernel-chi2
[ 91%] Linking CXX executable kernel/cpp-kernel-log
[ 91%] Built target cpp-kernel-log
[ 91%] Linking CXX executable neural_nets/cpp-neural_nets-feedforward_net_classification
[ 91%] Built target cpp-neural_nets-feedforward_net_classification
[ 91%] Linking CXX executable evaluation/cpp-evaluation-cross_validation
[ 91%] Built target cpp-evaluation-cross_validation
[ 91%] Linking CXX executable meta_api/cpp-meta_api-calls
[ 91%] Built target cpp-meta_api-calls
[ 91%] Building CXX object examples/meta/cpp/CMakeFiles/cpp-meta_api-literals.dir/meta_api/literals.cpp.o
/home/zhangjing/packages/shogun/build/UILD_META_EXAMPLES=ON/examples/meta/cpp/meta_api/literals.cpp:5:25: error: ‘io’ is not a namespace-name
using namespace shogun::io;
^~
/home/zhangjing/packages/shogun/build/UILD_META_EXAMPLES=ON/examples/meta/cpp/meta_api/literals.cpp:5:27: error: expected namespace-name before ‘;’ token
using namespace shogun::io;
^
examples/meta/cpp/CMakeFiles/cpp-meta_api-literals.dir/build.make:62: recipe for target 'examples/meta/cpp/CMakeFiles/cpp-meta_api-literals.dir/meta_api/literals.cpp.o' failed
make[2]: *** [examples/meta/cpp/CMakeFiles/cpp-meta_api-literals.dir/meta_api/literals.cpp.o] Error 1
CMakeFiles/Makefile2:5592: recipe for target 'examples/meta/cpp/CMakeFiles/cpp-meta_api-literals.dir/all' failed
make[1]: *** [examples/meta/cpp/CMakeFiles/cpp-meta_api-literals.dir/all] Error 2
Makefile:151: recipe for target 'all' failed
make: *** [all] Error 2
Do you have any idea about this question? I'm sorry to disturb you again but I have no idea about this.

@VisintZJ unfortunately this is "known" as in that specific meta example cpp no headers are included that contains the shogun::io namespace, hence the error. The are several ways to fix this in your case the easiest temporary solution is that simply remove the specific line from examples/meta/cpp/meta_api/literals.cpp and do a make again

@VisintZJ for the literals.cpp i've created a separate bug #4770

@vigsterkr Thank you very much! The problem has been solved after I remove that line and I have ‘make’ successfully. Thanks for your patient answers！ @gf712


FilterShowcase shows nothing when a filter name is clicked

I just downloaded this project. Opened up FilterShowcase in Xcode 8, clicked on one of the filters in list table in my iOS simulator and then it shows page with just a scroll bar. The page is blank. Where is a preview of image something? Comeon people at least have a working example.

You wouldn't happen to be running this in the Simulator, are you? The Simulator doesn't have proper camera support, and these examples all run through the device camera's input.

Yes, I was using iOS simulator. I didn't know that this would only work on real device. Perhaps there needs to be a check to sees if its a simulator then show a pop-up to tell the user to run it on actual device. Or better yet if it finds that this example is run on a simulator then instead of launching camera it applies those effects to a static image provided within the project. Just a suggestion. Though thanks for replying quickly.


Containerize your microservice using Docker

As a microservice developer
I need to containerize my microservice using Docker
So that the microservice can be easily deployed and scaled across different environments
Details and Assumptions
Docker is chosen as the containerization platform.
The microservice is properly configured for Docker.
Acceptance Criteria :
Given my microservice is properly configured
When I build a Docker image
Then the image should include all necessary dependencies and configurations


NSX: Fix code smells and reported bugs

Description
This PR...

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

How did you try to break this feature and the system with this change?

@blueorangutan package

@Pearl1594 a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 8165


Update Serenity BDD CLI to version >= version 3.9.8

Serenity BDD CLI should be updated to the latest version >= 3.2.0.
There was an attempt in #1129 but there was a regression in 3.1.1 (see #1133) and downgrade to 3.1.0 was necessary. Update to version > 3.1.0 is blocked by https://github.com/serenity-bdd/serenity-core/pull/2721.

Retest today with Serenity BDD CLI v 3.2.5, issue is not solved.

Blocked by https://github.com/serenity-bdd/serenity-core/issues/3214

Adding Serenity BDD 4.0.19 JSON output for reference
screenplay-tests.zip


Vertical display bar code

Whether vertical display barcode is considered

Do you have any results? May I ask how to operate it.


Update CashManager For Performance Improvements

Description

The performance did not come out properly due to read locking, Improve performance by changing mutual exclusion methods
Can operate within 600 ms when writing 100 and reading 10000 at the same time
Whether mutual exclusion is complete requires a different verification method.

Self LGTM


optim : remove useless call to SyntaxTreeCleaner.SetAssociativity whe…

…n no operation attributes were used

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

5 of 5 (100.0%)  changed or added relevant lines in 5 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.2%) to 88.325%

Files with Coverage Reduction
New Missed Lines
%

sly/parser/parser/SyntaxTreeCleaner.cs
1
63.71%

Totals

Change from base Build<PHONE_NUMBER>:
0.2%

Covered Lines:
4670

Relevant Lines:
5226

💛  - Coveralls


Usage of streams causing file descriptor leak

Describe the bug
I am attempting to make a SvelteKit API endpoint that makes a request to another backend API and streams the response body of its own response body, using fetch and response.body, like so:
// `filterHeaders` is simply a function to filter only some desired headers.

/** @type {import('./$types').RequestHandler} */
export async function GET(event) {
    const requestHeaders = filterHeaders(event.request.headers, ['range']);
    const response = await fetch('http://example.com/some/example/endpoint', {
        signal: event.request.signal,
        headers: requestHeaders,
    });
    const responseHeaders = filterHeaders(
        response.headers,
        ['content-length', 'content-type', 'content-range', 'accept-ranges'],
    );
    return new Response(response.body, {
        status: response.status,
        statusText: response.statusText,
        headers: responseHeaders,
    });
}

While this code works, it seems to leak a file descriptor each time it is requested, especially in the context of HTTP range requests while playing video content.
I have tried many variations of this code, like using pipeThrough or pipeTo, using the pipeline function from the node:stream/promises module, or using axios to make the request and converting the body back to a ReadableStream, but all of them demonstrated the issue, which prompts to me that maybe its the @sveltejs/adapter-node that doesn't close the response stream properly.
After some time, this issue leads to my app being unable to fulfil new requests, and the node process must be restarted.
Reproduction
I have made a minimal demo app to demonstrate the issue here:
https://github.com/Hirevo/sveltekit-stream-issue
The index page has steps of how to observe the issue, using lsof.
Logs
No response
System Info
System:
  OS: macOS 14.4.1
  CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
  Memory: 411.48 MB / 16.00 GB
  Shell: 0.1.0 - /Users/nicolaspolomack/.cargo/bin/psh
Binaries:
  Node: 22.0.0 - ~/.local/state/fnm_multishells/18305_1714256923846/bin/node
  Yarn: 1.22.22 - /usr/local/bin/yarn
  npm: 10.5.1 - ~/.local/state/fnm_multishells/18305_1714256923846/bin/npm
Browsers:
  Chrome: 124.0.6367.91
  Safari: 17.4.1
  Safari Technology Preview: 17.4
npmPackages:
  @sveltejs/adapter-node: ^5.0.1 => 5.0.1
  @sveltejs/kit: ^2.0.0 => 2.5.7
  @sveltejs/vite-plugin-svelte: ^3.0.0 => 3.1.0
  svelte: ^4.2.7 => 4.2.15
  vite: ^5.0.3 => 5.2.10

Severity
annoyance
Additional Information
From some of my research on this, I am aware that undici, which implements fetch in Node, does not release connection resources upon garbage collection.
I made multiple attempts to close it myself, but I was unsuccessful.

Perhaps related to #11617?

Could be also related to https://github.com/sveltejs/kit/issues/11751
When streaming, the request channel doesn't seem to get closed ever. Not sure at which layer (socket FD or some node abstraction).

I'm closing this since I'm unable to reproduce the issue with the latest SvelteKit and Vite running on Noda 20.18.0


Stabilize and catalog all document formats (chapter, book-chapter, book-chapter-section, etc.)

In order to sync data from the text server to the Meteor application's database, we need to better define the different document formats. What makes a document "chapter" v. "book-chapter", etc.?
It only really matters for the API to understand how many levels of nested content there are.  We can build it to be flexible if each level of nested content above the actual string of text (book, chapter, poem, etc.) has a similar structure.

Is this an issue you need my feedback on? If I understand right, you're saying that what really matters is depth of nesting?

Yes, that's correct--I think we just need to know the depth of nesting for the first round of updates.
We should get somewhat of a list together as we build so the text-sync script knows what to do with them.  So far I see chapter, book-chapter, book-line, and poem-line. Is there anything else?
At some point it would maybe make sense to infer genre from these as well.

Types of chunking of classical works (off the top of my head): chapter, chapter-section book-chapter, book-chapter-section, book-line, and poem-line, fragment, fragment-line, line (as in plays).
I assume that these will need slightly different fontend templates for displaying their contents. If discerning depth of nesting, a cheap and easy way might be to infer this from the "meta" tag, ie, "fragement-line" has a depth of 2, "lines" 1, "book-chapter-section" 3.

At some point it would maybe make sense to infer genre from these as well.
If by genre here you mean, say, dramatic play vs. prose text vs. epic poetry – then, yes, that may be inferred. But I think it's obvious that we can't parse historiography from philosphy, or lyric from odes.

Okay, great--this is super helpful, thanks. I'll add these to the wiki page, and if we run into more ambiguities in the future can reopen this issue.  Seems to be ready to be closed for now.


Tooltip issue with localPoint when chart has left padding

Main Issue
I noticed an issue with the Tooltip when a chart has left padding. The Tooltip has issues picking the correct data point.
Issue Details
When TooltipContext gets the localPoint, the localX value is never below the value of the left padding for the chart.
https://github.com/techniq/layerchart/blob/5c567e3beed590d097845d5f7e14415068dae0db/src/lib/components/TooltipContext.svelte#L140-L142
This means it does not get the proper xValueAtPoint.
https://github.com/techniq/layerchart/blob/5c567e3beed590d097845d5f7e14415068dae0db/src/lib/components/TooltipContext.svelte#L180
Solution?
I don't know whether it is as simple as subtracting the left padding to setting localX.
Screen Recordings
Line Chart example that has left: 16. Not super noticeable.

Line Chart example with left: 32. Very noticeable.

Line Chart example with left: 0. Removes the issue.

Tooltip Interactions example left: 36 Very noticeable.

Tooltip Interactions example left: 0 Removes the issue.

localX value when left: 32

@mattlangeman This is now fixed in 0.24.4.  I also update Tooltip to support variant prop with light, dark, and none.  I used none to update Sparkbar / Sparkline fixed position examples, as well as Clipped Area example

Tooltip variant option looks good. Nice to have full control over styling when needed.
The left padding issue also looks fixed, though I'm thinking when mode is bisect-y it should be using $padding.top instead of $padding.left.
https://github.com/techniq/layerchart/blob/d69295a0ec77894e0daf1c1ec08ef337a6eb9460/src/lib/components/TooltipContext.svelte#L191

Yeah. I was trying to find examples using bisect-y, but didn't see anything. I played around with the Single Date / Time Example, but I don't think you intended that to support bisect-y


Add telegram recipe

The recipe should create and not merely download the AppImage. Please look at the other receipes. When a new version of Telegram comes out, the recipe should automatically build the newest version of the AppImage. So please don't hardcode version numbers. For this please also study the other recipes. Thanks!

yes. I'm on it


Wrong default settings when using QuarterSkin

When just setting the skin the other default settings do not work. See screenshot.

To reproduce:
    gauge1 = GaugeBuilder.create()
                         .skin(QuarterSkin.class)
                         .build();

Looks like you modified the OverviewDemo where the the gauge1 will later be used in a FGauge control. This FGauge will now throw a RuntimeException when you try to apply it to a Gauge that has a Skin different than the GaugeSkin.
If you simply use it the way you showed, it will work :)


Pathpoint UI indicates support via form, should point to Pathpoint repo instead

Summary
Pathpoint UI contains a form for submitting support requests
Desired Behaviour
Pathpoint UI should point to Github repo instead to encourage customers to open an issue on the repo instead
Possible Solution
Additional context
Link to file containing "support" text:  https://github.com/newrelic/nr1-pathpoint/blob/main/nerdlets/pathpoint-nerdlet/config/messages.json

@rsamanez @Sandeep10parmar
We need to change this form.   This support method is obsolete.  I suggest we do the following

Get rid of the drop downs and edit forms
Add a message describing how Pathpoint is developed and supported
Replace submit with 2 buttons

Create GitHub Issue
Create Discussion Forum Thread]


Remove deprecated Metadata and User Keyword table name synonyms

Metadata is a synonym for Settings and User Keyword for Keyword. These aliases were deprecated in RF 3.0 (#2208) and can now be removed in RF 3.1.

Removing table names is safer now that we are going to report unrecognized headers as errors (#2860). Now, for example, "Metadata" table will cause an explicit error and won't be silently ignored.


Title changed to MY Todo List

Title is successfully changed to My Todo List

Thank you for your invaluable contributions to our open-source project! 🚀 If you like our project, please consider to start ⭐ the repo.

Thank you for your invaluable contributions to our open-source project! 🚀 If you like our project, please consider to start ⭐ the repo.

My pleasure .


Deck legality doesn't ensure there's a commander

This would only apply to some colorless decks, since the identity check would fail for any deck with color-bearing cards. Still, fixed in next deployment.


fix: fix list order

Small issue that semi fixes ordering issue for acl list. (still random but at least it is ordered by principals

Actually will merge into convinience commands


PPPoE Server Problem

I have problem with PPPoE Server on opnsense
OPNSense version: 18.7.7
os-pppoe Plugin version: 1.7_2
PPPoE server is configured as follows:

I have also added “any to any” ipv4 rules in Firewall rules (WAN & PPPoE)
When I want to connect OPNSense using PPPoE client (in windows 7) there is an error (following image) and There is no PPPoE Logins log in opnsense.

The PPPoE client security profile is as follow:

Thanks for support.

I have no idea of this plugin, but at first I'd start to check if:
* daemon is running

* packets arriving at WAN interface

* something to see in filter.log

* any other logs available?

Did your setup successfully run on any other version like 18.1?

I've checked:
Daemon is running
Packets arriving at wan interface
and there is not special log available
Is there any idea?
Thanks.

Do you see packets also replied?
I'd check system.log, ppps.log, or better everything in /var/log :)

g, pp

I've checked as following:
The firewall has globally been disabled,
Dump PPPoE Discovery packets:
root@OPNsense:~ # tcpdump -i igb0 pppoed
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on igb0, link-type EN10MB (Ethernet), capture size 262144 bytes
07:32:49.821187 PPPoE PADI [Service-Name] [Host-Uniq 0x0E000000000000000E000000]
07:32:54.823256 PPPoE PADI [Service-Name] [Host-Uniq 0x0E000000000000000E000000]
07:32:59.825883 PPPoE PADI [Service-Name] [Host-Uniq 0x0E000000000000000E000000]
07:33:04.828672 PPPoE PADI [Service-Name] [Host-Uniq 0x0E000000000000000E000000]
^C
4 packets captured
287 packets received by filter
0 packets dropped by kernel
root@OPNsense:~ #
Dump PPPoE Session packets:
root@OPNsense:~ # tcpdump -i igb0 pppoes
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on igb0, link-type EN10MB (Ethernet), capture size 262144 bytes
^C
0 packets captured
207 packets received by filter
0 packets dropped by kernel
root@OPNsense:~ #
poes.log file:
ov 27 06:54:12 OPNsense poes: caught fatal signal TERM
Nov 27 06:54:14 OPNsense poes: [B] Bundle: Shutdown
Nov 27 06:54:14 OPNsense poes: [L] Link: Shutdown
Nov 27 06:54:14 OPNsense poes: PPPoE: stop waiting for connection on igb0:, service "pppoe1"
Nov 27 06:54:14 OPNsense poes: process 54912 terminated
Nov 27 06:54:23 OPNsense poes: Multi-link PPP daemon for FreeBSD
Nov 27 06:54:23 OPNsense poes:
Nov 27 06:54:23 OPNsense poes: process 74143 started, version 5.8 (root@opn-build-amd64-1 23:48 27-Jul-2018)
Nov 27 06:54:23 OPNsense poes: PPPoE: waiting for connection on igb0:, service "pppoe1"
Actually PPPoE Discovery packets are sent to OPNsense but there is no reply from it.
Thanks for support.

not resolved? i am have the same problem!

I have this problem too. Issue -  set correct service name on client side. From our log - service name is "pppoe1". After I set this name on client side, all worked correctly.
Other question - where we can rename service name on server side?

I have a work around solution. You need to comment out the line
vi /usr/local/etc/inc/plugins.inc.d/if_pppoe.inc
//set pppoe service pppoe{$pppoecfg['pppoeid']}

According to mpd man page:
set pppoe service service-name
Sets the requested PPPoE service name. Setting service name to "*" on link with allowed incoming connections allows to accept incoming connection requests with any service name specified.

Since FreeBSD 6.3-STABLE/7.0-STABLE of 2008-01-30 it is possible to use "AC-Name\Service-Name" syntax to request specified access concentrator for outgoing connection.

The default is "*".

No solution ???

This issue has been automatically timed-out (after 180 days of inactivity).
For more information about the policies for this repository,
please read https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md for further details.
If someone wants to step up and work on this issue,
just let us know, so we can reopen the issue and assign an owner to it.


[Feature] Support AutoAug, AutoContrast, Equalize, Contrast, Brightness and Sharpness

Hi,
In this pull request, ColorTransform pipeline is added.
This pull request serves as a sub-task for implementing auto-augmentation.
Pipelines needed are listed below.

[x] Shear
[x] Translate
[x] Rotate
[x] AutoContrast (rely on open-mmlab/mmcv#881)
[x] Invert
[x] Equalize (rely on open-mmlab/mmcv#863)
[x] Solarize
[x] Posterize
[x] Contrast (rely on open-mmlab/mmcv#863)
[x] Color
[x] Brightness (rely on open-mmlab/mmcv#863)
[x] Sharpness (rely on open-mmlab/mmcv#864)

Please kindly take a look. Thank you.
Note that this pull request depends on multiple new commits in mmcv therefore cannot be merged until mmcv bump its version so that the unittests can pass.

fix unit test error

fix unit test error

Thanks for the reminder. The unit test will be fixed automatically once mmcv bump its version. Thx.


Updates to the 'How does Frontity work' section

Now that the Architecture section has been rewritten and includes the two Frontity modes, I've suggested making some updates and changes to the 'How does Frontity work' part of the About page so everything remains consistent. Please feel free to review it and make any changes or improvements you consider.

Approved and merged, thanks @rmartinezduque


Update index.js

I'd rather not use this repository for advertising existing Minecraft servers. I apologize.


Install error

I have tried to install this plugin a few times but get the following error:
npm ERR! code ENOENT
npm ERR! syscall spawn git
npm ERR! path git
npm ERR! errno -2
npm ERR! enoent Error while executing:
npm ERR! enoent undefined ls-remote -h -t<EMAIL_ADDRESS>npm ERR! enoent
npm ERR! enoent
npm ERR! enoent spawn git ENOENT
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR!  Please review log for details.

It looks like maybe git isn't installed?

Yes looks like it - the roon node api's are only available on github (they aren't published on npmjs.org for some reason), so you'll need to install git on your homebridge server.


RTL Support?

Hi. Is there any plan to add support for RTL layouts? Specifically, when the HTML dir="rtl", the progress bar should start from the right side and fill towards the left, to align with RTL conventions.
Thanks!

Well, that was unexpectedly quick! Thanks! 😃


Server crash due to suspected memory leak

The server was running normally, then suddenly crashed. A stack trace was generated, which suggests that there may be a memory leak. Unfortunately, I don't have further steps to reproduce it.
<--- JS stacktrace --->

==== JS stack trace =========================================

    0: ExitFrame [pc: 0x7f59c50b7b79]
    1: StubFrame [pc: 0x7f59c503e8e1]
Security context: 0x1c2a0fd1b9a1 <JSObject>
    2: extractBlockModulesMap(aka extractBlockModulesMap) [0x33744d47d71] [/home/ubuntu/storage/visualization-tool/node_modules/next/dist/compiled/webpack/bundle5.js:~77898] [pc=0x3c1493c887d0](this=0x2b84590404b1 <undefined>,0x1bf4fa6ab6e1 <Compilation map = 0x21cdf0487c39>)
    3: visitModules(aka visitModules) [0x3374...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0x7f59c41f53cc node::Abort() [/lib/x86_64-linux-gnu/libnode.so.72]
 2: 0x7f59c412567c  [/lib/x86_64-linux-gnu/libnode.so.72]
 3: 0x7f59c45cae2a v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/lib/x86_64-linux-gnu/libnode.so.72]
 4: 0x7f59c45cb1e4 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/lib/x86_64-linux-gnu/libnode.so.72]
 5: 0x7f59c477d509  [/lib/x86_64-linux-gnu/libnode.so.72]
 6: 0x7f59c478ddc6 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/lib/x86_64-linux-gnu/libnode.so.72]
 7: 0x7f59c478ec12 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/lib/x86_64-linux-gnu/libnode.so.72]
 8: 0x7f59c4790fbd v8::internal::Heap::AllocateRawWithLightRetry(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/lib/x86_64-linux-gnu/libnode.so.72]
 9: 0x7f59c4791029 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/lib/x86_64-linux-gnu/libnode.so.72]
10: 0x7f59c4755d43 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/lib/x86_64-linux-gnu/libnode.so.72]
11: 0x7f59c4aab6e7 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/lib/x86_64-linux-gnu/libnode.so.72]
12: 0x7f59c50b7b79  [/lib/x86_64-linux-gnu/libnode.so.72]
Aborted (core dumped)
error Command failed with exit code 134.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Thanks for reporting. This is unfortunate.

Has it been restarted automatically ?
Is there instrumentation that can help know the amount of memory the server was using at the moment of the trace ?
When did it crash ?
What is the amount of memory available to the server ?

Unfortunately no. Is there something I can activate to get a more detailed trace next time?
Not sure when it crashed. For context there is no load, this is a test server to evaluate the platform.
The amount of memory is 30GB

Not directly in the application, it would be something to have as part of a metrics platforms like Grafana. How much time was it running ?

Now the server crashes faster after starting: ~2 hours.
I tried to log the memory. My server has 32G. Based on my memory profiling, there was still plenty of memory.
26-02 17:18:30  | 49   1  50   0   0 | 10.4G 3995M  619M 14.8G |
26-02 17:18:31  | 30   1  69   0   0 | 10.4G 3989M  619M 14.8G |
26-02 17:18:32 |  0   2  98   0   0 | 8563M 6038M  619M 14.8G |
26-02 17:18:33 |  0   2  98   0   0 | 7159M 7442M  619M 14.8G  |


undefined blackfriday.EXTENSION errors on go test

Hi
Im using Go 1.12.9 and getting these errors, not matter which version i try to use on th gopkg.toml file
➜ go test -v -run TestGCPSqlInstanceCreation
# github.com/rocketlawyer/OPS-terraform-resources/gcp/database/sql/test/vendor/github.com/cpuguy83/go-md2man/md2man
vendor/github.com/cpuguy83/go-md2man/md2man/md2man.go:11:16: undefined: blackfriday.EXTENSION_NO_INTRA_EMPHASIS
vendor/github.com/cpuguy83/go-md2man/md2man/md2man.go:12:16: undefined: blackfriday.EXTENSION_TABLES
vendor/github.com/cpuguy83/go-md2man/md2man/md2man.go:13:16: undefined: blackfriday.EXTENSION_FENCED_CODE
vendor/github.com/cpuguy83/go-md2man/md2man/md2man.go:14:16: undefined: blackfriday.EXTENSION_AUTOLINK
vendor/github.com/cpuguy83/go-md2man/md2man/md2man.go:15:16: undefined: blackfriday.EXTENSION_SPACE_HEADERS
vendor/github.com/cpuguy83/go-md2man/md2man/md2man.go:16:16: undefined: blackfriday.EXTENSION_FOOTNOTES
vendor/github.com/cpuguy83/go-md2man/md2man/md2man.go:17:16: undefined: blackfriday.EXTENSION_TITLEBLOCK
vendor/github.com/cpuguy83/go-md2man/md2man/md2man.go:19:29: too many arguments to conversion to blackfriday.Markdown: blackfriday.Markdown(doc, renderer, extensions)
vendor/github.com/cpuguy83/go-md2man/md2man/roff.go:19:9: cannot use &roffRenderer literal (type *roffRenderer) as type blackfriday.Renderer in return argument:
	*roffRenderer does not implement blackfriday.Renderer (missing RenderFooter method)
vendor/github.com/cpuguy83/go-md2man/md2man/roff.go:102:11: undefined: blackfriday.LIST_TYPE_ORDERED
vendor/github.com/cpuguy83/go-md2man/md2man/roff.go:102:11: too many errors
FAIL	github.com/rocketlawyer/OPS-terraform-resources/gcp/database/sql/test [build failed]

OPS-terraform-resources/gcp/database/sql/

my Gopkg.toml (i have tried 0.19.0 - same result)
[[constraint]]
  name = "github.com/gruntwork-io/terratest"
  version = "0.18.3"

i then run dep endure from the test folder.
and my test file
package test

import (
	"testing"

	"github.com/gruntwork-io/terratest/modules/gcp"
	// "github.com/gruntwork-io/terratest/modules/random"
	"github.com/gruntwork-io/terratest/modules/terraform"
	test_structure "github.com/gruntwork-io/terratest/modules/test-structure"
	// "github.com/stretchr/testify/assert"
)

func TestGCPSqlInstanceCreation(t *testing.T) {
	projectID := gcp.GetGoogleProjectIDFromEnvVar(t)

	// Copy the module folder to a temp folder, this helps with making it
	// clean and reproducible
	rootFolder := "../../../../"
	moduleFolder := "OPS-terraform-resources/gcp/database/sql/instance"
	terraformTempDir := test_structure.CopyTerraformFolderToTemp(t, rootFolder, moduleFolder)

	terraformOptions := &terraform.Options{
		// The path to where our Terraform code is located
		TerraformDir: terraformTempDir,

		// Variables to pass to our Terraform code using -var options
		Vars: map[string]interface{}{
			"gcp_project": projectId,
		},
	}

	// At the end of the test, run `terraform destroy` to clean up any resources that were created
	defer terraform.Destroy(t, terraformOptions)

	// This will run `terraform init` and `terraform apply` and fail the test if there are any errors
	terraform.InitAndApply(t, terraformOptions)
}

I found out that locking the version of blackfriday to 1.5.2, instead of 2.0 as automatically detected, did the trick.
Gopkg.toml
[[override]]
  name = "github.com/russross/blackfriday"
  version = "1.5.2"

This solved the problem for me


feature Support copy into on Azure Blob Storage

Proposed changes

Support copy into logic in FE on Azure Blob Storage.

run buildall


pull-request: Unprocessable Entity (HTTP 422) Invalid value for "head"

Even though everything seems to have been set up correctly with the branches and remotes it seem like the selection of head branch is confused when creating a PR.
I think this is because my username (Mattias-) ends in a hyphen but I have not verified that.
$ git branch -vv
* add-py3kwarn 640caee [Mattias-/add-py3kwarn] python: Add py3kwarn maker
  master       ad726be [origin/master] Merge pull request #580 from blueyed/redraw-in-LogMessage

$ hub pull-request
Error creating pull request: Unprocessable Entity (HTTP 422)
Invalid value for "head"

$ hub pull-request -h Mattias-:add-py3kwarn
https://github.com/neomake/neomake/pull/595

$ hub --version
git version 2.10.0
hub version 2.2.5

Dupe of https://github.com/github/hub/issues/1256

Just for anyone getting here like me: check you didn't forget to push the branch to origin before doing the pull request...

@naoisegolden That's a common mistake that even I do from time to time, and the error message returned definitely isn't friendly. I'm working on improving that. Also, the pull-request --push flag  is in the works! #1294

Also, the pull-request --push flag is in the works!

Is it?

@batisteo Indeed. It was part of a prerelease that went out in February https://github.com/github/hub/releases/tag/v2.3.0-pre9


Fix spatial bugs: handle datasets with domain bounds out of order and zonal averaging

Description
This PR is intended to fix #324 and #338. It allows users to perform spatial averaging on datasets in which domain_bounds[:, 0] > domain_bounds[:, 1] by re-ordering the domain bounds for the purposes of calculating spatial weights. It also fixes an issue that prevented spatial averaging on lat-plev grids. A section of the code tried to load longitude bounds even when that axis was not specified for averaging; this section of code is updated to only load bounds information if the axis is specified for averaging.

Closes #324, #338

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] Any dependent changes have been merged and published in downstream modules

If applicable:

[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass with my changes (locally and CI/CD build)
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have noted that this is a breaking change for a major release (fix or feature that would cause existing functionality to not work as expected)

Codecov Report

Merging #340 (55f38a2) into main (f6bc409) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #340   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           14        14
  Lines         1196      1204    +8
=========================================
+ Hits          1196      1204    +8

Impacted Files
Coverage Δ

xcdat/spatial.py
100.00% <100.00%> (ø)

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

I think this is in good shape and can be reviewed. I do plan on re-running it over a bunch of cases before merging.

I re-did comparisons with CDAT - we still agree with CDAT in all cases where both can load the dataset (loop over 115 model files and 21 domains).


Missing product M365_SECURITY_COMPLIANCE_FOR_FLW

Missing the product details for SKU M365_SECURITY_COMPLIANCE_FOR_FLW

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

ID: 7c245452-161d-89a1-c026-99a0721cf071
Version Independent ID: 16dec59a-eb83-1837-4efd-4645e7aeaed2
Content: Product names and service plan identifiers for licensing - Azure AD
Content Source: articles/active-directory/enterprise-users/licensing-service-plan-reference.md
Service: active-directory
Sub-service: enterprise-users
GitHub Login: @daveba
Microsoft Alias: daveba

@leroydsouzapact Thank you for your feedback . We will investigate and update the thread.

@assign @Nicholak-MS who maintains the content of this page

#assign @Nicholak-MS

I added this today and it will go out with the next deployment.
#Please-Close


Add VM Insights Menu workbook

Also remove some unneeded templates. VM Insights workbook is a scope
selection for VM Insights workbooks.
Signed-off-by: andrewki-msft<EMAIL_ADDRESS>Tests
Context-free mode:

Hybrid mode, onboarded workspace:

Hybrid mode, non-onboarded workspace:

Workspaces is unset because this workspace has no reporting machines, Test parameter will not have the value of 1 as a result and can be treated as a non-onboarded scenario by the consuming template.

Azure mode (subscription):

Azure mode (subscription > resource group with no machines):

Resource groups is unset because this resource group has no machines. As a result, the Test parameter will not have the value of 1 and can be treated as a non-onboarded scenario by the consuming template.

Azure mode (subscription > resource group with machines):

@andrewki-msft this PR is almost a yea old, is it still necessary? if so, update and reopen, if not delete the branch?


Synchronize smart cell source before evaluation

Currently when evaluating a smart cell (especially with ctrl + enter) we may evaluate
Currently we have a race condition where the smart cell could be evaluated before the source is updated. A clear case is a smart cell field that sends update on blur, so ctrl + enter doesn't consider this change. Even if the field update was sent on every change, there is no guarantee that the smart cell source will update before evaluation.
To fix it, we ensure the following linearity:

evaluation triggered from UI or via a shortcut
run smart cell callback ctx.handleSync(() => ...) that should flush any deferred UI changes to the server
we ping the smart cell server from the client and await reply, this acknowledges all previous changes
we send evaluation request to the session
the session pings the smart cell server and awaits reply, this ensures the session receives all relevant source updates

@josevalim the callback is here, it's ctx.handleSync(() => ...), we need to update the smart cells examples though. Or did you mean something else?

For smart cells that rely on blur we will do
ctx.handleSync(() => {
  // Synchronously invokes blur listeners
  document.activeElement.dispatchEvent(new Event("blur"));
});

That's the simplest approach I could think of. I don't like that most cells will have to do this, but it's cell specific, so that's what we need.

I see. Is handleSync the best name? I was thinking onEvaluate, if it is only called before evaluation, unless you have other scenarios in mind?

Is handleSync the best name?

I'm not sure, but I wouldn't make it evaluation specific. Ideally the naming wouldn't even be smart cell specific, given that the js view abstraction is generic.

Ok! As you prefer then! Ship it!


Remove Deploy transaction

Please check if the PR fulfills these requirements

[ ] The formatter, linter, and tests all run without an error
[ ] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Entirely removes the Deploy transaction.
This is tracking PR. Smaller ones will be merged into it
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
YES
Other information

I think we should also remove AccountClient.create_account, right?


✨ ❄ 🎀 Use Homestead per project install, updated readme, add example config

See #27 for conversations.
I did something weird and broke my local repo, was easier to pull the commits into a new branch and squash them into a new PR.

Thank you so much for your work on this Joe! 🙌


issue in test

/gowireshark/tests/gowireshark_test.go:33 +0x25
testing.tRunner(0xc000110ea0, 0x57d100)
/usr/lib/go-1.18/src/testing/testing.go:1439 +0x102
created by testing.(*T).Run
/usr/lib/go-1.18/src/testing/testing.go:1486 +0x35f
exit status 2
FAIL    github.com/randolphcyg/gowireshark/tests        600.690s

/gowireshark/tests/gowireshark_test.go:33 +0x25 testing.tRunner(0xc000110ea0, 0x57d100) /usr/lib/go-1.18/src/testing/testing.go:1439 +0x102 created by testing.(*T).Run /usr/lib/go-1.18/src/testing/testing.go:1486 +0x35f exit status 2 FAIL github.com/randolphcyg/gowireshark/tests 600.690s

This should be the timeout mechanism of the go test module for 10 minutes, the reason may be that the read output data frame has been executed, and for more than 10 minutes, the go test module actively throws an error

Okay Thank you. i m looking for one more suggestion - how to get the dissected packet in json with values in descriptive.
for e.g
packet print
F1 Application Protocol (InitialULRRCMessageTransfer)
F1AP-PDU: initiatingMessage (0)
initiatingMessage
procedureCode: id-InitialULRRCMessageTransfer (11)
in json
[f1ap.criticality:1 f1ap.procedureCode:11 <<== i want here       "id-InitialULRRCMessageTransfer" instad number.. please advice. thank you.

Can you provide a sample packet file? I might be able to see if I can implement this idea~

This is a bin file that has an f1ap setup response. i need the output to
return to the main function in JSON format layers with descriptive instead
just values in digits. Please guide me. Thank you
F1 Application Protocol (F1SetupResponse)
F1AP-PDU: successfulOutcome (1)
successfulOutcome
procedureCode: id-F1Setup (1)
criticality: reject (0)
value
F1SetupResponse
protocolIEs: 2 items
Item 0: id-TransactionID
ProtocolIE-Field
id: id-TransactionID (78)
criticality: reject (0)
value
TransactionID: 20
Item 1: id-Cause
ProtocolIE-Field
id: id-Cause (0)
criticality: reject (0)
value
Cause: radioNetwork (0)
radioNetwork: unspecified (0)
On Mon, Jul 17, 2023 at 4:47 AM Randolph @.***> wrote:

Can you provide a sample packet file? I might be able to see if I can
implement this idea~
—
Reply to this email directly, view it on GitHub
https://github.com/randolphcyg/gowireshark/issues/8#issuecomment-1637722996,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQGWC4N4M2YDO3DQV3S6ULDXQUC2LANCNFSM6AAAAAAYC7MGGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

1.Since I couldn't find a PCAP file of F1AP protocol online, so I am unable to reproduce the real situation; Could you please send me the PCAP file so that I can verify and test it?
2.However, when testing with other existing protocol packets, you can observe that the parsing result contains descriptive values.
3.Additionally, there is a mapping of constant values for the F1AP protocol in the file ‘wireshark/epan/dissectors/asn1/f1ap/F1AP-constants.asn’. Therefore, the parsing of the F1AP protocol through the Wireshark DLL should also include descriptive values.

This is a bin file that has an f1ap setup response. Instead of printing output on console i need packet data output to return to the main function in JSON format layers with descriptive values. Please guide me. Thank you F1 Application Protocol (F1SetupResponse) F1AP-PDU: successfulOutcome (1) successfulOutcome procedureCode: id-F1Setup (1) criticality: reject (0) value F1SetupResponse protocolIEs: 2 items Item 0: id-TransactionID ProtocolIE-Field id: id-TransactionID (78) criticality: reject (0) value TransactionID: 20 Item 1: id-Cause ProtocolIE-Field id: id-Cause (0) criticality: reject (0) value Cause: radioNetwork (0) radioNetwork: unspecified (0)

1.Since I couldn't find a PCAP file of F1AP protocol online, so I am unable to reproduce the real situation; Could you please send me the PCAP file so that I can verify and test it?
2.However, when testing with other existing protocol packets, you can observe that the parsing result contains descriptive values.
3.Additionally, there is a mapping of constant values for the F1AP protocol in the file ‘wireshark/epan/dissectors/asn1/f1ap/F1AP-constants.asn’. Therefore, the parsing of the F1AP protocol through the Wireshark DLL should also include descriptive values.

f1ap.pcapng.zip
please find this file which has f1apsetup

f1ap.pcapng.zip
please find this file which has f1apsetup

This problem has been solved, and the code is added in the tag v2.0.9;
If there is a problem, you can let me know.


GraphQL queries without variables fail to execute

Repro
For this file:
POST https://api.spacex.land/graphql
Content-Type: application/json

query company_query {
  company {
    coo
  }
}

run httpyac test.http --all
Expected
{
  "data": {
    "company": {
      "coo": "Gwynne Shotwell"
    }
  }
}

Actual
POST https://api.spacex.land/graphql
accept: */*
accept-encoding: gzip, deflate, br
content-length: 47
content-type: application/json
user-agent: httpyac

query company_query {
  company {
    coo
  }
}

HTTP/1.1 400  - Bad Request
access-control-allow-origin: *
connection: close
content-length: 138
content-security-policy: default-src 'none'
content-type: text/html; charset=utf-8
date: Mon, 22 Nov 2021 13:38:10 GMT
server: Cowboy
via: 1.1 vegur
x-content-type-options: nosniff
x-powered-by: Express

<!DOCTYPE html>

<meta charset="utf-8">
<title>Error</title>

Bad Request

There were 2 errors present. If the file did not have a blank line at the end of the body, it was not treated as a correct GQL body. And requests without body were not extended with the query JSON.

I have published a bugfix. Thanks


WhenExpressions: support ANY match behavior

Feature request
The default behavior of:
If ALL the WhenExpressions evaluate to True
Needs a simple option to toggle the behavior to be:
If ANY of the WhenExpressions evaluate to True
Use case
I have a scenario where I have N spawned tasks, and if any ONE of their results have a particular value, I need something else to run.

I have a scenario where I have N spawned tasks, and if any ONE of their results have a particular value, I need something else to run.

@bitsofinfo if possible, could you please share more specifics of this use case? it'd help to have an example of what the N tasks are doing and what the something else to run is

pipeline kicks off 3 parallel deployments, if any one of them fails, they all have to get rolled back

pipeline kicks off 3 parallel deployments, if any one of them fails, they all have to get rolled back

thank you @bitsofinfo!
assuming that success/failure is indicated by a result, instead of task failure (that'd cause the pipeline to fail), can this use case be solved by checking that the failure status is in an array of the results from the tasks?
tasks:
- name: deploy-1
  taskSpec:
    results:
    - name: status
    ...
- name: deploy-2
  taskSpec:
    results:
    - name: status
    ...
- name: deploy-3
  taskSpec:
    results:
    - name: status
    ...
- name: rollback
  when:
  - input: failure
    operator: in
    values:
    - "$(tasks.deploy-1.results.status)"
    - "$(tasks.deploy-2.results.status)"
    - "$(tasks.deploy-3.results.status)"
  taskSpec:
    ...

thanks
Each of my deploy tasks outputs a result called last-exit-code and any code other than 0 is a failure. (i.e. 0=success, !=0 is failure)
so... i think this might work, w/ the current ALL behavior
  - input: "0"
    operator: notin
    values:
    - "$(tasks.deploy-1.results.last-exit-code)"
    - "$(tasks.deploy-2.results.last-exit-code)"
    - "$(tasks.deploy-3.results.last-exit-code)"

will go try this. still, any behavior would be a nice option.

thanks
Each of my deploy tasks outputs a result called last-exit-code and any code other than 0 is a failure. (i.e. 0=success, !=0 is failure)
so... i think this might work, w/ the current ALL behavior
  - input: "0"
    operator: notin
    values:
    - "$(tasks.deploy-1.results.last-exit-code)"
    - "$(tasks.deploy-2.results.last-exit-code)"
    - "$(tasks.deploy-3.results.last-exit-code)"

nice! glad you have a solution to the use case 😃

will go try this. still, any behavior would be a nice option.

having the values field as an array can be used to represent the any logic, however we can revisit supporting any if we get other ci/cd use cases that can't be solved otherwise

thx!

actually... @jerop realizing that unfortunately this still wont work
example:
deploy-1 succeeds, last-exit-code = 0
deploy-2 succeeds, last-exit-code = 0
deploy-3 fails, last-exit-code = 1
deploy-4 fails, last-exit-code = 99
Will not pass as 0 is in the list
  when:
  - input: "0"
    operator: notin
    values:
    - "$(tasks.deploy-1.results.last-exit-code)"
    - "$(tasks.deploy-2.results.last-exit-code)"
    - "$(tasks.deploy-3.results.last-exit-code)"
    - "$(tasks.deploy-3.results.last-exit-code)"

... and I can't do the inverse because the "input" is not necessarily known, the exit code could be anything !=0
  when:
  - input: "<exit code that is failure could be anything != 0>"
    operator: in
    values:
    - "$(tasks.deploy-1.results.last-exit-code)"
    - "$(tasks.deploy-2.results.last-exit-code)"
    - "$(tasks.deploy-3.results.last-exit-code)"
    - "$(tasks.deploy-3.results.last-exit-code)"

is using last exit code as a result a workaround to avoid your pipeline failing or is it something you actually want?
if it's a workaround, maybe the setup we need for this use case is that:

the deploy tasks are dag tasks that are allowed to fail (don't have exit code results)
the rollback task is a finally task that's guarded using when expressions that operate on the execution status of the deploy tasks

supporting accessing execution status of any dag task in finally tasks is progress in https://github.com/tektoncd/pipeline/pull/3390 (cc @pritidesai)
supporting when expressions in finally tasks is coming soon https://github.com/tektoncd/pipeline/issues/3438 (cc @bobcatfish)

in the meantime, i'd recommend changing your result to represent the success/failure instead of using the exit code directly (if exit code == 0, then result is success, otherwise result is failure) -- this would allow you to use the setup in https://github.com/tektoncd/pipeline/issues/3591#issuecomment-738197122
cc @bobcatfish @pritidesai

I write last-exit-code and then analyze it to make decisions because various things have different failure reasons. It's something I actually want to be able to do vs hard failing the actual worker tasks themselves.
in any case, all I'm asking for is an "ANY" option for WhenExpressions. Would be simple to add. I'm just an advocate for making it as flexible as possible for the end-user, vs changing their implementation to adhere with limited evaluation capabilities of the framework itself. Similar to the arguments in #3468. Seems adding a config flag for WhenExpressions might be simpler than altering core fundamental dag behavior.

in any case, all I'm asking for is an "ANY" option for WhenExpressions. Would be simple to add. I'm just an advocate for making it as flexible as possible for the end-user, vs changing their implementation to adhere with limited evaluation capabilities of the framework itself.

we want to add features only when they're absolutely necessary that's why we need to find use cases that can't be solved or that are challenging to solve, further described in the simplicity section of the design principles
i also think that adding is ANY is easy but not simple

I guess one use case we cannot satisfied:
  when:
  - input: success
    operator: in
    values:
    - "$(tasks.deploy-1.results.status)"
    - "$(tasks.deploy-2.results.status)"
    - "$(tasks.deploy-3.results.status)"

3 parallel tasks, if one if them success, the 4th task will start to run.
but if one of the 3 task stuck, although another one already success, we still wait until timeout.
I means the requirements is: if any of the tasks success, do not wait others, the 4th should execute immediately. @jerop

@bitsofinfo @vincent-pli check out the newly-added common expression language custom task which may be helpful for your use cases

@bitsofinfo @vincent-pli check out the newly-added common expression language custom task which may be helpful for your use cases

/remove-lifecycle stale

I have a pipeline whereby we have logic a little like this, and arrived here looking for exactly the same thing in the hope such support was now available, or in the pipeline:

install dependency1 if (param1) or (param2)
install app1 if (param1)
install app2 if (param2)

Basically we have two inputs, those inputs each directly control whether a certain branch in the pipeline is actived, but earlier in the pipeline there are some pre-req steps that are needed only if one or more of those optional branches are traversed.  We can't use the status of the app1/app2 install steps as this step happens before they do.
The hacky workaround we put in place at the moment is this, which works as we use empty string in the parameter to indicate "don't install that application":
      when:
        - input: "$(params.param1)$(params.param2)"
          operator: notin
          values: [""]

We did want to do more complex logic based on content of the param (which carries a version number), but I don't see how we can do that without the kind of ANY match support discussed in this issue.
Example: One app only needs this step depending on the version chosen, the other needs it as long as it's installed (any version)
      whenAny:
        - input: "$(params.param1)"
          operator: notin
          values: [""]
        - input: "$(params.param2)"
          operator: in
          values: ["8.5", "8.6"]

Hi, the CEL in WhenExpression has been supported in release v0.53 , which can be used to address the use case. Please try out the feature and if you have any suggestions, feel free to comment on this issue: https://github.com/tektoncd/pipeline/issues/7358


how control input cmd

how control input cmd?
1、record
all input、and all output to database
2、control
filter unsafe input and unsafe output
3、interface
where is the interface api，how use api to monitor and control
thank you

I don't understand what you say but in my code I test a little bit the inputs (not for security)
so you maybe it could help you to find a way:
term.on('data', function(data) {
                  //we test if it's "enter"
                  if(data == '\r'){
                    //make a new line with nothing on it
                    term.writeln("");
                    Streamy.emit('data', {content: data, idContainer: idContainer});
                  }else if (btoa(data) == "fw=="){ //it means that he pressed "return"
                    //delete the last char
                    term.write('\b \b');
                    Streamy.emit('data', {content: "return", idContainer: idContainer});
                  }else if (btoa(data) == "IA=="){ //it means that he pressed space
                    term.write(" ");
                    Streamy.emit('data', {content: "space", idContainer: idContainer});
                  }else{
                    term.write(data);
                    Streamy.emit('data', {content: data, idContainer: idContainer});
                  }
              });


co_filename is relative rather than absolute

I managed to get inspect working, mostly, with cython files using binding=True. However, now I ran into another issue where co_filename is set to the relative path of the pyx file at the time of the compile. This means that as soon as you you change directory, we cannot find the source file using co_filename as it doesn't map to the right path.
Looking at the generated c file, the problem is with the filename passed to __Pyx_PyCode_New. The value seems to be generated here: https://github.com/cython/cython/blob/master/Cython/Compiler/ExprNodes.py#L9396. By changing file_path = StringEncoding.bytes_literal(func.pos[0].get_filenametable_entry().encode('utf8'), 'utf8') to file_path = StringEncoding.bytes_literal(os.path.abspath(func.pos[0].get_filenametable_entry()).encode('utf8'), 'utf8'), the abs path was saved in the generated c file. Although I'm not sure this is the correct fix, or whether there are other implications to saving the full path.
My kv_cython_test.pyx file contains
#cython: binding=True

from kivy.uix.widget import Widget
from kivy.lang.compiler import KV, KVCtx

class MyWidget(Widget):

    def apply_kv(self):
        with KVCtx():
            self.x @= self.y

and is right next to the setup.py file that contains
from distutils.core import setup
from Cython.Build import cythonize
from os.path import join, dirname, abspath

setup(
    ext_modules=cythonize(abspath(join(dirname(__file__), "kv_cython_test.pyx")))
)

The only way to determine the path of the current module at module init time is PEP 489, and that cannot generally be implemented for an arbitrary extension module.
Using the build time path in the compiled module is not a good idea, as the module will be installed in an arbitrary place, most likely not the place where it was built.

The normal approach would be to install the Cython source files together with the binaries so that they can be looked up for tracebacks etc., just like Python finds the .py sources if they are around. Used to work in Py2.x, no longer works in Py3 due to https://bugs.python.org/issue32797 .

Hmm, ok. That makes sense. Should I close this then?

Enough of PEP-489 is implemented now to make this work.

Are we going to add switch to control whether to include absolute path or relative path?


Fix consul backend template

vault_tls_gossip is evaluated as a string and is considered true even if
it holds 0.

Thanks!


Feature/userproviderclasses

Reason for this PR:

created data classes for user and provider (store keys, token, ...)

Changes in this PR:

created data classes for user and provider (store keys, token, ...)

Checklist:
Select whatever applies:

[x] Test written
[x] Code Properly Formatted
[ ] Documented
[ ] Changelog updated

Looks very good!
The Representation tests do their duty and they'd be fit to uncover issues. Long-term, code to instantiate an object such as a Token will probably become easier, given that this is a standard functionality of the user (i.e. they'll instantiate a Token even with useful data as part of their normal operation). So as soon as that's the case, consider simplifying these tests by interweaving them with the "incentive system correctness" test code where Token objects are already lying around, anyway.
There are probably arguments for and against this, but it's something to think about (especially if one day, you end up fed up with writing so much code just for the sake of testing serialization of dumb objects).

I definitely agree, even though writing these simple test doesn't take much time and helps a lot at this early stage. Later, the representation should be covered by some other test, so if we have more advanced tests or this we can remove this one.


libtinycbor.a created as a directory on some buildsystem

Thanks for accepting the change on unnamed union.
There is another issue with tinycbor on buildroot. On some architectures, it seems that libtinycbor.a is created as a directory. You can find more information here: https://patchwork.ozlabs.org/patch/652187/. II have not found the issue yet.
There is juste this line which seems at bit strange to me: "test -d $(@D) || $(MKDIR) $(@D)". I don't think this line is needed because src and tools directories are always there but this is harmless.
Did you already have this issue with libtinycbor.a created as a directory?

I just submitted a pull request that fixes this issue.

Thanks, I would never have guessed what the issue was.

Thanks to both of you, could you make a new release such as 0.32 so we could remove these two patches from buildroot?

No, as the first patch was removed from master. You'll need to wait for the 0.4 release to get it.

Dear Thiago,
It seems you reapplied the patch on unnamed union to the dev branch and made a new 0.3.2 release which does not include this change (even it is listed in the release note: https://github.com/01org/tinycbor/releases/tag/v0.3.2). Did you have more tests to do to validate this change and publish a new release?
Best Regards,
Fabrice

The patch will be in the 0.4 release. I can't update too quickly because people need to get rid of their 0.2 depracated API first.


Add obsolete edges

Added consider and replaced_by edges for obsolete nodes

Do you also want to throw in an "obsolete" field on the term vertices in this PR?

@kellyhuang21 you should make "is_obsolete" a boolean type rather than a string

I went ahead and did that change


add NuGet ContinuousIntegrationBuild

Deterministic build is desired, which was planned as part of the NuGet improvements anyway (#42).
This PR adds the pretty new ContinuousIntegrationBuild to the dotnet pack command


Import missing language specs with at least 1 passing spec

We can remove the numbers_spec.rb from the self-hosted tests for now.

For now, I just disabled that single failing test. It contains a NATFIXME marker with more information, so it's easier to find than when we would just remove that whole spec suite.


Can't execute my project: missing @expo/vector-icons/Ionicos

This is my package.json:
 {
   "name": "CaliUp",
   "version": "0.0.1",
   "private": true,
   "scripts": {
     "start": "node node_modules/react-native/local-cli/cli.js start",
     "test": "jest"
   },
   "dependencies": {
     "native-base": "^2.2.1",
     "react": "16.0.0-alpha.12",
     "react-native": "0.46.4",
     "react-native-vector-icons": "4.1.1",
     "react-navigation": "^1.0.0-beta.11"
   },
   "devDependencies": {
     "babel-jest": "20.0.3",
     "babel-preset-react-native": "2.1.0",
     "jest": "20.0.4",
     "react-test-renderer": "16.0.0-alpha.12"
   },
   "jest": {
     "preset": "react-native"
   }
 }

created with react native cli. But if I try to execute run-android with any native-base component included in my code, the following exception ios thrown:

error: bundling failed: "Unable to resolve module @expo/vector-icons/Ionicons from C:\\Code\\ReactNativeProjects\\CaliUp\\node_modules\\native-base\\dist\\src\\basic\\IconNB.js: Module does not exist in the module map\n\nThis might be related to https://github.com/facebook/react-native/issues/4968\nTo resolve try the following:\n  1. Clear watchman watches: watchman watch-del-all.\n  2. Delete the node_modules folder: rm -rf node_modules && npm install.\n  3. Reset packager cache: rm -fr $TMPDIR/react-* or npm start -- --reset-cache."

Ho can I solve this?

@eggybot I've generated my app with react-native-cli, without crna, have I to install the @expo/vector-icons dependency anyway?

@eggybot I've installed @expo/vector-icons package and now the error is:

Unable to resolve module ./fonts/Ionicons.ttf from<EMAIL_ADDRESS>could not resolve<EMAIL_ADDRESS>as a folder: it did not contain a package, nor an index file"

How can I solve this instead?

@bm-software remove react-native-vector-icons from your dependency. native-base has that as its  internal dependency.

@shivrajkumar I'm using that for other things I have to used that included in native-base?

@bm-software yes

@SupriyaKalghatgi removing react-native-vector-icons from dependencies solves the problem. Thanks!


./start.sh doesn't work

When running ./start.sh   , comes following

JungleTestnet-vcchaintest5/stop.sh: line 16: kill: (70075) - No such process
Nodeos stopped.
Starting Nodeos
./start.sh: line 16: ulimit: open files: cannot modify limit: Invalid argument

Any idea how to fix it?
That's what in start.sh file:

ODEOS=/Users/vcchain/eos-source/build/programs/nodeos/nodeos
DATADIR=/Users/vcchain/JungleTestnet-vcchaintest5
$DATADIR/stop.sh
echo -e "Starting Nodeos \n";
ulimit -n 65535
ulimit -s 64000
$NODEOS --data-dir $DATADIR --config-dir $DATADIR "$@" > $DATADIR/stdout.txt 2> $DATADIR/stderr.txt &  echo $! > $DATADIR/nodeos.pid

Hi,
what OS version do you use? this scripts were tested for ubuntu/centos

I'm using Darwin, macOS High Sierra 10.13.6

probably you dont have ulimit command, try to comment it out. Also please check logs, maybe you va some other errors why nodeos do not start


Emit error rather than crash

In my situation, I am getting "Error" in my status, but not "dps".  The status packet looks a lot like the one generated by error_json, so returning it seems logical.  The only caveat here is that I cannot get my device to work, so I am not certain that there is no Error in a valid status message, though it seems unlikely.  If it is there, you could add a check to ensure "dps" is missing, but I suspect that will be unnecessary.

@eykamp Thanks for this!  Yes, I can see how this would prevent a crash.  I will accept this but may also update it to be more like this:
        if self.DPS not in status.keys():
            return status


Update to Swift 4.2.1, test under 16.04 and 18.04

This PR aims to update to the Swift 4.2 release version.

14.04 and 16.04 have started working again recently (I believe this is something to do with the Ubuntu Redis server packages).  18.04 still fails with all the tests failing to connect to the local Redis server.


Output Data Format

The data model for the target database for this process has two main parts - metadata about the station/sensors which does not change often and is generally changed with updates when it does change and insert only records for individual measurements.
The metadata is normalized in it's final storage, but transfer could be done in a flattened form.
Notes for the individual tables can be found at https://docs.google.com/spreadsheets/d/1mvKclBguYo5CsFvTIG5FiId5Sr2XMxVWs8IxhtTc6qI/edit?ts=5f888e74#gid=1301608214
Visual chart of the data model:

The biggest key to the normalization is that we need an identifier for each individual sensor (a location can have multiple sensors for each thing being measured). Ideally measurements data will come through with only the following fields:
sensor_id, timestamp, value (for stationary data)
and
sensor_id, timestamp, value, lat, lon (for mobile data)
All other data will end up getting normalized out into separate tables, but could come in as flattened csv, or nested json

Ultimate format for the metadata needs to provide for a structure like this, that being said, as long as I get all the information here, I can deal with just about anything on the database ingest side.
{
"": {
"sensor_nodes":
[
{
"sensor_node_site_name" : ... # name provided by the source that is unique within a source,
"sensor_node_geometry": {"latitude": ..., "longitude": ...}, # not needed if mobile
"sensor_node_is_mobile": ...,
... any other field that can be mapped to something in the sensor node tab on https://docs.google.com/spreadsheets/d/1mvKclBguYo5CsFvTIG5FiId5Sr2XMxVWs8IxhtTc6qI/edit?ts=5f888e74#gid=1132575684
"sensor_systems": [ # for most sources there will be just one sensor system
{
"sensor_system_name": ... # name provided by the source unique within a node -- if there is only one this can be blank,
... any field from that can be mapped to something in the sensor system tab on the spreadsheet,
"sensors" : [
{
"measurand" : ...,
"units": ....
... any field that can be mapped to something from the sensor tab on the spreadsheet
### alternate option to the two
}
]
}
]
}
]
}
We could break down using directories as well where the sources directory contained a directory for each sensor node which had a sensor_node.json and a directory for each sensor system etc

Going to close this issue as in our previous discussion we were mostly in line with the desired format. Let's open new issues for specific actionable items now that we have the general format implemented.


DataLakeFileClient.Upload does not upload data

Describe the bug
Data is not uploaded when Upload is called with a non seekable, non length supporting stream.  Data is not uploaded when UploadAsync is called under the same conditions with a maximum concurrency of 1.
Expected behavior
Data is uploaded
Actual behavior (include Exception or Stack Trace)
Data is not uploaded.
To Reproduce
See attached repro.
Repro.zip
It looks like the issue is in PartitionedUploader.UploadInSequenceInternal.  Inside the foreach loops StagePartitionAndDisposeInternal is called.  This will dispose the PooledMemoryStream so that when partitions.Add((block.AbsolutePosition, block.Length)); is run the position and block length are both 0.  That leads to an incorrect length + offset when flushing.
Environment:
Tested with Azure.Storage.Files.DataLake Version="12.6.0"

Thank you for your feedback.  Tagging and routing to the team best able to assist.

@seanmcc-msft What do you think about this bug? In order to upload we need to be able to get the Stream.Length and Stream.Position in order to determine what can be uploaded from the stream.
contentLength: (content?.Length - content?.Position) ?? 0

@Kyle8329, Upload does not support non-length streams.  This API is calling Put Block and Put Block List, and we have to know the stream length to correctly partition the blob into blocks.

@seanmcc-msft  Did you read my comment in the Reproduce section?  It shouldn't matter if the consumer of the library passes in a non seakable non length supporting stream.  The issue is that appears to trigger a code path with a bug in the sdk.  UploadInSequenceInternal is going to call GetPartitionsAsync in the foreach loop.  The user stream is going to be abstracted behind a SlicedStream (implemented by a PooledMemoryStream in my testing).

Repro above may not have been very clear.  Here's an updated repro showing the behavior I'm seeing more clearly.  Repro2.zip

Bumping this thread

Just to be clear are you saying that Upload should support non-seekable and non-length streams? Or are you saying there's a scenario where the SlicedStream gets disposed too early which causes this condition to happen?
If it's the first question, I would just reiterate what was said earlier that it would be difficult to create these blocks without the length and position of the stream. If it's the second then is there a different repro you have? because looks like the repro code you have has the stream always non-seekable and non length.

The second:  In the SDK it looks like UploadInSequenceInternal is disposing the SlicedStream (PooledMemoryStream) too soon.  The only significance of the non non-seekable, non-length streams is that they just happen to take this code path when passed to Upload.  A stream that supports seeking and length goes through a different method.
If you haven't run repro (and I should have put this at the beginning for clarity):  Run with line 25 uncommented (Upload) and line 28 (UploadAsync) commented out.  The test stream is 9 bytes.  You should see the uploaded file is 0 bytes.
Reverse that and run the repro with UploadAsync instead of Upload.  You should see that the uploaded file is 9 bytes as expected.
The difference appears to be that Upload in this case (non seekable, non length) uses UploadInSequenceInternal (where the stream gets disposed too early) while UploadAsync takes a different code path that correctly uploads the stream.

Not sure how to move forward with this issue because if the stream later becomes unseekable and/or non length down the line, the upload method cannot perform like that.

A stream that supports seeking and length goes through a different method.
I'm not sure what this means. I don't think the upload method can make assumptions on what other APis to retrieve the length and seekability.

When I went to repro, it does show me the results you were mentioning, however we can't justify supporting non-length and non-seekable streams still.


Open Web SSH on the specified instance if --instance option for az webapp ssh is specified on Windows

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

Currently az webapp ssh opens Web SSH n the following line, but the argument instance of the function ssh_webapp is ignored.
https://github.com/Azure/azure-cli/blob/a7afdf11ab917e257e99b03890804c8b50a4b8ee/src/azure-cli/azure/cli/command_modules/appservice/custom.py#L4283
This causes that the CLI user cannot control to connect instance on Windows command prompt even though --instance option for az webapp ssh is used.
Describe the solution you'd like

If --instance is specified on executing az webapp ssh on Command Prompt, the Web SSH with query parameter ?instance=<specified_instance_id> should be opened.
Describe alternatives you've considered

n/a
Additional context

n/a

route to service team

Who takes a look at this issue?


Use kleur instead of chalk?

I recently saw on bundlephobia that the package kleur is way smaller than chalk and has a similiar syntax. Kleur is also dependency free. What are your thoughts about replacing it with chalk to reduce the bundle size?

Hello @muuvmuuv! I didn't know about kleur! I just took a look at it and looks great.
Aside from the fact that it's smaller than chalk, is there any other reason you think it is worth to switch to it?

I recently came across this post on twitter and thought about my personal project where I have included so many packages where I have never thought about the packages, the packages have included themselves. Or packages that are not three shakeable (e.g. for webpack).
That is why I mostly get Security Vulnerability warnings on GitHub on some of my projects. Even if I'm not directly affected by the method a package in a package in a package has used.
I think in this case here it is not very mandatory but something to overall improve the compatibility and future maintenance of the package.
And filesize is very important for me :D I know from the auto tuning industry that every gramm is worth removing.


Added checks to wait for all targets associated with the removed link to get to "removed" state

@alena1108 , can you please review the extra checks added for verifying remove links for LB services ?

@alena1108 , @cloudnautique , can you please review the changes done for addressing the validation test failure?
Following changes have been addressed :

In Lb services tests , Added checks to wait for all targets associated with the removed link to get to "removed" state
Made cleanup() method use super_client and introduced deletion of test environments
In LB tests , increased the waiting time for Lb to become active to 45 seconds and skipped leastconn test since they do not always do roundrobin when connections are not held

LGTM

LGTM


Upgrade actions

Codecov Report

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

@@            Coverage Diff            @@
##             master      #10   +/-   ##
=========================================
  Coverage          ?   92.59%
=========================================
  Files             ?        2
  Lines             ?      108
  Branches          ?        0
=========================================
  Hits              ?      100
  Misses            ?        5
  Partials          ?        3

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


make permanent an option in trigger, without writing it on triggers

Hi Noah, hi all,
I continue Alfred s' brain (a physical Alive robot)
When I communicate with Alfred, I ofter tell "Alfred", at the beginning or end sentence :
How could I tell the program : forget alfred word ??
ex :
+ [alfred] power on the tv [alfred]

I'd like rivescript to ignore this word when i speak it. So I will not have to write it everywere !
Sure I could erase it on python with a replace command, but I'd like to do it under a rive file !

I think you can use default trigger in begin.rive.
This trigger is matched before other all triggers.
check this tutorial
https://www.rivescript.com/docs/tutorial#the-begin-block
> begin
	+ request // This trigger is tested first.
        - {ok}
< begin

Something like this maybe:
+ alfred *{weight=100}
- <@>

+ * alfred{weight=100}
- <@>

The high weight value should ensure the trigger gets tested first (unless you have other triggers with weight >100). If it begins or ends with the word "alfred" it just redirects to a trigger without that word.
It may be possible to combine them into one trigger, but using optionals on either end like your original example might backfire: the first iteration you'd match the [alfred] * [alfred] trigger and it would match whether or not you said the word alfred (because it's optional, you see), and it would redirect to <star> and it would test [alfred] * [alfred] first again, and repeat forever.

Perfect, Noah. So simple...
Options (before/after) is the best choice for me.
Thanks


mavlink: keep trying to find to broadcast

This should help the Snapdragon to connect if the network is not yet up
by the time the mainapp starts. It will retry to find a network and
broadcast once it finds one.

Rebased and applied.


Update tap

@LorenzMeier

Set Baud rate console to 57600
This added the Power button control (requires bootloader to be updated)
Fixes the PWM RGB LED - Driver was tightly coupled to one other board, this has been fixed.

Rebased and applied, thanks!


See if automatic WDL tests will run

This is a test to see if the continuous integration tests using GitHub actions are working...
The branch with GitHub actions set up is sf_continuous_integration, so this PR is set up to merge into that branch.  Hopefully the PR will automatically run the tests, which at this point are just womtool validate on every WDL in the repo.

Well now I'm confused because the test appears to be running... but it's telling me that the WDL did not validate!  :(
@carmendv  any ideas?  Is there actually a problem with the WDL, or is this a problem with the tests?

omg it's working


re-add header tag global style to accommodate pre-existing extensions

Summary
Fixes #7942 and re-opens https://github.com/rancher/dashboard/issues/7341 ... #7942 is a high priority for Harvester and #7341 is a tech debt issue so I think this is a fair trade.
Components in pre-existing Harvester extensions don't have the header-layout class and consequently the styles formerly applied to header tags are lost within those extensions. I think https://github.com/rancher/dashboard/issues/7341, the request to remove global styling of tags, will be more tricky to resolve with this limitation in mind. Honestly I can't think of a good solution and am open to suggestions. The only thing I thought of was using a selector like HEADER:not([class]) in __layout.scss which would let us use header tags without those styles applied by adding any class, but it feels pretty hacky.

Considering this new information I think reverting the changes is ok. I'm also not sure of a better approach, not sure if @cnotv has some other ideas, we could create a follow-up card to investigate and deal with this scenario?

I reopened the original issue already though I think creating a new one would work just as well if preferred

@mantis-toboggan-md @scures Could we have not fixed the only issue on Harvester?
This is a serious issue in styling to apply them globally, it's going to break somewhere else.

I guess this is even worse if that's the situation. We need to understand what are the constrains and how to get rid of them.


Fix enums documentation

Looks like enums type annotation is changed and I am confused a bit because of current docs. Also there was field ... so return type will be SelectionSpect and not ValueSpec so I am removed it (I think it's intuitive to create enums not attached to any field - just like type itself).

Oops, thanks for this!


make mobile-friendly

I was just coming here to pull request and there is no code!

Refresh.  :)

and there is no code!

Must have visited between repository creation and first push. There's lots of code now!

Fixed via https://github.com/benbalter/is-pennsylvania-avenue-open/commit/818dcee59470704e6b86961f756e0b6844055f74.


Add code coverage from codecov.io

Adding code coverage. As we're improving this repository and adding more functionality, adding a coverage report provides us the visibility to find areas of improvement from a testing perspective.

Codecov Report

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

@@            Coverage Diff            @@
##             master      #18   +/-   ##
=========================================
  Coverage          ?   54.48%
=========================================
  Files             ?        9
  Lines             ?      435
  Branches          ?        0
=========================================
  Hits              ?      237
  Misses            ?      177
  Partials          ?       21

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 ab5b790...eae17a4. Read the comment docs.


Feature: Remove lodash dependency

This closes https://github.com/bsdfzzzy/vue2-hammer/issues/8 by removing the lodash dependency and instead using Object.keys().length for the if check.
This will make using vue2-hammer much smaller without the lodash dependency. 😉

Cool. Thanks for the improvement.


[Bug] 知识库导入的文档上万字的时候，出现python异常终端，DEBUG模式并没有错误

Search before asking

[X] I had searched in the issues and found no similar issues.

Operating system information
Windows
Python version information

=3.11

DB-GPT version
main
Related scenes

[ ] Chat Data
[ ] Chat Excel
[ ] Chat DB
[X] Chat Knowledge
[ ] Model Management
[ ] Dashboard
[ ] Plugins

Installation Information

[X] Installation From Source

[ ] Docker Installation

[ ] Docker Compose Installation

[ ] Cluster Installation

[ ] AutoDL Image

[ ] Other

Device information
/
Models information
Xinference的embediing模型，zhipu_proxyllm模型
What happened
/
What you expected to happen

最后的输出日志为：2024-10-30 20:01:05 ZHY-PC chromadb.config[29572] DEBUG Starting component PersistentLocalHnswSegment
How to reproduce
/
Additional context
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

通过断点调试，判断是chromadb版本问题，换了几个版本后，还是没有解决，通过windows事件查看器发现是MSVCP140.dll出现问题，前往下载最新的VC_redist.exe安装解决问题https://learn.microsoft.com/da-dk/cpp/windows/latest-supported-vc-redist?view=msvc-170


Added Diagonal solution.

https://github.com/akgmage/data-structures-and-algorithms/issues/162
comment under this issue so i can assign it to you
On Sat, 21 Jan 2023 at 13:08, Uday @.***> wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/akgmage/data-structures-and-algorithms/pull/161
Commit Summary

0b43d91
https://github.com/akgmage/data-structures-and-algorithms/pull/161/commits/0b43d9136045a372c5f44739758e558247dd629e
Added Diagonal solution.

File Changes
(1 file
https://github.com/akgmage/data-structures-and-algorithms/pull/161/files
)

A Arrays/diagonal_sum.java
https://github.com/akgmage/data-structures-and-algorithms/pull/161/files#diff-3273740ec53189627b7e6b193f648302d4255835252a897c6db2cbc0c092b8e5
(71)

Patch Links:

https://github.com/akgmage/data-structures-and-algorithms/pull/161.patch
https://github.com/akgmage/data-structures-and-algorithms/pull/161.diff
—
Reply to this email directly, view it on GitHub
https://github.com/akgmage/data-structures-and-algorithms/pull/161, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APSV2YHFCK4KJZAG6ULKT2DWTOG7PANCNFSM6AAAAAAUCIJDNQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


[Creator Starter Kit] BUG: Unable to import unmanaged solution

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Download unmanaged solution from releases
Import using Power Apps

Expected behavior
Solution imported as unmanaged
Screenshots
If applicable, add screenshots to help explain your problem.

Shows follwoing message and unable to import
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

@last72 Thanks for reporting. We will look into it and get back to you as soon as possible.

@last72 Is it possible for you to import the latest managed solution file to start using the kit? https://github.com/microsoft/powercat-creator-kit/releases/download/CreatorKit-June2022/CreatorKitCore_1.0.20220604.1_managed.zip
We were experimenting with distribution of both managed and unmanaged versions, but the recommended guidance from the Microsoft Solutions team is to use managed and then add components from the managed into your unmanaged dev solutions. Sorry for the confusion.

@last72 can you please confirm if the latest version worked?

Closing this issue - please reopen if needed.


Upgrade v0.20.0 and dockerenable = false

Deployed the new v0.20.0 version but if I add the flag dockerEnabled: false it fails with the error in the controller log:
Reconciler error	{"reconciler group": "actions.summerwind.dev", "reconciler kind": "Runner", "name": "github-runner-bn4xw-55gx9", "namespace": "github-runner", "error": "Pod \"github-runner-bn4xw-55gx9\" is invalid: spec.containers[1].image: Required value"}
We use the following example deployment:
apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
  name: github-runner
  namespace: github-runner
spec:
  replicas: 1
  template:
    spec:
      organization: org-IT
      ephemeral: true
      dockerEnabled: false
      resources:
        limits:
          memory: "2Gi"
        requests:
          memory: "1Gi"
      image: privateacr.azurecr.io/github/actions-runner:v2.283.1-ubuntu-20.04
      env:
      - name: NODE_EXTRA_CA_CERTS
        value: /usr/local/share/ca-certificates/rootca.pem

If I revert back to 0.19.0 it works as expected (no dind is injected)

FWIW this seems the same issue that has a little discussion at the end (scroll down) of #801

@mumoshu - it seems https://github.com/actions-runner-controller/actions-runner-controller/blob/24602ff3ee05303e019b395b5d6805f2ebedaa14/controllers/runner_controller.go#L569 has the responsibility for taking the runner spec - containing a bunch of keys like image, dockerEnabled, VolumeMounts, etc. and creating a corev1.Pod, to be either used directly making a pod or embedding in another resource as a PodSpec.
Rather than making the CRD more flexible in accepting unknown/preserved fields, can't we correct the logic of this function to make a valid pod?  I.e. not appending the second "docker" pod when dockerEnabled is false?

Rather than making the CRD more flexible in accepting unknown/preserved fields, can't we correct the logic of this function to make a valid pod?

Nope, because AFAIK it's k8s-apiserver rather than our controller that is emitting validation errors.

As per advise from #801 the following config fixed this issue for me:
  dockerEnabled: false
  dockerdWithinRunnerContainer: true

@mumoshu I'm not talking about stopping the validation in K8s apiserver (as removing the CRD section might do), but fixing the bad data it's reasonably complaining about.  Please look at PR #837 which lets RunnerDeployments with dockerEnabled: false succeed.

@tyrken Ah thanks! Probably I have conflated two different issues. Yours seems to fix one of them. Let me review it in a few days.

Thanks everyone- I now understand https://github.com/actions-runner-controller/actions-runner-controller/issues/801#issuecomment-923155679 by @yuri-1987 was a dupe of this one. This will be fixed via #837.


New package: QXTn v0.1.5

Registering package: QXTn
Repository: https://github.com/JuliaQX/QXTn.jl
Created by: @nmoran
Version: v0.1.5
Commit: b421f835400f65583753677d91a33ea7c2e6bb35
Git reference: master

Will rename the package.


Deterministic RPMs through modifying Build host and Build time via LD_PRELOAD

rpmbuild does not produce deterministic builds because the following metadata fields (see rpm -qip) cannot be controlled via flags:

"Build host"
"Build time"

It looks like a common approach to addressing these shortcomings is overriding int gethostname(char* name, size_t len) and time_t time(time_t* timer) in a custom library, and referencing this library in LD_PRELOAD when rpmbuild is invoked.
PR with this solution is forthcoming

Let's try to figure out how to do this without a preload library.  Have you tried defining _buildhost in the .spec file?  That is half the battle there.

@aiuto You're right - I was not aware of _buildhost and SOURCE_DATE_EPOCH, which can be used to modify the build host and build time, respectively. I'll cut another issue and PR to fix this without ld_preload.


Fixing link of ion icons 3.0 to a 3.0 list

People clicking on ion icons v3 are linked to a list of v2.   For now link to v3 listing, and change this to the actual release page when 3.0 is released.

@GantMan: It's a link to docs for Ionic v2 which uses Ionicons v3, so icons should be identical just that the design is somewhat different.

Ah, I see.  I remembered this being an issue in this  library before, and seeing it labeled v2 was the bait that got me.   Closing ticket, cheers!