algorithms whose intended purpose is to run forever

From<EMAIL_ADDRESS>on July 25, 2009 09:33:14
In an algorithm specifying an operating system, there is no specified
output. Operating systems are intended to run forever (e.g., having an
outer loop while(TRUE) do X, where the loop precondition is always true).
Theoretically, these correspond to non-halting Turing machines.
At a smaller computational scale, this is also true of the fetch-execute
cycle.
Even though no actual concretization of such algorithms run forever, the
intent to have them run forever is clearly indicated in the plan.
Original issue: http://code.google.com/p/information-artifact-ontology/issues/detail?id=32

From<EMAIL_ADDRESS>on July 07, 2011 16:21:49
Current definition of algorithm reads "A plan specification which describes inputs, output of mathematical functions as well as workflow of execution for achieving an predefined objective. Algorithms are realized usually by means of implementation as computer programs for execution by automata."
Would you be able to suggest an update to take into account algorithms with no output?
Owner<EMAIL_ADDRESS>

From<EMAIL_ADDRESS>on July 07, 2011 18:57:39
I thought that many (or most) definitions "algorithm" define them as
being "effective", which in turn means they will halt and give an
answer.

From<EMAIL_ADDRESS>on July 07, 2011 19:22:53
Interesting.  So, an algorithm for an operating system has no output.  But what is meant by "output" here?

From<EMAIL_ADDRESS>on July 08, 2011 11:27:51
I have to admit that I was not thinking about OS algorithms when reading the current definition. I found a list on wikipedia, that seems to be pretty exhaustive and may help us address all cases: http://en.wikipedia.org/wiki/List_of_algorithms Note that their definition of algorithm, "an algorithm is an effective method expressed as a finite list of well-defined instructions for calculating a function.
Starting from an initial state and initial input (perhaps null), the instructions describe a computation that, when executed, will proceed through a finite number of well-defined successive states, eventually producing "output" and terminating at a final ending state." indicates that there is an "eventual" output, and that we expect termination in a final ending state - though it is not said when that termination happens.

From<EMAIL_ADDRESS>on July 08, 2011 12:01:02
The list of named algorithms from wikipedia is not an exhaustive list of algorithms...it is just an exhaustive list of algorithms that solve interesting problems in computer science.  The class of algorithm types is not restricted to just those types (e.g., sorting algos, search algos, etc.).
In fact, there is a large class of algorithms intended to maintain the state of a system rather than produce output or compute a mathematical function.  While these could be reduced to Turing machines, automata, or any number of formalisms that do produce output, I believe the reduction is not the same as the (original) algorithm.
Also, if by "effective" we mean simply "having effects", then I don't see why algorithms that do not halt can't also be effective.  There is a joke that the original shampoo instructions printed on the bottle "lather-rinse-repeat" produces an infinite loop (i.e., you would never stop washing your hair)...but even if this were taken literally the shampoo would have an effect on your hair with each iteration.
I still think the fetch-execute cycle / Operating System is still a good example of an algorithm that is effective by not halting.

From<EMAIL_ADDRESS>on July 08, 2011 12:30:22
I don't see that the implication that if an algorithm is intended to run forever means that there is no intended output. In the case of operating systems there are definitely intended outputs - signals responding to hardware events, messages scheduling tasks, etc.
In the case of fetch/execute there is definitely output - the result of correct execution, represented as levels on wires, bits in registers or memory, etc.


requests silently sends second request and drops first response (auth in use)

= short version =
When I am using a param and auth with requests.get(), requests appears to send a second request silently that's missing the param and then shows me the second response when i look at response.text.
= long version, with example and dumps =
I've been using requests to play a game. One level involved adding a param to a GET request in order to see hidden content on the webpage. This works fine with curl:
curl --user natas22:chG9fbe1Tq2eWVMgjYYD1MsfIvN461kJ "http://natas22.natas.labs.overthewire.org/?revelio"
Strangely, when I try something similar in requests I don't see the same response html text:
auth = ('natas22', 'chG9fbe1Tq2eWVMgjYYD1MsfIvN461kJ')
site = 'http://natas22.natas.labs.overthewire.org/?revelio'
r=requests.get(site,auth=auth)
r.text

After scanning with tcpdump, it appears that requests is getting the correct response, but then it interacts with the server a second time for some reason. During that second interaction requests fails to send the URL param.
Initial request:
22:59:10.459925 IP (tos 0x0, ttl 64, id 27245, offset 0, flags [DF], proto TCP (6), length 331)
    XXXXXX.58647 > melinda.labs.overthewire.org.http: Flags [P.], cksum 0x6cdb (correct), seq 1:280, ack 1, win 4117, options [nop,nop,TS val 377042043 ecr 980610639], length 279
..{...|.......E..Kjm@.@......o.O.....P_.).3.......l......
.y4{:r.OGET /?revelio HTTP/1.1
Host: natas22.natas.labs.overthewire.org
Connection: keep-alive
Accept: */*
Accept-Encoding: gzip, deflate
Authorization: Basic bmF0YXMyMjpjaEc5ZmJlMVRxMmVXVk1nallZRDFNc2ZJdk40NjFrSg==
User-Agent: python-requests/2.7.0 CPython/2.7.9 Darwin/14.3.0

Initial successful response that I never see from the interpreter:
22:59:10.579617 IP (tos 0x0, ttl 53, id 61399, offset 0, flags [DF], proto TCP (6), length 1500)
    melinda.labs.overthewire.org.http > XXXXXX.58647: Flags [.], cksum 0xed92 (correct), seq 1:1449, ack 280, win 235, options [nop,nop,TS val 980610675 ecr 377042043], length 1448
<EMAIL_ADDRESS>:r.s.y4{HTTP/1.1 302 Found
Date: Thu, 14 May 2015 03:59:10 GMT
Server: Apache/2.4.7 (Ubuntu)
X-Powered-By: PHP/5.5.9-1ubuntu4.9
Set-Cookie: PHPSESSID=p6ls9fd6jqaveoha3vc4kav7g0; path=/; HttpOnly
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Location: /
Content-Length: 1049
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html
<html>

[html page that I want]

Unlike curl, after this requests immediately sends some traffic back for reasons that are unclear to me. Note the r.sGET / HTTP/1.1 line is missing the revelio param:
22:59:10.579704 IP (tos 0x0, ttl 64, id 53914, offset 0, flags [DF], proto TCP (6), length 52)
    XXXXXX.58647 > melinda.labs.overthewire.org.http: Flags [.], cksum 0x4bc7 (correct), seq 280, ack 1497, win 4071, options [nop,nop,TS val 377042162 ecr 980610675], length 0
..{...|.......E..4<EMAIL_ADDRESS>.y4.:r.s
22:59:10.584887 IP (tos 0x0, ttl 64, id 54853, offset 0, flags [DF], proto TCP (6), length 369)
    XXXXXX.58647 > melinda.labs.overthewire.org.http: Flags [P.], cksum 0x2c85 (correct), seq 280:597, ack 1497, win 4096, options [nop,nop,TS val 377042167 ecr 980610675], length 317
..{...|.......E..q.E@.@.g....o.O.....P_.+.3.......,......
.y4.:r.sGET / HTTP/1.1
Host: natas22.natas.labs.overthewire.org
Accept-Encoding: gzip, deflate
Accept: */*
User-Agent: python-requests/2.7.0 CPython/2.7.9 Darwin/14.3.0
Connection: keep-alive
Cookie: PHPSESSID=p6ls9fd6jqaveoha3vc4kav7g0
Authorization: Basic bmF0YXMyMjpjaEc5ZmJlMVRxMmVXVk1nallZRDFNc2ZJdk40NjFrSg==

The server then responds with a gzipped version of the page, which is what ends up being what requests shows me when I type r.text:
22:59:10.707316 IP (tos 0x0, ttl 53, id 61401, offset 0, flags [DF], proto TCP (6), length 843)
    melinda.labs.overthewire.org.http > XXXXXX.58647: Flags [P.], cksum 0x8233 (correct), seq 1497:2288, ack 597, win 243, options [nop,nop,TS val 980610713 ecr 377042167], length 791
|.......{.....E..K..@.5.Wr.O.....o.P..3..._.,>.....3.....
:r...y4.HTTP/1.1 200 OK
Date: Thu, 14 May 2015 03:59:10 GMT
Server: Apache/2.4.7 (Ubuntu)
X-Powered-By: PHP/5.5.9-1ubuntu4.9
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 383
Keep-Alive: timeout=5, max=99
Connection: Keep-Alive
Content-Type: text/html

Why is requests making this second request and dropping the param on the floor?

Out of curiosity I checked to see if the problem persisted if I gave the param a value (i.e., site = 'http://natas22.natas.labs.overthewire.org/?revelio=foo'). I'm still experiencing the same pattern.

Because we got redirected. =)
The first response is a HTTP 302. Per RFC 7231, we follow that redirect, making another request with the URL set to the value of the 'Location' header on the 302. By default curl does not follow redirects: by default we do. To get curl to do what we do, pass it the -L command line flag. To get us to behave like curl, set allow_redirects=False in your call to requests.get.

Oh thanks! I didn't think to look at the return code. :)


Code Formatter

Hi, how can I use your library to access the element style to sort css3 codes?

I'm not really clear on what you're asking for, can you elaborate?

I'm not really clear on what you're asking for, can you elaborate?

Well, my dear friend, I wrote a css3 format code and I want to sort the css3 code next to the html at the same time as I format the html code.

private String formatCode(String code) {
    String html = code;
    var formatSrc = "";
    var formatStyle = "";
    Document doc = Jsoup.parse(html);
    Document.OutputSettings outputSettings = new Document.OutputSettings();
    outputSettings.indentAmount(2);
    doc.outputSettings(outputSettings.prettyPrint(true));

    Elements styleElements = doc.select("style");
    for (Element styleElement : styleElements) {
      String cssCode = styleElement.html();
      String formattedCssCode = javaFormat(cssCode);
      styleElement.html("\n\t" + formattedCssCode + "\n");
    }

    Elements jsElements = doc.select("script");
    for (Element jsElement : jsElements) {
      String jsCode = jsElement.html();
      String formattedJsCode = javaFormat(jsCode);
      jsElement.html("\n\t" + formattedJsCode + "\n");
    }

    if (doc.toString().contains("<!doctype html>")) {
      return doc.html().replace("<!doctype html>", "<!DOCTYPE html>");
    }

    return doc.html();
  }

I wrote a sample but it does not give a good output. I will show you an output sample
<html lang="en">
  <head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>Document</title>
    <style>
	h1{
	color:red;
}
</style>
  </head>
  <body>
  </body>
</html>

Thanks, makes sense. Jsoup doesn't include a CSS formatter. We do preserve linebreaks and spaces in style tags, so conceivably you could find another library or program to format the CSS, and feed it with select("style"), then update those elements with that result.

BTW if you do work up a solution, it would be great if you could post it here for posterity.


avoid probable race when creating fragments

Revised this based on re-reading the code and trying to test it. It turns out that the reuse of old items in the fragments map is probably harmless, but there was an actual underlying race condition that could result in trying to reopen a fragment immediately after creating it, rather than using the just-opened fragment.
Pull request checklist

[X] I have read the contributing guide.
[X] I have agreed to the Contributor License Agreement.
[X] I have updated the documentation.
[X] I have resolved any merge conflicts.
[X] I have included tests that cover my changes.
[X] All new and existing tests pass.

Code review checklist
This is the checklist that the reviewer will follow while reviewing your pull request. You do not need to do anything with this checklist, but be aware of what the reviewer will be looking for.

[ ] Ensure that any changes to external docs have been included in this pull request.
[ ] If the changes require that minor/major versions need to be updated, tag the PR appropriately.
[ ] Ensure the new code is properly commented and follows Idiomatic Go.
[ ] Check that tests have been written and that they cover the new functionality.
[ ] Run tests and ensure they pass.
[ ] Build and run the code, performing any applicable integration testing.

Do you think it's worth adding a test to cover this scenario like we did in https://github.com/pilosa/pilosa/pull/1675/files ?

yes, will do

@travisturner, I think this is probably ready now.
So when I made the (working) patch, I got stumped trying to test it -- any test which would delay suitably to manufacture the failure under the old code would deadlock under the new code, or vice versa. Then I realized I don't need an actual lock, I just need enough delay to make the scheduler likely to run both goroutines. 10ms later, here's a test which produces the expected (but unwanted) failure with the old CreateFragmentIfNotExists, but passes with the new one.

staticcheck is wiser than i am, and points out that you shouldn't call t.Fatalf() from a goroutine. Fixed using errgroup.

rebased and pushed. you'll be glad to know that, while i did indeed edit the comment on errorBroadcaster to say it delays, while leaving the comment on delayBroadcaster alone, I fixed that before committing.

hmm, interesting question. i wonder... say two nodes simultaneously create shards, and notify each other. do they have to wait on any processing on the remote end before they can finish/ack the message, in some way? because if they did, if they were doing shards of the same views, they could end up each having the view locked, and unable to do things to it based on the other end's message, for instance.
i'll study this more tomorrow, but i think the existence of that attempt to fix a deadlock implies something.
possibly a fix would be to add the fragment to v.fragments whether or not the broadcast succeeds; after all, if we don't, the next time we shut down, we still end up coming up with that fragment defined, and never broadcast it.

I've combed through this a few times now, and I'm pretty well convinced that this particular instance won't cause a deadlock, but I do think that having something locked, and then talking to other nodes in such a way that they require locking is something to be avoided if possible.
If you'd like to discuss the previous deadlocks and how they worked, lmk

Have fixed the two comments. I think for now I'm inclined not to report the broadcast errors, but that's a revisitable decision. I am also pondering the implications of this for a logging strategy to coalesce similar-and-repeated messages.


dyld_sim`dyld_fatal_error on ios 9.1.2

dyld: Library not loaded: /System/Library/Frameworks/Speech.framework/Speech
Referenced from: /Users/beonline2/Library/Developer/CoreSimulator/Devices/5B5D8349-5F7B-43EE-9ED0-B7182BDE48ED/data/Containers/Bundle/Application/DF9605BD-7B96-4119-913A-24262A667D4A/rnapp.app/rnapp
Reason: image not found
Please help me!

upgrade to ios10


v1.16 Backports 2024-11-06

[ ] #35784 (@sayboras) :warning: resolved conflicts

First commit is dropped as it's the original change was not backported.

Once this PR is merged, a GitHub action will update the labels of these PRs:
 35784

/test-backport-1.16

/test-backport-1.16


貌似OC项目调用不了啊，请问怎么兼容？

(SpreadsheetView *)spreadsheetView {
if (!_spreadsheetView) {
_spreadsheetView = [[SpreadsheetView alloc] initWithFrame:CGRectZero];
_spreadsheetView.delegate = self.presenter;(X)
}
return _spreadsheetView;
}

叉那一行报错，报错提示："Property 'delegate' not found on object of type 'SpreadsheetView *"

SpreadsheetView cannot be used from Objective-C directly. You should wrap the APIs in Swift that is designed to be accessed by Objective-C. Then you can use the library. @xiaohuiCoding


Submission  github exercise ahmedmd youssemk parajuba

https://github.com/SIMBADABU/git-exercise

OK enough :+1:, but a few things to learn:

Don't add files like __pycache__ or .DS_Store to version control. A .gitignore file can help preventing this.
Commit messages should reflect the what and ideally the why. Don't use "Ex2 task a".
If you close pull requests, always write why.
Tests for exercise 1 and 3 fail:

Task 1A)
def __init__(self, coordinates: List[float]) -> None:
        self._coordinates = coordinates.copy()

Task 1B)
You have to delete
https://github.com/SIMBADABU/git-exercise/blob/5a12756ba6def1b2a110542976b237e98c4a0f5d/exercise1.py#L55
It's bad practice to add commented-out code (especially without writing why it is commented out):
https://github.com/SIMBADABU/git-exercise/blob/5a12756ba6def1b2a110542976b237e98c4a0f5d/exercise2.py#L10
Task 3A)
You could simplify this code:
https://github.com/SIMBADABU/git-exercise/blob/5a12756ba6def1b2a110542976b237e98c4a0f5d/exercise3.py#L29-L32
Task 3C)
https://github.com/SIMBADABU/git-exercise/blob/5a12756ba6def1b2a110542976b237e98c4a0f5d/exercise3.py#L34
You could directly pass 0.0 as default value:
def contains(self, point: Point2D, tolerance=0.0) -> bool:


Add DatasetCreator

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (042c596) 100.00% compared to head (ac183c4) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #26   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            7        10    +3
  Lines           61        95   +34
  Branches         1         2    +1
=========================================
+ Hits            61        95   +34

Impacted Files
Coverage Δ

src/gtvision/creators/dataset/__init__.py
100.00% <100.00%> (ø)

src/gtvision/creators/dataset/base.py
100.00% <100.00%> (ø)

src/gtvision/creators/dataset/vanilla.py
100.00% <100.00%> (ø)

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


Fix garbage collection for event listener

Unless I'm mistaken, detachedCallback was the v0 name, which is now obsolete and superseded by disconnectedCallback?
We also need to remove the event listener from the node it was registered on.

I appreciate you, @FND! Your feedback was incredibly helpful. I'm going to merge in this PR and open a fresh one that include the suggestions from your comments.

I'm glad it proved useful! I certainly learned a few things from your code as well; thank you for sharing, it's a really enjoyable idea!


React Magma Versions> Version tag is not displayed in the header.

Describe the bug
React Magma Versions> Version tag is not displayed in the header.
To Reproduce
Steps to reproduce the behavior:
Go to https://docs-preview-646--upbeat-sinoussi-f675aa.netlify.app/api-intro/versions/#released_versions
Verify the Version tag is not displayed
Expected behavior
Version tag should display in the header.

This is not a bug.
@orion-cengage Do we want to keep this open, or close it because we don't have intentions to do this right now?


Cleanup environment variables in examples

It appears that the daemsonset example has many environment variables set that are no longer used.
For example:

JOIN_MANAGER
JOIN_PASSWORD

Thank you for you review. Fixed in new pr


V1.1.x

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


windows ovf template

Hello I'm having trouble with windows vmware_ovf templates.
I'm creating my own templates with packer. When I launch a vagrant box, the vmware_ovf template is uploaded to vcenter, the vm is created, but it isn't launched - I think the vm customization fails. I can manually launch the vm from vcenter just fine, but I notice network isn't configured as expected (dhcp lease instead of static ip, hostname isn't set etc...).
vagrant-rbvmomi-1.8.1/lib/rbvmomi/vim/Task.rb:11:in `wait_for_completion': InvalidArgument: A specified parameter was not correct.  (RbVmomi::Fault)
I'm not sure if I'm doing something wrong in my packer template, or if it's the Vagrantfile.
Would you be kind enough to provide an example Vagrantfile to launch a windows box?
Regards
edit:
reading on other issues, my problem is more or less the same as https://github.com/gosddc/vagrant-vcenter/issues/17.
I would like to add that I have no issues with centos and ubuntu gosddc boxes.

I also have the same problem.
it's helpful to know that in my case once the vm is created, the guest_os_type/Guest Operating System = rhel6_64Guest \ Red hate Enterprise 6(64bit) is being correctly identified in the newly created vm. along with the vlan and other vm properties.

The problem is caused by plugin not reading Vagrant config correctly.  For some reason it always defaults to LinuxCustomization,  that's why you get the error shown above.
Applying this patch fixes the problem.
--- a/lib/vagrant-vcenter/config.rb
+++ b/lib/vagrant-vcenter/config.rb
@@ -113,7 +113,6 @@ module VagrantPlugins
       attr_accessor :template_id

       def initialize
-        @prep_type = 'linux'
         @enable_vm_customization = true
       end

You will also need to put this line into all your Vagrantfiles that use this provider
vcenter.prep_type = "Windows"

Hi gents,
Thanks @vladistan for the patch, appreciated, and we do accept any PRs. (develop branch)
As you can probably imagine @frapposelli and myself are pretty busy on other stuff right now, so we can't really fix all the current issues.
We will try to review the PRs, test & merge them as soon as possible.
Sorry about that.


libbfd: fix build

Motivation for this change
The patch to separate it from binutils didn't apply anymore after
updating binutils to 2.34[1].
[1] #85951
Things done

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

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

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

@GrahamcOfBorg build llvm_7

@Ericson2314 updated. Missed that initially while resolving the conflicts :)


NameError: name 'hid' is not defined

$ poetry install
Installing dependencies from lock file

Nothing to install or update

  - Installing hwi (1.0.0)
A setup.py file already exists. Using it.

$ ./hwi.py enumerate
Traceback (most recent call last):
  File "./hwi.py", line 7, in <module>
    main()
  File "/home/torkel/dev/python/bitcoin-core-hwi/hwilib/cli.py", line 222, in main
    result = process_commands(sys.argv[1:])
  File "/home/torkel/dev/python/bitcoin-core-hwi/hwilib/cli.py", line 178, in process_commands
    return args.func(args)
  File "/home/torkel/dev/python/bitcoin-core-hwi/hwilib/cli.py", line 30, in enumerate_handler
    return enumerate(password=args.password)
  File "/home/torkel/dev/python/bitcoin-core-hwi/hwilib/commands.py", line 37, in enumerate
    result.extend(imported_dev.enumerate(password))
  File "/home/torkel/dev/python/bitcoin-core-hwi/hwilib/devices/ledger.py", line 338, in enumerate
    for d in hid.enumerate(LEDGER_VENDOR_ID, LEDGER_DEVICE_ID):
NameError: name 'hid' is not defined

Adding import hid at the top of hwilib/devices/ledger.py fixes the issue.

I've got the same error message after:
$ sudo apt install libusb-1.0-0-dev libudev-dev
$ git clone https://github.com/bitcoin-core/HWI.git
$ cd HWI
$ ./hwi.py enumerate

Adding import hid at the top of hwilib/devices/ledger.py fixes the issue as @torkelrogstad says.

Does this error occur if you use the released binaries?

I'm wondering what I've done differently in my setup that makes me unable to reproduce this.

The binary release works okay.


using mpd

1.) In your FAQ Audio is not working you recommend to modify file /usr/share/alsa/alsa.conf
Well that works but the better way is to add or modify file /etc/asound.conf
sudo nano /etc/asound.conf
pcm.!default {
    type hw
    card 1
}
ctl.!default {
    type hw
    card 1
}

2.) One question at last: you modified /etc/mpd.conf to run mpd as root user despite the warning. What is the reason?

Hi @kle99
Thanks for your contribution. I added your suggestion, linking to this post, because I could not test it:
https://github.com/MiczFlor/RPi-Jukebox-RFID/wiki/MANUAL#audio-is-not-working
and (2): well, this comes from a time where the playlists were added in the /tmp directory and mpd didn't do that without being root. Not sure what would break if that was changed :) even though the playlists are now stored elsewhere. Wanna give it a try? :)


Refactor cli UI (general output, user feedback)

Currently all user feedback of the cli (general and logging) is done directly via fmt in the various packages of carrier.
It will be better to have this refactored to have the actual output divorced from the functionality itself, to keep the packages UI independent.
Note that the above is in part covered by #36, however that ticket limits itself to logging, and not the general UI feedback of the cli.

Fixed with #64

Fixed with #64


⚠ Bofrost.de has degraded performance

In 5b38b8d, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1831 ms

Resolved: Bofrost.de performance has improved in 92bfc2f after 27 minutes.


Collect metrics for TCP and UDP connections

Feature
What did you expect to see?
tldr;
Store metrics for tcp and udp connections to InfluxDB and other destinations.
Background:
I recently had a need to track metrics for both http and tcp connections, but realised that only http metrics are sent to InfluxDB.
My use case is essentially to keep track of general traffic volumes going to tcp and http services, and then visualise this in Grafana after the metrics have been stored in InfluxDB. Grafana will also be used for alerting.
I am using the open source version of Traefik.

We really need this as well, and it is the only reason holding us back from using the traefik free or paid for solutions. We would also be looking for logs on TCP as well. I'm somewhat surprised that TCP is supported and we can't find any evidence of connections passing through traefik. Are missing something here?

+1 very welcome feature, at least tcp access logging has to be there

What is the status of this? TCP is supported as an ingress but we have no metrics or visiblity of this feature?

TCP doesn't have logs, or metrics, correct? Is it a bit crazy to put Kafka behind it? As there's no visibility if it's up or down 0o


Feature/231 mobile friendly

Resolves #231
The PR is a draft, I still need to populate the community cards in the preview;
Preview
These changes are made to the landing page of DevHub:

[x] The search filters dropdown and post button are now vertically stacked because they didn't fit horizontally.

[x] The community cards on the home page are now stacked 2x2 instead of horizontally which made them unreadable.

I'm closing this because we will revisit mobile as part of the redesign epic.


docs: Mendable Search Integration

Hi @jerryjliu,
Super excited to get Mendable search on Llama index docs. Here is an implementation of our floating button that stays in the bottom right, which doesn't interfere with the normal readthedocs search. Eric will message you the admin dashboard details so you can see all the insights!
Let me know if you have any feedback or customization requests.
I believe this should also work fine with the new theme on #1164

This looks amazing! Merging for now and we can discuss more on customization requests.


Save SVG/PNG to Python

Would it be possible to add options to save_svg and save_png so that they return the image data instead of proposing to save it from the browser. For example, myfig.save_svg(dump=True) would return the raw SVG data.
This would allow to process the images in Python, in my case to convert it to PDF.
Thanks for your wonderful work!

Dear all,
I have a similar request, I wish to programmatically generate figures and save them directly on the filesystem, rather than downloading them via the browser. Is there any way this can already be achieved or can you consider supporting this feature?

I am also looking for a way to save the figure as PNG programmatically.


Limit the size of external uploads

As of now external uploads can get arbitrarily large depending on bandwidth within a timeout. Would be nice to instantiate a hard limit on the backend to prevent us from running out of disk space.
P.S. to @dstndstn , if you are busy with dr8 stuff, I'm happy to look into solutions and put together a pull request.

There should be a Django file uploads setting for this.


Use 10 as keycode for return as well as enter

In actual practice this seems to be a better representation of how browsers implement keycodes for return.
Would close #6

:+1: @benmccormick sorry I did not see the issue earlier! thanks for this, looks good!

published v0.0.11 on NPM


permission denied writing UI app logs

In 3.0.2 the app is trying to log UI app messages, but doesn't have permission in the target directory.
Log Write Error: Error: EACCES: permission denied, open '/usr/lib/ziti-desktop-edge-preview/resources/app/logs/UI/ZitiDesktopEdge20221017.log'

❯ ll -d /usr/lib/ziti-desktop-edge-preview/resources/app/logs/UI/
drwxrwxr-x 2 root root 4.0K Oct 14 13:00 /usr/lib/ziti-desktop-edge-preview/resources/app/logs/UI//

Moved app logs to users app data / config directories


Attachments disappear from state in repeating groups

Description of the bug
If you upload an attachment to a FileUploadWithTag component (the same probably happens with normal FileUpload components) and then refresh the page, the attachment will disappear from the list. This causes the required validation to think that there is no file added despite the file existing in blob. If you then add another file then you'll see both the files for the same upload component on the receipt page.
Steps To Reproduce

Have a repeating group with a FileUploadWithTag component
Add an attachment, select a tag and save the attachment
Refresh the page
the file will now be missing

Additional Information
There is no limit to the amount of files you can upload by doing this

@MagnusMolaugFinans Which app is this? We have automatic tests for this functionality which haven't failed recently, so I suspect there is something specifically in the app that went wrong when you got this problem.
Also, have you followed the setup guide for attachments in repeating groups? You have to make sure to set up a data model binding for the file upload component when used in repeating groups (same goes for FileUploadWithTag), otherwise you'll get pretty much this behavior.

Debugged this and communicated via Slack. Not an issue in app-frontend, but a problem with the data model setup in the app. Closing as not planned.


maximum concurrent stream is defined only by the local settings

Types of Changes
Bug fix. Resolves #8

It would be good to add a spec to this to prevent a regression.

It would be good to add a spec to this to prevent a regression.

I'm looking at the connection spec and I was thinking of reusing some of the test logic here: https://github.com/socketry/protocol-http2/blob/014f415df03b7058488126bd899ce90f893d986e/spec/protocol/http2/connection_spec.rb#L82 while also setting the maximum concurrent connection setting. I'm just not sure how to set it. Is it possible? If so, how?

You should be able to access the settings directly:
https://github.com/socketry/protocol-http2/blob/main/lib/protocol/http2/connection.rb#L88-L90
Then you can set it yourself:
https://github.com/socketry/protocol-http2/blob/main/lib/protocol/http2/settings_frame.rb#L52-L53
Would be good to test both positive and negative cases to prevent regressions.


Make OpenAPI spec location configurable

Introducing DATABRICKS_OPENAPI_SPEC environment variable to hold a filesystem location of all-internal.json spec.

Codecov Report
Patch and project coverage have no change.

Comparison is base (c2ebc4f) 53.24% compared to head (a736db6) 53.24%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #237   +/-   ##
=======================================
  Coverage   53.24%   53.24%
=======================================
  Files          32       32
  Lines       19145    19145
=======================================
  Hits        10193    10193
  Misses       8952     8952

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


Fix issue parsing block comments, and always retain prefix comments for cgo imports.

Resolves #48.
Comments before import "C" should always be retained, as these are used by cgo.

Could we use "C" to detect CGO and make it into a single func?

Could we use "C" to detect CGO and make it into a single func?
I prefer divide parseToImportDefinitions  into some small parts to match different cases.

Block comments (/* ... */) aren't limited to cgo imports - they're equally valid elsewhere.

It might be more robust to use the ast package to parse files than doing what I've done here, but that would likely be a far bigger change.

It might be more robust to use the ast package to parse files than doing what I've done here, but that would likely be a far bigger change.

Track as #50

@daixiang0 thanks for merging this. Any chance you could tag a new release with this fix included?


3 issues

Issue 1: Wonds table not working correctly, it dose detect that a character or creature has been damaged correctly, however with NPC it seems to have some save assigned to it for no reason,
Issue 2: Wonds table no longer seems to roll after clicking roll button even though name is correct in table.
Issue 3: Zombies undead fortitude is calculated wrong with automation and dose not take into account the -5 to the roll that it should

the save is following the dmg rules. Refer to that for the full usage.

for players they are prompted to roll after the GM confirms, this must be done on their client

the auto fortitude check iant 100% accurate as we cannot read over spill damage. Use the slow check for more accuracy


Let users control page title buildup

Now we force a specific format on titles. Use app settings to control this!

Always append site name?
Title page and site name separator?
Remove sitename append on frontpage?

More?

I've added these now + functionality for it.


Remove dead code

Look at method render. It's do similar check.

https://github.com/mjmlio/mjml/pull/833/files/800501863f254c14a8b8f3dfe54176808bce6977#diff-327a862c444f85fc9611b8b91e6519b1L181
renderFullWidthSection calls renderSection, so that's why you still need this

My mistake. Sorry for taking the time.


"For more details on the API, see the code here." Broken link. EOM.

Fixed: https://github.com/auvsi-suas/interop/commit/ecaf1655acedded36410d9c7ffb706b08ce26550


clientv3: hide retry dial api

since grpc GA was pushed back, will probably have to wait for the picker stabilize
/cc @xiang90

LGTM


[TypeScript React-Query] export fetcher from each query

Is your feature request related to a problem? Please describe.
If we want to use the feature from Next.js, Incremental Static Regeneration, we need the fetcher itself to be executed on the static method getStaticProps. If the user uses Typescript React-Query to generate the queries, he will need the fetcher exported to be used separately.
At the moment I can't get Incremental Static Regeneration on my project using generators.

Describe the solution you'd like

We can do something related with the option to export unique key for the query and aggregate the fetcher like:
inside query variable, aggregate fetcher method:
useQuery

getKey (already present)
fetcher

import { useQuery } from './gen'

export function Index(props) {
  const { data } = useQuery()

  return <Component />
}

export async function getStaticProps() {
  const queryClient = new QueryClient()

  await queryClient.prefetchQuery(userQuery.getKey(), () => userQuery.fetcher())

  return {
    props: {
      dehydratedState: dehydrate(queryClient),
    },
  }
}

Describe alternatives you've considered

Additional context

I might be missing something here, but the fetcher is generated before each hook, and generally available for you to use. I think you can just use the fetcher as-is? Or you wish it to be wrapped somehow?
Maybe you can share an example of how userQuery.fetcher should be generated?

Hi,
This is is a good example made for swr (https://www.npmjs.com/package/graphql-codegen-plugin-typescript-swr). Basically, this should generate a fetcher and a hook for the same fetch method so we can use the fetch for getInitialProps (nextjs) and the hooks for the component itself.

I want to add a few words from my side:

It would be great to use the request functions that are used for hooks, because it is not always possible to use hooks (for example, on the server side)
The second problem is that now even the main fetcher is not exported and you have to write your own

export const useGetArticlesQuery = <TData = GetArticlesQuery, TError = unknown>(
  variables?: GetArticlesQueryVariables,
  options?: UseQueryOptions<GetArticlesQuery, TError, TData>,
) =>
  useQuery<GetArticlesQuery, TError, TData>(
    ['getArticles', variables],
    fetcher<GetArticlesQuery, GetArticlesQueryVariables>(GetArticlesDocument, variables),
    options,
  )

Where fetcher is (with no export at all...):
function fetcher<TData, TVariables>(query: string, variables?: TVariables) {
  return async (): Promise<TData> => {
    const res = await fetch(`${process.env.API_BASE_URL || ''}/graphql` as string, {
...

So for Next.js I use:
static async getInitialProps(appContext: AppContext) {
  const _queryClient = new QueryClient()
  await _queryClient.prefetchQuery(
    'getStatistics',
    fetcher<GetStatisticsQuery, GetStatisticsQueryVariables>(GetStatisticsDocument, {}),
  )
  ...
}

But want something like this:
static async getInitialProps(appContext: AppContext) {
  const _queryClient = new QueryClient()
  await _queryClient.prefetchQuery(
    useGetStatisticsQuery.key, // Defined and exported key
    fetchArticles, // Defined and exported fetcher
  )
  ...
}

You can mitigate the issue a tiny bit by manually exporting the unexported fetcher with
plugins:
  - add:
      placement: append
      content: "export { fetcher }"

but even then there's no type safety since the variables are not bound to the query being made.
The state of graphql data fetching libraries on nextjs is quite abysmal right now. next-apollo has big caveats with getServerSideProps (and more) that make it unusable, SWR doesn't support the hydration pattern and react-query has codegen issues. If a maintainer would be kind enough to hold the ropes with examples that might be relevant/useful in getting this feature implemented, I would be interested in giving it a shot because right now working with data fetching in nextjs is a terrible dev experience.

@Xetera lol. I was literally thinking the same thing! Just putting my feet on the water on this subject and everything is all over the place. I'm totally lost with the codegen part, since nothing kinda fits the nextjs solution. TBH, nextjs data fetching strategy is also all over the place.. I think react-query's strategy is the best one and super easy to implement:
export async function getServerSideProps() {
   const posts = await getPosts()
   return { props: { posts } }
 }

 function Posts(props) {
   const { data } = useQuery('posts', getPosts, { initialData: props.posts })

   // ...
 }

The issue now is with codegen, since I don't want to keep creating functions for everything, since I can codegen them hehe.

Attempted in #6365

Available in<EMAIL_ADDRESS>


Add a LinearNMM class to models.py with 2 methods

_init__(num_regions, SC)
forward(init_state, sim_len, step_size, use_noise):

Implementing the Euler-Maruyama method
without the tanh.
params: initialize with laplacian (can be defaulted as rand > transformed into laplacian, but the whole thing as an optional input).

[ ]

Implemented as first phase of #27 as class models.LinearRNN_Params


VSTest Task Fails with System.TimeoutException: The HTTP request timed out after 00:01:40

Setup:
TFS Update 3 on-premises
vsts agent 2.140.2
VsTest installed via Test Platform Installer (15.9.1 preview)
Visual Studio Test task Version 2.*

Select tests using Test Plan
multi-agent parallelism

Issue:
I am seeing test runs aborting in the middle, I believe due to the following error:
2018-10-25T05:58:16.5424818Z ##[error]Failure attempting to call the restapis. Method: System.Threading.Tasks.Task`1[Microsoft.TeamFoundation.Test.WebApi.TestExecutionServiceCommand] b__0(), Exception: System.AggregateException: One or more errors occurred. ---> System.TimeoutException: The HTTP request timed out after 00:01:40. ---> System.Threading.Tasks.TaskCanceledException: A task was canceled.
We see this on multiple test runs quite often - our setup is new and have seen this each time we try to run all of our tests (over 1200 test points across multiple environments). I cannot yet tell a pattern of when it happens. This particular test run was using 7 test agents. Two of the test agents completed their tests, one of them hadn't started running tests yet, and out of the remaining 4 agents, 3 of them are all similar logs with other agent appearing different, so I suspect it was that different agent that encountered the issue that caused the problem. Here are the logs around the failing section for that agent:
HttpTimeoutLogs.txt
Please let me know if you need any other information.

The call seems to have timed out. This is mostly an indication of unreliable network.
Can you check if the timeout always happen in the same set of machines? If so eliminating them from the pool will help improve the reliability of the test runs.
In the latest version, we have addressed this by adding a retry logic for this call.

I set the VSTS_HTTP_TIMEOUT; as suggested here:
https://github.com/Microsoft/azure-pipelines-agent/blob/master/docs/troubleshooting.md#workaround-httptimeoutexception
However, that doesn't seem to be honored. I still see the error in the log about timing out at 1:40:
2018-10-29T07:33:12.1263347Z ##[error]Failure attempting to call the restapis. Method: System.Threading.Tasks.Task`1[Microsoft.TeamFoundation.Test.WebApi.TestExecutionServiceCommand] b__0(), Exception: System.AggregateException: One or more errors occurred. ---> System.TimeoutException: The HTTP request timed out after 00:01:40. ---> System.Threading.Tasks.TaskCanceledException: A task was canceled.
Here is my environment variables:

What build of the vsts agent is the fix in? Is it available yet?

Sorry, I did not realize that the version you have already has the retry logic I was talking about. The logs also show that it retried and then still failed again.
This vsts_http_timeout value is currently not honoured by vstest task. But I will log a bug at our end (but please note that it will be picked up based on priority).
Is the network unreliable? If it is specific to a particular agent, you can try to eliminate it from the pool. The call that is failing for you is a high frequency call and will require the network to be reliable.

After a few days of running, it has happened on several of the machines in the pool, and removing them is not an option. I have the network team helping to look into the issue, but so far, they are not able to see anything on our end to explain why this would be happening.

@NDDeveloper13 please re-open you if you still facing the issue.

It seems that a Microsoft server is down, the tests are trying to consume a service in the IP: <IP_ADDRESS>:443


Unauthorized: Stream is not enabled for count requests

Hi,
Thank you for useful code!
When I use this sample with "-l option" via Premium Search API on sandbox, an error is raised. Could you tell me advice to avoid this error?
The settings are as follows.
# config/config.yaml
options:
  search_type: premium
  archive: 30day
  max_results: 100
  write_mode: standard-out
  out_box: ./output
  counts_to_standard_out: true
  compress_files: false

The error message is "Unauthorized: Stream is not enabled for count requests".
$ bundle exec ruby search-app.rb -r "from:TwitterDev" -s 14d -l

Getting counts for rule: from:TwitterDev
Retrieving counts for rule: from:TwitterDev
For time period:<PHONE_NUMBER>19 to now.  ...
ERROR occurred: 401  Authorization Required --> {"error":{"message":"Unauthorized: Stream is not enabled for count requests","sent":"2020-04-03T01:19:10+00:00","transactionId":"005c522f00280c53"}}
{}
Total counts: 0
Exiting

Without "-l option", I receive the correct response.
$ be ruby search-app.rb -r "from:TwitterDev" -s 14d
Getting activities for rule: from:TwitterDev
Retrieving data from<PHONE_NUMBER>23 to now.  ...
{"created_at":"Mon Mar 30 16:18:45 +0000 2020","id":1244660343646957568,"id_str":"1244660343646957568","text":"RT @getpostman: Those on the front lines of t
{"created_at":"Fri Mar 27 20:10:59 +0000 2020","id":1243631624945717248,"id_str":"1243631624945717248","text":"Update: We’re continuing to see increased wai
{"created_at":"Mon Mar 23 22:01:13 +0000 2020","id":1242209814706438144,"id_str":"1242209814706438144","text":"As we work to keep our employees safe during
{"created_at":"Mon Mar 23 16:26:09 +0000 2020","id":1242125490543976449,"id_str":"1242125490543976449","text":"The Tweets and recent search endpoints will n
{"created_at":"Mon Mar 23 16:26:08 +0000 2020","id":1242125486844604425,"id_str":"1242125486844604425","text":"A few months ago, we added Tweet annotations

The counts endpoint is not available in the sandbox mode, and is only available to a paid premium subscription. You can read more about this in the Twitter developer documentation. We could improve the documentation for this client library to make this more clear, so thank you for raising the issue!

Thank you for your polite reply!

With the /search/all refresh, closing out resolved issues...

With the /search/all refresh, closing out resolved issues...


chore: switch to tinyglobby to drop 21 dependencies

🔗 Linked issue

❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[x] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
https://npmgraph.js.org/?q=globby - 23 dependencies
https://npmgraph.js.org/?q=tinyglobby - 2 dependencies

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 40.43%. Comparing base (4b71b84) to head (c09a3d4).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #205      +/-   ##
==========================================
+ Coverage   40.29%   40.43%   +0.14%
==========================================
  Files          56       56
  Lines        3368     3368
  Branches      424      424
==========================================
+ Hits         1357     1362       +5
+ Misses       1973     1968       -5
  Partials       38       38

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Pathway data input documentation

This will close #62.
So far this is just a draft of the document and not ready for review. But I wanted to add show the path diagram I'm developing in design/pathways/images/raw/diagram-data-input.mmd, which is created with mermaid, with the syntax here and image below:
.

@K-Beicher and @rqding I've updated the data flow diagram for sample analysis type data that you can check out in design/pathways/images/data-input-sample-analysis.mmd. I've also made one for the batch type data in design/pathways/images/data-input-batch.mmd. You can use these to help you write the backend architecture document #61 and the API architecture document #56.

Several of these items can be used for the runtime/other sections. So I am merging in so that they can be used later.


Errors will happen when upgrading the libraries

An error will happen when upgrading libraries _coreos/go-systemd_and prometheus/client_golang:
For example----
github.com/coreos/go-systemd
-Latest Version: v22.1.0   (Latest commit b51e752 26 days ago)
-Where did you use it:
https://github.com/box/kube-iptables-tailer/search?l=Go&q=github.com%2Fcoreos%2Fgo-systemd
-Detail:

github.com/coreos/go-systemd/go.mod

module github.com/coreos/go-systemd/v22
go 1.12
require github.com/godbus/dbus/v5 v5.0.3

github.com/coreos/go-systemd/sdjournal/functions.go

package sdjournal
import (
	"github.com/coreos/go-systemd/v22/internal/dlopen"
	…
)

This problem was introduced since coreos/go-systemd v22.0.0 . Now you used the version v19. If you try to upgrade coreos/go-systemd to version v22.0.0 and above, you will get an error--- no package exists at "github.com/coreos/go-systemd/v22"
Similar issues can also happen when upgrading libraries prometheus/client_golang .
I investigated the libraries'  (coreos/go-systemdandprometheus/client_golang)  release information and found the root cause of this issue is that----

These dependencies all added Go modules in the recent versions.

They all comply with the specification of "Releasing Modules for v2 or higher" available in the Modules documentation. Quoting the specification:

A package that has migrated to Go Modules must include the major version in the import path to reference any v2+ modules. For example,  Repo github.com/my/module migrated to Modules on version v3.x.y.  Then this repo should declare its module path with MAJOR version suffix "/v3"  (e.g., module github.com/my/module/v3), and its downstream project should use "github.com/my/module/v3/mypkg" to import this repo’s package.

This "github.com/my/module/v3/mypkg" is not the physical path. So earlier versions of Go (including those that don't have minimal module awareness) plus all tooling (like dep, glide, govendor, etc) don't have minimal module awareness as of now and therefore don't handle import paths correctly See golang/dep#1962, golang/dep#2139.

Note: creating a new branch is not required. If instead you have been previously releasing on master and would prefer to tag v3.0.0 on master, that is a viable option. (However, be aware that introducing an incompatible API change in master can cause issues for non-modules users who issue a go get -u given the go tool is not aware of semver prior to Go 1.11 or when module mode is not enabled in Go 1.11+).
Pre-existing dependency management solutions such as dep currently can have problems consuming a v2+ module created in this way. See for example dep#1962.
https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher

Suggested solutions
1. Migrate to Go Modules.
Go Modules is the general trend of ecosystem, If you want a better upgrade package experience, migrating to Go Modules is a good choice.
2. Keep using the dependency manage tool (like dep, glide, govendor, etc).
Because the import paths have different meanings between the projects adopting module mechanism and the non-module mechanism.

https://github.com/golang/go/wiki/Modules#semantic-import-versioning
https://golang.org/cmd/go/#hdr-Module_compatibility_and_semantic_versioning
https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher

If you prefer to use the dependencies manage tool (like dep, glide, govendor, etc), a textbook example provided by repo github.com/moby/moby can prevent this type of issues.
https://github.com/moby/moby/blob/master/VENDORING.md
https://github.com/moby/moby/blob/master/vendor.conf
In the vendor directory, github.com/moby/moby adds the /vN subdirectory in the corresponding dependencies.
This will help more downstream modules to work well with your package, otherwise they will be stuck in github.com/coreos/go-systemd v21 .
By the way, have you ever encountered such errors when upgading the libraries? Do you plan to upgrade the libraries in near future?
Hope this issue report can help you ^_^
Thank you very much for your attention.
Best regards,
Kate

@mjlshen @mauilion  Could you help me review this issue? Thx :p


Multiple worker threads

If you have a loop creating many runs within the same code a new worker thread is created on each iteration. With this simple example code you end up with 10 worker threads:
from simvue import Run

if __name__ == "__main__":
    count = 0
    while count < 10:
        with Run() as run:
            run.init()
        count += 1

This is not surprising, as the worker thread only exits when the parent exits.

Fixed in https://github.com/simvue-io/client/tree/improved_worker

Implemented


Staging Multi-Tier Web Scenario For Live

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/example-scenario/articles.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Customize target color

Targets are currently always yellow, but players should be able to customize their color.

Closed on 56e2a72


Fixed bug in Bastion that was preventing ctf-starting-user from ssm

Not sure when or how this started, but anonymous discord user reported bug where ctf-starting-user couldn't ssm into the bastion ec2 with the applied bastion-ssm policy.  This updated fix seems to fix the issue.

@sethsec Maybe my ignorance at play here, but bastion gets deployed and run from a single account right ?  I think it would be much easier to use the aws_caller_identity data source then defining the account_id as a variable.
data "aws_caller_identity" "current" {}

then later you could do:
 Resource = [
          aws_instance.bastion.arn,
          "arn:aws:ssm:us-west-2:${data.aws_caller_identity.current.account_id}:document/SSM-SessionManagerRunShell",
          "arn:aws:ssm:us-west-2:${data.aws_caller_identity.current.account_id}:session/ctf-starting-user-*",
        ]

very similar to what I did at https://github.com/BishopFox/cloudfoxable/blob/c8ec6bf2b575cc7e76c03713895269944b4dd525/aws/main.tf#L49 in my last PR.
just .02 :)

That's so interesting. Yea it always just worked for me in the past.  Not sure what this bug is/was, but thanks for digging into it @bf-singularity!


wontfix: fixed some translations to uzb lang

Background
Some translations viewed not right
Changelog
Fixing some translates to uzb lang

Thank you for asap fixes and your attention to details! ❤


🚀 Release ➾ Taqueria v0.24.0

🌮 Taqueria PR
🪁 Description
This PR covers the version bump and required updates to documentation and release notes for the Taqueria v0.24.0 release
🪂 Pre-Merge Checklist (Definition of Done)
🚦 Required to merge:

[x] ⛱ I have completed this PR template in full and updated the title appropriately
[x] ⛵ My code builds cleanly, and I have manually tested the changes
[ ] 🏄♂ Another team member has built this branch and done manual testing on the change
[ ] 🏖 New and existing unit tests pass locally and in CI
[ ] 🔱 The test plan has been implemented and verified by an SDET
[x] 🤿 Corresponding changes have been made to all documentation
[ ] 🪸 Required updates to scaffolds have been made
[ ] 🚢 The release checklist has been completed

🎢 Test Plan
Manual verification via release checklist
🛸 Type of Change

[ ] 🧽 Chore ➾
[ ] 🛠 Fix ➾
[ ] ✨ Feature ➾
[ ] 👷 Refactor ➾
[ ] 🧪 Pre-Release ➾
[x] 🚀 Release ➾

Do we need to inform users that they need to manually install the core plugin after upgrading Taqueria?
Or do we prefer to never put an essential command in it?

@AlirezaHaghshenas I think currently users have to manually install all the plugins after upgrading Taqueria no? Alternatively, run the jq script that I believe was made for this? @hu3man right?


Error in algorithm environment

For example, this code will have an error: algorithm.sty:96: LaTeX Error: Command \c@algorithm already defined. [\floatname]
\begin{algorithm}
\caption{1}
\label{alg:1}
\begin{algorithmic}
\end{algorithmic}
\Require 1
\Ensure 1
\end{algorithm}

Solution:
We can solve the problem by commenting the following part in hkustthesis.cls:
\declaretheorem[
    name=Algorithm,
    style=hkustthm,
    refname={algorithm,algorithms},
    Refname={Algorithm,Algorithms},
    % numberwithin=section,
]{algorithm}

Then we can add a line \listofalgorithms after
\listoffigures
\listoftables

in the front, which will have a list page of all the algorithms in the thesis, just like the list page of all the figures from \listoffigures.

Thank you. This issue originated from the historical code (see https://github.com/nju-lug/NJUThesis/issues/49). I made the changes accordingly. Please refer to the latest release. You can replace the latest .cls file with the old one and it won't break the main file.
However, the default listofalgorithms environment is a bit inconsistent with the overall style of its counterparts, so I tried my best to make a similar implementation but still had some issues. Hope someone in the future can help achieve a full implementation.


Support managed_challenge for access rules

Current Terraform and Cloudflare provider version
terraform -v                                                                             ─╯
Terraform v1.0.4
on darwin_amd64
Description
We are still using the cloudflare_access_rule and we would like to extend the use of managed_challange
Use cases
same as rate limit case: https://github.com/cloudflare/terraform-provider-cloudflare/issues/1432
Potential Terraform configuration

resource "cloudflare_access_rule" "challenge_countries" {
  for_each = toset(local.challenge_countries)
  notes    = "Challenge requests from ${each.key} (Terraform)"
  **mode     = "challenge"**
  configuration {
    target = "country"
    value  = each.key
  }
  zone_id = module.zone-settings.cf_out_zone_id
}

References
No response

PR: https://github.com/cloudflare/terraform-provider-cloudflare/pull/1457


[Documentation] - Form ecosystem (Input/InputGroup/FormField/TextField, etc.)

Create a dedicated page on Storybook to explain that.


[FEATURE REQUEST] - Remember window size & position

Summary
Thanks for developing this - it's useful in my organization and design process.
This is a minor nitpick, but I can't seem to get the app to remember its size or position (Windows). This would be helpful as I've assigned a button on my file manager's toolbar to open the app for selected files. (The single instance thing would help here too, but I see there's already a feature request open for that).
Basic Example
When you set the window size and position for the app window, it should remember and reuse those settings when next opened.
Reference Issues.
No response

In fact, someone has already made the exact same suggestion, and it's already in my plans.
I'm currently busy with other things and haven't had the time to add new features, so all I can do for now is some bug fixes.


Scan element detection timeout set to 600 seconds. How to change it?

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
When I run bundle exec fastlane ios tests, which is using scan :
platform :ios do
  desc 'Runs all the tests'
  lane :tests do
    scan(
      scheme: 'Companion',
      project: './ios/Companion.xcodeproj'
    )
  end
end

It is taking a lot of time to end up with the following message :
All tests
Test Suite CompanionTests.xctest started
CompanionTests
✗ testRendersWelcomeScreen, ((foundElement) is true) failed - Couldn't find element with text 'Welcome to React Native!' in 600 seconds

CompanionTests
testRendersWelcomeScreen, ((foundElement) is true) failed - Couldn't find element with text 'Welcome to React Native!' in 600 seconds
/Users/guillaumehain/Developments/companion/ios/CompanionTests/CompanionTests.m:64

XCTAssertNil(redboxError, @"RedBox error: %@", redboxError);
XCTAssertTrue(foundElement, @"Couldn't find element with text '%@' in %d seconds", TEXT_TO_LOOK_FOR, TIMEOUT_SECONDS);
}

   Executed 1 test, with 1 failure (0 unexpected) in 600.062 (600.063) seconds

600 seconds is really too much. I looked at the scan documentation but didn't found any way to change this value to something like 30 seconds.
Is there anything already existing or does it have to be implemented?
Complete output when running fastlane, including the stack trace and command used

All tests
Test Suite CompanionTests.xctest started
CompanionTests
✗ testRendersWelcomeScreen, ((foundElement) is true) failed - Couldn't find element with text 'Welcome to React Native!' in 600 seconds
CompanionTests
testRendersWelcomeScreen, ((foundElement) is true) failed - Couldn't find element with text 'Welcome to React Native!' in 600 seconds
/Users/guillaumehain/Developments/companion/ios/CompanionTests/CompanionTests.m:64
  XCTAssertNil(redboxError, @"RedBox error: %@", redboxError);
  XCTAssertTrue(foundElement, @"Couldn't find element with text '%@' in %d seconds", TEXT_TO_LOOK_FOR, TIMEOUT_SECONDS);
}

 Executed 1 test, with 1 failure (0 unexpected) in 600.062 (600.063) seconds

** TEST FAILED **
[15:01:34]: Exit status: 65
[15:01:34]: Successfully sent Slack notification
+--------------------+---+
|      Test Results      |
+--------------------+---+
| Number of tests    | 1 |
| Number of failures | 1 |
+--------------------+---+

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
10.13.6

Ruby
2.4.1

Bundler?
true

Git
git version 2.15.1 (Apple Git-101)

Installation Source
~/.rvm/gems/ruby-2.4.1@companion/bin/fastlane

Host
Mac OS X 10.13.6 (17G31f)

Ruby Lib Dir
~/.rvm/rubies/ruby-2.4.1/lib

OpenSSL Version
OpenSSL 1.1.0h  27 Mar 2018

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
9.4

System Locale

Variable
Value

LANG

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version '2.96.1'

default_platform(:android)

before_all do
  update_fastlane
  yarn(
    command: 'install',
    package_path: './package.json'
  )
  ANDROID_VERSION_NAME = get_version_name(
    gradle_file_path: 'android/app/build.gradle',
    ext_constant_name: 'versionName'
  )
  ANDROID_VERSION_CODE = get_version_code(
    gradle_file_path: 'android/app/build.gradle',
    ext_constant_name: 'versionCode'
  )
end

platform :ios do
  desc 'Runs all the tests'
  lane :tests do
    scan(
      scheme: 'Companion',
      project: './ios/Companion.xcodeproj'
    )
  end
end

platform :android do
  desc 'Runs all the tests'
  lane :tests do
    gradle(task: 'assemble', project_dir: './android/')

    sh '$(which adb) devices'
    sh 'pwd'
    sh 'ls -al ../android/app/build/outputs/apk/'

    gradle(task: 'test', project_dir: './android/')
    sh 'cd .. && $(which bundle) exec calabash-android run android/app/build/outputs/apk/app-debug.apk'
  end

  private_lane :clean_android do
    gradle(task: 'clean', project_dir: './android/')
  end

  desc 'Submit a new Beta Build to Crashlytics Beta'
  lane :beta do
    gradle(task: 'clean assembleRelease')
    crashlytics

    # sh "your_script.sh"
    # You can also use other beta testing services here
  end

  desc 'Deploy a new version to the Google Play'
  lane :deploy do |options|
    clean_android

    gradle(task: 'assemble', build_type: 'release', project_dir: './android/')

    if options[:play_store]
      # upload to alpha track on google play developer's console
      supply(
        track: 'alpha',
        apk: 'android/app/build/outputs/apk/app-release.apk'
      )
    end
  end
end

fastlane gems

Gem
Version
Update-Status

fastlane
2.97.0
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-badge
1.1.0
✅ Up-To-Date

fastlane-plugin-get_version_code
0.2.0
✅ Up-To-Date

fastlane-plugin-get_version_name
0.2.2
✅ Up-To-Date

fastlane-plugin-yarn
1.0
✅ Up-To-Date

Loaded gems

Gem
Version

did_you_mean
1.1.0

io-console
0.4.6

CFPropertyList
2.3.6

public_suffix
2.0.5

addressable
2.5.2

atomos
0.1.2

awesome_print
1.8.0

babosa
1.0.2

curb
0.9.6

fastimage
2.1.3

bundler
1.16.2

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

dotenv
2.4.0

emoji_regex
0.1.1

excon
0.62.0

multipart-post
2.0.0

faraday
0.15.2

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20180417

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
0.12.2

gh_inspector
1.1.3

jwt
2.1.0

little-plugger
1.1.4

multi_json
1.13.1

logging
2.2.2

memoist
0.16.0

os
0.9.6

signet
0.8.1

googleauth
0.6.2

httpclient
2.8.3

mime-types-data
3.2016.0521

mime-types
3.1

declarative
0.0.10

declarative-option
0.1.0

uber
0.1.0

representable
3.0.4

retriable
2.0.2

google-api-client
0.21.2

json
1.8.6

mini_magick
4.5.1

multi_xml
0.6.0

plist
3.4.0

rubyzip
1.2.1

security
0.1.3

naturally
2.2.0

simctl
1.6.4

slack-notifier
2.3.2

terminal-notifier
1.8.0

unicode-display_width
1.4.0

terminal-table
1.8.0

tty-screen
0.6.4

tty-cursor
0.5.0

tty-spinner
0.8.0

word_wrap
1.0.0

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.5

xcodeproj
1.5.9

rouge
2.0.7

xcpretty
0.2.8

xcpretty-travis-formatter
1.0.0

badge
0.9.1

builder
3.2.3

gherkin
4.1.3

cucumber-core
1.5.0

cucumber-wire
0.0.1

diff-lcs
1.3

multi_test
0.1.2

cucumber
2.99.0

escape
0.0.4

thor
0.20.0

luffa
2.0.0

slowhandcuke
0.0.3

calabash-android
0.9.2

clipboard
1.1.2

edn
1.1.1

geocoder
1.4.9

command_runner_ng
0.1.3

concurrent-ruby
1.0.5

i18n
0.9.5

run_loop
2.7.1

calabash-cucumber
0.21.5

fastlane-plugin-badge
1.1.0

fastlane-plugin-get_version_code
0.2.0

fastlane-plugin-get_version_name
0.2.2

fastlane-plugin-yarn
1.0

generated on: 2018-06-07

Come one stupid bot, there isn't activity from Fastlane team, I'm waiting on this issue !
You should promote my issue to the team instead of try to close it : Got to hell.

🤦♂

@fastlane-bot uninstall yourself.

Yeah, congrats 👍, good job bot, you're smart, our future is really sexy.
And thank you very much to the fastlane guys for the grateful help, my problem is now fixed thanks to your bot 💪
.............................. 🤦♂

@zedtux I guess your are using react-native, if so you need to change a const define in your test file
#define TIMEOUT_SECONDS 600
Usually the react native project is ootstrap with a test target and this constant is defined in a file name YourProject/YourProjectTest.m


Lambda for godot 3.0

Looks like your history has some issues. You should probably apply your changes to a fresh branch.
Also, you didn't post a description - what is this PR supposed to do?

@cbscribe I thought I should pull it to the lambda branch.

I see - what's this branch for? It looks to be quite old.

You should use git pull --rebase origin/master if you want to rebase the lambda branch on the current master.

@akien-mga Oh,I close first, repull it later.


Can't uninstall deprecated package

I have the language-typescript package installed. Apparently it's deprecated and superseded by atom-typescript, but I'm not interested in keeping it around and would prefer to just uninstall it, but that option is missing for this package specifically.

Would you mind moving this to https://github.com/atom/settings-view?

Moved to https://github.com/atom/settings-view/issues/545


[BUG] No current_branch on release.

Describe the bug
Running a github action caused by a release cut from develop. When using branch-names, current_branch is null during the workflow.
To Reproduce
Steps to reproduce the behavior:

Create workflow with<EMAIL_ADDRESS>Design workflow to trigger on release.
Cut release from branch w/ workflow
current_branch is null

Expected behavior
current_branch shows branch name of branch release is cut from
Desktop (please complete the following information):

OS: github action ubuntu-latest
Version v4.1

This should be fixed now using the latest patch v4.2 or v4. Thanks @almed4

Thanks @jackton1! Incredible turnaround.


Avoid materializing huge intermediate variable

Hi! I'm wondering whether there's a way to lazily evaluate matrix-vector products like in keops, especially on GPU. As a toy example, I'd like to compute
import jax, jax.numpy as jnp
from jax.random import PRNGKey, split, uniform

@jax.jit
def get_Ky(x_i, x_j, y_j):
    assert len(x_j) == len(y_j)
    kernel_ij = jnp.exp(-((x_i[None, :, :] - x_j[:, None, :])**2).sum(-1))
    return kernel_ij * y_j

Evaluating this on large inputs gives an out of memory error:
n = 160000
key_x, key_y = split(PRNGKey(30))
xs = uniform(key_x, (n, 2))
ys = normal(key_y, (n,))
get_Ky(xs, xs, ys)

Is it possible to avoid materializing dist2_ij and kernel_ij?
(Seems related to #787.)

If I understand the question correctly: today you would essentially have to express the "lazy" computation directly, with loops (or jax.lax.map). We could wonder whether XLA might do this as an optimization under jit, but it is unlikely in general across kernels. On the jax side, it is a rather open-ended feature request to introduce a sublanguage for lazy matrix-vector expressions in a way akin to keops.
These are marginal asides, but note that in the current bulk array approach:

You might squeeze in slight gains by vectorizing the expression sum(x ** 2) + sum(y ** 2) - 2 * dot(x, y) in place of sum((x - y) ** 2).
You might find it nice to express your kernel matrix with two vmap calls over an expression-wise entry, like in our kernel least squares example, but this is minor and I would find it more useful when plugging in different kernels.


Create feature-request.md

Issue:
What I did
Added issue template : feature_request.md file
How to test
N/A
@bjavaid @amnajunaid please review the changes and merge them.

:tada: This PR is included in version 3.7.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


mqtt_cpp::server::accept_handler

mqtt_cpp::server::accept_handler = std::function<void(endpoint_t& ep)>;
But the only place where this is called is here:
auto sp = std::make_shared<endpoint_t>(force_move(socket), version_);
if (h_accept_) h_accept_(*sp);

I think that we should change server::accept_handler to
mqtt_cpp::server::accept_handler = std::function<void(std::shared_ptr<endpoint_t> ep)>;

I agree with you.


Allowing ingress controllers owncloud chart

Hello @mcapuccini! As per our discussion, here is the branch for dev testing of the owncloud chart. Any comments and suggestions are more than welcome ;-) Cheers

@carmat88 looks good but it shouldn't be based to master, but in a secondary branch


update README with rebranding

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 21.65%. Comparing base (7cafeb9) to head (90f82e1).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #435   +/-   ##
========================================
  Coverage    21.65%   21.65%
========================================
  Files          297      297
  Lines         9287     9287
========================================
  Hits          2011     2011
  Misses        7276     7276

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Selecting JavaScript option causes failure to build.

What version of Remix are you using?
^1.7.2
Steps to Reproduce

run npx create-remix@latest --template remix-run/indie-stack blog-tutorial
Select JavaScript option

Expected Behavior
Should successfully build; like selecting the TypeScript option does.
Actual Behavior
All migrations have been successfully applied.
Environment variables loaded from .env
Running seed command node --require tsconfig-paths/register prisma/seed.js ...
TypeError: Cannot read properties of undefined (reading 'hash')
at seed (/home/Desktop/myFolder/blogPost/prisma/seed.js:15:39)
An error occured while running the seed command:
Error: Command failed with exit code 1: node --require tsconfig-paths/register prisma/seed.js
🚨 Oops, remix.init failed
Command failed: npm run setup

Duplicate of #164


add efficientdet wrapper

Added this on the kaggle example. Will merge it to the main repo in the next version.

added in .01.5, but multi-scale support not yet


Cursor position problem in amount field

The cursor is always moved to the end of the field during transaction's amount editing.
Reproduction steps:

Create new transaction with amount e.g. 1,234.56 and save it

Open the transaction again and try to change or delete any cipher

Current behavior: The cursor is moved to the end of the number deleting ciphers in front of it while typing.
Expected behavior: The cursor stays in place while typing without replacing existing ciphers..

Guys, I have another problem: gnucash doesnt let to manipulate cursor in ANY field. So if I want to edit a description of a transaction I should retype it entirely.
Is it a variation of this problem, or should I file a new bug?
This is most similar place I found for my issue.

@searoso you mean this happens for you not just in the account field, but in all other text fields as well?

Yes, indeed.
13.02.2015 13:50 пользователь "Ngewi Fet"<EMAIL_ADDRESS>написал:

@searoso you mean this happens for you not just in the account field, but
in all other text fields as well?
—
Reply to this email directly or view it on GitHub.


The "Directory-Layout" wiki page is horribly out of date

https://github.com/mozilla/tofino/wiki/Directory-Layout

So is the in-tree README that was explaining the same/similar thing https://github.com/mozilla/tofino/blob/master/app/README.md

👍

I've linked there from the wiki.


(QENG-1913) rolling back the name change for pe-puppet that was made for AIO

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/Beaker Combined Smoketest/578/
:red_circle: Test failed.

just the known debian failures, unrelated to change

@puppetlabs-jenkins retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/Beaker Combined Smoketest/583/
:red_circle: Test failed.


feat: add package @remirror/extension-gap-cursor

Description
Add @remirror/extension-gap-cursor package

Closes #21 - arrow keys between emoji now work
Closes #17 #15 - outlined composition bugs for emoji and mentions on android should now be fixed

Refactor and slightly improve testing infra

Simplify the node-view and portal interchange. The NodeView is no longer reliant on unstable_renderSubtreeIntoContainer but solely reliant on portals.

Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.

This pull request introduces 5 alerts when merging 5d43a65e828e24ba05b2f6edf17a40ccd8354b50 into e6a099217cb803fa7e7d1655381cab5358022df2 - view on LGTM.com
new alerts:

2 for Superfluous trailing arguments
1 for Useless conditional
1 for Duplicate character in character class
1 for Useless comparison test

Comment posted by LGTM.com


Mixing stage and automatic MaxEventsToSkip

This PR includes a NoPrimaryMix stage in the POMS campaign and the automated calculation of the MaxEventsToSkip factor for resampling stages.

Hi @soleti,
You have proposed changes to files in these packages:

CampaignConfig
MDC2020

which require these tests: build.
@Mu2e/write have access to CI actions on main.
:hourglass: The following tests have been triggered for e6773781c8edd927aafeb5baf98b512d4831f561: build  (Build queue has 1 jobs)
About FNALbuild. Code review on Mu2e/Offline.

:sunny: The tests passed at e6773781c8edd927aafeb5baf98b512d4831f561.

Test
Result
Details

merge
:white_check_mark:
Merged e6773781c8edd927aafeb5baf98b512d4831f561 at c947ccaf2b0e4e6d66091c258cad8a58a49169d0

build (prof)
:white_check_mark:
Log file. Build time: 14 min 26 sec

ceSimReco
:white_check_mark:
Log file.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:white_check_mark:
Log file.

cosmicOffSpill
:white_check_mark:
Log file.

ceSteps
:white_check_mark:
Log file.

ceDigi
:white_check_mark:
Log file.

muDauSteps
:white_check_mark:
Log file.

ceMix
:white_check_mark:
Log file.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at e6773781c8edd927aafeb5baf98b512d4831f561 after being merged into the base branch at c947ccaf2b0e4e6d66091c258cad8a58a49169d0.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.

Muse can put this directory
/cvmfs/mu2e.opensciencegrid.org/Musings/SimJob/%(release)s/link/Production/MDC2020/POMS/samCountFiles.sh
in your path, so you can refer to it with just
samCountFiles.sh
This would work with the local development area too.
Please see how Offline/.muse adds Offline/bin, or I'm happy to put in a PR


Port Required for ARMv8

Can any one Knows, how to port to Cortex-M23 Controller. OS-2 Port is missing for the Same.

Solved the Problem,

Dear my friend @vamsireddybtech,
I have the same question, how to port to cortex-m23? Please share me your sulution.
Thank you very much.


chore(js-init): update init sort

Coverage remained the same at 47.748% when pulling d11b9ba8eed72856e326308a0db5563b722e4df2 on develop into b6e408ac4aa2137e7281a38b6782e22f11516865 on master.


How to check if a PeerID has write-permission

If someone says "here is my database /orbitdb/.../mydatabase"
How do I check if he is the owner of the database, using only his IPFS peerID?

@hazae41 Did you find the solution for this? :)

I found an array named "write" in an object named "access" in the database object

But this array contains orbit-db peerIDs, not ipfs peerIDs

It seems an orbit-db app must only use orbit-db peerIDs as they are the only way of proving an identity
https://github.com/orbitdb/orbit-db/blob/master/GUIDE.md#identity
So an ipfs peerID refers to the device, while an orbit-db peerID refers to a certain profile in the app

Well that is succinct. Thank you!


Structural improvements: enhance schemes, host and basePath handling

On OpenAPI spec current version, schemes, host and basePath are handled this way

schemes, host and basePath are declared on root level
schemes can be overidden on operation

schemes:
  - http
  - https
host: api.domain.com
basePath: /basepath
paths:
  /resources:
    get:
      schemes:
        - https

With current version:

you can only declare one environment in a OpenAPI spec file
all paths and operations shares the same host and basePath
you can only override schemes

Proposed enhancement
1 - Create a new urls object:
urls:
    # (new) Grouping schemes, host and basePath and add optional environments handling.
    schemes:
      # (existing) Moved from root to urls.
      # These schemes are used by all environments if multiple environments are defined.
    host:
      # (existing) Moved from root to urls.
      # This host is used by all environments if multiple environments are defined.
    basePath:
      # (existing) Moved from root to urls.
      # Base path used all environments if multiple environments are defined.
    externalDocs:
      # (new) link to some external documentation
    defaultEnvironment:
      # (new) default environment name if multiple environments are defined
    {environment name}:
      # (new) optional definition per environment
      schemes:
        # (new) schemes for this environment.
        #  Overrides urls.schemes
      host:
        # (new) host for this environnement
        # Overrides urls.host
      basePath:
        # (new) base path for this environment
        # Overrides urls.basePath
      externalDoc:
        # (new) link to some external documentation for this environment

2 - use this new object in paths and its sub-levels (cf. #684 )
# schemes, host and basePath are removed from root
paths:
  # url object can be defined on any level in paths object (paths, path, operation)
  urls:
    # will apply on all paths and operation
    schemes:
      - http
      - https
    basePath: /basepath
    sandbox:
       # host for sandbox environment
       host: api.sandbox.domain.com
    production:
       # host for production environment
       host: api.domain.com
  /resources:
    urls:
      # will apply on all operations
      # declared properties override paths urls properties
      schemes:
        # overriding paths schemes
        - http
    post:
      urls:
        # will apply on this operation
        # declared properties override /resources urls properties
        schemes:
          # overriding /resources schemes
          - https
        sandbox:
          # overriding host for sandbox environment
          host: api.sandbox.specific.domain.com
        production:
          # overriding host for production environment
          host: api.specific.domain.com

@arno-di-loreto Have you seen this PR? It partially addresses what you are looking for.  However, it doesn't explicitly attempt to address the environments problem, although you could use it to do that.  Personally, I would prefer to see environments dealt with in something like apis.json rather than increase the scope of the OpenAPI spec even further.

@darrelmiller I've checked issues but not PR (doh!).
I've thought about apis.json on this topic, it totally make sense if you don't need to override thing in your api definition (but do we really need that). So a second idea would be to remove these data from the spec :-)

parent #560

We've decided to not support environments.
As @darrelmiller mentioned, this is covered by #646, but also covered by #604. The main difference is that #646 needs to be applied to #604 as the structure. Since this is work in progress, we've decided to iterate at the end and clean such things out. However, for easier tracking I'll open a ticket to help us track such changes.


filter: Fix bug where invalid stream name could throw an error.

to reproduce the bug that this fixes:

open search bar
type channel: name-that-doesnt-exist topic:foo and then start typing anything else

Merged, thanks @evykassirer!


Web editor socket connection

Please see below for a short demo. 😎
https://user-images.githubusercontent.com/8352868/152601802-dea49f39-2121-4dce-b33e-907bd66d8824.mp4
Overview
This change adds support for bidirectional communication between the web editor and the LuckPerms plugin, allowing edits made in the editor to be applied in one click. It is implemented using the WebSocket protocol.

The transfer of data between the LuckPerms plugin (runs on the users Minecraft server) and the LuckPerms editor (runs in the users web browser) is facilitated by a separate web service called bytebin.

This is the service that has always powered the web editor, as well as some of my other projects (spark, pastes.dev, etc).
The plugin posts permissions data to bytebin, which stores the data and returns a unique code to reference it.
The user is then prompted to open the editor with the unique code in the URL, which allows the editor to retrieve the posted data. A similar process occurs in reverse when the editor changes are saved. The user has to run a command containing a unique code on their server.

A new service has been introduced called bytesocks (I'm bad at names ok) which is similar to bytebin, except that instead of using GET and POST requests, it allows clients to connect via a WebSocket to a bytesocks "channel" and send messages to other connected clients.

This allows for continuous bi-directional communication without extra action from the user.
However, this opens up some weak points in terms of security which must be considered carefully to ensure the system remains secure.

Security
The following processes and checks have been implemented, which to the best of my knowledge, will ensure that the system is secure (or is at least as secure as the previous system).
1) Signature verification using public/private keypairs

Both the plugin and editor generate and store an RSA keypair
The plugin public key is sent in the initial data payload, and the editor will only acccept messages from the socket if they have a valid signature created with the plugin key.
The editor public key is sent when it first attempts a "handshake" with the server via the socket. The plugin maintains a store of trusted editor public keys. The user will need to manually confirm new browsers when they connect for the first time. The plugin will only accept messages from the socket if they have a valid signature created with a trusted editor key.

2) Other safeguards

The user who initiated the session must remain online on the server for changes to be applied automatically.
The users permission status is re-checked each time an automatic change is received.

Reviews
If you have an understanding of app security, I'd really appreciate your help in this area! The main cryptographic code can be found in ws.js in LuckPermsWeb and the socket package in LuckPerms.
Please have a look at let me know if you think anything has been overlooked. :)
Beta Testing
Most importantly, we need your help testing!
This is a big change and we'd like to catch any remaining bugs or problems before we merge it into the main release. Please download using the links below, unzip and test it out on your server!

LuckPerms-Bukkit-5.3.108.jar.zip
LuckPerms-Sponge-5.3.108.jar.zip

:o

This is incredible! Amazing work!

Amazing dude, thanks


modules/paygate: mount GOOGLE_APPLICATION_CREDENTIALS as filepath, not file contents

Codecov Report

Merging #149 (e66e4e3) into master (4996513) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #149   +/-   ##
=======================================
  Coverage   75.75%   75.75%
=======================================
  Files           1        1
  Lines          33       33
=======================================
  Hits           25       25
  Misses          4        4
  Partials        4        4

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 4996513...e66e4e3. Read the comment docs.

Codecov Report

Merging #149 (e66e4e3) into master (4996513) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #149   +/-   ##
=======================================
  Coverage   75.75%   75.75%
=======================================
  Files           1        1
  Lines          33       33
=======================================
  Hits           25       25
  Misses          4        4
  Partials        4        4

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 4996513...e66e4e3. Read the comment docs.


Syntax highlighting fails when adding display annotation for a return statement

Description:
When adding display annotation for a return statement and there is a json variable just after the method signature,
the VS Code plugin fails to highlight the syntax.
This issue happens only for functions within a class.
But still code compiles and works fine.
Before adding display annotation:

After adding display annotation:

Affected Product Version:
Alpha 2
OS, DB, other environment details and versions:
Mac OS
Steps to reproduce:

Create a class in ballerina.
Add a function which has a return statement.
Add a display annotation for the return statement.
Add a json variable after the method signature.

Following is a sample code
class Bar {
    function k() returns @display {label: "k method"} string {
        json x = {"test": ""};
        return "";
    }
}

For a function not within a class

For a function within a class

Links about the display annotation:
https://github.com/ballerina-platform/ballerina-spec/issues/681
https://github.com/ballerina-platform/ballerina-lang/pull/27626

This is fixed with the alpha3 release. Please check with this vsix.


Add and update temperature docs

on-termperate-condition.md is no more

@ganicke,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


501 Unable to submit request because one or more response schemas specified unsupported field min_length

Expected Behavior
Until this morning this worked. I have this schema and I'm using :
vertexai = "^1.69.0"
google-cloud-aiplatform = "^1.69.0"
And for some reason I receive this error:

501 Unable to submit request because one or more response schemas specified unsupported field min_length. Learn more: https://cloud.google.com/vertex-ai/generative-ai/docs/multimodal/control-generated-output
Request Method: | GET
-- | --
http://localhost:8651/test
5.0.3
MethodNotImplemented
501 Unable to submit request because one or more response schemas specified unsupported field min_length. Learn more: https://cloud.google.com/vertex-ai/generative-ai/docs/multimodal/control-generated-output
This is the schema:
INVOICE_PRODUCTS_SCHEMA = {
"type": "array",
"items": {
"type": "object",
"properties": {
"product_code": {
"type": "string",
"minLength": 1,
"maxLength": 50,
"pattern": "^[a-zA-Z0-9-.]+$",
"description": "A unique identifier for the product. This may include letters, numbers, and specific symbols (hyphen, underscore, period)."
},
"product_description": {
"type": "string",
"minLength": 5,
"maxLength": 500,
"pattern": "^[\w\s,.-]+$",
"description": "A detailed description of the product, typically including its name, type, and key features."
},
"external_product_code": {
"type": "string",
"minLength": 0,
"maxLength": 50,
"pattern": "^[\w\s-.]*$",
"description": "An optional external code used to identify the product in systems outside your organization."
},
"unit_and_quantity_detected": {
"type": "string",
"minLength": 1,
"maxLength": 100,
"pattern": "^[\w\s,()]+(\s\d+)?$",
"description": "The detected unit and quantity of the product, which may include text descriptions (e.g., 'boxes', 'packs') and quantities."
},
"customer_unit_and_quantity_detected": {
"type": "string",
"minLength": 1,
"maxLength": 100,
"pattern": "^[\w\s,()]+(\s\d+)?$",
"description": "The customer-specific unit and quantity detected, similar to the previous field but tailored to the customer's terminology.",
"example": ['20 for 40 Stuck', 'pro 10 stk', '20uz', 'Dis a 50 Stk', '60 Stuck/Dispenser', '20 Stuck/Dispenser', '30 Stuck', 'a 50 ST', 'Pack a 10 Stk', 'only a integer']
},
"product_quantity": {
"type": "integer",
"minimum": 1,
"description": "The actual quantity of the product being purchased, which must be a positive integer."
},
"unit_price": {
"type": "number",
"minimum": 0.01,
"description": "The price per unit of the product, expressed in the appropriate currency format with two decimal places."
}
},
"required": ["product_code","product_description","external_product_code","unit_and_quantity_detected","customer_unit_and_quantity_detected","product_quantity","unit_price"],
},
}

This was working until 2 hrs ago or something like that, And in the documentation I can see that we can use this schema:
https://cloud.google.com/vertex-ai/docs/reference/rest/v1/Schema
Specifications

Version: 1.69.0

@mihalaches: can you please check if it's still happening to you? Thanks.

@gericdong There is a similar issue happening right now (since 30 min ago) on the "pattern" field of the response schema, with error:
'Arguments: (InvalidArgument('Unable to submit request because one or more response schemas specified unsupported field pattern. Learn more: https://cloud.google.com/vertex-ai/generative-ai/docs/multimodal/control-generated-output'),)'
However, this was all working perfectly fine and now it seems to crash it. VertexAI works if I remove the 'pattern' field, but can you please double-check and see what the cause behind this is? Thanks
response_schema = {         "type": "object",         "properties": {             value_researched : {                 "type": "object",                 "properties": {                     "value": {                 "type": "string",                 "description": "Value we are looking for. Nothing should be invented : values should be found in the provided documents, infered from provided documents.",                 "default": ""                 },                     "sourceQuote": {                         "type": "string",                         "description": "Grounded text, extracted from the source document you took the value from. \                             It should be as much as possible an exact extract from the document, used to determine the value. \                             The source should be self sufficient and not require any additional context. \                             Nothing should be invented, if the source can not be found, that should be stated clearly.",                         "default": ""                     },                     "document": {                         "type": "string",                         "description": "Exact file name (or file names, if multiple ones where used) of the file(s) you extracted the information from.",                         "default": "AI was not able to identify a document."                     }                 },                 "required": ["value", "sourceQuote"]             }         },         "required": [value_researched]     }

I'm getting same error from the beginning.
version:
google-cloud-aiplatform = "^1.60.0"