always use lodash.get

makes nested option absolete

Are there any reasons that someone wouldn't want the nested option always enabled? Since this would require a major version bump.

@knownasilya  I don't think so. The PR ignores the nested options entriely. I don't think someone specified "nested" field strings by accident.

I meant more like if they didn't use nested before, and now it's using nested by default (because of this PR), would it break anything?

no, this wouldn't break anything.

The only thing that would break is they would see an error when using the nested option. Looks like it'll have to be a major bump.

good spot!

i was thinking of adding custom defaults to single fields like this
json2csv({ data: myCars,
  fields: ['car', 'prize', 'color'],
  defaultValue: ['No Name', 0, 'likely black']}, ...

what do you think?

Great idea, it would fulfill https://github.com/zemirco/json2csv/issues/71

call it defaultValues, since it's an array, and it works with fields.

ok


Vis specs: content group - with pictograms

User story
As a maker of IBM.com experiences, I need design specs for the layout patterns that accurately reflect what's available in code so that I can design, build, and communicate with a clear understanding of what to expect.
Notes from the epic
There are a few different cases where the design spec may not reflect eh code accurately:

Some of the designs were changed during development for various reasons
Some of the designs specs were not created accurately as we went through the ontological restructuring of the patterns and subpatterns.

Additional Information

This issue is dependent on the Spacing and Pattern Structure in Visual Specs & Code #35 and the Visual Spec Standards #36 issues included on the Ideation board.

Acceptance criteria
All of the following patterns have dedicated, separate, and accurate design specs in their respective Box - [ ] Design specs are available in PDF format in this Box fodler

Moving this work to backlog until the Ideation work is finished.


Load extension error on Windows

Load extension fails with prebuilt binary from releases. I've tried both v0.14.0 and v0.13.0 dlls.
import sqlite3

conn = sqlite3.connect("tmp.db")
conn.enable_load_extension(True)
conn.load_extension("crsqlite.dll")**

> python test.py
Traceback (most recent call last):
  File "C:\Users\can.altiparmak\Downloads\test.py", line 6, in <module>
    conn.load_extension('crsqlite.dll')
sqlite3.OperationalError: Belirtilen modül bulunamadı.

Same with rust.
    let conn = Connection::open_in_memory()?;

    unsafe {
        let _guard = LoadExtensionGuard::new(&conn)?;
        conn.load_extension("crsqlite.dll", Some("sqlite3_crsqlite_init"))?
    }

Running `target\debug\rusqlite-test.exe`
Error: SqliteFailure(Error { code: Unknown, extended_code: 1 }, Some("Belirtilen modül bulunamadı.\r\n"))
error: process didn't exit successfully: `target\debug\rusqlite-test.exe` (exit code: 1)

While I can load other extension successfully, such as the ones from sqlean.
Windows 10 x64 22H2
Python 3.10.10

This is what I just tried this morning on Windows:
C:\Users\tantaman>python
Python 3.11.0 (main, Oct 24 2022, 18:26:48) [MSC v.1933 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import sqlite3
>>> conn = sqlite3.connect("tmp.db")
>>> conn.enable_load_extension(True)
>>> conn.load_extension("./crsqlite")
>>> conn.execute("SELECT crsql_siteid()").fetchall()
[(b'\xb1F\x95\x99\xaa\xd0@M\xa7\xcb\x8d\xe9L%&\xea',)]
>>>

w/ 0.14.0
I also re-enabled Windows in GitHub CI and those tests seem to be working --
https://github.com/vlcn-io/cr-sqlite/actions/runs/5599462745/jobs/10240455790

Thanks for the quick response.
Tried on another machine, same. I'll try to build myself later, and report back.
PS C:\Users\can\Desktop> python
Python 3.10.6 (tags/v3.10.6:9c7b4bd, Aug  1 2022, 21:53:49) [MSC v.1932 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import sqlite3
>>> conn = sqlite3.connect("tmp.db")
>>> conn.enable_load_extension(True)
>>> conn.load_extension("./crsqlite")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
sqlite3.OperationalError: The specified module could not be found.

hm. The fact that it says The specified module could not be found seems like the path to the extension is wrong.
Can you link the output of dir, before running python?

Sorry for late answer.
PS C:\Users\can.altiparmak\Desktop\test> dir

    Directory: C:\Users\can.altiparmak\Desktop\test

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a---          18.07.2023    11:22        1708514 crsqlite.dll
-a---          19.07.2023    09:41        1634351 crsqlite.dll-13
-a---          18.07.2023    17:45         777198 sqlean.dll

PS C:\Users\can.altiparmak\Desktop\test> python
Python 3.11.0 (main, Oct 24 2022, 18:26:48) [MSC v.1933 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import sqlite3
>>> conn = sqlite3.connect("tmp.db")
>>> conn.enable_load_extension(True)
>>> conn.load_extension("./crsqlite")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
sqlite3.OperationalError: Belirtilen modül bulunamadı.

>>> conn.load_extension("./sqlean")
>>> conn.execute("SELECT crsql_siteid()").fetchall()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
sqlite3.OperationalError: no such function: crsql_siteid
>>> conn.execute("SELECT * FROM sqlean_define").fetchall()
[]
>>>

Though, so load fine in WSL. Is there anything I can provide?

This should be fixed now.
See this release: https://github.com/vlcn-io/cr-sqlite/releases/tag/prebuild-test.zip
which includes new windows builds.
Note that v0.16 is not compatible with v0.15 DBs.

Thank you @tantaman for your work. It loads fine now.


[ModuleInterface] Short-circuit module loading for frameworks too

Follow-up to #23857 that handles frameworks as well. Oops.
Credit to @griotspeak for the branch name.
rdar://problem/50070463

@swift-ci Please smoke test

I don't think this can affect LLDB; maybe it's just a flutter?
@swift-ci Please smoke test macOS


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2250

Questions ?
Please refer to the Backport tool documentation


ListResponse more method needs review

calling more on an instance of a ListResponse returns an array not a ListResponse. I have made an adjustment that gives the correct return value but it needs review. I think there has to be a better way to do it.

Yes :) - at the moment the ListResponse is a child of Array. A more idomatic way of dealing with it would be to mixin Enumerable to ListResponse.

Done.


Enrich Repository class

This PR closes #24

It enriches the repository model.
It divides up properties in status and urls sub case classes
It adds a decoder to serialise the json returned by github.
It adds unit tests for decoders.

@fedefernandez Could you review please? Thank you.

[Current coverage][cc-pull] is 86.30%

Merging [#25][cc-pull] into [master][cc-base-branch] will increase coverage by 6.70%

@@             master        #25   diff @@
==========================================
  Files            14         14
  Lines           147        219    +72
  Methods         146        217    +71
  Messages          0          0
  Branches          1          2     +1
==========================================
+ Hits            117        189    +72
  Misses           30         30
  Partials          0          0

Powered by Codecov. Last updated by [ee346a0...f1e9d88][cc-compare]
[cc-base-branch]: https://codecov.io/gh/47deg/github4s/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/47deg/github4s/compare/ee346a0c64f56d4b0248e4059414e560243c51dc...f1e9d88db59097d8c6694a8eb5021473cd6f12bb
[cc-pull]: https://codecov.io/gh/47deg/github4s/pull/25?src=pr

LGTM!


Support tags defined on frontmatter

Hi. First of all, this project is great! I enjoy Neovim too much as to not use it for everything, including writing and note taking.
I usually declare tags on the frontmatter of a file, and I write them without the # prefix. This is actually supported by Obsidian and obsidian.nvim, but I'm not getting tag completion with moxide. Here's what I mean:

The suggestions are actually not meant to be tags (and probably they're fixed disabling tags on code blocks). Sure, I could manage to automate adding a # to every tag on every file, but I think they look cleaner without it, so I wanted to know if this is something that could be added!

Hey! Thanks for the write up and kind words! I am happy you are enjoying the project.
We can consider adding this to version 0

Hey again, this will be part of v1 through the new parser, and so that I can make v1 actually happen, I'm gonna put this off until v1 can tackle it.

-- closing as this is not considered a current issue.
If I forget to do this in v1, surely this can be reopened.


Remove IED from project file

There are currently three use cases where an IED removal is required

Simple: Someone created a new SCD file (or modifies an existing SCD file) and added too many IED's from the Import Templates menu. removing this IED should be straightforward
We have an existing SCD file. An IED (e.g. Merging Unit) has failed, and we do not have enough emergency spares, or we are no longer allowed to purchase and install this device. So now we need to replace the old IED with a new IED (and its ICD file). We are now breaking some MU/GOOSE publishers and subscriptions. OpenSCD needs to be smart enough to remove the device form all subscriptions and show the user a list af what is broken and need fixing.
Transpower decides that Bay123 is no longer required. All IED's need to be removed. Similar to the previous case, but more complex.

Thanks for filing this issue.
I propose, for now that the MVP is a simple plugin to remove one or more IEDs.
It will remove all IEDs and all references to the IED (as if it had never been there).
Including references in "LNode",  "ConnectedAP", "KDC", "ExtRef", "ClientLN", "Association", "LN > DOI[Go/SVCBRef]", "IEDName".
Case 1 and 3 are in scope. The subscriptions will all be removed for Case 2 and the end user must use the forthcoming diff/merge functionality to identify the required changes (or other documentation).
The approach will looks similar to the "Rename IEDs" plugin and allow multiselection and deletion of devices.
We'll contribute an upstream function to make this easier for others: https://github.com/OpenEnergyTools/scl-lib/issues/91

We now have a menu plugin "Remove IEDs". Please test and report any issues.


I18n for Spanish is possible?

I want contribute with Spanish, french and Italian UI translation

Yes, sure. There's been another request at #193, but I had prioritized some other tasks. I'll update this thread soon once I prepare the I18n for the app.

Duplicate of #188


Help with XML response

Setting the state does work well. Great work!
How can i get the state from this XML? „value“ is the state.

Thanks for your help.

I think you forgot to attach the XML.

Sorry

?xml version="1.0" encoding="ISO-8859-1" ?></state

<?xml version="1.0" encoding="ISO-8859-1" ?><state><datapoint ise_id='52967' value='4'/></state>

Try it with a mappers sections like this:
"mappers": [
  {
    "type": "xpath",
    "parameters": {
      "xpath": "string(/state/datapoint/@value)"
    }
  }
]

It works. Thanks


Update changelog for 3.4.0-beta release.

Summary

Update changelog for 3.4.0-beta release.

Pull Request Test Coverage Report for Build 1164

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

Totals

Change from base Build 1163:
0.0%

Covered Lines:
3597

Relevant Lines:
4007

💛  - Coveralls


Index error (r0 to dl1 process) on the base production (dec_931)

I found an error on the r0 to dl1 process for a single file and the merge jobs failed consequently.
/fefs/aswg/data/mc/DL1/AllSky/20221027_v0.9.9_base_prod/TrainingDataset/dec_931/Protons/node_corsika_theta_31.589_az_122.714_/job_logs_r0dl1/job_20543571_6.e
Traceback (most recent call last):
  File "/fefs/aswg/software/conda/envs/lstchain-v0.9.9/bin/lstchain_mc_r0_to_dl1", line 8, in <module>
    sys.exit(main())
  File "/fefs/aswg/software/conda/envs/lstchain-v0.9.9/lib/python3.8/site-packages/lstchain/scripts/lstchain_mc_r0_to_dl1.py", line 74, in main
    r0_to_dl1.r0_to_dl1(
  File "/fefs/aswg/software/conda/envs/lstchain-v0.9.9/lib/python3.8/site-packages/lstchain/reco/r0_to_dl1.py", line 459, in r0_to_dl1
    for i, event in enumerate(source):
  File "/fefs/aswg/software/conda/envs/lstchain-v0.9.9/lib/python3.8/site-packages/ctapipe/io/eventsource.py", line 278, in __iter__
    for event in self._generator():
  File "/fefs/aswg/software/conda/envs/lstchain-v0.9.9/lib/python3.8/site-packages/ctapipe/io/simteleventsource.py", line 376, in _generator
    yield from self._generate_events()
  File "/fefs/aswg/software/conda/envs/lstchain-v0.9.9/lib/python3.8/site-packages/ctapipe/io/simteleventsource.py", line 393, in _generate_events
    for counter, array_event in enumerate(self.file_):
  File "/fefs/aswg/software/conda/envs/lstchain-v0.9.9/lib/python3.8/site-packages/eventio/simtel/simtelfile.py", line 291, in iter_array_events
    self.next_low_level()
  File "/fefs/aswg/software/conda/envs/lstchain-v0.9.9/lib/python3.8/site-packages/eventio/simtel/simtelfile.py", line 155, in next_low_level
    self.current_mc_event = o.parse()
  File "/fefs/aswg/software/conda/envs/lstchain-v0.9.9/lib/python3.8/site-packages/eventio/simtel/objects.py", line 1413, in parse
    d = MCEvent.parse_mc_event(self.read(), self.header.version)
  File "src/eventio/simtel/parsing.pyx", line 53, in eventio.simtel.parsing.parse_mc_event
  File "src/eventio/simtel/parsing.pyx", line 66, in eventio.simtel.parsing.parse_mc_event
IndexError: Out of bounds on buffer access (axis 0)

/fefs/aswg/data/mc/DL1/AllSky/20221027_v0.9.9_base_prod/TrainingDataset/dec_931/Protons/merging-output.e
 31%|███       | 2618/8391 [13:48<35:41,  2.70it/s]Can't append node /dl1/event/telescope/parameters/LST_LSTCam from file /fefs/aswg/data/mc/DL1/AllSky/20221027_v0.9.9_base_prod/TrainingDataset/dec_931/Protons/node_corsika_theta_31.589_az_122.714_/dl1_simtel_corsika_theta_31.589_az_122.714_run192.h5
Traceback (most recent call last):
  File "/fefs/aswg/software/conda/envs/lstchain-v0.9.9/bin/lstchain_merge_hdf5_files", line 8, in <module>
    sys.exit(main())
  File "/fefs/aswg/software/conda/envs/lstchain-v0.9.9/lib/python3.8/site-packages/lstchain/scripts/lstchain_merge_hdf5_files.py", line 88, in main
    auto_merge_h5files(
  File "/fefs/aswg/software/conda/envs/lstchain-v0.9.9/lib/python3.8/site-packages/lstchain/io/io.py", line 341, in auto_merge_h5files
    out_node.append(in_node.read().astype(out_node.dtype))
ValueError: structures must have the same size

Thank you for reporting @SeiyaNozaki !
I will look into it

Hi @SeiyaNozaki
Is there another analysis/production affected by this error?

No, I found this error by chance:)

I have restarted the DL1 production for node node_corsika_theta_31.589_az_122.714_ and the merging.

Ok this seems fixed.

@vuillaut It seems other base productions have the same issue:
20221215_v0.9.12_base_prod and 20230127_v0.9.12_base_prod_az_tel

@vuillaut Did you already reprocess those productions? I heard gammaness distribution is strange when Estelle used this production (dec_931 in 20230127_v0.9.12_base_prod_az_tel), so I suspect this issue affects her analysis.


Don't add spaces into CC fields when you use @... for adding user

If you add Users with @... the list will be "comma + space" (, ) delimited.
However if you comment again without changing the values, Trac mentiones that it will change the Users:

Cc changed from Cyclodex, Spot to Cyclodex,Spot

I am not 100% sure if this goes into this mentions plugin or trac itselfe.
Somehow I also can reproduce this with trac itself, but perhaps this plugin should not put the space in it.

Fixed in https://github.com/trac-hacks/trac-mentions/commit/73fa8587e7c1fd6351ae0eba6973a27d7c3b2612.


Investigate supporting new Discord slash commands with Tempbot

Verify if Discord4J supports slash commands in any new versions
Sketch out what support would look like from a UX perspective
Decide if Tempbot should support slash commands

This has been done.


feat: replace timeout seconds option with timeout durations

Deprecate TIMEOUT_SECONDS options in favour of simpler TIMEOUT options.
The new options take a duration as a more user-friendly and flexible
input. It will always take precedence over the old option.
If the old option is provided, a warning is printed out.

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-08-29T20:46:06.489+0000

Duration: 8 min 35 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
160

Skipped
2

Total
162

:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

I am curious if you reviewed other configuration options also?
The lambda extension is GA, and I'd like to avoid spreading deprecations in separate releases. Instead, we should aim for reworking any existing config option that should be changed within the same release.

I am curious if you reviewed other configuration options also? The lambda extension is GA, and I'd like to avoid spreading deprecations in separate releases. Instead, we should aim for reworking any existing config option that should be changed within the same release.

Good question! I reviewed the other options but these are the only one that needed a rework IMO


Added nix 1.11.5

Hi, this is my first cask package. Let me know if I missed anything.

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if adding a new cask:

[x] Named the cask according to the token reference.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.
[x] Checked there are no open pull requests for the same cask.
[x] Checked that the cask was not already refused in closed issues.

This seems to be a CLI-only open-source tool. Please submit it first to Homebrew and only if they don’t accept it, submit here (linking back to the pull request where it was refused).
This policy is documented in faq/rejected_casks:

The app is both open-source and CLI-only (i.e. it only uses the binary artifact). In that case, and in the spirit of deduplication, submit it first to Homebrew. If it is rejected there, you may then try again in Homebrew-Cask (link us to the issue on Homebrew so we can see their reasoning for rejection).

Thanks a lot for reviewing and fixing my code.
nix is a package manager itself, just like macports which is also in this repo. It's quite unlikely that I will be able to build it from source and propose a recipe to the main homebrew repo as it's build process depends on nix itself. Right now it's bootstrapped from another system that has nix installed already.

nix is a package manager itself, just like macports

Yes but the Cask for MacPorts installs a .pkg as its artifact, which is totally different to how Nix is installed.

The Macports CLI could also probably be compiled using a Homebrew formula. After the installation I think both have the same set of constraints that don't make them good candidates for Homebrew.
They both install under a non-standard prefix. Macports uses /opt/local and Nix uses /nix. I believe that Homebrew wants to keep everything under /usr/local.
They both self-upgrade and want to manage software themselves. Having Homebrew hold one part of the software under /usr/local would probably cause issues. http://docs.brew.sh/Acceptable-Formulae.html also says "We don’t like tools that upgrade themselves"
In that sense I see Homebrew Cask most like a bootstrap in both cases. Basically if users already have Homebrew installed but need extra dependencies from macports or nix then it makes it easier to extend the package set. They could also run some curl | sh script but having this managed is nice to have and also helps by establishing the trust chain.

They could also run some curl | sh script but having this managed is nice to have and also helps by establishing the trust chain.

[emphasis added]
I really hope not, with the utmost sincerity. For one, we’re not actually verifying the script, just running it, so there’s absolutely no reason users should trust this more simply because it comes from us.
In addition, we’re adamant users do not trust us blindly: see https://github.com/caskroom/homebrew-cask/blob/master/doc/cask_language_reference/stanzas/url.md#when-url-and-homepage-hostnames-differ-add-a-comment and https://github.com/caskroom/homebrew-cask/blob/master/doc/faq/not_a_discoverability_service.md.
The rest of the argument makes sense, though.

Thanks @vitorgalvao. It's the first time I'm cooperating on a PR with the reviewer pushing code to it and it's quite nice actually, it feels much more collaborative like that.
Do you want me to squash and rebase the PR?

C: 26: 33: Align the elements of an array literal if they span more than one line.

All fixed now


Kubectls sometimes fails to set-context causes cryptic e2e failures

I did a make clean, followed by a ./hack/e2e-test.sh and found that even though my cluster seemed to be running (per gcloud compute instance list and ssh), the actual test suite didn't even start. go run hack/e2e.go -isup also returned false. From what I could tell from the logs, my e2e cluster was trying to contact <IP_ADDRESS> for validation. This immediately got me thinking about the .kubeconfig.
I tried:
 ./cluster/kubectl.sh config set-context kubernetesdev_e2e-test-beeps
current-context: "local"
Running: ./cluster/../cluster/gce/../../_output/local/bin/linux/amd64/kubectl config set-context kubernetesdev_e2e-test-beeps

followed by:
 ./cluster/kubectl.sh config view
current-context: "local"
Running: ./cluster/../cluster/gce/../../_output/local/bin/linux/amd64/kubectl config view
clusters:
  kubernetesdev_e2e-test-beeps:
    certificate-authority: /usr/local/google/home/beeps/.kube/kubernetesdev_e2e-test-beeps/kubernetes.ca.crt
    server: https://<IP_ADDRESS>
  local:
    insecure-skip-tls-verify: true
    server: http://<IP_ADDRESS>:8080
contexts:
  gce:
    cluster: ""
    user: ""
  kubernetesdev_e2e-test-beeps:
    cluster: ""
    user: ""
  local:
    cluster: local
    user: ""
current-context: local
preferences: {}
users:
  kubernetesdev_e2e-test-beeps-admin:
    auth-path: /usr/local/google/home/beeps/.kube/kubernetesdev_e2e-test-beeps/kubernetes_auth

which confused me. So I dug around a bit and found the .kubeconfig file, which had:
apiVersion: v1
clusters: []
contexts: []
current-context: kubernetesdev_e2e-test-beeps
kind: Config
preferences: {}
users: []

I then tried to correct things via something like:
cluster/kubectl.sh config set-cluster local --server=http://<IP_ADDRESS> --certificate-authorit=/usr/local/google/home/beeps/.kube/kubernetesdev_e2e-test-beeps/kubernetes.ca.crt --global
  cluster/kubectl.sh config set-context kubernetesdev_e2e-test-beeps --cluster=kubernetesdev_e2e-test-beeps --global
  cluster/kubectl.sh config use-context kubernetesdev_e2e-test-beeps

But it didn't seem to help (by which i mean ./hack/e2e.go -isup still failed).
I might've hacked around a little more at this point, after which I just deleted my .kubeconfig. Surprisingly, it now worked.
Running: ./cluster/../cluster/gce/../../_output/local/bin/linux/amd64/kubectl config view
clusters:
  kubernetesdev_e2e-test-beeps:
    certificate-authority: /usr/local/google/home/beeps/.kube/kubernetesdev_e2e-test-beeps/kubernetes.ca.crt
    server: https://<IP_ADDRESS>
  local:
    insecure-skip-tls-verify: true
    server: http://<IP_ADDRESS>:8080
contexts:
  kubernetesdev_e2e-test-beeps:
    cluster: kubernetesdev_e2e-test-beeps
    user: kubernetesdev_e2e-test-beeps-admin
  local:
    cluster: local
    user: ""
current-context: kubernetesdev_e2e-test-beeps
preferences: {}
users:
  kubernetesdev_e2e-test-beeps-admin:
    auth-path: /usr/local/google/home/beeps/.kube/kubernetesdev_e2e-test-beeps/kubernetes_auth

and go run ./hack/e2e.go -isup is happy. It would be nice if a make clean also just unset your context etc so I don't have to babysit my e2e runs.
@jlowdermilk wdyt?

This is surely related to cross-cluster kubectl.
$ ./cluster/kubectl.sh config view
current-context: "kubernetesdev_e2e-test-beeps-admin"
Running: ./cluster/../cluster/gce/../../_output/local/bin/linux/amd64/kubectl config view
clusters:
  kubernetesdev_e2e-test-beeps:
    certificate-authority: /usr/local/google/home/beeps/.kube/kubernetesdev_e2e-test-beeps/kubernetes.ca.crt
    server: https://<IP_ADDRESS>
  local:
    insecure-skip-tls-verify: true
    server: http://<IP_ADDRESS>:8080
contexts:
  kubernetesdev_e2e-test-beeps:
    cluster: kubernetesdev_e2e-test-beeps
    user: kubernetesdev_e2e-test-beeps-admin
  local:
    cluster: local
    user: ""
current-context: kubernetesdev_e2e-test-beeps-admin
preferences: {}
users:
  kubernetesdev_e2e-test-beeps-admin:
    auth-path: /usr/local/google/home/beeps/.kube/kubernetesdev_e2e-test-beeps/kubernetes_auth

-isup run output:
2015/03/05 16:19:14 Running: get status
Project: kubernetesdev
Zone: us-central1-b
current-context: "kubernetesdev_e2e-test-beeps-admin"
Running: /usr/local/google/home/beeps/goproj/src/github.com/GoogleCloudPlatform/kubernetes/hack/e2e-internal/../../cluster/../cluster/gce/../../_output/local/bin/linux/amd64/kubectl version
Client Version: version.Info{Major:"0", Minor:"12+", GitVersion:"v0.12.0-121-g404d5b1799ed85-dirty", GitCommit:"404d5b1799ed859d980120f78a4b3655dae213d7", GitTreeState:"dirty"}

(GET) http://localhost:8080/versionCouldn't read version from server: Get http://localhost:8080/version: dial tcp <IP_ADDRESS>:8080: connection refused
2015/03/05 16:19:15 Error running get status: exit status 1
2015/03/05 16:19:15 Cluster is DOWN

Getting rid of .kubeconfig
beeps@linux3234:~/goproj/src/github.com/GoogleCloudPlatform/kubernetes$ mv ./.kubeconfig /tmp
beeps@linux3234:~/goproj/src/github.com/GoogleCloudPlatform/kubernetes$ ./cluster/kubectl.sh config view
current-context: "kubernetesdev_e2e-test-beeps"
Running: ./cluster/../cluster/gce/../../_output/local/bin/linux/amd64/kubectl config view
clusters:
  kubernetesdev_e2e-test-beeps:
    certificate-authority: /usr/local/google/home/beeps/.kube/kubernetesdev_e2e-test-beeps/kubernetes.ca.crt
    server: https://<IP_ADDRESS>
  local:
    insecure-skip-tls-verify: true
    server: http://<IP_ADDRESS>:8080
contexts:
  kubernetesdev_e2e-test-beeps:
    cluster: kubernetesdev_e2e-test-beeps
    user: kubernetesdev_e2e-test-beeps-admin
  local:
    cluster: local
    user: ""
current-context: kubernetesdev_e2e-test-beeps
preferences: {}
users:
  kubernetesdev_e2e-test-beeps-admin:
    auth-path: /usr/local/google/home/beeps/.kube/kubernetesdev_e2e-test-beeps/kubernetes_auth

isup output:
beeps@linux3234:~/goproj/src/github.com/GoogleCloudPlatform/kubernetes$ go run ./hack/e2e.go -isup -v
2015/03/05 16:19:49 Running: get status
Project: kubernetesdev
Zone: us-central1-b
current-context: "kubernetesdev_e2e-test-beeps"
Running: /usr/local/google/home/beeps/goproj/src/github.com/GoogleCloudPlatform/kubernetes/hack/e2e-internal/../../cluster/../cluster/gce/../../_output/local/bin/linux/amd64/kubectl version
Client Version: version.Info{Major:"0", Minor:"12+", GitVersion:"v0.12.0-121-g404d5b1799ed85-dirty", GitCommit:"404d5b1799ed859d980120f78a4b3655dae213d7", GitTreeState:"dirty"}

(GET) https://<IP_ADDRESS>/version
Couldn't read version from server: Get https://<IP_ADDRESS>/version: dial tcp <IP_ADDRESS>:443: i/o timeout

Note that the first time isup did a GET on localhost and the second time it was on <IP_ADDRESS>, and the only difference between the runs was me mv'ing the .kubeconfig to /tmp.

If I understand correctly, when you run kubectl config set-context foo (without the --global flag), it creates a .kubeconfig locally in the directory, which overrides the global config in ~/.kube/kubeconfig.
If you run kubectl config unset contexts.foo in the same directory, it unsets the context stored in .kubeconfig in the current directory. It would have the same effect as deleting this shadow config.
I've learned not to run set-context before running e2e. What I really wanted to use was almost always use-context

Sorry, I thought I had responded a few hours ago, but I only hit preview...
@yujuhong is correct, kubectl config set-context foo creates an empty local context; kubectl config use-context foo is the command to switch active contexts.
The reason that hack/e2e.go -isup returned false in the first place is because you had an existing local .kubeconfig file containing a local current-context. I'm guessing you probably made one while testing with a local cluster. The local .kubeconfig overwrites the global one, but kube-up stores its config in theglobal ~/.kube/.kubeconfig, so when you ran the e2e tests, they were trying to talk to the local cluster.
Unfortunately this is a common source of confusion because current-context, gets overwritten by a local .kubeconfig, and by default kubectl writes to the local file. This should get better when we separate config from preferences. For now, you almost never want a local .kubeconfig.

alright, we can close this out i guess


Bi-Directional RNN support

Re-opened request on a new branch.
Contains an implementation of BRNN for the LSTM module based on the BiSequencer module here.
Let me know of any feedback/alterations!

@elbamos I've opened a PR here but there is a merge with RNN happening here. Would be nice to get BRNN support for the LSTM in RNN, hopefully @jcjohnson agrees!

Cool! I just hope it doesn't make rnn even more complicated.

On Apr 14, 2016, at 6:50 AM, Sean Naren<EMAIL_ADDRESS>wrote:
@elbamos I've opened a PR here but there is a merge with RNN happening here. Would be nice to get BRNN support for the LSTM in RNN, hopefully @jcjohnson agrees!
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

@SeanNaren Sorry I've been slow to respond to this - I agree that bidirectional RNNs are a good thing that we should support.
Overall the BRNN and ReverseSequence API looks good to me, but I have some inline comments.

No worries, thanks for the comments will work through em, all seem very valid points! I agree with loop, wasn't really a fan of it, so will try to find a better solution to it. Any suggestions would be awesome!

@jcjohnson Added a different version of reversing the sequence using this response. How does it look now?
For clearState it seems to be in the nn.Container and I add the modules to the container so hopefully that will handle it. Let me know of any more feedback or if I missed anything!

@SeanNaren The solution using narrow is pretty much the same as before, just using a different syntax; each call to copy will still invoke a separate CUDA kernel. I haven't thought through the details, but I think you should be able to reverse the sequence all at once using a single call to gather, which will probably be much faster.
Other than that it's looking good. Can you add some unit tests to make sure everything works as expected?

@jcjohnson Thanks for your suggestion helped a lot! I've pushed a change that uses gather, let me know of any feedback you may have on it, will add some unit tests now.

Added tests, let me know if there is any more issues/feedback.

I have some comments on the code (mostly minor), but I commented on two things that I think deserves some attention. But overall I think this is nice :)

@fmassa Thanks a lot man! Lots of good fixes cheers. I think I've covered all the issues, let me know if you have any more feedback.

Dear SeanNaren:
How to apply BRNN? The command
$th train.lua -input_h5 my_data.h5 -input_json my_data.json -model_type bran
just returns
Running with CUDA on GPU 0
/home/liao/torch/install/bin/luajit: ./LanguageModel.lua:46: attempt to index local 'rnn' (a nil value)
stack traceback:
./LanguageModel.lua:46: in function '__init'
/home/liao/torch/install/share/lua/5.1/torch/init.lua:91: in function </home/liao/torch/install/share/lua/5.1/torch/init.lua:87>
[C]: in function 'LanguageModel'
train.lua:90: in main chunk
[C]: in function 'dofile'
...liao/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
[C]: at 0x00405d50

How to integrate it into train.lua? New code doesn't seem to be plugged into existing torch-rnn facilities.
Also, how they behave in practice? According to papers, they're good at certain kinds of tasks and have better loss than other types of RNN. But how they compare with, say, LSTM on character-level language modelling? Are they producing better or more interesting results?


Justified Container on Safari

The justified container component aligns the content in the wrong direction in safari http://grab.by/JmNo

@hxtomprice this should now be fixed in this PR - https://github.com/holidayextras/ui-toolkit/pull/61
If you have chance can you review?


Initial review

@sttk can you review this implementation please.  I'm trying to refactor some things out of Liftoff (I have some ideas on how to integrate this with my new changes).

@phated I've reviewed and there are some confirmations and suggestions:

I think it's better to add a comment of the purpose of L16-L17.

Is it appropriate for us that the default basedir is this?

Is it better these event name can have an user specified prefix? For example:
const loader = new EventedRequire(basedir, { eventPrefix: 'preload:' });
loader.on('preload:before', (moduleName, result) => { ... });
loader.on('preload:success', (moduleName, result) => { ... });
loader.on('preload:failure', (moduleName, result) => { ... });

nyc and coveralls should be upgraded because a lot of warning and vulnerabilities are printed when npm install. I think it is enough to measure coverage only newer versions (>=node.js v6).

Thanks for reviewing!

I'll add a comment.  I should also add a test for the requireAll destructuring
The resolve module already does that defaulting so we shouldn't have to.
I am planning to make another module that re-emits events and maps them to different names so I don't think we need namespaces/prefix
I like when the whole suite is run against the entire matrix and the warnings only show up when you npm install inside the module itself, not when someone installs it into their project. Once we actually begin work on gulp 5, we'll be able to drop support for all of the old stuff.


Non-blocking Merkle tree rebuilds

The Merkle trees the node is using are most of the time rebuilt in an optimized fashion, reusing as many hashes as possible. However, whenever the number of leaves is a power of 2, the entire tree needs to be rebuilt. This PR spawns a dedicated blocking task whenever such conditions are detected, making it a non-blocking operation.

I feel we are being too granular with these blocking tasks -- but okay.

I think that I just need to make the failing tests #[tokio::test(flavor = "multi_thread")] now; checking it locally.

I feel we are being too granular with these blocking tasks -- but okay.

@Protryon I don't know if we can do better, as large-scope blocking tasks, e.g. over an entire Block import, would still involve a lot of async code, which would get delegated to non-blocking tasks and those would still become stuck once a blocking operation is encountered.
Not a huge fan either, but in this case the blocking task is spawned only for each power of 2 of the number of either commitments or serial numbers, meaning this won't happen too often.

Cc https://github.com/AleoHQ/snarkVM/pull/138 for the measurements of Merkle tree rebuild spikes.


Functions in defmt::Write to allow encoding and framing

As mentioned in #168, it would be awesome to have some functions along the lines of start_of_frame and end_or_frame, to allow implementing stuff like CRC and framing (eg. COBS).
I am opening this issue, as I think this is hidden and forgotten in the other issue, as it came up as a side-note.
Preferably the start_of_frame would contain information about the total length of the full frame to come.

@japaric hmm, why is this a breaking change? Couldn't we provide an empty default implementation in the trait?

@japaric hmm, why is this a breaking change? Couldn't we provide an empty default implementation in the trait?

hmm, why is this a breaking change?

Hmm, I forget the reason. I was probably thinking that adding a frame to the defmt stream is a breaking change and it is at the level of the "transport" crate (e.g. defmt-rtt) but it's not a breaking change in the defmt crate.

Couldn't we provide an empty default implementation in the trait?

yes, that change in defmt should be non-breaking .

hmm, why is this a breaking change?

Hmm, I forget the reason. I was probably thinking that adding a frame to the defmt stream is a breaking change and it is at the level of the "transport" crate (e.g. defmt-rtt) but it's not a breaking change in the defmt crate.

Couldn't we provide an empty default implementation in the trait?

yes, that change in defmt should be non-breaking .

What's the motivation behind putting the framing into the Write trait rather than a level up? Whatever calls write can just do the COBS encoding itself in a streaming fashion before it calls write. Then the encoding can be shared amongst the transports and doesn't need to be re-implemented.
Do some transports already have their own framing protocol and thus don't need to have one implemented on top?

Framing isn't strictly necessary to use defmt, so we wanted to make it optional. The framing algorithm to use also might be something the user wants to control (for example, COBS vs. SLIP is a tradeoff between worst-case overhead and RAM usage).

Right, the transport implementation is pluggable so it's a more flexible place for modifications.


Installation failure on MacOS 10.11

It appears that the installer is looking for Mono in /usr/bin/mono.
"'/usr/bin/mono' could not be spawned. Is it installed and on your path? If so please open an issue on the package spawning the process."
Due to the System Integrity Protection (SIP) feature, it is not possible to install or link Mono in this location. On my system, Mono is installed in /usr/local/bin/mono and is on my path.

Please set path to your mono installation (usr/local/bin) in both ionide-fsharp and ionide-paket plugin settings.

So, since this caused errors during installation, are there any necessary steps to take after setting the path to /usr/local/bin in those two packages? Re-run post-installation scripts? Or should everything be OK after just setting the path for those two plugins?

Everything should be OK after setting path.


⚠ Senior School Website has degraded performance

In e6430fb, Senior School Website (https://www.cranleigh.org) experienced degraded performance:

HTTP code: 200
Response time: 22305 ms

Resolved: Senior School Website performance has improved in a9ece25.


Add Emberlight as Arclight variant to be counted as a banned weapon

As of the release of While Guthix Sleeps, the Emberlight was introduced into the game. This item is an upgrade to the arclight, and its special attack functions the same.

@Box-Of-Hats Do you know if/when Runelite will review and merge your most recent commit, which includes the addition of the Emberlight?

@Veracs I've submitted the update to the Runelite team this morning. It usually takes up to a week for them to approve updates.
You can see the progress here: https://github.com/runelite/plugin-hub/pull/6317

@Veracs The Runelite devs have just approved this so it should be live and working now 🙂
Thanks again for your work on this issue!


[SPARK-17447] Performance improvement in Partitioner.defaultPartitioner without sortBy

What changes were proposed in this pull request?
if there are many rdds in some situations,the sort will loss he performance servely,actually we needn't sort the rdds , we can just scan the rdds one time to gain the same goal.
How was this patch tested?
manual tests

Can one of the admins verify this patch?

Jenkins test this please

Test build #65224 has started for PR 15039 at commit f5d1e24.

Test build #65224 has finished for PR 15039 at commit f5d1e24.

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/65224/
Test PASSed.

Merged to master


Update register-public-azure-ad-client-app.md

Revise the doc to improve clarity per customer feedback

@zxue : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


How about the inference speed?

Dose anyone know the running speed? including the inference and mesh rendering process.

I run it on a single 4090, for a 43s video (1300 frames), it takes about 12 mins.

Thanks @shubham-goel. To follow up,
How about the training speed? Using the same format, with a batch size of 1, on NVIDIA RTX A6000, dataloading takes about 5-7s to yield a batch of 1 sample. Is this expected and the reason why the training takes 7 days on 8 A100 GPUs, or perhaps there is a bottleneck somewhere else? Secondly, what would be the effective reason for choosing webdataset if training takes this long? Thanks for your clarification.


Syft cycloneDX: create sBOM data from source packages instead of binary packages (e.g. debian packages) ?

tl;dnr:  could syft offer an option to generare a cycloneDX sBOM for os packages by considering only the source (put in the upstream part, also in metadata:source and version from metadata:sourceVersion on some package manager) and not the binaries?
Hello,
let's start with the business background: every software delivered by our company need a proper clearance of open source software (OSS clearing).
each team must generate a sBOM and get all software component analyzed on the shared SW360 platform: components must be properly identified and the source code provided.
A dedicated team will go through the source code to check the licenses.
Each team can use the tool of its choice to create the component on sw360. Some even take the path of doing it manually.
In our team, we create software that will be eventually deployed as a container image (docker for now): we use debian bullseye slim as base image and our software can further packages either built from source, or from some package manager (debian, pip, npm, nuget) or depending of the language (go, python, nodejs, ruby, c#, etc)
Therefore, in my team, we want to use Syft to generate a CycloneDX BOM and eventually tranform it to get the components uploaded in our sw360.
Syft is already providing the list of licenses but this is unfortunately not considered (yet) in our process.
Considering debian packages, the internal team dealing with debian OS (let's call it DebT) insists of using only the source package and not the binary.
DebT start with the list of debian components with this command:
dpkg-query -f '${source:Package}|${source:Version}|${binary:Package}|${Version}\n' -W
DebT eventually only take ${source:Package}|${source:Version}
Currently, the syft command is however generating a cycloneDX bom based on the binaries. Source is sometimes set as metadata property and then attached to the upstream part in the purl. It is particularly true for libraries, generating duplicates component of the not lib variant (e.g. curl and libcurl both pointing to the same source)
I've seen this upstream= addition only for debian packages, not yet on other package providers.
This however create a purl with this upstream extension not defined in the standard:
https://github.com/package-url/purl-spec/blob/master/PURL-TYPES.rst#deb
Let's take a real exemple This is one line from the dpkg-query above.
util-linux|2.36.1-8+deb11u1|bsdutils|1:2.36.1-8+deb11u1
DebT is only interessted by scanning the source file so consider this package as
name: util-linux
version: 2.36.1-8+deb11u1
Syft generates the following in the cycloneDX sBON:
  "bom-ref": "pkg:deb/debian/bsdutils@1:2.36.1-8+deb11u1?arch=amd64&upstream=util-linux%402.36.1-8+deb11u1&distro=debian-11&package-id=677e6ace24dce684",
  "type": "library",
  "publisher": "util-linux packagers<EMAIL_ADDRESS>  "name": "bsdutils",
  "version": "1:2.36.1-8+deb11u1",
  "cpe": "cpe:2.3:a:bsdutils:bsdutils:1\\:2.36.1-8\\+deb11u1:*:*:*:*:*:*:*",
  "purl": "pkg:deb/debian/bsdutils@1:2.36.1-8+deb11u1?arch=amd64&upstream=util-linux%402.36.1-8+deb11u1&distro=debian-11",
  "properties": [
    {
      "name": "syft:metadata:installedSize",
      "value": "394"
    },
    {
      "name": "syft:metadata:source",
      "value": "util-linux"
    },
    {
      "name": "syft:metadata:sourceVersion",
      "value": "2.36.1-8+deb11u1"
    }
  ]

Source and sourceVersion are set as properties, as well as in the upstream part.
For us, the correct package data would be
  "name": "util-linux",
  "version": "2.36.1-8+deb11u1",
  "purl"<EMAIL_ADDRESS>
(according to purl spec, arch should be set as source when we speak about the source package)
We are working on our own transformation from the syft output, but I wonder if this could better be an special output from syft directly.
What do you think?

I would be very interested in the background of the upstream qualifier. I couldn't find much about it besides the initial PR #769. Is this somehow aligned with other sBOM scanning tools, CycloneDX team etc? I guess this was a workaround for the restriction of CycloneDX to one package-url, right?
Note that I once requested CycloneDX support for specifying source information via externalReferences, but additional URLs won't allow to specify source references in a unique way (think about mirrors, .zip vs. .tar.gz link etc.).
So we now prefer the arch=source qualifier in Debian purls these days, here's the background discussion: https://github.com/package-url/purl-spec/pull/57.
cc: @wagoodman

the following jq query is doing the job AFTER the syft scan in all layers, transforming the "binary based" CycloneDX to a "source base" CycloneDX:
   jq '"syft:metadata:source" as $srcName | "syft:metadata:sourceVersion" as $srcVersion
        |.components[]
        |= . + ( (
          .version as $componentVersion
          | .properties//[]
          | from_entries
          | select(has($srcName))
          | (.[$srcVersion]//$componentVersion) as $version
          | .[$srcName] as $name
          | { $name, $version, purl: "pkg:deb/debian/\($name)@\($version)?arch=source" }
        ) // {}
      )' syft_cyclonedx_bom.json > dx_bom_src.json

Thanks to StackOverflow !

@ericbl -- that's one heck of a jq command! (adding mental note to work on my jq chops... ). Let me see if I can answer a few questions.

I would be very interested in the background of the upstream qualifier.

We hesitated on adding this for a long time, specifically because the upstream param is out-of-spec, as pointed out. Using the pURL in this way has been very useful from a vulnerability matching point-of-view in grype, probably for the same reason  that your internal DebT wants the SBOM results oriented with a source purl instead of being aligned with the binary: for vulnerability matching the source package matters most, since vulnerabilities tend to be written against the source package and not downstream packages.
Syft supports multiple SBOM formats, and the goal is to allow for grype to interop with these SBOMs in a way where vulnerability matching will not differ just because you've decided to use a different SBOM format. We explored multiple options for both SPDX and CycloneDX to express a source package clearly for the purposes of vulnerability matching but also wanted to ensure that it was clear to the SBOM consumer that these source packages were not found to be installed. At the time the methods we explored couldn't check all the boxes (the boxes were roughly: a) be clear to the user what's being expressed, 2) be able to show what's installed vs upstream relationships, and 3) be interoperable with multiple formats).
Grype also supports being able to perform vulnerability matching when only specifying a pURL or set of pURLs. This, combined with the other efforts, made me lean towards adding an out-of-spec qualifier onto the pURL. upstream aligned nicely with multiple OS ecosystems that have these vulnerability matching requirements.

I've seen this upstream= addition only for debian packages, not yet on other package providers.

All OS catalogers tend to have this feature: https://github.com/search?q=repo%3Aanchore%2Fsyft PURLQualifierUpstream&type=code (alpm, apk, dep, rpm).

we now prefer the arch=source qualifier in Debian purls these days

Correct, no dispute here about the source qualifier 👍 I agree that using the source qualifier is the right thing to do when writing a pURL for a source package.
However, this did not fulfill the needs of what we're trying to convey, which is "here is the [binary] package we found, and this is the package which it came from (the source package)". A pURL representing the source package alone only answers half of what was needed, and providing multiple pURLs is confusing for something that should be used as an identity (so should be singular).

All OS catalogers tend to have this feature: https://github.com/search?q=repo%3Aanchore%2Fsyft PURLQualifierUpstream&type=code (alpm, apk, dep, rpm).

thanks, I tried only on debian, npm, python, etc, but not yet on other linux distrib. I ll do asap that with alpine / apk.
It means my jq command above is not correct and shall be even more complex with a regex to rebuild the purl!

I found the cycloneDX spec a bit unprecise of the discussion, I did not find any rule either "source purl" or "binary purl".
Adding a 2nd purl in the cycloneDX spec could be an option...

@ericbl, a while back, I requested a similar topic with the CycloneDX team. It was not about a source purl, but adding a specific type for external source references. The CycloneDX team however claimed that it's not easy/possible to distinct between "source" and "binary" references throughout all ecosystems: https://github.com/CycloneDX/specification/issues/98. I guess the same arguments would apply on source purls, so I wouldn't expect this to happen soon...
Also taking the point of @wagoodman into consideration, that an SBOM should express what is "installed" in an image, a "source purl" would somehow be inconsistent in the default SBOM.
But still, the feature as requested by @ericbl here – adding a syft --upstream mode to produce a "upstream relationship SBOM", would be very helpful for us and I think it wouldn't be in contradiction with CycloneDX spec or the other goals of Syft.

the extraction of the source purl differs from package manager.
For instance with alpine, I just got this component (I removed some data irrelevant for current discussion)
{
	 "bom-ref": "pkg:apk/alpine/busybox-binsh@1.35.0-r29?arch=x86_64&upstream=busybox&distro=alpine-3.17.2&package-id=256fc96b4a8c4da8",
	  "type": "library",
	  "publisher": "Sören Tempel<EMAIL_ADDRESS>	  "name": "busybox-binsh",
	  "version": "1.35.0-r29",
	  "purl": "pkg:apk/alpine/busybox-binsh@1.35.0-r29?arch=x86_64&upstream=busybox&distro=alpine-3.17.2",
	  "externalReferences": [
		{
		  "url": "https://busybox.net/",
		  "type": "distribution"
		}
	  ],
	  "properties": [
		{
		  "name": "syft:package:foundBy",
		  "value": "apkdb-cataloger"
		},
		{
		  "name": "syft:package:metadataType",
		  "value": "ApkMetadata"
		},
		{
		  "name": "syft:package:type",
		  "value": "apk"
		},
		{
		  "name": "syft:metadata:originPackage",
		  "value": "busybox"
		},
		{
		  "name": "syft:metadata:size",
		  "value": "1547"
		}
	  ]
}

so the upstream part is built from the "syft:metadata:originPackage" instead of from the "syft:metadata:source" with Debian.
This means my proposed jq command above is wrong: I should parse the purl on the upstream part, and not considering the metadata that differ from package manager.
Having a ' upstream' mode as proposed by Gernot would help us a lot and avoid getting crazy with jq :)

There are two paths forward:

The path you suggested: add an application configuration option to replace the binary purls for source purls on OS packages.
Another path: add an application configuration option to add additional packages that represent the source packages (derived from information we find from the binary packages) and add package-to-package relationships between them (e.g. build-dependency-of).

These aren't mutually exclusive, so both in theory could be done, but I'm interested in hearing folks thoughts on which might be more useful (or if there are any other ideas here).

your 2nd path proposal seems a bit more complex. And how could I then filter out the packages listing binary information I am not interested with?

as I wrote above, my jq query is specific to Debian and difficult to maintain.
Therefore, I replaced it in our pipeline with the following python script.
`import argparse
import json
from packageurl import PackageURL
def transform_json(import_json, export_json):
image_sbom = json.load(open(import_json))
for comp in image_sbom['components']:
if 'purl' in comp:
purl = comp['purl']
# extract the purl items.
syft_purl = PackageURL.from_string(purl)
if "upstream" in purl:
# extract the upstream and then the name and version of the source package.
# example: "purl": "pkg:deb/debian/bsdutils@1:2.36.1-8+deb11u1?arch=amd64&upstream=util-linux%402.36.1-8+deb11u1&distro=debian-11"
upstream = syft_purl.qualifiers['upstream']
if "@" in upstream:
name, version = upstream.split("@")
else:
name, version = upstream, syft_purl.version
# build a source purl from the purl items.
src_purl = f"pkg:{syft_purl.type}/{syft_purl.namespace}/{name}@{version}?arch=source"
# replace the purl
comp['purl'] = src_purl
# example: "purl": "pkg:deb/debian/util-linux@2.36.1-8+deb11u1?arch=source"
# update component's name and version
comp['name'] = name
comp['version'] = version
# write the output json
with open(export_json, "w") as file:
    json.dump(image_sbom, file, ensure_ascii=False)  # unicode output

if name == "main":
parser = argparse.ArgumentParser()
parser.add_argument("--import_json", type=str,
help="cycloneDX json-file out of syft", default="syft-cyclone-dx_sbom.json")
parser.add_argument("--export_json", type=str,
help="cycloneDX json-file out of current transformation", default="")
args = parser.parse_args()
transform_json(args.import_json, args.export_json)

`

full script has been merged in Gridcontrol's runners, here:
https://code.siemens.com/gridcontrol-shared/support/container/gitlab-runner/-/blob/main/syft.transform_sbom-bin-purl-to-source-purl.py

full script has been merged in Gridcontrol's runners, here: https://code.siemens.com/gridcontrol-shared/support/container/gitlab-runner/-/blob/main/syft.transform_sbom-bin-purl-to-source-purl.py

Eric, it doesn't make much sense to provide Siemens-only URLs here. Perhaps attach the script if you consider it relevant for our bug report?

There seem to be a couple paths forward here, although this isn't a priority at the moment we've promoted this to our backlog and we welcome pull requests and would be happy to help.


DataGrid PropertyColumn LabelAttribute/DisplayAttribute support

Feature request type
Enhance component
Component name
PropertyColumn
Is your feature request related to a problem?
PropertyColumn Title does not respect LabelAttribute or DisplayAttribute. I implemented a simple extended class that showcases a possible fix.
Describe the solution you'd like
I am aware there is an ongoing discussion regarding LabelAttribute and DisplayAttribute so I made an example that supports both.
public class SmartPropertyColumn<T, TProperty> : PropertyColumn<T, TProperty>
{
    protected override void OnParametersSet()
    {
        if (Property.Body is MemberExpression memberExpression)
        {
            var propertyInfo = memberExpression.Expression?.Type.GetProperty(memberExpression.Member.Name);
            var label = propertyInfo?.GetCustomAttributes(typeof(LabelAttribute), true).Cast<LabelAttribute>().FirstOrDefault()?.Name;
            label ??= propertyInfo?.GetCustomAttributes(typeof(DisplayAttribute), true).Cast<DisplayAttribute>().FirstOrDefault()?.Name;
            label ??= propertyInfo?.Name;

            Title ??= label;
        }

        base.OnParametersSet();
    }
}

This example looks for LabelAttribute first, then DisplayAttribute and finally falls back to name of the property. I am still looking into how to apply a similar thing for showing enumeration values in cells.
P.S.: Personally I think LabelAttribute is not a way to go here as it makes our DTOs or even base models dependent on MudBlazor. Also in general it feels like reinventing the wheel. Related issue: https://github.com/MudBlazor/MudBlazor/pull/5225
Have you seen this feature anywhere else?
No response
Describe alternatives you've considered
No response
Pull Request

[X] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Kinda against it, since this fragment is not trim friendly.
 memberExpression.Expression?.Type.GetProperty(memberExpression.Member.Name)

Kinda against it, since this fragment is not trim friendly. memberExpression.Expression?.Type.GetProperty(memberExpression.Member.Name)

It could probably be done more easily in the PropertyColumn itself, I only did it this way because a bunch of properties was private.


[FixCode] Add a diagnosis/fixit to help users convert void pointers.

This patch warns the usage of Unsafe[Mutable]Pointer, and fix users' code by replacing it with Unsafe[Mutable]RawPointer.

Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

Builds the compiler incrementally.
Builds the standard library only for macOS. Simulator standard libraries and
device standard libraries are not built.
lldb is not built.
The test and validation-test targets are run only for macOS. The optimized
version of these tests are not run.

A smoke test on Linux does the following:

Builds the compiler incrementally.
Builds the standard library incrementally.
lldb is built incrementally.
The swift test and validation-test targets are run. The optimized version of these
tests are not run.
lldb is tested.

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

…Pointer to Unsafe[Mutable]RawPointer. rdar://27730408

@swift-ci smoke test OS X platform

@jrose-apple mind reviewing this?

@swift-ci smoke test OS X platform

@swift-ci smoke test OS X platform

I'm a little unhappy with hardcoding this in the compiler, and I'm not sure that UnsafeMutablePointer<Void> is never correct, but the implementation looks fine. @atrick, any comments?

Hard-coding this into the compiler is a last ditch effort to get decent diagnostics (I spent lots of time last week exploring the limits of availability annotations).
I'm not sure "deprecated" is the right language. UnsafePointer will always be a valid type in generic contexts, but people should be strongly discouraged from using it in a concrete bound generic. If they do, it will cause a number of confusing downstream errors, and the diagnostics for those errors will be better if they first rename to UnsafeRawPointer.

@jrose-apple UnsafePointer<Void> is a valid type (not really deprecated), but if a user is spelling that type, then they really should be using UnsafeRawPointer. I would be fine with a warning:
"Unsafe%0Pointer has been replaced by Unsafe%0RawPointer"
We do need a warning to help with code migration because the void* import type has changed and UnsafePointer conversion is restricted.

@atrick Should the warning be "Unsafe%0Pointer has been replaced by Unsafe%0RawPointer" or "Unsafe%0Pointer has been replaced by Unsafe%0RawPointer"? I thought the later is the case we are handling here specifically.

:-) I think you both fell prey to Markdown's HTML embedding. "Unsafe%0Pointer<Void>" (written Unsafe%0Pointer\<Void\>).

I think we both didn't quote the warning string properly. I think it should be
Unsafe%0Pointer<Void> has been replaced by Unsafe%0RawPointer
https://github.com/apple/swift/pull/4114 has been merged.

@jrose-apple @atrick Right, I realized what happened the moment I saw my message posting.

@swift-ci test

@swift-ci test

@swift-ci test

Slave went offline during the build.
@swift-ci  test


Correct noise cascade initialisation

Task related to this pySTEPS issue: 332
Now, the all noise cascade levels are initialized to zero.
It is probably better to initialize the noise with the appropriate noise field as provided by the EPS term.
The noise cascade has holds 2 time levels of noise. Both time levels should be initialized with the same noise field. If not the overall power of the noise cascade level will not converge to the correct power.

Created a new helper function in the pysteps.blending.steps.py file:
def init_noise_cascade(shape,n_ens_members,n_cascade_levels,generate_noise,
decompositor,pp,randgen_prec,fft_objs,bp_filter,domain,noise_method,noise_std_coeffs,ar_order):
noise_cascade = np.zeros(shape)
if noise_method:
for j in range(n_ens_members):
EPS = generate_noise(
pp,
randstate=randgen_prec[j],
fft_method=fft_objs[j],
domain=domain
)
EPS = decompositor(
EPS,
bp_filter,
fft_method=fft_objs[j],
input_domain=domain,
output_domain=domain,
compute_stats=True,
normalize=True,
compact_output=True
)
for i in range(n_cascade_levels):
EPS = EPS["cascade_levels"][i]
EPS_ *= noise_std_coeffs[i]
for n in range(ar_order):
noise_cascade[j][i][n] = EPS_
EPS = None
EPS_ = None
return(noise_cascade)

The noise was previously initialized before the initialization of the random generator. But since you now need them to initialize the noise.
The noise_cascade = _init_noise_cascade(...) should be called after the random generator initializations.
Also check with developments in issue #1

Fixed with commit 2eb125bc89f4cd13205bd88ff763d6a0097c938e

This is excellent!!


add mono repo single version support

This is currently supported either by defining the list of files or by using a glob, fork version currently is able to update multiple files at once with a single version.


Added test cases for StylesContext

Description
Please include a brief summary of the change and include the relevant issue(s).
Closes #232
What change does this PR introduce?
I have added a StylesContext.test.tsx file which contains test code for StylesContext.
Please select the relevant option(s).

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update (changes to docs/code comments)

What is the proposed approach?
Please give a short overview/explanation on the approach taken to resolve the issue(s).
Checklist:

[x] The commit message follows our adopted guidelines
[x] Testing has been done for the change(s) added (for bug fixes/features)
[ ] Relevant comments/docs have been added/updated (for bug fixes/features)

I have made the changes as you told me please tell me if you need me to make anymore changes

I have made the changes as you told me please tell me if you need me to make anymore changes

Hey @Suvrat1629, there're still outstanding comments unresolved 😅

@tjtanjin updates?


vuejs2.0 v-focus demo code does not work in the document

Vue.js version
2.0.0-rc.3
Reproduction Link
https://jsfiddle.net/matiascx/tdhzjavg/1/
Steps to reproduce
run
What is Expected?
input focused
What is actually happening?
No focus happen on input element

Why use rc3? The final version is out. 😃  If you update your version of Vue, it works.

great, i'd like to update it.
@chrisvfritz , by the way, i use npm install vue@next to fetch the package in my node_modules.
Should I now use that command again or something different since vuejs2.0 stable is available now?
thanks~!

Since 2.0 is out now, you can just use npm install vue.


Replication test for a shared database

We should validate that replication runs successfully when using a Cloudant shared database as a target by adding a new replication acceptance test.

Since accessing a shared database is essentially the same as accessing a database via an API Key, (see slack discussion), we don't need a specific test for this.


Call callAfterCreationHook before init.

Done. I also added a few more calls to the creation hook, e.g. after dynamically inserting / replacing a protocol


update to latest rust crate and expose SyncState encode decode

update to latest rust crate and expose encode decode functions in SyncState object

are these mac failures legit? i have the resources to attempt to address them if they are.

I'll review this properly tomorrow but one thing that immediately jumps out to me is that I think this could use a test or two.


Progress bar when loading multiple files

🚀 Feature

Progress bar when loading multiple files (for example from drag n drop)
Motivation
When loading multiple files it will be nice to have some feedback information, not frozen interface.

Pitch
As there Is a great threading mechanism with the generator worker then loading data could be moved to separated thread, layers added live and progress bar in the interface.

Alternatives

Additional context

I think we should be able to leverage the progress interface relatively easily to provide this feedback to the user - and I do agree we should move the opening of large files into a separate thread for usability.


clearOnGuiReadyObservable

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

Visualization tests for webgl1 have failed. If some tests failed because the snapshots do not match, the report can be found at
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13476/merge/testResults/webgl1/index.html
If tests were successful afterwards, this report might not be available anymore.

Visualization tests for webgl2 have failed. If some tests failed because the snapshots do not match, the report can be found at
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13476/merge/testResults/webgl2/index.html
If tests were successful afterwards, this report might not be available anymore.


member content self heal

Create member content entry upfront with channel id as the claim id. Once the upload finishes, call the API again to set the claim id.
A backend job will be setup to self heal where claim id = channel id

Closed by #2325


feat: add vburenin/ifacemaker

vburenin/ifacemaker: Generate interfaces from structure methods
$ aqua g -i vburenin/ifacemaker

How to confirm if this package works well
Reviewers aren't necessarily familiar with this package, so please describe how to confirm if this package works well. Please confirm if this package works well yourself as much as possible.
Command and output
$ ifacemaker --help
Usage:
  ifacemaker [OPTIONS]

Application Options:
  -f, --file=          Go source file to read, either filename or glob
  -s, --struct=        Generate an interface for this structure name
  -i, --iface=         Name of the generated interface
  -p, --pkg=           Package name for the generated interface
  -y, --iface-comment= Comment for the interface, default is '// <iface> ...'
  -d, --doc=           Copy docs from methods (default: true)
  -D, --type-doc       Copy type doc from struct
  -c, --comment=       Append comment to top, default is '// Code generated by ifacemaker; DO NOT EDIT.'
  -o, --output=        Output file name. If not provided, result will be printed to stdout.

Help Options:
  -h, --help           Show this help message

If files such as configuration file are needed, please share them.

Reference

GitHub Releases is old(latest is v1.2.0 )

Please review.

Thanks!

v1.1.0 and v1.0.0 have assets in GitHub Releases, so we should use them instead of building them from source with Go.

Thank you for your help.

Released. https://github.com/aquaproj/aqua-registry/releases/tag/v3.112.0


babel.server.js losing，and readme didn't update

Pardon?  Where is the babel.server.js you mention in the readme 0 0?
「What initally gets run is babel.server.js, which does little more than enable ES6 and ES7 awesomeness in the server-side node code. It then initiates server.js. 」
谢谢~

Sorry. It got renamed to bin/server.js.


fix test case that incorrectly sets the gas limit to 90k when it should be 21k

@hboon good for review again


How can I pass the slot options to the Vue constructor?

How can I pass the slot options to the Vue constructor?

You can't. it wouldn't make sense, because a main instance can't have slot contents, since slot content come from the parent.
Also: Your issue is a usage/support question, and the issue tracker is reserved exclusively for bug reports and feature requests (as outlined in our Contributing Guide).
We encourage you to ask it on the forum  , Stack Overflow or on gitter and are happy to help you out there.


[CHANGE] Eliminated use of  --short option from kubectl version commands

This PR supersedes/ closes #644 .


Allow local provision only with the --feeling-safe option

In order to make the tmt run command always safe to execute, even when entering an unkown repository, we should refuse to execute plan with provision --how local to prevent executing arbitrary code on user laptop.
As some users might already use this in their automation the decision from the hacking session is to start showing a warning since 1.35 and refuse to execute such plans in later tmt version. Let's give it roughly three months and add a hard stop in 1.38 or so?
In addition to the command line option, environment variable TMT_FEELING_SAFE should be implemented to allow users to enable this behaviour by default. This should probably include a warning, as such setting might be dangerous.
Would it make sense to also implement something like --feeling-paranoid which would override the environment variable above (or future user configuration), in order to make tmt run command safe regardless the environment or config?

In addition to the command line option, environment variable TMT_FEELING_SAFE should be implemented to allow users to enable this behaviour by default. This should probably include a warning, as such setting might be dangerous.

Not sure about the warning part, e.g. if it's run in a CI environment.

Would it make sense to also implement something like --feeling-paranoid which would override the environment variable above (or future user configuration), in order to make tmt run command safe regardless the environment or config?

Lol, that would be fun :+1:

Would it make sense to also implement something like --feeling-paranoid which would override the environment variable above (or future user configuration), in order to make tmt run command safe regardless the environment or config?

Lol, that would be fun 👍

Having a kill switch like this would be nice, exactly for CI systems: when set, no matter what the user sets in plans or environment, unsafe actions would remain disabled.

Yes, I agree in CI we would set the paranoid flag

In addition to the command line option, environment variable TMT_FEELING_SAFE should be implemented to allow users to enable this behaviour by default. This should probably include a warning, as such setting might be dangerous.

Not sure about the warning part, e.g. if it's run in a CI environment.

Ah, probably just a wrong wording on my side? I meant that the description of the newly added environment variable TMT_FEELING_SAFE should include a warning that setting this option in user environemnt means enabling the possible unsafe behaviour by default and can be dangerous. Does that make sense?


Armstrong number

Describe the project you want to add with tech stack
This C project is an Armstrong number detector.

Expected behavior
Given an input number, the program outputs if it is an armstrong number or not.

Screenshots (optional)

Additional context (optional )

@MohitGupta121 @TusharKesarwani Kindly assign this issue.


Output latest rclone version with rclone version --check

Currently, rclone reports its existing version when you run rclone version. I suggest that if the user specifies any level of verbosity, rclone could output the latest publicly available stable version in that output as well.
First, I'm not suggesting the output of rclone version or rclone --version change at all - I'm sure somebody's shell scripts somewhere depend on that. Instead, I'm suggesting that if the user passes one or more levels of verbosity, a simple HTTP GET could be performed with something like a 100ms timeout to rclone.org/versions/latest (or somewhere) that just returns a very simple string containing only the version number, nothing else. If you get that response back in < 100ms, display appropriate output.
For example:
$ rclone version -v
rclone v1.41
- os/arch: darwin/amd64
- go version: go1.10.1
Latest available via rclone.org: v1.4.9
Update your package manager or visit rclone.org to upgrade to the latest stable release!

I traveled to the future to get the above example, of course, after rclone v1.4.9 was released with this feature. 😃BTW they have hover cars in the future, true story!

Alternatively, if you're on the latest version:
$ rclone version -v
rclone v1.41
- os/arch: darwin/amd64
- go version: go1.10.1
Latest available via rclone.org: v1.4.1
Thanks for running the latest stable version of rclone!

This sample from an alternate reality where Hover Boards DO work on water!

And if rclone.org doesn't respond within < 100ms (or whatever's short and reasonable) for some reason? (User offline, internet exploded, clowns ate the server...), just ignore it and do what's already being done right now (omit last two lines).
Optionally this could be put behind a -vv flag instead of just one level of verbosity, if that suits others better.
Basically I think it would be nice to have a way to check what's actually running - not what my package manager tells me, which may be wrong or lagging behind - against what's actually released. This could be a very handy feature for such a fast-moving and promising project!

Thanks again for your feedback, @ncw. To respond with some thoughts:

I'm not sure I like the user interface, but I really like the idea behind it.

Thank you! I'm far from insistent on the interface or the output, so feel free to play with the concept all you want. To differentiate, I'm thinking of "interface" as "what I type to get the info", and "output" as "what info gets displayed".
One thing you could do is publish a JSON file with maybe a bit more data in it somewhere (where the aforementioned version file would go, or along-side it). Maybe it looks something like this:

Admittedly this is just a first crack without much (any) planning so probably not perfect

{
  "versions":
  {
    "latest":
    {
      "version":"1.4.1",
      "release_date":"2018-MM-DD 13:54:00 UTC",
      "source":"https://github.com/ncw/rclone/releases/tag/v1.41",
      "platforms":
      [
        {
          "macos":
          {
            "files":
            [
              {
                "arch": "x64",
                "download": "https://github.com/ncw/rclone/releases/download/v1.41/rclone-v1.41-osx-amd64.zip",
                "checksums":
                [
                  { "md5":  "..." },
                  { "sha1": "..." }
                ]
              },
              {
                "arch": "i386",
                "download": "https://github.com/ncw/rclone/releases/download/v1.41/rclone-v1.41-osx-386.zip",
                "checksums":
                [
                  { "md5":  "..." },
                  { "sha1": "..." }
                ]
              }
            ]
          }
        },
        {
          "windows":
          {
            "_comment":"repeat the structure, you get the idea"
          }
        }
      ]
    }
  },
  "previous":
  {
    "_comment":"same as latest, just with appropriate values for that version"
  }
}

(Obviously that should be minified without whitespace for production.)
By doing something like this, you've got a canonical, singular source of truth for the two most recent release versions, and by having this, not only can rclone fetch it and display whatever the user asks for (notes on that below), but automation tools can count on this file being available too, so they can script against it and have an always up-to-date singular source of information so they can automate builds, update installations, etc. however they want.
So now that we have more data in a way that's sort of "universally" useful...

Examples of my current thinking (unrefined)

The first thing that occurs to me is, perhaps: rclone version --check [-v|-vv]
Adding a --check flag could be what we need to differentiate it enough so that some one has to purposefully ask for this information before getting it unexpectedly. With -v, rclone could output a little more information, or with -vv it could give them a lot (as it pertains to the user's platform).
Example concept:
$ rclone version --check
   yours:   1.4.1
   latest:  1.4.3
   upgrade:
       https://github.com/ncw/rclone/releases/tag/v1.43

#
# This example is for a MacOS x64 install.
# For other platforms the output would be adjusted accordingly
#

$ rclone version --check -v
   yours:   1.4.1
   latest:  1.4.3 (released 2018-09-22)
   upgrade:
       https://github.com/ncw/rclone/releases/tag/v1.43
   download:
       https://github.com/ncw/rclone/releases/download/v1.43/rclone-v1.43-osx-amd64.zip

#
# An example for a Linux i386 run (for contrast) using -vv
# Here I'm showing just the match of platform in "latest",
# so as not to flood the user with way too much information about all the various
# platform/arch combinations. Note that if the platform you're on is suddenly
# discontinued, this would be a bit of an edge case where we should warn the
# user somehow, maybe with an `exit 99` or something and a big warning in caps
#

$ rclone version --check -vv
   yours:   1.4.1
       platform: linux
       arch: 386
   latest:  1.4.3 (previous: 1.4.2, released 227 days ago)
       platforms: linux
       archs: [ "i386", "x64" ]
   upgrade:
       https://github.com/ncw/rclone/releases/tag/v1.43
   download:
       https://github.com/ncw/rclone/releases/download/v1.43/rclone-v1.43-linux-386.zip
           checksums:
             md5:  value
             sha1: value
   release metadata (JSON):
       https://rclone.org/versions/latest.json

Again, I'm far from insistent on anything here. I'm just throwing what's in my head at you in hopes that it'll spark some creativity in you and/or your team to carry this forward as you see fit. Thanks again for your reply!

Thanks for your thoughts.  I like the --check parameter to rclone version that sounds good!
I can fetch the current version and the current beta release version very easily and I can get the dates of those releases without changing any of the build architecture.

I have made a first version of this roughly along the lines of your first suggestion...
https://beta.rclone.org/v1.42-006-gb77a330d-fix-2348-version-check/ (uploaded in 15-30 mins)
What do you think?
Here is the help
Version
Show the version number, the go version and the architecture.
Eg
$ rclone version
rclone v1.41
- os/arch: linux/amd64
- go version: go1.10

If you supply the --check flag, then it will do an online check to
compare your version with the latest release and the latest beta.
$ rclone version --check
yours:  <IP_ADDRESS>
latest: 1.42          (released 2018-06-16)
beta:   <IP_ADDRESS>      (released 2018-06-17)

Or
$ rclone version --check
yours:  1.41
latest: 1.42          (released 2018-06-16)
  upgrade: https://downloads.rclone.org/v1.42
beta:   <IP_ADDRESS>      (released 2018-06-17)
  upgrade: https://beta.rclone.org/v1.42-005-g56e1e820

Oops, try this instead
https://beta.rclone.org/v1.42-006-g5821e7c7-fix-2348-version-check/ (uploaded in 15-30 mins)

I've merged this to master now
https://beta.rclone.org/v1.42-132-g4eefd05d/ (uploaded in 15-30 mins)
This will be in the latest beta from now on and 1.43


More reorganization of build tree lifecycle

Context
Continuing on from #16821, some more restructuring of the build action pipeline, to detangle core classes from those types used to communicate with the daemon. Rename a bunch of types to use more consistent names for types that perform a similar role in each scope, and also group some types into packages by scope.
Contributor Checklist

[ ] Review Contribution Guidelines
[ ] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[ ] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[ ] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[ ] Ensure that tests pass sanity check: ./gradlew sanityCheck
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

@bot-gradle test and merge

Your PR is queued because #16831 is being built.

OK, I've already triggered a build for you.

@bot-gradle test and merge

Your PR is queued because #16846 is being built.

Pre-tested commit build failed.

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

OK, I've already triggered a build for you.

OK, I've already triggered a build for you.


cant use headless client in Liberation Lythium

Bug report
Basic Information
**Mission version: v0.96.7a
**Map used:Lythium
**Mods used:
@A3 Thermal Improvement;
@ace;
@ACE Compat - RHS Armed Forces of the Russian Federation;
@ACE Compat - RHS United States Armed Forces;
@ACE Compat - RHS- GREF;
@ACE Compat - RHS- SAF;
@Anrop Jbad Legacy Compatibility;
@ACEX;
@AUSSOF_LITE_mas;
@BackpackOnChest;
@BettIR (Legacy v0.2.1);
@Blastcore Edited (standalone version);
@BRAF - Brazilian Armed Forces A3;
@CBA_A3;
@Complementary Special Weapons (Backup);
@cTab;
@CUP ACE3 Compatibility Addon - Terrains;
@CUP ACE3 Compatibility Addon - Vehicles;
@CUP ACE3 Compatibility Addon - Weapons;
@CUP Terrains - Core;
@CUP Terrains - Maps;
@CUP Terrains - Maps 2.0;
@CUP Units;
@CUP Vehicles;
@CUP Weapons;
@DUI - Squad Radar;
@Enhanced GPS;
@Enhanced Map Ace Version;
@Enhanced Movement (ACEX Fix);
@Enhanced Soundscape;
@Fawks' Enhanced NVGs;
@Females-TCGM_Girls;
@Gruppe Adler Trenches;
@Immersion Cigs;
@Jbad;
@JSRS SOUNDMOD;
@JSRS SOUNDMOD - CUP VEHICLES MOD SOUND SUPPORT;
@JSRS SOUNDMOD - CUP WEAPONS MOD SOUND SUPPORT;
@JSRS SOUNDMOD - Reloading Sounds;
@JSRS SOUNDMOD - RHS  AFRF Mod Pack Sound Support;
@JSRS SOUNDMOD - RHS GREF Mod Pack Sound Support;
@JSRS SOUNDMOD - RHS SAF Mod Pack Support;
@JSRS SOUNDMOD - RHS USAF Mod Pack Sound Support;
@LYTHIUM;
@Multi-play Uniforms;
@Multi-play Uniforms for TCGM_Girls;
@No More Aircraft Bouncing;
@No Weapon Sway;
@Project OPFOR;
@RHSAFRF;
@RHSGREF;
@RHSSAF;
@RHSUSAF;
@TAC VESTS;
@Task Force Arrowhead Radio (BETA!!!);
@TAW View Distance - Addon;
@TFAR Animations;
@Tier One Weapons;
@Tier One Weapons-BettIR Compatibility Config;
@Turret Enhanced;
@Zeus Enhanced;
@Zeus Enhanced - ACE3 Compatibility;
**Dedicated or local game: Dedicated
**Source of the mission file (URL): https://steamcommunity.com/sharedfiles/filedetails/?id=1226882826
Individual Things
**Did you edit anything within the mission files?
no
Expected Behaviour
the bug occur when i try to use a headless client in this missions
this is the bug
You cannot play/edit this mission; it is dependent on downloadable content that has been deleted.afghan_houses_old, Wall_L, Wall_k, afghan_houses, afghan_houses_c, mil, Misc_Ramps, Jbad_Misc_Construction, Jbad_misc_market, Ind_Workshop01, Ind_Conveyer, Ind_Coltan_Mine, Cargo_Cont, ffaa_casas_af, gbr_Bush, gbr_Veg, Jbad_Ind_SawMill, Ind_Shed, Wall, Jbad_Rock1

i already teste in Liberation atlis and chernarus in the same version


Updated TabControl styles for VS

Implement support for StandardTabItem & TabStripPlacement for tabs in VS theme
Right now tab 4 TabStripPlacement are supported with rotation like in VS

Closes #2346
Closes #2090
Closes #1890

@armano2 Thx


Select current location

This solves #13 and #26.
Basically, I added the functionality to also select the current location, not just displaying it.
Observation: I've created the updateLocation function because that snippet has to be executed twice: when you drop a pin and also when you want to get your current location.

Thanks for this PR.
It is working fine now . But, why this didn't merged yet????

Hello, I've restrained from merging this because this PR selects current location when user presses show current location button. I wasn't sure how it was from UX perspective, since some users may want to keep selected location, and press show me button just to see where they are, etc. On the other hand, it makes sense too, so I'm open to discussions of selecting current location when that button pressed.

Made long press gesture work on current location blue dot too.


Implement export command

Resolves #179

I'm not sure if the command is supposed to download a csv file to my computer. As of now it doesn't do that and only says "Address book data has been exported!".

Could you check your data folder that contains the addressbook.json save folder? It should be there.

I'm not sure if the command is supposed to download a csv file to my computer. As of now it doesn't do that and only says "Address book data has been exported!".

Could you check your data folder that contains the addressbook.json save? It should be there.

Yes there's a property.csv there. So it will be downloaded onto user's computer when it becomes a JAR file?

I'm not sure if the command is supposed to download a csv file to my computer. As of now it doesn't do that and only says "Address book data has been exported!".

Could you check your data folder that contains the addressbook.json save? It should be there.

Yes there's a property.csv there. So it will be downloaded onto user's computer when it becomes a JAR file?

Yep, it should act this way as well. But do give it a test just in case, as it works for me.

Perhaps we could also tell the users where to find their exported CSV file in the help menu + user-guide?

Good idea. I'll write that in.

I'm not sure if the command is supposed to download a csv file to my computer. As of now it doesn't do that and only says "Address book data has been exported!".

Could you check your data folder that contains the addressbook.json save? It should be there.

Yes there's a property.csv there. So it will be downloaded onto user's computer when it becomes a JAR file?

Yep, it should act this way as well; it works for me. But do give it a test by launching it via a JAR file in a seperate folder just in case.

I exported to jar file and tested in a separate folder. No file is downloaded when I use the export command though.

I'm not sure if the command is supposed to download a csv file to my computer. As of now it doesn't do that and only says "Address book data has been exported!".

Could you check your data folder that contains the addressbook.json save? It should be there.

Yes there's a property.csv there. So it will be downloaded onto user's computer when it becomes a JAR file?

Yep, it should act this way as well; it works for me. But do give it a test by launching it via a JAR file in a seperate folder just in case.

I exported to jar file and tested in a separate folder. No file is downloaded when I use the export command though.

Could you screenshot the contents of your "Data" folder? Mine looks like this when I do the command using the JAR file

Perhaps we could also tell the users where to find their exported CSV file in the help menu + user-guide?

Alright, I've put that in already! Additionally, could you help me check if you are able to see the exported .csv file under the "data" folder when you run the JAR file of PROperty?

I'm not sure if the command is supposed to download a csv file to my computer. As of now it doesn't do that and only says "Address book data has been exported!".

Could you check your data folder that contains the addressbook.json save? It should be there.

Yes there's a property.csv there. So it will be downloaded onto user's computer when it becomes a JAR file?

Yep, it should act this way as well; it works for me. But do give it a test by launching it via a JAR file in a seperate folder just in case.

I exported to jar file and tested in a separate folder. No file is downloaded when I use the export command though.

Could you screenshot the contents of your "Data" folder? Mine looks like this when I do the command using the JAR file

I'm not sure if the command is supposed to download a csv file to my computer. As of now it doesn't do that and only says "Address book data has been exported!".

Could you check your data folder that contains the addressbook.json save? It should be there.

Yes there's a property.csv there. So it will be downloaded onto user's computer when it becomes a JAR file?

Yep, it should act this way as well; it works for me. But do give it a test by launching it via a JAR file in a seperate folder just in case.

I exported to jar file and tested in a separate folder. No file is downloaded when I use the export command though.

Could you screenshot the contents of your "Data" folder? Mine looks like this when I do the command using the JAR file

Here you go. The csv file does appear when I use "export".

That's great! Could you also test by running rerunning the shadowjar command and then running the JAR file in a seperate folder just in case.


issue on horizontal ScrollAreaThumb component

The horizontal ScrollAreaThumb component's width is becoming the same as ScrollAreaScrollbar.
https://github.com/shadcn/ui/assets/86896657/198a9781-0ab9-4121-a667-15458d62598d

There isn't a pic of your code so it might be harder to determine your problem, but the ScrollArea and its content may have the same size or dimensions, this can make the scroll thumb and scroll bar to appear the same or overlap , this just means that the height of your content does not exceed the fixed scrollArea height

There isn't a pic of your code so it might be harder to determine your problem, but the ScrollArea and its content may have the same size or dimensions, this can make the scroll thumb and scroll bar to appear the same or overlap , this just means that the height of your content does not exceed the fixed scrollArea height. This is just a suggestion from me, i did not see your actual code so the problem might be something else

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


Set holiday via Luxtronik?

Hi, is it possible to set periods of absence (holiday) from HA? Are these interfaces available?

I think it is param 161-667. 506 values...
I don't see the benefit to implement 506 values. And on gui site we have to implement a calendar control. I don't think this is possible with the ha config flow.
You can create very easy one or more ha automation and start/stop heating, domestic water or tdi.

In the climate thermostat you can choose preset=away. This is the corresponding preset of luxtronik holiday mode.
You can create a HA automation with timer and set this mode.
In heatpump24.com you can set timers and the luxtronik interface allows this over the socket connection. But I think this timers are only for day/night mode and not for holiday.

Could you help on this one? I tried to set the heatpump to holiday mode via the UI, but didn't find the right option.
If I understand the code correctly, the parameters are ID_Ba_Hz_akt and ID_Ba_Bw_akt. However, in the code they are coded as switches for Automaticand Off. Is there an easy way to make them a drop-down?
https://github.com/BenPru/luxtronik/blob/6d3976c4cedee5ca2c5b0799aaa05af302167213/custom_components/luxtronik/switch.py#L95-L108)

@tmp-hallenser The luxtronik holiday mode can be set in climate.luxtronik*_heating preset_mode: away

@Crashman1983 An idea:
Sync the Luxtronik schedules as HA Automations.

ID_Einst_SuAll --> First Automation
ID_Einst_SuHkr --> Second Automation
ID_Einst_SuMk1 / 2 / 3 --> Third-n. Automation
ID_Einst_SUBW
ID_Einst_SuLuf


No license found

This project does not seem to have a license declared in an obvious way, or at all. A license should be added (as this project seems to be intended as open source) so that users can run, modify, study, distribute, and use the code.
https://choosealicense.com/no-permission/

Fixed in https://github.com/swaywm/swaywm.org/commit/b9f5611f836f91e8e0abb0eff00671b964c017f5.


Renaming the kubernetes namespace to quantum-serverless

What is the expected enhancement?
Currently, our helm chart installs to the ray namespace. However, our project is called quantum-serverless, so this could be confusing to users / cluster admins.
Perhaps we should rename the namespace to quantum-serverless?
If we do, we should also remove the quantum-serverless- prefix from most components, as it would be redundant.
(quantum-serverless seems like the obvious name to use here, but also open to another, less-obvious one)
/cc @IceKhan13 @pacomf @Tansito @akihikokuroda

I don't know if left that referencie un the documentation but yeah, from #447 for example I'm assuming quantum-serverless as the namespace