javaType : generate classes in subpackage of the target package

Suppose I generate my classes in target package com.example.
If I specify a javaType property of Foo, it will be generated as com.example.Foo, as expected.
However if I specify a javaType property of bar.Foo (with a dot), it will be generated as bar.Foo (i.e. in package bar).
To me it would make more sense to generate it in package com.example.bar.Foo, i.e. a subpackage of the target package. As it is now, if I want to generate classes in subpackages of the target package, I have to repeat the fully qualified package name in every javaType property. And of course if I want to change it I will have to change in all the places it is referenced...
If we want to preserve this behavior for compatibility and still allow generating classes in subpackages, I suggest we introduce the convention that if the javaType begins with a dot, it's considered relative to the target package.
For example:

javaType=bar.Foo -> generates class bar.Foo (same as current behavior)
javaType=.bar.Foo -> generates class com.example.bar.Foo

What do you think?

I realize this has already been suggested here: https://github.com/joelittlejohn/jsonschema2pojo/issues/195#issuecomment-69217947
but I can't figure out the status of this request. I'm using the Maven plugin v1.0.2 and it totally ignores if my javaType begins with a dot (it just strips it).

https://github.com/joelittlejohn/jsonschema2pojo/issues/195#issuecomment-69217947 has been marked as closed by https://github.com/joelittlejohn/jsonschema2pojo/pull/1054, which was merged into master on Dec 12, 2019, while release 1.0.2 is from Jan 27, 2020.
Yet I get the same behavior whether I specify javaType=bar.Foo or javaType=.bar.Foo
What am I missing?

(sorry for the monologue...)
So apparently the commit only handles the case where the javaType is not a qualified name (i.e. does not contain a dot) but it does not handle the case where it begins with a dot.
So my issue still stands :)

What prevents you from declaring your javaType to be com.example.bar.Foo?

What prevents you from declaring your javaType to be com.example.bar.Foo?

Nothing, and that would work, but I shouldn't have to use  com.example to be in the schema because it's a generation-time parameter. I want to be able to put the generated classes in subpackages of the target package, without knowing what it will be.

Thanks @ogerardin. I have reopened #1054.


docs:Improve CONTRIBUTING.md

Remove a typo from CONTRIBUTING.md
Signed-off-by: manaswinidas<EMAIL_ADDRESS>

Nice catch, @manaswinidas! Merging this change now.


Flash message on new challenge success/failure

Right now it redirects and that's kind of crappy. Let's have a flash message

There are other places we could be doing flash messages too. Login failure, for example

#92 Takes care of this


Tensorflow example image has a lot of warnings and python 2.7.

I was using the tensorflow example image to demonstrate JobSet functionality and I saw a lot of warnings related to deprecated features.  Not sure if this image will eventually stop working but wanted to bring it to your attention.
[ec2-user@ip-172-31-93-184 jobset-kevin]$ kubectl logs tensorflow-tensorflow-0-0-5l6bb
WARNING:tensorflow:From /var/tf_mnist/mnist_with_summaries.py:39: read_data_sets (from tensorflow.contrib.learn.python.learn.datasets.mnist) is deprecated and will be removed in a future version.
Instructions for updating:
Please use alternatives such as official/mnist/dataset.py from tensorflow/models.
WARNING:tensorflow:From /usr/local/lib/python2.7/dist-packages/tensorflow/contrib/learn/python/learn/datasets/mnist.py:260: maybe_download (from tensorflow.contrib.learn.python.learn.datasets.base) is deprecated and will be removed in a future version.
Instructions for updating:
Please write your own downloading logic.
WARNING:tensorflow:From /usr/local/lib/python2.7/dist-packages/tensorflow/contrib/learn/python/learn/datasets/base.py:252: wrapped_fn (from tensorflow.contrib.learn.python.learn.datasets.base) is deprecated and will be removed in a future version.
Instructions for updating:
Please use urllib or similar directly.
WARNING:tensorflow:From /usr/local/lib/python2.7/dist-packages/tensorflow/contrib/learn/python/learn/datasets/mnist.py:262: extract_images (from tensorflow.contrib.learn.python.learn.datasets.mnist) is deprecated and will be removed in a future version.
Instructions for updating:
Please use tf.data to implement this functionality.
WARNING:tensorflow:From /usr/local/lib/python2.7/dist-packages/tensorflow/contrib/learn/python/learn/datasets/mnist.py:267: extract_labels (from tensorflow.contrib.learn.python.learn.datasets.mnist) is deprecated and will be removed in a future version.
Instructions for updating:
Please use tf.data to implement this functionality.
WARNING:tensorflow:From /usr/local/lib/python2.7/dist-packages/tensorflow/contrib/learn/python/learn/datasets/mnist.py:290: __init__ (from tensorflow.contrib.learn.python.learn.datasets.mnist) is deprecated and will be removed in a future version.
Instructions for updating:
Please use alternatives such as official/mnist/dataset.py from tensorflow/models.
2023-08-10 13:42:32.288488: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 AVX512F FMA

Ref: https://github.com/kubernetes-sigs/jobset/pull/253

I think we should use docker.io/kubeflowkatib/tf-mnist-with-summaries:latest in the TFJob example since the image is so old.

I can open up a PR to fix that.

@johnugeorge What do you think removing kubeflow/tf-mnist-with-summaries:latest then using ocker.io/kubeflowkatib/tf-mnist-with-summaries:latest?

We are building kubeflow/tf-mnist-with-summaries:latest image built each time.
https://github.com/kubeflow/training-operator/blob/855e0960668b34992ba4e1fd5914a08a3362cfb1/.github/workflows/publish-example-images.yaml#L31-L32
So if update Dockerfile here to use latest tensor flow, won't it be solved automatically?
https://github.com/kubeflow/training-operator/blob/855e0960668b34992ba4e1fd5914a08a3362cfb1/examples/tensorflow/mnist_with_summaries/Dockerfile#L15

We are building kubeflow/tf-mnist-with-summaries:latest image built each time.
https://github.com/kubeflow/training-operator/blob/855e0960668b34992ba4e1fd5914a08a3362cfb1/.github/workflows/publish-example-images.yaml#L31-L32
So if update Dockerfile here to use latest tensor flow, won't it be solved automatically?
https://github.com/kubeflow/training-operator/blob/855e0960668b34992ba4e1fd5914a08a3362cfb1/examples/tensorflow/mnist_with_summaries/Dockerfile#L15

I'm not sure if the image works well by just bumping the base image version because we must resolve issues for Python major version bumping (Python 2.7 -> Python 3.x) and Tensorflow major version bumping (TF 1.11 -> TF 2.x).

Newer tensorflow images are not using python 2.x. I  just checked tensorflow/tensorflow:2.13.0 and it uses Python 3.8.10

Newer tensorflow images are not using python 2.x. I just checked tensorflow/tensorflow:2.13.0 and it uses Python 3.8.10

I see. I'm ok with bumping TF version if it works without error.

/good-first-issue

/lifecycle frozen

Hi @kannon92, I think we can close this issue as I already updated the images and adjusted the code to use TF v2  (https://github.com/kubeflow/training-operator/issues/2015)
If this doesn't answer your request please let me know, otherwise please close this issue.
Thanks for bringing this to our attention!
@tenzen-y FYI
/assign


Sample graphql lookup of related records

This is an example for the GraphQL Wire Adapters and Functions Pilot
This example focuses on a new accountRelatedContacts sample component.
It @wires graphql to run a primable query to fetch the top 5 related Contacts.
For completeness, a simple viewContactRecord LWC is proveded, so that tapping a Contact in the list can navigate to view the Contact.

Wondering if we should add eslint-disable lines for the issues that show up in vscode?  For example:
/* eslint-disable @salesforce/lwc-graph-analyzer/no-unresolved-parent-class-reference */

I see a mocks class, but no unit tests. Can you please add unit tests for the JS code?

@dbreese tests that reference components using lightning/uiGraphQLApi are not able to find that module. I think we have to go without it for now, and I think we can address the bugs with the linting separately.


Input_file_handling_robustness

This PR makes the input file handling routines more flexible and robust.

Lets you not specify any grid entry in the input file. You can now run a scalar case.
Let's you not specify any algorithm entry in the input file. This makes a Algorithm.empty which does nothing at all (neater than handling no algorithms as some special case).
As a consequence of allowing scalar cases, adds a minor modification to sanitize_variable which works around scalar-valued coordinates (see https://github.com/pydata/xarray/issues/1709). This has the pleasing side-effect of getting the correct dimension name in the regression JSON.
Adds cfspopcon as an entry point, equivalent to popcon. Now you can either poetry run popcon or poetry run cfspopcon — these do the same thing.
Lets you pass dictionaries to input_file_handling instead of just filepaths, in case you want to programmatically set input values.
Runs ruff on tests to tidy this up

Algorithm.empty() is useful if you want to set up a dataset based on an input file. Often useful in a development step, where you want to load up a case and then develop an algorithm in a jupyter notebook.


Turn skipLibCheck on by default

Turn skipLibCheck on by default

That is actually a bad idea. I really want to know if there is some issues in dependencies by default as it is right now.

https://twitter.com/SeaRyanC/status/1515465823585902593
:(

To expedite the triage process, we need everyone to follow the issue template and instructions.
When you clicked "Create New Issue", the issue form was pre-populated with a template and some instructions. We need you to read those instructions completely, follow them, and then fill in all the fields in that template.
We are not able to assist with issues that don't follow the template instructions as they represent a significantly larger amount of work compared to issues which are correctly specified. Thank you for understanding.


make scmInfo a required field for open source projects

steps
publish an open source project without scmInfo
problem
its hard to find the source
expectation
every open source project must have a scmInfo tag
notes
scaladex has to keep track of the lost & found: https://github.com/scalacenter/scaladex-contrib/blob/master/claims.json

I don't know if a build tool should enforce these kinds of rules. How would I know if something is OSS and if something is even published publicly. If it's mostly for sbt plugins, would it make sense to enforce this at sbt-bintray instead?

I think the build tool should guide the user. It's true that in this case it's mostly Bintray not enforcing VCS tags. Sonatype does the validation manually.

openSource := true
Should be set by default since the publish task publish source by default.

publishTo could point to a corporate repository that has nothing to do with open source, which is a licensing matter.

good point :)

Given sbt is OSS (BSD 3 clause) I'm happy to make it opinionated that the software it builds is OSS by default. And there would be an obvious way to opt-out of that (:= None or := false).

Why solve it at this layer if Sonatype already checks for this, and we can tackle it at sbt-bintray?

I'm thinking perhaps it would be good to fail early, at the core. Instead of the status quo where we fail after having delivered incomplete metadata.

Not sure what you mean. If we implemented it, we'd put check on deliver task or something like that, right? How would that be any different in a plugin?

As one of my professors used to say, correctness is strictly a function of the specification. One might want to build an scmInfo-less in order to test whether a certain repository system handles it correctly, for instance, or for all sorts of debugging or development reasons.
If I want to build a project without scmInfo, the build tool must be there to build what I ask for, not to impose rules on me. You may wish to issue a warning, at best, but I disagree the field must be made mandatory. You can always push enforcement to other layers, if you so wish.

I think this should not be required, and I would propose to close it. We already have too many open issues in sbt :smile:.

closing.

Why are we closing this issue? It's a real problem and this is backing it https://github.com/scalacenter/scaladex-contrib/blob/master/claims.json

I'm sorry @MasseGuillaume, I didn't intend to stand in your way. The reason I proposed to close is because the title of the issue suggests to make scmInfo mandatory for all sbt builds which is clearly not possible for the aforementioned reasons.
I don't doubt there's a real motivation behind this issue. Perhaps we can open a new issue proposing an alternative solution to it?


refactor: refactor and clean omg_eth to be thin, thinly tested, no-deps

refactor: aiming for decoded-only OMG.ETH's api (WIP - happy path pass)
refactor: aiming for decoded-only OMG.ETH's api (WIP - perf test pass)
refactor: aiming for decoded-only OMG.ETH's api (WIP - watcher fixture)
refactor: aiming for decoded-only OMG.ETH's api (WIP - watcher pass)
style: format (WIP, to be squashed)
refactor: shorter path to encoding integer arguments to jsonrpc (WIP)
refactor: decoded binaries for Eth.WaitFor.eth_receipt (WIP)
refactor: remove unused and superflouous call_contract_value (WIP)
fix: quick fix eth_test for mix test --only wrappers to work
refactor: (experimental) remove sorting of ethereum logs
refactor: remove contract_transact_sync! from production code
refactor: get rid of bare keccakf1600 calls
fix: give more specific typespec to from_hex for dialyzer (WIP)
test: remove redundant and dependency inducing eth_tests
left only the test of the "pipeline" that the thin wrapper offers
refactor: large tidy around OMG.Eth.Encoding (WIP)
fix: avoid passing default tx opts to submit_block transactions
fix: update demo to new APIs (WIP)
refactor: move and rename token_contract_config to fee_file fixture WIP

re encoding: let's defer to OMG-233


Revert "chore: upgrade libp2p to 0.52.1 (#3115)"

This reverts commit 4469ff43b02011244220c8a82dd4beafd3a0a437.
Summary of changes

Changes introduced in this pull request:

it seems the upgrade produced same issues as described in https://github.com/ChainSafe/forest/issues/2762

Reference issue to close (if applicable)

Closes
Other information and links

Change checklist

[ ] I have performed a self-review of my own code,
[ ] I have made corresponding changes to the documentation,
[ ] I have added tests that prove my fix is effective or that my feature works (if possible),
[ ] I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

Does this need a regression test?

Does this need a regression test?

How would you achieve this? For context, it's not that the chain exchange failure happens all the time with the new version. It happens sometimes, even after 24 hours. Unfortunately, we do not know currently what exact conditions are triggering this (apart from the fact that it doesn't seem to happen with the older libp2p release)

If we revert the PR, how will we debug the problem?

If we revert the PR, how will we debug the problem?

We can debug it on a branch. It's essential not to restart our infrastructure services every time this issue appears.


undefined reference to `typeinfo for Halide::Internal::GeneratorOutputBase'

when I use setup.py, I  get the error.

Is this using the provided Docker configuration ? if not, this might come from a Halide version mismatch. https://github.com/adobe/sbmc/blob/2ca0b3e79c0d90236da61dfc95de7acfab0299ee/dockerfiles/cuda-sbmc.dockerfile#L93

Is this using the provided Docker configuration ? if not, this might come from a Halide version mismatch.
https://github.com/adobe/sbmc/blob/2ca0b3e79c0d90236da61dfc95de7acfab0299ee/dockerfiles/cuda-sbmc.dockerfile#L93

Thank you very much!

Is this using the provided Docker configuration ? if not, this might come from a Halide version mismatch.
https://github.com/adobe/sbmc/blob/2ca0b3e79c0d90236da61dfc95de7acfab0299ee/dockerfiles/cuda-sbmc.dockerfile#L93

Thank you very much!


Pass shapefile to DB to CSV interface

By this new parameter, we can  dump the polygons base on shapefile.
E.g., if we only paln to dump subset of polygon-base result in the waterbodies DB as CSV files, we can use this approach.

Codecov Report

Merging #46 (ce81ff6) into main (77933f1) will decrease coverage by 0.21%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##             main      #46      +/-   ##
==========================================
- Coverage   86.45%   86.24%   -0.21%
==========================================
  Files          19       19
  Lines        1580     1585       +5
==========================================
+ Hits         1366     1367       +1
- Misses        214      218       +4

Files
Coverage Δ

dea_conflux/__main__.py
76.70% <33.33%> (-0.58%)
:arrow_down:

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


Use the request validator from common gem

Similar changes as https://github.com/ManageIQ/catalog-api/pull/402:

All 422 error codes are changed into 400;
Raise error if any parameters is missing;

Depends on https://github.com/ManageIQ/manageiq-api-common/pull/133


Nested bullets only work in the preview

Source:
This is a test

* Bullet 1
  * Nested

Result: https://www.notehub.org/2015/9/7/this-is-a-test

Thanks for the bug report! I'm currently middle in migration of NoteHub to Node.js, so this will be fixed automatically, because only marked.js will be used in the future both on the client & server side.

Sounds good, thanks for letting me know.

Works as expected now.


MSID: 88008 Version: 2 DOI: 2<IP_ADDRESS>7765

[PLACE MANUSCRIPT AND EDITOR DETAILS HERE WHEN AVAILABLE] See step 3
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=88008)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/88008/v2)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews and QC
Who can help: Production team

[ ] QC passed or QC not needed

Who can help: Editorial team

[x] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>7765)
[ ] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/88008/v2/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2<IP_ADDRESS>4241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>4241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/88008)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/88008

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/88008

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/88008/v2/88008-v2.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/88008)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

note: this is v2 of the preprint, not most recent version


Feat/inline prop

adds suport for inline prop
closes #5

i forgot to add the new props on the readme section

i forgot to add the new props on the readme section

@demetrius-mp Good catch, do you mind adding that here?

ok, ill add them

sorry, i definetly messed up something when doing the branches thing. im new to open source 😅
i think that if you close #29 and merge only this PR, it will be ok, since this PR has the commits from #29.
this PR has

inline prop with its tests, and also declared on the readme
gap prop with its tests, the adjustments suggested here, and also declared on the readme

i think that if you close https://github.com/himynameisdave/svelte-flex/pull/29 and merge only this PR,

I'd rather have each of these props included as separate commits (makes it easier to revert if there are any issues, plus I it's a nicer commit history to keep things separated). Please address the final comments in #29 and then we can take a look at this PR :)

ok!


ERROR while installing in log

17-12-10 16:02:25 INFO (SyncWorker_1) [hassio.dock.addon] Start build fe029bfe/armhf-addon-rpi-homegear:0.1
17-12-10 16:02:36 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 416, in start
resp = yield from self._request_handler(request)
File "/usr/lib/python3.6/site-packages/aiohttp/web.py", line 323, in _handle
resp = yield from handler(request)
File "/usr/lib/python3.6/site-packages/hassio/api/util.py", line 31, in wrap_api
answer = await method(api, *args, **kwargs)
File "/usr/lib/python3.6/site-packages/hassio/addons/addon.py", line 474, in install
if not await self.docker.install(self.last_version):
File "/usr/lib/python3.6/site-packages/hassio/dock/util.py", line 18, in wrap_api
return await method(api, *args, **kwargs)
File "/usr/lib/python3.6/concurrent/futures/thread.py", line 55, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/lib/python3.6/site-packages/hassio/dock/addon.py", line 219, in _install
return self._build(tag)
File "/usr/lib/python3.6/site-packages/hassio/dock/addon.py", line 232, in _build
image = self.docker.images.build(**build_env.get_docker_args(tag))
File "/usr/lib/python3.6/site-packages/docker/models/images.py", line 179, in build
raise BuildError(chunk['error'])
docker.errors.BuildError: The command '/bin/sh -c apt-get update && apt-get -y install homegear homegear-nodes-core homegear-nodes-extra homegear-homematicbidcos homegear-homematicwired homegear-insteon homegear-max homegear-philipshue homegear-sonos homegear-kodi homegear-ipcam homegear-beckhoff homegear-knx homegear-enocean homegear-intertechno homegear-influxdb vim less htop' returned a non-zero code: 100
core-ssh:~# returned a non-zero code: 100

I am struggeling with the error above. Has anyone an Idea how to solve it?

Me too...

Let's continue this on https://community.home-assistant.io/t/homegear-add-on-for-hassio/35169/5


Adds a link to callingallpapers.com

This commit adds a link to callingallpapers.com as alternative to the link to the CfP-Page on joind.in

These are technically independent projects, and plenty of other cfp tools also use joind.in, so I'd prefer not to add the link.

A pity but I can absolutely understand that :wink:


Add Font::codepoint_ids

Provide an abstraction for mapping GlyphId -> char.
pub trait Font {
    fn codepoint_ids(&self) -> crate::CodepointIdIter<'_>;
}

let font = FontRef::try_from_slice(include_bytes!("../../dev/fonts/Exo2-Light.otf"))?;

// Iterate over pairs, each id will appear at most once.
let mut codepoint_ids = font.codepoint_ids();
assert_eq!(codepoint_ids.next(), Some((GlyphId(408), '\r')));
assert_eq!(codepoint_ids.next(), Some((GlyphId(1), ' ')));
assert_eq!(codepoint_ids.next(), Some((GlyphId(75), '!')));

// Build a lookup map for all ids
let map: HashMap<_, _> = font.codepoint_ids().collect();
assert_eq!(map.get(&GlyphId(75)), Some(&'!'));

Resolves #18

Looks good to me.  Thanks for implementing this so quickly!


JFXComboBox prompt overflow

Im really sorry to be doing this again but the style is not exactly what I was expecting, could it be formatted like the standard ComboBox where it uses an ellipsis if overflowing?

Thanks again

Currently, prompt text is using Text node which doesn't support ellipsis. feel free to add your own contribution to JFoenix.
Regards,


fix: Ensure Teradata OutofBound dates don't affect other date columns

Closes #1218
Previously, if one date column was OutOfBounds (large timestamps '9999-12-31' or dates starting with 0 '0001-01-01'), all date fields would be converted to an 'object' data type in the pandas schema. This causes issues when comparing to the standard 'datetime64[ns]' dates in BQ or other DBs.
This PR fixes it so that only OutOfBounds date columns get converted to 'object' data types.

/gcbrun

/gcbrun


bugfix, file download doesn't work while running on FPM

file download doesn't work while running on FPM, cause by output buffer have been closed by function fastcgi_finish_request();

Thanks for this! Unfortunately, the issue was a bit more complex. I'm closing this in favor of #335 being merged.


add support for automated deployment on Maven Central

#91 is a first step, but it's not working yet.


Allow setting the facing direction when following

When following another character, there is currently no way to specify which facing direction of the character to follow. For example one might want to follow always the facing side of another character. Or in another scenario always follow it behind its back (or running next to it).
The proposal is to add an option to follow that sets the facingDirection to follow (face, back, left, right, any). Default will be any .

https://annoraaq.github.io/grid-engine/examples/following-facing-direction/


Keep receiving TypeNotFound when running in console

Hey there! I've been running my script using VSCode environment without any issue.
But when I try to run the same scripts using PS console (Task Scheduler) I receive the following issue:
Unable to find type [Microsoft.PowerShell.Commands.WebRequestSession].
At C:\Users\sebas\Documents\WindowsPowerShell\Modules\PSGraphQL\1.0.10\Functions\Invoke-GraphQLQuery.ps1:144 char:27
+ ... sition = 3)][Microsoft.PowerShell.Commands.WebRequestSession]$WebSess ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (Microsoft.Power...bRequestSession:TypeName) [], RuntimeException
    + FullyQualifiedErrorId : TypeNotFound

Any ideas?
Thanks in advance!

Hello, please try the following in order:

Before importing the PSGraphQL module, run "Import-Module Microsoft.PowerShell.Utility -Force" then import PSGraphQL and attempt to execute Invoke-GraphQLQuery.
From the same computer (as a scheduled task) run Invoke-RestMethod to a known endpoint and let me know the results. This may determine if something is broken regarding the current installation of PowerShell.
From a different computer run Invoke-GraphQLQuery (as a scheduled task). This will determine if the issue is isolated to the above machine.
Please post the output of $PSVersionTable here.

Hey there!
Thanks for your response.
It fails when running Invoke-RestMethod as a scheduled task) (Step 2)
Invoke-RestMethod : GET query missing.
At line:1 char:1
+ Invoke-RestMethod
+ ~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebExc
   eption
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

Sorry I meant Invoke-RestMethod with a URI but I think I know the issue. Can you create a new scheduled task that runs the following in sequence:
Import-Module Microsoft.PowerShell.Utility -Function Invoke-RestMethod -Force
Import-Module PSGraphQLQuery
...then your GQL query via:
Invoke-GraphQLQuery -Query  -Uri

I was able to replicate this issue myself. This has been fixed in v1.1.5. Please get the latest version and let me know if this issue still occurs.

It works! Thanks!


Update add -p testcase

Changes

add toString test in EmailTest, PhoneTest
add company test in Person
add company test in ParserUtilTest
update Javadoc in PersonBuilder

Codecov Report

Merging #272 (bd04414) into master (24dde0a) will increase coverage by 0.24%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #272      +/-   ##
============================================
+ Coverage     60.48%   60.73%   +0.24%
- Complexity      585      588       +3
============================================
  Files           102      102
  Lines          2417     2417
  Branches        326      326
============================================
+ Hits           1462     1468       +6
+ Misses          773      770       -3
+ Partials        182      179       -3

Impacted Files
Coverage Δ

...in/java/seedu/address/logic/parser/ParserUtil.java
74.60% <0.00%> (+3.17%)
:arrow_up:

...rc/main/java/seedu/address/model/person/Email.java
91.66% <0.00%> (+16.66%)
:arrow_up:

...rc/main/java/seedu/address/model/person/Phone.java
90.90% <0.00%> (+18.18%)
:arrow_up:

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


defer document structure to html?

Suggestion: how difficult would it be to handle each pane (javascript, html,css and preview) in it's own div? I ask because it would be much easier to style the page if we had more than one element where everything is dumped to, as opposed to a set of divs that we can arrange in tabs, or in a quad or side by side or implement different layouts or whatever via css.
as it is, each instance of Jotted(document.querySelector('#id') is independant from each other (surprisingly)

There's an easier way to get what you want.
You can use separate instances of Jotted, and connect them with a simple plugin. You can have separate containers for each instance this way.
Here's a quick demo:
http://jsbin.com/jifane/edit?html,js,output

thanks, that did work, but where do i call the plugins now?
say...ace?
i tried calling them the same way as the single instance...once for each pane. that didn't work.
var htmlEditor = new Jotted(document.querySelector('#html'), {   pane: 'html', debounce: '1000',   files: [{ type: 'html', content: ' ', showBlank: true, 	plugins: [ {name:'markdown', options:{} } , {name:'ace', options:{} }	]}]});
so i suppose they should be attached to the callback?
commonPlugin.params.content += 'referencing the plugins array here wont work.'   callback(null, params);
but how?

There was a bug when using content: '', but I fixed it in the latest version.
Here's a demo using Ace:
http://jsbin.com/jifane/edit?html,css,js,output

hmm.. interesting. it works if i only use html and css
but if i add a js pane, js works but css does not.
also, any malformed html (such as an incomplete tag) will spew this to the output:
(function () { window.addEventListener('DOMContentLoaded', function () { window.parent.postMessage(JSON.stringify({ type: 'jotted-dom-ready' }), '*') }) }())

Thanks for reporting the malformed HTML bug. :beer:
I fixed it as released it as 1.4.2.


 Please resolve the merge conflicts.

Blocked by rust-lang/rust#133249

CI is green now.


Instructions on how to add post data to a webhook

File: docker-hub/webhooks.md, CC @johndmulhausen
This is my first attempt at configuring a webhook and I can't see how you actually specify the post data.  It's mentioned in the docs but there's no field for it in the UI.  Can an example be included in the docs?

I think the docs are kind of misleading because I can't configure the POST payload. Docker Hub will always POST a request with the same content.


Warnings, but completes to predict

2023-09-14 08:56:46.293903: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-09-14 08:56:47.295135: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT

Thats standard TensorFlow waringing for some users.


~3 second delay from file change to change notification

Is there a way of improving the ~3 second latency from file change to change notification?

Are you using Hotwatch::new, or Hotwatch::new_with_custom_delay? The latter allows you to specify any delay you'd like.
The documentation for new could certainly be more clear about this behavior, as could the API itself; it might not be the most helpful default.

Yes, it works. With Hotwatch::new_with_custom_delay it is possible to watch file changes at any latency.


Adding hl=en to the page URLs and making language selection full heig…

…ht of list items
@petele @PaulKinlan this is to address: #2143
This does mean all links will have a language code. The canonical URLs will not change with this (i.e. canonical urls in head of pages will not have a hl query param).
Is there any negative side effects to this change?

This replicates the mostly the original way that we handled translated content in WF.


Make Form.Input modifiable

The current Form.Input does not allow to edit its value on the webpage.
React value prevents modification. Form.Input would require an OnChange Handler as a function that would update the state of the component everytime a change is made.

@MrJarv1s do you mean FormTextInput or Form.Input? Form.Input already has onChange and value props that you can pass in a handler and value so that you can control it from the outside, however, there is a bug if you are also trying to use the icon props, this will be resolved in https://github.com/tabler/tabler-react/pull/73/files#diff-958699d8f9fe581c56494bdcc48ec6b3

That is my bad @jonthomp I looked at the Types and not the Props...


GC: Beta Client Package

Description
To add needed features, Kiota-Generated Beta Connector created

Does this PR need a docs update or release note?

[x] :white_check_mark: Yes, it's included

Type of change

[x] :sunflower: Feature

Issue(s)

closes  #2086

Test Plan
Compilation and current CI tests will fail if the package does not align with current operational standards.

[x] :zap: Unit test
[x] :green_heart: E2E

Beta is not production value: Build-times / serialization / and impact on downstream products is too great.

This will be the anchor for feature development.

Process:

Generated package 110k of line changes
Removal of obvious site request which are found in v1.0 --> 800k lines of change

It is important to consider that changes for the Site upload may require a multi-step restore workflow

Removed models that are not necessary for SharePoint.Page GET / POST  commands --> 15k of changes.
Will reduce tomorrow to: Get, Select, Post, Publish


Replace ToUpper/ToLower with ToUpperInvariant/ToLowerInvariant.

Fixes #16855.
This first commit shows the extent of the changes to code files. The only remaining calls/references to ToLower or ToUpper are in the following .md files:

data/ef-mvc/sort-filter-page.md
data/ef-rp/sort-filter-page.md
mvc/controllers/routing.md
mvc/models/file-uploads.md
razor-pages/razor-pages-conventions.md

I'll address those in another commit, excluding the SlugifyParameterTransformer stuff.
Note: The SlugifyParameterTransformer code is all inline in .md files, with no corresponding sample files.
cc @Rick-Anderson, @guardrex

Hold off on mvc/controllers/routing.md, I've already fixed that in a PR I'm working on. That will also prevent a merge conflict.

Without mvc/controllers/routing.md and SlugifyParameterTransformer, this leaves the following two topics:

data/ef-mvc/sort-filter-page.md
data/ef-rp/sort-filter-page.md

Both of these topics currently show ToUpper in the context of an EF Core query, which could be converted to execute within T-SQL. I don't think changing these to ToUpperInvariant is needed, because it seems that this doesn't work the same way due to that conversion to T-SQL. Is there someone that could confirm that?

@serpent5  I'd say skip those two.


[NCL-6752] Implement auth service

You need to specify: export REACT_APP_KEYCLOAK_URL=https://secure-sso-newcastle-devel.psi.redhat.com
Skeleton is there and working, still need some improvements that I noticed:

get rid off env var and read keycloak url in html from configuration file
without kinit aka in private window in protected route is user always unauthenticated and login process is started, it will do it automatically but screen flickers because of this
methods in keycloak service are redundant really, you can and I guess will call static keycloak instance and call methods on it than creating instance of keycloak service to call them

anyway, look at it guys and I'm looking forward your feedback

Hi @DnsZhou , can you check test related parts?

@DnsZhou Thanks for your input Dennis, I extended keycloak mock hopefully to somewhat working mock of full service, do you think we can move creation of new test to new issue as I don't have much knowledge about this and would like to research it a bit first.


update notification style and location

per @ChrBach - "i’d change the color abit (font or background) - and move it under the menu before appernetic, etc."

LGTM


Connecting the viewer when using Docker

I started a docker container with the following command:
docker run --gpus all -v /home/alex/nerfstudio_workspace:/workspace/ -v /home/alex/.cache/:/home/user/.cache/ -p 7007:7007 --rm -it --shm-size=12gb dromni/nerfstudio
I trained my first nerf with poster data and use ns-viewer --load-config outputs/poster/nerfacto/2023-03-24_162756/config.yml
But visiting https://viewer.nerf.studio/?websocket_url=ws://localhost:7007 shows that renderer is disconnected. During training it was disconneceted too.
What I have to do in order to connect it?

I have the same problem,do u solve it?

@Liumt1949 @Alpe6825 use
ns-train nerfacto --data data/nerfstudio/poster --vis viewer_beta


Extend and generate files based on IPMI data

In earlier patches, VirtualBMC was introduced to the CI Framework, with
an easy and small generated fact and subsequent file on the hypervisor.
This patch extends this fact in order to ensure we're exposing the
credentials, meaning we're now able to consume everything from some
other roles (in the same run).
In the reproducer role, we now take that virtualbmc fact, and extend it
a bit more, in order to add network interfaces information; we also
ensure key consistency by applying a "lower" mapping.
The generated file, as of first release of this PR:
baremetal_nodes:
    compute-0:
        address: <IP_ADDRESS>
        boot_mode: UEFI
        nics:
        -   mac: 52:54:00:c6:04:90
            network: public
        -   mac: 52:54:00:ca:a1:e1
            network: osp_trunk
        password: password
        port: 6240
        status: running
        username: admin
    controller-0:
        address: <IP_ADDRESS>
        boot_mode: UEFI
        nics:
        -   mac: 52:54:00:5b:35:8a
            network: public
        -   mac: 52:54:00:ca:45:9f
            network: osp_trunk
        password: password
        port: 6241
        status: running
        username: admin
    crc-0:
        address: <IP_ADDRESS>
        boot_mode: UEFI
        nics:
        -   mac: 52:54:00:86:85:df
            network: public
        -   mac: 52:54:00:4b:3c:e4
            network: osp_trunk
        password: password
        port: 6242
        status: running
        username: admin

As a pull request owner and reviewers, I checked that:

[X] Appropriate testing is done and actually running

This will need another patch to land first, for the proper UEFI vs BIOS support: #1335

Updated generated files:
on the controller-0, this is the current state
[zuul@controller-0 ~]$ cat ci-framework-data/parameters/baremetal-info.yml
baremetal_nodes:
    compute-0:
        address: <IP_ADDRESS>
        boot_mode: legacy
        nics:
        -   mac: 52:54:00:a9:39:04
            network: public
        -   mac: 52:54:00:ec:85:f3
            network: osp_trunk
        password: password
        port: 6240
        status: running
        username: admin
        uuid: 33e71329-b695-47cf-8740-2e8db51b8aeb
    controller-0:
        address: <IP_ADDRESS>
        boot_mode: legacy
        nics:
        -   mac: 52:54:00:da:65:1b
            network: public
        -   mac: 52:54:00:70:26:95
            network: osp_trunk
        password: password
        port: 6250
        status: running
        username: admin
        uuid: 5720b997-91b8-4824-85f9-cde3126aaa2c
    crc-0:
        address: <IP_ADDRESS>
        boot_mode: legacy
        nics:
        -   mac: 52:54:00:bc:28:84
            network: public
        -   mac: 52:54:00:85:e8:97
            network: osp_trunk
        password: password
        port: 6260
        status: running
        username: admin
        uuid: 2ad050da-bb5d-467c-b934-462a4790170c

the boot_mode is computed in such a way it will show either UEFI or legacy depending on the "family" VM UEFI support.
On the hypervisor, those files are generated:
[virtuser@builder2 ~]$ cat ci-framework-data/artifacts/libvirt-uuids.yml
libvirt_uuid:
    cifmw-compute-0: 33e71329-b695-47cf-8740-2e8db51b8aeb
    cifmw-controller-0: 5720b997-91b8-4824-85f9-cde3126aaa2c
    cifmw-crc-0: 2ad050da-bb5d-467c-b934-462a4790170c

[virtuser@builder2 ~]$ cat ci-framework-data/artifacts/virtual-nodes.yml
cifmw_virtualbmc_known_hosts:
-   Address: <IP_ADDRESS>
    Domain name: cifmw-compute-0
    Port: 6240
    Status: running
    password: password
    username: admin
    uuid: 33e71329-b695-47cf-8740-2e8db51b8aeb
-   Address: <IP_ADDRESS>
    Domain name: cifmw-controller-0
    Port: 6250
    Status: running
    password: password
    username: admin
    uuid: 5720b997-91b8-4824-85f9-cde3126aaa2c
-   Address: <IP_ADDRESS>
    Domain name: cifmw-crc-0
    Port: 6260
    Status: running
    password: password
    username: admin
    uuid: 2ad050da-bb5d-467c-b934-462a4790170c

It should therefore meet the various needs. Note that calling the deploy_layout outside of the reproducer, without virtualbmc will let you with "only" the ci-framework-data/artifacts/libvirt-uuids.yml file on the hypervisor. You'll have to gather it and compute it yourself if you need those data.

/test all

/approve


Tenant aware broadcasting with authentication

Bug description
This may not be technically a bug, but I didn't find anything related to broadcasting in the docs. I am creating a simple restaurant management system API which fires a broadcasting event when a customer places an order from the mobile app and the restaurant will receive that event on a desktop client. I am using laravel-websockets for broadcasting. I am using tenancy in this project as this will be used in multiple restaurants with their own users and data.
For simplicity and testing purpose, I am using a separate Vue project and Postman to test the broadcasting. It worked fine and the broadcast was successfully received by Vue while using public channel, but I couldn't make it work using private channel and authentication.
I am using sanctum for authentication, so I modified the BroadcastServiceProvider as below:
class BroadcastServiceProvider extends ServiceProvider
{
    /**
     * Bootstrap any application services.
     *
     * @return void
     */
    public function boot()
    {
        Broadcast::routes(['middleware' => ['auth:sanctum']]);
        require base_path('routes/channels.php');
    }
}

I created a channel route in routes/channels.php to handle the request and authentication:
Broadcast::channel('customer-order', function ($user) {
    return $user->role == "admin" || $user->role == "staff";
});

Below is the defined broadcast channel on my OrderPlaced event
....
/**
 * Get the channels the event should broadcast on.
 *
 * @return \Illuminate\Broadcasting\Channel|array
 */
public function broadcastOn()
{
    return new PrivateChannel('customer-order');
}
....

I am using simple Vue.js app to listen to broadcasts:
import Echo from "laravel-echo";
import Pusher from "pusher-js";
window.Pusher = Pusher;

const token = "1|OZdkQFNRDpUxHNnXD7MFAyqlVo9dMCesA2ZkIDRz"

window.Echo = new Echo({
  broadcaster: 'pusher',
  key: 'laravel_socket',
  wsHost: '<IP_ADDRESS>',
  authEndpoint: 'http://localhost/my-app/public/broadcasting/auth',
  encrypted: true,
  forceTLS: false,
  wsPort: 6001,
  wssPort: 6001,
  disableStats: true,
  enabledTransports: ['ws', 'wss'],
  auth : {
    headers : {
        Authorization: "Bearer " + token,
        Accept: "application/json",
    }
},
})

window.Echo.private('customer-order')
    .listen('OrderPlaced', (e) => {
    console.log(e)
})

With this configuration, Vue.js app cannot connect to the socket server because server responds with POST http://localhost/my-app/public/broadcasting/auth 401 (Unauthorized)
Again, everything works if I use public channels for broadcasting and listening without any reference to tenancy and authentication. My main concern is how do I set up to use tenancy aware broadcasting with authentication?
Steps to reproduce

Expected behavior

Laravel version
9.7.0
stancl/tenancy version
3.5.6

@stancl Is there any info about broadcasting and authentication for now so that I could continue my development till it officially gets it way to the documentation.

I think this may have been discussed on our Discord

Yeah, very briefly. I asked that question but that was a workaround kind of solution. Is there anything else that this package provides?

Would be nice to have some documentation about this. I'm ready to migrate my app to use tenancy and broadcasting is a big thing.

Thank you so much for asking this! Because I want to create same system

Recently prepared to use soketi and broadcast system, but did not find relevant documentation.
It is recommended to add a description in the V4 version of the document

Would be nice to have some docs about this on V3. Even though it says something like: "- we do not support it. You should manage it yourself."

Going to decide how we handle broadcasting when I work on v4. Will probably share some updates soon

I discovered that this is dangerous as the authentication works but the channels are just one big Channel, for example;
You have two tenants; tenant1 and tenant2 with separate databases.
There  is user with id 10 on tenant 1 and also on tenant2.
You broadcast to id 10 on tenant1 with private channel me.10
You only want the user on tenant1 to receive the message but the message is received on both tenants because the user ID is the same. I fixed this by adding the tenant id in the private channel so; me... A other option would be different pusher keys for each tenant
I discovered this by accident but I wanted to share this with you.

Thanks! Will take a look on my implementation!

Going to decide how we handle broadcasting when I work on v4. Will probably share some updates soon

Is there any documentation on multi-tenant broadcast handling now?

Just wanted to hop in here and add to this one, while it isn't a solution (yet), certainly something to consider.
We are using Soketi for our socket service, and as such are using the Apps feature of that to manage our socket client access. This allows for db usage to manage 'apps', which we are doubling up with our tenants db, so as to allow each tenant to have their own broadcasting system, isolated from other clients.
Now, this gives the ability to simply create a custom bootstrapper which will swap out the required credentials within Laravel regarding the broadcaster. This is something I hope to work on in the next week or so.
The only problem I see is that this is made easy due to the abilities of Soketi or other Pusher service such as Pusher Channels or Laravel-Websockets, but maybe won't be so simple with something like laravel-echo-server or other custom service.
But could be tackled using/providing various 'sub' bootstrappers for the more mainstream broadcasting engine configurations.
Will see what I can come up with as part of my experimentation and feed back :)

Adding my two cents:
In my case (SPA frontends / API backend) i needed to handle brodcasting routes both for the central app and the tenant app.
Just added the below in the routes/api.php
if (request()->hasHeader('X-Tenant')) {     Broadcast::routes(['middleware' => ['auth:sanctum',InitializeTenancyByRequestData::class]]); } else {     Broadcast::routes(['middleware' => ['auth:sanctum']]); }

Thanks to your solution it worked for me! But now I have a problem with Pusher. In the face-to-face channels, the connection in each tenant works correctly, but with private channels they always appear as: Occupied. Has this happened to anyone else?

I see that there is currently a tenancy bootstrapper for broadcasting in the works to be in the next release so take my current solution with a grain of salt if 4.x is out.
The issue with @iamsubingyawali solution is as @zainspresso pointed out. That ultimately, an event being handle by whatever driver and server combo you choose is "session-less". The channel name needs to contain something that uniquely identifies the tenant. The tenant ID would be an obvious choice.
Broadcast::channel('order.{tenant}', function ($user, $tenant) {   return $tenant === tenant()->id; });
If tenant isolation is a concern, then as @J5Dev suggested multiple servers can be a solution especially with soketi. But along with other potential security issues and the complexity/hassle of implementation and maintenance, I feel like my solution is a lot simpler and secure if you have a typical tenancy setup that identifies tenants by domain/subdomain.
https://tenancyforlaravel.com/docs/v3/session-scoping/#using-a-middleware-to-prevent-session-forgery
By utilizing one of the session scoping strategies suggested, you can simply use InitializeTenancyBySubdomain::class as one of the specified middlewares for Broadcast::routes(...). Or whatever equivalent middleware based on your tenancy setup.
You should only use InitializeTenancyByRequestData::class if you aren't identifying the tenant by domain or subdomain. Like a SPA with sanctum or an API with passport for example.


Change password option does not work from the portal IOT server 3.1.0

When I change the password and login using the new password to the IOT server 3.1.0 server device management portal it is stuck and not redirected to portal home

fixed


Fix logging error for batch size greater than 1

Addresses #5

Should fix e2e tests due to example model changes.


[META] ML Inference Processor Enhancements III

Is your feature request related to a problem?

[ ] template query  --targeting 2.19
[ ] ml inference search request extension --targeting 2.19
load image from url  function in Connector (PIL.image) -- supporting image search and CLIP
[ ] save memory --- supporting conversational search --targeting 2.20
[ ] hide/remove field search response processor --targeting 2.20

All META Issues for ML Inference Processor:
https://github.com/opensearch-project/ml-commons/issues/2839
https://github.com/opensearch-project/ml-commons/issues/2878
What alternatives have you considered?
A clear and concise description of any alternative solutions or features you've considered.
Do you have any additional context?
#2173

Linking https://github.com/opensearch-project/ml-commons/issues/3152 as it relates to image support

Hi, for the  load image from url function in Connector (PIL.image) -- supporting image search and CLIP task we have to put on pause as our internal security team has stated explicitly that they don't want us to implement this (has to many edge cases).
Currently ML Commons supports for base64 strings that are used to invoke multi-modal models. Full end to end workflows were done to see that this is possible, without downloading from URL


Question: sensu event filter

Hi,
I've had a go at using event filters to only specify alerts to be sent from certain DCs / environments based on a custom host attribute, this works fine as long as I only specify one environment name / filter - however - as soon as I add a second, it does not seem to work as I had expected.
Does this https://github.com/sensu/sensu/blob/master/lib/sensu/server/filter.rb#L194 mean that, unless all event filters match, that the event will be filtered ? An AND action, rather than OR ?
I couldn't find clear documentation about this, hence me asking. The behaviour does suggest that it's doing a AND rather than OR.
If it's doing a AND ( e.g. filter unless env=prod AND env=qa ) is there a way to instruct the filter "engine" to do a OR (e.g. filter unless env=prod OR env=qa) ?
Let me know if it doesn't make sense :)
Thanks,
Alex

Hey @alex-leonhardt, it is AND. You could make use of an eval filter attribute - https://sensuapp.org/docs/latest/filters#filter-eval-attributes - e.g. "env": "eval: %w[prod qa].include?(value)" :+1:

Thanks @portertech - I guess I should raise a feature request to add ability to specify if it's a AND or a OR :) ? I'll try that eval you've got there and post results here.


Space submits form

Hi,
Is anyone else seeing this?
When typing in a text field on a swal-form hitting the space bar submits the form.
Thanks
Wayn0

I cannot reproduce it on the live example (using Chrome): https://cdn.rawgit.com/taromero/swal-forms/master/live-demo/live-demo.html. Could you provide a reproduction case in a JSFiddle (or the like), indicating the browser and swal-forms version (commit)?
Thanks!

Wow, thanks for the quick response man :-)
Can't reproduce with the live demo.
JsFiddle demonstrating the issue.
https://jsfiddle.net/za7mvfqj/2/
swal version:
swal-forms commit: 92a912e4dac46e08d92035e65347a3ce1c533da1 (most recent I believe)
Firefox 44.0 on Ubuntu 15.10
Chromium on Ubuntu 15.10
Chrome 48 on Windows 7
Thanks, anything else you would like me to test?

I just tested it again and this only seems to happen with the specific version of sweet-alert that is linked in the jsfiddle. By replacing that lib with either the lib that is currently available for download on sweet-alert's site or by https://cdnjs.cloudflare.com/ajax/libs/sweetalert/1.1.3/sweetalert.min.js, the problem doesn't happen.
Which is the version (commit) of sweet-alert that you point to?

Thank you sir, updating to the latest sweet-alert fixed the issue.
The version I was using came bundled with code I was handed, so it does not have any version strings.
Thanks for your help, hopefully if anyone else experiences the same problem they will find this issue.
Great work by the way, these form really speed up input :-)

Thanks for reporting!


Revised JupyterCon Logo

Revised jupytercon logo on landing page to match O'Reilly's new one:
Before:

After:

Looks good, merging!


[1.11 regression] user namespaces + btrfs can't run containers

This works on both 1.10.2 and 1.10.3-rc2.
% docker version
Client:
 Version:      1.11.0-dev
 API version:  1.23
 Go version:   go1.6
 Git commit:   f70f570
 Built:        Thu Mar 10 12:13:38 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.0-dev
 API version:  1.23
 Go version:   go1.6
 Git commit:   f70f570
 Built:        Thu Mar 10 12:13:38 2016
 OS/Arch:      linux/amd64
% docker info
Containers: 4
 Running: 0
 Paused: 0
 Stopped: 4
Images: 7
Server Version: 1.11.0-dev
Storage Driver: btrfs
 Build Version: Btrfs v3.17
 Library Version: 101
Execution Driver: native-0.2
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host bridge
Kernel Version: 4.4.3-1-default
Operating System: openSUSE Tumbleweed (20160307) (x86_64)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.688 GiB
Name: gondor
ID: DDDM:OY6U:WD3X:DVTL:6OXN:JL4L:2YDN:2BAU:6LAZ:WCZA:Z2YJ:4KH5
Docker Root Dir: /var/lib/docker/123456.123456
Debug mode (client): false
Debug mode (server): false
Username: cyphar
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
WARNING: No kernel memory limit support

List the steps to reproduce the issue:
% docker daemon -s btrfs --userns-remap default
[in another shell]
% docker pull alpine:latest
% docker run -it alpine sh
docker: Error response from daemon: Container command could not be invoked..

The error logs from docker daemon being:
ERRO[0109] error locating sandbox id 4ccbd5aebe711239cdbbd7ed9fe4305420fc99238a75ebea32c562c802f6ed34: sandbox 4ccbd5aebe711239cdbbd7ed9fe4305420fc99238a75ebea32c562c802f6ed34 not found
WARN[0109] failed to cleanup ipc mounts:
failed to umount /var/lib/docker/123456.123456/containers/d2b965c3dba48236adf830a90b956664f17196c3f9464507b172bb9bf600da0a/shm: invalid argument
ERRO[0109] Error unmounting container d2b965c3dba48236adf830a90b956664f17196c3f9464507b172bb9bf600da0a: not mounted
ERRO[0109] Handler for POST /v1.23/containers/d2b965c3dba48236adf830a90b956664f17196c3f9464507b172bb9bf600da0a/start returned error: Container command could not be invoked.

/cc @estesp

I tried use loop device to simulate btrfs, (make btrfs pools etc). Not found this issue
ubuntu@dockerwork:~$ docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: 1.10.3
Storage Driver: btrfs
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: null host bridge
Kernel Version: 3.13.0-43-generic
Operating System: Ubuntu 14.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 7.798 GiB
Name: dockerwork
ID: TKJQ:7UVP:PMPC:QIYJ:BYIO:NFMN:D4MI:CVUN:4PNS:IHAT:5FLP:6I73
WARNING: No swap limit support
ubuntu@dockerwork:~$ docker pull alpine:latest
latest: Pulling from library/alpine
4d06f2521e4f: Pull complete
Digest: sha256:7739b19a213f3a0aa8dacbd5898c8bd467e6eaf71074296a3d75824e76257396
Status: Downloaded newer image for alpine:latest
ubuntu@dockerwork:~$ docker run -it alpine sh
/ #

Maybe it happened on real device only?

Yes, this is with btrfs on my root filesystem, so it's using actual subvolumes.

Not understand why only happened on actual subvolumes.  Interesting to know that. I did not have free machine or disk to test that. So wait for others response :)

ping @vbatts, who runs on btrfs :heart:

Something is very strange. I can no longer get userns to run on my master fork (even after making sure I'm even with master) on any kind of graphdriver.  After lots of headscratching, I decided that the "chdir()" failure with access permissions must be related to /var/lib/docker dir perms.. and sure enough, if I change it on Fedora or Ubuntu to "0711" (you must do this after starting Docker as it checks/sets perms every time), then everything starts working again.
Why master runs are not hitting this, I have no idea :(

Adding this to the milestone, so that we don't loose track

hmmm. This seems to work OK with ed6fb41 and compiled with go1.5.3
vbatts@valse ~ (master) $ docker version
Client:
 Version:      1.11.0-dev
 API version:  1.23
 Go version:   go1.5.3
 Git commit:   ed6fb41
 Built:        Sun Mar 13 11:11:07 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.0-dev
 API version:  1.23
 Go version:   go1.5.3
 Git commit:   ed6fb41
 Built:        Sun Mar 13 11:11:07 2016
 OS/Arch:      linux/amd64
vbatts@valse ~ (master) $ docker pull alpine:latest
latest: Pulling from library/alpine
4d06f2521e4f: Pull complete
Digest: sha256:7739b19a213f3a0aa8dacbd5898c8bd467e6eaf71074296a3d75824e76257396
Status: Downloaded newer image for alpine:latest
vbatts@valse ~ (master) $ docker run -it alpine:latest sh
/ # ^D
vbatts@valse ~ (master) $ docker info
Containers: 1
 Running: 0
 Paused: 0
 Stopped: 1
Images: 1
Server Version: 1.11.0-dev
Storage Driver: btrfs
 Build Version: Btrfs v4.3.1
 Library Version: 101
Execution Driver: native-0.2
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host bridge
Kernel Version: 4.4.3-300.fc23.x86_64
Operating System: Fedora 23 (Workstation Edition)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 11.43 GiB
Name: valse.usersys.redhat.com
ID: PK4Z:YOAF:KCUV:IHEF:HXW2:QKPI:36RK:JIHI:ERMB:KPG2:LKCN:YIAL
Docker Root Dir: /home/docker/100000.100000
Debug mode (client): false
Debug mode (server): true
 File Descriptors: 14
 Goroutines: 27
 System Time: 2016-03-13T11:17:37.568655036-04:00
 EventsListeners: 0
Username: vbatts
Registry: https://index.docker.io/v1/

But not when compiled with go1.6
vbatts@valse ~ (master) $ docker version
Client:
 Version:      1.11.0-dev
 API version:  1.23
 Go version:   go1.6
 Git commit:   ed6fb41
 Built:        Sun Mar 13 11:18:18 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.0-dev
 API version:  1.23
 Go version:   go1.6
 Git commit:   ed6fb41
 Built:        Sun Mar 13 11:18:18 2016
 OS/Arch:      linux/amd64
vbatts@valse ~ (master) $ docker pull alpine:latest
latest: Pulling from library/alpine
4d06f2521e4f: Pull complete
Digest: sha256:7739b19a213f3a0aa8dacbd5898c8bd467e6eaf71074296a3d75824e76257396
Status: Downloaded newer image for alpine:latest
vbatts@valse ~ (master) $ docker run -it alpine:latest sh
/home/vbatts/src/github.com/docker/docker/bundles/1.11.0-dev/binary/docker-1.11.0-dev: Error response from daemon: Container command could not be invoked..

@vbatts It might be some stdlib change that's causing this issue then.

right. To be clear, it is a docker-1.11 and go1.6 issue. Because docker-1.10.3 and go1.6 works fine.

can someone confirm that setting perms to 0711 on /var/lib/docker allows containers to start? You will need to do that chmod after Docker is started or else it will revert the perms to 0701.

@estesp No, that doesn't work for me (some environment as above).

@estesp Yes, that solves this problem for me.


Not able to collect custom metrics

I deployed dotnet monitor as a side car  and I have written a custom metric using EventCounter in my dotnet application with Event Source name demo.RequestTime and added the below json file as a secret with name api-secret
{
"Metrics": {
"Providers": [
{
"ProviderName": "demo.RequestTime"
}
]
}
}
And below is my YAML file for deployment and I'm not getting custom metrics created using EventCounter when I access /metrics end point.
apiVersion: apps/v1
kind: Deployment
metadata:
name: dotnetmonitorsample
labels:
app: dotnetmonitorsample
spec:
replicas: 1
selector:
matchLabels:
app: dotnetmonitorsample
template:
metadata:
labels:
app: dotnetmonitorsample
spec:
volumes:
- name: sharedtmp
emptyDir: {}
- name: api-secret
secret:
secretName: api-secret
containers:
- name: dotnetmonitorsample
image: dd:v1
volumeMounts:
- name: sharedtmp
mountPath: /tmp
- name: dotnetmonitoragent
image: mcr.microsoft.com/dotnet/nightly/monitor:5.0.0-preview.1
ports:
- containerPort: 52325
args: ["--urls", "http://:52323", "--metricUrls", "http://:52325"]
volumeMounts:
- name: sharedtmp
mountPath: /tmp
- name: api-secret
mountPath: /etc/dotnet-monitor

Are you certain that your custom event source provider has a name of Microsoft-AspNetCore-Server-Kestrel? That looks like a built-in event source provider.

Sorry I copied wrong json file, I edited the json file now can you please see it once

Your JSON content needs to be mounted as a settings.json file under /etc/dotnet-monitor, otherwise dotnet-monitor will not be able to discover the settings.

My JSON content is mounted as settings.json file under /etc/dotnet-monitor
I followed the below steps  to add custom metrics support can you see once and check if I miss anything
step 1: Created a custom metric using EventCounter with EventSource name demo.RequestTime
step 2: Created a settings.json file with the below JSON content
{
"Metrics": {
"Providers": [
{
"ProviderName": "demo.RequestTime"
}
]
}
}
step 3: created a secret using the command: Kubectl create secret generic api-secret --from file="C:\Users\jaya.reddy\Desktop\Demo\demo1\settings.json"
step 4: Deployed the below YAML file
apiVersion: apps/v1
kind: Deployment
metadata:
name: dotnetmonitorsample
labels:
app: dotnetmonitorsample
spec:
replicas: 1
selector:
matchLabels:
app: dotnetmonitorsample
template:
metadata:
labels:
app: dotnetmonitorsample
spec:
volumes:
- name: sharedtmp
emptyDir: {}
- name: api-secret
secret:
secretName: api-secret
containers:
- name: dotnetmonitorsample
image: dd:v1
volumeMounts:
- name: sharedtmp
mountPath: /tmp
- name: dotnetmonitoragent
image: mcr.microsoft.com/dotnet/nightly/monitor:5.0.0-preview.1
ports:
- containerPort: 52325
args: ["--urls", "http://:52323", "--metricUrls", "http://:52325"]
volumeMounts:
- name: sharedtmp
mountPath: /tmp
- name: api-secret
mountPath: /etc/dotnet-monitor
step5: used the cmd to port-forward: kubectl port-forward pod/dotnetmonitorsample-b4b496977-5tkbx 7001:52323
step:6 accessed localhost:7001/metrics  and I don't see my custom metrics

You should check the status of your pod and make sure all of the containers are running. From my testing, it is likely your dotnet-monitor container keeps exiting. With your choice of args for the dotnet-monitor container args: ["--urls", "http://:52323", "--metricUrls", "http://:52325"] I'm seeing that the dotnet-monitor container exits. If I look at the logs on the container, it shows:
{"Timestamp":"2021-06-22T15:38:40.8803854Z","EventId":15,"LogLevel":"Error","Category":"Microsoft.Diagnostics.Tools.Monitor.Startup","Message":"Unable to listen to http://:52323. Dotnet-monitor functionality will be limited.","Exception":"System.FormatException: Invalid url: \u0027http://:52323\u0027    at Microsoft.AspNetCore.Http.BindingAddress.Parse(String address)    at Microsoft.Diagnostics.Tools.Monitor.AddressListenResults.Listen(KestrelServerOptions options, String url) in /_/src/Tools/dotnet-monitor/AddressListenResults.cs:line 74","State":{"Message":"Unable to listen to http://:52323. Dotnet-monitor functionality will be limited.","url":"http://:52323","{OriginalFormat}":"Unable to listen to {url}. Dotnet-monitor functionality will be limited."},"Scopes":[]}
{"Timestamp":"2021-06-22T15:38:40.8854161Z","EventId":15,"LogLevel":"Error","Category":"Microsoft.Diagnostics.Tools.Monitor.Startup","Message":"Unable to listen to http://:52325. Dotnet-monitor functionality will be limited.","Exception":"System.FormatException: Invalid url: \u0027http://:52325\u0027    at Microsoft.AspNetCore.Http.BindingAddress.Parse(String address)    at Microsoft.Diagnostics.Tools.Monitor.AddressListenResults.Listen(KestrelServerOptions options, String url) in /_/src/Tools/dotnet-monitor/AddressListenResults.cs:line 74","State":{"Message":"Unable to listen to http://:52325. Dotnet-monitor functionality will be limited.","url":"http://:52325","{OriginalFormat}":"Unable to listen to {url}. Dotnet-monitor functionality will be limited."},"Scopes":[]}
{"Timestamp":"2021-06-22T15:38:40.9626451Z","EventId":6,"LogLevel":"Critical","Category":"Microsoft.AspNetCore.Hosting.Diagnostics","Message":"Application startup exception","Exception":"Microsoft.Diagnostics.Monitoring.MonitoringException: Unable to bind any urls.    at Microsoft.Diagnostics.Tools.Monitor.Startup.Configure(IApplicationBuilder app, IHostApplicationLifetime lifetime, IWebHostEnvironment env, IAuthOptions options, AddressListenResults listenResults, ApiKeyAuthenticationOptionsObserver optionsObserver, ILogger\u00601 logger)    at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor, Boolean wrapExceptions)    at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)    at Microsoft.AspNetCore.Hosting.ConfigureBuilder.Invoke(Object instance, IApplicationBuilder builder)    at Microsoft.AspNetCore.Hosting.ConfigureBuilder.\u003C\u003Ec__DisplayClass4_0.\u003CBuild\u003Eb__0(IApplicationBuilder builder)    at Microsoft.AspNetCore.Hosting.GenericWebHostBuilder.\u003C\u003Ec__DisplayClass13_0.\u003CUseStartup\u003Eb__2(IApplicationBuilder app)    at Microsoft.AspNetCore.Mvc.Filters.MiddlewareFilterBuilderStartupFilter.\u003C\u003Ec__DisplayClass0_0.\u003CConfigure\u003Eg__MiddlewareFilterBuilder|0(IApplicationBuilder builder)    at Microsoft.AspNetCore.HostFilteringStartupFilter.\u003C\u003Ec__DisplayClass0_0.\u003CConfigure\u003Eb__0(IApplicationBuilder app)    at Microsoft.AspNetCore.Hosting.GenericWebHostService.StartAsync(CancellationToken cancellationToken)","State":{"Message":"Application startup exception","{OriginalFormat}":"Application startup exception"},"Scopes":[]}

You need to specify a host for each of the URLs, e.g. args: [ "--urls", "http://localhost:52323", "--metricUrls", "http://localhost:52325" ] in order for the tool to run.

Once you get your container running and if you are still having issues, you can exec into the container to run dotnet-monitor config show to make sure that dotnet-monitor sees your configuration. Please provide that configuration with your next update if you are still having issues.

Separately, I would encourage you to update your image to Preview 5: mcr.microsoft.com/dotnet/monitor:5.0.0-preview.5. The Preview 1 image is now a year old and many enhancements and bug fixes have been made since then. If you do move to a newer image (Preview 4 or newer), be aware that authentication is being enforced (#27). Please read the documentation for more information.

I'm closing this issue because it's going stale and I believe the problem was that your container wasn't actually running. Feel free to reopen if you need more help specifically with this issue.


[change] Turn on API by default #203

Set the default value of USERS_AUTH_API in settings.py to true.
Updated the readme.
Closes #203

Coverage remained the same at 98.391% when pulling 1e9e5d28827cd052b7ac5403359bda4c06fb2253 on lehone-hp:issue-203 into e3577f03a0c381e1ab53ace751dd902d3498647d on openwisp:master.

Coverage remained the same at 98.391% when pulling 1e9e5d28827cd052b7ac5403359bda4c06fb2253 on lehone-hp:issue-203 into e3577f03a0c381e1ab53ace751dd902d3498647d on openwisp:master.

Coverage remained the same at 98.391% when pulling 1e9e5d28827cd052b7ac5403359bda4c06fb2253 on lehone-hp:issue-203 into e3577f03a0c381e1ab53ace751dd902d3498647d on openwisp:master.

Coverage remained the same at 98.391% when pulling 1e9e5d28827cd052b7ac5403359bda4c06fb2253 on lehone-hp:issue-203 into e3577f03a0c381e1ab53ace751dd902d3498647d on openwisp:master.

Thanks :+1:

Thanks :+1:


[FLINK-1556] Corrects faulty JobClient behaviour in case of a submission failure

Corrects the behaviour of the JobClient in case of a submission failure. The PR also contains test cases for the job submission.
Additionally, reworked how exceptions are transmitted from the JobManager to the JobClient. They are directly wrapped into a akka.actor.Status.Failure and send to the JobClient.
This PR is based on #419.

Looks good, will merge this as well...


Response definitions can be defined globally in spec

Fixes #180 .
Description
As described in Swagger Specification it is possible to define global responses to be used in endpoint specs.
Changes proposed in this pull request:

Added possibility to reference (exp.: $ref: '#/responses/Something') responses defined globally in specification.

Coverage increased (+0.002%) to 99.415% when pulling d355d8ae5db706def0b2a434c2224900c0a5d465 on rafaelcaricio:global_response_defs into 83a439dc64e486774e29680ad93a1d5f31123bc1 on zalando:master.

Tested with a global response spec, works as expected.


Upgrade QUnit to 2.0

Corollary to https://github.com/rwjblue/ember-qunit/pull/234.
Only real change here is to provide a new test adapter for handling async. This might belong in ember-qunit as opposed to this addon, but adding it here was way easier.

Tested this against Ember Observer and all is passing. But it is dependent on https://github.com/rwjblue/ember-qunit/pull/234 being released first. I'll figure out what Travis is red in the meantime...

I just released<EMAIL_ADDRESS>with the changes from https://github.com/rwjblue/ember-qunit/pull/234, would you mind updating things here to match and smoke test?

@rwjblue rebased this to use<EMAIL_ADDRESS>and everything seems green. Also tested against the Ember Observer test suite again, no issues.


components/engine_test: fix double-lock in open_tablet

What is changed and how it works?

Issue Number: Ref #13186
What's Changed:

Restrict `registry.lock()` in a scope so that it cannot double-lock with another `registry.lock()` in `open_tablet_raw`->`create_table`
Remove the redundant `reg.insert`, which has been called in `create_tablet`.

Related changes

Need to cherry-pick to the release branch

Check List
Tests

No code

Side effects
Release note
Fix a double-lock bug in components/engine_test

/run-check-issue-triage-complete

/merge


Why is the minimum capacity 64?

Using OptAsChan allows me to override this but was surprised.

Sounds reasonable, was surprised a bit but setting as chan seemed to solve my underlying issue and mental disconnect. I very much appreciate the detailed response.


[DOC] Flink KDF usage

Code of Conduct

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

Search before asking

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

What type of changes will we make to the documentation?
Usage of New Feature
Affects Version(s)
master
Improving the documentation
https://github.com/apache/kyuubi/issues/4938
Spark KDF usage
https://github.com/apache/kyuubi/blob/master/docs/extensions/engines/spark/functions.md?plain=1
https://kyuubi.readthedocs.io/en/master/extensions/engines/spark/functions.html
Are you willing to submit PR?

[ ] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to improve.
[ ] No. I cannot submit a PR at this time.

I could take care of this. Assigned myself if no other volunteers.


SXIV is archived

Since Jan/2023 SXIV is archived, there is an alternative being maintained nsxiv, maybe this plugin can be updated to used the nsxiv version?

Hello
Thanks for the advise.
Anyway, I have made configurable the application to open the resultant image:
require'soil'.setup{
    image = {
        -- This is a default implementation of using xsiv to open the resultant image
        -- Edit the string to use your preferred app to open the image
        -- Some examples:
        -- return "feh " .. img
        -- return "xdg-open " .. img
        execute_to_open = function(img)
            return "sxiv -b " .. img
        end
    }
}

Have a nice day!


Create Header Component

I'll like to take this on as the section of the site has a coming soon on it

That will be awesome, I assigned it to you, make sure you look at how the pages for the other components were structured

Alright I'll do that 💪🏽

I think this has been resolved
@khazifire

@Elishaokon13 can you run npm build and try to resolve the errors then create another pull request


tailscale: 1.74.0 -> 1.74.1

Description of changes
https://tailscale.com/changelog#2024-09-18
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 342881 run on x86_64-linux 1

4 packages built:

tailscale
tailscale-gitops-pusher
tailscale-nginx-auth
trayscale

Tested Locally

@NixOS/nixpkgs-merge-bot merge


Issue configuring CAS 4.2.3 with Mongo service registry

After following the CAS 4.2.X documentation for configuring the Mongo Service Registry, the following error is produced in the logs upon deployment from Maven (mvn clean tomcat7:deploy or mvn clean tomcat7:redeploy).
Usage of 'UserCredentials' with 'MongoClient' is no longer supported
Root cause appears to be (from tomcat logs):
Caused by: org.springframework.dao.InvalidDataAccessApiUsageException: Usage of 'UserCredentials' with 'MongoClient' is no longer supported. Please use 'MongoCredential' for 'MongoClient' or just 'Mongo'.
at org.springframework.data.mongodb.core.SimpleMongoDbFactory.(SimpleMongoDbFactory.java:137)
at org.springframework.data.mongodb.core.SimpleMongoDbFactory.(SimpleMongoDbFactory.java:93)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:147)
... 120 more
tomcatLog.txt
Environment:

OS: Centos 7
Container: Tomcat 7
Java 8
Maven 3.3.9
Vanilla CAS 4.2.3 Maven Overlay (only customization made is trying to setup Mongo Service Registry)
Vanilla Mongo DB installed on same server (Centos 7)

Thank you.

https://github.com/apereo/cas/issues/1891


Fix deadlock

Is it fixed or not yet?

This does stop the deadlock but i literally have no idea why the Close call was deadlocking. Probably something to do with redirecting the output stream


util.inspect is your friend with this API

All the tests and readme show properties being already embedded in strings.  If you already have a json object you want to use, use util.inspect as shown below.  Perhaps an example of this can find its way into the readme and/or test suite if others find it useful.
api.addEvent = async ({event}) => {
  const query = `CREATE (:event${util.inspect(event)})`;
  const result = await graph.query(query);
  console.log('RESULT', result);
};

Not sure yet how to deal with quoted object key values required for keys like 'some-key' or '@context' in javascript.  Also, it appears that nested properties are not allowed.  I'm not sure yet if that's a Cypher limitation or a limitation somewhere in the RedisGraph stack.

nested props are a cypher limitation, not sure if it's too encourage peoples to follow a graph way of creating nodes instead of nesting objects or if it's just the neo4j team being lazy


how to use

is this code correct?
(import requests

headers = {
    user-agent': 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 Safari/537.36',
    'body': 'tiktok url',

}
u="https://signtok.vercel.app:8080/signature"

r = requests.post(u, headers=headers)
print(r)
print(r.text)
#print(r.json()))

because it gave error connection closed...
is this working with the new tiktok api?
is there any demo at Heroku or similar?

Hi,

That url is not correct. You have to use https://signtok.vercel.app/api/signature (vercel requires that /api for the serverless functions)
You have to send a 'data' parameter for the POST payload
You don't need to send a custom user-agent, the program will handle that for you.

So, fixing those issues your code should look like this:
import requests

data = 'tiktok_url'

u = "https://signtok.vercel.app/api/signature"

r = requests.post(u, data=data)
print(r.json())

I'll write some documentation for usage

is this working with the new tiktok api?

Yes, at least for now it can generate valid _signature and x-tt-params

is there any demo at Heroku or similar?

I had one on Heroku but I ended up moving it to Vercel because it would exceed my cuota, but I'm planning to make an app.json to make hosting an instance easier.

You are the star, that's working very well, thank you very much

when we got signed url this is not giving us data any help ?


Ambiguous function all

In utility.cc, @ line 305, isnan(value) in ambiguous when compiled with c++.  It should be std::isnan(value)

Hmm.. I don't see a utility.cc or isnan() in the whole project. Can you give a link to what file you are talking about?

I'm closing this as an invalid report as it does not make any sense to me. Maybe reported against a wrong project?


Matching Arbitrary Path

Hello,
It's been great contributing small fixes to this library (Kudos to @Vkt0r), so I have a slightly more challenging problem now which I'd like to collaborate/contribute as well.
Basically, I have a requirement to make the router match against an arbitrary path. Here is the exact code I have in my project:
server["/mock-server/:mockpath"] = { request in

    guard let spec = self.mounting.spec(for: request) else {
        os_log("[404]: Request not found %@", request.path)
        return .notFound
    }

    var headers = spec.response.headers
        .filter { !badHeaders.contains($0.key.lowercased()) }
    headers["Content-Length"] = "\(spec.response.data.count)"

    return .raw(spec.response.code,
                "OK",
                headers,
                { try $0.write(spec.response.data) })
}

Basically, I use mock-server as an entry point to the mock server features, and :mockpath is captured and used to look up the mock response. I understand I can perhaps achieve the same result using query parameter mock_path=..., but I'd like the application being tested to be as identical as possible to the real world scenario. It is also more convenient for developers to treat the mock server in an identical manner using a path instead of a query.
So, to achieve that, I tried first to play with the wildcard * specifier, but wasn't successful in achieving this.
Unfortunately, due to time constraint, I ended up with a tiny hack that made it work, but at the expense of breaking other routing functionality, as you can see in the following commit:
https://github.com/Mazyod/swifter/commit/fd2c8e08737d69eed637ac5d3627aa5250d3ead4
My question becomes, is this a feature you're interested in? Do you have a general opinion about the direction or implementation in which this should be achieved that I can follow? Or would you be open to a proposal from me to potentially support this feature without breaking current routing logic?
Thanks!

Hey, @Mazyod Thanks for bringing this up. You're completely right. the possibility to match arbitrary path was removed in 1.4.6. Let me explain a little more about the issue we were having allowing arbitrary paths or match all routes like /mock-server/:mockpath.
The first issue reported was in #355 with examples of routes like:
router.register("GET", path: "a/:id", handler: handler)
router.register("GET", path: "a/:id/c", handler: handler)

In that case, the routers were giving precedence to paths causing the handlers were resolved incorrectly, you can try it yourself in your fork with the failing tests you mentioned. With the arbitrary path, the router would resolve it with the first one even when the request is a/b/c as he matches everything and a route was specified with that purpose and IMHO that is wrong as we should have a better way of specifying a match-all route maybe a/* 🤔 (several servers are doing in that way).
Right now the wildcard is not used with that purpose unfortunately but it can be modified for that purpose with a little work. Nevertheless, it's very important to know when a match-all route is identified this would have precedence over all the rest of the routes!
I want to make more investigation related to the match-all route (I've some ideas around) in another server but if somebody has suggestions about it I would be very happy to hear it 😀.

Hi,
Will there be support to match arbitrary paths in future versions? I'm staying on 1.4.5 until I can find a workaround..

@Joebayld Yes, that's the plan! Please be careful with 1.4.5 as in cases of routes overlapping it can have issues.

Hello,
Any update on this ? Would be a really nice feature.
Thank you

I've been very busy, if somebody else wants to add the feature I'll be glad to review it.

I'm having an issue with this too, we have paths like this:
/content/stream/:isbn/:path
/content/stream/:isbn/:type/:path
/content/stream/:isbn/:type/:subtype/:path
and we can't match them all, I think the last one ends up failing with 404's and not ever matching, and possibly others too.  We originally just had the latter 2 paths and then definitely the last one was failing, but I had to add the first one as well, and now things are definitely messed up.   Would love to see a fix for this!

Same issue here, I use the following workaround to expose folder and all its subfolders :
private func exposeFolderRecursively(httpServer: HttpServer, folderUrl: URL ){
        let rootLastPathComponent = folderUrl.lastPathComponent
        httpServer[rootLastPathComponent + "/:path"] = shareFilesFromDirectory(folderUrl.path)

        if let enumerator = FileManager.default.enumerator(at: folderUrl, includingPropertiesForKeys: [.isDirectoryKey], options: [.skipsHiddenFiles, .skipsPackageDescendants]) {
            for case let subFolderUrl as URL in enumerator {
                do {
                    let fileAttributes = try subFolderUrl.resourceValues(forKeys:[.isDirectoryKey])
                    if fileAttributes.isDirectory! {
                        if let range = subFolderUrl.path.range(of: rootLastPathComponent){
                            let subPath = subFolderUrl.path[range.lowerBound...]
                            httpServer[subPath + "/:path"] = shareFilesFromDirectory(subFolderUrl.path)
                        }
                    }
                } catch {}
            }
        }
    }