[RFC] Add new reassembly package and accompanying reassemblydump example

This is the current state of our new reassembly package which does full
(IPv4 and TCP) bidirectional reassembly, implements a TCP state machine
and various security checks on TCP traffic. It is based on the existing
tcpassembly package. A new reassemblydump program is provided which uses
the reassembly package, with support for DNS and HTTP reassembly.
The code is probably not fit for merging as-is, however all comments and
feedback are welcome at this stage.
The old tcpassembly package and its example programs are removed as the
reassemblydump tool supersedes them.

My most important comment right now is that we can't (and shouldn't) remove tcpassembly and its examples.  We can mark it deprecated, but removing it is a backwards-incompatible breakage which will break all current users, and we really don't want to do that.
Having both around and marking tcpassembly as deprecated seems like it shouldn't be too bad.  Thoughts?

And, lest I forget to say this earlier, thanks so much to all involved for this work.  This is a REALLY excellent effort, and I'm amazingly pleased that my horribly hacky TCP assembly code is being replaced by something really solid.  Kudos to all who worked on this... it's really exciting.

Thanks Graeme for your congratulations. At Sentryo we really love GoPacket and we think we should give some value back to the GoPacket community. We have more to come and as already said, we are willing to participate in any OSS project around Gopacket. I will forward to all the team your last comment !

Thanks for the review, Graeme.
The rationale for the removal of the old tcpassembly package was that we were under the impression that it had no external users given the low level of activity, and since the new package is based on it the removal would avoid some code duplication.
But if you think it's important to keep providing the old package, we can keep it. What of its example programs, should we keep them as well?

I actually spoke to a few folks at GopherCon this year who were using tcpassembly, so there are some uses out there.  As far as the examples go, maybe keep them around for a bit?  Let's comment that tcpassembly is deprecated inside them.
Or, we could port them to use reassembly.  While reassemblydump looks great and does everything, I think it suffers from doing everything.  Maybe having httpassembly and statsassembly use it, but do the barest minimum to get things off the ground, would allow users to have a better starting point.  Thoughts?

Any progress on this?

Since the initial submission we have collected a set of fixes based on our production usage and we plan to submit a new version which addresses your previous comments and includes these fixes soon, but we've been very busy lately.... sorry for the delay.

And by the way, we would be happy to hire a freelancer to help submit a mergeable version. Anyone interested should contact me directly.

If you are interested in hiring someone to help merge and putback, try http://omniti.com/ they might be able to help with that.
Can you point me to the branch that has the latest version with all the fixes you mentioned?

@lhausermann So what's the state of tcpassembly? I can help if time is an issue here.

We are planning to release an updated and production proof code in October.

@lhausermann updated tcpassembly is still not ready ?

@sentryo @lhausermann is the latest version with fixes available somewhere? Keen to test this as I think I'm seeing the same issues as #112

The branch has (finally) been updated with the current version of our code, rebased on master. I believe we've addressed all Graeme's comments, and left the old tcpassembly package for now.
Reviews are welcome, and we can hopefully merge this soon! Thanks.

Thanks for the review! We'll get back to you ASAP.
We're all for merging the code into master if you deem it good enough after this last round. It would, in fact, be a great achievement :)
Regarding this account: the wizard behind the curtain is @rfrancoise but the code was authored by several people, the copyright belongs to Sentryo (the company) and we signed the corresponding CLA.

This looks like a nice addition to a great library! I'd love to have it available in mainline gopacket -- are there any obstacles to merging? Huge thanks to all the authors as well!

Got back from xmas leave a week ago, and mostly caught up on real work (read: email) since then.  Is this ready for another look?

FYI this latest sentryo:reassembly branch is working really well for me on long running http captures, albeit low bandwidth, with no issues. (Fedora 25 and OS X)

@gconnell the team would like to add a real case for 'set consumed' API we think it's needed for some case. We'd like to do it for DNS and next envision some 'binary payload' which are not really stream based like SNMP for example.

We'd like to get this code merged, so for now we have dropped the new SetConsumed() API, and we'll resubmit it later when we have a real-world example in one of the layers.
Thanks!

Also, if this is fit for merging, let us know if you want us to clean up the branch history beforehand.

Awesome work again, guys!  Merging in.
Keeping history around is always nice :)

Bookkeeping-wise:
I've made Laurent a project admin, and added sentryo as a committer.  If there's any individual accounts for the sentryo folks you'd like added in as committers, please reach out and I'll be happy to do so.

Thanks Graeme! It's been a long road, but we finally got there with your invaluable help. :)
Also thanks for granting us push access, we appreciate your trust! We'll use it wisely.

Thanks Graeme, our team here is very happy. That patch will be the foundation of upcoming project. Gopacket followers hope you appreciate !


Docs: Cleanup Docs Folder

Description

Moved /docs to the root directory
Renamed files to maintain a consistent naming style
Reorganized the folder structure for improved maintainability

Removed sprint planning file as it is no longer in use

Fixes #NA
Type of change

[X] 📝 Documentation update

How Can this be tested? Testing Plan to review this PR
I have manually tested all the reference links to ensure they all work after the name change.
Checklist:

[X] I have performed a self-review of my own code.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[X] I have made corresponding changes to the documentation.
[X] My changes generate no new warnings.
[ ] Any dependent changes have been merged and published in downstream modules.
[X] I have reviewed the Security Best Practices Document.
[X] I have followed the Naming Conventions Guide for my changes.
[X] I have ensured that my pull request title is descriptive.

Converted to draft to enable #429 to be merged first


CameraXBasic updated to use 1.0.0-alpha10

This PR has the least changes required to work with the new API.

Hey @syslogic, sorry to pull the rug from under you but the team was very eager to have the sample updated to beta01 which is now officially available and we couldn't wait another week to resolve all pending issues with this PR. Please see: https://github.com/android/camera-samples/commit/03bea1f64bbe5cc96db6e47055ca0efe2ef224c9
There are still a few things being done here that I didn't address in my commit, and you also had some ideas around media store -- if you'd like, we can shift the conversation towards that.

Sorry if you are still working on this, but I need to ask you again to first squash all your commits into a single one and then rebase again with the tip of master, otherwise the CLA check will fail since you are including previous commits.
If all else fails you can create a patch, checkout the latest version from master from scratch, then reapply your patch.

Closing from lack of action


Invalid Add-on repository!

Trying to get my Dyson fan-heater working but cannot add this as a local repository
Operating System
Home Assistant OS 6.1
Core
Version
core-2021.6.6
Supervisor
Version
supervisor-2021.06.6

This is a custom integration not add-on. Use HACS.


"citedby" doesn't work

I try the code
# Retrieve the author's data, fill-in, and print
search_query = scholarly.search_author('Steven A Cholewiak')
author = scholarly.fill(next(search_query))
print(author)

# Print the titles of the author's publications
print([pub['bib']['title'] for pub in author['publications']])

# Take a closer look at the first publication
pub = scholarly.fill(author['publications'][0])
print(pub)

# Which papers cited that publication?
print([citation['bib']['title'] for citation in scholarly.citedby(pub)])

And the "citedby" method doesn't work
---------------------------------------------------------------------------
MaxTriesExceededException                 Traceback (most recent call last)
<ipython-input-35-7ee19fb1ae51> in <module>
     12
     13 # Which papers cited that publication?
---> 14 print([citation['bib']['title'] for citation in scholarly.citedby(pub)])

/usr/local/anaconda3/lib/python3.7/site-packages/scholarly/_scholarly.py in citedby(self, object)
    226         if object['container_type'] == "Publication":
    227            publication_parser = PublicationParser(self.__nav)
--> 228            return publication_parser.citedby(object)
    229         else:
    230             print("Object not supported for bibtex exportation")

/usr/local/anaconda3/lib/python3.7/site-packages/scholarly/publication_parser.py in citedby(self, publication)
    343         if not publication['filled']:
    344             publication = self.fill(publication)
--> 345         return _SearchScholarIterator(self.nav, publication['citedby_url'])
    346
    347     def bibtex(self, publication: Publication) -> str:

/usr/local/anaconda3/lib/python3.7/site-packages/scholarly/publication_parser.py in __init__(self, nav, url)
     51         self._url = url
     52         self._nav = nav
---> 53         self._load_url(url)
     54         self.pub_parser = PublicationParser(self._nav)
     55

/usr/local/anaconda3/lib/python3.7/site-packages/scholarly/publication_parser.py in _load_url(self, url)
     56     def _load_url(self, url: str):
     57         # this is temporary until setup json file
---> 58         self._soup = self._nav._get_soup(url)
     59         self._pos = 0
     60         self._rows = self._soup.find_all('div', class_='gs_r gs_or gs_scl')

/usr/local/anaconda3/lib/python3.7/site-packages/scholarly/_navigator.py in _get_soup(self, url)
    204     def _get_soup(self, url: str) -> BeautifulSoup:
    205         """Return the BeautifulSoup for a page on scholar.google.com"""
--> 206         html = self._get_page('https://scholar.google.com{0}'.format(url))
    207         html = html.replace(u'\xa0', u' ')
    208         res = BeautifulSoup(html, 'html.parser')

/usr/local/anaconda3/lib/python3.7/site-packages/scholarly/_navigator.py in _get_page(self, pagerequest)
    156             tries += 1
    157             self._session, timeout = self.pm.get_next_proxy(num_tries = tries, old_timeout = timeout)
--> 158         raise MaxTriesExceededException("Cannot Fetch from Google Scholar.")
    159
    160

MaxTriesExceededException: Cannot Fetch from Google Scholar.

It is not that it did not work, your ip has been flagged by google, consider using a vps or wait for them to possibly unban. there are several other issues that are related so I am closing this one

It is not that it did not work, your ip has been flagged by google, consider using a vps or wait for them to possibly unban. there are several other issues that are related so I am closing this one

But I can use "search_author" and other methods...
I think I can't search author or keyword if my ip has been flagged?
Sorry to bother you.

But I can use "search_author" and other methods...
I think I can't search author or keyword if my ip has been flagged?
Sorry to bother you.

Google allows the search author. However, search pubs is blocked in the robots.txt and therefore Google will block your IP after a few searches.

Google allows the search author. However, search pubs is blocked in the robots.txt and therefore Google will block your IP after a few searches.

Thank you for the answers above. I have the same issues today as well but I just started using this library. Is it possible that Google detected a minimal usage of this function and banned it anyway?

Yes, it happens often.


[Entity] Need support to check and update for new data

In the model entity, I want to check and update the new data (from client)

Duplicate #17


Postgres query with where in (subquery) wants to return every field as Option

When selecting rows using WHERE IN (SUBQUERY) sqlx erroneously(?) tries to return the rows with every field as nullable:
https://github.com/regularfellow/todos-example/blob/c74f96319e15c2b181f140c0f7e497a5ccd8ac05/src/main.rs#L19-L22
struct Todo {
    id: i64,
    description: String,
    done: bool,
}

sqlx::query_as!(
    Todo,
    "SELECT * FROM todos WHERE id IN (SELECT todo_id FROM todo_things)"
)

➜  todos-example git:(master) cargo check
    Checking sqlx-example-postgres-connected-todos v0.1.0 (/home/github/todos-example)
error[E0308]: mismatched types
  --> src/main.rs:19:17
   |
19 |       let todos = sqlx::query_as!(
   |  _________________^
20 | |         Todo,
21 | |         "SELECT * FROM todos WHERE id IN (SELECT todo_id FROM todo_things)"
22 | |     )
   | |_____^ expected `i64`, found enum `Option`
   |
   = note: expected type `i64`
              found enum `Option<i64>`
   = note: this error originates in the macro `$crate::sqlx_macros::expand_query` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0308]: mismatched types
  --> src/main.rs:19:17
   |
19 |       let todos = sqlx::query_as!(
   |  _________________^
20 | |         Todo,
21 | |         "SELECT * FROM todos WHERE id IN (SELECT todo_id FROM todo_things)"
22 | |     )
   | |_____^ expected struct `String`, found enum `Option`
   |
   = note: expected struct `String`
                found enum `Option<String>`
   = note: this error originates in the macro `$crate::sqlx_macros::expand_query` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0308]: mismatched types
  --> src/main.rs:19:17
   |
19 |       let todos = sqlx::query_as!(
   |  _________________^
20 | |         Todo,
21 | |         "SELECT * FROM todos WHERE id IN (SELECT todo_id FROM todo_things)"
22 | |     )
   | |_____^ expected `bool`, found enum `Option`
   |
   = note: expected type `bool`
              found enum `Option<bool>`
   = note: this error originates in the macro `$crate::sqlx_macros::expand_query` (in Nightly builds, run with -Z macro-backtrace for more info)

For more information about this error, try `rustc --explain E0308`.
error: could not compile `sqlx-example-postgres-connected-todos` due to 3 previous errors

Example repo can be found from https://github.com/regularfellow/todos-example if helpful.

It's quite common for Postgres not to report nullability of columns directly unfortunately. See #367 and #1126 as some examples.

Alternatively, try this query, which should produce the same results but generate a query plan that's much friendlier to the heuristics:
SELECT todos.*
FROM todo_things
INNER JOIN todos ON todo_things.todo_id = todos.id


sbt 1.1.6

Fixes #issue_number
Problem
sbt 1.1.1 -> sbt 1.1.6
Solution
sbt 1.1.1 -> sbt 1.1.6
Notes
sbt 1.1.1 -> sbt 1.1.6
Checklist

[x] Unit test all changes
[ ] Update README.md if applicable
[ ] Add [WIP] to the pull request title if it's work in progress
[ ] Squash commits that aren't meaningful changes
[ ] Run sbt scalariformFormat test:scalariformFormat to make sure that the source files are formatted

@getquill/maintainers

thank you @sullis !


Is dll requirement still up to date?

Hey,
I was testing your project on windows with CLion 2024 without any problems.
In the README.md it says that

On windows copy cpptrace.dll to the same directory as the executable for your_target

is this still correct? It seems that the library was completely embedded in my .exe and did not require a dll.
I mean its good that I don't need a separate dll but I was just wondering.

Ah thanks of the clarification, I already thought so.
Initially we rejected this library when we saw it requires a separate dll.
(We did not even try to build it once, otherwise we would have seen that it can be linked statically).


Conflict in requirements.txt

ERROR: Cannot install -r requirements.txt (line 1) and ansible-base==2.10.7 because these package versions have conflicting dependencies.
The conflict is caused by:
The user requested ansible-base==2.10.7
ansible 3.4.0 depends on ansible-base<2.11 and >=2.10.9

Thanks for reporting this.
Issue solved.


cannot successfully run jetson nano imagenet commands

I am trying to run the jetson-inference samples on jetson nano. Running the imagenet  test app results in the following error:
command: $ ./imagenet --network=coco-dog ./images/dog_0.jpg out_dog_0.jpg
ERRINFO:
-- URI: file:///home/nvidia/jetson-inference/build/aarch64/bin/./images/dog_0.jpg
- protocol:  file
- location:  ./images/dog_0.jpg
- extension: jpg
-- deviceType: file
-- ioType:     input
-- codec:      unknown
-- width:      0
-- height:     0
-- frameRate:  0.000000
-- bitRate:    0
-- numBuffers: 4
-- zeroCopy:   true
-- flipMethod: none
-- loop:       0
[video]  created imageWriter from file:///home/nvidia/jetson-inference/build/aarch64/bin/out_dog_0.jpg
imageWriter video options:
-- URI: file:///home/nvidia/jetson-inference/build/aarch64/bin/out_dog_0.jpg
- protocol:  file
- location:  out_dog_0.jpg
- extension: jpg
-- deviceType: file
-- ioType:     output
-- codec:      unknown
-- width:      0
-- height:     0
-- frameRate:  0.000000
-- bitRate:    0
-- numBuffers: 4
-- zeroCopy:   true
-- flipMethod: none
-- loop:       0
[OpenGL] glDisplay -- X screen 0 resolution:  1680x1050
[OpenGL] glDisplay -- X window resolution:    1680x1050
[OpenGL] glDisplay -- display device initialized (1680x1050)
[video]  created glDisplay from display://0
glDisplay video options:
-- URI: display://0
- protocol:  display
- location:  0
-- deviceType: display
-- ioType:     output
-- codec:      raw
-- width:      1680
-- height:     1050
-- frameRate:  0.000000
-- bitRate:    0
-- numBuffers: 4
-- zeroCopy:   true
-- flipMethod: none
-- loop:       0
[TRT]    imageNet -- failed to initialize.
imagenet:  failed to initialize imageNet
my networks dir:
~/jetson-inference/build/aarch64/bin/networks$ ls
DetectNet-COCO-Dog  detectnet.prototxt  ilsvrc12_synset_words.txt  ssd_coco_labels.txt
my DetectNet-COCO-Dog :
~/jetson-inference/build/aarch64/bin/networks/DetectNet-COCO-Dog$ ls
class_labels.txt  digits.deploy.prototxt  mean.binaryproto   snapshot_iter_38600.caffemodel                           solver.prototxt
deploy.prototxt   info.json               original.prototxt  snapshot_iter_38600.caffemodel.1.1.7103.GPU.FP16.engine  train_val.prototxt
Can someone please suggest me what all things i can solve this issues

Hi there, I think you mean to use detectnet sample with coco-dog model.  That is an object detection model, not an image classification model.

From: oldseven<EMAIL_ADDRESS>Sent: Wednesday, September 2, 2020 9:17:09 PM
To: dusty-nv/jetson-inference<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [dusty-nv/jetson-inference] cannot successfully run jetson nano imagenet commands (#706)
I am trying to run the jetson-inference samples on jetson nano. Running the imagenet test app results in the following error:
command: $ ./imagenet --network=coco-dog ./images/dog_0.jpg out_dog_0.jpg
ERRINFO:
-- URI: file:///home/nvidia/jetson-inference/build/aarch64/bin/./images/dog_0.jpg

protocol: file
location: ./images/dog_0.jpg
extension: jpg
-- deviceType: file
-- ioType: input
-- codec: unknown
-- width: 0
-- height: 0
-- frameRate: 0.000000
-- bitRate: 0
-- numBuffers: 4
-- zeroCopy: true
-- flipMethod: none
-- loop: 0
[video] created imageWriter from file:///home/nvidia/jetson-inference/build/aarch64/bin/out_dog_0.jpg
imageWriter video options:
-- URI: file:///home/nvidia/jetson-inference/build/aarch64/bin/out_dog_0.jpg
protocol: file
location: out_dog_0.jpg
extension: jpg
-- deviceType: file
-- ioType: output
-- codec: unknown
-- width: 0
-- height: 0
-- frameRate: 0.000000
-- bitRate: 0
-- numBuffers: 4
-- zeroCopy: true
-- flipMethod: none
-- loop: 0
[OpenGL] glDisplay -- X screen 0 resolution: 1680x1050
[OpenGL] glDisplay -- X window resolution: 1680x1050
[OpenGL] glDisplay -- display device initialized (1680x1050)
[video] created glDisplay from display://0
glDisplay video options:
-- URI: display://0
protocol: display
location: 0
-- deviceType: display
-- ioType: output
-- codec: raw
-- width: 1680
-- height: 1050
-- frameRate: 0.000000
-- bitRate: 0
-- numBuffers: 4
-- zeroCopy: true
-- flipMethod: none
-- loop: 0

[TRT] imageNet -- failed to initialize.
imagenet: failed to initialize imageNet
my networks dir:
~/jetson-inference/build/aarch64/bin/networks$ ls
DetectNet-COCO-Dog detectnet.prototxt ilsvrc12_synset_words.txt ssd_coco_labels.txt
my DetectNet-COCO-Dog :
~/jetson-inference/build/aarch64/bin/networks/DetectNet-COCO-Dog$ ls
class_labels.txt digits.deploy.prototxt mean.binaryproto snapshot_iter_38600.caffemodel solver.prototxt
deploy.prototxt info.json original.prototxt snapshot_iter_38600.caffemodel.1.1.7103.GPU.FP16.engine train_val.prototxt
Can someone please suggest me what all things i can solve this issues
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/dusty-nv/jetson-inference/issues/706, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADVEGK4F5HLQSUPCNKFVZGLSD3VBLANCNFSM4QUCGCRQ.

yes,now i use command like :
python3 detectnet.py --network=coco-dog imges/test1.mp4 out_1.mp4
is ok....
However, dogs can be identified in the video file, sometimes even people are identified; do I need to train the model again?

I would recommend using the ssd-mobilenet-v2.  coco-dog is based on an outdated/slow DNN architecture.


Add documentation for VSAN policy support

Add documentation for VSAN policy support feature

PR is out for review - https://github.com/kubernetes/kubernetes.github.io/pull/3219


redo army system

at the moment, it's a mess. needs revamping.
it was originally done by @CnRXoMoX

this should be done 3adfd994a7d81d87291a1df9d09a17426ef89988

this should be done 3adfd994a7d81d87291a1df9d09a17426ef89988


Won't Connect to MQTT Until Restart

Not sure if this is more of a EmonESP issue or your particular setup. I just got mine working with emoncms, but was going to experiment with influxdb via mqtt. I put in my mqtt details and never could get it to connect. I think tried the publish mosquitto test server and still didn't connect.
I then restarted the device and it connected. It seems any time I change the settings I must restart for it to connect.

Glad you got it working! What version of EmonESP are you using?

This should have been fixed in v2.6. Please let me know if you are still having issues.


Review Requests Github Signin results in No Auth Provider

After installing software, following blog post guidance, still unable to authenticate via Demo Review Requests component.
Expected Behavior
Prompted to login to Github then continue.
Current Behavior
No Auth Provider error.
Steps to Reproduce

Installed https://github.com/RoadieHQ/roadie-backstage-plugins
Accessing Review Requests in demo page results in pop-up with Exception: No Auth Provider
Followed steps here: https://roadie.io/blog/github-auth-backstage/

Note that I have these env variables set when I run "yarn dev"
GITHUB_TOKEN
AUTH_GITHUB_CLIENT_ID
AUTH_GITHUB_CLIENT_SECRET
Also, I am authenticating with person token, not Github apps.
Context
I wish to demo roadie capabilities next week to some colleages.
Your Environment

@backstage/plugin-catalog-react version: 1.4.0
@backstage/integration version: 1.4.3

What's your app-config.yaml's auth and integrations section look like (without revealing exact secret values!)

@devinvenable is this issue still happening for you?


[MINOR][DOCS] Tighten up some key links to the project and download pages to use HTTPS

What changes were proposed in this pull request?
Tighten up some key links to the project and download pages to use HTTPS
How was this patch tested?
N/A

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/10877/
Test PASSed.

Test build #105623 has started for PR 24665 at commit 47af659.

Test build #105623 has finished for PR 24665 at commit 47af659.

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

Merged build finished. Test PASSed.

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


ACCURACY COMPARISON

I'm new to Speech Recognition. Didn't try much and have never followed before. I need suggestions to decide which Library (Open Source) or API (like Google Speech or Microsoft's) to use.
Could any compare the performance of CMU Sphinx (with fine tune), Kaldi, autosub (https://github.com/agermanidis/autosub) wrt Google Speech API in terms of WER (word error rate)?!
Also, if you could mention the compatibility and ease of setting up with Python2/3 and on Windows, would work offline/online and is free or proprietary.

@The-Gupta It sounds like you want to analyze the service, not this library.
Here is the documentation for the service itself: https://cloud.google.com/speech/
None of the maintainers of this library have particularly deep knowledge of the service beyond the API.

This library only works online (it talks to a service offered by Google).
This library is not OS dependent (i.e. works fine on Python)
This library supports Python 2.7, 3.4, 3.5 and 3.6

I am going to close this issue since I have (hopefully) answered your question. Feel free to ask follow up questions, but I don't think we'll be able to help much.

What would you suggest I shall do - ask on Reddit or where else?

https://cloud.google.com/speech/docs/support may be helpful


add ANAME support to DnsMadeEasy (ALIAS == ANAME)

Adds requested feature from #304
This maps an OctoDNS ALIAS record to DnsMadeEasy's ANAME record. In looking at their ANAME support, they allow IP addresses as values for ANAME records, which seems silly as then it's just an A record at that point, so I did not handle that case, if it's common enough I guess we could.
Example OctoDNS config
---
? ''
: - ttl: 1800
    type: ALIAS
    value: www.example.com.
  - type: MX

OctoDNS will dump all ANAME records to being ALIAS records
OctoDNS will apply all ALIAS records as being ANAME records
/cc @fahanson

Hold on, there is a big during updates.

Refactored, fixed the update issue.


separated StreamList

This PR solves #3767
Deleted StreamList component and made two extra components AllStreamList and SubscriptionsList.
Removed selected prop because it wasn't used in any place

This PR is failing system tests and the reason is this
The command "TERM=dumb tools/test --full ${TEST_SUITE}" exited with 1.```

For reference: This is a resumption of #3792.
(Please don't close a pull request just to open a new one.)

Thanks, @rheo-chiti!
I've decided to close this, for a few reasons:

The code has changed pretty significantly since this was opened. I think it would be more work to resolve the rebase conflicts than to just start over afresh.
The commits would need to follow our commit discipline more closely for us to do an efficient review.


Importing Functions from local files with dynamic paths

Bug Report
I am trying to dynamically import a function with the filename given in a function argument.
This are my approaches and outcomes:
First approach: require()
Line of Code:
const file = await require(`./${fileName}`);
And the compiler options:
"module": "ESNext",
"target": "CommonJS",
"esModuleInterop": true,

This is giving me this error:
ReferenceError: require is not defined
    at (api/test.js:116:87)
    at (api/test.js:116:24)
    at (api/test.js:130:28)

However, when i trying the same with an static path and not the variable in the path, it works, no errors.
const file = await require('./test');
Second approach: import()
Line of Code:
const file = await import(`./${fileName}`);
const file = await import('./test');
And my typescript compiler options:
"module": "es2020",
"target": "es2020",
"esModuleInterop": true,

But that is giving me this error, with the variable in the path and also without.
Error: internal error
    at (api/test.js:87:52)
    at (api/test.js:101:34)
    at (api/test.js:23:11)

Sorry, that is not supported and not expected to be supported.
You should to get your code ready before passing it to Edge Runtime, like this example:
https://edge-runtime.vercel.app/packages/runtime#usage
🙂


[BUG] Discord: cannot clean messages older than 14 days, and deleted content gets logged

Describe the bug
Discord: cannot clean messages older than 14 days, and deleted content gets logged as "verbose" for the deleted messages, which is a potential privacy violation.
To Reproduce
Steps to reproduce the behavior:

Go to a Discord guild where the bot is present.
Find a text channel with messages older than 14 days
Write '!clean all' (adjust prefix and language, if needed)
Wait until the Bot replies with a result.

Actual behavior
The Bot replies: "Sorry, could not execute the command. Reason: Internal bot's problem. Contact developers of the bot." Messages older than 14 days are not deleted. Also, the content of deleted messages get logged in "messages delete check" logs if the log verbosity level is set to 6 ("verbose").
Expected behavior
All old messages are deleted successfully. Messages' content is not logged even if the log verbosity level is 6 ("verbose").
Additional context
The first part is caused by the Discord API limitation which does not allow to remove old enough messages in batches.

Fixed in 689f7b802eec89c44ef140f5859b6d5aecf4d9ff


Add ability to declare tests in extensions

Description
Would be awesome if we can declare tests in extensions, to make "self-testable" code. Something like this:
protocol TCKSuite<Item>: AnyObject {
  associatedtype Item

  func createPublisher() -> some Publisher<Item>
}

extension TCKSuite {
  @Test
  func testSomething() {
    let publisher = self.createPublisher()
    #expect(publisher ...)
  }

  @Test
  func testAnotherThing() {
    let publisher = self.createPublisher()
    #expect(publisher ...)
  }
}

And then, simply use like this:
final class JustPublisherTest: TCKSuite {
  typealias Item = Int

  func createPublisher() -> some Publisher<Int> {
    return JustPublisher(1)
  }
}

In the (g)old XCTest we usually inherit XCTestCase to allow this behavior.
From what I understand, it's currently only possible to use @Test in structs, final classes and actors due to init and deinit methods. But why not use something like @BeforeAll or @BeforeEach? I think this will unlock use on non-final classes or extensions. What do you think?
Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
swift-testing version/commit hash
No response
Swift & OS version (output of swift --version && uname -a)
No response

Tests are fully supported in extensions. Be aware that we do not currently recommend placing your test content outside a test target as it may remain in your build product(s) after optimization.

Tests are not supported in non-final classes due to unavailable type information during macro expansion, requiring the testing library to use Self where a type name is needed and resulting in errors about "covariant Self" when used with a non-final class. We hope to remove this constraint in a future Swift PR.


ios not play audio

react-native-af-video-player version:1.19
React Native version: 0.54.0
OS:  ios

Is any one nitce this issue - Android play audio (mp3) fine ios not
Any one can support?

same problem

any one more? or solution ?

mp4 also audio not working.

did you set the iPhone silent mode?

Audio works on headphones somehow.


dml docs

There doesn't appear to be any documentation of dml itself. As far as I can tell it matches one-to-one with the class types (and their members) in dlangui, is that true?

I don't know this part of sources too good so let someone correct me if I'm wrong.
Widgets that are available for DML are registered in startup code:
https://github.com/buggins/dlangui/blob/master/src/dlangui/platforms/common/startup.d#L321
How they are registered you can see here:
https://github.com/buggins/dlangui/blob/master/src/dlangui/widgets/metadata.d
Which properties are available depends on SetXXXXXProperty() methods.
For example see widget.d file:
https://github.com/buggins/dlangui/blob/master/src/dlangui/widgets/widget.d#L1607

Docs will be added on Wiki
https://github.com/buggins/dlangui/wiki/Using-DML-to-create-layouts

I suppose current state of docs on Wiki is good enough.
Closing this issue.
If something is unclear, please submit your questions as a separate issue.


ipmag.vgpmag_magic erases 'normal' poles if there are reverse ones

What command was run:
ipmag.vgpmap_magic(dir_path=dir_path,size=50,flip=True,save_plots=True,lat_0=60,rsym='b^',rsize=50,fmt='png')
and
ipmag.vgpmap_magic(dir_path=dir_path,size=50,flip=False,save_plots=True,lat_0=60,rsym='b^',rsize=50,fmt='png')
What happened:
There are no 'normal' poles when flip is set to True.  This used to work but something happened!
What I expected to happen:
I expect the red and blue symbols as advertized for when flip is set to True
Data file(s):
sites.txt
Screenshot(s):
plot with both normal and reverse data only shows only reverse poles:

without flip, you get only the normal poles (as expected).

The way it is supposed to work (and does on jupyterhub.earthref.org, weirdly, with the same version of PmagPy).

PmagPy version:
pmagpy-4.2.98

It looks like the code is first plotting the normal:
    if len(lats) > 0:
        # add the lats and lons of the poles
        pmagplotlib.plot_map(FIG['map'], lats, lons, Opts)

and then plotting the reversed:
    if len(rlats) > 0:
        Opts['sym'] = rsym
        Opts['symsize'] = rsize
        # add the lats and lons of the poles
        pmagplotlib.plot_map(FIG['map'], rlats, rlons, Opts)

What might be happening is that the land and ocean in the second pmagplotlib.plot_map() is covering up the first set of points.

yeah but the flag ‘pltgrid’ in Opts is turned off, so it isn’t supposed to do that.  I tried a bunch of things and couldn’t get it to work….
lisa

On Apr 13, 2022, at 2:07 PM, Nick Swanson-Hysell @.***> wrote:
It looks like the code is first plotting the normal:
if len(lats) > 0:
    # add the lats and lons of the poles
    pmagplotlib.plot_map(FIG['map'], lats, lons, Opts)

and then plotting the reversed:
if len(rlats) > 0:
    Opts['sym'] = rsym
    Opts['symsize'] = rsize
    # add the lats and lons of the poles
    pmagplotlib.plot_map(FIG['map'], rlats, rlons, Opts)

What might be happening is that the land and ocean in the second pmagplotlib.plot_map() is covering up the first set of points.
—
Reply to this email directly, view it on GitHub https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_PmagPy_PmagPy_issues_649-23issuecomment-2D1098488155&d=DwMCaQ&c=-35OiAkTchMrZOngvJPOeA&r=HLmFoB00cDyPMQ7s6Fl35Q&m=YdK6F0MjPiTwHkeOagnlXs_8odwLk_4TIhDaYRAT6oATfT9R-gwwfaQCeMD83Pe7&s=trk8Koexbsga_k8ypR-gfDTYYjmAHus-4x2saelRbb4&e=, or unsubscribe https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AABKWDJBV6YJJPWHJACYIU3VE4ZQ7ANCNFSM5TL2D6EA&d=DwMCaQ&c=-35OiAkTchMrZOngvJPOeA&r=HLmFoB00cDyPMQ7s6Fl35Q&m=YdK6F0MjPiTwHkeOagnlXs_8odwLk_4TIhDaYRAT6oATfT9R-gwwfaQCeMD83Pe7&s=9fBa9bVAP8HAfAZjNb4lUKIvTG8VIvujmAVTJRBEu7Q&e=.
You are receiving this because you authored the thread.

and the really weird thing is that the exact same code works perfectly well on the jupyterhub site.  maybe I should just move on….
lisa

On Apr 13, 2022, at 2:07 PM, Nick Swanson-Hysell @.***> wrote:
It looks like the code is first plotting the normal:
if len(lats) > 0:
    # add the lats and lons of the poles
    pmagplotlib.plot_map(FIG['map'], lats, lons, Opts)

and then plotting the reversed:
if len(rlats) > 0:
    Opts['sym'] = rsym
    Opts['symsize'] = rsize
    # add the lats and lons of the poles
    pmagplotlib.plot_map(FIG['map'], rlats, rlons, Opts)

What might be happening is that the land and ocean in the second pmagplotlib.plot_map() is covering up the first set of points.
—
Reply to this email directly, view it on GitHub https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_PmagPy_PmagPy_issues_649-23issuecomment-2D1098488155&d=DwMCaQ&c=-35OiAkTchMrZOngvJPOeA&r=HLmFoB00cDyPMQ7s6Fl35Q&m=YdK6F0MjPiTwHkeOagnlXs_8odwLk_4TIhDaYRAT6oATfT9R-gwwfaQCeMD83Pe7&s=trk8Koexbsga_k8ypR-gfDTYYjmAHus-4x2saelRbb4&e=, or unsubscribe https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AABKWDJBV6YJJPWHJACYIU3VE4ZQ7ANCNFSM5TL2D6EA&d=DwMCaQ&c=-35OiAkTchMrZOngvJPOeA&r=HLmFoB00cDyPMQ7s6Fl35Q&m=YdK6F0MjPiTwHkeOagnlXs_8odwLk_4TIhDaYRAT6oATfT9R-gwwfaQCeMD83Pe7&s=9fBa9bVAP8HAfAZjNb4lUKIvTG8VIvujmAVTJRBEu7Q&e=.
You are receiving this because you authored the thread.

An inelegant solution that works is where:
    if len(rlats) > 0:
        Opts['sym'] = rsym
        Opts['symsize'] = rsize
        # add the lats and lons of the poles
        pmagplotlib.plot_map(FIG['map'], rlats, rlons, Opts)

is replaced with:
    if len(rlats) > 0:
        Opts['sym'] = rsym
        Opts['symsize'] = rsize
        if len(lats) > 0:
            color, symbol = Opts['sym'][0], Opts['sym'][1]
            plt.gca().scatter(rlons, rlats, s=Opts['symsize'], c=color, marker=symbol,
                              transform=ccrs.PlateCarree(), edgecolors=Opts['edgecolor'])
        else:
            pmagplotlib.plot_map(FIG['map'], rlats, rlons, Opts)

That solution just plots with scatter on the already generated axis and gives:

yeah but the flag ‘pltgrid’ in Opts is turned off, so it isn’t supposed to do that.

I think it is the plotting of the oceans and land rather than the grid that is hiding the normal points when the reversed map is generated with pmagplotlib.plot_map().
It is likely preferable to be using the map that is already generated rather than making a whole new map (which is what the edited code above does). I can commit that if it looks ok to you.

yes please.  that whole function needs re-writing I guess - but not today!
lisa

On Apr 13, 2022, at 2:31 PM, Nick Swanson-Hysell @.***> wrote:
yeah but the flag ‘pltgrid’ in Opts is turned off, so it isn’t supposed to do that. I tried a bunch of things and couldn’t get it to work…. lisa
… x-msg://62/#
I think it is the plotting of the oceans and land rather than the grid that is hiding the normal points when the reversed map is generated with pmagplotlib.plot_map().
It is likely preferable to be using the map that is already generated rather than making a whole new map (which is what the edited code above does). I can commit that if it looks ok to you.
—
Reply to this email directly, view it on GitHub https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_PmagPy_PmagPy_issues_649-23issuecomment-2D1098506958&d=DwMFaQ&c=-35OiAkTchMrZOngvJPOeA&r=HLmFoB00cDyPMQ7s6Fl35Q&m=fTRpZCKe4xM1Y2nYlddrDs5nMqjOBBUPvzI5AYL4bHzdIp3lVs6_hEUYS-OIDvHl&s=3EsInp0g452cM36F2XfqXwKZA7lm5K_YAFllqZzju64&e=, or unsubscribe https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AABKWDKK5GKD67KLVICFKXTVE44J5ANCNFSM5TL2D6EA&d=DwMFaQ&c=-35OiAkTchMrZOngvJPOeA&r=HLmFoB00cDyPMQ7s6Fl35Q&m=fTRpZCKe4xM1Y2nYlddrDs5nMqjOBBUPvzI5AYL4bHzdIp3lVs6_hEUYS-OIDvHl&s=QlL3IUuaLvV3pbXGF1V5WPGtdn3LW9KQ3RIV2cKu78w&e=.
You are receiving this because you authored the thread.

Did commit https://github.com/PmagPy/PmagPy/commit/e2a7b00060a939d5b45224fd9eaad53dc4bb2d6f solve the issue? If so, we can go ahead and close.

no it didn’t.  sorry.

On Apr 20, 2022, at 3:54 PM, Nick Swanson-Hysell @.***> wrote:
Did commit e2a7b00 https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_PmagPy_PmagPy_commit_e2a7b00060a939d5b45224fd9eaad53dc4bb2d6f&d=DwMCaQ&c=-35OiAkTchMrZOngvJPOeA&r=HLmFoB00cDyPMQ7s6Fl35Q&m=DYdK0kzCw7aVzPJIzs5ee-WMpaKy5fJG885Hh6m5-FGfXAaBHOwfJtg46W_Frh3q&s=T_Ngxt8hB5hHoFGsFZ1iLOF24ASthf_IYu5d2bU0Ov0&e= solve the issue? If so, we can go ahead and close.
—
Reply to this email directly, view it on GitHub https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_PmagPy_PmagPy_issues_649-23issuecomment-2D1104531479&d=DwMCaQ&c=-35OiAkTchMrZOngvJPOeA&r=HLmFoB00cDyPMQ7s6Fl35Q&m=DYdK0kzCw7aVzPJIzs5ee-WMpaKy5fJG885Hh6m5-FGfXAaBHOwfJtg46W_Frh3q&s=MfHhMRvOk--1ZCn5bp1yFYY5ylODohnPldN4atXpiiQ&e=, or unsubscribe https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AABKWDI2IXDOEWJBCDB2XS3VGCDL3ANCNFSM5TL2D6EA&d=DwMCaQ&c=-35OiAkTchMrZOngvJPOeA&r=HLmFoB00cDyPMQ7s6Fl35Q&m=DYdK0kzCw7aVzPJIzs5ee-WMpaKy5fJG885Hh6m5-FGfXAaBHOwfJtg46W_Frh3q&s=17p1-dOjg0MMiXmujvBdD_HWXbUSAiC-bxhrT6X4k8s&e=.
You are receiving this because you authored the thread.


move identification of chargeback models to chargeback base class

@martinpovolny Please review. Im trying to provide a solution for what you asked here:
https://github.com/ManageIQ/manageiq/pull/8154#issuecomment-216136200
cc @simon3z

@simon3z : agree on the placement of the method. @zeari, can you, please, move the method?

Done

Nice, :+1:

@lpichler : ping me, when done with review here, pls

@lpichler debating the implementation of chargeback_model? method should not hold up this PR.  I like the method extraction and we can always rework the implementation of chargeback_model? method in a future PR.  /cc @martinpovolny

@martinpovolny looks good. there issue for follow up PR


Uml 954 Tell search engines not to index UaL domains

Purpose
Uml 954 Tell search engines not to index UaL domains
Approach
Change to nginx config and behat test to test it. Note - the behat test has to live in smoke tests in order to tests the whole system that includes nginx
Checklist

[x] I have performed a self-review of my own code
[ ] I have added relevant logging with appropriate levels to my code
[ ] I have updated documentation (Confluence/GitHub wiki/tech debt doc) where relevant
[x] I have added tests to prove my work
[ ] The product team have tested these changes

Coverage decreased (-0.06%) to 81.604% when pulling 1a3b263d45d2b18ebc2c0faec0311e798ac6e13c on UML-954 into ad63ab61de9b34c5becff1b3c8b206a97e0771b6 on master.


WBC-1005 Set media title attribute for Piwik + WBC-947 Update WBC Player UI

Coverage remained the same at 100.0% when pulling bcd49a5e2ee6e1df0a46908de460ad64c99e3bef on WBC-1005 into 2c788e74644933c8da0d1a7e32bc0e52765646fa on master.


Problems running front page sample

This
const init = require('3d-core-raub');
const { Screen, Brush, loop } = init();

does not work as init is not a function but an object that contains init() function. So to fix it:
const {init} = require('3d-core-raub');
const { Screen, Brush, loop } = init();

But even that is failing to run, I am getting:
E:\samples\node3d>node index.js
E:\samples\node3d\node_modules\3d-core-raub\js\objects\screen.js:92
this._camera = new this.three.PerspectiveCamera(
                                               ^                                                                                TypeError: Cannot read properties of undefined (reading 'PerspectiveCamera')
     at new Screen (E:\samples\node3d\node_modules\3d-core-raub\js\objects\screen.js:92:34)

Sorry for the confusion. The example has become outdated after the latest changes. I have now updated the readme, please let me know if there are other issues.


[BUG] SKMatrix values are changed in the SkiaSharp higher version

Description
I am using SkiaSharp library to translate the text from the SKMatrix values and I have recently upgraded the SkiaSharp library version [2.80.2-preview.19]. Then I try to translate the text in the Higher version and its text width different from the older version[2.80.0]. kindly provide your suggestion to resolve this issue.
Code
SKMatrix tempMatrix = SKMatrix.MakeIdentity();
                tempMatrix.Values = new float[] { 1, 0, 0,0, 1, 0, 0, 0, 1 };
                SKMatrix.RotateDegrees(ref tempMatrix, 0);
                tempMatrix.SetScaleTranslate(1.2f, 1.0f, 0, 0);
                Console.WriteLine(tempMatrix.Values[0]);

Expected Behavior
1.2
Actual Behavior
1
Basic Information

Version with issue:  2.80.2-preview.19
Last known good version:  2.80.0
IDE:  Visual Studio 2017
Platform Target Frameworks: .NET Core 2.1

Thanks for reporting this, I have a fixing building and I will ensure it reaches the next preview: #1452

Thanks for this issue. I have fixed the issue and merged the changes. I will update NuGet as soon as CI is done.


Storyboard -> SwiftUI Converter

Added Storyboard -> SwiftUI Converter

Project URL

https://swiftify.com/#/converter/storyboard2swiftui/
Category

Tools
Description

Added Storyboard -> SwiftUI Converter under the Tools category.
Why it should be included to awesome-ios (mandatory)
This tool converts .storyboard and .xib files to SwiftUI.
This tool would be very useful for iOS developers when they want to port to SwiftUI. As more developers start developing on SwiftUI this converter would help them reuse their older UI by converting it to SwiftUI.
Checklist

[ ] Has 50 GitHub stargazers or more
[ ] Only one project/change is in this pull request
[ ] Isn't an archived project
[ ] Has more than one contributor
[ ] Has unit tests, integration tests or UI tests
[x] Addition in chronological order (bottom of category)
[ ] Supports iOS 9 / tvOS 10 or later
[ ] Supports Swift 4 or later
[ ] Has a commit from less than 2 years ago
[ ] Has a clear README in English

@Ibrahimhass Thanks for contributing!


mazeGenerator-Xavier

A blot program that generates random mazes using a Depth-First Search algorithm. This program only requires the size of the grid and the size of each cell, and it will create a new random maze each time.
I took a computer science course in 10th grade, but I don't consider myself to be a very experienced programmer, rather more of an engineer. But this was a very valuable project for me to practice my programming! Moving forward, I want to spend some time optimizing the turtle commands to decrease the path length for the Blot plotter head (and minimize the number of times it needs to pick the pen up!).

Darn, wish I saw this PR before making mine! Nice job :)

Darn, wish I saw this PR before making mine! Nice job :)

Great minds think alike! I'll have to take a look at your project to see what you did differently (and probably better!) than mine.

Thanks for the submission. We have a few mazes but it seems you approached it a bit differently.
Congrats you've earned a Blot. You can order it here.


Update VapourSynth

Motivation for this change
Usual version bump
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change
[x] Tested execution of all binary files
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build vapoursynth

Failure on aarch64-linux (full log)
Partial log (click to expand)
src/core/cpufeatures.c: In function 'getCPUFeatures':
src/core/cpufeatures.c:97:2: error: #error Do not know how to get CPU features on Linux.
 #error Do not know how to get CPU features on Linux.
  ^~~~~
src/core/cpufeatures.c:78:24: warning: unused variable 'hwcap' [-Wunused-variable]
     unsigned long long hwcap = getauxval(AT_HWCAP);
                        ^~~~~
make: *** [Makefile:1325: src/core/libvapoursynth_la-cpufeatures.lo] Error 1
builder for '/nix/store/66v0aw6v0alkd5szx3qy976b0wjlwmbd-vapoursynth-R43.drv' failed with exit code 2
error: build of '/nix/store/66v0aw6v0alkd5szx3qy976b0wjlwmbd-vapoursynth-R43.drv' failed

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/9r857nl3bq1zfr4hbqlriik5s98vb03g-vapoursynth-R43/lib/vapoursynth/libremovegrain.so
shrinking /nix/store/9r857nl3bq1zfr4hbqlriik5s98vb03g-vapoursynth-R43/lib/vapoursynth/libmorpho.so
shrinking /nix/store/9r857nl3bq1zfr4hbqlriik5s98vb03g-vapoursynth-R43/lib/vapoursynth/libmiscfilters.so
shrinking /nix/store/9r857nl3bq1zfr4hbqlriik5s98vb03g-vapoursynth-R43/lib/libvapoursynth-script.so.0.0.0
shrinking /nix/store/9r857nl3bq1zfr4hbqlriik5s98vb03g-vapoursynth-R43/lib/python3.6/site-packages/vapoursynth.so
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/9r857nl3bq1zfr4hbqlriik5s98vb03g-vapoursynth-R43/lib  /nix/store/9r857nl3bq1zfr4hbqlriik5s98vb03g-vapoursynth-R43/bin
patching script interpreter paths in /nix/store/9r857nl3bq1zfr4hbqlriik5s98vb03g-vapoursynth-R43
checking for references to /tmp/nix-build-vapoursynth-R43.drv-0 in /nix/store/9r857nl3bq1zfr4hbqlriik5s98vb03g-vapoursynth-R43...
/nix/store/9r857nl3bq1zfr4hbqlriik5s98vb03g-vapoursynth-R43

Could you please set the platform attribute to platforms = [ "x86_64-linux" ];?

darwin and windows should also be supported, so maybe platforms.x86_64.

@rnhmjoj yes, we can try this!
@GrahamcOfBorg build vapoursynth

Failure on aarch64-linux (full log)
Partial log (click to expand)
Package ‘vapoursynth-R43’ in /var/lib/gc-of-borg/nix-test-rs-26/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-26/pkgs/development/libraries/vapoursynth/default.nix:39 is not supported on ‘aarch64-linux’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/zdf63lhq7qx8w1yq2qbd8jszszz65pm5-vapoursynth-R43/lib/vapoursynth/libmiscfilters.so
shrinking /nix/store/zdf63lhq7qx8w1yq2qbd8jszszz65pm5-vapoursynth-R43/lib/vapoursynth/libimwri.so
shrinking /nix/store/zdf63lhq7qx8w1yq2qbd8jszszz65pm5-vapoursynth-R43/lib/libvapoursynth-script.so.0.0.0
shrinking /nix/store/zdf63lhq7qx8w1yq2qbd8jszszz65pm5-vapoursynth-R43/lib/python3.6/site-packages/vapoursynth.so
shrinking /nix/store/zdf63lhq7qx8w1yq2qbd8jszszz65pm5-vapoursynth-R43/lib/libvapoursynth.so
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/zdf63lhq7qx8w1yq2qbd8jszszz65pm5-vapoursynth-R43/lib  /nix/store/zdf63lhq7qx8w1yq2qbd8jszszz65pm5-vapoursynth-R43/bin
patching script interpreter paths in /nix/store/zdf63lhq7qx8w1yq2qbd8jszszz65pm5-vapoursynth-R43
checking for references to /tmp/nix-build-vapoursynth-R43.drv-0 in /nix/store/zdf63lhq7qx8w1yq2qbd8jszszz65pm5-vapoursynth-R43...
/nix/store/zdf63lhq7qx8w1yq2qbd8jszszz65pm5-vapoursynth-R43

@LnL7 fixed the package some time ago to build on darwin. I suppose it still works.

Ok. Thanks.


Command line iOS screen recording (using physical devices)

🐞 Whats wrong
irecord isnt recording iOS device screen using command line interface
🌈 Desired state
Record iOS physical device screen without Quick Time hassle
📏 Challenges
I am not aware of any other way of iOS screen recording using command line
📂 Sources
I was able to get some information from www.rotato.xyz they send me some clues on how to start.
The way Rotato does it in Swift/Cocoa is by enabling screen capture devices, and then simply treating it
as a camera via AVCaptureDevice. I haven't seen any stand-alone command-line apps that does this,
but it's definitely not impossible, so you might be able to find something on GitHub, or even build it
yourself.

This search might yield something interesting
https://github.com/search?q=kCMIOHardwarePropertyAllowScreenCaptureDevices&type=Code

https://github.com/matthutchinson/videosnap

From the version 0.0.5 videosnap now supports recording from devices. The hard thing is to handle distribution, since you need to build it yourself in Xcode due to code-signing and sandboxing on macOS.

Seems like there is no need to handle anything special regarding distribution.
All I had to do was install the tool using standard .pkg file.
https://github.com/IntergalacticPenguin/mobile-toolkit/pull/204


How to copy the files into router

Well, I am a begineer of linux, I really dont't know how to copy these files to my router... Coluld someone can explain the installation process in detail?

Hi @IceNotCold
You can use scp to copy the files to the router. Look how to use scp on the Internet
Best,
Alejandro

Okay, thanks for reply!


Expose ace editor splits option to the users

The ace editor has a horizontal and vertical split mode.  This may be a useful thing to expose to the users as it can make working on large files easier when you want to see two parts of the same file at once.  Would need shortcuts for navigating between splits, e.g. ctrl-h/j/k/l, as long as they don't conflict with browser standard shortcuts.  Possibly also have key binds to enable the splits.
This would be exposed in the existing editor context menu.
See https://ace.c9.io/build/kitchen-sink.html for an example.

Believe we need to include this extra script to make it work ace/ext-split.js
See how it is implemented in the kitchen sink
https://github.com/ajaxorg/ace/blob/c2c8c23a0b83adcae928840da6cdf5c921e3ba39/demo/kitchen-sink/util.js#L37


Review the markdown-it plugins and see which will be useful

There are some handy plugins available to the underlying Markdown parser library we use, so do a review of them and see about adding any that would serve Frogmouth well.
For example, I can see a plugin that could help with #15.
This might actually be more of an issue for Textual itself, as perhaps some of these plugins will require further widget choices when rendering the Markdown widget.

See also #46.

This can progress now that Now that https://github.com/Textualize/textual/pull/2803 is part of Textual.


Added a /_health endpoint

Signed-off-by: Miquel Sabaté Solà<EMAIL_ADDRESS>

See https://github.com/kubic-project/caasp-container-manifests/pull/42#issuecomment-300477906

Done

Sorry about the broken build, if you rebase to master it should be green.


[FEATURE] Add support for PutComposableIndexTemplateRequest while resolving request

Is your feature request related to a problem?
Security plugin doesn't support PutComposableIndexTemplateRequest while resolving request/index permissions. This causes permissions to be evaluated against all(*) indices.
Hence, a user/role with permissions limited to specific index patterns sees 403s when an index template request is performed.
What solution would you like?
Support for specific index patterns permissions with index template actions
What alternatives have you considered?
NA
Do you have any additional context?
NA

Thanks for filing, we would be happy to accept a pull request for this issue.

@shikharj05 Can you list the steps to reproduce this issue?

@DarshitChanpura The reproduce steps seem to be in the description of another issue.

@DarshitChanpura - the issue can be reproduced using the steps here - https://github.com/opensearch-project/documentation-website/issues/619
You will see a debug log line -
class org.opensearch.action.admin.indices.template.put.PutIndexTemplateRequest
not supported (It is likely not a indices related request)

However, since the workaround in above issue suggests adding indices:admin/template/* permission to cluster permissions, user can create index template for any index.
@cliu123 updated the description to include the right link.

[Triage] We've looked into this request for supporting this permissions on an index level, and with the current architecture this proposal would create many problems.  For example templates do not apply to existing indices that can be permissioned, instead they are associated with a patterns of future created indices, who can control reducing or increasing the scope of these patterns is a hard thing to describe with our current model that would lead to more confusing behavior.
As we aren't going to implement changes in this space, closing out this issue.
Note; We did find some bugs this space see https://github.com/opensearch-project/security/issues/1884, and will be addressing that issue shortly.


Update config examples for LDAP

Replace 'test.com' with 'example.com'.
The examples for how to configure LDAP, in particular the basedn was not
particularly clear since it didn't include ou=Users, which is typically
used.

Looking for input from @alexrasmussendk and @CrackerJackMack on this one.

lgtm   reference: http://tools.ietf.org/html/rfc2606#section-3

based on the conversation in IRC today we should probably mention that in some cases the LDAP servers are case sensitive and sometimes the non-OU basedn (dc=example,dc=com) search's aren't always allowed.

Indeed, I hadn't understood the case-sensitive part when I wrote the patch. While I think the updated examples (including ou=Users) should remove some cause of mistakes it might be a good idea to point out why.. are we sure this is due to recursion not being supported or could it be something else?

Since I'm not able to reproduce this myself but we do have the corresponding error and solution we can reference them both in the config example.

The message is
Authentication error: {'info': '000004DC: LdapErr: DSID-0C0906E8, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, v1db1', 'desc': 'Operations error'}

As discussed on IRC, I think we'll add it to a FAQ as to not overload the configuration file too much. I'm keeping it here for reference.


Cancel old break count and update to new break interval when changes

When I change the break interval in the Atom Settings I would like it to cancel my old session with the original time and update to the new break interval time.

@Glavin001 In version 2.0.0 once the settings are changed the break session will be reset.


server: flag to destroy metastore on restore err

This adds a new flag that when set to true will destroy the metastore and start with a fresh db file when restore runs into issues. This is a temp fix to for larger metastore restore issues that include disk malformed issues that we have seen.

Why is this not merged @LucioFranco ?

I took the liberty to resolve conflicts and push the updated change. @LucioFranco please have a look if I didn't make any mistakes and let's get this merged if we still want this

@athoscouto Lucio told me that this was done on your request. Do we still want/need this?


Any way I can use the TOMWrapper outside TE?

Hi, I'd like to write a "smart process" tool in PowerShell that you give the main table you want to process and a number of levels deep and it will traverse through the dependencies and process all the tables.
It occurred to me that it would be much easier if I could reuse the TOMWrapper that is in Tabular Editor. Is there a way that I can load the model to a wrapper outside Tabular Editor?

I haven’t tried, but since it’s a .NET lib, you should be able to create an instance of the TabularModelHandler class from TOMWrapper.dll directly from PowerShell. However, if your objective is to refresh calc tables after refreshing one or more base tables, a simple ProcessRecalc at the model level should take care of that. Or are you talking about refreshing tables based on following relationships?

Yeah, we have a big cube and usually for development we only want/need to process directly related tables to the fact that we are working on
What is the method to initialise the TOMWrapper with a folder? I think I've asked before but I think the TOMWrapper doc is out of date on the wiki, it would be great if this could be updated. I noticed the other day that the objecttype enum doesn't have calculation groups in etc.

var handler = new TabularModelHandler("c:\\MyRepository\\MyAsDatavaseFolder);


Upgrade dependencies to fix Github Security Alerts

See a private message on what exactly these are. Use your judgement in deciding if some may not be relevant.

I think I sent a message in slack with screenshots. My guess is that you don't have access because of access privileges.


CB-9660 Kill emulator/app process at the end of test run

https://issues.apache.org/jira/browse/CB-9660

Why do this at both start and end?

@dblotsky At start just to be sure that nothing is running at the moment and at the end to clean up after yourself.

Sounds good. The step will also not run when something breaks, so it will still leave the emulators open for debugging.


nbin should extract from $HOME/.local instead of /tmp

After my investigation with Warp, I think we should be working on how we can make nbin cache the package in $HOME/.local since it provides better compatibility with vendors rather than relying on /tmp because not everytime /tmp is accessible.

Resolving since nbin now uses the XDG spec.


How to use CSP to CAN??

I am currently using CSP version 1.6 on Ubuntu 18.04 LTS. I am working with GomSpace's A3200 and would like to send and receive messages with other devices using CAN communication. However, no matter how much I look into it, I cannot figure out which code to use.
I referred to this issue on GitHub and wrote a function, but I encountered the following error: - I tried various attempts to reference csp_can_socketcan_open_and_add_interface, but I failed.

Is it possible that socketcan cannot be used on the A3200?
Are there any third-party resources or documentation regarding CAN transmission with CSP that I could refer to?
I apologize for my questions not being very specific, as I am a beginner.

Hello @Elowehye, are you building an application for Ubuntu or GomSpace's A3200? If your code is meant to run on GomSpace's A3200 and it’s not running Linux, you won’t be able to use socketcan. I’m not sure if there’s any detailed documentation on this, but you can refer to the source code here: https://github.com/libcsp/libcsp/blob/v1.6/src/drivers/can/can_socketcan.c, which demonstrates how to add a CAN driver to the existing CAN interface.


get_or_none doesn't work as expected

get_or_none не работает с User.select()
get_or_none doesn't work with User.select()
code: info = await objects.get_or_none(User.select().where(User.user_id==1))
expected to receive / ожидал получить: None
Received / Получил:
Traceback (most recent call last):
  File "/home/USRRD/.local/lib/python3.12/site-packages/peewee_async.py", line 176, in get
    return list(result)[0]
           ~~~~~~~~~~~~^^^
IndexError: list index out of range

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/USRRD/.local/lib/python3.12/site-packages/peewee_async.py", line 207, in get_or_none
    return (await self.get(model_, *args, **kwargs))
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/USRRD/.local/lib/python3.12/site-packages/peewee_async.py", line 178, in get
    raise model.DoesNotExist
database.models.UserDoesNotExist

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/USRRD/projects/bots/__main__.py", line 45, in <module>
    asyncio.run(main())
  File "/usr/lib64/python3.12/asyncio/runners.py", line 194, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.12/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.12/asyncio/base_events.py", line 684, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/home/USRRD/projects/bots/__main__.py", line 39, in main
    info = await objects.get_or_none(User.select().where(User.user_id==10131433030))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/USRRD/.local/lib/python3.12/site-packages/peewee_async.py", line 208, in get_or_none
    except model_.DoesNotExist:
           ^^^^^^^^^^^^^^^^^^^
AttributeError: 'ModelSelect' object has no attribute 'DoesNotExist'

An example of a solution to an error  /  Пример решения ошибки
    async def get_or_none(self, model_, *args, **kwargs):
        """Try to get an object and return None if it doesn't exist."""
        try:
            return (await self.get(model_, *args, **kwargs))
        except peewee.DoesNotExist:
            pass

Try to use  info = await objects.get_or_none(User, user_id==1),  or better yet, use new api  ``````info = await User.aio_get_or_none(user_id==1)```

Just a bit convenient and follow the sync peewee style. Also Manager class seems redundant and will be removed next versions

No. You can see all methods of the api in the documentation.


fix(starrocks): fix starrocks coordinator incorrect try_join_all on join handle

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Previously in #16816, we used a try_join_all directly on the JoinHandle, which only returns the JoinError, while the error in the output of JoinHandle is ignored, because it is treated as Ok(Err(...)).
In this PR, we transform the future of JoinHandle to a single layer result, so that the error in join handle output will be treated as error.
Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[x] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Many thanks for @ly9chee to help locate the bug!


Generalize description of password data type

Fixes #3404

@darrelmiller , @lornajane  - I think this one can be merged+closed.

This new wording completely changes the semantics of the format.  Currently the words do not infer that a response payload is going to be changed to not include the password.  It only says that tools should not display in UI the value.  The new words say that the service should not return the value.  If you do not want a service to return the value, then the property needs to be indicated as writeOnly, which existed in 3.0 but I we removed in 3.1 because it caused a host of other challenges.

The new words say that the service should not return the value

I disagree; "obscure" and "redact" have a different definition to "omit".

@darrelmiller writeOnly was only removed from 3.1 because it was added to JSON Schema (alongside readOnly).
I agree that the proposed wording is not quite right, but I think the goal, to generalize away from "UI", is reasonable.  I assume "redact" is intended to mean "do not show in plain text to users", whether that's in a UI or whether you store the field in a user-visible database (which might show up in a UI, but without the OpenAPI-provided schema modifiers being available), or wherever.

@darrelmiller , @handrews  - if this issue sits for several weeks do we close it with a label (that might indicate some sort of lack of consensus?)
@mgrafl  - What about: "A hint to secure sensitive data".  (thinking about this a bit more, perhaps one might suggest changing the format value of "password" to something like "sensitive".  Anyways, we can tackle this from a the context that the format wants to imply rather than from comments.

I don't have a problem with the proposed wording. We can look at this as:

dropping "to UIs": I think this is fine since any client should take similar precautions
changing "obscure" to "obscure/redact": maybe unnecessary but not fundamentally wrong
changing "input" to "the value": this seems like a good change, since "input" implies some context that isn't necessarily clear

But I also want to point out that any change here should also be reflected in the "password" entry of the OpenAPI format registry

Discussed in the weekly meeting, this is a good change to have, but the wording needs an update as per the suggestions in this thread.

@darrelmiller , @handrews - if this issue sits for several weeks do we close it with a label (that might indicate some sort of lack of consensus?)
@mgrafl - What about: "A hint to secure sensitive data". (thinking about this a bit more, perhaps one might suggest changing the format value of "password" to something like "sensitive". Anyways, we can tackle this from a the context that the format wants to imply rather than from comments.

To add some context: the reason for this PR is that the OpenAPI Generator for Java Spring had passwords included in the toString method (https://github.com/OpenAPITools/openapi-generator/issues/16851), which I consider a security risk.
So, at the very least "to UIs" should be dropped from the specification (as @mikekistler explained above).
@robjtede, it appears that the registry file is in a different branch and I don't know how to include it in this PR. Should I create another PR for that?

Oh, so it is... what an interesting structure. I guess you can't include it in this PR then.

if this issue sits for several weeks do we close it with a label (that might indicate some sort of lack of consensus?)

@miqui As you now know from this week's TDC call the day after you made the above comment, we do not have these sorts of processes well-defined.
For the benefit of others who did not join the call and have the same (totally reasonable) sort of question:
I usually prefer to avoid discussing/proposing processes ad-hoc across different PRs and issues, because many people who might care will miss comments like this.  We have many process issues currently filed for such discussions.
We will be working through all of the necessary process (re)definition in the TDC calls as quickly as we can.  There is a lot to do right now, and the first thing to do is what we're doing: updating the TSC membership so that we have a fully active governing body.  Then we will have the people in place to make the process decisions (and expand the groups to which permissions like labeling and closing issues are delegated).
Until we can get there, we will just keep muddling along as we have been doing.  But that should not be the case for too much longer – I hope it is clear from the massive number of notifications anyone subscribed to this repo has been seeing this past month that we are very, very busy working to reduce the backlog and clear out cruft, which is another pre-requisite for defining processes that make sense for where we are now.  Right now we can't even see what we're working with.  We are also dealing with some cruft in our deployment processes, that makes fully finishing some of these PRs more challenging than one would think.
So let's keep the process discussions in the process issues and wait until we have re-built our governance and cleaned out enough cruft that we can see what we really need.  I know it is frustrating.  It wasn't that many years ago that I was new here and agitating for more action (resulting in a previous round of closing a lot of stale issues).  But there is a lot happening and it should be easier to participate and contribute to this project very soon.

Since we're doing a 3.0.4, should this go into the 3.0.4 branch/version first and then be forward-ported?

Note:  I have manually validated that this change passes the validate-markdown check when it is run with the correct environment.  This PR can be safely merged without rebasing (which we should do and then backport to 3.0.4, rather than waiting to re-target this).

Thanks for confirming that the tests do pass Henry!
And thanks for the original PR as well. 🙏


feat: add trust option from cutechess

reference: https://github.com/cutechess/cutechess/pull/414
already tested it, works well

merge conflicts resolved


how to get a frontal rendered image?

@Fanziapril, Hi, I am appreciated with your great job?  but I have some question.
How could I get a absolute frontal rendered image given the generated 3d face model and a InputB image which is a relative frontal face?

Please refer to #8


feat(backend): Update config API

Description

Built the API for updating configs.
Added the essential tests for the APIs - covering both unit and integration.

Related Issue

[x] Link to the related issue (if applicable) #17

Type of Change

[ ] Bugfix
[X] New Feature
[ ] Documentation

Checklist

[X] Code follows the project style guidelines
[X] Tests have been added/updated
[X] All tests pass

Summary by CodeRabbit
Release Notes

New Features

Introduced an endpoint for updating configurations via HTTP PUT requests.
Added a new class for representing configuration updates, enhancing model definitions.
Implemented validation for configuration updates to ensure data integrity.

Bug Fixes

Improved error handling for configuration updates, ensuring appropriate HTTP responses.

Tests

Added new integration and unit tests to validate the configuration update functionality, including various scenarios and edge cases.
Expanded test cases in the payloads to cover different update scenarios.

Wonderful work @Vaish24navi 🥂


Ayaneo Air Plus Desktop Mode Rotation Fix

Describe the bug
Ayaneo Air Plus Desktop Mode Rotation Fix
What did you expect to happen?
#!/usr/bin/bash

# This script fixes the screen orientation in the Desktop Mode in Bazzite-Deck KDE
# Author: d3Xt3r

SYS_ID="$(cat /sys/devices/virtual/dmi/id/product_name)"

STEAM_PID=$(cat $HOME/.steam/steam.pid)
STEAM_CMDLINE_PATH=/proc/$STEAM_PID/cmdline
STEAM_CMDLINE=$(cat $STEAM_CMDLINE_PATH)

IS_GAMEMODE=$(echo $STEAM_CMDLINE | grep gamepadui*)

sleep 1
echo $(date '+%Y-%m-%d %H:%M:%S') Starting Bazzite Desktop Orientation Fix script...| tee -a /tmp/bazrotfix.log

# This bit is needed to allow enough time for the desktop to load, otherwise the fix won't work
# Since Steam launches automatically in the Desktop mode in Bazzite-Deck, we can use it
# to determine whether or not the desktop has loaded.
while ! pgrep -x "steam" > /dev/null; do
	echo $(date '+%Y-%m-%d %H:%M:%S') Waiting for Steam to start.. | tee -a /tmp/bazrotfix.log
	sleep 0.5
done

sleep 1

# Debug: Get current outputs
kscreen-doctor --outputs 2>&1 | tee -a /tmp/bazrotfix.log

# Fix default scale on for Steam Deck hardware
if /usr/libexec/hardware/valve-hardware; then
	kscreen-doctor output.1.scale.1.00 2>&1 | tee -a /tmp/bazrotfix.log
fi

# Fix desktop orientation
# Rotation options: right, normal, left, inverted
echo $(date '+%Y-%m-%d %H:%M:%S') Fixing desktop orientation... | tee -a /tmp/bazrotfix.log
if [[ ! -z "$IS_GAMEMODE" ]]; then
	kscreen-doctor output.1.rotation.normal 2>&1 | tee -a /tmp/bazrotfix.log
elif [[ ":83E1:Loki Max:" =~ ":$SYS_ID:" ]]; then
       kscreen-doctor output.1.rotation.left 2>&1 | tee -a /tmp/bazrotfix.log
elif [[ ":83E1:AIR Plus:" =~ ":$SYS_ID:" ]]; then
	kscreen-doctor output.1.rotation.left 2>&1 | tee -a /tmp/bazrotfix.log
else
	kscreen-doctor output.1.rotation.normal 2>&1 | tee -a /tmp/bazrotfix.log
fi

echo $(date '+%Y-%m-%d %H:%M:%S') Ending Bazzite Desktop Orientation Fix script >> /tmp/bazrotfix.log
echo -e '\n' >> /tmp/bazrotfix.log

the code should be like this (i cannot test it yet due to cannot modify system file in my Air Plus
Output of rpm-ostree status
No response
Hardware
No response
Extra information or context
No response

What's the point of adding the condition of Loki here if we already have device quirks for each specific device, it would make sense if the conditions are for multiple variant of the Air Plus (ie. i3, medochino, etc).
I have an Air Plus myself and I have no problem modified the original script from here with left orientation and add the whole thing to KDE Autostart, Bazzite is immutable by nature so you shouldn't try to modify your system files

Fixed in latest build #888


Kerberos Authentication - KeyError: 'dcc'

Using the tool for a while, for the first time facing an issues with Kerberos authentication for HTB machine "Absolute".
Any suggestions? other tools for example netexec works fine with Kerberos auth for the same account.
Also,using the latest code from git.
bloodyAD -d absolute.htb --host DC.absolute.htb --dc-ip <IP_ADDRESS> -k -u d.klay -p "Darkmoonsky248girl" get writable
Traceback (most recent call last):
  File "/root/Tools/bloodyAD/bloodyAD.py", line 5, in <module>
    main.main()
  File "/root/Tools/bloodyAD/bloodyAD/main.py", line 157, in main
    for entry in output:
  File "/root/Tools/bloodyAD/bloodyAD/cli_modules/get.py", line 485, in writable
    searchbases.append(conn.ldap.domainNC)
                       ^^^^^^^^^
  File "/root/Tools/bloodyAD/bloodyAD/network/config.py", line 80, in ldap
    self._ldap = Ldap(self.conf)
                 ^^^^^^^^^^^^^^^
  File "/root/Tools/bloodyAD/bloodyAD/network/ldap.py", line 89, in __init__
    ldap_factory = LDAPConnectionFactory.from_url(
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/msldap/commons/factory.py", line 80, in from_url
    credential = UniCredential.from_url(connection_url)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/Tools/bloodyAD/bloodyAD/msldap_patch.py", line 681, in from_url
    if extra["dcc"] is not None:
       ~~~~~^^^^^^^
KeyError: 'dcc'

I think it's a package version issue. You should have at least the version 0.0.17 of asyauth

Thank you, indeed, it was.
Just updated to 0.0.20 and it just works fine now!


add custom nonce flag to cmd package token subcommand

add a custom-nonce flag to allow user supplied string array for Custom Nonce
added the flag in token subcommand for generating tokens with the custom nonce field
added the flag in unit test

/gcbrun

/gcbrun

/gcbrun


Testing save of artifact

I also didn't add an example to save results to the examples folder, so hopefully I can accomplish both here. Consider this a WIP until tests pass.
Signed-off-by: vsoch<EMAIL_ADDRESS>

That's strange... the actions workflow didn't trigger...


Export Modal’s Flow types

Summary
I'd like to use Modal’s flow types in my application to make a reusable component.
Changelog
[JavaScript] [Added] - Exported Modal’s types
Test Plan
n/a

Do you mind keeping the type names the same as they are now and just adding export type for them?

Yeah, totally! I just noticed that View’s props are exported as ViewProps, but I'll change it.

Reverted the names in 1d08c25571ff6f727aa0044a4e3e638b37d20d69.

Thank you! I’ll land it tomorrow.
We should probably change the ViewProps file then :D


oneof fields are not read from the client correctly

Using the following proto file:
syntax = "proto3";

package oneof;

service EchoOneofService {
  rpc EchoOneof(EchoOneofRequest) returns(EchoOneofResponse);
}

message AttributeValue
{
  oneof attribute
  {
    bool bool_value = 1;
    int32 integer_value = 2;
    double double_value = 3;
    string string_value = 4;
  }
}

message EchoOneofRequest {
 AttributeValue attribute = 1;
}

message EchoOneofResponse {
 AttributeValue attribute = 1;
}

generate a client and a server. Modify the server to just pass back the same data as it received from the client. Create a client that sets one of the fields comprising the oneof and then invoke the EchoOneof RPC. If you step into the generated LV code around the RPC and probe the class wire, you'll see the index and data are updated appropriately for the class in the request data. However, the index field for the class in the response isn't set even though the one of field has the appropriate data value. The flat->rich conversion then reassigns a default class value since the index is 0 rather than the appropriate index for the field number. I suspect the C++ client code is failing to assign the index based on the last set field value on the wire. This might also be related to #343?
AB#2936036

@jasonmreding let us know incase you have a fix, we can group a bunch of bugs together and make a release for you. Thanks!


[Enhancement][Cherry-Pick] iceberg refactor and optimize on fe [stage 3]

What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
https://github.com/StarRocks/starrocks/pull/18885
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.25 out of 26 committers have signed the CLA.:white_check_mark: liuyehcf:white_check_mark: Youngwb:white_check_mark: Astralidea:white_check_mark: amber-create:white_check_mark: wyb:white_check_mark: evelynzhaojie:white_check_mark: luohaha:white_check_mark: letian-jiang:white_check_mark: zaorangyang:white_check_mark: abc982627271:white_check_mark: kangkaisen:white_check_mark: kevincai:white_check_mark: xiangguangyxg:white_check_mark: decster:white_check_mark: zombee0:white_check_mark: tracymacding:white_check_mark: sduzh:white_check_mark: stdpain:white_check_mark: nshangyiming:white_check_mark: TszKitLo40:white_check_mark: EsoragotoSpirit:white_check_mark: sevev:white_check_mark: LiShuMing:white_check_mark: stephen-shelby:white_check_mark: gengjun-git:x: mergify[bot]You have signed the CLA already but the status is still pending? Let us recheck it.


undefined is not an object (evaluating 'this.props.dispatch')

So I'm just starting out with react native, redux, the works. I feel like I've got basic redux under my belt well enough, but I'm getting an error I don't understand. When I click the changeColor button on the DetailsScreen it throws an error: undefined is not an object (evaluating 'this.props.dispatch'). I'm confused because I thought dispatch() came free with connect(mapStateToProps). But something is wrong with this and I'm not sure what it is. Any pointers/help would be appreciated.
////MapviewScreen.js

import MapView, { Marker } from 'react-native-maps';
import React, { Component } from 'react';
import { View } from 'react-native'
import styles from '../styles'
import { connect } from 'react-redux'

class MapScreen extends Component {
  render() {
    const { navigation, color } = this.props
    const initialRegion = {
      latitude: 43.7370,
      longitude: -111.8338,
      latitudeDelta: 0.0922,
      longitudeDelta: 0.0421,
    }
    return (
      <View style={styles.container}>
        <MapView
          initialRegion={initialRegion}
          style={styles.map} >
          <Marker
            coordinate={initialRegion}
            onPress={() => navigation.navigate('Details')}
            pinColor={color} />
        </MapView>
      </View>
    )
  }
}

const mapStateToProps = (state) => ({
  color: state.color
})

export default connect(mapStateToProps)(MapScreen)

////DetailsScreen.js
import React, { Component } from 'react'
import { View, Text } from 'react-native'
import { Button } from 'react-native-elements'
import { connect } from 'react-redux'
import { actionCreators } from '../redux/actionCreators'

class DetailsScreen extends Component {
  changeColor() {
    this.props.dispatch(actionCreators.changeColor())
  }

  render() {
    const { checked } = this.props;
    return (
      <View style={{ flex: 1, alignItems: 'center', justifyContent: 'center' }}>
        <Text>Details Screen</Text>
        <Text>checked: {JSON.stringify(checked)}</Text>
        <Button
          title="Change Color"
          onPress={this.changeColor} />
      </View>
    )
  }
}

const mapStateToProps = (state) => ({
  checked: state.checked,
  color: state.color
})

export default connect(mapStateToProps)(DetailsScreen)

////App.js
import React, { Component } from 'react';
import { Provider } from 'react-redux'
import Drawer from './src/screens/Drawer'
import { store } from './src/redux/storeCreator'

export default class App extends Component {
  render() {
    return (
      <Provider store={store}>
        <Drawer />
      </Provider>
    )
  }
}

////Drawer.js
import React, { Component } from 'react';
import { createDrawerNavigator } from 'react-navigation';

import DetailsScreen from './DetailsScreen'
import HomeScreen from './HomeScreen'
import MapScreen from './MapScreen'

export const DrawerNav = createDrawerNavigator(
  {
    Home: HomeScreen,
    Details: DetailsScreen,
    Map: MapScreen
  },
  {
    initialRouteName: 'Map',
  }
)

class Nav extends Component {
  render() {
    return (
      <DrawerNav />
    )
  }
}

export default Nav

I got it to not throw the error on this by adding in a const mapDispatchToProps = (dispatch) => ({   changeColor: () => dispatch(actionCreators.changeColor()) }), but now I'm finding that the reducer IS being called, but it doesn't appear that my state is getting back to my map component. I'm assuming that's a different issue and I need to find issues related to that. Any direction would be great.


fix(models): hypens -> hyphens

Summary of Changes
Spelling fixes
Issue(s) that this PR Closes
n/a
Associated End To End Test PR(s)
Not opened yet (will update when I have a PR #)
Associated Documentation PR(s)
n/a
Associated Design Document(s)
n/a
Testing Instructions
n/a
Pull Request Hygiene TODOs
Please make sure the below checklist is complete.

[x] Your pull request is concise and to the point (make another PR for refactoring nearby code)
[x] Your commits are squashed into logical units of work
[x] Your commits follow the commit style guidelines

:cherry_blossom: Thank you! :cherry_blossom:

Since these are typos this can skip the normal PR process. Thanks!


Upgrade of Bartholomew Wasm Module

This is an update of the bartholomew.wasm file in the modules directory to implement fixes for relative vs absolute URLs and also improvements i.e. allowing dynamic URLs (so a user is not thrust over to the common section's menu if clicking on a shared document that exists in the common area).

Closes https://github.com/fermyon/developer/issues/481

Closes https://github.com/fermyon/developer/issues/603
Where an instance of localhost was being used for hyperlink to another page.

Closes https://github.com/fermyon/developer/issues/617

Closes https://github.com/fermyon/developer/issues/410

Closes https://github.com/fermyon/developer/issues/394


[4.0] Use Global Transform Changed Notification

Use set_notify_transform() instead of set_notify_local_transform().

don't worry about the 4.0 branch. It's probably totally broken.


Skip some pointless background work for LinkingObjects notifiers

See https://github.com/realm/realm-cocoa/issues/5816. This fixes the problem in two ways: it skips implicitly creating a notifier at all for LinkingObjects, and skips calculating the change sets for Results which do need a background notifier but don't have any callbacks.
No new tests as this should have no functional impact other than being faster. The obj-c tests do attempt to verify that the implicit notifier is created in the places where we actually want it (and those tests still pass).

Can't see anything glaringly wrong :-) outside of adding a changelog note about the performance improvement.


Sequential k8s pods deployment

Rewrite the function of k8s pods deployment by following the sequence of core-vs-rack-vhost.
Refine log and error message in database.go

Solve issue: #124

Why it calls sequential k8s pods deployment?


Brand assets for application

This is blocked by picking a name. Also seems like it could happen in Sprint 4 instead.

Picked a name! SimpleReport


Suspect buffer verification issue since flatbuffers upgrade

Detected by fuzzer in downstream project, see https://github.com/OSGeo/gdal/issues/5718.
Reproduced here with https://github.com/flatgeobuf/flatgeobuf/blob/master/src/cpp/fuzz-4642513358553088.cpp and test data from fuzzer https://github.com/flatgeobuf/flatgeobuf/blob/master/test/data/clusterfuzz-testcase-minimized-fgb_fuzzer-4642513358553088.
Reproduce in this repo cloned and the following steps:

run ./scripts/getcppdeps.sh (gets flatbuffers master source and other deps)
change dir to src/cpp
clang++ -g -o ./fuzz-4642513358553088 -Iinclude fuzz-4642513358553088.cpp
valgrind ./fuzz-4642513358553088

Output is:
==476535== Memcheck, a memory error detector
==476535== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==476535== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==476535== Command: ./fuzz-4642513358553088
==476535==
### unhandled dwarf2 abbrev form code 0x25
### unhandled dwarf2 abbrev form code 0x25
### unhandled dwarf2 abbrev form code 0x25
### unhandled dwarf2 abbrev form code 0x23
get_Form_szB: unhandled 35 (DW_FORM_rnglistx)
--476535-- WARNING: Serious error when reading debug info
--476535-- When reading debug info from /home/bjorn/code/flatgeobuf/src/cpp/fuzz-4642513358553088:
--476535-- get_Form_contents: unhandled DW_FORM
==476535== Invalid read of size 2
==476535==    at 0x10A640: unsigned short flatbuffers::ReadScalar<unsigned short>(void const*) (base.h:408)
==476535==    by 0x10A6DE: flatbuffers::Table::GetOptionalFieldOffset(unsigned short) const (table.h:42)
==476535==    by 0x109ED7: flatbuffers::Table::VerifyOffset(flatbuffers::Verifier const&, unsigned short) const (table.h:135)
==476535==    by 0x109D8A: FlatGeobuf::Header::Verify(flatbuffers::Verifier&) const (header_generated.h:551)
==476535==    by 0x1097BB: bool flatbuffers::Verifier::VerifyBufferFromStart<FlatGeobuf::Header>(char const*, unsigned long) (verifier.h:182)
==476535==    by 0x10B5B0: bool flatbuffers::Verifier::VerifyBuffer<FlatGeobuf::Header>(char const*) (verifier.h:203)
==476535==    by 0x1095E8: FlatGeobuf::VerifyHeaderBuffer(flatbuffers::Verifier&) (header_generated.h:700)
==476535==    by 0x10945E: main (fuzz-4642513358553088.cpp:28)
==476535==  Address 0x4deaf8c is 44 bytes inside a block of size 45 alloc'd
==476535==    at 0x484A2F3: operator new[](unsigned long) (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==476535==    by 0x1093A5: main (fuzz-4642513358553088.cpp:23)

Hexdump of the size prefixed buffer (which is intended to be a https://github.com/flatgeobuf/flatgeobuf/blob/master/src/fbs/header.fbs#L67 but fuzzer has made it so it's probably pretty wierd):
002d 0000 0008 0000 2020 2020 fff8 ffff
2020 2020 001d 2020 0000 0000 0004 0000
0004 0000 0020 0000 0000 0020 0010 0000
0020

You can try annotating the binary to see what parts are incorrect.
flatc --annotate <schema.fbs|bfbs> -- <that buffer in a file.bin>


All Typescript modules fail to run due to Transforming JavaScript decorators

(related PR https://github.com/dagger/dagger/pull/7573, creating an issue for tracking+visibility)
Currently, all typescript modules will fail to run due to a breaking change pushed to tsx (issue), which the typescript SDK did not pin the version of in all previous engine releases.

If your engine has a local cache of previous typescript SDK calls, it may work for a while until that local cache gets pruned

The error message looks like:
/src/dagger/src/index.ts:3:0: ERROR: Transforming JavaScript decorators to the configured target environment ("node21.3.0") is not supported yet

Workaround until next release
This will be fixed in our next release (planned for early in the week of June 17-21), but if you are blocked by this in the meantime, a temporary workaround is to use a wrapper of the typescript SDK with the fix.
To initialize a new typescript module with this SDK, run
dagger init --sdk github.com/dagger/dagger/sdk/typescript/standalone@2cbda9c7547809a35eb93ff7677e5bab4afd00c1 <rest of dagger init args>

To change an existing module to use that SDK, edit dagger.json to specify
"sdk": "github.com/dagger/dagger/sdk/typescript/standalone@2cbda9c7547809a35eb93ff7677e5bab4afd00c1"

After our next release with the fix for this we'll close this issue and you can change back to using typescript as the SDK.
We also will improve this in the future so the ability to version SDKs separate from the engine is easier, initial proposal here: https://github.com/dagger/dagger/issues/7585

Following the upstream tsx fix in https://github.com/privatenumber/tsx/issues/582 I retested a pipeline that was working prior to the tsx upstream breakage, and this is the new error observed:
Stderr:
node:internal/modules/cjs/loader:1181
  const err = new Error(`Cannot find module '${request}'`);
              ^
Error: Cannot find module<EMAIL_ADDRESS>    at createEsmNotFoundErr (node:internal/modules/cjs/loader:1181:15)
    at finalizeEsmResolution (node:internal/modules/cjs/loader:1169:15)
    at resolveExports (node:internal/modules/cjs/loader:591:14)
    at Module._findPath (node:internal/modules/cjs/loader:668:31)
    at Module._resolveFilename (node:internal/modules/cjs/loader:1130:27)
    at resolve (/usr/local/lib/node_modules/tsx/dist/register-DIqrWwRV.cjs:1:2193)
    at /usr/local/lib/node_modules/tsx/dist/register-DIqrWwRV.cjs:1:2776
    at m._resolveFilename (file:///usr/local/lib/node_modules/tsx/dist/register-AuYqD7n5.mjs:1:831)
    at Module._load (node:internal/modules/cjs/loader:985:27)
    at Module.require (node:internal/modules/cjs/loader:1235:19) {
  code: 'MODULE_NOT_FOUND',
  path<EMAIL_ADDRESS>}
Node.js v21.3.0
Error: input: module.withSource.initialize resolve: failed to initialize module: failed to call module "node" to get functions: call constructor: process "tsx --no-deprecation --tsconfig /src/pipelines/node/tsconfig.json /src/pipelines/node/src/__dagger.entrypoint.ts" did not complete successfully: exit code: 1
Stderr:
node:internal/modules/cjs/loader:1181
  const err = new Error(`Cannot find module '${request}'`);
              ^
Error: Cannot find module<EMAIL_ADDRESS>    at createEsmNotFoundErr (node:internal/modules/cjs/loader:1181:15)
    at finalizeEsmResolution (node:internal/modules/cjs/loader:1169:15)
    at resolveExports (node:internal/modules/cjs/loader:591:14)
    at Module._findPath (node:internal/modules/cjs/loader:668:31)
    at Module._resolveFilename (node:internal/modules/cjs/loader:1130:27)
    at resolve (/usr/local/lib/node_modules/tsx/dist/register-DIqrWwRV.cjs:1:2193)
    at /usr/local/lib/node_modules/tsx/dist/register-DIqrWwRV.cjs:1:2776
    at m._resolveFilename (file:///usr/local/lib/node_modules/tsx/dist/register-AuYqD7n5.mjs:1:831)
    at Module._load (node:internal/modules/cjs/loader:985:27)
    at Module.require (node:internal/modules/cjs/loader:1235:19) {
  code: 'MODULE_NOT_FOUND',
  path<EMAIL_ADDRESS>}
Node.js v21.3.0

I can also confirm the issue has been fixed by the latest version of  tsx v4.13.3!
@sipsma I let you close this issue if you're okay with that


Include node_module of containing folders in the automatic @types discovery

c:\test>tree /f
│   package.json
│
├───node_modules
│   └───@types
│       └───node
│
└───src
        index.ts
        tsconfig.json

c:\test>cd src

c:\test\src>type index.ts
import * as fs from "fs";

c:\test\src>npm install @types/node
<EMAIL_ADDRESS>c:\test
`--<EMAIL_ADDRESS>
c:\test\src>tsc
index.ts(1,21): error TS2307: Cannot find module 'fs'.

The issue here is that we only including node_modules in the current folder for automatic type discovery. this causes a lot of confusion for users trying to use the new @types package, specially if they are global. ppl do not usually associate the location of their tsconfig.json with it not working, all they see is that sometimes it does and sometimes it does not.

Worth noting that TypeScript already searches up through containing folders for typings that are bundled into their modules, i.e. modules whose package.json uses the "typings" field.
And of course the runtime behaviour with node_modules is to search up through containing folders too.