Help request: how to connect to a remote server

Hi,
Do you have a recommendation for connecting to a database file in another machine? Perhaps via SSH? I would like to connect to another machine on my local network.
I have a permanent running job on the remote machine where the file is stored. This job inserts and updates records in several tables.
I would like to run a shorter update job in parallel, from another machine. This shorter job just updates in 2 tables, no inserts, no changes to foreign key values or unique fields. I'm retrieving data from an external API and I would like to circumvent rate limits by sending requests through 2 different IP addresses.
I found this https://stackoverflow.com/questions/58425047/how-to-connect-to-sqlite-database-with-node-js, but is not using better-sqlite3.
I also read this https://stackoverflow.com/questions/8357496/access-sqlite-from-a-remote-server. There are several solutions in this page as well as warnings about Sqlite not being a network database.
What is your recommendation? Would any of the solutions above work? Can it be done, in a scenario where the 2 data streams don't cause conflicts or inconsistencies?
Thanks.

Can it be done, in a scenario where the 2 data streams don't cause conflicts or inconsistencies?

This would be something to ask on the SQLite forums. This is a Node.js library, not the database. better-sqlite3 doesn't make any guarantees on its own beyond what SQLite does. Everything that applies to SQLite in this regard applies to better-sqlit3 and vice versa. My guess is that this is an incredibly bad idea and will perform bad at best.

I would like to circumvent rate limits by sending requests through 2 different IP addresses.

Sounds like using the second machine as a proxy server would be a much more reasonable approach than trying to write to a remote SQLite file.

SQLite is really tuned for single-writer scenarios. When there are multiple simultaneous writers, you can incur bad performance hits. I always recommend writing a "manager" service that has sole write privileges to the database, and all other clients only access the database through that service's API. This works well as long as the API only exposes high-level operations, and doesn't allow clients to keep transactions open while waiting for network traffic. Essentially you are creating a simple client-server architecture with SQLite at it's core. It can work fine for simple situations, but you might also want to consider just using a database that is designed for client-server situations, like PostgreSQL.
I'm closing this because it is not an issue with better-sqlite3 (out of scope).


Preemptively validate configuration

While working on #30, I saw that todoman just passes the raw configparser through the CLI. I think it would be better if there was a dedicated Config type that has all valid params as properties (which raise if somebody tries to set an invalid value).
khal uses ConfigObj for this.

We might want to close this if we merge #59, though that would have to be a mayor release, since it's backwards-incompatible.

agreed


Enquiries about examples/ppi

Hi,
I have a few questions regarding examples/ppi.

Is the implemented architecture from any paper, can you post it here?
preds.append((out > 0).float().cpu()) It can be considered as you use 0 as threshold to convert network output to positive and negative predictions. Is there any explanation about why it is 0 here?

Thanks.

We try to follow the proposed GAT architecture for PPI. We use 0 as threshold because the network output does not integrate a sigmoid function (because we use the more stable BCEWithLogitsLoss as loss op).

I konw there is no a sigmoid function in the output of the model so the out \in R, but in this case, how to define or any hint to set this threshold? Additionally, how to interpret the model output in this case without a sigmoid since its value belongs to R?

The way we train it: - infinity for false labels, and infinity for true ones, so 0 is a reasonable threshold. We could actually search for more better thresholds using ROC curves, but I do not see the necessity here.

Thanks.


Fix the command to generate encryption key in string

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

/cc @gkuga

/approve


Fix issue #327

Comments are now extracted as "begin" and "end" comment tokens by the lexer. The content
of the comment is extracted as a text token.
A new comment node class (of type TwingNodeType.COMMENT) has been added and is
extracted by the parser into the AST. Its compile method does nothing.

@Kocal, can you have a look at this? Comments now transit up through the node tree and it should be possible now to recreate a lossless Twig source from the token stream.

Here is the token list extracted from the following template:
{# foo #}
[ TwingToken { type: 12, value: null, lineno: 1, columnno: 1 },
  TwingToken { type: 0, value: ' foo ', lineno: 1, columnno: 3 },
  TwingToken { type: 13, value: null, lineno: 1, columnno: 8 },
  TwingToken { type: -1, value: null, lineno: 1, columnno: 10 } ]

Coverage remained the same at 100.0% when pulling 6c3f70f60a067382d4dd8546cadbb8745f5589f5 on issue_327 into bedac38035c1d71b7d69e965a695f73f415b30f9 on master.

Nice! :smile:
Just some questions:

TwingLexer.STATE_COMMENT was not needed? Why? Since STATE_BLOCK and STATE_VAR both exist :thinking:
Same for renaming currentVarBlockLine to currentVarBlockCommentLine

Otherwise it looks nice, thanks again! :)

@Kocal, well, comments are very simple to parse. They don't need to maintain a state because there is no logic inside them - the inner of a comment is a text token, there is no alternative. The verbatim tag doesn't need a state either for example because it consists of a text token.
Now that I think about it, there is no START/END token for the verbatim tag. So you would not be able to recreate a template source from the AST without loosing the verbatim tags! Let me open an issue foir this one too.

May you discover other tokens missing that would make recreating a source from the AST lossy, don't hesitate to open issues.

because there is no logic inside them
Ah yes, it makes sens when you say it 😋

So you would not be able to recreate a template source from the AST without loosing the verbatim tags!
Yup! But I'm really far to prettify verbatim tags, so we still have time before fixing this issue :)


TODO: add "click outside" support

If a user clicks outside of the dropdown when it's open, the dropdown should close.

Added in #30


Wrong repeating update ???

Hello, im using app-sync now on few apps and just got wrong update repeatly.
after calling appSettings.clear(), the app will notify to exit/restart to update again.
is this the bug ?? or i have to avoid to call  appSettings.clear() ??
thank you

Hi, good observation. The plugin needs to remember the current hash (version) it's running and that's stored in appsettings. Can you confirm this doesn't occur without blindly deleting everything in appsettings? Perhaps we can figure out a good way to work around this issue.


TableGen configuration is not compatible with cross-compiling the IREE compiler

I found this while compiling the IREE compiler through Emscripten to WebAssembly (see notes).
When cross-compiling the IREE compiler, there is no way to specify a host version of iree-tablegen, in the same way that we specify a host version of iree-translate and other tools when cross-compiling the IREE runtime. LLVM provides a -DLLVM_TABLEGEN cmake option, documented here: https://llvm.org/docs/HowToCrossCompileLLVM.html. In the case of WebAssembly cross-compilation, our current setup attempts to run the js/wasm version of iree-tblgen through node, which fails.
We should revisit this:
https://github.com/google/iree/blob/68c27a08f42ba64d566f7a6e4816550f6e0f57ae/build_tools/cmake/iree_copts.cmake#L449-L452
either using our IREE-specific IREE_HOST_BINARY_ROOT or using LLVM's add_tablegen

A few more cases of this popped up since I last looked:
https://github.com/google/iree/blob/2322a1694d8800a86c319a3b158901f8ec3e5147/llvm-external-projects/iree-dialects/CMakeLists.txt#L42-L45
https://github.com/tensorflow/mlir-hlo/blob/1b2588b24e309d0503bcb02c58fab5445f8c3046/CMakeLists.txt#L69
I'm not quite sure what the right setup is, but https://github.com/llvm/llvm-project/blob/main/llvm/cmake/modules/TableGen.cmake is generally structured to support cross compilation.

Perhaps a duplicate of #4662?

Perhaps a duplicate of #4662?

Eh, related but I'd say no. That issue is more broad, while this issue has a specific scenario that is broken.

We should revisit this:
https://github.com/google/iree/blob/68c27a08f42ba64d566f7a6e4816550f6e0f57ae/build_tools/cmake/iree_copts.cmake#L449-L452
either using our IREE-specific IREE_HOST_BINARY_ROOT or using LLVM's add_tablegen

In case that using LLVM‘s add_tablegen is acceptable I could come up with a fix. I don‘t know if I can promise the same when using IREE_HOST_BINARY_ROOT (this would probably take longer for me).


Update input.rst

Added example for returning the entire input stream.

That particular piece of documentation is meant only to demonstrate that the method works the same as post() and get(). Other than that, you shouldn't really need to use xss_clean with it and your example indirectly encourages that.
If you want to add an example about fetching the entire (decoded) stream, you can add to the method description in the class reference, but please omit the second parameter.


Add a way to easily created a k8s "cluster"

I kind of would rather this be separate from this repo.  For example, we already have a docker-compose-kubernetes repo that brings up a local cluster and I'd rather we collectively use and support that repo since it is one of our recommended "try out Calico on k8s" options.  I'm not a huge fan of sticking a bunch of scripting inside of the makefile to spin up Kubernetes, especially when we have other code which already does it.
That said, it is a pretty isolated change so I can't really complain too much...

Discussed offline and agreed it's useful so merging.


Image 20200621.1 is missing .Net Core 2.2

As of the update from build image 20200614.1 to 20200621.1 our .Net Core 2.2 applications are failing to build due to the missing SDK. The updated documentation also shows it missing vs what master shows.
Side question: is there any way to force our pipelines to use a specific build image version? I tried changing the vmImage from ubuntu-18.04 to ubuntu-18.04:20200614.1 but that doesn't work and I don't see any documentation on this subject.

Looks to be from #1016

I've implemented a workaround of installing 2.2 SDK as part of the build pipeline. Would still be nice to know if we could target specific build image versions, but this will work for now. Closing issue.


Add MaryTTS platform

Description:
Based on the Yandex TTS code.
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#2397
Example entry for configuration.yaml (if applicable):
tts:
  - platform: marytts
    marytts_host: 'localhost'
    marytts_port: '59125'

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

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

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

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

If the code does not interact with devices:

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

Hi @johanpalmqvist,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

⚡


[WIP] 🚀 feat: リポジトリ詳細画面の各アイテムタップでブラウザ開いたり画像をプレビュー表示したりする

残件

iOS, Web, macOS で動作確認

Issue #132

Codecov Report

Merging #134 (80e73e9) into develop (230f739) will decrease coverage by 0.06%.
The diff coverage is 99.09%.

@@             Coverage Diff             @@
##           develop     #134      +/-   ##
===========================================
- Coverage    99.52%   99.45%   -0.07%
===========================================
  Files           44       47       +3
  Lines          840      925      +85
===========================================
+ Hits           836      920      +84
- Misses           4        5       +1

Flag
Coverage Δ

unittests
99.45% <99.09%> (-0.07%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

lib/entities/owner/owner.dart
100.00% <ø> (ø)

lib/entities/repo/repo.dart
100.00% <ø> (ø)

lib/utils/url_launcher.dart
88.88% <88.88%> (ø)

lib/entities/owner/owner.g.dart
100.00% <100.00%> (ø)

lib/entities/owner/owner_data.dart
100.00% <100.00%> (ø)

lib/entities/repo/repo.g.dart
100.00% <100.00%> (ø)

lib/entities/repo/repo_data.dart
100.00% <100.00%> (ø)

...presentation/components/common/hyperlink_text.dart
100.00% <100.00%> (ø)

lib/presentation/components/common/icon_label.dart
100.00% <100.00%> (ø)

...ntation/components/common/preview_avatar_view.dart
100.00% <100.00%> (ø)

... and 2 more

Continue to review full report at Codecov.

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


chore: Add meta info to plugin

Prerequisites checklist

[x] I have read the contributing guidelines.

What is the purpose of this pull request?
Add meta info to the plugin
What changes did you make? (Give an overview)

added meta object to the plugin
updated release-please-config.json to update src/index.js with the correct version number
removed release-as from release-please-config.json

Related Issues

Is there anything you'd like reviewers to focus on?

Not sure what the problem is with Node.js v22. Hopefully just a transient.

Just one more thing - this looks like something we'd want to release, so perhaps it should be tagged as feat?

Good call. :+1:


Is it possible to connect to SAMP servers?

Is it possible to connect to SAMP servers?

No, the project uses it's own network protocol.

you can use raknet to connect to SAMP servers, but the problem will be with client authorization because the server will also reset the connection

it's not only connecting to server, you need to implement their protocol to, among other things, synchronize network objects ...


Cocoapods integration

I am trying to use this with XCode 6.2 and Cocoapods 0.36.0 with no success, any idea how to make this works, I am importing the using
import ZHSwiftLogger
but the methods are not detected.

Ok, the answer is here https://developer.apple.com/library/ios/documentation/Swift/Conceptual/Swift_Programming_Language/AccessControl.html#//apple_ref/doc/uid/TP40014097-CH41-ID7, all elements has a internal visibility, we need to explicitly specify to be pubilc.

@chrux Hi chrux, all of these methods are exposed to the whole project using it. If you want to use import ZHSwiftLogger
Then I think git submodule will be for this.
For the cocoa pods integration, I will add a spec as soon as I can, possibly by Friday.
If you like, you can help me to create one, make a PR, :)

@chrux Seems like the pod spec file cannot pass the validation of pod lint, for now, if you like, just drag the file into the project. I'll fix it later

@chrux I'm

@chrux Hey, ZHSwiftLogger has been renamed to Loggerithm, which is also CocoaPod supported. Please check README. Thanks!

@chrux Now you can use pod 'Loggerithm', '~> 1.2'

thanks @honghaoz


The coreml model option does not work properly

The coreml model option does not work properly，Click run inference No invalid！

The Core ML model is working fine. It's just the option to inference the model solely using Core ML that is still work in progress because of problems with the output. If you want to use the Core ML model you can use the Vision framework.

The Core ML model is working fine. It's just the option to inference the model solely using Core ML that is still work in progress because of problems with the output. If you want to use the Core ML model you can use the Vision framework.

Consider calling up a real-time segmentation version of the video header?

No, while some YOLOv8 variants in combination with frameworks like Vision may be suitable to perform real-time segmentation the post-processing in this repo would be way to slow. If you want to perform real-time segmentation you would rely on performing the post-processing part on the GPU using Metal.

No, while some YOLOv8 variants in combination with frameworks like Vision may be suitable to perform real-time segmentation the post-processing in this repo would be way to slow. If you want to perform real-time segmentation you would rely on performing the post-processing part on the GPU using Metal.

Can I get a real-time split?

Split of what?

Split of what?

Split image content in real time using mobile phone cameras

No, this project is just an example on how to perform instance segmentation using YOLOv8 with various mobile inference frameworks on iOS.


Update 11-Container-With-Most-Water.rs

File(s) Modified: 11-Container-With-Most-Water.rs
Language(s) Used: rust
Submission URL: https://leetcode.com/submissions/detail/827530282/

Again accidentally 2 files changed in this branch. Don't know why this keeps happening. This is just my lack of knowledge of git & github.


deps: update to ics23 0.11.3

Describe your changes
Updates to ics23 0.11.3
Issue ticket number and link
Checklist before requesting a review

[x] If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

No effect on consensus state as no IBC transactions have occurred and no changes in library other than bug fixes.

Are transitive dependencies such as ibc-types on ics23 a concern here?

There's only one version of the ics23 crate in the workspace, and we can see from the lock file that it's set to the version we want. Cargo unifies compatible dependencies. This can also be verified using cargo tree -i ics23.

If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

awesome


Force string into array

I have a 'select2' form field and want to be able to use it as a select box. However, it's for telescope, and telescope requires an array for this particular field, what's the best way to transform the result into an array (e.g. if the result is "string", turn it into ["string"] before it's validated.

You can set the onSubmit hook using AutoForm.hooks() and modify the document before it is submitted

Thanks, I did as you suggested. I actually tried that before, but forgot to add the file responsible to packages.js.
sigh


comment console. log call to fix IE 11 bug

Fixes an Internet explorer bug where console causes failure of JS scripts if the developer console is closed.
Reference:
http://stackoverflow.com/questions/7742781/why-does-javascript-only-work-after-opening-developer-tools-in-ie-once

Solved, THX!


Replace RISParser by rispy

This PR updates the deprecated RISParser library to rispy. This will resolve issues with Rayyan files when https://github.com/MrTango/rispy/pull/25 will be merged and released.
This PR is part of issue https://github.com/asreview/asreview/issues/348.

This is a bit of an issue now https://github.com/MrTango/rispy/pull/16.

This merge adds support for Rayyan RIS export files as well.


This link in database track doesnt work anymore

https://pythonhosted.org/Flask-SQLAlchemy/quickstart.html flasksql alchemy not working

This should be resolved now to http://flask-sqlalchemy.pocoo.org/2.1/quickstart/ - can you confirm?

@JonHMChan Thank you. It's working nice now


Ctrl + S doesn't seem to be working

For me, Ctrl + S doesn't work, though F1 - Save As works as expected.
I am on Ubuntu 14.04 using the latest master branch.
At first I thought this was due to my terminal (Gnome Terminator) or shell (Zsh), but I then tested it with the stock ubuntu terminal too. No luck.
I guess this is related to Ctrl + Q. Since Ctrl + S is suspend mode, right?

Yep, you're totally right. Ctrl+S doesn't work on terminals that use it for suspend. I had to disable that feature on my terminal.
I have found a fix for it, but I need to test it out before pushing to master.
I'll push the fix to the dev branch soon.
Thanks for the report! :+1:

Hi, good news!
I changed the curses terminal mode in the Suplemon UI from raw to cbreak. That should disable special terminal keys. I tested it on my Ubuntu virtual machine, and seems like it works fine. Could you test the dev branch to verify it works? I would really appreciate it :+1:
Thanks!

Congratulations! It seems to be working fine now. Thanks again for making such a nice tool.

No problem, nice to hear you like it!


fix cannot override the addon values using customized variable

issue: https://issues.redhat.com/browse/ACM-14178

/lgtm


Failing test for Boolean

It seems that there are missing asserts in this line and the next: https://github.com/scipr-lab/zexe/blob/14445938364f7ee97f42dfe7eaa1393f1f0b87c1/snark-gadgets/src/bits/boolean.rs#L1797, which causes test compilation to fail.
Does this change make sense?
-            Boolean::enforce_nand(&mut cs, &[Boolean::constant(false)]).is_ok();
-            Boolean::enforce_nand(&mut cs, &[Boolean::constant(true)]).is_err();
+            assert!(Boolean::enforce_nand(&mut cs, &[Boolean::constant(false)]).is_ok());
+            assert!(Boolean::enforce_nand(&mut cs, &[Boolean::constant(true)]).is_err());

Thanks, I believe https://github.com/scipr-lab/zexe/pull/15 should fix this?

Yep, that's great! Thanks!
On Fri, Aug 9, 2019 at 6:58 AM Pratyush Mishra<EMAIL_ADDRESS>wrote:

Thanks, I believe #15 https://github.com/scipr-lab/zexe/pull/15 should
fix this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/scipr-lab/zexe/issues/5?email_source=notifications&email_token=AA23MGFEYFJN3L3WXQOGR2LQDTTOXA5CNFSM4HRTPHUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD35QPPQ#issuecomment-519767998,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA23MGFXV4FCQDY6VDKVTODQDTTOXANCNFSM4HRTPHUA
.


Update Profile Bucket Validation Code To Account For Custom S3 Endpoint

Change Overview
This PR updates the validate.ProfileBucket() method to use custom S3 endpoint, if provided, for its validation steps. Without this change, stow will default back to using the s3.<region>.amazonaws.com domain, even though the custom endpoint is provided.
Pull request type
Please check the type of change your PR introduces:

[ ] :construction: Work in Progress
[ ] :rainbow: Refactoring (no functional changes, no api changes)
[ ] :hamster: Trivial/Minor
[x] :bug: Bugfix
[ ] :sunflower: Feature
[ ] :world_map: Documentation
[ ] :robot: Test

Issues

fixes #1590

Test Plan
Use the latest kanctl CLI to reproduce the issue:
$ kanctl create profile s3compliant --access-key "test" --secret-key "test" --endpoint https://s3.cern.ch/  --bucket my-bucket --region cern --namespace default --verbose

The validation code ignores the s3.cern.ch endpoint:
secret 's3-secret-ggiorh' created
Failed the 'Validate bucket region specified in profile' check.. ❌
validation failed, deleting secret 's3-secret-ggiorh'
secret 's3-secret-ggiorh' deleted
Error: profile validation failed: failed to get bucket my-bucket: GetBucketLocation: RequestError: send request failed
caused by: Get "https://s3.cern.amazonaws.com/my-bucket?location=": dial tcp: lookup s3.cern.amazonaws.com on <IP_ADDRESS>:53: no such host

Run kanctl with this change:
go run ./cmd/kanctl create profile s3compliant --access-key "test" --secret-key "test" --endpoint https://s3.cern.ch/  --bucket my-buclet --region cern --namespace default --verbose

The right endpoint is used:
secret 's3-secret-ijj2lv' created
Failed to obtain reader, failed to marshal fields to JSON, json: unsupported type: func(time.Duration)
Failed the 'Validate bucket region specified in profile' check.. ❌
validation failed, deleting secret 's3-secret-ijj2lv'
secret 's3-secret-ijj2lv' deleted
Error: profile validation failed: failed to get bucket my-bucket: GetBucketLocation: InvalidAccessKeyId:
        status code: 403, request id: tx000000000000049299681-00631bb733-2af9b497-default, host id:
{"File":"pkg/kanctl/kanctl.go","Function":"github.com/kanisterio/kanister/pkg/kanctl.Execute","Line":48,"error":"profile validation failed: failed to get bucket my-bucket: GetBucketLocation: InvalidAccessKeyId: \n\tstatus code: 403, request id: tx000000000000049299681-00631bb733-2af9b497-default, host id: ","level":"info","msg":"Kanctl failed to execute","time":"2022-09-09T14:59:15.597305194-07:00"}
exit status 1

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

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test


RC2 cleanups

What are you trying to accomplish?

Make TestHelpers#rendered_content public per https://github.com/ViewComponent/view_component/issues/1629#issuecomment-1411863454.
BREAKING: Rename SlotV2 to Slot and SlotableV2 to Slotable.

(The PVC failure is expected and will require a quick rename of the Slots class references)


Include exports dir in ceph-nfs config file

Exports dir is used when dynamic exports creation is enabled.

@leseb done


Better migration guide from Redux

https://effector.now.sh/en/recipes/migrating-to-effector/from-redux

IssueHunt Summary

Backers (Total: $40.00)

 issuehunt ($40.00)

Become a backer now!
Or submit a pull request to get the deposits!
Tips

Checkout the Issuehunt explorer to discover more funded issues.
Need some help from other developers? Add your repositories on IssueHunt to raise funds.

IssueHunt has been backed by the following sponsors. Become a sponsor

@goodmind start working on this

@Laiff are you still working on this?


[feat] Add projects list

Describe the solution you'd like
The project list will be "opt-in" for specific github repos. Along with automatically including the pinned projects from github's profile.
The general layout should follow a similar layout 4 main "cards" and then a table
list of other projects.
note unlike the index, there should be custom data provided via props.

This will also include the previous "static" files that were available/added in the old portfolio.


Rework markup link rendering

Fixes #26548
This PR refactors the rendering of markup links. The old code uses strings.Replace to change some urls while the new code uses more context to decide which link should be generated.
The added tests should ensure the same output for the old and new behaviour (besides the bug).
We may need to refactor the rendering a bit more to make it clear how the different helper methods render the input string. There are lots of options (resolve links / images / mentions / git hashes / emojis / ...) but you don't really know what helper uses which options. For example, we currently support images in the user description which should not be allowed I think:

Profile
https://try.gitea.io/KN4CK3R

Thank you very much for your work. I remember another bug that may be relevant to this PR, maybe it can be fixed together.
Bug https://github.com/go-gitea/gitea/issues/25632
Related https://github.com/go-gitea/gitea/issues/15075

By tested locally, overall LGTM, but  I need some time to understand the change

Resolve a conflict caused by my PR 67bc21d2e87f82df29582e4d073842b7adeb780a

It has been stable for long time. I will do some work (new PRs) without considering conflict with these changes ......

I was unable to create a backport for 1.21. @KN4CK3R, please send one manually. :tea:
go run ./contrib/backport 26745
...  // fix git conflicts if any
go run ./contrib/backport --continue


More detailed information about target path

There is no information as to whether an existing relative path must be specified for the target path parameter or whether a non-existent (relative) directory or tree  is created automatically.
In general, one would wish that the path logic for uploaded and downloaded artifacts was described in more detail. The examples alone are not enough.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 861ce7a5-4fa4-55f1-2c97-46a9cc6a2f66
Version Independent ID: bdf954b9-9bbe-8b34-b674-71ad8153519d
Content: Publish and download artifacts in your pipeline - Azure Pipelines
Content Source: docs/pipelines/artifacts/pipeline-artifacts.md
Service: azure-devops-pipelines
Sub-service: azure-devops-pipelines-artifacts
GitHub Login: @ramiMSFT
Microsoft Alias: rabououn

@dbyte Thanks for the feedback! I'm adding clarifications shortly


Improve information tags in Publisher

Describe your problem(s)

The following (per resource security enable/disable option) is confusing what happens when disabled. It removes all application level securities I believe.

The following(Application level security in Runtime configurations) mentions about a mutual SSL. Which is a transport level security.

Describe your solution

How will you implement it

Optional Fields
Related Issues:

Suggested Labels:

3.1.0 publisher
Suggested Assignees:

+1 yes we need to revise the help text.


ICE functionality and datachannels

The current code lets you get the ice candidate string to send to the client but not the sdpmid or sdpmlineindex values. I can't see a way of pushing an ICE candidate into the peer connection object from the client which is needed for ice negotiation.
 There is this https://github.com/RainwayApp/spitfire which has done basically all of the work already, should just be a case of copying/ pasting the relevant interfaces. I'd do it but i'm not really a c++ guy and don't have a build system for the webrtc project.

 There is this https://github.com/RainwayApp/spitfire which has done basically all of the work already, should just be a case of copying/ pasting the relevant interfaces. I'd do it but i'm not really a c++ guy and don't have a build system for the webrtc project.

You cannot just copy and paste the implementation. A language binding is all about interfaces, and the libraries have obviously different interfaces because they are written by different people. It is not possible to integrate them.

ok, it's a start though, i'll look into it.

I've looked into it. It's much more complicated than I was imagining. I've sorted out the ICE stuff but the data channel integration is beyond me. Adding a data channel on the client actually crashes the application by the way. If you added data channels to this it'd be the only proper cross platform solution for webrtc. Is there really no chance of that happening?

Don't worry about it, got it sorted out


Exclude compiler/tiered/Level2RecompilationTest.java

Signed-off-by: Simon Rushton<EMAIL_ADDRESS>

Ref: https://github.com/adoptium/aqa-tests/issues/2671

Test runs with this PR:
jdk8
x86_windows: https://ci.adoptopenjdk.net/job/Grinder/994/
arm_linux: https://ci.adoptopenjdk.net/job/Grinder/993/
ppc64_aix: https://ci.adoptopenjdk.net/job/Grinder/992/
ppcle64_linux: https://ci.adoptopenjdk.net/job/Grinder/988/
jdk11
x86_windows: https://ci.adoptopenjdk.net/job/Grinder/991/
There are failures in the jdk8 test runs but they are from tests not excluded by this PR>


Fixed pip package name

The original command installs the azure-storage-blob package, which if you run the example will end up with an ImportError: No module named queue.
I believe the intent was to include the azure-storage-queue package, with which the code runs fine.

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


compatibility issue when migrating to androidx

This code stop working on devices below 25 when I migrate to androidx recently.
Device info: Sony xperia M5 - Android 6.0.0
Those code block
import android.support.v13.view.inputmethod.EditorInfoCompat;
import android.support.v13.view.inputmethod.InputConnectionCompat;
import android.support.v13.view.inputmethod.InputContentInfoCompat;

are replaced with
import androidx.core.view.inputmethod.EditorInfoCompat;
import androidx.core.view.inputmethod.InputConnectionCompat;
import androidx.core.view.inputmethod.InputContentInfoCompat;

Is it androidx issue?
Thanks,

I was also banging my head on wall trying to understand what I was doing wrong in my production app. Seems like with androidx, below Android 8 shows this Toast.


build.sh will run sh cli tests

Added invoking of shell integration tests to test Pharo Launcher CLI
fixes #20

should be working now.

Thanks for this work @Bajger .
If you take a look at https://github.com/PharoLauncherCmdLine/CommandLineLauncher/blob/dev/script/pharo-launcher.sh, you will see that the script is very different than the one in this branch. It is very closed to zero-conf script (using get.pharo.org/xx). It is the script that will be delivered and I think it is good to keep it as it is.
Also, there is a problem for testing as the folder layout is not the same as the one when pharo launcher is installed.
As we are doing functional testing (black box) of pharo launcher command line, I would not update the script to manage the test case (not the instructions that will be used by final users) but I would rather create an environment that is almost the same as in production, and use pharo-launcher.shas in production. It means, on linux:

create a directory  named shared with a copy of the launcher image (to remove after tests)
copy pharo-launcher.sh script aside the pharo-vm directory

WDYT?

@demarey: Hi Christophe, thanks for your insight! One of my concern was that I didn't like a fact that pharo-launcher.sh is dependent on directory where user currently operates. There has to be exact directory set, otherwise it won't work. So when users would use Launcher CLI, then they need to set directory first in order to use it. For me, it is usability concern. (why to limit users to be in given directory?)
Anyway, I'll try to use your approach (with copying image and script) and let you know then.
Question: Is pharo-launcher.sh that is put aside to vm executable a deployment artefact? Or it should be removed after test as well?
Maybe I'm a bit lost with each phase (before creating deployment artefacts/package and and after that)

One of my concern was that I didn't like a fact that pharo-launcher.sh is dependent on directory where user currently operates.

 That's why https://github.com/PharoLauncherCmdLine/CommandLineLauncher/blob/dev/script/pharo-launcher.sh is only bound to the location where Pharo Launcher is installed. Then, you add pharo-launcher.sh directory to your PATH and you can use it from any location.
pharo-launcher.sh is not meant to be moved at any place in the system.
pharo-launcher.sh is copied in the packaging step of the build. You can see it at https://github.com/PharoLauncherCmdLine/CommandLineLauncher/blob/dev/build.sh#L71
What I suggested to do not pollute the workspace when testing is to copy everything you need in a folder and drop it after testing (probably only the vm and the script).

@demarey: Fixed how pharo launcher script should be called based on your recommendations. There is just one detail:
pharo-launcher.sh is expected to be in root dir (where repo is cloned).
Tests are now failing, but it is problem of kill command (created separate issue #22 ), in general mechanism of calling from build.sh should be fixed now.
Reprosteps are:
gh repo clone PharoLauncherCmdLine/CommandLineLauncher
cd CommandLineLauncher
git checkout 20-Extend-CI-to-run-shell-unit-tests-testing-CLI-commands
PHARO=80 ARCHITECTURE=64 ./build.sh prepare
PHARO=80 ARCHITECTURE=64 ./build.sh test

I think PR can be closed now


multi echartsLayer conflict

When add multi echartsLayer to map, only the last one can be seen.

maybe ID in code,it sets id in div created


Cannot add attachment to issue without admin access

Description
I have an issue created by User A.
I try to add an attachment via API for user B. User B is in a Team with write permissions for issues (and everything else)
When I do an sudo upload for user B i get the error:

user should have permission to write issue

But the user has the permission. When I login as user B and do it via the web interface everything works fine.
It only works via API when I give the team admin access.
Gitea Version
1.20.0+dev-919-gf9cfd6ce5
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
docker
Database
MySQL

Which endpoint are you using?

Maybe related #25019

The endpoint is: POST /repos/{owner}/{repo}/issues/{index}/assets

Could you update the the latest version and try it again since #24767 merged.

No the error still occurs in Version: 1.20.0+dev-1002-g379ec1303


Illegal invocation using patched XMLHttpRequest

I've recently updated a React Native app that uses Zone.js to manager its database transactions and, in doing so, encountered an illegal invocation exception when calling fetch.  The exception is thrown from the scheduleTask function within patchXHR of zone.js.  Specifically, the call to oriAddListener.call(target, READY_STATE_CHANGE, newListener);
I've done my best to diagnose the problem but I can't see it.
I'm using Zone.js 0.9.0 with React Native 0.59 and debugging the application using Chrome 73.0.3683.86 (Official Build) (64-bit) on Ubuntu 16.04.6 4.15.0-46-generic x86_64.

Could you provide a reproduce repo? Thanks

Is that the most useful thing I can do?  To reproduce it from code, you're going to need a JDK installation and an Android device or emulator to hand.  If you have those things, it's enough to react-native init  TestApp, npm i zone.js, import 'zone.js' in index.js and make a call to fetch.
In other news, FileReader is also broken.  Am I doing something dumb?  How should I import Zone.js in a React Native application?

I never tried using zone.js in react native, and I don't think you did any thing wrong, the most possible reason is in react native, the webview has different implementation vs normal browser. So if you can provide a very basic repo to reproduce fetch and FileReader issue, so I don't need to begin to learn how to setup react native 101. Thanks!

OK, I've created a repo at https://github.com/sdc395/react-native-zones.git.
I had no problems using Zone.js with React Native 0.56.  The sooner Zones becomes a standard part of JavaScript the better.  :-)

Thanks, I will look into it.

@sdc395, it seems react native implement it's own EventTarget and XMLHttpRequest, and it is inside Worker, so the patch become a little weird, so in your use case, you want to use zone to control XMLHttpRequest and FileReader?

At the moment, I'm only knowingly using Zone.js to make database transaction objects available to asynchronous functions that need database access.
Perhaps I can disable the Zone.js patches I don't need.  I had set __Zone_disable_XHR = true.  Do I need to set __Zone_disable_EventTarget = true also?  Could you clarify the steps?
Thanks for your help with this issue.

@sdc395, yes, you are right, the walk around is,

create a env.js in the root.

if (typeof global !== 'undefined') {
  global['__Zone_disable_XHR'] = true;
  global['__Zone_disable_EventTarget'] = true;
}

in index.js, before import zone.js,

/**
 * @format
 */
import './env';
import 'zone.js';
import {AppRegistry} from 'react-native';
import App from './App';
import {name as appName} from './app.json';

AppRegistry.registerComponent(appName, () => App);

And everything should work fine.

That has done the trick, although I've only needed to disable EventTarget patching (so far).  Thanks so much.
Will full, on-going support for React Native be available in the future?  I'm building my mobile app's database access around Zone.js and I'd hate to have to rip that out post-launch.

I have issue with version 0.9.0 too. I've recently updated all packages in project and Angular to version 7.2.13. Core-js is on version 3.0.1. After every request, zone.js throw this error: TypeError: Cannot read property 'call' of undefined at ZoneTask.scheduleTask [as scheduleFn].
Call of undefined is on this line: oriAddListener.call(target, READY_STATE_CHANGE, newListener);
We work with LG smart TV with webOS version 3.8.0 (latest LG update).
Here is stacktrace:
"TypeError: Cannot read property 'call' of undefined     at ZoneTask.scheduleTask [as scheduleFn] (file:///media/developer/apps/usr/palm/applications/app/dist/polyfills.js:12611:27)     at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.scheduleTask (file:///media/developer/apps/usr/palm/applications/app/dist/polyfills.js:9688:26)     at Object.push../node_modules/zone.js/dist/zone.js.DELEGATE_ZS.onScheduleTask (file:///media/developer/apps/usr/palm/applications/app/dist/polyfills.js:9579:29)     at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.scheduleTask (file:///media/developer/apps/usr/palm/applications/app/dist/polyfills.js:9682:51)     at Zone.push../node_modules/zone.js/dist/zone.js.Zone.scheduleTask (file:///media/developer/apps/usr/palm/applications/app/dist/polyfills.js:9516:43)     at Zone.push../node_modules/zone.js/dist/zone.js.Zone.scheduleMacroTask (file:///media/developer/apps/usr/palm/applications/app/dist/polyfills.js:9539:25)     at scheduleMacroTaskWithCurrentZone (file:///media/developer/apps/usr/palm/applications/app/dist/polyfills.js:10472:25)     at file:///media/developer/apps/usr/palm/applications/app/dist/polyfills.js:12649:28     at proto.(anonymous function) [as send] (file:///media/developer/apps/usr/palm/applications/app/dist/polyfills.js:10796:24)     at Observable._subscribe (file:///media/developer/apps/usr/palm/applications/app/dist/main.js:8049:17)"
After downgrading to zone.js version 0.8.29, application works

@JiaLiPassion - it looks like Googlebot does not like Zone.js 0.9.0 either: https://github.com/angular/angular/issues/30203

@petebacondarwin, got it, I will check it, thanks!

I will close this one because https://github.com/angular/angular/issues/30203 has been fixed.


Supports %checks modifier on class methods

Proposal
Allow the use of the %checks modifier on class methods.
Use case
A big example is the lodash flow-typed file. Function such as isNil are defined like this:
declare class Lodash {
    isNil(value: any): boolean
}

New feature would allow the following:
declare class Lodash {
    isNil(value: any): boolean %checks (value != null);
}

Right now, the use of this method does not allows flow to know that the checked value is not null:
const test: ?React$Element<any> = window.document.getElementById('test')
if (!isNil(test)) {
   return ReactDOM.createPortal(test, this.containerEl) // Throw flow error about test being undefined
}

https://github.com/facebook/flow/pull/7735

Nice! Sorry, I missed it while searching for existing issue.

Not sure if declare class would work, only tested regular class

@telaoumatenyanis added your lodash example to tests

Closing this since we only plan to support this for type guard


Feature: extra space to the image, allows to pan further from the sides (like PAN_LIMIT_CENTER but customizable).

Possibility to pan image further from the side.
Behaves as PAN_LIMIT_CENTER but with customizable distance per side.
Why is this needed:
If your have panels above the image, part of it gets inaccessible.
To handle this problem we can add extra space and allow image to be panned further.
Particularly usable for interactive building plans.

I don't plan to merge this but I'll leave the PR open so others can use this branch.


about page content addition

add above:
Warning
*Please note, this website is an experiment that uses a very large data set of images.  This may affect your experience of it, due to your connectivity or the browser you use, and therefore it may not load properly.
We advise you experience it on a desktop machine using the latest version of Chrome.

fixed d780496


Periodic 'Refresh all feeds in background'

Use Case
I prefer to use the Fever API integration + Press (Android) to consume my RSS feeds.
When launching Press on my phone, I want feeds to be readily available, i.e.,  sync the articles miniflux has already cached to my phone.
Note that this is orthogonal to #94 where a feature for initiating feed refresh from the client is requested.
Feature Request

Provide an option to configure periodic refresh of all feeds
Provide means to set default feed polling interval
Provide option to override feed polling interval (some sites impose rate limits)

I assumed periodic refreshs are already supported given this config setting:
‘‘‘
POLLING_FREQUENCY: Refresh interval in minutes for feeds (default=60)
‘‘‘

Feeds are refreshed every hours in the background by default after the process start. You can see that by enabling the debug mode.


Typo "Azure Pipeline"→"Azure Pipelines"

https://docs.microsoft.com/en-us/azure/devops/release-notes/2019/sprint-157-update
#PingMSFTDocs

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

Looks good (refers to the Azure service, and not to an instance); merging. Thanks @hyoshioka0128.


Update cats-effect, cats-effect-laws to 2.5.0

Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-laws

from 2.1.4 to 2.5.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Migrations

github:typelevel/cats-effect/v2_4_0?sha=v2.4.0

Documentation:

https://github.com/typelevel/cats-effect/blob/v2.4.0/scalafix/README.md

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

labels: library-update, semver-minor, scalafix-migrations

Superseded by #147.


[type-safe] New port.

[debug-assert] Added as it is a dependency.

What does your PR fix? Fixes #10804 (currently closed without resolution)

Which triplets are supported/not supported? All triplets should be supported.

Have you updated the CI baseline? No, the build should pass everywhere so the default should do.

Does your PR follow the maintainer guide? Yes, except adding an additional port to the same pull request.

LGTM.
Phoebe is OOF and I took over this PR.

LGTM.
Phoebe is OOF and I took over this PR.


Dockerize production environment | closes #14

Error w/ container. Site continues to display 404 error

docker-compose.yml file missing Traefik network information

container is not registering w/ Traefik


Add comparsion to tinylog

Thank you for spending energy to a modern logging framework.
At https://github.com/jstachio/rainbowgum?tab=readme-ov-file#comparison-to-other-frameworks, I miss a comparison to tinylog2, which also has similar goals (IMHO).

Tagging @pmwmedia to keep me honest and for corrections:
Yes I saw tinylog a long time ago as 1.0 and I forgot to add it to the list. Great library!
For now the major difference is tinylog like its name focuses on being "tiny" and rainbowgum is focused on being "small" in core and modular as well as exploiting as much of modern JDK offerings.
Rainbow Gum also focuses on having faster initialization, strong programmatic options for configuration and doing various optimizations because of invariants as well as static code generation (annotation processor).
For example the programmatic configuration for Tinylog is filling a Map<String,String> with not-javadoc-ed properties. They should have those properties as public static constants somewhere at the minimum but even then it is not type-safe like Rainbow Gums builders. Tinylog's requirement of config is Map<String,String> where as Rainbow Gums is Function<String,String>. The former allows somewhat easier config as you can look at all the keys but the latter can be used with more config systems perhaps with 1000s of keys.
Tinylog is less componetized and like logback prefers inheritance and large classes to do multiple things which is the case with its Writers. There are pros and cons to this approach.
Rainbow Gum's builders and composition over inheritance come at a cost of more classes and is most likely why its core is bigger than all of Tinylog (which massive kudos for tinylog on that). Just to give an example. Say there is a composite like component that has a list of tinylog writers. The natural solution would be to have that as one class that always iterates over that list. Rainbow Gum does not do that. It has "single" version that will not iterate over a list and this is resolved through static factory methods. Again this is why rainbow gum is bigger because it has more implementations of these components where something like logback and tinylog would only have one implementation and rely on the JIT to make the eventual optimization.
An example of eager optimization in terms of loggers is best to use tinylogs custom logging api example: https://tinylog.org/v2/extending/#custom-logging-api
Tinylog recommends this:
package org.tinylog.example;

import org.tinylog.Level;
import org.tinylog.provider.LoggingProvider;
import org.tinylog.provider.ProviderRegistry;

public class MyLogger {

    private static final LoggingProvider provider = ProviderRegistry.getLoggingProvider();

    private static final int minimumLevel = provider.getMinimumLevel(null).ordinal();
    private static final boolean infoEnabled = minimumLevel <= Level.INFO.ordinal();
    private static final boolean errorEnabled = minimumLevel <= Level.ERROR.ordinal();

    public static void info(String message) {
        if (infoEnabled) {
            provider.log(2, null, Level.INFO, null, null, message);
        }
    }

    public static void error(Throwable exception) {
        if (errorEnabled) {
            provider.log(2, null, Level.ERROR, exception, null, null);
        }
    }

}

Rainbow Gum on the other hand literally has a class for each level such that the error logger is literally:
    public static void info(String message) {
    }

    public static void error(Throwable exception) {
        provider.log(2, null, Level.ERROR, exception, null, null);
    }

While the above doesn't actual exist in Rainbow Gum because static method logging is not common so its best to compare the SLF4J logger implemntations:
That is compare:
https://github.com/tinylog-org/tinylog/blob/v2.7/slf4j-tinylog/src/main/java/org/tinylog/slf4j/ModernTinylogLogger.java
https://github.com/jstachio/rainbowgum/blob/main/rainbowgum-slf4j/src/main/java/io/jstach/rainbowgum/slf4j/LevelLogger.java
Tinylog I think uses a fair amount of synchronized (I need to double check this) which is problematic with virtual threads but what is something I think the should change is they capture the literal Thread object in the event which was okay in traditional thread pools but with virtual threads where you want those GC as fast as possible I think that is not a good idea.
Tinylog custom service loader approach (it allows more than no-arg constructors) while novel I'm not sure how well it works in a modular environment. I assume it would but not sure. That is I'm not sure if the provides ... with ... just makes  single class entirely open or are there more rules like only a public constructor.
One of my favorite things in the Tinylog doc is how they format the java.util.Properties with the = lined up and that custom service loader approach makes it look even nicer. I may have to borrow that formatting for my properties part of the doc.
Anyway its  a great library and its why I did such an in depth analysis.

 There is no way Rainbow Gum is that much faster. I kept think it was slower because it is "s/op".
https://tinylog.org/v2/benchmark/


Check if monolog runs in web context

I faced the problem that if I use the FirePHP and ChromePHP handlers in a non-web context especially the firephp handler collected a lot of data (it stores every record in an internal array). So if you have a long process (for example a migration task) and the this process logs a lot of data you end up with a huge amount of memory in the end.
This PR checks if monolog/PHP runs in web context and if not doesn't do anything in case of the ChromePHP and FirePHP handlers.
I will fix the tests once I got feedback for the idea and if it will be accepted.

Makes sense, thanks. If you can get the tests working again that'd be great, and also turn that abstract class into a trait.

@Seldaek what's the best way to test this now? As I make use of the builtin PHP function php_sapi_name I somehow need to emulate it returns not cli. There is a PHP function mock lib for PHPUnit but I don't want to introduce a new dependency just because of that. Should I create mocked Chrome/FirePHP handlers in the tests an mock the trait function of them?

Yes I think mocking the function is the best way here.

@Seldaek done ✅

@stof thanks for your feedback. Done ✅

Thanks!


more robust overscan rms?

We are currently using standard deviation to report the overscan RMS.
For larger counts, the neighbouring overscan regions seem to also get a smaller amount of flux, artificially skewing the distribution.
Maybe the RMS would be more robust when reporting:
0.5*(84th-16th percentile)

It looks as if the overscan region for 2Amp is reasonably stable. But for the 4Amp case, the overscan needs to be adjusted! It is currently adding extra flux which in turn leads to wrong overscan RMS and thus wrong readout noise estimates!

Switched from STD = (P84-P16)/2

This has fixed the issue for the 4Amp case, where extra flux from nearby pixels was causing significantly higher overscan RMS / "readout noise" to be registered.


The "Select provider choice" should be more visible

The "Select provider choice" can currently be easily overlooked (see screenshot). This could be easily remedied by adding an additional header right above the "Select provider" dropdown widget and renaming the dropdown hint to something else.

This comes from the fact that this header is added as a stand-alone HTML widget in the notebook. For the embedded widget (which is used here) it is not present and should be added manually.
There are two choices:

Implement it in the OptimadeQueryWidget from aiidalab_widgets_base.databases (https://github.com/aiidalab/aiidalab-widgets-base/blob/3c509a5fbfc3e6efbd1f05b650995349174c05ed/aiidalab_widgets_base/databases.py#L127).
Have the OptimadeQueryProviderWidget from optimade_client absorb/embed the header.

This comes from the fact that this header is added as a stand-alone HTML widget in the notebook. For the embedded widget (which is used here) it is not present and should be added manually.
There are two choices:
1. Implement it in the `OptimadeQueryWidget` from `aiidalab_widgets_base.databases` (https://github.com/aiidalab/aiidalab-widgets-base/blob/3c509a5fbfc3e6efbd1f05b650995349174c05ed/aiidalab_widgets_base/databases.py#L127).

2. Have the `OptimadeQueryProviderWidget` from `optimade_client` absorb/embed the header.

Thanks for the quick response! I think I will go with option 1.


HA cleanup etc.

I am going to make my edits etc. on this branch for now. Don't merge yet!

This was rather erroneous and has been quickly made obsolete :)


can't authenticate kitematic from mac to my account

Expected behavior
Actual behavior
(HTTP code 401) unexpected - {"message":"Get https://registry-1.docker.io/v2/kitematic/hello-world-nginx/manifests/latest: unauthorized: incorrect username or password"}
Information about the Issue
Steps to reproduce the behavior

...
...

Please try to login using your Docker ID (hub username) instead of your email. This should fix the issue.


backport fixes for negative years (with tests) from netcdf4-python

with these all the tests in netcdf4-python pass

Thanks @jswhit!


Checkpoint room state

Users can join and leave rooms. If all users who are using the proxy leave a room, then Stuff happens and someone rejoins, the poller will be resent the entire room state from fresh. We currently do not use this correctly, and instead treat it as a "gappy sync", meaning we take what we previously had as the room state, and "roll forward" using what we are told in the state block.
We shouldn't do that, as it means that we can't handle state resets correctly (i.e we never remove state by rolling forwards), and if we calculate the wrong state in the past (not uncommon), we cannot self-heal by using the latest authoritative answer from upstream.
To do this is reasonably easy. All we need to do is, in Initialise:

is there an m.room.create even in the state block?

No: gappy sync, roll forward.
Yes: this sync contains everything, do a complete snapshot "rolling forwards" from the empty set [].

All we need to do is

then emit a cache invalidation payload (#294)

I think what we need Initialise to do is then:
	// 0. If the state block is empty, bail.
	//
	// 1. Capture the current snapshot ID, possibly zero.
	//
	// 2. Determine the kind of state block. Is it:
	//    a.
	//    b. B "gappy sync" state delta, not containing m.room.create?
	//
	// 3. Does this alter the current state of the room from the proxy's POV?
	//    a. Complete snapshot: state changes iff current snapshot's contents != state block.
	//       (What if this comes from a slow poller? Ahh, it'll catch up with later events and self-heal via Accumulate.)
	//    b. Gappy sync: state changes iff some state block event is not in the current snapshot.
	//    If the state hasn't altered, bail.
	//
	// 4. Create new snapshot.
	//    a. Complete snapshot: trust the state block verbatim.
	//    b. Gappy sync: build a map from (type, state_key) to nids for the current snapshot. Overwrite its entries
	//       with the new things in `state`. (There must be similar logic already in Accumulate for this?)
	//    Store the snapshot. Mark the room's current state as being this snapshot.
	//
	// 5. If the starting snapshot ID was not zero, emit a cache invalidation payload.

After discussion:
	// 0. If the state block is empty, bail.
	//
	// 1. Capture the current snapshot ID, possibly zero.
    //
    // 2. Fetch the current state of the room, as a map from (type, state_key) to event.
    //      If there is no existing state snapshot, this map is the empty map.
	//
	// 3. Does the state block alter the current state of the room from the proxy's POV?
	//     This is the case iff some event in the state block is unknown to the proxy.
	//     If the state hasn't altered, bail.
	//
	// 4. Create new snapshot.
	//     Update the map from (2) with the events in  in `state`.  (There must be similar logic already in Accumulate for this?)
	//    Store the snapshot. Mark the room's current state as being this snapshot.
	//
	// 5. If the starting snapshot ID was not zero, emit a cache invalidation payload.


Create an initial release job

Implementation of #94.
Implements scripts that build and push releases of the API and SDK to Rubygems, and augments the CI config to trigger them.
The proposed release process is as follows. To release a gem:

The version constant must be set to the version to be released.
A tag called #{gem_name}/v#{version} must be created and pushed to Github. (e.g. opentelemetry-api/v1.2.3). Thus, anyone with direct write access to the repo will be able to initiate a release.

When the tag is created in Github, CircleCI will automatically (after running that gem's tests one final time) run the release script. This script:

Verifies that the tag's version matches the gem's version constant
Builds the gem and pushes to Rubygems.

The release script requires the following environment variable configuration to be set on the CircleCI project (currently not yet done):

The OPENTELEMETRY_RUBYGEMS_API_KEY environment variable must be set with credentials for the Rubygems account we want to use to push the gem. Rubygems credentials will be held by the CI; individuals will not need direct access to them.
The OPENTELEMETRY_RELEASES_ENABLED environment variable should be set to the value true. (If it is not, the release script will run in test mode, and will go through the motions of building and verifying the gem, but will not actually push it to Rubygems.)

Current limitations, which I can address once we've agreed on the basic approach:

The Jaeger exporter is not yet covered. (Actually it's not yet covered by the CI at all. I can add it.)
The release script probably could check up front whether the proposed version has already been released, and fail fast with a more useful error message. As it is, I believe it will only fail at the end when the gem push is attempted.
The script is not enforcing any CHANGELOG updates. Indeed, we don't even have a changelog at all yet. At some point in the future, I think it might make sense to adopt conventional commits and have the release script automatically populate the changelog based on commit messages.

I'm not sure why the CLA check has hung. I have seen commenting on a PR is sometimes enough to get it unstuck. Let's see if this does anything.


add missing cortex memcached args

What this PR does:
Fix missing arg to configure memcache of ditributor.
Which issue(s) this PR fixes:
Fixes #307
Checklist

[ ] CHANGELOG.md [BUGFIX] - add missing memcache argument to ditributor

Distributor doesn't use memcache or any cache for that matter. Where did you find that information?


WIP: WRKLDS-517 - Extracting configs from the OCI FBC catalog for rendering

Description
This PR is part of the work for Jira epic CFE-538 and story WRKLDS-456.

A new GetConfigDirFromOCICatalog function is added in image.go. The purpose of this function is to extract (untar) the blob which contains the configs folder from the catalog OCI image.
The PR illustrates how this function can be used in the usecase MirrorToMirror with the imageSetConfig and command shown below in the test section.

TODOs:

defer cleanup of the tmp dir used for unpacking
handle cases where OCI FBC path in imageSetConfig is relative
Call the function also in renderDCFull, renderDCDiff, all cases

Fixes # WRKLDS-517
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update

How Has This Been Tested?
This is a WIP PR.
Its purpose is to show-case the solution to Workloads + Operator FW + Fields Eng teams (@jpower432 @ardaguclu , @deejross, @dinhxuanvu), and agree on it.
Further work (see TODOs) and unit test implementations are to come.

[x] Manual test using command   ./bin/oc-mirror -c imstcfg.yaml  docker://quay.io/skhoury/ocmir

Test Configuration:

ImageSetConfig:   kind: ImageSetConfiguration
   apiVersion: mirror.openshift.io/v1alpha2

   storageConfig:
     registry:
       imageURL: quay.io/skhoury/ocmir
       skipTLS: false
    mirror:
      operators:
     - catalog: oci:///home/skhoury/go/src/github.com/openshift/oc-mirror/rhop-ctlg-oci
   packages:
  - name: node-observability-operator
    channels:
    - name: alpha
helm: {}

Checklist:

[ ] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

/cc @lmzuccarelli

/cc @dinhxuanvu
Hi Vu,
Would you mind giving @lmzuccarelli and I an early feedback on this implementation?
This is a bit different than what we discussed in the Design Doc: we've seen that a new implementation of a Registry isn't required after all.
We also have a doubt right now as to the scenario the customer is targeting, and the way oc-mirror behaves :

When using oci (or file) in the ImageSetConfig under mirror.operators.catalog, and using ./bin/oc-mirror -c imstcfg.yaml docker://quay.io/skhoury/ocmir, we are in MirrorToMirror (see ImageSetConfig yaml example in description)
When using command, ./bin/oc-mirror  --from oci:/home/skhoury/go/src/github.com/openshift/oc-mirror/rhop-ctlg-oci/ docker://quay.io/skhoury/ocmir, we are in DiskToMirror

Your input will be very valuable.
Thank you

/test unit


Add documentation on how to uninstall an Operator

An Operator is installed by creating a Subscription that subscribes
to a specific Operator. By deleting the subscription, all Operator
resources such as CSV will be deleted.
Signed-off-by: Vu Dinh<EMAIL_ADDRESS>

All feedbacks are addressed. Ready for another round of review.

Fixed and ready for review @ecordell

/lgtm


New splash screen for 3.3

Yep, like discussed in https://github.com/jMonkeyEngine/sdk/issues/146.
I'm also in favor of using the yellow as main color for the version number. The red is visible, I'll give you that. But dammit that it hurts the eye. I myself do not possess any artistic capabilities, only autistic if any. I think that the appearance of the splash screen is rather important. It is the first thing a new user sees. And it is a graphics engine. Bling bling!

+1 for throwing the red color out

Yes I agree, yellow will look much better.

This can be closed already? This was done?

You are right, solved in 17cc281909db0a711fc0543e4af7771ead025b57 and c63b74256de3a9bad5495db993329f6aacefc843


[OPPRO-305] Fix semi join and support existence join

What changes were proposed in this pull request?

Fix the output type of semi join. Only one side of table should be included in the join result.
Supported existence join.

How was this patch tested?
under test

@zhejiangxiaomai Please help take a review, thanks.


git: fix the "perlSupport = false" configuration

When perlSupport = false, we will set NO_PERL=1, and build Git without Perl support. This is a build option that Git supports. However, Git's test suite still requires a Perl to be available to run the tests, and we did not provide one. The tests respect PERL_PATH, and if it is not set, they default to /usr/bin/perl.
Before this commit, if we set perlSupport = false, then no Perl would be available to the package, and so the tests would default to /usr/bin/perl. When building without a sandbox, that could still work,
even though there is no perl on the path, because the tests defaulted to an absolute path.
You can reproduce this issue as follows:
nix-build -E 'let pkgs = (import ./default.nix) {}; in pkgs.git.override { perlSupport = false; }'

I just ran into this when trying to build pkgs.git from an old version of Nixpkgs that I was able to build just fine in the past, and today it would not build any more, complaining when running the tests:
make -C t/ all
make[1]: Entering directory '/build/git-2.18.0/t'
rm -f -r 'test-results'
/nix/store/czx8vkrb9jdgjyz8qfksh10vrnqa723l-bash-4.4-p23/bin/bash: /usr/bin/perl: No such file or directory

In the past the sandbox was not enabled by default, so then it worked for me. But now that it is enabled, my host's (not NixOS) /usr/bin/perl is no longer accessible, and the build fails.
The solution is to explicitly set PERL_PATH when running the tests. This almost works, except that there appears to be a bug in the test for git request-pull. That command is a Bash script that calls Perl at some point, so it requires Perl, and therefore it cannot be supported when NO_PERL=1. But that particular test does not check whether Git was compiled with Perl support (other tests do include that check), and that makes the test fail:
t5150-request-pull.sh ..............................
not ok 4 - pull request after push
not ok 5 - request asks HEAD to be pulled
not ok 6 - pull request format
not ok 7 - request-pull ignores OPTIONS_KEEPDASHDASH poison
not ok 9 - pull request with mismatched object
not ok 10 - pull request with stale object
Dubious, test returned 1 (wstat 256, 0x100)
Failed 6/10 subtests

This output makes sense if you look at t5150-request-pull.sh. Test 1 and 2 are setup steps. Test 3 does call request-pull, but it expects the command to fail, and it cannot distinguish between the command exiting with a nonzero exit code, or failing to start it at all. So test 3 passes for the wrong reasons. Test 4 through 10 all call request-pull, so they fail.
The quick workaround here is to disable the test. I will look into upstreaming a patch that makes the test skip itself when Perl is disabled.

Motivation for this change
Without sandbox, setting perlSupport = false creates an implicit dependency on the host system. With sandbox, building with perlSupport = false fails.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I also verified that this does not introduce a Perl dependency in the closure with nix-store -qR.
Notify maintainers
cc @peti @the-kenny @wmertens @globin
Also, @bgamari, as the author of perlSupport, you might be interested in this.

Thanks for having a look! I rebased this on top of staging and changed the base branch.

Thanks!


Looks like we're calling etcd long-form args with only single -

Seems to work, but the help text uses --<arg_name> so it could bite up if they close that loophole.
$ sudo cat /etc/init/etcd.conf
<snip>

exec /usr/bin/etcd -name calicobobcatci01gulfstreamdatconcouk                                                      \
                   -advertise-client-urls http://<IP_ADDRESS>:2379,http://<IP_ADDRESS>:4001      \
                   -listen-client-urls http://<IP_ADDRESS>:2379,http://<IP_ADDRESS>:4001                                          \
                   -listen-peer-urls http://<IP_ADDRESS>:2380                                                                \
                   -initial-advertise-peer-urls http://<IP_ADDRESS>:2380                                \
                   -initial-cluster-token chef-cluster-1                                                                \
                   -initial-cluster calicobobcatci01gulfstreamdatconcouk=http://<IP_ADDRESS>:2380      \
                   -initial-cluster-state new

Fixed by https://github.com/Metaswitch/calico-chef/pull/24

I’ve also fixed the two instances of this in the docs; commit 63b8dd3.


Remove FastAPIError class.

Why?

Why?

Because the class "FastAPIError" inherits "RuntimeError" and doesn't have anything additional.
In my opinion, it would be better to use "RuntimeError" directly.

Why?

Because the class "FastAPIError" inherits "RuntimeError" and doesn't have anything additional.
In my opinion, it would be better to use "RuntimeError" directly.

FastAPIError should'n add anything additional, it just helps you to find the source of mistake. RuntimeError is built-in and can be evoked by several other libraries and it will be hard to find exception source. But FastAPIError is specific for FastAPI.
For example, you now your code can raise FastAPIError and what to mitigate this, you do something like this
try:
    func_that_may_rise_error()
except FastAPIError:
    log.info('it\'s okay, we can handle this')
    handle_error()
except RuntimeError:
    log.exception('something weird happened, take a look')
    raise

Thanks for your explanation.
My idea isn't good. sorry to all. I will close this PL.

Thanks for the help here @SirTelemak ! :cake:
And thanks @MashhadiNima for the interest. :nerd_face:


Resource based auth -- return errors.

I guess this is a bit of a mixed concern between authZ and validation...
How can you return errors from resource based auth without ending up with a spaghetti of if..elif.. statements checking individual policies?
Contrived example: User belongs to several groups. Super user of a group can add users to its group. How can I relay to the user that they don't have access to a particular group?

This is a dup of https://github.com/aspnet/Security/issues/1530, which we plan to handle as part of https://github.com/aspnet/Security/issues/1359.


Doc updates - break out configuration from downloading

Break out downloading from configuring in the README
The auto formatted updated the TOC to take out section numbers. It really wasn't part of the markdown standard with the HTML Note that the section numbers weren't applied in the body
Updated a couple of pictures.

Understand if this is rejected.  Ask that someone update the image that shows the wrong project and break out "downloading project" from "configuring project" and add NGC_HOME reference

Actually, all of these changes look great. Especially the updated screenshots! Thank you!
The only note I want to make is that the contents of the readme file are actually in the docs folder and they get joined together into one document. To be honest, this is mostly done to automate the documentation of the config schema. But it also makes the files smaller.
Could you please check out the instructions for updating the documentation here: https://github.com/nvidia/nim-anywhere?tab=readme-ov-file#updating-documentation
and let me know if you think you could port your changes over.


Cannot run some commands using uv tool run

Platform: macOS
UV version: uv 0.4.23 (Homebrew 2024-10-17)
I installed 2 tools using uv tool:

uv tool install labelme (an annotation tool)
uv tool install "huggingface-hub[cli]" (Hugging Face CLI)

I expected to run these tools using uv tool run (or uvx) but this does not work for the huggingface-cli command which return this error:
  × No solution found when resolving tool dependencies:
  ╰─▶ Because huggingface-cli was not found in the package registry and you require huggingface-cli, we
      can conclude that your requirements are unsatisfiable.

Here is the command I used (which is a valid command):
uv tool run huggingface-cli scan-cache
However, the command runs fine using those 2 commands:

uv run huggingface-cli scan-cache
huggingface-cli scan-cache

On the opposite, I can run the labelme command using uvx but not with uv run nor with a bare command call (simply labelme), which output this error:
Traceback (most recent call last):
  File "/Users/louislac/.local/bin/labelme", line 5, in <module>
    from labelme.__main__ import main
  File "/Users/louislac/.local/share/uv/tools/labelme/lib/python3.13/site-packages/labelme/__init__.py", line 6, in <module>
    from qtpy import QT_VERSION
  File "/Users/louislac/.local/share/uv/tools/labelme/lib/python3.13/site-packages/qtpy/__init__.py", line 287, in <module>
    raise QtBindingsNotFoundError from None
qtpy.QtBindingsNotFoundError: No Qt bindings could be found

Any reason those tools does not seem to work as expected?

Installing the tool adds its binaries to your PATH so, uv tool install "huggingface-hub[cli]" is expected to enable invoking huggingface-cli directly. Using uv tool run downloads a package with the matching name, then runs it. uv tool run huggingface-cli fails because it's looking for the huggingface-cli package. You want, uv tool run --from "huggingface-hub[cli]" huggingface-cli.
uv run huggingface-cli works because it invokes the binary on your PATH if it's not present in current virtual environment.

thanks, that is very clear!


fix ISO8601 formatter to always use the 24h format

:bulb: Motivation and Context
Closes https://github.com/PostHog/posthog-ios/issues/103
:green_heart: How did you test it?
:pencil: Checklist

[X] I reviewed the submitted code.
[ ] I added tests to verify the changes.
[ ] I updated the docs if needed.
[X] No breaking change or entry added to the changelog.

@bddq are you able to test from a branch?
the format was HH already and not hh so I believe it could be the default timezone and locale.
I cannot change my emulator to 12h only for some reason, the settings are blocked.


locals() dict share actual local variable

Feature

def a(d):
    locals()['d'] = 3
    b = 3 + d
    print(b)

a(21)

The code above generates the following error:
(locals dict share actual local variable)
Actual Result
Finished dev [unoptimized + debuginfo] target(s) in 0.11s
Running `target/debug/rustpython c.py`
6

Expected Result
24

If this issue is valid, can I take it?


Fix +/- 1 bug in converge algorithm

We were off by one with the turns. It is a miracle the algo was working at all earlier.


TEP-0127: Larger results using sidecar logs - feature flags and cluster-roles

Changes

Prior to this, we were extracting results from tasks via the termination messages which had a limit of only 4 KB per pod. If users had multiple results outputted by a task then they would have to share the 4KB limit.
We now run a dedicated sidecar that has access to the results of all the steps. This sidecar prints out the result and its content to stdout. The logs of the sidecar are parsed by the taskrun controller and the results updated instead of termination logs. We enforce an upper limit of 4KB per result (configurable) but there is no overall cumulative limit shared the results (users can have as many 4KB (or as configured) results as they desire).
This PR addresses the installation related changes of TEP-0127 - feature-flags and cluster-roles (see https://github.com/tektoncd/pipeline/pull/5695).
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] Has Docs included if any changes are user facing
[x] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[x] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
Implemented feature flags to enable larger results using sidecar logs.

/lgtm


Fixed #31310 -- Wrong hint about recursive relationship

Changed ForeignKey to ManyToManyField and removed outdated symmetrical=False keyword argument.

@matheuscmotta Thanks :+1: It looks that we don't have a test for fields.E334, can you add it in the first commit, and fix hints in the second?

Done @felixxm. Added the test in first commit with the old hint structure so that tests pass at that point in timeline.
On second commit made the fixes to hints. Also changed the name of the test for field 335, so that it's consistent with the new 334 naming and provide better context on its differences: from and to.
If the renaming is undesirable or cause issues I'm unaware of, could revert it back to old name.

@matheuscmotta Thanks :+1: I pushed minor edits.


Type check failed when call function via apply with array arguments

TypeScript Version:  3.4.0-dev.20190306、3.3.333333

Search Terms:
Code
function add (num1: number, num2: number, ...others: number[]) {
}

add.apply(null, [1, 2, 3, 4]) // right
const arr = [1, 2, 3, 4]
add.apply(null, arr) // Argument of type 'number[]' is not assignable to parameter of type '[number, number, ...number[]]'

Expected behavior:
compile success
Actual behavior:
Argument of type 'number[]' is not assignable to parameter of type '[number, number, ...number[]]'
but when I set strict to false in tsconfig.json it works fine
Playground Link:
https://www.typescriptlang.org/play/index.html#src=function add (num1%3A number%2C num2%3A number%2C others%3A number[]) {

}

add.apply(null%2C [1%2C 2%2C 3%2C 4])

const arr %3D [1%2C 2%2C 3%2C 4]
add.apply(null%2C arr)

Related Issues:

looks like (num1:number, num2: number, ...others: number[]) means should have at least 2 arguments, but number[] can have any length(less than 2 prob), right?

The problem as you correctly guessed is that arr has the type number[] which can't be guaranteed to have more that 2 elements. You want arr to be a tuple type. Tuples are similar to arrays (in fact at runtime they are arrays) but they are of a fixed length. Typescript will not however infer tuples for array literals by default.
You have several options to get around this:
Soo, in 3.4 you will be able to write as const, to get the compiler to infer a readonly tuple for arr:
const arr = [1, 2, 3, 4] as const

An option for before 3.4 is to use a function that hints at the compiler you want a tuple:
const arr = (<T extends any[]>(...o:T)=>o)(1, 2, 3, 4)

Or you can just manually type the tuple:
const arr: [number,number,number,number] = [1, 2, 3, 4]


Defect: Lab 5 Statistic

Defect

What is the source for this data point (which types of disabilities does it include)? According to the NIH he prevalence of adult ADHD alone is 4.4% for adults in the US.
On top of this, according to Yale, 20% of the US population (1 in 5 people) suffer from dyslexia.
If the statistic listed does not include either of these, that would bring the datapoint closer to 30%, not including children with ADHD (roughly 2.6% of total US population).

Acceptance Criteria

[ ] Statistic is updated
[ ] Everything else works as intended

SOURCES:
According to the CDC, ~11% of U.S. adults have a cognition disability with serious difficulty concentrating, remembering, or making decisions.
https://www.cdc.gov/ncbddd/disabilityandhealth/infographic-disability-impacts-all.html
According to the NIH, the overall prevalence of current adult ADHD is 4.4%.
https://www.nimh.nih.gov/health/statistics/attention-deficit-hyperactivity-disorder-adhd
According to NIH research, the prevalence of dyslexia is 20% in the US.
https://pubmed.ncbi.nlm.nih.gov/33278155/


create release branches

As soon as we can (by Oct 9), create release-soca-1.0.0 branches of (add if I am missing anything):

[ ] soca
[x] jedi-docs

The release branch for jedi-docs has been created.  PRs for soca documentation should go to there so we can finalize them before publishing them.

Just pushed release/soca-1.0.01 for gsw and soca. mom6 will require a bit of work.

Closing this issue. Admin work is done ... for now.
I added branch protection for soca, so we will have to issue PR's to merge into release/soca1.0.0 , same goes for jedi-docs @mmiesch added protections for release/* branches.


train on subset of classes

In COCO dataset there are 80 different classes, some architectures that worked previously on COCO might not work on Open Images in scale 1:1.
Having an option to train on just a subset of classes (e.g. 80) and sampler from #1 that will generate images with instances from this subset could help evaluating base architectures.

added in #31


Add more default metrics for Python topology

This patch adds more default metrics for Python topology, namely:
'__gateway-sent-metrics-size'
'__gateway-sent-metrics-packets-count'
'__gateway-sent-metrics-count'
'__gateway-sent-exceptions-count'
'__gateway-in-stream-queue-size'
'__gateway-out-stream-queue-size'
'__gateway-in-stream-queue-expected-capacity'
'__gateway-out-stream-queue-expected-capacity'
'__gateway-in-queue-full-count'

This PR also adds a half-acking topology example.
related to #1264

@taishi8117 - if you could take a look at this, it will be awesome.

it looks fine to me 👍

let us wait until @taishi8117 gives feedback.

@kramasamy @objmagic I made some comments, but other than that, this PR looks fine to me.

@taishi8117 I have addressed your comments in the latest commit.

seems integration test is very unstable. restarted CI...

Can you identify which integration test is unstable?

On Aug 30, 2016, at 10:04 AM, Mark Li<EMAIL_ADDRESS>wrote:
seems integration test is very unstable. restarted CI...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/twitter/heron/pull/1309#issuecomment-243508505, or mute the thread https://github.com/notifications/unsubscribe-auth/AAWcRF-ktaKuwqo-QKkdfSkGYCrJ9TAjks5qlGKcgaJpZM4JvL0V.

seems to me each one of them failed before (retried > 25 times)

restarted CI and now it's fine.


"Line removed" indicator duplicated on wrapped line

In this example, a line has been removed after line 13:

Hi, what version of Atom is this?  Can you reproduce it in safe mode (atom --safe)?

0.182.0, on Mac OSX Mavericks. behaves identically with --safe.

I was able to reproduce this:


Sharing violation on test.stdout.log and test.stderr.log

I am encountering situations where for some yet unknown reason another process is attaching to the test.stdout.log and the test.stderr.log of the files generated by the boost unit test executable.  This is of course causing that the test execution result to become undetermined.  If the user decides to run a batch of tests the whole batch goes in an undetermined state.
The log i have is

Executing:   -> [mytest01]
Exception caught while running test batch \Bin\Debug\Win32\i386\bin\BoostTest01.exe [mytest01] (The process cannot access the file 'C:\Users\gastart\AppData\Local\Temp\BoostTest01.exe.7096.6.test.stdout.log' because it is being used by another process.)

I dunno if we can print out the process with which we are having the access violation violation with so in future we can troubleshoot such problems easier, so as not to have to resolve to other tools like process monitor.
The below settings in the runsettings are a workaround to the problem but they come with the expense of losing functionality.
  <EnableStdOutRedirection>false</EnableStdOutRedirection>
  <EnableStdErrRedirection>false</EnableStdErrRedirection>

After deeper investigation of the process monitor logs, a simplified explanation of the problem I encountered is that the problem is that the boost unit test executable enchilada was not 100% ready when the executable returned!!  The test adapter is attempting to read the test.stdout.log about 25ms before all the related processes to the boost unit test executable closed off the test.stdout.log and test.stderr.log, hence causing the access violation.
Inserting a pause in BUTA between the execution phase and the reading off the log file solved the problem.
In essence can you please:
Insert a configurable sleep time (via the runsettings file) between the execution phase and the start of processing of the log files.  The optional parameter should have a default of zero and is to be defined in milliseconds.

executable enchilada was not 100% ready when the executable returned!!
Insert a configurable sleep time (via the runsettings file)

Hi @gastart thanks for your investigation. I'm not a big fan of so many configurable properties. Is there no way to ensure that writing the file is finished? Maybe Windows provides such a way, e.g. getting exclusive read access to the file?

OpenFile function: https://msdn.microsoft.com/en-us/library/windows/desktop/aa365430(v=vs.85).aspx
with OF_SHARE_EXCLUSIVE: Opens a file with exclusive mode, and denies both read/write access to other processes. If a file has been opened in any other mode for read/write access, even by the current process, the function fails.

Having debugged the problem with @netspiri, the issue regards external processes which are attaching to the test module.
In this particular test scenario, the test module is launching and executing the test successfully. By design, the test adapter redirects the standard output stream to a file. In the meantime, an external process seems to have hooked onto the output stream of the test module.
The problem occurs when the test adapter tries to read the contents of the standard output file while the external process still has a handle open to the stream. As correctly mentioned, Process Monitor signals a SHARING VIOLATION error, causing the exception to be thrown in the adapter. Apparently, the external process is opening the file utilising this configuration. Analysis using Process Monitor also hint that the external process is not spawned by the test module itself since the parent process is not the test module but this is non-conclusive information.
There were other test runs where the external process relinquished access to the file before the adapter tries to read it. Such cases were successful but, as evident, we are at the mercy of OS scheduling.
Just to be clear, this issue is only apparent in this kind of scenario. In general, this issue can be caused by processes such as anti-virus software, or as in this case, licensing servers. I do not think it is an issue which is perceived by a lot of users (but please, correct me if I am wrong) so starting off with a configuration addition might be a suitable solution for now. If the issue persists, then we can think of a long-er term solution.

@netspiri where in the code do you open the LOG file? Could you provide a link to source code please.

my idea is still to try OpenFile with OF_SHARE_EXCLUSIVE and if failing try again.
is there the case where no LOG file exists: means we are running always into the maximum timeout?

Hello @guwirth. I gave a quick look at the code and the log file seems to be opened via the methods GetStandardOutput() and GetStandardError().  The file is being opened in the ctor of BoostTestResultOutputBase
I discussed the option of "trying again" with @netspiri before we discovered that the interim sleep would do.  The "trying again" option would require the user defining a number of retries and interim time between retries I guess.
Regarding your second point as far as I know, the user has the option not to generate and process the stdout and stderr via the options
<EnableStdOutRedirection>false</EnableStdOutRedirection>
<EnableStdErrRedirection>false</EnableStdErrRedirection>

Additionally I think there might be crash situations of the boost unit test executable (for example dll not found) that might lead for the stdout, stderr to not be generated.

@gastart think you are closer to the problem and it's up to you to choose the right solution. My point is only that I'm not a big fan of user options. They are hard to test and maintain (especially combination of settings).

I discussed this issue with @netspiri offline.  We agreed that we should implement the sleep period as described in one of my previous comments.  This should be a very minor change in reality and I'll try to work on it sometime in the coming weeks....so please do not block any BUTA releases because of this enhancement.

Closed with #180


Add 'apartments details' view

Add  'apartments details' view and template.
Each time a user will click on see more or more info button on the apartment card in the search he will redirect to this view.
In this view will be displayed all the data about a specific apartment.

This was done in #146


Change that confusing "Joomlaish" menu-centric conceptual framework!

From the orig. README: "gui::Menu
The special, unique root layout. It behave like a VBoxLayout." (Ignore the typo.)
So... Where are the real menus (pulldown, context etc.) then?
ChatGPT's best (for a baseline ref), after a long massage session:

GuiCtrl
WidgetMgr
UiHandler
GraphCtrl
DisplayCtrl
GuiMaster
ScreenCtrl
WindowMgr
UiMaster
VisualCtrl

Btw, something "Session"-ish was also one I've been contemplating...
Also, if the new namespace could be kept sg descriptive (other than just "sfw"), it could help...

It's gui::Main now. You're welcome. ;)


fix: missing notification icons on dev and stag

Description

Type of Change

[ ] ✨ New feature (non-breaking change which adds functionality)
[x] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[ ] 🗑 Chore

Codecov Report
Base: 97.99% // Head: 97.99% // No change to project coverage :thumbsup:

Coverage data is based on head (1f72f3a) compared to base (561149b).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #35   +/-   ##
=======================================
  Coverage   97.99%   97.99%
=======================================
  Files         114      114
  Lines        2898     2898
=======================================
  Hits         2840     2840
  Misses         58       58

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Update search UI to return artifacts and collections

The search results should also specify whether the response is a project, artifact, or collection, either via an icon or some separation in how the results are presented in the tooltip

Going to need to switch Algolia to directly fetch from BigQuery

Most recent Plasmic publish takes care of this for Projects and Collections.
Artifacts are currently not being indexed on Algolia because it blows past our free tier atm. Very to easy to turn this on when we decide we want it.


Access denied. Operator $setOnInsert not allowed in a restricted collection. [403]

Hello @aldeed
Thanks for great packages!
I'm just upgrading into Autoform 6.0.0 release and I just stuck on this error.
Please let me know if you have any idea I can pursue here.
Note that I've already installed simpl-schema npm package and collection2-core package.
Access denied. Operator $setOnInsert not allowed in a restricted collection. [403]
This is my simple update form:
{{#autoForm
	id="book_editor_form1"
	collection=BookDB
	type="update"
	doc=book
	schema=BookDB.schema
	autosave=true
	autosaveOnKeyup=true
	trimStrings=false
	validation="keyup"}}

	{{> afQuickField name='grade'}}
	{{> afQuickField name='lesson'}}
	{{> afQuickField name='title'}}
{{/autoForm}}

This is my simplified schema and I've also removed unrelated array data here in schema, please ignore them.
BookDB.schema = new SimpleSchema({
	_id: {
		type: String,
		optional: false,
		defaultValue: function() {
			return Random.id();
		},
		regEx: SimpleSchema.RegEx.Id
	},
	_authorId: {
		type: String,
		optional: false
	},

	title: {
		type: String,
		optional: false,
		autoform:{
			label: false,
			leftLabel: function() {
				return TAPi18n.__('BookSchema.title');
			},
			options :[
			    ....
			]
		}
	},
	lesson: {
		type: String,
		optional: false,
		autoform:{
			label: false,
			leftLabel: function() {
				return TAPi18n.__('BookSchema.lesson');
			},
			options :[
			    ......
			]
		}
	},
	grade: {
		type: Number,
		optional: false,
		autoform:{
			label: false,
			leftLabel: function() {
				return TAPi18n.__('BookSchema.grade');
			},
			options : [
			    ......
			]
		}
	},

	categories: {
		type: Array,
		optional: true
	},
	"categories.$": {
		type: BookDB.schema.category
	}
}

Hello @aldeed
I'm sorry for opening this issue in wrong place, I believe I found its root cause in simpl-schema package. Somehow defaultValue leads this error.

I'm having issue too

Hello @sgelbart,
Have you take a look into defaultValue attributes in your schema? I had to remove all of them to get it work

Removing defaultValue fixed it!! Now I see what you said above :-) 👍 Thanks!

I'm having this same issue. I'm guessing this is a bug in node-simpl-schema? defaultValue fields are kind of an integral part of my schemas, and removing them all isn't really an option. I guess I could convert them all to autoValues that only return on insert but what a mess..

https://github.com/aldeed/node-simple-schema/blob/3eca0e858ba318d4764d3dea29380c8555531159/lib/SimpleSchema.js#L754

Hopefully we can verify if this is a bug or not soon and possibly a fix if it is. @fuatsengul this is probably best filed on the node-simpl-schema repo. For now as a workaround I have used an IIFE closure which returns a function that only returns the value if the operation is an insert and the field isn't set.
const defaultValue = value => function autoValue() {
  if (!this.isUpdate && !this.isUpsert && !this.isSet) {
    return value;
  }
};

// Schema field definition
fieldName: {
  type: Number,
  autoValue: defaultValue(10),
}

Thanks for the workaround @copleykj
I'm having this exact issue, which is a little painful considering all the schemas I'm working with.

I am having the same issue, and I'm not even using defaultValue in the schema. Any idea why?

Thanks for @copleykj to figure it out. I also had the same problem.

Had to change it a bit, as the solution didn't work for upserts:
const defaultValue = value => function autoValue() {
  if ( this.isSet ) return;
  if ( this.isInsert ) {
    return value;
  } else if ( this.isUpsert ) {
    return { $setOnInsert: value };
  }
}

Haven't tested it well yet, but upserts start to work just fine.


Promote AbortController for fetching in examples

cc @kacperkapusciak

two years) I had forgotten that contribute this pr