WebSocket connection to 'ws://localhost:3000/nuxt_devtools/entry' failed

Using devtools when another middleware websocket is registered won't work.
WebSocket connection to 'ws://localhost:3000/__nuxt_devtools__/entry' failed:
Maybe devtool can check url path, or registering only necessary path for filtering implementation ?
https://github.com/nuxt/devtools/blob/4deb883e190149dad3b1c5475b02d3db44edec6e/packages/devtools/src/server-rpc/index.ts#L83

We temporarily close this due to the lack of enough information.
Please provide a minimal reproduction to reopen the issue.
Thanks.

Why reproduction is required

Running into the same issue when I have another module that uses websockets.
Steps to reproduce:
Install nuxt,
Install nuxt-socket-io module
Install devtools module
Try running the project with both modules active.


Obsoletions: translation regulator activity and children

There are some horrible terms under 'translation regulator
activity', and I don't believe any of them are true functions.
Many are defined to sound like proteins and are defined by
being involved in a certain process.
If you have any comments or other suggestions for
alternatives, please add them; otherwise I will obsolete
these terms after returning from the GO meeting.
Those terms in full:
translation regulator activity ; GO:0045182
Any substance involved in the initiation, activation,
perpetuation, repression or termination of polypeptide
synthesis at the ribosome.
-->translation ; GO:0043037
translation factor activity, non-nucleic acid binding ; GO:
0045183
Any of a group of soluble proteins involved in polypeptide
synthesis at the ribosome which do not bind to nucleic
acids.
-->translation ; GO:0043037
translation factor activity, nucleic acid binding ; GO:
0008135
Functions during translation by binding nucleic acids during
polypeptide synthesis at the ribosome.
-->translation ; GO:0043037, nucleic acid binding ; GO:
0003676
translation activator activity ; GO:0008494
Any of a group of soluble proteins functioning in the
activation of ribosome-mediated translation of mRNA into a
polypeptide.
-->positive regulation of translation ; GO:0045946
translation elongation factor activity ; GO:0003746
Functions in chain elongation during polypeptide synthesis
at the ribosome.
-->translational elongation ; GO:0006414
translation initiation factor activity ; GO:0003743
Functions in the initiation of ribosome-mediated translation
of mRNA into a polypeptide.
-->translational initiation ; GO:0006413
translation termination factor activity ; GO:0008079
Functions in the termination of translation.
-->translational termination ; GO:0006415
translation release factor activity ; GO:0003747
Involved in catalyzing the release of a nascent polypeptide
chain from a ribosome.
-->translational termination ; GO:0006415
translation release factor activity, codon nonspecific ; GO:
0016150
A translation release factor that is not specific to particular
codons; binds to guanine nucleotides.
-->translational termination ; GO:0006415, guanine
binding ; GO:0050NEW
translation release factor activity, codon specific ; GO:
0016149
A translation release factor that is specific for one or more
particular termination codons; acts at the ribosomal A-site
and require polypeptidyl-tRNA at the P-site.
-->translational termination ; GO:0006415, ribosome
binding ; GO:0043022
translation repressor activity ; GO:0030371
Antagonizes ribosome-mediated translation of mRNA into a
polypeptide.
-->negative regulation of translation ; GO:0016478
translation repressor activity, non-nucleic acid binding ; GO:
0000901
Antagonizes the ribosome-mediated translation of mRNA
into a polypeptide but does not bind directly to nucleic acid.
-->negative regulation of translation ; GO:0016478
translation repressor activity, nucleic acid binding ; GO:
0000900
Antagonizes the ribosome-mediated translation of mRNA
into a polypeptide via direct binding to nucleic acid.
-->negative regulation of translation ; GO:0016478,
nucleic acid binding ; GO:0003676
Reported by: girlwithglasses
Original Ticket: "geneontology/ontology-requests/1438":https://sourceforge.net/p/geneontology/ontology-requests/1438

thanks www.movied.org

As of today, there are only 111 manual annotations.

We have 4 annotations and would be very happy for this to go away.
In fact I will reannotate now to:
byr4 MF mRNA binding involved_in  BP positive regulation of cytoplasmic translation
ppr4 MF mRNA binding involved_in  BP positive regulation of mitochondrial  translation
puf6  mRNA 3'-UTR binding   BP negative regulation of cytoplasmic translation
mss51 MF none  BP positive regulation of mitochondrial  translation
and block this internally. It has no meaning other than "regulation of translation"

Actually PAscale that isn't everything.
Although we only have 4 annotations to "translation regulator" we have 7 to "translation release factor" so there must be some "missing parents"
Probably need to reevaluate annotation numbers before proceeding.

This one is housed under
http://www.ebi.ac.uk/QuickGO/GTerm?id=GO:0003747
"translation factor activity RNA binding"
so would need to count these.
Anything with "factor" in the term name.
https://github.com/geneontology/go-ontology/issues/13536

Nice review here: PMID:28363112
We'll wait to have done more progress on transcription to make sure these two branches are consistent with each other.

This has been delt with by recent tickets @pgaudet reopen if you disagree


How to customize video record layout  ?

First I would like to thank for wonderful sdk.
I am facing the issue on customization for embedded video recorder. voice, camera switch, done, start recording options should be out side of the video view (will use custom buttons as per my design). I do not want show any icon in the video view.
can you please help me on this ?

OnPageLoad recording should be started through front cam
Camera switch access
By Tapping Stop button, video recording should be stop and start upload to server

Hi @rameshkec85,
You can change default camera to front by putting Camera.CameraInfo.CAMERA_FACING_FRONT as argument for preferredCameraId.
Unfortunately there is no way for ui customisation for now. On monday I will think what will be the best way for such kind of functionality and will back to you with estimates for it.

@3akat  Thanks very much. Can you fix it asap as this is urgent requirement for me.

@rameshkec85
Already working on it, will be ready tomorrow.

Hi @rameshkec85,
I've added ability to specify custom layout for recorder. To do it you will need

Update to latest sdk version.
Use method .setRecorderLayout(int layoutResId)
In your custom layout if you need everything from default layout but with custom designs you need to use following ids for your views:

vg_recorder - for root view
sv_video - for SurfaceView
iv_voice_indicator - for sound indicator
tv_time_status - for recording time progress
v_play - for starting video player
v_switch_camera - for camera switching
v_start_stop - for start and stop recording
v_send_and_close - for ability to send video immidiate

If you need only views which are shown in you screenshot, you will need

sv_video - for SurfaceView
tv_time_status - for recording time progress
v_start_stop - for start and stop recording.

Feel free to tell me if you need something more.

Button clicks are not working. Can you try with the following code in your sample(by update the latest version) and I want to remove select thumbnail after stop the video reocrding (it should not be displayed  since user should not interact with recording.).
my_custom.xml

<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
android:id="@+id/activity_main"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:orientation="vertical"

<LinearLayout
    android:layout_width="match_parent"
    android:layout_height="wrap_content"
    android:layout_margin="5dp"
    android:background="#FD0"
    android:gravity="center_vertical">

    <ImageView
        android:id="@id/iv_switch_camera"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:layout_margin="5dp"
        android:src="@drawable/ic_switch_camera"
        android:text="@string/start" />

    <ImageView
        android:id="@id/iv_start"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:layout_margin="5dp"
        android:src="@drawable/ic_start"
        android:text="@string/start" />

    <ImageView
        android:id="@id/iv_play"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:src="@drawable/ic_play"
        android:text="@string/start" />

</LinearLayout>

<com.ziggeo.androidsdk.ui.views.AdaptiveSurfaceView
    android:id="@id/sv_video"
    android:layout_width="200dp"
    android:layout_height="200dp"
    android:layout_gravity="center_horizontal" />

Activity:
setContentView(R.layout.activity_main);
Ziggeo ziggeo = new Ziggeo(APP_TOKEN);
long maxDuration = 20000L;
ziggeo.setSendImmediately(false);
ziggeo.setRecorderLayout(R.layout.my_custom);
ziggeo.attachRecorder(getFragmentManager(), R.id.fl_content, maxDuration, true, this);

@rameshkec85
From what I can see, you're not following rules that I've described above.

You don't need ziggeo.setSendImmediately(false);
ids should be

v_switch_camera instead of iv_switch_camera
v_start_stop instead of iv_start
v_play instead of iv_play

Regarding to other points.
If seems you've missed some part of your layout, when you will provide full layout I will test it.
Also hiding thumbnail selection is not currently supported. Will start work now on it.
com.ziggeo.androidsdk.ui.views.AdaptiveSurfaceView is not prepared to fit any random size, it needs to be improved, I will do it, but it will take some time, so if you need it asap you can make your own implementation.

@3akat Thanks very much. Its working now except thumbnail selection and customizing surface view (I'll try to customize it).

Hi @rameshkec85,
I've updated sdk, please use ziggeo.setShowCoverShotSelectionPopup(false) to prevent thumbnail selection.

Thanks very much @3akat
Its not picking up the custom layout if using the following code.
        ziggeo.setRecorderLayout(R.layout.my_custom);
        ziggeo.attachRecorder(getFragmentManager(), R.id.fl_content, maxDuration, Camera.CameraInfo.CAMERA_FACING_FRONT, this);

where this is working fine with custom layout but I want to force camera front face .
        ziggeo.setRecorderLayout(R.layout.my_custom);
        ziggeo.attachRecorder(getFragmentManager(), R.id.fl_content, maxDuration, false, this);

And I have one more doubt, how to start auto start recording without tapping button ?
Ziggeo ziggeo = new Ziggeo(APP_TOKEN, this);
     long maxDuration = 20000L;
     ziggeo.setSendImmediately(true);
     ziggeo.setShowCoverShotSelectionPopup(false);
     ziggeo.setRecorderLayout(R.layout.my_custom);
     ziggeo.attachRecorder(getFragmentManager(), R.id.fl_content, maxDuration, false, this);

Hi @rameshkec85,
Will check the bugs today.
Unfortunately there is no ability to start recording without tapping button. Are you sure you need it? It seems user need some time to focus camera on things he want to shoot.

@3akat  Yes, this is major requirement for my app (start recording on load) or else  Can you give callback once camera is ready ?

@rameshkec85 I can start recording right after screen loads, but the camera need some time to start recording. On some devices it will take 0.5 second, on some maybe 2 seconds. How in that case we should indicate that recording was started?

@rameshkec85
Fixed bugs with cover shot popup and custom layout.

Closing it due to inactivity.
@rameshkec85 please, open it if you have any issues regarding recorder customization.

Hi,
I am still facing many customisation issues using this sdk. Can u help me on this ? or can u provide  control on VideoRecorderFragment ?

I want to play the recording video. (there is no way to get recorded file name)
Needs to add Begin, Stop && finish etc. based on the recording state.
Timer format needs to be changed as per my requirement (ex. 5 Secs )

I felt very difficult to customising UI based on my requirement. Is there any work around this ?

Hi @rameshkec85,
The things you described related more to functionality than to UI castomisation.

Needs to add Begin, Stop && finish etc. based on the recording state.

Such functionality requires a lot of architectural changes, so it will not be ready in nearest time.

I want to play the recording video. (there is no way to get recorded file name)

There is method in ziggeo class called setVideoRecordingProcessCallback, I will update callback and put path there.

Timer format needs to be changed as per my requirement (ex. 5 Secs )

I can add ability to set custom formatter for time in millis. Will it be enough?

@3akat :
Thanks,

Provide me the url that i can play it ziggeo video player in one screen (should be embeded in screen where other buttons also required to place)
Custom Timer format

Hi @rameshkec85,
We've added CameraView in new version.
Please, check it out, it provides ability for any customisations.


Update to use with more recent Dakota versions

Recent versions of Dakota do not work well with Carolina, because they require a more recent version of boost, which is not compatible anymore with Carolina. This is just an issue of using different boost libraries.
There is now a patch in the Carolina repository that can be applied with git apply to fix the setup file to work with recent versions of Dakota.
To make usage of Carolina straightforward again, these changes should be integrated into the setup.py, without affecting usage with older versions of Dakota.

Resolved through referenced issues.


Chore/fds-206 remove design tokens as peer-dependency from Cascara

Resolves FDS-206.
Dependencies
Design tokens was listed as peer-dependency for Cascara, which is incorrect. This PR removes such dependency.

Fails

:no_entry_sign:
Please add a '### Dependencies' section to explain the reason we are changing dependencies.

Warnings

:warning:
Please assign someone to merge this PR, and optionally include people who should review.

  Generated by :no_entry_sign: dangerJS against bca8ab53ac14fd3cdd9a560e3c416f6d29554d4f


denomination of fees

fee denominiation is unclear and numbers are off
e.g. "fee for settlement of delivery: 29199.838 sat --> 2919 ppm"

alles gut.


Error when resolving dependency com.reposilite:reposilite:3.0.3

What happened?
I want to write a plugin for reposilite and have a completely fresh maven java project created with:
mvn archetype:generate -DgroupId=group -DartifactId=plugin -DarchetypeArtifactId=maven-archetype-quickstart -DarchetypeVersion=1.4 -DinteractiveMode=false

I added the following to pom.xml
<repositories>
  <repository>
    <id>reposilite-repository-releases</id>
    <name>Reposilite Repository</name>
    <url>https://maven.reposilite.com/releases</url>
  </repository>
</repositories>

<dependencies>
  <dependency>
    <groupId>com.reposilite</groupId>
    <artifactId>reposilite</artifactId>
    <version>3.0.3</version>
  </dependency>
</dependencies>

Also changed the compiler version to 11.
And get this error when running mvn install -U:
Could not find artifact com.reposilite:reposilite-frontend:jar:3.0.3 in maven-reposilite-repository-releases (https://maven.reposilite.com/releases)

Also get the same error when using the uber jar:
<dependencies>
  <dependency>
    <groupId>com.reposilite</groupId>
    <artifactId>reposilite</artifactId>
    <version>3.0.3</version>
    <classifier>all</classifier>
  </dependency>
</dependencies>

Reposilite version
3.x
Relevant log output
No response

Works now with 3.0.4-SNAPSHOT. Thank you.


Fix broken cluster role

The cluster role is broken. The items in the list must be quoted individually.
See https://kubernetes.slack.com/archives/C09NXKJKA/p1543244788508000.

Thanks for the contribution! This makes sense, sorry for the mistake. Can you just run make generate-in-docker and commit the changes? That should make CI succeed :slightly_smiling_face: .

lgtm :+1: thanks!


implement a model for speakers

This has been implemented in https://github.com/TechStreamConference/website-backend/pull/20


Crash when opening invalid XML scene

Operating system or device - Godot version:
Windows 10 . Godot Version 2.1 stable
Issue description (what happened, and what was expected):
I was trying to open a .tscn file. By mistake, I hit an XML file. Godot crashes.
This looks silly, but somebody could lost unsaved work if it happens.
Steps to reproduce:
Open a project which has XML file. Go to Open Scene, and select that wrong XML File.
Link to minimal example project (optional but very welcome):
Open godot demos. Open 3d In 2D example. Click on Scene -> Open Scene. Select player.xml.
Godot crashes.

There is no XML file in the 3D in 2D demo:
$ find .
.
./player.scn
./player_2d.scn
./engine.cfg
./robot_demo.png
./icon.png
./main.scn
./player_3d.scn

Are you using demos from Godot 1.1 or earlier?

That's weird. I can't find that XML file on the latest 2.1 demos. I'll check it again when I get home.

It looks like I had an old XML file.
player.zip

For the reference, for whom wants to fix this issue:

Download the above zip archive
Check that opening that XML file still triggers the bug
Run the editor through a debugger and open the XML file
Find where it crashes, prevent it and raise an error instead (no need to try to fix loading that XML, it's a corner case)

I thought XML is no longer a valid scene format, therefore it simply won't attempt to open it?

Hm that's a good point. And it seems to be a corner case (no other users affected), so probably not worth keeping around for the 2.1 branch.


Test as I explore code

Hi @jkaving,
As I mentioned yesterday, I added some tests and did a bit of refactoring as I went through the code.
/Raul

Ready for merge.

Ready for merge.


Ensure that generate pdf is machine readable (for ATS systems)

Hi,
Most resumes are now parsed by Applicant Tracking Systems and sometimes resumes written in latex are not parseable by ATS.
\pdfgentounicode=1 from the glypthtounicode package ensures that the output pdf is parseable.
Thanks!

Thanks for adding this. Really appreciate it.


Add step to read bounding box from build_parameters.yml as an area

At the moment, the routing engine reads in large files (at the level of states/countries) and we'd like to use a service that extracts one small part of a file to make sure it's not too long to rebuild the tool.
https://app.protomaps.com/downloads/osm is such a service
https://extract.bbbike.org/?sw_lng=-74.159&sw_lat=40.533&ne_lng=-73.685&ne_lat=40.755&format=osm.pbf&city=whatever&lang=en is another.
We could also download a file containing the bounding box and cut it ourselves before processing, it should be much faster but is more involved.

The GUI allows this now, but this feature would be useful as part of the dockerbuild as well


[Frontend] Fix decomposition tests

Context:  Recent changes in the TOML files broke some tests.
Description of the Change: Fix those tests.
Benefits: Latest/latest/latest passes again (at least for lightning.qubit).
Comment:
The minimum version of pennylane-lightning required is 0.37.0-dev7 but those wheels failed to be uploaded. I have used 0.37.0-dev9. If the minimum version required is required for this PR, let me know and I will ask the team to push wheels for -dev7
[sc-63376]

I'm not sure how much of this PR is clashing with #718 and #712, could you double check?

I'm not sure how much of this PR is clashing with https://github.com/PennyLaneAI/catalyst/pull/718 and https://github.com/PennyLaneAI/catalyst/pull/712, could you double check?

I'm happy to close this PR without merging if #718 and #712 would fix latest/latest/latest.

I'm not sure how much of this PR is clashing with #718 and #712, could you double check?

I'm happy to close this PR without merging if #718 and #712 would fix latest/latest/latest.

We need #712 . I would suggest to merge it instead of this PR. #712 addresses exactly this issue, but in my opinion - in a more systematic way: it adds an option to modify capabilities directly so we no longer need to stick to a particular toml syntax in tests.
The #718 fixes another toml leftover, it requires #712 as a prerequisite.

I'm not sure how much of this PR is clashing with #718 and #712, could you double check?

I'm happy to close this PR without merging if #718 and #712 would fix latest/latest/latest.

We need #712 . I would suggest to merge it instead of this PR. #712 addresses exactly this issue, but in my opinion - in a more systematic way: it adds an option to modify capabilities directly so we no longer need to stick to a particular toml syntax in tests.
The #718 fixes another toml leftover, it requires #712 as a prerequisite.

Let's give those PRs the final push! @grwlf can you ensure relevant discussions are resolved with the reviewers and merged this week?

@dime10 and @grwlf just commenting that this is probably no longer required, right?

@dime10 and @grwlf just commenting that this is probably no longer required, right?

Probably not 👍


Misc Makefile improvements for quiet mode V=0

See commits for more details.

test/bpf: Fix compilation with V=0
Makefile: Fix dirname errors with empty PRIV_TEST_PKGS
Makefile: Print quiet lines for each package tested
.travis: Make output less verbose

Filed #20034 for ConformanceKind1.19 failure.

Fixed a breakage in privileged tests. Will run one of the jenkins jobs to make sure those tests run.

/test-1.16-4.9


Yaml file or Colab Notebook?

Hi, I am trying to install DeepPocket using the listed dependencies but running into many conflicts between packages. Could you please provide an updated .yml file or perhaps a Google Colab Notebook that installs the dependencies and runs DeepPocket? Many thanks!

Do you still need one? I will create one over the weekend maybe but I just need to know if this is urgent

I think I figured it out and got it running. I can share the notebook if you want!


Quick way to get an nREPL going?

This is not necessarily a conjure question. Just wondering. I want to run eval some code, and test some snippets. I would prefer not having to bootstrap a whole project for that. Is there an easy way to get an nREPL going, like a default one? Thanks in advance!

Of course! It can all be started from one command, even with CIDER middleware 😄 (assuming you have the Clojure CLI installed)
clojure -Sdeps '{:deps {nrepl {:mvn/version "0.7.0"} cider/cider-nrepl {:mvn/version "0.25.2"}}}' -m nrepl.cmdline --middleware '["cider.nrepl/cider-middleware"]'

(taken from the CIDER docs)

I've added this to the Clojure on the JVM quickstart guide too.

POIFECT! Thank you very much for the prompt reply. I have just added the alias below to my .bashrc.
alias nrepl=clojure -Sdeps '{:deps {nrepl {:mvn/version "0.7.0"} cider/cider-nrepl {:mvn/version "0.25.2"}}}' -m nrepl.cmdline --middleware '["cider.nrepl/cider-middleware"]'

By the way. What do you think about this feature. Conjure could "run" the command above on the background, in case it doesn't find any active nREPL instances. What do you think?

Nice! Glad it was what you were looking for 😄
And yeah, that's what I would call "jack in" and I'm still kind of avoiding it at the moment because as soon as I add it it becomes "could ya just add this config to make it do this" and before you know it you have a Clojure environment manager built into Conjure. Something that I may get around to one day.
I was hoping someone would step in before me and write a great plugin for this before I had to do it 😅

Thank you for your help. And for the insight into the implication of such a design change. My problem is solved! Closing the issue now. Thank you!

Not a problem! I would love to have a one button setup in the future, it's just something that opens up a can of question and config worms that I don't want to tackle just yet. Too many bigger fish to fry!
A plugin to start various REPL servers (not even just Clojure!) to pair with Conjure would be amazing, maybe I'll do it one day or write up enough help and outline that it'll be easy for someone else to implement and maintain.

There is the vim-jack-in plugin that I find very useful.

Oh neat! Thank you @chopptimus I need to have a look at it! It seems pretty generic, I had a feeling it'd be tied to fireplace but nope, it just starts a REPL. Then I guess if it created a .nrepl-port file you could just hit <prefix>cf and away you go.  Thanks for creating it @SevereOverfl0w!

I'll give it a trial run and probably recommend vim-jack-in from the docs if it works well for me 😄

I use vim-jack-in all the time, let me know if you need a hand.   I'm on slack all day.


Null pointer exception in jira collector after connecting to Jira server

When the jira collector connects to my jira server. It throws null pointer exception twice. What could be the reason for the error. Please see the log below.
2017-02-07 10:53:00,002 INFO  c.c.d.collector.CollectorTask - Running Collector: Jira
2017-02-07 10:53:00,007 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2017-02-07 10:53:00,009 INFO  c.c.d.collector.CollectorTask - http://<IP_ADDRESS>:8989/
2017-02-07 10:53:00,009 INFO  c.c.d.collector.CollectorTask - -----------------------------------
2017-02-07 10:53:00,010 DEBUG c.c.d.client.team.TeamDataClientImpl - Constructing data collection for the feature widget, team-level data...
2017-02-07 10:53:10,984 ERROR c.c.d.client.DefaultJiraClient - IOException
java.net.ProtocolException: Server redirected too many  times (20)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1884) ~[na:1.8.0_111]
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) ~[na:1.8.0_111]
        at java.net.URLConnection.getContent(URLConnection.java:739) ~[na:1.8.0_111]
        at com.capitalone.dashboard.client.DefaultJiraClient.getTeams(DefaultJiraClient.java:192) ~[jira-feature-collector.jar!/:2.0.5-SNAPSHOT]
        at com.capitalone.dashboard.client.team.TeamDataClientImpl.updateTeamInformation(TeamDataClientImpl.java:61) [jira-feature-collector.jar!/:2.0.5-SNAPSHOT]
        at com.capitalone.dashboard.collector.FeatureCollectorTask.collect(FeatureCollectorTask.java:107) [jira-feature-collector.jar!/:2.0.5-SNAPSHOT]
        at com.capitalone.dashboard.collector.FeatureCollectorTask.collect(FeatureCollectorTask.java:28) [jira-feature-collector.jar!/:2.0.5-SNAPSHOT]
        at com.capitalone.dashboard.collector.CollectorTask.run(CollectorTask.java:63) [core-2.0.5-SNAPSHOT.jar!/:2.0.5-SNAPSHOT]
        at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) [spring-context-4.1.7.RELEASE.jar!/:4.1.7.RELEASE]
        at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81) [spring-context-4.1.7.RELEASE.jar!/:4.1.7.RELEASE]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_111]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_111]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_111]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_111]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_111]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_111]
        at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]
2017-02-07 10:53:12,710 DEBUG c.c.d.client.team.TeamDataClientImpl - Size of paged Jira response: 75
2017-02-07 10:53:13,132 INFO  c.c.d.collector.CollectorTask - Team Data              75       13s
2017-02-07 10:53:13,132 DEBUG c.c.d.c.p.ProjectDataClientImpl - Constructing data collection for the feature widget, project-level data...
2017-02-07 10:53:14,381 DEBUG c.c.d.c.p.ProjectDataClientImpl - Size of paged Jira response: 75
2017-02-07 10:53:14,719 INFO  c.c.d.collector.CollectorTask - Project Data           75        1s
2017-02-07 10:53:14,720 DEBUG c.c.d.c.story.StoryDataClientImpl - Constructing data collection for the feature widget, story-level data...
2017-02-07 10:53:14,726 ERROR c.c.d.collector.FeatureCollectorTask - Failed to collect jira information
java.lang.NullPointerException: null
        at com.capitalone.dashboard.client.DefaultJiraClient.getStatusMapping(DefaultJiraClient.java:320) ~[jira-feature-collector.jar!/:2.0.5-SNAPSHOT]
        at com.capitalone.dashboard.client.story.StoryDataClientImpl.updateStatuses(StoryDataClientImpl.java:726) ~[jira-feature-collector.jar!/:2.0.5-SNAPSHOT]
        at com.capitalone.dashboard.client.story.StoryDataClientImpl.updateStoryInformation(StoryDataClientImpl.java:152) ~[jira-feature-collector.jar!/:2.0.5-SNAPSHOT]
        at com.capitalone.dashboard.collector.FeatureCollectorTask.collect(FeatureCollectorTask.java:119) [jira-feature-collector.jar!/:2.0.5-SNAPSHOT]
        at com.capitalone.dashboard.collector.FeatureCollectorTask.collect(FeatureCollectorTask.java:28) [jira-feature-collector.jar!/:2.0.5-SNAPSHOT]
        at com.capitalone.dashboard.collector.CollectorTask.run(CollectorTask.java:63) [core-2.0.5-SNAPSHOT.jar!/:2.0.5-SNAPSHOT]
        at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) [spring-context-4.1.7.RELEASE.jar!/:4.1.7.RELEASE]
        at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81) [spring-context-4.1.7.RELEASE.jar!/:4.1.7.RELEASE]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_111]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_111]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_111]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_111]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_111]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_111]
        at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]

This is the property file which we have used
#PageSize
feature.pageSize=50

# api.query.folder=${base.config.dir}/jiraapi-queries
feature.queryFolder=jiraapi-queries
# Jira API Query file names (String template requires the files to have .st extension)
feature.storyQuery=story
feature.epicQuery=epic
feature.projectQuery=projectinfo
feature.memberQuery=memberinfo
feature.sprintQuery=sprintinfo
feature.teamQuery=teaminfo
feature.trendingQuery=trendinginfo

#Jira Connection Details
#feature.jiraProxyUrl=
#feature.jiraProxyPort=
######################
# Trending Query need Number of Days After today to filter out Sprints which ends in future.
# This will used to filter Kanban project which has 20 years of Sprints
feature.sprintDays=60
# Trending Query also need Number of Days prior to look for Sprints which has already Ended
feature.sprintEndPrior=7
######################
#Scheduled Job prior minutes to recover data created during execution time
feature.scheduledPriorMin=2
#Delta change date that modulates the collector item task (which should not see changes often)
feature.deltaCollectorItemStartDate=20016-10-01T00:00:00.000000

######################
#Spring Application Properties
spring.data.mongodb.database=dashboarddb
spring.data.mongodb.host=localhost
spring.data.mongodb.port=27017
spring.data.mongodb.username=dashboarduser
spring.data.mongodb.password=dbpassword

#Jira Connection Details
feature.jiraBaseUrl=http://myjiraserver.com/
feature.jiraCredentials=UGFsYW5pdmVsbjpUdXR1QDA2Kg==
#feature.jiraOauthAuthtoken=oauth, not used
#feature.jiraOauthRefreshtoken=oauth, not used
#feature.jiraOauthRedirecturi=uri.this.is.test:uri
#feature.jiraOauthExpiretime=234567890987
# In Jira, general IssueType IDs are associated to various "issue"
# attributes. However, there is one attribute which this collector's
# queries rely on that change between different instantiations of Jira.
# Please provide the name value reference to your instance's IssueType for
# the lowest level of Issues (e.g., "user story") specific to your Jira
# instance.  Note:  You can retrieve your instance's IssueType Name
# listings via the following URI:
# https://[your-jira-domain-name]/rest/api/2/issuetype/.  It is listed as
# attribute "name" in the JSON response.
feature.jiraIssueTypeId=7
# In Jira, your instance will have its own custom field created for "sprint" or "timebox" details,
# which includes a list of information.  This field allows you to specify that data field for your
# instance of Jira. Note: You can retrieve your instance's sprint data field name
# via the following URI, and look for a package name com.atlassian.greenhopper.service.sprint.Sprint;
# your custom field name describes the values in this field:
# https://[your-jira-domain-name]/rest/api/2/issue/[some-issue-name]
feature.jiraSprintDataFieldName=customfield_10700
# In Jira, your instance will have its own custom field created for "super story" or "epic" back-end ID,
# which includes a list of information.  This field allows you to specify that data field for your instance
# of Jira.  Note:  You can retrieve your instance's epic ID field name via the following URI where your
# queried user story issue has a super issue (e.g., epic) tied to it; your custom field name describes the
# epic value you expect to see, and is the only field that does this for a given issue:
# https://[your-jira-domain-name]/rest/api/2/issue/[some-issue-name]
feature.jiraEpicIdFieldName=customfield_10702

######################
#Chron schedule: S M D M Y [Day of the Week]
feature.cron=0 * * * * *

#StartDate
feature.deltaStartDate=2017-01-30T00:00:00.000000
feature.masterStartDate=2016-10-01T00:00:00.000000

#Core Artifacts
# These arrays of status mappings must be completed in order for custom source system statuses to be providable by
# Hygieia.  Currently, Hygieia only maps to the following 3 status mappings:  to do, doing, and done.  You can find
# all available issue status mappings by going to your instance's version of the following API call:
# http://fake.jira.com/rest/api/2/status/.  Your statuses are listed in the JSON response as "name."
feature.todoStatuses[0]=OPEN
feature.doingStatuses[0]=IN PROGRESS
feature.doingStatuses[1]=TEST
feature.doingStatuses[2]=TESTING
feature.doneStatuses[0]=DONE
feature.doneStatuses[1]=CLOSED

@roshanvc Try setting feature.pageSize to 25.
Also change feature.jiraIssueTypeId to feature.jiraIssueTypeNames and set its value accordingly.
Also add/set as blank feature.jiraTeamFieldName=
to specify no tempo teams

@satishc1 : Tried to suggestions, still getting the same error :-(

@roshanvc Does your jira setup have tempo teams ? Paste your command that you are using to start the jira collector.

@roshanvc - Are you still facing this issue? If so, can you please paste the command you are using?

@roshanvc I am closing this issue. If you are still facing problems please reopen.


Graphical bug fixes

This update mostly brings bug fixes related to visual errors such as animations looping incorrectly and gui elements being too close together. As well as this, the collision of Base Zone Act 2 has been restored.
As featured in #36.

Looking over the changes I don't see any conflicts and any issues I did find I'll probably be fixing myself as I do more work on this branch, Good work.


documentation — fail, empty reason, for PR #25203

documentation — fail, can't find reason, for PR #25203, are there anyone meeting this:
Build Errors:
Fix the path under windows for dockerimages.md: https://github.com/docker/docker/pull/25203
Filtered (engine) Summary:
Found: 852 files
Found: 0 errors

Thanks for the report: I think that's a known (and temporary) issue with the documentation CI. Ping @thaJeztah and @SvenDowideit for confirmation!

Hm, the temporarily broken links are fixed now (still some broken links in others repos it seems), but it seems the end result is UNSTABLE
@SvenDowideit do you know what's the cause if that?

Got a reply from @SvenDowideit (he's traveling, so from his phone); and he suspects it's due to network instabilities during the test, so can be ignored

Link is https://jenkins.dockerproject.org/job/docs-docker-pr/11513/console

I tried to re-test, result is unstable,  but it still display: documentation — fail

@SvenDowideit would have a look at the CI, possibly change some configuration

yeah, every now and then jenkins is just mean to us :)
I think I've fixed a new issue that cropped up with the v1.12 GA release, so I'm going to close this - please kick me under the table if things go wonky again :)


500 is not a valid SSR component in Sapper

This is a very nice component.
I have setup a page exactly like the demo https://github.com/shiryel/saos/blob/master/demo/src/Animations.svelte
in Sapper and it works nice but I get the following error once in a while

500
 is not a valid SSR component. You may need to review your build config to ensure that dependencies are compiled, rather than imported as pre-compiled modules
Error:  is not a valid SSR component. You may need to review your build config to ensure that dependencies are compiled, rather than imported as pre-compiled modules
at validate_component (/home/web/svelte-sapper-experiments/sapper/dev/server/server.js:291:15)
at /home/web/svelte-sapper-experiments/sapper/dev/server/server.js:2163:48
at Object.$$render (/home/web/svelte-sapper-experiments/sapper/dev/server/server.js:309:22)
at Object.default (/home/web/svelte-sapper-experiments/sapper/dev/server/server.js:2982:86)
at Object.default (/home/web/svelte-sapper-experiments/sapper/dev/server/server.js:2728:84)
at /home/web/svelte-sapper-experiments/sapper/dev/server/server.js:2691:46
at Object.$$render (/home/web/svelte-sapper-experiments/sapper/dev/server/server.js:309:22)
at /home/web/svelte-sapper-experiments/sapper/dev/server/server.js:2727:58
at Object.$$render (/home/web/svelte-sapper-experiments/sapper/dev/server/server.js:309:22)
at /home/web/svelte-sapper-experiments/sapper/dev/server/server.js:2979:40

Also some times when i navigate to another route I still see the contents of this Animation page and I usually need to refresh the page and navigate back and forth before this page runs again.
I have seen https://github.com/sveltejs/sapper/issues/774 that might help.

@GiorgosK Thanks for opening the issue, I think I fixed it, just a miss-configuration. Please tell me if its now working for you :smile:
PS: Sorry for replying so late, I messed up with my github notifications

@shiryel no problem, now it works great

Sorry it seems to still be there when making any change to a .svelte that includes saos and than sapper dev rebuilds and refreshes the browser

 is not a valid SSR component. You may need to review your build config to ensure that dependencies are compiled, rather than imported as pre-compiled modules
Error:  is not a valid SSR component. You may need to review your build config to ensure that dependencies are compiled, rather than imported as pre-compiled modules
at validate_component (/home/web/svelte-sapper-experiments/node_modules/svelte/internal/index.mjs:1342:18)
at /home/web/svelte-sapper-experiments/sapper/dev/server/server.js:2465:48
at Object.$$render (/home/web/svelte-sapper-experiments/node_modules/svelte/internal/index.mjs:1365:23)
at Object.default (/home/web/svelte-sapper-experiments/src/node_modules/@sapper/internal/App.svelte:24:50)
at Object.default (/home/web/svelte-sapper-experiments/sapper/dev/server/server.js:3068:85)
at /home/web/svelte-sapper-experiments/sapper/dev/server/server.js:3029:46
at Object.$$render (/home/web/svelte-sapper-experiments/node_modules/svelte/internal/index.mjs:1365:23)
at /home/web/svelte-sapper-experiments/src/routes/_layout.svelte:33:26
at Object.$$render (/home/web/svelte-sapper-experiments/node_modules/svelte/internal/index.mjs:1365:23)
at /home/web/svelte-sapper-experiments/src/node_modules/@sapper/internal/App.svelte:20:18

@GiorgosK I don't know if I'm missing some configuration to make the sapper SSR work, but installing as a dev dependency solves this problem for me

I noticed that in some other packages, when they have this problem and can't be used as a dev dependency, they make the import like this: import Saos from 'saos/src/Saos.svelte'; and that worked for me too

@shiryel yes adding saos as dev dependency solves the previous mentioned problems
thanks


Create example for IBM Graph service integration

This is a placeholder task for creating an example integration with CDS Graph.  Some approaches were discussed offline at a high level with @ukmadlz
If you want to contribute towards this - please add a comment.

I might be interested. What approaches did you talk about?

@KimStebel - as a starting point create a java application that can perform one-off exports of some data on the cluster (e.g. hdfs) into graph.

@KimStebel - still interested? :)

Importing larger datasets into graph isn't trivial at the moment, so that would actually be a good example. I'm afraid we wouldn't be able to use the bulk import endpoint and would instead have to use gremlin queries. I can certainly help with that, but I'm not sure how much time I'll have.

@KimStebel - we don't have any specific time pressures on this.  Any help you can give will be appreciated.  Let me know if you need access to a cluster to develop this.

Yes, I would indeed need access to a cluster. Also, what about getting data out of graph? I'm still a bit confused whether Graph will be positioned more towards the OLAP or the OLTP side of things, but query times limited to 60 seconds suggest OLTP. So getting data out of graph and into something that does longer running processing jobs (spark, hadoop) seems important, too.


project velocity discussion

This notebook sets up everything to be able to discuss the specifics for the project velocity visualization

@cdolfi
So, I found where the definition has been applied in the CNCF's work:
https://github.com/cncf/velocity
I also found the source article where this is talked about:
https://www.cncf.io/blog/2017/06/05/30-highest-velocity-open-source-projects/
Both sources are in the CHAOSS definition page:
https://chaoss.community/kb/metric-project-velocity/
The x and y axes are 'log # commits' and 'log (# prs + # issues)' I think, in the CNCF script. They appear to make no distinction between open, closed, merged, (etc.) PRs and Issues.
The data they get from BigQuery isn't very discerning.
e.g.
org,repo,activity,comments,prs,commits,issues,authors kubernetes,kubernetes/kubernetes,11243,9878,720,70,575,40 ethereum,ethereum/go-ethereum,10701,570,109,43,9979,14 ...
The script that the analysis is done in isn't commented much, and is in Ruby, so I'm not entirely sure if they may any distinction.
That being said, reading the CHAOSS definition, Velocity seems to want to capture a snapshot of the state of projects at time 'T' with the motivation being, quote Dan Kohn:
"...most developers are interested in using and participating in the largest projects, and the projects with the most developers are more likely to quickly fix bugs, add features and work reliably across the largest number of platforms."
My reading of the spirit of the definition is that, at time T, the number of pull requests made (opened + merged + closed_unmerged) and issues made (open + close) is most appropriate. If the assumption of the Velocity paradigm is that larger, more active projects are more likely to experience increasing returns of scale (more people are going to want to join highly active projects) then these all-including axes make the most sense to me.
An extension of this thinking is to use time-window based analysis in a future iteration which will allow us to discount earlier activity if a project at time T is much less active than at time 't', thereby the volume of time 't' doesn't overrepresent the current activity.
Velocity seems pretty reasonable in that respect- PRs are made, merged, closed, etc. and it's all signal implying activity and engagement. Those projects that do dramatically more "engagement" stuff will have higher churn or direct net-new development that (to my intuition) are more likely to attract new people, meriting inspection.

@JamesKunstle For me "pull requests or issue made" would be just opening a pull request or issue. Merged or Closed are actions done on said pull request. With that, I am more concerned with this visualization being the most informative than it following any specific definition elsewhere. With that ill apply adding all of those together and see what the results are like

@cdolfi
I don't think I was specific enough in my description of a definition: each count would just be concerning the existence of a pull request that was made. This includes PRs that are in any state at time 'T', including "currently open", "has been merged", and "has been closed without merging". Which is equal to the total number of pull requests ever opened. Same for issues.

@JamesKunstle Ah I see what you are saying. After thinking about the "...most developers are interested in using and participating in the largest projects..." quote I actually could see some potential value in including all of those actions as it does represent a trend towards overall progression of bugs fixed, features implemented all the way through. I have some ideas. I am going to implement a few different interpretations on this and push those updates so we can check them out. Really liking this process of collaboration on a more complicated visualization, the time to go into implementing different strategies is actually super quick

@JamesKunstle Quick follow up: Do you have anything specific on the x axis I should try besides log of commits? Everything I am thinking of/ weve been discussing (I believe) has been about the y axis

New strategies implemented, very curious to hear peoples thoughts on them or others to try

@JamesKunstle Quick follow up: Do you have anything specific on the x axis I should try besides log of commits? Everything I am thinking of/ weve been discussing (I believe) has been about the y axis

I totally missed this message. TBH x-axis of log(#commits) seems reasonable. Even if projects have relatively different commit practices I think, on average, it's a reasonable proxy for net growth, though it's certainly not perfect.

So I actually do not view this as a double count, I view this as counting something completely different. this is inspired by the quote  "...most developers are interested in using and participating in the largest projects, and the projects with the most developers are more likely to quickly fix bugs, add features and work reliably across the largest number of platforms." This is looking at all of the actions around prs and issues. I feel like there is a difference between the existence of a pr and issue, and the full development cycle around them (opening, commenting, closing/merging). The question is that does this provide a better view into "project velocity" or the 1 dimensional view is better.  Note: The merged vs closed problem is handled in the actions query. There is no double count for merged PRs

View entire conversation on ReviewNB

Yeah in talks with sean on this. There is some augur bug happening here

View entire conversation on ReviewNB

Wait actually realized I thought you were responding to something else. Not sure what you mean by a "Double count" here. This doesnt take into account "at time t", this is just counting the number of each action through all time. So the goals of these values are not to get the number of open issues, prs, etc at a specific time T, but to count the actions themselves

View entire conversation on ReviewNB

I like this idea of having a toggle on the view

View entire conversation on ReviewNB

The merged vs closed problem is handled in the actions query. There is no double count for merged PRs

View entire conversation on ReviewNB

What is LoC?

View entire conversation on ReviewNB

@JamesKunstle This is the summery I am getting from your comments, let me know if a missing or misinterpreting anything:
x axis: log(commits)
y axis: PR and issue Actions (open closed merged) with user inputed weights and the ability to toggle between log or not
let me know and ill start building the viz!

++ nice

View entire conversation on ReviewNB

Ah awesome, that's super nice.

View entire conversation on ReviewNB

Lines of Code. Since commits are only representative of a change occurring, and not how large of a change, LoC could be a useful toggle-able perspective.

View entire conversation on ReviewNB

Ah makes sense. That would involve integrating another query into this visualization, which im not against. Im going to do the first time pass at the viz with just commits and we can see if we want to add another user input. RN its up to 6 which is twice as much as any of our other ones so I want to see how overwhelming it is or isnt

View entire conversation on ReviewNB

++ sounds great. We'll probably have to go through an iteration of query optimization as well- the materialized view query took a while when I ran this notebook locally. Pre-aggregating in SQL is probably faster, and if it's not fast enough, we can do separate queries on the respective tables.

View entire conversation on ReviewNB

@cdolfi Yes, that sounds exactly right. Very very excited for this.

The query throughput time might be fast (how long it takes for the database to receive a request, prepare a response, and begin sending the response) but, at least in the example in the beginning of the notebook, there are still 1.6 million rows that need to travel over the wire. If they can pre-aggregate the statistics that we need based on this table, and we just have to request the view of it, that'd be sick. Not sure how much that'd take to do.

View entire conversation on ReviewNB

As we use this query more there might be a few preprocessing steps that are consistent for a few of the vizs and we make them into their own queries based on the materialized view. Lets come back to this idea (if nothing more comes from the josh/sean convo) after we have a few more vizes in that use it and see if there is some consistencies that come up

View entire conversation on ReviewNB

@JamesKunstle updates in, from my side ready to merge


Add support for Multiselect field type in system configuration

Is your feature request related to a problem? Please describe.
The current system configuration options in Bagisto are limited to basic field types such as text, textarea, number, select and boolean. This restriction makes it challenging to provide users with the flexibility they need to select multiple options for various settings. For instance, when configuring payment methods, user roles, or feature toggles, there is often a requirement to allow for multiple selections, which is not possible currently.
Describe the solution you'd like
I would like to propose the addition of a multiselect field type for configuration settings in Bagisto. This new field type should allow administrators to select multiple options from a dynamically generated list. The multiselect field should have a user-friendly interface and function similarly to the existing select field but support multiple selections.
Describe alternatives you've considered
No response
Additional context

Use CTRL + click.

Use CTRL + click.

Did you test it before answering?
In my case it only accepts one value not 2
Check video for reference
https://github.com/user-attachments/assets/e16db42a-bd53-4d02-9e69-ba94793f1529

Hello @ghermans,
Here are the steps, i tested on the dashboard page,
<x-admin::form.control-group.control
        type="multiselect"
        name="swatch_type"
>
        @foreach (['dropdown', 'color', 'image', 'text'] as $type)
            <option value="{{ $type }}">
                @lang('admin::app.catalog.attributes.create.option.' . $type)
            </option>
        @endforeach
</x-admin::form.control-group.control>

Then you can check on the page,
https://github.com/user-attachments/assets/78e43691-6e1c-41b1-9386-e32f92392d49
If you need any more information, feel free to ask me. I will help you :innocent:
Thanks!

@devansh-webkul please try the following
config/system.php
<?php

return [
    [
        'key'    => 'sales.carriers.myparcel',
        'name'   => 'myparcel::app.myparcel',
        'info'   => 'myparcel::app.admin.system.info',
        'sort'   => 3,
        'fields' => [
            [
                'name'          => 'apiKey',
                'title'         => 'myparcel::app.admin.system.api_key',
                'info'          => 'myparcel::app.admin.system.api_key_info',
                'type'          => 'password',
                'validation'    => 'required',
                'channel_based' => true,
                'locale_based'  => false,
            ], [
                'name'          => 'active',
                'title'         => 'myparcel::app.admin.system.status',
                'type'          => 'boolean',
                'channel_based' => true,
                'locale_based'  => false,
            ], [
                'name'          => 'something',
                'title'         => 'Testing',
                'type'          => 'multiselect',
                'options' => [
                    [
                        'title' => 'option_1',
                        'value' => 'value_1',
                    ], [
                        'title' => 'option_2',
                        'value' => 'vallue_2',
                    ],[
                        'title' => 'option_3',
                        'value' => 'vallue_3',
                    ],

                ],
                'depends'       => 'active:1',
                'channel_based' => true,
                'locale_based'  => false,
            ]
        ],
    ],
];

i'm unable to select more then one option
https://github.com/user-attachments/assets/3dc40bd6-f32f-480e-a719-cb8cbf54a946

As from the video its look like there may be a bug.

@amit-webkul,
Please look into this.

@ghermans
We have checked and verified the details and now the multiselect issue has been fixed.
Video
https://github.com/user-attachments/assets/96d8cf38-5473-4e74-bdee-b2ed764e6e2e


python3Packages.zeroconf: 0.35.1 -> 0.36.0

Motivation for this change
Update to latest upstream release 0.36.0
Change log: https://github.com/jstasiak/python-zeroconf/releases/tag/0.36.0
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 packages 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/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

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

1 package failed to build:

octoprint

43 packages built:

calibre
catt
cinnamon.warpinator
cura
curaLulzbot
dpt-rp1-py
esphome
expliot
gnomecast
home-assistant
home-assistant-cli
mkchromecast
platformio
python38Packages.HAP-python (python38Packages.hap-python)
python38Packages.PyChromecast
python38Packages.aioesphomeapi
python38Packages.aiohomekit
python38Packages.boschshcpy
python38Packages.devolo-home-control-api
python38Packages.libpurecool
python38Packages.libsoundtouch
python38Packages.netdisco
python38Packages.openwebifpy
python38Packages.pyatv
python38Packages.python-miio
python38Packages.pyvizio
python38Packages.webthing
python38Packages.zeroconf
python39Packages.HAP-python (python39Packages.hap-python)
python39Packages.PyChromecast
python39Packages.aioesphomeapi
python39Packages.aiohomekit
python39Packages.boschshcpy
python39Packages.devolo-home-control-api
python39Packages.libpurecool
python39Packages.libsoundtouch
python39Packages.netdisco
python39Packages.openwebifpy
python39Packages.pyatv
python39Packages.python-miio
python39Packages.pyvizio
python39Packages.webthing
python39Packages.zeroconf


[examples] Use typography v2 until release

This reverts everything under examples/ in commit 2be2826c70ba30762c8096a3e0971e334eb049fc.


Install a vim extension

JavaScript and TypeScript extensions

https://github.com/pangloss/vim-javascript
https://github.com/neoclide/coc.nvim/wiki/Install-coc.nvim


Missing DELETE /ddosx/v1/domains/{name}records/{id}

The CLI tool is missing the command ukfast ddosx domain record delete.
The endpoint which it needs to hit is DELETE /ddosx/v1/domains/{name}records/{id} with no parameters and it should expect a response code of 204 on a successful deletion.
The documentation for this endpoint is at https://developers.ukfast.io/documentation/ddosx#/Record/delete_ddosx_v1_domains__name__records__id_

This command already exists:
ukfast safedns zone record delete --help
This command removes one or more zone records

Usage:
  ukfast safedns zone record delete <zone: name> <record: id>... [flags]

Are you mistaking this with a different command?


Opening multiple serial ports

I want to use 3 TI mmWave radar's simultaneously on an Ubuntu system using ROS. Everytime I launch the second radar, the first one dies giving this message-
[ INFO] [1533763639.507378042]: mmWaveCommSrv: Sending command to sensor: 'sensorStop'
[ INFO] [1533763639.573949686]: mmWaveCommSrv: Received response from sensor: 'sensorStop
Done
mmwDemo:/>'
Is the sensorStop command something this serial package is giving?

No, this package doesn't depend on ROS, so any ROS node related stuff is specific to something other than this library. This library only opens/closes serial ports and sends arbitrary data to/from it with read/write. It has no support for specific devices or command sets.


Live Interactive Audio Streaming supported?

My question is whether this SDK supports the Agora Product "Live Interactive Audio Streaming", or just the regular "Voice Call" product.
If so, how do I use this SDK to use the interactive product?

https://github.com/AgoraIO/agora-react-native-rtm

@fritzfr the SDK contains all of the products about video and audio.


update IKS version

update the IKS version on the installing kubeflow page to v1.7.0

/cc @Tomcli

/cc @RFMVasconcelos @8bitmp3

tag owners again
/cc @RFMVasconcelos @8bitmp3

@yhwang thanks for this update.   do the links to the IKS website, etc work ?   I got a 404 on one of them.

@jbottum
there are two links and both work for me:

https://ibm.github.io/manifests/
https://github.com/IBM/manifests/releases/tag/v1.7.0

/lgtm
/approve


Added missing 'sendLater' method

Proposed changes
@thetutlage proposed me to make this PR w/ the changes. Full discussion can be found here.
Types of changes

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[x] I have read the CONTRIBUTING doc
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have added necessary documentation (if appropriate)

Further comments
I'm not sure, I'm still in learning phase of writing type definitions for TypeScript projects. I hope I made the correct fix. :)

Hey @msrumon It's only the typing is missing. The sendLater method also needs to be implemented on MailManager, along with some tests :)

Oh I see. That's why the tests have failed, right?

Thanks for the fix. The doc says sendLater method pushes the emails to in-memory queue, but doesn't tell anything about how to push them to separate queue server. Can you add that as an example to the doc please? Or at least describe here?


feat: more retrieval metrics

Checklist

[x] I have read the coding guide.
[ ] My change requires a documentation update, and I have done it.
[ ] I have added tests to cover my changes.
[ ] I have filled out the description and linked the related issues.

Description
Adding metrics as part of  #3876.

there some existing metrics already, can we cleanup and use only the ones we need.

there some existing metrics already, can we cleanup and use only the ones we need.

how should we know which metrics are not needed?

When you are also fixing the dashboards, the decision is yours to keep and discard the metrics you need :)


Maybe some possible questions in your  Cpp-Primer/ch02

1.exercise 2.5   lose answer of (d)
2.exercise 2.6   your answer is “The first line's integer is decimal, the second line's integer is octal.”,    but I think second line’s first integer isn’t octal . 9 doesn’t appear in Octal like that A doesn’t appear in decimal.
3.exercise 2.27   your answer think  that  “int *const p2 = &i2” is legal,
But if i2 is a variable of double type ,what’s the answer ?so it’s not strict .
So (d),(f) have same questions ,we don’t know i2 what type it is .

exercise 2.31	r1 = v2 is illegal.                                    Error message : invalid initialization of reference of type 'int&' from expression of type 'const int'

My English level is very poor , so can you understand what I want to express?thanks!

Hi, @cxs944745612 Good to see you. :smile:
1 and 2, you are right, and I have tried to fix it.

int *const p2 = &i2, we can judge the variable type according by it's name. Or, the question make no sense. Thus, i2 should be an integer, rather than double as you say.

I can't sure whether it will appear this error message. I am try to list the related codes as following:

const int v2 = 0;
int v1 = v2;
int &r1 = v1;
// above is previous exercise (Exercise 2.30)
r1 = v2;

Use Clang 3.5 and gcc 4.9.2, All passed. Could you please tell me what environment do you have?
Thx a lot for bug reporting. :+1:

I'm very sorry ,it's my fault .You're right!
what's more,you say"we can judge the variable type according by it's name",it means that we keep i2 as a default  integer variable .(  i: integer, d: double, f: float)
My English level is very poor , so can you understand what I want to express? I really want to say Chinese ! thanks a lot for your guidance！

我觉着你们俩可以用中文讨论来着：）

@cxs944745612 @jjjasperd
那咱们以后就用中文吧～ :cn:

i: integer, d: double, f: float. so d2 is a double variable in c++ primer ? like this？

是的，就是这样，这本书的命名很讲究，也为初学者培养好不乱命名的好习惯。除了你提到的，第二章里，还有 r 代表 reference, c 代表 const, p 代表 pointer.

好的，非常感谢！我有些新的问题请教您，我又提了两个问题在知乎上邀请您回答了，如果有时间的话，麻烦您了。

@cxs944745612 真的抱歉，周末有些事耽搁了，明天我帮你看看～ :horse_racing:

没事没事，您有时间就看，非常感谢您的无私帮助！


Add support for JUnit Pioneer's @CartesianTest

JUnit Pioneer is an extension of JUnit 5 and has a @CartesianTest annotation that allows for multiple parameters (instead of a single parameter in the traditional @ParameterizedTest.)
This PR adds support for that new annotation.
Ref: https://junit-pioneer.org/docs/cartesian-product/

Didn't notice it changed formatting. I pushed again w/ only the annotation added

Interesting annotation :eyes:


Unary bitwise complement "~" in dart2js is wrong

for example,
var i = 0;
print(~i);

It should print -1 not<PHONE_NUMBER>
Dart2js will compile it to
~i >>> 0
Not ~i only

dart2js and DDC chose to restrict bit operations to the range [0, 2^32).
The other choice was [-2^31, 2^32).
The unsigned range makes more code 'just work'.
See: https://github.com/dart-lang/sdk/issues/25493


Added Markov Switching Multifractal simulation

I added a module that runs a Binomial Markov Switching Multifractal simulation, as introduced by Calvet and Fisher in this 2002 paper https://core.ac.uk/download/pdf/162459682.pdf
I think there might be a couple of mistakes and/or improvements to be made, so please review this, but I thought it would be a good addition to this package.
I wasn't exactly sure how to get it to adhere to the same interface as the BrownianMotion.simulate() method, as this seems to return some kind of distorted time along with the Brownian motion itself. Maybe you can explain further.
In the future it might be interesting to develop modules to infer MSM model parameters from data, which is a can of worms... But for the time being, a simulation from hardcoded parameters is nice.
If you run the markov_switching_multifractal.py as main you can quickly demo the code.

@xavierdcruz0 Thank you for your contribution! After a quick review, we will merge your code.
You are right that the BrownianMotion.simulate() method returns a distorted time such that the step increments are not equivalent. This is a product of constructing the time series with a fractal generator that has two turning points. The time coordinates of this generator are adjusted based off of a random measure. See this Medium article for more detail.
In the examples section, you will see that interpolation of the time series that BrownianMotion.simulate() produces is required to produce equal time steps.

@xavierdcruz0 Once again, fantastic work on this. Your contribution is really appreciated!
I have one request before I merge your code. With respect to the simulate method, you have the ideal output as compared to the BrownianMotion simulate method, since your time increments are equivalent. The method, however, should return the price series in the form of a 2D array [[x,y]...]. I see that you have a helper method to get this price series named returns_to_prices. Please do the following before the merge.
Adjust the code to comply to the proper simulate method. You will have to move the timesteps parameter to the __init__ method.
def simulate(self):
    ...
    return prices # where prices is a 2D array [[x, y]...] where x is the time coordinate and y is the price. (your x will be equally spaced)

Feel free, of course, to keep a method that calculates the returns series from the price series.

Hi, thanks for getting back to me. I made the changes to add the time array, so it fits the existing interface:

I just wanted to get your opinion on one design choice:
When converting the returns generated by MSM into absolute price values, I chose a starting price arbitrarily of 1.0. https://github.com/xavierdcruz0/fractal-market-analysis/blob/master/fractalmarkets/msm/markov_switching_multifractal.py#L101
I don't know how exactly this impacts the scale of the resulting values, as I noticed that the existing Brownian Motion is (mostly) confined to the unit interval (owing to the interesting way it is constructed recursively from that lightning-bolt shape).
Just have a look and let me know if it's consistent with the rest of the simulations in the package.
I am excited by this repo, I hope we can make it a one-stop-shop for everything multifractal in python time-series analysis! Perhaps writing code to estimate multifractal model parameters from data would be a good direction to go?

@xavierdcruz0,
@dluftspring and I discussed the consequences of starting the price arbitrarily at 1.0 and concluded that there weren't any.
With respect to the following question:

Perhaps writing code to estimate multifractal model parameters from data would be a good direction to go?

This is exactly the right direction to take the project and all suggestions are welcome here. Please see issue #27 for a starting point.


Stratux does not show up on iPad Foreflight but works fine on iPhone

Stratux version: v1.6r1

Stratux config:
SDR

[ ] single
[X] dual

GPS

[X] yes
[ ] no
type:

AHRS

[X] yes
[ ] no

power source: external battery bank
usb cable: known good 6” USBA-Micro USB

EFB app and version: Foreflight 12.9.2
EFB platform: iPadOS 14.2 / iOS 14.3 Public Beta
EFB hardware: iPad Pro 11”, WiFi-only / iPhone 12 Pro Max

Description of your issue:

Just got a Flightbox, trying to get it to work with Foreflight. It connects to Foreflight on my iPhone just fine, but it does not show up at all on Foreflight on my iPad. Have tried disabling AHRS, reflashing the card, closing all apps on my iPad, and hard rebooting my iPad. Any solution?
Logs coming momentarily

stratux.log


Add more docs

Also- figured out the Doxygen mainpage stuff:
diff --git a/src/circllhist.h b/src/circllhist.h
index 304cb5f..6ddb015 100644
--- a/src/circllhist.h
+++ b/src/circllhist.h
@@ -29,6 +29,10 @@
  * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  */

+/*! \mainpage A C implementation of Circonus log-linear histograms
+ * \ref circllhist.h
+ */
+
 #ifndef CIRCLLHIST_H
 #define CIRCLLHIST_H

The comments in circllhist.c are just internal notes. No API documentation. So this is fine.

All fixed. LGTM.


[BUG] page update failed when document related files changed

If document/index.js use document/Header.js, when Header code updated, html should update to latest.

This bug can not be resolved in HMR, recommend to refresh page.
Modifying the document is a very low frequency requirement, under normal circumstances, there will be no subsequent modification requirements after the initial modification, so we consider not to realize this ability


[App]: Duplicate Runs in the Sweep with Parallel Agents

Current Behavior
When I use wandb.agent to sweep different hyperparameters, I notice that there are a significant number of runs with identical hyperparameters. This results in a considerable waste of computing resources.
The main part of my running script is as follows:
import argparse
import os
from pprint import pprint
import wandb

parser = argparse.ArgumentParser()

parser.add_argument('--wd', type=float, default=1e-2)
parser.add_argument('--batch_gap_to_rebuild_tree', type=int, default=80000)
parser.add_argument('--sample_num', type=int, default=70)
parser.add_argument('--emb_dim', type=int, default=24)
parser.add_argument('--scheduler_mode', type=str, default='exponential', choices=['polynomial', 'exponential', 'cosine'])
parser.add_argument('--lr', type=float, default=1e-3)
parser.add_argument('--min_lr', type=float, default=1e-6)
parser.add_argument('--dropout_p', type=float, default=0.0)
parser.add_argument('--gpu_id', type=int, default=0)
parser.add_argument('--sweep_id', type=str, required=True)
parser.add_argument('--project_name', type=str, required=True)
parser.add_argument('--sweep_count', type=int, default=5, required=True)
parser.add_argument('--dataset', type=str, choices=['mind', 'movie', 'tmall', 'amazon'], required=True, help='dataset')

args = parser.parse_args()

dir_path = './sweep_log_{}'.format(args.dataset)
os.makedirs(dir_path, exist_ok=True)

def train(config=None):
    with wandb.init(config=config, dir=dir_path, group=args.dataset, settings=wandb.Settings(init_timeout=300)):
        # Replace the attributes in args with the attributes in config
        print('Arguments passed:')
        pprint(vars(args))
        for key, val in wandb.config.items():
            if key in vars(args):
                setattr(args, key, val)
            else:
                print('Warning: {} is not in the arguments'.format(key))
        print('After replaced with config:')
        pprint(vars(args))

wandb.agent(args.sweep_id, train, count=args.sweep_count, project=args.project_name)

The shell script is as follows:
(
    python sweep_one_epoch.py --dataset mind --sweep_id gi5t62yt --project_name mind_deforec_sweep --sweep_count 5 --gpu_id 1
)&
(
    python sweep_one_epoch.py --dataset mind --sweep_id gi5t62yt --project_name mind_deforec_sweep --sweep_count 5 --gpu_id 2
)&
(
    python sweep_one_epoch.py --dataset mind --sweep_id gi5t62yt --project_name mind_deforec_sweep --sweep_count 20 --gpu_id 5
)&
wait

Expected Behavior
No response
Steps To Reproduce
No response
Screenshots

I have observed that these two runs have the same hyperparameters. Additionally, they both share the same gpu_id, indicating that they are executed by the same agent. Therefore, it appears that the issue is not related to the use of multiple agents.
Environment
OS: Linux ubuntu 5.4.0-126-generic
Browsers: Edge 125.0.2535.79
Version: wandb 0.16.0
Additional Context
I would like to understand the cause of this problem as soon as possible. Thanks!

Thanks @marsh312! I did some tests on my end but was unable to reproduce the issue. Would you mind sharing if you're using Hydra? We have seen this issue happening when using it so wanted to double-check

Thanks @marsh312! I did some tests on my end but was unable to reproduce the issue. Would you mind sharing if you're using Hydra? We have seen this issue happening when using it so wanted to double-check

Of course, @luisbergua! I am using a shell script to run the sweep, not Hydra. The script is listed above.

Thanks @marsh312! I haven't been able to repro this issue yet so wanted to ask if you could try to avoid passing --gpu_id and only execute the command once. I know you mentioned that repeating runs have the same --gpu_id and agree that this doesn't seem to be associated with the use of multiple GPUs but would like to double-check. Also sharing our docs about sweeps on launch since those could be helpful for running sweeps in distributed environments

Sorry, @luisbergua! Due to resource limitations, I was only able to conduct some experiments based on your instructions and haven't witnessed the same issue again. Here is my hypothesis regarding the issue: because the sweep space I set is small and discrete, using the Bayesian sweep method might lead to duplicate runs. Do you think this hypothesis is reasonable?

I'm experiencing the same issue with grid-based search. In my case I set up a hyperparameter search that's supposed to execute 24 runs, and I launched 4 agents to execute in parallel. But the search never stops and in the end I got over 1k runs... and still not stopping. Eventually had to kill the process in order to stop the sweep.


Background blur when tooltip open

When open a tooltip for touring, then need blur background without tooltip and the highlighted area.

Is any solution for it

I haven't find a way to make it blurry, but you can add the following CSS-rule to give it a more "highlighted"-look.
.v-tour__target--highlighted {
    box-shadow: 0 0 0 9999px rgba(0,0,0,.5);
}

any way to make the whole page with some background when tour guide is active???

any way to make the whole page with some background when tour guide is active???

https://github.com/coodde/vue3-tour


Fix a typo in C# bindings generator for default value types

I accidentally broke this in #45424, position instead of size, likely a copy-paste problem. This PR fixes it.
In the current master, all default values for size are zero (and all default values for position are zero), so this PR doesn't actually change behavior anywhere. It is technically only a bug fix in that this buggy code could break some future code.

Thanks!


New package: LMGPU v0.1.2

Registering package: LMGPU
Repository: https://github.com/ChelseaTrotter/LMGPU.jl
Created by: @ChelseaTrotter
Version: v0.1.2
Commit: 166dcaf5092040faa6a6dc97cef9d627bba5d17a
Git reference: master

Please close this issue. This package is renamed according to guideline.


Fixes on ChatHandler and Flashlight sync

Made ChatHandler  its own gameobject that will get automatically destroyed on scene loads
Fixed issue that would make the remote animations break when using the flashlight without having put the suit on for the first time
Made some research for syncing rafts

Make sure that the changes don't immediately break anything


[Feature] Add target_path to global_flags

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
From @graciegoheen here:

Like looking at this page for target-path, I don't see anything for dbt retry - is that expected @ChenyuLInx ?

This is explained<EMAIL_ADDRESS>not being included within the flags for dbt retry.
The easiest way to "solve" this would be adding @p.target_path to the dbt retry command here.
But the proposed way to implement this would be to add it to the global_flags and remove it from each of the sub-commands.
Current status
Currently, @p.target_path is included for all sub-commands except for:

dbt debug
dbt deps
dbt retry

Describe alternatives you've considered
A couple alternatives:

don't add target_path to any more sub-commands (which is the status quo)
add target_path only to dbt retry, but not dbt debug or dbt deps

Who will this benefit?
If dbt retry produces any artifacts to the target directory, then this flag would make that location configurable.
Are you interested in contributing this feature?
No response
Anything else?
No response

[!TIP]
All the << EOF business below is the start of a "here document" -- just a handy way to write dbt model files on the fly for reprex purposes.

dbt retry
Since dbt retry writes files to the target_path directory, it should be configurable via DBT_TARGET_PATH or --target-path just like nearly all other dbt sub-commands.
Acceptance criteria 1
Users should be able to set the DBT_TARGET_PATH environment variable and have it work with subsequent retries:
export DBT_TARGET_PATH=artifacts
cat << EOF > models/my_model.sql
select 1/0 as id
EOF
dbt run -s my_model
cat << EOF > models/my_model.sql
select 1 as id
EOF
dbt retry

Instead, they will get this error:
01:10:28  Encountered an error:
Runtime Error
  Could not find previous run in 'target' target directory

Acceptance criteria 2
Put another way...
Suppose you start with some bad SQL, run it, and then fix it:
dbt clean
rm -rf target
rm -rf artifacts
cat << EOF > models/my_model.sql
select 1/0 as id
EOF
dbt run -s my_model --target-path target
mkdir -p artifacts
mv target/run_results.json artifacts/
rm -rf target
cat << EOF > models/my_model.sql
select 1 as id
EOF

This command works, and it writes output files to the target directory:
dbt retry --state artifacts

We should make it so this command writes output files into the my_target_path directory:
dbt retry --state artifacts --target-path my_target_path

Something to consider
As shown in the logic here:

dbt retry will use the configured state directory to find run_results.json.
Otherwise, it will fall back to the configured target_path directory.

When these are the same directory, then the newest run_results.json file will overwrite the pre-existing one.
Maybe this is partially why there was the following warning message in 1.7.4 and earlier? Or maybe that warning was there for different reasons?
Warning: The state and target directories are the same: 'target'. This could lead to missing changes due to overwritten state including non-idempotent retries.

This warning was added in https://github.com/dbt-labs/dbt-core/pull/8638. Then the warning disappeared following https://github.com/dbt-labs/dbt-core/pull/9328 (which resolved https://github.com/dbt-labs/dbt-core/issues/9327).
Separate acceptance criteria
In the case of successive executions of dbt retry, we should make sure that it is okay that run_results.json is overwritten.
We should probably move this separate acceptance criteria to its own issue, but leaving it here for sake of expedience.
See below for an example of successive executions of dbt retry. I'm not sure or if it is a sufficient example to show that it's okay for run_results.json to be overwritten each time.
cat << EOF > models/my_model.sql
select 1/0 as id
EOF
dbt run -s my_model
dbt retry
cat << EOF > models/my_model.sql
select 1 as id
EOF
dbt retry

Decision
@aranke and I discussed this over a video call today and decided to add this to the global_flags and remove it from each of the sub-commands.
Here are the reasons:

there are very few commands that wouldn't want to write to the target-path directory (which is target by default)
if we add any dbt commands in the future, they will automatically get the target-path configuration for free
any commands that don't write to the target-path directory will just ignore that value


Add drought tolerant and CA native status

Incorporate drought tolerant and CA native data:  https://docs.google.com/spreadsheets/d/1s8GtXKEdwAt4b4bxgf3uJJ4E3mC7PW5CnBU88yKW6F4/edit#gid=0

And other fun facts that Seiji has in the additional columns

The current information I have is from the old tree walk PDFs. We need to figure out how to integrate that exactly. Anything is possible. Just like in the CSV referenced I suggest to separate semantic information (like boolean is it drought tolerant yes/no and boolean is it native yes/no information) into fields. This way we can use them for coloring, or displaying that specific info in a structured format, like I have the latin name, height, width and some more information separately from the free form text description. The more info we have that way the more we can do later, for example filtering the stops by some criteria. The same information can be in the free text as well though, so we don't necessarily have to strip it, it's up to us.

Instead of California native status we add native region. We also add climate action, poluution, traffic meta data.


let provide to be one member of image

content.Provider, which is mainly reading io stream, is a strong and
inside dependency field to container images, as struct image.Image. So
move this to Image member. It can bring benefit to reduce argument,
and show the relationship. As well, it may easy the possible refactor on this.
Signed-off-by: xiekeyang<EMAIL_ADDRESS>

Codecov Report

Merging #717 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #717   +/-   ##
=======================================
  Coverage   62.46%   62.46%
=======================================
  Files           5        5
  Lines         682      682
=======================================
  Hits          426      426
  Misses        160      160
  Partials       96       96

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 6291851...78abb85. Read the comment docs.

The image is a shallow data type and should not be coupled with the provider.


Getting log output from failing build

We are trying to fix the broken build. This PR is only to get more information about why the build is failing. We do not intend to merge this.

It passed three times in a row! We fixed Travis!

This was landed via https://github.com/facebook/react-native/commit/1d30ace94ac8b00d571f6dc37e0c20be46c67c87.
Builds pass now.


Fix Integration Tests - WIP

Description
This PR fixes integration tests by fixing parcel builds and fixing the failing integration tests.
Related Issue
Closes https://github.com/adobe/reactor-sdk-javascript/issues/72
Motivation and Context
Makes our overall testing more reliable.
How Has This Been Tested?
Integration tests run now
Screenshots (if appropriate):
Types of changes

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[X] I have signed the Adobe Open Source CLA.
[X] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[X] All new and existing tests passed.

This isn't quite ready yet. Sorry for requesting reviews early.


Support custom k8s-app label on cluster service installation

Hi there! 👋
TL;DR:
I would like to override the k8s-app label to kube-dns rather than coredns when installing this Chart in cluster service mode (isClusterService enabled). However, actually there is no way to change that since it's pointing to the Chart name - as shown below.
https://github.com/coredns/helm/blob/c4e1c9936688c6257993c2d3c4472b2ffebf75b4/stable/coredns/templates/deployment.yaml#L10
https://github.com/coredns/helm/blob/c4e1c9936688c6257993c2d3c4472b2ffebf75b4/stable/coredns/templates/service.yaml#L24
Context:
I've used kOps to configure and launch my Kubernetes clusters so far. When provisioning the cluster, kOps determines the cluster DNS IP address (e.g. based on pod's overlay network) and handover it to nodes (over the --cluster-dns parameter on kubelet) and it creates a kube-dns Service in the cluster with a fixed clusterIP address as well.
Now, I would like to use the official CoreDNS Helm Chart and replace the KubeDNS one. However, I want to do this by preserving the old kube-dns Service to be able to avoid any outage on apps (regarding DNS resolutions, for sure 🙈). Since the selector is an immutable field in the Service spec, I can't change it to accord with the CoreDNS one (k8s-app==coredns). So, I would like to be able to override the k8s-app label. 😬

When is this going to be merged?? And what are you doing for the time being

You can use (customLabels)[https://github.com/coredns/helm/blob/master/charts/coredns/values.yaml#L222] unfortunately there's a minor bug that will break the pod disruption budget. Personally this helm chart was overcomplicated so I took the existing version and copied it to our local repo to fix the PDB issue I mentioned


Port to cargo_metadata where possible

For determining the default tag, I did not switch us from finding the git root to finding the workspace root.  I figured that if the crate wasn't in the git root, regardless of the use of workspaces, we probably want to scope the tag.

cargo metadata doesn't expose publish, that is weird
cargo_metadata doesn't expose the metadata table.  I understand (its freeform, what API to provide?).

nm, it does support metadata.  Somehow I missed that when going through the docs
https://docs.rs/cargo_metadata/0.7.1/cargo_metadata/struct.Package.html#structfield.metadata

Did a rebase
Fixed an expect failing when run in a workspace root without a package (pure_ws test condition)

Perhaps we can submit an issue for cargo_metadata to support publish?
Just knew about cargo_metadata is a great to for cargo ecosystem, I will close #63 because cargo_metadata is a better approach.

Perhaps we can submit an issue for cargo_metadata to support publish?

iirc cargo metadata (which cargo_metadata wraps) doesn't expose publish, so we'd first need the issue resolved in cargo metadata.
But yes, it'd be nice if they exposed it.


Update cop/watcher vocabulary

Update vocabulary for cluster watchers.   Has a mixup with previous PR, but this should be good to go.   Tested on Red Hat slack channel.

Can one of the admins verify this patch?


Switch use of codecov-action from v1 to v2.

Isn't this a duplicate of #38?

This was a duplicate. You merged the other one so fast I thought I missed it. Sorry.


Add localization support for datepicker component (v5)

Is your feature request related to a problem? Please describe.
The DatePicker component does not have the possibility to have translated buttons and a custom format for the header text.
Current behaviour:

What it should look like (in my case german locale and text):

I forked this repo and created a PR on the latest v5 on my side with the needed changes to accomplish this:
https://github.com/DreadCube/material-table-core/pull/1
Maybe we wanna support that generally for the v5?
On v6 things look a little different because from there on material ui v5 is used with new Date Picker components:

But i guess formatting the placeholder / value to a different locale would make sense there too.
In my case we have to stay still for a while on material-ui v4 with the older DatePicker variant.

Hi, did you try this: https://mui.com/x/react-date-pickers/localization/#set-translations-globally


Error help me please

Problem encountered on https://dotnet.microsoft.com/learn/dotnet/hello-world-tutorial/install
Operating System: macOS M1
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

@Maximeduyne please see https://github.com/dotnet/core/issues/6953
I believe it could be related.

@Maximeduyne what version of the SDK have you installed? For M1, you should install Arm64. If you have installed a different version, please uninstall that and install the Arm64 version.


Valerio and Ceri modified this so that it always requires it be insid…

…e corpus, so needed to update the query to always join on reference and mca

Thanks @sweng66 !


教程-用户指南   中的  请求体-多个参数  章节中代码错误

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
from typing import Union

from fastapi import Body, FastAPI
from pydantic import BaseModel

app = FastAPI()

class Item(BaseModel):
    name: str
    description: Union[str, None] = None
    price: float
    tax: Union[float, None] = None

class User(BaseModel):
    username: str
    full_name: Union[str, None] = None

@app.put("/items/{item_id}")
async def update_item(
    *,
    item_id: int,
    item: Item,
    user: User,
    importance: int = Body(gt=0),
    q: Union[str, None] = None
):
    results = {"item_id": item_id, "item": item, "user": user, "importance": importance}
    if q:
        results.update({"q": q})
    return results

Description
教程-用户指南   中的  请求体-多个参数  中的  多个请求体参数和查询参数   中的示例代码出现错误
https://fastapi.tiangolo.com/zh/tutorial/body-multiple-params/#_3

Body参数缺少一个位置参数，即TypeError: Body() missing 1 required positional argument: 'default'
个人建议改为 Body(..., gt=0),
Operating System
Windows
Operating System Details
No response
FastAPI Version
无
Python Version
3.7
Additional Context
No response

Hi @liufei1997 Maybe you need to update the version of fastapi to 0.78.0.
See https://github.com/tiangolo/fastapi/issues/4911#issuecomment-1127729335


make = sign highlight

As you can see a colorscheme which tries to highlight operator symbols, but fails at the first
equals sign inside the member variable declaration.
As shown in the next screenshot, that now works, but i still don't know how to make
the ending colon on that line also highlight as the others do...

I found a way to solve the ending colons problem, coming in another PR.
I'm sure you noticed I'm still learning this, so I don't know if it's the best way to go....

I just noticed the ending colons are also not highlighting inside
'typescriptObjectType'

fixed

Thanks for using yats.
But I don't like the idea to hightlight all the non-alphanumeric symbols. It adds too much visual clutter.


ISO-8859-1 encoded XSD failes.

While processing nested XSD (all ISO-8859-1) i get the following error.
Error decoding XSD: xml: encoding "ISO-8859-1" declared but Decoder.CharsetReader is nil
with some time or some hints where to search i'm happy to add a PR to fix this.

Hello @kranzo, Thank You for the report. Are You willing to share a reproducer? Perhaps a small cut/subset of Your XSD is enough?

Looks like CharsetReader may need to be used. See https://github.com/golang/go/issues/8937


Threshold rule false positive

Hello I've implemented the following rule to monitor for no data on a specific index:
name: No data on index streamparse
type: flatline
index: streamparse-*
threshold: 1
timeframe:
    minutes: 60
realert:
    hours: 3
use_count_query: true
doc_type: "doc"
alert:
- "stomp"
stomp_hostname: rabbitmq
stomp_hostport: 61613
stomp_login: "guest"
stomp_password: "guest"

I got a lot of false positives, for example I got the following alert:
An abnormally low number of events occurred around 2018-06-27 11:41 UTC. Between 2018-06-27 10:41 UTC and 2018-06-27 11:41 UTC, there were less than 1 events. @timestamp: 2018-06-27T11:41:17.716208Z count: 0 key: all num_hits: 0 num_matches: 4

And then I query elasticsearch manually:
GET streamparse-2018.06/_count
{
    "query": {
        "range" : {
            "@timestamp" : {
                "gte": "2018-06-27T10:41:17.716208Z",
                "lte": "2018-06-27T11:41:17.716208Z"
            }
        }
    }
}

And I got the following result:
{
  "count": 372,
  "_shards": {
    "total": 1,
    "successful": 1,
    "skipped": 0,
    "failed": 0
  }
}

This happens a couple of time a day. Is there something wrong on my elastalert alert?

Try adding
query_delay:
  minutes: 5

I'd bet that elastalert is querying too close to the current time for the documents to register in Elasticsearch.


Verify profile installation succeeded

Not sure if we should and if we can do this.

Running profiles list -type configuration -output stdout-xml provides the information we need. Running that from a sandboxed app is fortunately not trivial.


Is there breacking changes from 1.7 to 2.0?

I guess the answer is yes, but is there a release note?

There's a changelog with the breaking changes.

Thanks!


Shuttle with feather.js error

Shuttle with feather.js gives message.toCosmosMsg is not a function
import { MsgSend } from<EMAIL_ADDRESS>
const msg = new MsgSend(
            "migaloo1xxxxxxxxxxxxxxxxxxxxxxx",
            "migaloo1xxxxxxxxxxxxxxxxxxxxxxx",
            { uwhale: 1200000 }
        )

const {simulate} = useShuttle()
const wallet = useWallet()
const response = await simulate({
        messages : [msg],
        wallet
 })

any idea how to make it works with feather.js

any update on this ?

the MsgSend class from feather.js isn't compatible with shuttle. Use the native one in the latest shuttle.
import { MsgSend } from "@delphi-labs/shuttle";

and how about MsgAllianceDelegate ?

It is possible to use stargate for custom msgs but currently shuttle doesn't expose the registry to register new protobufs.
Something like: https://github.com/cosmos/cosmjs/blob/main/packages/stargate/CUSTOM_PROTOBUF_CODECS.md
Could that be a solution?

This is a very good point, I think we need to improve the docs on how to add Msgs that Shuttle doesnt include (yet) so that everyone can just create a PR for them or even just have them locally and use them directly with Shuttle it's actually "pretty straightforward".

and how about MsgAllianceDelegate ? which is avaibale in feather.js but not on shuttle

For any Msg that Shuttle currently doesn't have you can easily create a custom Msg Class that is compatible with Shuttle as long as it implements the following required methods:
export class TransactionMsg<T = any> {
  static TYPE: string;
  static AMINO_TYPE: string;

  constructor(public typeUrl: string, public aminoTypeUrl: string, public value: T) {}

  toCosmosMsg(): CosmosMsg {
    return {
      typeUrl: this.typeUrl,
      value: this.value,
    };
  }

  toAminoMsg(): AminoMsg {
    return {
      type: this.aminoTypeUrl,
      value: this.value,
    };
  }

  toProtoMsg(): ProtoMsg {
    return {
      typeUrl: this.typeUrl,
      value: new Uint8Array(),
    };
  }

  toTerraExtensionMsg(): string {
    return JSON.stringify({
      "@type": this.typeUrl,
      ...this.value,
    });
  }
}

You can create a class for the Msgs that Shuttle doesn't have yet and test them directly on your codebase, if it works we would love to have PR for it, we only implemented the Msgs we currently need and we will be adding them as we need.
So for MsgAllianceDelegate you can write the following class:
import { Coin } from "@cosmjs/stargate";
import { MsgDelegate as TerraMsgAllianceDelegate } from<EMAIL_ADDRESS>
import TransactionMsg, { AminoMsg, ProtoMsg } from "./TransactionMsg";

export type MsgAllianceDelegateValue = {
  delegatorAddress: string;
  validatorAddress: string;
  amount: Coin;
};

export class MsgAllianceDelegate extends TransactionMsg<MsgAllianceDelegateValue> {
  static TYPE = "/alliance.alliance.MsgDelegate";
  static AMINO_TYPE = "alliance/MsgDelegate";

  constructor({ delegatorAddress, validatorAddress, amount }: MsgAllianceDelegateValue) {
    super(MsgAllianceDelegate.TYPE, MsgAllianceDelegate.AMINO_TYPE, {
      delegatorAddress,
      validatorAddress,
      amount,
    });
  }

  toTerraExtensionMsg(): string {
    return JSON.stringify({
      "@type": this.typeUrl,
      delegator_address: this.value.delegatorAddress,
      validator_address: this.value.validatorAddress,
      amount: this.value.amount,
    });
  }

  toAminoMsg(): AminoMsg {
    return {
      type: this.aminoTypeUrl,
      value: {
        delegator_address: this.value.delegatorAddress,
        validator_address: this.value.validatorAddress,
        amount: this.value.amount,
      },
    };
  }

  toProtoMsg(): ProtoMsg {
    const cosmosMsg = this.toCosmosMsg();
    return {
      typeUrl: this.typeUrl,
      value: TerraMsgAllianceDelegate.encode(TerraMsgAllianceDelegate.fromPartial(cosmosMsg.value)).finish(),
    };
  }
}

export default MsgAllianceDelegate;

Which as I write this comment, I already added to Shuttle and should now be available through the package but whenever you need anything new that isn't in Shuttle you can write the class yourself and pass directly to Shuttle and it should work.


replace tsdx with tsup

As tsdx is not currently maintainted, we can look around for a replacement. I heard about https://github.com/egoist/tsup, which can be a good replacement.
(some insights about it: https://twitter.com/iansu/status/1524860613943382017?s=21)

Maybe we should also consider https://github.com/preconstruct/preconstruct. It uses babel and I would prefer the simplicity of esbuild, so tsup seems like a better choice.