Bug in Visible If + Visible + Panel combination?

Are you requesting a feature, reporting a bug or ask a question?
Reporting a bug
What is the current behavior?
When specifying a 'Visible if' and then moving to the JSON Editor tab, somehow automatically the 'Visible' property is set to False. In my eyes this is not needed, as this is a seperate property and the Visible if property works well on its own (but I could be wrong). It has no effect on functionality, except when you put the question that has the Visible if in a Panel, and the question it depends on (as specified by the Visible if) outside of that panel. Then, the fact that the Visible property automatically gets set to false results in the Visible If statement not working anymore.
See below for a more detailed walk-through.
What is the expected behavior?
2 options:

The Visible property is not automatically set to False when moving to the JSON Editor tab as a result of the Visible If property being specified.

There needs to be a fix that the Visible if still works across panels, given that the Visible property gets automatically set to false. (The problem seems to be that the combination of Visible = false & panel structure results in the Visible If statement not working anymore).

I personally would opt for option 1, since it seems as an unnecessary dependency, but I might very well miss something there.
How would you reproduce the current behavior (if this is a bug)?

Make a form with two questions in the SurveyDesigner part of the SurveyJS Editor
Make the second question (question2) dependent on the first (question1) by adding Visible if (i.e. {question1} contain 'Item1'). Leave the Visible property checked (Visible = True)
Confirm that the Visible If works by Testing the form.
Move to the JSON Editor and out of it to the Survey Designer
Confirm that for question2, next to the Visible If option, the Visible option is now set to false. You can of course also see this in the JSON Editor itself.
Confirm that the Visible If  still works by Testing the form.
Now add a panel and put question2 (that contains the specified visible if property) into that panel. Leave question 1 out.
Confirm that the Visible If  no longer works by Testing the form.
Add question1 to the panel as well
Confirm that the Visible If  now works again by Testing the form
Take question1 out of the panel again, but leave question2 in there. Manually set Visible=True for question2 in the SurveyDesigner and directly go to the Test tab. Confirm that now, with the panel, the Visible If does work.
Go back and forth to the JSON Editor, see Visible being set to False automatically again, and confirm that now, the Visible if stopped working again.

Provide the test code and the tested page URL (if applicable)
Tested page URL: https://surveyjs.io/Survey/Builder/

@Lynn42 ok, I have added a unit test and fixed it. Survey do not run conditions (change visible/enable) at design mode, in Editor
It should work fine since the next minor update on the next week.
Thank you,
Andrew

Wow that was fast, thank you!
For my understanding, do I understand correctly that you implemented the first solution? : The Visible property is not automatically set to False when moving to the JSON Editor tab as a result of the Visible If property being specified.

@Lynn42 Yes, you are right. But the bug is still here. I have to modify the Editor a little bit as well :)

@Lynn42 ok, it is fixed now :)


rename BusinessLogicSyscallHandler

Renames the BusinessLogicSyscallHandler struct to DeprecatedBLSyscallHandler.

Codecov Report

Merging #266 (90229f8) into main (7faf22d) will decrease coverage by 0.01%.
The diff coverage is 97.36%.

@@            Coverage Diff             @@
##             main     #266      +/-   ##
==========================================
- Coverage   96.36%   96.36%   -0.01%
==========================================
  Files          46       46
  Lines        8257     8253       -4
==========================================
- Hits         7957     7953       -4
  Misses        300      300

Impacted Files
Coverage Δ

src/utils.rs
95.17% <ø> (ø)

...rc/core/syscalls/business_logic_syscall_handler.rs
89.46% <87.50%> (-0.09%)
:arrow_down:

.../business_logic/execution/execution_entry_point.rs
95.81% <100.00%> (ø)

src/core/syscalls/syscall_handler.rs
96.28% <100.00%> (ø)

src/core/syscalls/syscall_response.rs
88.08% <100.00%> (ø)

src/starknet_runner/runner.rs
97.52% <100.00%> (ø)

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


Revert "[SPARK-24152][R][TESTS] Disable check-cran from run-tests.sh"

What changes were proposed in this pull request?

This reverts commit 91d990162f13acde546d01e1163ed3e898cbf9a7.
Why are the changes needed?

CRAN check is pretty important for R package, we should enable it.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Unit tests.

cc @dongjoon-hyun @HyukjinKwon

Let's check if CRAN check is back.

Test build #113184 has started for PR 26381 at commit b421ef0.

Merged build finished. Test PASSed.

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

Test build #113184 has finished for PR 26381 at commit b421ef0.

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

Merged build finished. Test PASSed.

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

The CRAN issue looks resolved now.


Link is broken on bootstrap-tokens.md page

Problem:
The link https://github.com/kubernetes/community/blob/master/contributors/design-proposals/cluster-lifecycle/bootstrap-discovery.md is dead.
see the Link to know more about the issue.
Proposed Solution:
This issue has been resolved by adding a simple link and enhancing the document line.
Page to Update:
https://kubernetes.io/docs/reference/access-authn-authz/bootstrap-tokens/
/kind document
/assign

/help wanted
/english en

/assign

/help
/language en

/triage accepted
Thanks for reporting this. I'm wondering how we should fix it: pointing to the new location or removing the pointer to design docs?

Hi @tengqm
IMO we can point it to the new location, which is kubernetes/design-proposals-archive/cluster-lifecycle/bootstrap-discovery.md
https://github.com/kubernetes/design-proposals-archive/blob/main/cluster-lifecycle/bootstrap-discovery.md
So it is easy for the readers to understand things. What do you think?

This PR is fixed by #34076 . I think we can close the PR. Thanks.

Since it is already fixed. This issue can be closed.
/close

@Shubham82 My primary concern is that the design proposals usually contain too many "design" details which a user doesn't really need to understand. My other concern is that such links are fragile considering that the upstream repo may move the files again and again.

@tengqm agree with you, there are so many design links in the docs which redirect to the same page. see this comment


Actor crashed EOFError: end of file reached

I've been able to successfully send notifications in the past but whatever I try at the moment gives me an error. I tried both using the CLI and from pry. All result in the same error.
Looking at the stack trace the problem seems to be in openssl, so I tried regenerating my push certificate as well. After doing the certificate dance I'm still getting the error.
I was able to send a push notification with the same certificate/token using houston.
Logs / stack trace:
lowdown --debug --verbose -e "production" -m "Test" -c certificate.pem "[token]"
W, [2016-04-21T13:01:51.650617 #98370]  WARN -- : Dangerously suspending task: type=:call, meta={:dangerous_suspend=>true, :method_name=>:initialize}, status=:callwait
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/call/sync.rb:41:in `response'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/call/sync.rb:45:in `value'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/proxy/sync.rb:22:in `method_missing'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/proxy/cell.rb:12:in `_send_'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid.rb:207:in `new_link'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-pool-0.20.5/lib/celluloid/supervision/container/pool.rb:137:in `__spawn_actor__'
I, [2016-04-21T13:01:51.651909 #98370]  INFO -- : [APNS Connection#0x7ff9bc9ede10] Connecting...
W, [2016-04-21T13:01:51.654349 #98370]  WARN -- : [APNS Connection#0x7ff9bc9ede10] Defer performing request, because the connection has not been established yet.
I, [2016-04-21T13:01:52.212565 #98370]  INFO -- : [APNS Connection#0x7ff9bc9ede10] Connection established.
D, [2016-04-21T13:01:52.212630 #98370] DEBUG -- : [APNS Connection#0x7ff9bc9ede10] Maximum number of streams: 500. Flushing 1 enqueued requests.
D, [2016-04-21T13:01:52.212854 #98370] DEBUG -- : [APNS Connection#0x7ff9bc9ede10] [00000000-0000-0000-0000-000000000001] Performing request
E, [2016-04-21T13:01:52.377537 #98370] ERROR -- : Actor crashed!
EOFError: end of file reached
	/Users/klaaspieter/.rubies/ruby-2.3.0/lib/ruby/2.3.0/openssl/buffering.rb:178:in `sysread_nonblock'
	/Users/klaaspieter/.rubies/ruby-2.3.0/lib/ruby/2.3.0/openssl/buffering.rb:178:in `read_nonblock'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-io-0.17.3/lib/celluloid/io/stream.rb:42:in `block in sysread'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-io-0.17.3/lib/celluloid/io/stream.rb:390:in `synchronize'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-io-0.17.3/lib/celluloid/io/stream.rb:40:in `sysread'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-io-0.17.3/lib/celluloid/io/stream.rb:129:in `readpartial'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/lowdown-0.3.1/lib/lowdown/connection.rb:223:in `block in runloop'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/lowdown-0.3.1/lib/lowdown/connection.rb:221:in `loop'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/lowdown-0.3.1/lib/lowdown/connection.rb:221:in `runloop'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/calls.rb:28:in `public_send'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/calls.rb:28:in `dispatch'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/call/async.rb:7:in `dispatch'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/cell.rb:50:in `block in dispatch'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/cell.rb:76:in `block in task'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/actor.rb:339:in `block in task'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/task.rb:44:in `block in initialize'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/task/fibered.rb:14:in `block in create'
I, [2016-04-21T13:01:52.377761 #98370]  INFO -- : [APNS Connection#0x7ff9bc9ede10] Closing...
D, [2016-04-21T13:01:52.506076 #98370] DEBUG -- : Terminating 6 actors...
W, [2016-04-21T13:01:52.507216 #98370]  WARN -- : Dangerously suspending task: type=:finalizer, meta={:dangerous_suspend=>true, :method_name=>:__shutdown__}, status=:receiving
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/actor.rb:230:in `receive'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid.rb:395:in `receive'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/future.rb:90:in `value'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-pool-0.20.5/lib/celluloid/supervision/container/pool.rb:39:in `block in __shutdown__'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-pool-0.20.5/lib/celluloid/supervision/container/pool.rb:39:in `each'
	/Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-pool-0.20.5/lib/celluloid/supervision/container/pool.rb:39:in `__shutdown__'
D, [2016-04-21T13:01:52.507285 #98370] DEBUG -- : Discarded message (mailbox is dead): #<Celluloid::TerminationRequest:0x007ff9bd9a0650>
W, [2016-04-21T13:01:52.507369 #98370]  WARN -- : Terminating task: type=:finalizer, meta={:dangerous_suspend=>true, :method_name=>:__shutdown__}, status=:receiving
	Celluloid::Task::Fibered backtrace unavailable. Please try `Celluloid.task_class = Celluloid::Task::Threaded` if you need backtraces here.
D, [2016-04-21T13:01:52.507541 #98370] DEBUG -- : Discarded message (mailbox is dead): #<Celluloid::ExitEvent:0x007ff9bd9825d8>
D, [2016-04-21T13:01:52.507600 #98370] DEBUG -- : Discarded message (mailbox is dead): #<Celluloid::TerminationRequest:0x007ff9bd9a0678>
D, [2016-04-21T13:01:52.507742 #98370] DEBUG -- : Discarded message (mailbox is dead): #<Celluloid::ExitEvent:0x007ff9bd982bf0>
D, [2016-04-21T13:01:52.507786 #98370] DEBUG -- : Discarded message (mailbox is dead): #<Celluloid::ExitEvent:0x007ff9bd982e20>
D, [2016-04-21T13:01:52.508087 #98370] DEBUG -- : Discarded message (mailbox is dead): #<Celluloid::Call::Sync:0x007ff9bd981ea8>
D, [2016-04-21T13:01:52.508162 #98370] DEBUG -- : Discarded message (mailbox is dead): #<Celluloid::Future::Result:0x007ff9bd97b800>
/Users/klaaspieter/.rubies/ruby-2.3.0/lib/ruby/2.3.0/openssl/buffering.rb:178:in `sysread_nonblock': end of file reached (EOFError)
	from /Users/klaaspieter/.rubies/ruby-2.3.0/lib/ruby/2.3.0/openssl/buffering.rb:178:in `read_nonblock'
	from /Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-io-0.17.3/lib/celluloid/io/stream.rb:42:in `block in sysread'
	from /Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-io-0.17.3/lib/celluloid/io/stream.rb:390:in `synchronize'
	from /Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-io-0.17.3/lib/celluloid/io/stream.rb:40:in `sysread'
	from /Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-io-0.17.3/lib/celluloid/io/stream.rb:129:in `readpartial'
	from /Users/klaaspieter/.gem/ruby/2.3.0/gems/lowdown-0.3.1/lib/lowdown/connection.rb:223:in `block in runloop'
	from /Users/klaaspieter/.gem/ruby/2.3.0/gems/lowdown-0.3.1/lib/lowdown/connection.rb:221:in `loop'
	from /Users/klaaspieter/.gem/ruby/2.3.0/gems/lowdown-0.3.1/lib/lowdown/connection.rb:221:in `runloop'
	from /Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/calls.rb:28:in `public_send'
	from /Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/calls.rb:28:in `dispatch'
	from /Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/call/async.rb:7:in `dispatch'
	from /Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/cell.rb:50:in `block in dispatch'
	from /Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/cell.rb:76:in `block in task'
	from /Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/actor.rb:339:in `block in task'
	from /Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/task.rb:44:in `block in initialize'
	from /Users/klaaspieter/.gem/ruby/2.3.0/gems/celluloid-0.17.3/lib/celluloid/task/fibered.rb:14:in `block in create'

Probably a duplicate of #14, updating to lowdown 0.3.2 should fix it.

It appears that way. Now I'm stuck with 400 Bad Device Token.


Added ability to toggle maven snapshot on version when regular commits are greater than zero

In reference to #4 , this PR adds the ability to toggle maven snapshots on the generated version. I've updated tests and such, though I think that the method of specifying the configuration could be refactored into a more robust class, rather than being scattered into three or four already.
I'm not a pro with Kotlin by any standards, so any guidance or things I've missed please let me know.

Hello, thanks for the contribution. A few notes:
I'm not sure I follow the logical flow here. Maybe this is because Maven traditionally doesn't use patch numbers as in semantic versioning, but it doesn't look like either maven versioning or semantic versioning has been implemented fully here.
What I mean is, for semantic versioning we'd probably want to keep the patch number, as that contains useful semantic information. If we do 20 bug fixes on version 1.2.0 to bring us to 1.2.20, do we want to throw away that information on the next snapshot and have it as 1.2-SNAPSHOT? I don't think that's a great idea, I'd much prefer to keep the patch number intact and have the -SNAPSHOT after the fact.
Additionally, maven versioning conventions stipulate that a SNAPSHOT version is strictly a predecessor of the release version, so 1.2-SNAPSHOT (Or 1.2.20-SNAPSHOT) comes before 1.2 (1.2.20). This makes sense, as if you're using a snapshot version and then move to the actual release version, you want maven to know that the release is a later version than the snapshot. This creates a problem, because as soon as we perform a release (of 1.3.0 for instance), our next commit is going to be 1.3-SNAPSHOT (Or 1.3.0-SNAPSHOT), which isn't correct. In maven terms it ought to be 1.4-SNAPSHOT, but if you don't throw away the patch version then it's a bit more unclear. Is it 1.3.1-SNAPSHOT or 1.4.0-SNAPSHOT? Probably 1.3.1-SNAPSHOT, but in that case you could still end up releasing a snapshot of 1.3.1 and then actually end up releasing 1.4 instead. That might not be a problem, just something to keep in mind.
It might be worth making the versioning more flexible in general so that it can work for all the use cases outlines. For example- we could include a suffix option the same as prefix that could be used to append -SNAPSHOT. This would also include a build number in the output version though which isn't ideal, so maybe we could have a separate options for including .build or even .patch too. This way, you could use maven versioning with just 1.0, 1.1-SNAPSHOT, 1.1. You could use semantic versioning with SNAPSHOT like 1.0.0, 1.0.1-SNAPSHOT. It would also open up the possibility to use semantic versioning metadata or other suffixes like RC-1 or -RELEASE if you're following different versioning conventions, which would be a nice bonus. Not sure on the snapshot incrementing in this scenario though. If you remove "maven snapshot" from the configuration and have it done manually, you lose the logic to increment the minor/patch version when using snapshot versions instead of build versions.
Hmm. At the very least I think this should change to preserve the semantic versioning information and follow maven version increment conventions. Whether it needs to add all the flexibility mentioned I don't know- it doesn't solve all the problems and I can't think of a neat way to solve them right now.

This should have been fixed in #9
Let me know if not


Remove broken travis ci badge with github ci badge

:partying_face: :partying_face: :partying_face: :partying_face: :partying_face:


Site Ready for Deployment

-updated event cards
-modified hero on mobile

I pushed a new commit with the requested changes


Question: How is this different from tox-gh-actions?

Not an issue but a question: How is this project different from https://github.com/ymyzk/tox-gh-actions?
Right now the other project has a lot more stars and forks than this one.
What would be the upside to using this GitHub action rather than tox-gh-actions?

This plugin is only compatible with the upcoming tox 4 version. They both do the same(ish) thing but they have a bit different design philosophies. For details why we have to https://github.com/ymyzk/tox-gh-actions/issues/74

Right now the other project has a lot more stars and forks than this one.

You're free to use either one you like.
Notably https://github.com/ymyzk/tox-gh-actions#examples has different configuration format than https://github.com/tox-dev/tox-gh#basic-example

@gaborbernat reading between the lines in https://github.com/ymyzk/tox-gh-actions/issues/74, it seems like there isn't going to be much effort to bring these two project back together?  Are you planning to fully support this plugin?

Yes, there's no plan to unify the projects. I am planning on supporting this plugin (though is a community project, so PRs welcome).

Is unclear to me what that is trying to do and how.

I was trying to move in https://github.com/pytest-dev/pytest-github-actions-annotate-failures/pull/91. The idea is to be able to run just the "-pytestN" job but still keep the rest of the automatic selection.

I do not think that is a feature we support today, but PR welcome.


Can't auto import in server dir ?

same one

how to import method to the server?

just got the same error on server api routes trying to use lodash on server side


Move the docs!

The documentation at sphinx-exercise.readthedocs.io is pointing to the old version. We should delete that project entirely and then add this project for that URL. (unfortunately I don't believe you can move projects on RTD)

@choldgraf I don't fully follow - sphinx-exercise.readthedocs.io is not our project or is it? 👀

ohhhh lol, I didn't realize that 🤦

let's see what they say https://github.com/lizardzhou/sphinx-exercise/issues/1

Followed up but that account looks pretty inactive.


Refactor main

Codecov Report

Merging #222 (fa7db39) into main (806fd6a) will decrease coverage by 0.98%.
The diff coverage is 50.49%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #222      +/-   ##
==========================================
- Coverage   76.24%   75.27%   -0.98%
==========================================
  Files         137      144       +7
  Lines        7776     8081     +305
==========================================
+ Hits         5929     6083     +154
- Misses       1563     1691     +128
- Partials      284      307      +23

Flag
Coverage Δ

unittests
75.27% <50.49%> (-0.98%)
:arrow_down:

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

Impacted Files
Coverage Δ

checker/checker.go
35.54% <0.00%> (-1.00%)
:arrow_down:

internal/diff.go
19.04% <19.04%> (ø)

internal/errors.go
22.22% <22.22%> (ø)

internal/json.go
40.00% <40.00%> (ø)

internal/yaml.go
40.00% <40.00%> (ø)

internal/breaking-changes.go
49.01% <49.01%> (ø)

internal/run.go
57.53% <57.53%> (ø)

internal/flags.go
73.86% <73.86%> (ø)

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


Add 2nd baro to offline temperature calibration script

Needed to temperature calibrate full Pixhawk 2 sensor suite.

Tempcal works fine on master. It had been my mistake.


Why treat empty filenames specially?

opustags complains if a filename argument is empty. Most programs don't do this, they will just give an error when they try to open a file with an empty name.

You’re absolutely right. That applies to both input and output file. We’ll need an extra state to differentiate empty path_out and unspecied path_out when validating options.

Sorry, it seems I wasn't clear: my suggestion was that we don't need any special code to deal with empty path_out, and we don't validate that path_out is non-empty.

I got that point, but look at: https://github.com/fmang/opustags/blob/6f7ac1f13bbbe30b173bc4c7ea2d52da2051bea7/src/cli.cc#L73-L74
If we accept empty as a valid path_out, then this test breaks because we won’t be able to distinguish the case -o "" (path_out is empty because the user specified an empty value) and the case with no -o at all (path_out empty by default). If we just dropped the validation, then the CLI won’t detect any error with -o "" -o x.

This is no problem. Just as in any other case, if a valid filename overrides an invalid one, there's no reason why that should be detected. We don't validate filenames before using them. Again, this is how standard command-line utilities behave.

I realize that you're also referring to the fact that you can't specify --output more than once. Again, we can detect that properly, by detecting whether the string has been set, not whether it's empty.


Allow Headers to be set with m.request config

Description:
Sometimes you need to set http headers when making a request to a remote end service.  This includes things like custom headers your API requires such as tokens, etc...
It should be possible to set these headers or pass them in as a parameter when calling m.request
Steps to Reproduce:
var headers = { "Authorization" : "Bearer 12345abcd12345" };
var users = m.request({method: "GET", url: "/user", headers: headers});

Expected:
Headers are sent alongside the m.request
Actual:
Headers aren't sent

http://mithril.js.org/mithril.request.html#configuring-the-underlying-xmlhttprequest provides access to do whatever configuration you desire to the underlying XHR object. Does that cover your use-case?

Oh, I went a bit of a different route: https://github.com/lhorie/mithril.js/pull/1464
It's probably a redundant PR if you can do it that way.  Depends whether you feel that there should be a cleaner interface for this sort of stuff


bpf: Explicitly drop unhandled IP fragments

Recent commits should reduce occurrences of unexpected IP fragments
generated within the cluster, but could still plausibly arrive
unexpectedly from external entities. In such cases, if policy is
enabled, then drop the fragments explicitly with a reason that makes it
clear why they're dropped.
IPv6 already has this behaviour via #4222.
This is unlikely to be hit in most deployments because at least as of
Cilium 1.2, kube-proxy is typically used for proxying any packets that
may interact with a host that could send fragments. Other nodes within
Cilium's control are typically automatically configured by Cilium in a
way that prevents fragments from being sent.
This splits out part of #3766.

This change is

test-me-please

Nominating for backport as this will be very helpful in troubleshooting.


need to delete server certificate on delete_foundation using

https://docs.aws.amazon.com/cli/latest/reference/iam/delete-server-certificate.html


Countermeasure-generated assets don't appear in asset model

Expected behaviour
Countermeasure-generated assets should appear in classModelElements stored procedure.
Actual behaviour
Countermeasure-generated assets don't appear in classModelElements stored procedure.
Steps to reproduce the behaviour
Generate asset from countermeasure.  View asset model.
Version of CAIRIS
All
Operating Systems / Hardware
All

The problem here is that the asset was generated without being assigned to an environment.  Can't reproduce so closing for now until we can.


Add CODEOWNERS file

Support automatically requested for review when someone opens a pull request.
Note that:

code owners are not automatically requested to review draft pull requests.
when you mark a draft pull request as ready for review, code owners are automatically notified.

More information on https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
https://github.com/longhorn/longhorn/issues/2382

Let's add codeowners for each primary components. Thanks Jenting.


API key expired error

When selecting Trigger new event or Forward events to your local machine, raise an API expired error.
On Stripe CLI, API key option is available but I guess the API key is hard coded, and don't know how to pass API key on VS CODE.
 FATAL Error while authenticating with Stripe: Authorization failed, status=401, body={
  "error": {
    "code": "api_key_expired",
    "doc_url": "https://stripe.com/docs/error-codes/api-key-expired",
    "message": "Expired API Key provided: rk_test_*********************************************************************************************KtSz7X",
    "type": "invalid_request_error"
  }
}

Hi @DIGITALSQUAD, we don't have a way for you to pass in an API key for these actions from the extension. Could you login to your account? There should be a login flow that pops up but that seems to not be coming up for some reason -- I'll look into that. Meanwhile, you can login via the command line with stripe login. This will save the credentials for you so you do not have to provide the key for every command.

@gracegoo-stripe Fixed after login, thanks!


mellowplayer: 3.6.7 -> 3.6.8

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/MellowPlayer/versions.
meta.description for mellowplayer is: "Cloud music integration for your desktop"
meta.homepage for mellowplayer is: "https://gitlab.com/ColinDuquesnoy/MellowPlayer"
meta.changelog for mellowplayer is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 3.6.8 with grep in /nix/store/hfi7k8isashc3nclm52j1dbk4nbh1kwi-MellowPlayer-3.6.8

directory tree listing: https://gist.github.com/bcf0ddfcd4a493a424b7702fdbdaab55

du listing: https://gist.github.com/243b383696b01a4d5b105eec1fbb4bda

Rebuild report (if merged into master) (click to expand)

4064 total rebuild path(s)

1329 package rebuild(s)

1200 x86_64-linux rebuild(s)
1105 i686-linux rebuild(s)
580 x86_64-darwin rebuild(s)
1179 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
DisnixWebService
R
abcl
adapta-gtk-theme
adoptopenjdk-icedtea-web
alloy
alloy4
alloy5
ansible-lint
antlr
antlr3
antlr3_4
antlr3_5
antlr4
antlr4_8
apache-airflow
apache-jena
apache-jena-fuseki
apacheKafka
apacheKafka_2_4
apacheKafka_2_5
ape
apeClex
apktool
appdaemon
apprise
archivy
areca
asciidoc-full
asciidoc-full-with-plugins
autofs5
av-98
avian
aws-google-auth
axoloti
azure-cli
azureus
backintime
backintime-common
backintime-qt
bareos
bazel
bazel-remote
bazel-watcher
bazel_0
bazel_0_26
bazel_0_29
bazel_1
bazel_3
belle-sip

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hfi7k8isashc3nclm52j1dbk4nbh1kwi-MellowPlayer-3.6.8 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A mellowplayer https://github.com/r-ryantm/nixpkgs/archive/5b2cfe4fc2c2925ee68278d6555062e89561bf68.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hfi7k8isashc3nclm52j1dbk4nbh1kwi-MellowPlayer-3.6.8
ls -la /nix/store/hfi7k8isashc3nclm52j1dbk4nbh1kwi-MellowPlayer-3.6.8/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @kalbasit for testing.

@ryantm it seems that the auto-update thought that this change will rebuild over 1k packages when it's only going to rebuild one package. Not sure why it did that.
4064 total rebuild path(s)

1329 package rebuild(s)

1200 x86_64-linux rebuild(s)
1105 i686-linux rebuild(s)
580 x86_64-darwin rebuild(s)
1179 aarch64-linux rebuild(s)

I changed the base back to master given it's only rebuilding one package.

@ryantm it seems that the auto-update thought that this change will rebuild over 1k packages when it's only going to rebuild one package. Not sure why it did that.
4064 total rebuild path(s)

1329 package rebuild(s)

1200 x86_64-linux rebuild(s)
1105 i686-linux rebuild(s)
580 x86_64-darwin rebuild(s)
1179 aarch64-linux rebuild(s)

I changed the base back to master given it's only rebuilding one package.

@kalbasit Thanks, this is a known bug that I haven't investigated yet.

@kalbasit Thanks, this is a known bug that I haven't investigated yet.

Tested locally on my NixOS. It works well.

Tested locally on my NixOS. It works well.


Bug Fix: #70 (Updated : mobile-view docsify logo

Description
Updated Style.css Fixed : #70 mobile-view darklight logo
Fixes # (issue)
#70 https://github.com/collab-community/journey-book/issues/70#issue-1321288079
How Has This Been Tested?
Tested on local device
Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

[x] Test A
[x] Test B

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[] Any dependent changes have been merged and published in downstream modules

@vikasganiga05  @KendallDoesCoding  Review Required !

@vikasganiga05 @KendallDoesCoding Review Required !

Yes, we have been marked for review. Thanks


updated uptime AND added debug

to show the real uptime and the last start...

i have added it but i dont know i i implemented it right...

and the debug:

Remove the second $bootTime initialization

like this?

No, $dateFormat and $timeFormat are important for parsing the datetime.
It's the other line that needed to be removed.

i litterly searched for "$bootTime = "
got 3 and the secound was that that was deleted...
but let me fix that...

this should be good? @StudentSerai1181201811

Yeah, uptime seems fine to me now, haven't tested it with Powershell 5.X however so I'm not sure if it works on that version.

my last knowledge is that psp is only for .. upwards...

I checked it just now, it works except for this line:
$formattedBootTime = $bootTime.ToString("dddd, MMMM dd, yyyy HH:mm:ss", [System.Globalization.CultureInfo]::InvariantCulture) + " [$lastBootStr]"

This is because in powershell 5.X, we're using $lastBoot while for the new powershell, we're using $lastBootStr
So you might want to change all instances of $lastBoot to $lastBootStr or vice versa.
An alternative would be to use + " [$bootTime]" instead but then a datetime format mismatch may occur.
ie. formatted as [11/16/2024] when my datetime format is [16/11/2024]


Is there any method which i can use to interact with change country field? in a form

Question
there is a change country field in my automation but I am unable to find any method which I can use to click on this button and select country

@TYLEROL


Update documentation for snapshots.pattern

The current documentation for usage of "creation_date" is unclear for users not familiar with pongo2. In addition the documentation about date formatting with pongo2 out there is minimal.
The explanation of the suffix is just wrong and should be corrected.

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

Looks good, thanks!


Allow the hint.css package in npm to expose CSS

Many modules are starting to expose their css entry files in their package.json files via the style field . This allows tools like npm-css, rework-npm and npm-less to import hint.css CSS from the node_modules directory.
Also this plays well with browserify plugins ( like parcelify) which helps in bundling CSS together from npm packages

Replaced hint.css with hint.min.css
Initially referenced the non-minified file so that it would easy to debug in case of conflict with other CSS being included. Read it somewhere, that not to reference minified files in package.json (atleast in the main field , but can't find reference for this practice anywhere in the official npm documentation now).


CWA interfers with app that use bluetooth sync functions (Polar Flow)

First of all, thank you for contributing to a safer and healthier world!
Describe the bug
The CWA interferes with the app Polar Flow that uses Bluetooth to sync wearables or bike computers.
When CWA is installed, only the connection to the wearables is possible and sync does not work anymore. The wearable seems to be connected to the device, but it does not connect to the app to sync. When CWA is uninstalled, the syncing is working. It also occurs on an other device with another wearable using the same service (friend of mine) and likewise, uninstalling CWA fixed the issue.
Expected behaviour
The CWA is installed and Bluetooth and GPS is on.
When syncing the wearable you make sure Bluetooth and GPS is on, that you are connected to the internet and your device is connected to the wearable. Then you open the Polar Flow App and start the syncing with your wearable. The wearable connects to the app and syncs your data. This all happens while CWA is installed.
Steps to reproduce the issue
You need to install CWA and try to sync a wearable with Polar Flow. There will be no error message in CWA, but the syncing will fail.
Technical details
Android 10 on Samsung Galaxy M31
Possible Fix
Additional context
The wearable used was the Polar V800.

CWA does not interfere with the sync process of my Fitbit Charge 3. So it seems to be a problem on Polar's side IMHO.

As mentioned above this looks like an issue on Polar Flow. Therefore I will close this issue.


Fix for #551

Fixes # 551.
Did you remember to?

[ x] Add test case(s)
[ x] Update CHANGES.txt

Thanks!


Custom RAG Context Provider

Validations

[x] I believe this is a way to improve. I'll try to join the Continue Discord for questions
[x] I'm not able to find an open issue that requests the same enhancement

Problem
I was going through this to build a custom RAG context provider -https://docs.continue.dev/customize/tutorials/build-your-own-context-provider.
The RAG service that we have provides the generations along with the context. Think of it similar to what perplexity offers - https://docs.perplexity.ai/api-reference/chat-completions
I would like those generations just to be rendered. However I don't see an option of avoiding default LLM generation and using one from RAG service. I understand that context providers are meant to provide additional context. But was wondering if there a way that this can be done.
Solution
No response

Any update / suggestions on this one ?

Hi @roshankarande, and apologies the late reply. I don't think this is possible to do through a context provider, but you may try to integrate this feature as a custom AI model. For example, you could ensure that your RAG provider's API is compatible with OpenAI and then define it in your config.json with "provider": "openai". I'm not 100% confident this is going to work but it's probably your best bet.
Let me know if it works and if you need anything else!
More context:
https://docs.continue.dev/customize/model-providers/openai

Thanks for the response. Is there a way to pass in the context to a custom llm provider as of the parameters. What I mean is I can create a custom provider which queries in the content groups in my RAG system and I would like to pass the name of the content group selected by the user to the custom llm provider to render generations. Kind of hacky but can this be achieved.

I think you can pass arbitrary parameters in the request body of the request (extraBodyProperties) and handle them in your custom LLM. See this and this.


Endpoints options are not populated

Hi!
Thanks for the effort creating this provider. We are currently looking into using it when upgrading to Optimizely 12 but we found some issues when trying it out.
When using the UdpUnicastEventProviderOptions configuration section in appSettings.json, the Endpoints list is always empty even if you specify items. A solution is to, instead of initializing the endpoints property with Array.Empty<UdpEndpoint>(), change it to new List<UdpEndpoint>().
I can create a PR for this.

Happy to know you find it useful, @moleman. Thanks for your suggestions and your PR.
I will look into packing and pushing to the Optimizely Nuget feed.


Project not importable in other Go projects

I want to build a controller that watches for RootSync objects, and tried to add
import configsync "kpt.dev/configsync/pkg/api/v1beta1"

at the top of the controller file.
However, then go mod tidy fails with this error, which seems like it should be fixable (it refers to files in examples which might not have to be bundled with the package, or named like this?):
 λ go mod tidy
go: finding module for package kpt.dev/configsync/pkg/api/v1beta1
go: downloading kpt.dev/configsync v0.0.0-20220719182314-469c8ee811cc
<redacted>/controllers imports
        kpt.dev/configsync/pkg/api/v1beta1: create zip: examples/kubevirt-compiled/clusterrole_kubevirt.io:operator.yaml: malformed file path "examples/kubevirt-compiled/clusterrole_kubevirt.io:operator.yaml": invalid char ':'
examples/kubevirt/cluster/kubevirt.io:operator-clusterrole.yaml: malformed file path "examples/kubevirt/cluster/kubevirt.io:operator-clusterrole.yaml": invalid char ':'

cc @mortent @mikebz

It seems that we could fix this by renaming clusterrole_kubevirt.io:operator.yaml and kubevirt.io:operator-clusterrole.yaml.

I'll take a look

this is fixed:
go  mod tidy
go: finding module for package kpt.dev/configsync/pkg/api/configsync/v1beta1
go: downloading kpt.dev/configsync v0.0.0-20220812180759-434145413977
go: found kpt.dev/configsync/pkg/api/configsync/v1beta1 in kpt.dev/configsync v0.0.0-20220812180759-434145413977


Hercules CI doesn't build PRs from external projects

...but those checks are expected by github, so merging is blocked.
See e.g. https://github.com/nix-community/dream2nix/pull/620 which never triggered a Hercules CI build according to https://hercules-ci.com/github/nix-community/dream2nix but waits for one since I have approved the checks to run.
I have permission to allow the checks, but not to check merge queue and ci settings, so we'll need at least @DavHau. Might be a good idea to ask roberth and/or mic92 about it if we are stuck? Not pinging them until clarified :)

I guess we have to migrate away from hercules. It doesn't seem to work with community contributions.
It won't submit to the merge queue until the checks have passed, but they cannot because hercules blocks.
If I remove the hercules checks from being required, it submits to the queue, but then it also doesn't execute the checks in the queue anymore.
Even if we could make the queue work and execute the checks there, it's still very suboptimal UX. Users should get quick feedback for failing builds on every commit, not just when the PR is submitted to the queue.
Therefore, if that is not possible it doesn't make sense in my opinion to use hercules.

Sound's good to me, but do we have an alternative ready? Back to Github Actions? Trying Garnix? Others?

Even if we could make the queue work and execute the checks there, it's still very suboptimal UX.

Totally agree, getting rid of that would be great :)

opened https://github.com/hercules-ci/support/issues/70

Even if we could make the queue work and execute the checks there, it's still very suboptimal UX.

I agree the the UX isn't great but if you'd like an interim solution something like https://github.com/nix-community/infra/pull/793 should work.
We've also talked a little about deploying buildbot which would support external PRs but I couldn't say when it would be available.

Fixed with the switch to buildbot


Can not install geant4 and root_base packages simultaneously

Solution to issue cannot be found in the documentation.

[X] I checked the documentation.

Issue
Trying to install both geant4 and root_base packages results in a dependency conflict. This is unfortunate, as I was hoping to be able to produce easy instructions for me colleagues concerning how to deploy both Geant4 and ROOT in the same conda environment (in order to build garfield++).
I am not 100% sure, but the conflict might be caused by the krb5 dependency, dragged in through xrootd. Or at least, that was one Issue I managed to track down, but there might be others.
Personally, I would love it if there was a an alternative root_minimal package (mimicking -Dminimal=ON), since the number of dependencies of a full-blown root package is rather sizeable. I am investigating providing my colleagues with a custom conda package recipe for such a minimal package, but it would of course be preferable if it was made available from the real experts :-)
Cheers,
Thomas
Installed packages
geant4 / root_base (but obviously I didn't manage)

Environment info
conda version : 23.7.2
    conda-build version : 3.26.0
         python version : 3.9.17.final.0
       virtual packages : __archspec=1=x86_64
                          __glibc=2.31=0
                          __linux=5.4.0=0
                          __unix=0=0
       base environment : /some/where/miniforge_install/miniforge_installed  (writable)
      conda av data dir : /some/where/miniforge_install/miniforge_installed/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
          package cache : /some/where/miniforge_install/miniforge_installed/pkgs
                          $HOME/.conda/pkgs
       envs directories : /some/where/miniforge_install/miniforge_installed/envs
                          $HOME/.conda/envs
               platform : linux-64
             user-agent : conda/23.7.2 requests/2.31.0 CPython/3.9.17 Linux/5.4.0-155-generic ubuntu/20.04.6 glibc/2.31
                UID:GID : 1001:1001
             netrc file : None
           offline mode : False

Actually, scratch that last remark about root-minimal. Even e.g. garfield needs one or two specific components enabled, so that obviously won't work then. However, it would be great if there was a root_reallybase without the most potentially troublesome components (those which pin dependencies to non-standard values like llvm/clang/cling and apparently also xrootd).


chore: test-python-jenkins to 0.0.28

chore: Promote test-python-jenkins to version 0.0.28

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Update GitHub templates

Here are suggested issue templates for bugs and features, as well as a PR template that will prompt users to enter the issue that the PR is closing.

@alamb @jorgecarleitao

wrong repo!


Remove flash of unrendered content for HMR

Resolves #458, https://www.pika.dev/npm/snowpack/discuss/313
Our HMR engine had a problem with loading files that either took a long time to rebuild, or needed to be sent over a non-local network connection. In both cases, an HMR update caused a flash of unrendered/unstyled content. The root of the issue was our workflow for HMR updates:
dispose() -> fetch updated module -> execute new module -> accept()

This change updates this order so that the dispose call is run after the load, with the accept call called immediately after:
fetch updated module -> dispose() -> execute new module -> accept()

dispose() and accept() are now called synchronously, on the same turn of the event loop, meaning that no flash of unrendered/unstyled content is possible.
Added bonus: dispose() is now always guaranteed to run when an updated module is loaded. This wasn't the case before.

Merged via command line


Confirm we check all the things CSS engines care about

Just saw a great presentation at typolabs 2018 in the CSS wg session by @fantasai with a good list of the font metadata that is used directly by cash layout engines just now at typolabs. When her slides or video is posted we should double check that we are checking all those rhings in a comprehensive and sensible way.
Thank you @fantasai!!

Thanks! Slides posted at http://fantasai.inkedblade.net/style/talks/css-font-metrics/ and video at https://www.youtube.com/watch?time_continue=2&v=zUIMdIF694Q


move json description in dashboard object to graffonnet representation

The Grafana operator supports a grafonnet representation of the dashboards [1]. This is much cleaner and maintainable than using a json blob.
[1] https://github.com/integr8ly/grafana-operator/blob/master/documentation/dashboards.md

Just want to mention that in the past we had briefly considered https://github.com/deliveryhero/grafyaml as well, I think. Definitely onboard with using something that makes it easier to review changes.

@csibbitt will look into that. Grafana operator does not work with grafyaml AFAICT, however STO could do a yaml to json translation


Sharding

Work out the sharing architecture in more detail to allow for discussion with core and eventually PRs.

We will open the new ticket when there is need and a good definition.


only mutate the image Buffer [pr]

buf is UOp in delete_lazy, UOp is immutable. This shouldn't impact correctness of the schedule.

ew it's mutable?


Quality issues with Inpainting

Hello,
the current Inpainting implementation changes the whole color of its surrounding at white tones.
I tried it on Dreamstudio and API and can be easily reproduced.
I tried it with Inpainting 1.0 and 2.0

Edit - more examples:
zoom in and left comes from inpainting result is pretty blurry:

another one:

Other open-source SD server do not have these issues.

Another issue is still the content filter which is known already to have many false positives. Getting this in Inpainting quite often while generating hands for example:

To confirm, you were seeing this through the SDK/gRPC API?
Do you have an example of a mask image that produced these artifacts? (I'm mostly curious if there was a hard line or smooth gradient for the mask edges).

yes it is gRPC I just wanted to send you a mask image but now I doesn't work at all so I made a new ticket: https://github.com/Stability-AI/stability-sdk/issues/174

I can confirm this behavior. Using the Python SDK. I hope it will be fixed


CONTRIBUTING: note license.

This is to be more explicit about the contribution process and license.

We can ignore the test failures as they're completely unrelated - gonna fix those now.


Integrated with ApplicationStarter and added metadata registration to…

… commands

Pull Request Test Coverage Report for Build 589

78 of 123 (63.41%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-3.1%) to 96.581%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

source/Cosmos-CommandLineHandler/CosmosCommandLineHandler.class.st
0
45
0.0%

Totals

Change from base Build 587:
-3.1%

Covered Lines:
4887

Relevant Lines:
5060

💛  - Coveralls


Add client-side language support

If it was possible to run some languages client-side (e.g. x86 assembly using v86), maybe things wouldn't be as expensive. Would that be possible?

This is true, but unfortunately it's nowhere near a general-purpose solution. Some platforms that provide similar features to Riju take this approach, but it generally limits you to a small subset of the available languages---most languages require interesting system dependencies that are difficult or impossible to replicate on the client-side, especially if you want reasonable performance. So insofar as universal language support is a design goal for Riju, it has to be server-side.

This is true, but unfortunately it's nowhere near a general-purpose solution. Some platforms that provide similar features to Riju take this approach, but it generally limits you to a small subset of the available languages---most languages require interesting system dependencies that are difficult or impossible to replicate on the client-side, especially if you want reasonable performance. So insofar as universal language support is a design goal for Riju, it has to be server-side.

Would it be possible for something like x86 assembly?

Sure, of course for specific languages---but even then, server-side execution isn't typically a heavy resource load for languages that can be executed client-side. The expensive ones are also impractical to execute client-side! (E.g., Sagemath and its darned 10 GB download size.)


Export > Triple loader refers to incorrect info

Original author<EMAIL_ADDRESS>(November 15, 2010 01:21:26)
What steps will reproduce the problem?

Start a clean project (or delete current schemas)
Click Export > Triple loader
Watch alert

What do you see?
You haven't done any schema alignment yet,
so there is no triple to export.
Use the Freebase > Edit Schema Alignment Skeleton...
command to align your data with Freebase schemas first.
What's wrong?
I can't find the  "Edit Schema Alignment Skeleton" button. The Freebase button (to the right of "Extensions") has:
Align to Freebase's schemas...
Load into Freebase...

Browse data load details...
Import QA data
Please use labels and text to provide additional information.
I'm running Ubuntu 10.10, SVN revision 1858
Original issue: http://code.google.com/p/google-refine/issues/detail?id=206

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

This should be adapted so that Freebase is not mentioned at all.

@wetneb Is this fixed now, where Freebase is not mentioned any longer ? If so, let's close this.

"Triple loader "and "MQL write" export options should just be removed as they were specific to Freebase.


Added Miro extension with Claude support

#12 This pull request enhances the Miro Chrome extension by integrating support for Claude Sonnet alongside ChatGPT. Key updates include:

Content Script Enhancements: Modified to detect and handle responses from both Claude and ChatGPT, ensuring users receive timely notifications.
Background Script Updates: Implemented logic to manage notifications for Claude, allowing seamless user experience across both platforms.
User Interface Adjustments: Updated the popup UI to reflect the dual functionality, improving usability.

@Shailendra1703 Thank you for your kind words and apologies for the late reply. Actually, I got caught up with some other tasks, I'll look into this and make the necessary adjustments, will update you when it's done 👍

@Shailendra1703 Thank you for your kind words and apologies for the late reply. Actually, I got caught up with some other tasks, I'll look into this and make the necessary adjustments, will update you when it's done 👍

Sure @Kr-Adarsh, take your time btw GPT responses detections are working fine now, but we have some merge conflicts in this PR so we need to look on them.

@Shailendra1703 I've resolved the issues. Should I merge it directly with the main branch, or should I create a new branch?

@Shailendra1703 I've resolved the issues. Please look into it..

Hello @Kr-Adarsh, I'm getting this error while detecting the response of Claude sonnet and also it's not notifying, so can you please check this out?
Also the GPT response detection is working fine with Chrome webrequests so we don't need to use Mutations observers for that case.

@Shailendra1703 I've resolved the issues. Please look into it..

Hello @Kr-Adarsh, I'm getting this error while detecting the response of Claude sonnet and also it's not notifying, so can you please check this out?
Also the GPT response detection is working fine with Chrome webrequests so we don't need to use Mutations observers for that case.

@Shailendra1703 Firstly I'd like to apologise for not sharing consistent updates. I got engaged with some college work and other stuff, but I've been working on this issue since last evening, this error seems to not go; it's working sometimes and then suddenly stops working for Claude. I'm trying different routes to avoid these errors, and I'll get back to you soon with the good news. Thanks for your patience..

@Shailendra1703 I've resolved the issues. Please look into it..

Hello @Kr-Adarsh, I'm getting this error while detecting the response of Claude sonnet and also it's not notifying, so can you please check this out?
Also the GPT response detection is working fine with Chrome webrequests so we don't need to use Mutations observers for that case.

Hii @Shailendra1703 Firstly, I'd like to apologise for not sharing consistent updates. I got engaged with some college work and other stuff, but I've been working on this issue since last evening, this error seems to not go; it's working sometimes and then suddenly stops working for Claude. I'm trying different routes to avoid these errors, and I'll get back to you soon with the good news. Thanks for your patience..

Hey @Kr-Adarsh ,  don't worry buddy I completely understand, take your time and you can ask your doubts anytime. open source is all about community feedbacks and that's how we learn and grow together.
Btw I'm grateful to have you as a contributor on this project.
You can check thd PR's by @mdtausifiqbal, he worked on the calude support via chrome webrequests, it was a very good approach.

@Shailendra1703 I made quite a lot of changes to the code, and it's working for both, but the error in the extension section keeps coming. I'm unable to resolve them.
Here take a look:
https://github.com/user-attachments/assets/0e5e2f68-9ae1-405f-89ce-9478b89aefe3
Errors:

@mdtausifiqbal could you please help on this..

@Shailendra1703, please check the changes; now it's not giving any errors and is working fine for both the AIs'.

@Shailendra1703 I made quite a lot of changes to the code, and it's working for both, but the error in the extension section keeps coming. I'm unable to resolve them. Here take a look:
Screen.Recording.2024-10-24.020719.mp4
Errors:
@mdtausifiqbal could you please help on this..

Hello @Kr-Adarsh, I apologize for my delayed response; I got caught up with some office work. Regarding the error mentioned above, I'm not entirely sure of its cause. Based on my knowledge, I believe it may be due to the unavailability of chrome.runtime. I encountered a similar issue before, which resolved on its own ( #2  ) , so it might be related to the content.js file.

@Shailendra1703, please check the changes; now it's not giving any errors and is working fine for both the AIs'.

Great, I approved your changes and long back ago, unfortunately, I can't merge this PR as the code we have right now is very much similar to our existing code, but I'm really glad to have you as a contributor on this project.
Thanks @Kr-Adarsh ❤

@Shailendra1703, please check the changes; now it's not giving any errors and is working fine for both the AIs'.

Great, I approved your changes and long back ago, unfortunately, I can't merge this PR as the code we have right now is very much similar to our existing code, but I'm really glad to have you as a contributor on this project.
Thanks @Kr-Adarsh ❤

The pleasure is all mine's. This project helped me learn so many new things that I might have skipped.  Thanks @Shailendra1703, if I'm able to I'd love to contribute on your upcoming projects.🙌🏻❤

@Shailendra1703, please check the changes; now it's not giving any errors and is working fine for both the AIs'.

Great, I approved your changes and long back ago, unfortunately, I can't merge this PR as the code we have right now is very much similar to our existing code, but I'm really glad to have you as a contributor on this project.
Thanks @Kr-Adarsh ❤

The pleasure is all mine's. This project helped me learn so many new things that I might have skipped. Thanks @Shailendra1703, if I'm able to I'd love to contribute on your upcoming projects.🙌🏻❤

Sure, would love to collaborate.


Rework internal processing to use Artifacts and a "state machine" like approach

Whilst wrestling with the more complicated cases introduced by trying to extend Fab to handle C source it emerged that perhaps the existing approach of instantiating Tasks as part of the descent and having the descent extended by their results was going to struggle with more complex examples.
So after much thought and discussion here we present a completely different approach which moves much of the processing logic inside of the queue system, via a new "Engine" that works like a state machine.  A new Artifact object which represents a file on disk with some attached details becomes the new work unit which passes through the queue and is handled by the Engine.  This also brings the pre and post analysis tasks together so that we no longer have the artifical barrier between analysing the source and beginning compilation.
Unfortunately it's quite a large and destructive change but hopefully worthwhile

Marking this as ready - I do think it is going to need some further work; the biggest emerging problem with it is going to be handling errors and other situations (as an example - at the moment specifying a non-existent target results in a lockup)


Tranche needs better doc

Is the need for developer doc or for end-user doc? (Can we maybe differentiate the tags for the two types?)

good point. dev doc.
Added a new label: UserDoc

closing this. vqsr is being redone


Move .modal-scrollbar-measure styles into Modal.prototype._getScrollbarWidth

Is there any reasons that styles for .modal-scrollbar-measure are in Bootstrap SCSS?
As they are not related to modal styles, I'd suggest to move them into Modal.prototype._getScrollbarWidth because only there are used, and are directly related to that functionality.

Hi @iamandrewluca,
Personaly I'm not a big fan of adding inline CSS with JS, moreover when it's not a dynamic CSS.
/CC @twbs/js-review

Yeah, I don't like this approach either.

Currently it's used only in our Modal components

@Johann-S If this is a no n, I can just reuse _getScrollbarWidth in tests, redefining that function in tests it's not so good. I'll move styles back in SCSS.

yep seems good to me 👍

Closing since this seems like a no-go from us and OP has an answer :).


Only part of the name string is focused and has a background color if select the custom environment which has a long name

Storage Explorer Version: 1.35.0-dev (98)
Build Number: 20240614.1
Branch: main
Platform/OS: Windows11/Windows 10/Linux Ubuntu 22.04 & MacOS Sonoma 14.5(Apple M1 Pro)
Architecture: arm64/x64/x64/arm64
How Found: Exploratory testing
Regression From: Not a regression
Steps to Reproduce

Open the connect dialog -> Click 'Subscription -> Custom Environment'.
Click 'Manage custom environments...' -> Click 'Add'.
Add one custom environment with a long name.
Select the custom environment -> Drag the scrollbar.
Check whether the entire custom environment name is focused and has a background color.

Expected Experience
The entire name is focused and has a background color.

Actual Experience
Only part of the name string is the focused and has a background color.

Verified this issue on the main build 20240716.5. Fixed.


Update Maven URL in README

Can you add a Test stanza now ?

Once my change lands, @asfalcone we can re-trigger the presubmit checks.


Permission to let certained players join when slots are full

Is your feature request related to a problem?
I want to let staff and content creators still be able to join my server when its full (slots)
Describe the solution you'd like.
I would love a permission that let people still join the server.
Describe alternatives you've considered.
I know some plugins have this feature, but I really don't want to add essentials only for this and it sounds like a really good Purpur feature.
Also Roan on Discord said that this is possible for OP's but I don't really want to give content creators and all staff op so thats not an option.
Agreements
Please agree to the following.

[x] I have searched for and ensured there isn't already an open issue regarding this.
[x] I have ensured the feature I'm requesting isn't already in the latest supported Purpur build.

In extenion of this
It would be cool if basically anything that requires op could be turned into a permission
E.g. using structure blocks


Improve installation of segment-anything

The installation of segment-anything currently requires the user to have "git" installed.
To move forward, revisit how the package is installed by installing from a remote url^1 (for example pip install segment_anything@https://github.com/facebookresearch/segment-anything/archive/refs/heads/main.zip

Git requirement is removed for segment-anything installation. Thanks for the suggestion.


Fix for closing the geneset modal from OncoMatrix and GEC

Description
Thanks to Craig for fixing the modal issue with closing by clicking on the Close button or X icon. Additional fixes made to failing PP tool-wrapper unit tests.
Checklist

[ ] Added proper unit tests
[ ] Left proper TODO messages for any remaining tasks
[ ] Scanned for web accessibility with aXe, and mitigated or documented
flagged issues

Screenshots/Screen Recordings (if Appropriate)

The code changes look fine.

@craigrbarnes  Are you able to approve and merge to develop? Not sure if I needed to do anything else for this PR to get merged.

The code changes look fine.

@craigrbarnes Are you able to approve and merge to develop? Not sure if I needed to do anything else for this PR to get merged.

I'm trying to figure out why the pipeline is stalled, but I merged the PR today regardless of whether it's still hung.


refactor logging to make idiomatic use of ruby log levels

This PR proposes a change to the logging levels to be more idiomatic and have less conditional checks on environment variables.
The default log-level will be set at WARN and any calls to logger.warn will be printed.
If DEBUG or FASTLANE_CI_SUPER_VERBOSE are set, then the log-level is lowered to the most verbose setting DEBUG. The difference being that FASTLANE_CI_SUPER_VERBOSE will have extra thread IDs.
Logging about normal system operation should be done with logger.info

@snatchev this is great, thank you!

did the rename as suggested by https://github.com/fastlane/ci/pull/148#discussion_r169216426

🎉


Update gt-letterhead.sty

Fixes layout issue with department name placed right onto foot.png.

Thanks!


OmniSharp stopped working after update to 1.1.4

Environment data
dotnet --info output:

.NET Command Line Tools (1.0.0-preview1-002702)
Product Information:
Version:     1.0.0-preview1-002702
Commit Sha:  6cde21225e
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.10586
OS Platform: Windows
RID:         win10-x64

VS Code version: 1.2.0
C# Extension version: 1.1.4
Steps to reproduce
dotnet new
dotnet restore
code .
Start typeing some code for autocomplete
Expected  behavior
Autocomplete work.
Actual behavior
No autocomplete, exception in omnisharp log:

[INFO] Starting OmniSharp at 'c:\Users\user\Desktop\Nowy folder'...
[INFO] Started OmniSharp from 'C:\Users\user.vscode\extensions\ms-vscode.csharp-1.1.4.omnisharp\OmniSharp.exe' with process id 8628...
OmniSharp: -s c:\Users\user\Desktop\Nowy folder --hostPID 4980 dnx:enablePackageRestore=false --stdio
[INFORMATION:OmniSharp.Startup] Omnisharp server running using Stdio at location 'c:\Users\user\Desktop\Nowy folder' on host 4980.
[INFORMATION:OmniSharp.DotNet.DotNetProjectSystem] Initializing in c:\Users\user\Desktop\Nowy folder
[INFORMATION:OmniSharp.DotNet.DotNetProjectSystem] Auto package restore: True
[INFORMATION:OmniSharp.DotNet.DotNetProjectSystem] Update workspace context
[INFORMATION:OmniSharp.DotNet.DotNetProjectSystem] Update project c:\Users\user\Desktop\Nowy folder
[INFORMATION:OmniSharp.DotNet.DotNetProjectSystem] Add project c:\Users\user\Desktop\Nowy folder\project.json => dfcbe7ac-86d0-45c7-87d3-30ecdd58ed53
[INFORMATION:OmniSharp.DotNet.DotNetProjectSystem] Resolving projects references
[INFORMATION:OmniSharp.DotNet.DotNetProjectSystem]   Processing [ProjectState] Nowy folder/.NETCoreApp,Version=v1.0
[INFORMATION:OmniSharp.DotNet.DotNetProjectSystem]     Added 74 and removed 0 file references
[INFORMATION:OmniSharp.DotNet.DotNetProjectSystem]     Added 1 and removed 0 documents.
[INFORMATION:OmniSharp.MSBuild.MSBuildProjectSystem] No solution files found in 'c:\Users\user\Desktop\Nowy folder'
[INFORMATION:OmniSharp.ScriptCs.ScriptCsProjectSystem] Detecting CSX files in 'c:\Users\user\Desktop\Nowy folder'.
[INFORMATION:OmniSharp.ScriptCs.ScriptCsProjectSystem] Could not find any CSX files
[INFORMATION:OmniSharp.Startup] Configuration finished.
[ERROR:Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware] An unhandled exception has occurred: The type initializer for 'OmniSharp.CSharpSyntaxContext' threw an exception.
[INFORMATION:OmniSharp.Middleware.LoggingMiddleware] /autocomplete: 500 67ms
[ERROR:Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware] An unhandled exception has occurred: The type initializer for 'OmniSharp.CSharpSyntaxContext' threw an exception.
[INFORMATION:OmniSharp.Middleware.LoggingMiddleware] /autocomplete: 500 12ms
[INFORMATION:OmniSharp.Middleware.LoggingMiddleware] /v2/getcodeactions: 200 824ms

It was working yesterday before update to 1.1.4 (1.0.11 if I remember right).

The same for me.

@troydai -- do you know anything about the exception being thrown in the log above?

FYI -- I can reproduce the problem. Thanks for the heads up!

I have no idea now. But I can take a look now.

Can't repo on mac. But the original repo is on Windows.

No worries. I'm looking too.

@troydai, note that the extension is using v1.9-beta4 of OmniSharp.

I can't repro on OSX either. One other thing @troydai, it's using the net451 build of v1.9-beta4 on Windows.

I can repo it. I suspect it is caused unmatched dotnet and project model.

Looks like the problem's been there awhile, but got fixed at some point. I sync'd back to v1.9-beta4 and rebuilt OmniSharp and can repro. I can't repro with the latest dev branch though.

I'll take a look at updating OmniSharp in the extension

FWIW, it looks like the class in question, CSharpSyntaxContext does a bunch of reflection calls in its static constructor.

Yup -- it fails right here: https://github.com/OmniSharp/omnisharp-roslyn/blob/dev/src/OmniSharp.Roslyn.CSharp/Workers/Intellisense/CSharpSyntaxContext.cs#L438

OK. I've pushed a new release (1.1.5) to the marketplace that fixes the problem. @sec and @PiterGoCompany, could you update the C# extension from within Visual Studio Code and let me know if you're up and running again? Thanks!

The new release seems to work for me.

Also working here. Thanks.

1.1.5 also working here

I think we can close this one then.

Yup! Thanks all for reporting this so quickly and helping us get this fixed.


Add the missing .htaccess file which is causing some issue on docker.

Added the missing .htaccess file and created an entry to copy it to /var/www/html. Please proof and let me know if something wrong.
Thank you very much.
Christian

Thank you for your feedback. I appreciate this; I changed everything like you mentioned and checked-in again.

Perfect @ChrisRo89! Thanks a lot for your contribution! 🎉


Improve inlay hinting for types

Add hints for types in for loop expressions.
Resolve types for every tuple parameter.
Refactor the code.

seems reasonable!
bors r+


Znode long name when using Zookeeper as service registry

[x] I have searched the issues of this repository and believe that this is not a duplicate.
[x] I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.1
Operating System version: CentOS 7.5
Java version: 1.8.202

Steps to reproduce this issue
Simply using Zookeeper for the service registry.
Register a service.
Actual Result
When browsing Zookeeper Znodes, we see the service providers is stored in a ZNodes with long name, such as
/dubbo/com.test.dubbo.TestDubboPoc$MyService/providers/dubbo://<IP_ADDRESS>:20880/com.test.dubbo.TestDubboPoc$MyService?anyhost=true&application=first-dubbo-provider&default.deprecated=false&default.dynamic=false&default.register=true&deprecated=false&dubbo=2.0.2&dynamic=false&generic=false&interface=com.test.dubbo.TestDubboPoc$MyService&loadbalance=roundrobin&methods=writeFile,getData&optimizer=com.test.dubbo.SerializationOptimizerImpl&payload=2147483647&pid=10894&register=true&release=2.7.1&revision=version1&serialization=avro&side=provider&timestamp=1556969914059&version=version1
Expectation
Is it possible to manage the znode name, such as providing a SHA hashing ID?

But the problem is I don't think there's a way to retrieve the original value from a hash ID.


Dart VM options to compiled dart binary

Hi,
I want to pass --old_gen_heap_size= option to a dart program compiled by dart compile exe.  Is there a way to do it?
Thanks.

//cc @mit-mit is this something we want to support, currently there is no way to distinguish vm command line options from the application command line options when using a native executable generated from dart2native.

Hmm, I would have expected that those flags were passed during compilation and then "set" in the output. Is that possible, or do the flags just not work at all for compiled code?

These flags do work for compiled code it is just that we don't have a means of passing them down. We encode only a few key features in the AOT snapshot that are read back but not all the VM flags


Undefined error in Block component

In your plant-app, while learning as soon as I import {Block} from components I get the following error on snack.expo project:
Device: (101:380) Invariant Violation: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined.
This error is located at:
in App
in RCTView
in RCTView
https://snack.expo.io/@alibth/plants

@iloveyii Thanks for opening this issue. Usually this should work, but I double check this snack and probably the error is in the App setup, don't know exactly.
Try this: import Block from './components/Block';
Also please copy the theme.js because the Block component is using it.


[Feature Request] [tw_gcal_sync] Support virtual tags

I've tried to synchronize tasks using virtual tag +DUE but I don't know if it was implemented.
tw_gcal_sync -c warrior -t "DUE"

versions
tw_gcal_sync, version 1.2.1
taskwarrior 2.6.2

Not supported by taskw but it should be automatically fixed once we switch to tasklib - see #65

Hi @amiroslaw
This should now be supported across all the apps in this repo that interact with Taskwarrior. Use the custom taskwarrior filtering in order to specify that you don't want to synchronize tags of a particular tag. To include tags by a virtual tag in the sync, you have to specify that virtual tag via a custom TW filter. For example:
tw_gtasks_sync  -l some_google_task_list -t tw_tag_to_include  -f "+OVERDUE"

This feature should work on latest master - commit https://github.com/bergercookie/syncall/commit/0893f12870aff5242118993c70f61bbfc85544cb - and should make its way to a pypi release in the coming week(s)


fixed cloud build issue for pytz

Could we try updating the requirements.txt file instead of patching the test script?


Support Laravel 11 and more

Hi, this pull request should close #6.
It also makes use of some PHP 8 features.

Thanks for the pull request @matthiez! Could you take a look at the error Root composer.json requires php ^8.2 but your php version (8.1.2) does not satisfy that requirement? The changes lgtm.

Thanks for the pull request @matthiez! Could you take a look at the error Root composer.json requires php ^8.2 but your php version (8.1.2) does not satisfy that requirement? The changes lgtm.

Thanks,
I just specified the PHP version in the workflow. I believe this should do the trick.

Thanks! I believe the GitHub action is still using its default installed PHP version (8.1.2) and is not using the versions specified. I'll merge and adapt the workflow accordingly :)


octree converted point clouds errors while training

Hi,
I tried using unorganised point clouds and I got this error at line 70 of OctreeConvolutionMM.lua
invalid input size, self.nInputPlane=1, input:feature_size()=3
I assume it's because unorganised point clouds do not have positional information of the points and hence are 1 * numofpoints instead of height * width
So I tried I using organised point clouds, and the code errors out giving before even loading the octrees completely.
feature_size of path 1 does not match in octree_read_batch_cpu (3, 1)
Both of them are related to the feature size and input plane mismatch which pushes me to believe that I'm doing a mistake while creating the octree.
I'm using python pcl to load point clouds and I convert them into numpy arrays before using create_octree_from_cpu.
import pcl
path = "./organisedpointclouds/cloud1.pcd"
p = pcl.load(path)
xyz = cloud
features = np.ones_like(xyz)
oc_from_pcl = pyoctnet.Octree.create_from_pc(xyz, features, vx_res, vx_res, vx_res, normalize=True,
n_threads=n_threads)
for idx in range(3):
xyz[..., idx] = (xyz[..., idx] - xyz[..., idx].min()) / (xyz[..., idx].max() - xyz[..., idx].min())
xyz[..., idx] *= vx_res
oc_from_pcl = pyoctnet.Octree.create_from_pc(xyz, features, vx_res, vx_res, vx_res, normalize=False,
n_threads=n_threads)
savePath = "./octrees/octree1.oc"
oc_from_pcl.write_bin(savePath)
cloud.zip

I am not sure what you mean with organised vs. unorganised point clouds?
However, I guess you can get rid of the first error, if you use features = np.ones((1,xyz.shape[0]), dtype=np.float32) instead of  features = np.ones_like(xyz), given that xyz has the right shape, ie Nx3.

I got initially the same error:
invalid input size, self.nInputPlane=1, input:feature_size()=3
but then when I used features = np.ones((1,xyz.shape[0]), dtype=np.float32) I get the error:
[program started on Mon Dec 17 11:44:11 2018]
[command line arguments]
[----------------------]
[INFO] start_epoch=1
[INFO] train epoch 1, lr=0.001
Segmentation fault (core dumped)

It should be features = np.ones((xyz.shape[0],1), dtype=np.float32)


Team Lead Can Create Requests

Follows #1821
Team leads should be able to create a new request within an itinerary they manage.
We should be careful to ensure that a team lead can only create requests against itineraries they are currently set as team lead for.
@schuback - With regards to this requirement, we discussed this working for canvasing style activities. The safest option seems to be to create the request bound to the itinerary the volunteer leads. However, in cases where the canvasing happens on day 1 and then those requests need assignment to suitable deployment itineraries at a later day, this flow breaks down.
In a case where the request is added and immediately serviced, adding it to the same itinerary makes sense. However for the future deployment flow, would it be better to add it to the event in general, which would allow an admin to schedule it appropriately? In this case, it's possible that once added, the team lead will not longer be able to view the request since it will be outside the bounds of their access if not assigned to an itinerary they manage.
Could you help confirm all possible flows we might need here and how this is best implemented?

I'm working on a pre-requisite PR to support easier authorization of such actions

@stevejgordon @tonysurma This can be closed as per my comments in #1787.


set env vars externally

DigitalOcean has the Supabase creds stored, so no need for the env file which it cannot find since we don't want to put it in the Github repo

Looks good to me!


Updated setting-up-your-development-environment.md to use the latest dependencies

The dependencies in the original document do not work with the example code. This pull request updates these to the latest versions I needed to use to get examples in the tutorial working.

@robertprice Hi Robert, thanks for your PR and suggestion. I had this reviewed internally, and the docs were updated for this issue via https://github.com/mendix/docs/pull/2036. So I will close this PR.
Cheers,
Adam


A request to add Wine-Proton

Wine-Proton builds are made by Kron4ek -> https://github.com/Kron4ek/Wine-Builds
They are similar to Wine-GE which can be used outside of Steam.
Links from Kron4ek GitHub-repo:
wine-6.3-8-proton-amd64.tar.xz
wine-5.13-6-proton-amd64.tar.xz
Older links can be downloaded from MEGA Cloud:
wine-5.0-9-proton-amd64.tar.xz
wine-4.11-12-proton-amd64.tar.xz
wine-4.2-8-proton-amd64.tar.xz
wine-3.16-9-proton-amd64.tar.xz
wine-3.7-8-proton-amd64.tar.xz
You can add them to a GitHub repo, or I will do that if you want.

There are older games @ protondb.com that only have good reports under Proton 5.0 or Proton 4.11. The idea is the user check the compatibility of the game @ protondb.com then use the same version to run the game.
Sample of games that run fine under older Proton versions:
https://www.protondb.com/app/339340 -> Works fine under Proton 5.0
https://www.protondb.com/app/368370 -> Works fine under Proton 4.11

We don't will implement a compatibility checker and adding support for older version which are not provided by the release section of a github repository are hard to implement. Also proton is not really working outside of steam. If Wine-proton is meant to work outside of steam aswell, i will add the github repository nothing more.

That is fine. Thanks for your help.

Ok i can't implement that without alot of changes. He is splitting each part in seperate archives instead in one.
Thought it is just one archive like Wine-ge which contains everything.
If you familiar with Typescript, maybe implement it, but for now i will drop it.
Or you could create a bundle archive same structure like wine-ge and upload it in a seperated github repository.

I have no prior experience with Typescript, and I do not know how to create a bundle achieve like wine-ge, so there is nothing I can do to help. Thanks anyway.


[Feature request][V2sink-StarRocks/Doris] Ensure exactly-once semantics

Search before asking

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

Description
To ensure accurate one-time semantics for reading data sources to write StarRocks/Doris(or any other data destination database for this case), a policy can be adopted that writes only when Seatunnel is checkpoint;
There is a question about the existing configuration of StarRocks sink. Seatunnel ensures exactly once by checkpoint, but StarRocks sink can be configured with batch_max_rows, batch_max_bytes,  batch_interval_ms and other parameters; If both exist at the same time, it cannot be guaranteed  exactly once；
This is even better: when the exactly-once option is explicitly configured, Seatunnel is written if and only if it is checkpoint, and the batch_* configuration in the sink section should be invalidated automatically even if configured
Usage Scenario
增量读取jdbc，写入StarRocks
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

I found some pull request about this feature https://github.com/apache/incubator-seatunnel/pull/3850. Only write data when checkpoint is a way to ensure exactly-once. But I'm afraid this will cause OOM exception, because this may let sink save more data in memory. Some times the source read is very fast(such as File Source Connector), If the sink save data in memory, OOM is almost inevitable.


Gregorian Events Not Updating

We discussed this on Discord but here's a gif to jog your memory, idk how to describe it but the events are all hinky.

This should be fixed in the latest release.


List more than one generic product for PPU formulation swaps

We only list one product as being prescribed generically when we have an item with a formulation swap e.g.
https://openprescribing.net/ccg/06Y/0403040W0AAAEAE/price_per_unit/?date=2017-06-01
This lists Venlafaxine_Cap 150mg M/R as generic, but isn't listing Venlafaxine_tab 150mg M/R
If you go to the page for the tabs: https://openprescribing.net/ccg/06Y/0403040W0AAAKAK/price_per_unit/?date=2017-06-01 it still lists only the caps as generic

Appears to be fixed


Velocity Modifiers

This PR adds velocity modifiers to replace drag and acceleration.
A new modifier "Noise" adds a simple sinusoïdal 2D noise.
A new example velocity.rs replaces drag.rs by illustrating Constant, Drag and Noise modifiers.
There is also a new PrecalculatedParticleVariables struct used in systems.rs when applying the modifiers to the particles transforms: It is handful to avoid doing multiple normalize() or length() on velocity when they are used in multiple modifiers.

Let me know what you think of this !

As we mentioned previously, a VectorOverTime was needed.
And with a VectorOverTime, we want to be able to have a constant, a lerp, but also a gradient-like value/key pair to animate the vector over the particle's life.
So I changed the Gradient struct to a "Curve" struct that is generic and is used as Color, Vec3 and f32. This change allow us to animate Vec3 and f32 with keys, when it was only possible for Color. Plus we can now use a VectorOverTime as a VelocityModifier, its more freedom for the user !
The name "Curve" was inspired by Unreal's "Cascade" particle system editor, that features the same value/key pair animation method, and "Gradient" wasn't relevant for f32 and Vec3 values.
I kept the ValueOverTime/ColorOverTime/VectorOverTime enums implementations separated because they probably won't handle the same variants: like Sin(SinWave) for ValueOverTime for example. Such a variant wouldn't make any sense with Vectors or Colors. Also we might want to rotate vectors, or change HSV for colors, etc... I ended up thinking that these should not be in the same enum generic type despite all having some common variants.
I updated the examples and "fixed" shape_emitter.rs where it was using a Curve but its lifetime + max_distance didn't allow the particles to finish their lifetime, and by extension their Curve. I lowered the lifetime, and now we can see them nicely fade.
Let me know what you think !

Fantastic!


Calling XCGLogger.logln directly

Hi,
I used to call XCGLogger.logln directly from a wrapper of another (C++) logging library.
But now when its arguments are of StaticString type and I can't call it any more passing my String arguments, as it seems impossible to convert from String to StaticString.
(XCGLogger 3.5.1)
Any suggestions what can be done?

@emovla Can you send me a small sample project? Though, since using StaticString was just supposed to be a performance tweak, it may be easier to just change back to String.

Well entire project will be difficult as this is called from C++ code, but the essense is I’m passing the original file and line from the C++ logging macros into this wrapper class that calls XCGLogger:
@objc class LoggerWrapper : NSObject {
private let logger = XCGLogger.defaultInstance()
func log(message: String, fileName: String, line: Int32, severity: BWNLogLevel) {
var xlevel: XCGLogger.LogLevel
switch (severity) {
case BWNLogLevel.Verbose: xlevel = .Debug
case BWNLogLevel.Info: 	xlevel = .Info
case BWNLogLevel.Warn: 	xlevel = .Warning
case BWNLogLevel.Error: 	xlevel = .Error
default:
xlevel = .Warning
}
  self.logger.logln(xlevel, functionName: "", fileName: "", lineNumber: Int(line), closure: { return message })

}
}
Cheers, Emil

On Sep 13, 2016, at 7:11 AM, Dave Wood<EMAIL_ADDRESS>wrote:
@emovla https://github.com/emovla Can you send me a small sample project? Though, since using StaticString was just supposed to be a performance tweak, it may be easier to just change back to String.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/DaveWoodCom/XCGLogger/issues/152#issuecomment-246568473, or mute the thread https://github.com/notifications/unsubscribe-auth/AEieDUAl5G6_zRAV4t8uwjmIwewslnLKks5qpiJYgaJpZM4J67xc.

I've pushed an update that should solve this for you. Right now it's on the master branch only. I'll have to add it to the swift_3.0 later. For some reason CocoaPods is having issues and won't lint the podspec. I have to crash for a bit and then will come back and figure that out...

Many thanks
Emil

On Sep 13, 2016, at 5:52 PM, Dave Wood<EMAIL_ADDRESS>wrote:
I've pushed an update that should solve this for you. Right now it's on the master branch only. I'll have to add it to the swift_3.0 later. For some reason CocoaPods is having issues and won't lint the podspec. I have to crash for a bit and then will come back and figure that out...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/DaveWoodCom/XCGLogger/issues/152#issuecomment-246707973, or mute the thread https://github.com/notifications/unsubscribe-auth/AEieDXHPo15dJ6rGjuHIwKySr4Aqqnulks5qprihgaJpZM4J67xc.

I've pushed an update that should solve this for you. Right now it's on the master branch only. I'll have to add it to the swift_3.0 later. For some reason CocoaPods is having issues and won't lint the podspec. I have to crash for a bit and then will come back and figure that out...

@DaveWoodCom just a desperate attempt without looking into details - perhaps it is related to CocoaPods#5841: Fix linting on Xcode 8? Maybe adding a .swift-version file with 3.0 contents could fix this? Just brainstorming loud without understanding any of this, please take with a grain of salt 😄

This is now on the swift_3.0 branch.
@dusek And for the record, the linting issue was just me being tired and forgetting to change the podspec to include the Objective-C files.


OS X Terminal cannot open

VSCode Version: 1.1.1
OS Version: os x 10.11.5

Steps to Reproduce:

Add User Key Binding

  {
    "key": "ctrl+shift+t",
    "command": "workbench.action.terminal.toggleTerminal"
  }

Trigger

No handler found for the command: 'workbench.action.terminal.toggleTerminal'. An extension might be missing an activation event.

The terminal is currently only available in the Insiders build, you can download it here code.visualstudio.com/insiders


fix: support azure policy

这个 PR 实现什么功能/修复什么问题:
Azure 策略同步及应用
是否需要 backport 到之前的 release 分支:
/area region
/cc @swordqiu @yousong

/lgtm

Codecov Report

Merging #5749 into master will decrease coverage by 0.00%.
The diff coverage is 7.00%.

@@            Coverage Diff             @@
##           master    #5749      +/-   ##
==========================================
- Coverage    6.97%    6.96%   -0.01%
==========================================
  Files         635      638       +3
  Lines      107918   108175     +257
==========================================
+ Hits         7525     7537      +12
- Misses      99809   100056     +247
+ Partials      584      582       -2

Flag
Coverage Δ

#aFlag
6.96% <7.00%> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/cloudprovider/cloudprovider.go
1.63% <0.00%> (-0.03%)
:arrow_down:

pkg/compute/models/guests.go
0.56% <ø> (ø)

pkg/compute/models/policy_definition_resource.go
0.00% <0.00%> (ø)

pkg/compute/models/purge.go
0.00% <0.00%> (ø)

pkg/httperrors/consts.go
0.00% <ø> (ø)

pkg/httperrors/errors.go
2.08% <0.00%> (-0.05%)
:arrow_down:

pkg/compute/models/policy_definition.go
5.62% <5.62%> (ø)

pkg/compute/models/policy_assignment.go
16.98% <16.98%> (ø)

pkg/cloudcommon/cronman/cronman.go
46.05% <0.00%> (-2.64%)
:arrow_down:

... 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 4c85b2e...6ba4d43. Read the comment docs.

/lgtm


split.h: Reworded API documentation

Signed-off-by: “Rico<EMAIL_ADDRESS>

Thanks 😄


Tokyo Ghoul: Jail [PCSG00615]

App summary

App name: Tokyo Ghoul: Jail (東京喰種トーキョーグール JAIL)
App serial: PCSG00615
App version: 1.00

Vita3K summary

Version: 0.1.3
Build number: 2269
Commit hash: https://github.com/vita3k/vita3k/commit/9cb2063d50ae5fe0603594ea6122069cf8d67510
CPU backend: Dynarmic

Test environment summary

Tested by: WhiteRonin
OS: Windows 10
CPU: Intel i5 11th Gen @2.4GHz
GPU: Intel Iris Xe integrated graphics
RAM: 8 GB

Issues

Minor drop in audio quality while ingame.
Note*: The game is playable, but I haven't completed it so I would like to say the game is ingame+. It's a visual novel.
Screenshots

Log
vita3k.log
Recommended labels

Ingame+ or playable

@FruitPunchSamuraiG0700 sorryy, you have create double issue, update with last build in other already exist


useage (and doc improvement)

Following the README is pretty clear until section2 which states

The configuration (org.pac4j.core.config.Config) contains all the clients and authorizers required by the application to handle security.

and then cites a lot of code with no context (no function name, class, file name, etc.). I don't understand what to do with this code or what the sentence quoted above means. Can you please explain?

@eroux in order to configure pac4j, you need to provide a Config object (like this).
The code simply shows examples of Config object, this is specific to pac4j, not jax-rs-pac4j, so you can do it wherever you want as long as you pass the config object to the various Features and Providers that you register into the JAX-RS resource.
Is this clearer?

It is true that the documentation assumes that the reader is familiar with JAX-RS and pac4j, if you have ideas of improvements, I'm interested, but I don't have the time to write much more documentation right now :)

Thank you! Not really clerarer I'm affraid... I think the doc about the Config object is http://www.pac4j.org/docs/config.html but even with that I'm really puzzled on where it is used...? I'm familiar with JAX-RS but not with pac4j. In fact I'm trying to have a very little demo working and it's really complex... is there an software somewhere that uses pac4j and that I could get inspiration from?

do you plan to use it exclusively with JAX-RS?

(i.e. not with dropwizard)

yes, only JAX-RS, but I guess I can inspire from the code of the dropwizard app?

ould you show me how you setup your jax-rs resources and features? Which container are you using (jersey, resteasy, grizzly, jetty, etc)?
If you give me that, I will include pac4j in it and we can add it to the documentation as a self-contained example :)

That's very kind, thanks a lot! I only have a boilerplate now: https://github.com/BuddhistDigitalResourceCenter/auth-api I'm trying to figure out what to do to have, say /login to take a login/pass and spit a jwt token... (see the design doc of the repo) but I should probably start with more simple things!

ok, I will get back to you soon :)

For the record, I answered on the mailing list: https://groups.google.com/d/msg/pac4j-users/qjorvxOmSrk/mP4E6dgTCwAJ

So, if you are interested to document this use case, you submit a PR :)
But before let's see ho it unravel, I opened two related issues in pac4j so maybe some better solutions will be found via discussion: pac4j/pac4j#938 and pac4j/pac4j#939

One of the most glaring issue is that the code fragments provided in the documentation are not correct/compilable anymore.
The code fragment are based on an old version where the config was passed to JaxRsContextFactoryProvider, Pac4JSecurityFeature, etc as a constructor argument.
This has been changed and is not an option anymore.
So the reader is left trying different things and hope (without success in my case), that the jax-rs magical features/providers/context auto-weaving will finally pick up the config in a correct way.

@bbarroux good point, any way for you to provide a PR to clarify or even simplify (if tests already exists that illustrate some points) the README?
Or at least a clear list of what is working and what is not?
Thanks :)

I'm closing this, feel free to open a PR directly

I don't understand why this issue was closed. Many parts of the readme are still not correct/compilable, e.g. most code in the JAX-RS configuration section. Also, the dependencies section seems to be outdated (the latest version for org.pac4j/jax-rs-pac4j is 2.3.0, I guess this should point to org.pac4j.jax-rs/core instead).
Personally, such documentation issues certainly don't increase my trust in this library and, after a day of struggling to get this working for my project, I won't try any further until they are resolved.

Having a good/accurate documentation is a permanent issue. No need to create one for that.
This is an Open Source project, not a paid software. If the documentation is not accurate, it's ALSO up to you to help fixing the documentation.