Rails 6.1 html.erb not reloading on changes

Hey, I'm using rails 6.1, ruby 2.7.2
When having a component ex
a_component.rb and having the template inside a_component/a_component.html.erb
when editing the HTML file, the browser reloads, but the HTML output doesn't change.
Worked before in 6.0.
To trigger the correct reload, I need also to change the a_component.rb

I do confirm I face the same behavior!

Rais 6.1.0
Ruby 2.7.2

Whenever I change the HTML markup in app/components/notification_component.html.erb and refresh the browser, changes do not seem to take effect.
To trigger the changes:

Restart the rails server
Do any change on any .rb file like application_controller.rb or user.rb, to give some examples.

Is that a expected behavior or there's any way to fix it?

@sebyx07 @alexventuraio thank you for the report! This is not the expected behavior. Might you be able to open a PR with a failing test?
There are existing tests for similar behavior you might be able to reuse bits of: https://github.com/github/view_component/blob/main/test/view_component/view_component_test.rb#L284.

@sebyx07 @alexventuraio thank you for the report! This is not the expected behavior. Might you be able to open a PR with a failing test?
There are existing tests for similar behavior you might be able to reuse bits of: https://github.com/github/view_component/blob/main/test/view_component/view_component_test.rb#L284.

Same issue on Rails 6.1.
Looks like ViewComponent::CompileCache.invalidate!  isn't triggered within reqests(mandatory to clear templates cache).
Manual call of ViewComponent::CompileCache.invalidate! in application code during request cycle - helps

@alexventuraio , @sebyx07,  i just setuped "view_component" on my new Rails app. Templates were always cached.
Then i found that i forgot to do  require: "view_component/engine" in Gemfile.
I had  gem "view_component" in Gemfile, but correct setup is gem "view_component", require: "view_component/engine"
After adding engine require - issue disappeared and i no longer need to do ViewComponent::CompileCache.invalidate! manually

@volodymyr-sh thanks!

I just ran into this too!  Making sure the require: "view_component/engine" was in Gemfile fixed it!
The "failure mode" of forgetting to do this is subtle, everything seems mostly to work, with some odd edge case failures (like this one), that you might not notice, or might not even realize it's broken.
I wonder if there are other error reports that could be caused by this but nobody realizes?
I wonder if the failure mode can be made "noisier" somehow, so if you forget to do this it's obvious you've made a mistake, instead of just subtle edge-case differences.
(If loading view__component/engine is optional, there must be a use case for choosing not to do it though? I don't think you can use ViewComponent without Rails at all, so I don't think that's it?  I assume there is a reason to not make loading the engine class forced in all cases though?)

@joelhawksley isn't there a way to make the gem work without having to require the engine from the Gemfile?

One way is following this: https://github.com/github/view_component/commit/9268939f06c1d47f312301ba092703940a8102d8

Perhaps following this: https://github.com/github/view_component/commit/9268939f06c1d47f312301ba092703940a8102d8

That's splendid, thank you for the effort @rmacklin  👍🏻
I can confirm that this change solves the "reloading HTML" problem.
As a side-note, the following line also fails when the engine was not loaded ("config.view_component is not defined").
# config/development.rb
config.view_component.preview_paths << Rails.root.join('spec/components/previews')

So, the change in your branch would also warrant changing the documentation here, the require can be removed:
https://github.com/github/view_component/blob/69087aaffb79d7c841990926d90edde1a2d3a440/docs/guide/getting-started.md#L22

Curious to hear from @joelhawksley if there's a reason we haven't been doing this before, or if we should proceed with the change


Clean-up: delete old frontend and dash apps. Keep old frontend in master, new dev moves to a develop branch

As we migrate to the new frontend, it will be easier if we don't have to maintain support for the old frontend (e.g. the new frontend uses a different authentication system, which conflicts with the old views), shall we delete it and dash apps? Then we can get rid of all the old view tests, and focus on testing the new api.

we can keep the old frontend on the master branch, and new dev moves to a develop branch?

Meeting 15th June: this seems like a good way forward.


add more logging to vmi.wait_until_running()

Short description:
Add more logging to VirtualMachineInstance.wait_until_running()
More details:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
Bug:

/verified

/verified

/verified

/verified

/lgtm

/verified

/cherry-pick v4.14

/lgtm

/cherry-pick v4.14


Update sap-solution-deploy-alternate.md

Changes to KV and AZ CLI support

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

@DavidMi13 - one change to fully spell out the acronyms, and then it looks like you need to update your fork.
but once those are done, please enter "sign-off" (preceded by a #) to have this merged into master. thanks!

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

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

thanks David!
#sign-off


Add insert_with_values to ListStore and TreeStore

Please squash and we're good to go!

Done

Thanks!


[hotfix][doc] add repo links of externalized connectors

What is the purpose of the change
Add the externalized connector repos into the doc to ease developer find the related connectors.
Verifying this change
This change is a trivial doc update.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)

Thanks @snuyanzin @1996fanrui for your review.


Fix doc description of HTTPClient::request

The URL parameter has been used directly as the request-target in HTTP request line since Godot was open sourced. So it's the doc description & sample code that's incorrect. The parameter should begin with a slash for common use cases.
Fixes #45195, also applies to the 3.x branch.

Thanks!

Cherry-picked for 3.4.

Cherry-picked for 3.3.3.


Convert structs that implement the Enumerable protocol to lists

I found it surprising that I could not use a MapSet or another Enum when using in in a query as I expected it to function similarly to Kernel.in/2.
ids = MapSet.new([1, 2, 3])
where(Comment, [c], c.id in ^ids)

This PR checks for an implementation of the Enumerable protocol and converts it to a list when casting, returning an error if there is none.
If this isn't the direction you want Ecto to go, I'm happy to have this closed. Otherwise, let me know anything else I should be mindful of or any documentation I should update.
Thanks!

Thanks. It would be good to update the docs here: https://hexdocs.pm/ecto/Ecto.Query.API.html#in/2

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


Subdomains list, can not select all elements when the list is in edit mode

Steps to reproduce
:

Navigate to a root domain details page
Click on Edit list to activate the Edit mode in the subdomains list
Click on Add Subdomains button
Add more than 2 subdomains
Click Select All in the list, in Edit Mode or try to select all the elements in the list, one by one
Current result: Just one of the newly added subdomains is selected, the rest of the new added subdomains can't be selected, and the background color is different
The number of elements selected is wrong

Expected results: All the subdomains in the list will be selected and the background color will be gray if and only if the row is selected. The number next to word Selected will match with the number of selected rows


Add a plugin: Leaflet.SimpleLocate

A Leaflet plugin displaying device location and orientation on the map, with orientation adjusted according to screen rotation. Tested on desktop and mobile versions of Chrome, Edge, Firefox, and Safari.

Demo Page: demo (Click the button on the demo page to activate, double-click to deactivate.)

Source Code: Github
Demo Page: demo (Click the button on the demo page to activate, double-click to deactivate.)


%mp_dirlist tries to overwrite last table

I've been working with %mp_dirlist and encountered some weird behaviour, in which the macro call fails dependent on whether it is run together with other parts of my script or as stand alone.
I call the macro as: %mp_copyfolder(&DQ_INPUT_PATH.,&DQ_FULL_DEST_PATH);
And get the error: ERROR: You cannot create or delete datasets, views or indexes in this mode. Try the option METAOUT=DATA. Use Proc Metalib to create metadata for datasets.
From the log it appears that it tries to overwrite a table in a libname that I have previously used, which it is not allowed to do for this libname. I believe it happens on this line in the macro (i.e. it ends up using the last table referenced in the script, which in this case is completely unrelated), but I am not sure what the best way to resolve it is:
https://github.com/sasjs/core/blob/21d6671a5feb240eff8fee39018dd86139b5367a/base/mp_dirlist.sas#L78

Nevermind - my code was missing a ; somewhere else, and that was causing unexpected behaviour. The macro seems to be working as intended.

Glad you resolved it!
We do have tests for this macro, you can find them here:  https://core.sasjs.io/mp__dirlist_8test_8sas_source.html


Make dataset snippets testable

Uses #1831 as a base.
Toward a real fix for #1786 and related issues (usage docs out-of-sync with API surface).

@dhermes Rebased after merging #1831 to master.  PTAL

@dhermes bump?

@dhermes can you make anything of the Travis failure?
travis_fold:start:worker_info
Worker information
hostname: travis-worker-gce-org-prod5-11:a4b53531-f729-499f-a1e7-fe8182a33df6
version: v2.3.0-5-gef7116f https://github.com/travis-ci/worker/tree/ef7116fac34a232b5d8ecfe0eb9d834b0af9705d
instance: testing-gce-9a8d2370-4c80-48b8-b2ee-014edd581e75:travis-ci-ruby-precise-1450195856
startup: 21.707417759s
travis_fold:end:worker_info
Could not fetch .travis.yml from GitHub.
/home/travis/build.sh: line 2: travis_terminate: command not found

Done. Your build exited with .
/home/travis/build.sh: line 5: travis_terminate: command not found

I've restarted it twice now.

Looks like a bad instance that failed to retrieve .travis.yml. It seems like their architecture is showing a bit (i.e. they re-use the same instance on re-starts and maybe cache the filesystem)

@dhermes I pushed a tiny docs tweak to re-trigger the Travis build, hoping it would fix any caching.

@tseaver I went here https://travis-ci.org/GoogleCloudPlatform/gcloud-python/caches and deleted the cache for this PR. It's building again. We'll see if that does the trick!

@daspecster Thanks for digging that up -- I didn't know it existed!

NP! Travis and I have battled before!

I will merge in spite of the pylint failure.  See #1974.


Hyperlinks Don't Work With 'full_pdf_viewer_scaffold.dart' Import

It appears if you import
import 'package:flutter_full_pdf_viewer/flutter_full_pdf_viewer.dart';
internal and external hyperlinks work however if you import
import 'package:flutter_full_pdf_viewer/full_pdf_viewer_scaffold.dart';
tapping links doesn't work. This isn't clear in the documentation why this is or which you should be using.

Okay this seems to be really crazy now. Could you send me a pdf url with hyperlinks that I can test this?

Could you provide me with an email address, I don't want to post links on here

sure<EMAIL_ADDRESS>

Thanks. Sent

Ok, I tested it. It does not work for me aswell. I have no idea why this is happening to be honest. Need to find some time to debug this. Could be possible that it is related to any AndroidX update....

Ok, I tested it. It does not work for me aswell. I have no idea why this is happening to be honest. Need to find some time to debug this. Could be possible that it is related to any AndroidX update....

Hi Albo1337, does 1.0.4 have a fix for this issue?

Hey @l-k22 I haven't test it anymore but I did not change anything so the issue should still be there.

To anyone with this issue, I ended up using flutter_pdfview


add video support

Using the youtube approach from ado-hugo.
Possibly eventually support other video sites, but not now.
If the "latest episode" has a video, show that video in the hero, not the image (video across the whole div, with summary below)

Fixed in #91


Set Maven Staging Repository for 1.1.0 jars and sign them

Staged Bundle 405 with staging workflow 16.
We are ready to publish maven artifacts for OpenSearch 1.1.0 to Release Channel.


Design and print automated turntable vial rack

https://www.tindie.com/products/fluxgarage/turntable-for-stepper-motor-kit/
For automated storage of Pioreactor vials, hopefully some way to make it easier to robotically insert and remove the vials. Maybe some kind of flexible mechanism?
Probably ~8 vials in a single rack. Ideally a Fusion 360 design with parametric modeling.
Something that can be fixtured to the top plate with minimal hardware (maybe even without hardware and using PLA-CF with four rounded pins/knobs to avoid breakage)
Perhaps upload to BambuLab maker world (?)
Aside: vial rack should perhaps have a spot on the side and/or on top for an AprilTag, and numbering of the vial positions along the side (1 through 8).

@MiceeNS thanks for your initial work on this.

Do you have dimensions spec sheet because I cant see find any in the link? Do you already have the automated turntable that is linked above? Are you trying to print only the white storage thing?
Will update the drawing as fast as possible

Ah got it, I think the design files might be around somewhere. Yes, I do have a few of these units. One is set up fully.

I would just be printing whatever attaches to the black top plate.

@cyrilcaoyang has also been looking into something similar.

This should have dimensions and design files for the base system: https://www.instructables.com/Automated-Turntable-With-Steppermotor/
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Bojan Micevski @.>
Sent: Thursday, October 10, 2024 2:32:04 PM
To: AccelerationConsortium/ac-training-lab @.>
Cc: Sterling Baird @.>; Mention @.>
Subject: Re: [AccelerationConsortium/ac-training-lab] Design and print automated turntable vial rack (Issue #15)
Do you have dimensions spec sheet because I cant see find any in the link? Do you already have the automated turntable that is linked above? Are you trying to print only the white storage thing?
Will update the drawing as fast as possible
—
Reply to this email directly, view it on GitHubhttps://github.com/AccelerationConsortium/ac-training-lab/issues/15#issuecomment-2405784710, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AK25ABNTSTZABDPFP63EPNLZ23B2JAVCNFSM6AAAAABNMX4N4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBVG44DINZRGA.
You are receiving this because you were mentioned.Message ID: @.***>

Thank you, will take a look

I think its best to order longer screws for the upper plate and attach the 3d printed vial rack on those screws. Do you want to change something on the vial rack? I suggest printing only one piece of the holder so we are sure fit tight and works well before printing the whole rack.

When I get more time, I will improve some things on the rack

Overall nice! Thank you. Do you mind starting one of the prints on the Bambu Lab printer?
Everything including and below the yellow plate is something that comes in the kit (except for stepper motor, which we buy separately). The only thing that is 3d printed is the actual rack. Originally, the intention was to have the vial rack attach via the holes on the side.

(Self-note / aside - file is https://a360.co/3UpCiPU)

Hey Sterling,
I will adjust so you can attach it with bolts on those holes. Will also specify which ones. For the Bambu Lab, I have the app but the credentials for log in is asking for email. I cant log in with the credentials you sent me. I made my own account but I am not connected to any device printer.
Could you please help me out with this.

That was my bad - just messaged you about the credentials.

Thank you, now I am in. I will print it asap. Do you prefer bolts or plastic studs in those holes. Maybe plastic studs would be much rational than bolting the rack?

Thank you, now I am in. I will print it asap. Do you prefer bolts or plastic studs in those holes. Maybe plastic studs would be much rational than bolting the rack?

Plastic studs sound fine! Could you include a link to a corresponding mcmaster part, if possible?

The plastic studs would be printed with the rack, cylindrical pins that would go in the holes of the turntable. That way you don't need to bolt it, but it can be lifted up.

Ah, got it! From a 3d printing standpoint, this might change what supports are needed. Considering the small size of the holes, the studs might break off (especially if they're long). Printing in the CF-imbued filament would help a bit with this. I'm not decided one way or the other. Thoughts?

Yes absolutely, I was thinking the same It would need to create a lot of supports because those studs are going to lift the rack from the ground. Lets go with bolt and nut. For future we might change and create more generative design.

Sounds good!

Please take a look : https://a360.co/3UpCiPU
Here are the materials you need from McMaster Carr:
https://www.mcmaster.com/91292a113/  x4
https://www.mcmaster.com/93625A100/ x4
You can also get any M3 bolt 10mm length and a M3 Nut with compatible thread if you want to go cheaper. I had to make the clearance for the hole close fit since you already have the holes on the Upper plate.
I will send it for print now if you are okey with this.

Ok, great! Yes, please do. Just have a look at the print chamber to make sure nothing is in it first

Oh, actually you might not be able to print today. Looks like someone has an overnight print they're doing.

I see printing going at the moment, will take a look later. If not, is it okey for tomorrow?

👍
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Bojan Micevski @.>
Sent: Thursday, October 24, 2024 5:25:37 PM
To: AccelerationConsortium/ac-training-lab @.>
Cc: Sterling Baird @.>; Mention @.>
Subject: Re: [AccelerationConsortium/ac-training-lab] Design and print automated turntable vial rack (Issue #15)
I see printing going at the moment, will take a look later. If not, is it okey for tomorrow?
—
Reply to this email directly, view it on GitHubhttps://github.com/AccelerationConsortium/ac-training-lab/issues/15#issuecomment-2436364295, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AK25ABMWGWPHETT6XTLDADTZ5FQVDAVCNFSM6AAAAABNMX4N4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZWGM3DIMRZGU.
You are receiving this because you were mentioned.Message ID: @.***>

I don't think the print will be removed tonight, so best to wait until tomorrow when it's been taken off. Maybe send the Bambu 3mf file over? (Not sure if there's a way to store the print in a queue)

It is higher than the printer can do probably, do you want me to shorten it?

Yes that sounds good. Maybe adjust for a 20 mL vial?

Hi @MiceeNS I was using the 3D printer extensively yesterday. Apologies for any inconvenience.
I opened the 3mf file you sent and the printer generated the supports like this:

Should it be printed this way, or should I adjust the support settings?

Hi @MiceeNS I was using the 3D printer extensively yesterday. Apologies for any inconvenience.
I opened the 3mf file you sent and the printer generated the supports like this:

Should it be printed this way, or should I adjust the support settings?

I changed to the normal supports settings, if you think this might cause any issues please adjust. Thank you

Hi @MiceeNS I was using the 3D printer extensively yesterday. Apologies for any inconvenience.
I opened the 3mf file you sent and the printer generated the supports like this:

Should it be printed this way, or should I adjust the support settings?

I changed to the normal supports settings, if you think this might cause any issues please adjust. Thank you

I’m not familiar with the purpose of this part, so I’m just double-checking that these supports won’t interfere with its use.
I’ll proceed with the print as you’ve set it.

Are you placing the print in que or you have to wait for the printing to finish?

Hi @MiceeNS I was using the 3D printer extensively yesterday. Apologies for any inconvenience.
I opened the 3mf file you sent and the printer generated the supports like this:

Should it be printed this way, or should I adjust the support settings?

Let's hold off on you doing the print. Didn't realize the supports would be quite like this. @Neil-YL can you make sure the print bed is clear of parts at the end of the day? That way @MiceeNS can tune the design and supports as needed and send the print remotely.
Sorry for the back and forth and confusion.

@Neil-YL Are you placing the print in que or you have to wait for the printing to finish?

I have not put it in queue but the printer is available now if you want to access

Supports are 30% of the time, the only way I can make this better is changing the actual design of the model. Or make this holders to be printed separate and attached to the column. What do you think @sgbaird ?

Ooh, good point about the holders being separate. From a print standpoint, that would make things a lot easier, and a lot better and that it could accommodate a range of vial sizes by inserting different sized holders as needed, and would be relatively straightforward to switch from one vial size to another vial size completely.
If using a mechanism where it clips in to the rack, then as long as there's access from the top for someone's hand to fit through, I think the clip mechanism could be undone.
An alternative (that I don't like as much) is splitting the vial rack in half, printing separately, and attaching the two halves later either with hardware or a "clip together" mechanism.

No need for clips (they can be hard to design and easy to break), I would make like a turbine blade root which can be attached to the column. Do you know the diameter and approximate height on 20ml vial? Different vials manufacturer have different diameter on google.

I am having a fever at the moment, but will try to make it by tonight and print it.

Ok, turbine sounds good (makes sense about clips). Take some time to feel better - this one isn't so urgent.

Share file link - https://a360.co/3YpRoWC
The triangles are to reduce material and not create supports. The model now is without supports. The holders have same "adapter" so you could just draw another model tomorrow and just attach it. some of the important dimensions you could check them on the drawing.
Same bolts and nuts like in the previous design.
Let me know what you think and if OK do you want me to print it?

Way cool! 😎 Yes, please do!

There is a problem with the first layer sticking on the plate. I will stop this print, if somebody has a chance to clean the print bed.
I check on the internet it is some problem with adhesion with the printing bed, it needs to be cleaned with 70% Isopropyl Alcohol. Do you have any suggestions?

@Neil-YL ?

Usually alcohols can help remove the grease possibly from skin contact. If glue was used in the previous print, it is best to wash thoroughly with water and wipe dry with some isopropanol.We recently found in SDL2 that the PEI bed can wear out over extended use and become less sticky to PLA. Hope this is not the case :)YangOn Oct 26, 2024, at 20:36, Bojan Micevski @.***> wrote:
Screenshot.2024-10-26.202914.png (view on web)
Screenshot.2024-10-26.203216.png (view on web)
There is a problem with the first layer sticking on the plate. I will stop this print, if somebody has a chance to clean the print bed.
I check on the internet it is some problem with adhesion with the printing bed, it needs to be cleaned with 70% Isopropyl Alcohol. Do you have any suggestions?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

@Neil-YL, have you dealt with this before? (We can address next week)

Based on my experience, I would suggest enabling the Raft layer function when printing parts with very small details on the first layer or when the geometry is not perpendicular to the X/Y axis of the printer.

@Neil-YL, have you dealt with this before? (We can address next week)

Based on my experience, I would suggest enabling the Raft layer function when printing parts with very small details on the first layer or when the geometry is not perpendicular to the X/Y axis of the printer.

Thank you for sharing your knowledge! Will do that in the next print.

I have cleaned up the print bed

I have cleaned up the print bed

Thank you, when I get home I will give it another try.

I had the same problem today with the print. When you get a chance could you please clean the printing bed @Neil-YL?
Also, is it possible for me to send you the file so you can try to print it? I tried multiple times on different places on the printing bed.  This is only the raft being printed.

@Neil-YL that would be great if you could try to get the file printed. Not a super urgent task - sometime this week or next would be fine.

I had the same problem today with the print. When you get a chance could you please clean the printing bed @Neil-YL?
Also, is it possible for me to send you the file so you can try to print it? I tried multiple times on different places on the printing bed. This is only the raft being printed.

Of course. Please send the model file to<EMAIL_ADDRESS>

@MiceeNS you can also attach directly here (not sure if you'd need to zip it based on filetype). If .zip or the file type isn't supported, email is fine too

Sent him the file through gmail, luckily I remembered to send it to myself this morning.

This is a photo of a failed first layer:

The failure mainly located close to the edge of the bed, I am suspecting an uneven temperature distribution of the printing bed.
After several trails and errors, I seem to have a promising first layer print:

What I change to have this print:

Initial layer height:  The default setting for Banbu is 50% of the nozzle diameter, which is 0.2 in our case. I changed it to 0.35mm (close to the diameter of the nozzle) to have a better adhesive performance of the raft layer (since we print with raft layer the first layer thickness may effect the quality of the printed parts)
Bed temperature: the previous setting is 55 Celsius,  I increase to 65 for the first layer (actually I didn't change it for the whole printing work).
I also rearranged the parts to have a more regular placement on the bed and remove the largest part to be print in separate work.

If this print still fails, I would reduce the amount of the parts and place them in the middle of the bed.
Reference:
https://overture3d.com/pages/help-center?hcUrl=%2Fen-US%2Fnot-sticking-to-the-bed--bed-adhesion-issue-765548

Could you please help me confirm the number of these two parts, now I have eight for each.

8 of each, i dont care about the surface inside the legs , sry I am not responding fast
Thank you

The parts would be ready to use by tomorrow

Thank you @Neil-YL , you are the hero!

How does the connections fit? Are they tight? I would not want them the move and also easy to put them in / take them out.
What are your impressions?
Thank you again for what you are doing.

@Neil-YL maybe a quick video of insertion and removal?

The grip on the vial when inserted is pretty good. It could be a bit looser.
@Neil-YL maybe tomorrow you could also upload a video of inserting and removing a vial?

The grip on the vial when inserted is pretty good. It could be a bit looser.
@Neil-YL maybe tomorrow you could also upload a video of inserting and removing a vial?

we can adjust that no problem, I had no idea of the diameter of the vials and also it depends on the plastic flexibility

The connection is very tight. I have to polish a bit to assemble them in place. It is almost impossible to remove without tools now.
Here is a short video
IMG_0381.MOV

I dont think we want to move them frequently, just in case one breaks to replace it.

I was impressed it happened to be such a good size! I think somewhat looser on the vial and slightly looser on the inserts and we're golden.

Here is a video of inserting and removing a vial
https://github.com/user-attachments/assets/b3a6f911-6654-45e7-ab9e-adbdd0e1c3b6

Holder v2.zip
STL file
I changed the tolerances and the holder grip, it should be better now. I can try printing it if you want when the printing bed is empty. It is only the holder not the whole design

@Neil-YL could you send the print? @MiceeNS, you're welcome to (seems open now), but there are some other users so occasionally there will be overnight prints.

@Neil-YL could you send the print? @MiceeNS, you're welcome to (seems open now), but there are some other users so occasionally there will be overnight prints, which is when I'd imagine you're usually sending prints.

Sorry I am not in the office this afternoon and it seems the printer is in use now. I can try tomorrow morning

Sent to print

All eight is fine - not a super long print. Maybe if we have future iterations just one so we can check the tolerance and fit first.

The new design is too loose to hold the vial. I should have printed once for trial first.
Here are the videos:
https://github.com/user-attachments/assets/8046cd1d-7cdd-49bc-8a61-28652c5d09f7
https://github.com/user-attachments/assets/0547bf45-066f-4cee-b522-dea6a9455c0b

Thanks @Neil-YL!
@MiceeNS, I'm thinking of two options:

We add a little platform for the vial to sit on (I had been considering this, and am thinking now maybe it would be worthwhile)
We switch to a single-layer design that is basically just 8 holes, maybe with a slight backdrop to each one

Holder v3.zip
@Neil-YL I am printing another holder, could you please test it out when you get there. Also, would you be kind to give me the dimensions of the vial like diameter and height

Even though we might change the complete design I do not want to leave this unfinished.

Holder v3.zip @Neil-YL I am printing another holder, could you please test it out when you get there. Also, would you be kind to give me the dimensions of the vial like diameter and height !

The diameter of the vial is 27.5mm and height(with cap) is 66mm
The new holder is way too large compared with previous two, here is a video testing the vial holding with three designs:
https://github.com/user-attachments/assets/ba91dfb1-b1ae-4b86-b6b1-e656912f0187

Holder v3.zip @Neil-YL I am printing another holder, could you please test it out when you get there. Also, would you be kind to give me the dimensions of the vial like diameter and height !

The diameter of the vial is 27.5mm and height(with cap) is 66mm
The new holder is way too large compared with previous two, here is a video testing the vial holding with three designs:
IMG_0694.mov

Thank you

Maybe worth printing a series of sizes?

Maybe worth printing a series of sizes?

Should I test the third one (the most recently printed) with a different size vial? I’m not very familiar with this project, make sure I’m not missing any context

Maybe worth printing a series of sizes?

Should I test the third one (the most recently printed) with a different size vial? I’m not very familiar with this project, make sure I’m not missing any context

If you have time it's not gonna hurt to try it but initially i was designing it for the same vial.I had no idea on the dimensions and was just guessing. Next I will print 3-4 designs hopefully it will work.
What you can try is the last design tolerances on the rack. See if it fits nice.
Thank you for all your help, I don't know how to make it up for everything you do!

I think the fit on the rack is excellent. Stable and not difficult to remove.
Here is the video:
https://github.com/user-attachments/assets/ebb3814d-c569-4772-b794-b093c784f598
I’m not sure if we have other sizes of vials in the office. Maybe Sterling could let me know if you’d like to try designing a series with different sizes.

From the video Design 3 is the best in my opinion. @sgbaird let me know if you want me to print 8 of them for the rack. Or maybe there is still room for improvement on the holder

Thanks @Neil-YL! The video was really informative. Thanks for the designs @MiceeNS! I agree, let's go with design 3. We can wait on printing more until we do some testing.
@MiceeNS could you tell us the dimensions of the square plate meant for the AprilTag?
@SissiFeng, could you print an AprilTag of the dimension @MiceeNS provides and put it in the training lab office? I'll leave it up to you which family and tag you want to use.
@Neil-YL could you fixture the AprilTag to the vial rack?
@gursi26 can you try out a vial insertion and removal workflow with a MyCobot 280 Pi? (fyi to Bojan: it's a low-cost robot arm, but also lower accuracy/precision and less force).
A picture of the vial rack with the fixtured AprilTag/holder and videos of the insertion/removal attempts (even and especially failed attempts) would be great to have.
Once we have a setup working decently, then I suggest we print 8 holders of the final design (might be the same version as above), and I'll ask someone to handle the stepper motor of the turntable.

@SissiFeng the square dimensions are 25mm x 25mm. Picture of the square plate

@sgbaird Sure. I will get the vial rack ready for MyCobot test.
@MiceeNS Do you need me to print the new vial holder? Someone else is using the printer (until 14:00) I can set up the print after that one finish if you can send me the model file.

@sgbaird Sure. I will get the vial rack ready for MyCobot test.
@MiceeNS Do you need me to print the new vial holder? Someone else is using the printer (until 14:00) I can set up the print after that one finish if you can send me the model file.

I do not have Design 3 with the root that can be mounted on the rack. I will do that tonight and send one to print.

Root, as in a little shelf at the bottom?

Root, as in a little shelf at the bottom?

That is the word that I came up with :) The last designs did not had the feature to be attached on the rack. I did not want to waste material if the designs did not work.
The green marked on the picture:

Oh, got it! The "puzzle piece" portion at the base of the clip. I was thinking about a small shelf for the vial to sit on to keep a more consistent XYZ position for the vial. Thanks for clarifying!

Oh, you mentioned that before. I could add like a bottom support for the vial to sit on. Whoever the holder grasp the vial and it will just levitate from the bottom support. Unless it should be like a slot that guides the vial to the holder position.

I could add like a bottom support for the vial to sit on

That would be great. Not required for the tests I described above, but maybe nice to have.

Hi @MiceeNS
Someone plans to print a large model over the weekend (but it might not start before your tonight). Since no one can collect our part during the weekend to clean up the plate for them, I think you can post the model here after you finish the designing, and I’ll print it as soon as I get to the office next Monday.
I will print one first for test and if everything works well I will do eight then.

Here are two designs. There is nothing on bambu studio currently on the printing bed so I could print them. The design with the bottom support requires bunch of supports i can adjust it in future for less supports. Let me know if you want me to print both design
Attaching zip file with both STL files and the bambu lab project.
Holder Designs.zip
Shared file link: https://a360.co/3V1MVc0
Pictures:

I think the idea is that someone is planning to start a print tomorrow that may take up most of Saturday and Sunday, so if you haven't submitted the job already, maybe best to wait for @Neil-YL to run it on Monday. If you have, no worries ☺ training lab projects like these take priority since it's owned by the training lab.

Cool designs!

I will try to redesign this, now having a full picture of the automation and the purpose of rack I think there are simpler and better ways of doing it.


Manage profile

#361

I think you have missed web series, tv, movies, premium, and few other pages.
Also, change manage profile to "My Profile".

@shivshankar9 any updates.

Tommorow I will try to make or

Share the website link also when you are done. So I can review your changes.

https://shivshankar9.github.io/Movie-Streaming-Website/

Correct all navbars. Also, add scroll to top button in profile page.

Please open others issue for this, because of my exams load unable to make contribution
I need some time to fix
Also if you wish ,you can close this PR I have no issue with that..

Take your time.


Feature Request: To make this theme compatible with the Influx Plugin

Feature Requested
I hope this theme is compatible with the Influx Plugin ((https://github.com/jensmtg/influx)).
Relevant Screenshot
This is what shows in the Default theme:

This is in this theme:

Checklist

[X] I have checked that the feature is not already available via the Style Settings plugin.
[X] The feature would be useful to more users than just me. (If it's only relevant to you, have you considered using a CSS Snippet?)
[X] My issue concerns Obsidian version 0.16+ and I am not using the Legacy Editor. (Older Obsidian versions and the Lecacy Editor are not supported anymore.)

+1 for this

+1 for plugin support, any updates on the plugin support @chrisgrieser?

In the latest release, there is an option to use the normal display of backlinks. That setting also affects the influx plugin, and enabling it will display the regular influx plugin display you want.

Thanks, @chrisgrieser!


Argument in stacktrace

Description
I would like access arguments from the stacktrace inside the notification callback, which is currently not possible.
It's clear that this is a design choice atm given the following code:
// Reduce memory usage by omitting args and objects from backtrace
$backtrace = debug_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS & ~DEBUG_BACKTRACE_PROVIDE_OBJECT);

It would be nice if there was a config option to change this.
If you also see a benefit in this or would suggest a different solution,  I am happy to provide a PR.

Hi @jeroensmit, thanks for the feedback, I'll raise this ticket to our products team to consider.


Logging issues

See original issue on GitLab
In GitLab by [Gitlab user @devcurmudgeon] on Feb 12, 2018, 11:28

Not obvious what all the ?????? mean
logs are losing some timings

bst reports [00:00:41] SUCCESS Updated 0 source references
time tells me "real	0m44.317s"

all config should be reported in the logs (so it's clear what was being done)
all cache-keys should be reported in the logs
there is no indication of what happened when - bst is only reporting specific times for individual tasks, not the wall clock time

In GitLab by [Gitlab user @tristanvb] on Feb 12, 2018, 12:04

Not obvious what all the ?????? mean

These are printed only in the case where the cache key cannot yet be known, this happens when tracking is enabled during a build until the element completes tracking (discovers the latest sources), or when workspace builds happen until after the build completes.
It is possible though that some messages could have had a cache key in them but dont, that would be a good bug to fix if this is the case.

logs are losing some timings
bst reports [00:00:41] SUCCESS Updated 0 source references
time tells me "real 0m44.317s"

This is #186

all config should be reported in the logs (so it's clear what was being done)

Disagree.
I.e. it is not relevant in the log, if I chose to provide 80 lines of context for build failures to appear in the master log, or if I stuck with the default 20 lines. It's also not really relevant if I explicitly launched the build with forced colors in the output or not.
Policy is to make sure that anything which may effect the output should be included, and a few other details which are less pertinent have also snuck through (like how many builder processes and network processes are allowed to run concurrently).
Is there a specific detail you would like to see in the startup summary ?

all cache-keys should be reported in the logs

If there are places where a cache-key is known but was never printed, this should be fixed.
Further, I would be interested in seeing a summary of all cache keys which were derived during the build process printed at the end of the log along with the rest of the summary.

there is no indication of what happened when - bst is only reporting specific times for individual tasks, not the wall clock time

This is #193, what you want here is some level of control and customization in logging.

In GitLab by [Gitlab user @devcurmudgeon] on Feb 12, 2018, 12:25
Config: Logs are part of the evidence of a project. Worst case, I may need to produce a log in court, to show what was done. If we don't log all of the config, logs can not be traced to anything.
Wallclock: I don't want to have to configure logging. wall clock time is much more useful by default than the current overuse of [--:--:--] imo.

In GitLab by [Gitlab user @tristanvb] on Feb 16, 2018, 11:46
So after discussing this in private and reaching a conclusion that it will be acceptable to make log lines configurable, I've created #258 to reflect that specifically.
For the rest of this I think we have things covered already:

Cache keys are printed in the early summary where possible

When workspaces are not open, which means the cache key needs to be discovered during the session
When all source refs are currently known, which means they dont need to be tracked and discovered during the session

If cache keys cannot be known, they are displayed in the log as they are discovered

Issue #252 was opened to make these cases also more clear, so we should be printing a summary of what was discovered during the session all in one place at the end

Incorrect total session time is known issue and should be addressed in #186
Wall clock time should be handled as a part of #258
"all config should be reported in the logs" is too vague at this point, we agree that not all config needs to be printed (i.e. it doesnt really make sense to print the configuration of how many lines will be displayed for a message or an error)

While we've been careful to record everything pertinent in the log heading before the pipeline summary, it is of course possible that we're missing some important things; however these should be reported on a case by case basis, otherwise the issue is too vague to ever truly close.

So I will close this issue now and leave it to the individual issues to get solved.

In GitLab by [Gitlab user @tristanvb] on Feb 16, 2018, 11:46
closed


proposal: encoding/xml: Allow to omit default namespace declarations

Problem and Proposal
Currently, an arbitrary Go value marshalled to XML with a (non-local) XML namespace sets the default namespace for its start element and all elements contained within it. For example, a value with local name "foo" in the "bar" namespace would be marshalled as
<foo xmlns="bar"/>

While this leads to succinct XML most of the times, it does not work well with the newly added 1.5 feature to declare custom namespace prefixes: the xml.Encoder marshals the xml prefix declarations but ignores them while marshalling inner XML elements (see the example below).
I propose to make the declaration of default namespaces optional, and activated by default for backward-compatibility. To do so, I outlined a proof of concept in CL 11074.
Example
A value of type
type Foo struct {
    XMLName xml.Name `xml:"foons foo"`
    Bar     string   `xml:"barns bar"`
}

encoded with EncodeElement and explicitly declared namespace prefixes "f" for "foons" and "b" for "barns" is currently marshalled as
<foo xmlns="foons" xmlns:b="barns" xmlns:f="foons">
   <bar xmlns="barns"></bar>
</foo>

whereas the following output might be expected
<f:foo xmlns:b="barns" xmlns:f="foons">
  <b:bar></b:bar>
</f:foo>

ATTN some recent contributors to this package: @rsc @dspezia @rogpeppe @dullgiulio @nigeltao
Does this make sense to you?

This proposal was based on the now reverted XML changes for Go 1.5. I might just as well close this issue and abandon the CL. If there is no other feedback, I'll do so tomorrow.

I'll just close it now.


Internationalize strings

Hi!
I've been using a modified version of Bootstrap Select, because I want the text of Selects in Brazilian Portuguese (things like "Nothing selected", or "No results match" when the select has a search field).
Although I can make changes for myself, and post on my own server, it is not possible when a third party CDN serve JS files: I'm using jsdelivr.com now.
If there is a way to add internationalization of strings, can help with the translation.
Thank you.

We seem to have i18n working now, so I'll be closing this.


Feature/static map and dashboard pages

Overview
Updates the map and dashboard routes to use next v9's getStaticPaths and getStaticProps when building the app. With this comes a few positive side effects:

we are now using the new nextjs catch all which allows for a path of /map/ to exist without needing a rewrite on the server to /map/global/. This solves the issues we were having with query params not updating and is more inline with what we are trying to achieve.
we can pre-build the country pages so that they are served statically, making them lighter and faster
we can now use the next-sitemap library to parse our statically built pages and dynamically output a sitemap to our public folder. This has some cool features:

we can trigger out sitemap with the npm postbuild script allowing us to rebuild the sitemap whenever we deploy.
the sitemap will always be up to date with the current page routes of the app
a robots.txt files is output in parallel with the sitemap referencing any (multiple) sitemaps generated and with a size limit. This helps us to follow SEO best practices.

Notes
The next-sitemap library has the following config. Note the excluded paths and transform functions for handling exceptions to the rule.
module.exports = {
  siteUrl: 'https://www.globalforestwatch.org',
  generateRobotsTxt: true,
  sitemapSize: 5000,
  changefreq: 'weekly',
  exclude: [
    '/404',
    '/search',
    '/thank-you',
    '/browser-support',
    '/terms',
    '/my-gfw',
    '/privacy-policy',
    '/subscribe',
  ],
  transform: (config, url) => {
    if (url.includes('/embed')) {
      return null;
    }

    if (url.includes('/map') || url.includes('/dashboards')) {
      return {
        loc: url,
        changefreq: config.changefreq,
        priority: '0.7',
        lastmod: config.autoLastmod ? new Date().toISOString() : undefined,
      };
    }

    return {
      loc: url,
      changefreq: config.changefreq,
      priority: '1.0',
      lastmod: config.autoLastmod ? new Date().toISOString() : undefined,
    };
  },
};

Testing

check out the /sitemap.xml
visit the global map /map and make sure query params are updating
visit a country map page through click interaction
visit the dashboards and change countries
visit a widget embed page

Thanks! Then off it goes, into the wild 🥏 🌴


Adds Validator for Image Type and Size

Checks that assets are

png (or svg)
if png that they are not more than 200x200
that height and width are equal

prints to terminal like
⚠ MZPN width is 343 should be less than or equal to 200
🟨 cSHIBA height must be same as width height: 53 width: 64
✅ Poof Governance Token
✅ Moola cEUR
✅ Celo Euro
✅ NetM Token
✅ Moola
✅ Optics v1 WETH
✅ Optics v2 USDC
complete 🚀

exactly 200 sounds smart to me. And simple to change, and simplifies the logic too.
My view is that the filesize check for svg can be done in the future.


update HOW_TO_RELEASE.md

This PR updates our step-by-step guide for releasing Xarray. It makes a few minor changes to account for #6206 and officially documents the switch to CALVER. This should be clearly documented in whats-new.rst as part of the first release utilizing CALVER.
Also, note that this should probably wait until we make the 0.20.1 patch release.

[x] Closes #6176, #6206
[ ] User visible changes (including notable bug fixes) are documented in whats-new.rst

A few other things we can do:

Insert things like contributors automatically; I've used fastmod for this sort of automation

Not sure whether we can strip out bot names?

Automate checks for things like "am I on the correct branch", remove checks like "run the tests again" given our CI infra is really good now (thanks @andersy005 & @keewis & others!)
Automate release notes? Is this possible (without spinning up GPT3 :) )

I didn't add a description for them the most recent release
We already have whatsnew, maybe that's enough?
I rather enjoy reading release notes for libraries I follow! So maybe this is something to spend a few minutes on?

Insert things like contributors automatically; I've used fastmod for this sort of automation
Not sure whether we can strip out bot names?

Yes, let's do that - we could have a bot name red list, but I don't personally think it matters if there are a couple of bot names or duplicated names in the list.

Automate checks for things like "am I on the correct branch", remove checks like "run the tests again" given our CI infra is really good now

If we can do this reliably then yes!

Automate release notes? Is this possible (without spinning up GPT3 :) )
I didn't add a description for them the most recent release
We already have whatsnew, maybe that's enough?
I rather enjoy reading release notes for libraries I follow! So maybe this is something to spend a few minutes on?

I feel like we could just make release notes explicitly optional? So we can write a summary if there is particularly cool feature we want to highlight, but most of the time the whatsnew will do fine?


Improve validation support for NumberFieldEntry

Is your feature request related to a problem? Please describe
Currently, dealing with number fields can be a little bit confusing. While there is browser built-in validation for number fields, how it is displayed is browser dependent and at least in Firefox requires a hover on top of the field, which is pretty hard to find.

I don't think there exists a way to pipe the validation errors through to the UI via code (I could be wrong), though I know that via CSS we can at least apply some styling rules if the field is invalid, this might be useful. But in practice, I'd still rather have a similar validation experience as with the regular text fields.
Describe the solution you'd like
Allow the supplying of a validation function for the NumberFieldEntry component, mirroring how it is done for TextFieldEntry.
Describe alternatives you've considered
Rely solely on browser default validation, unfortunately, the way browsers do this lacks a bit of clarity
Additional context
Initial comment that shows the confusion people experience with this: https://github.com/bpmn-io/form-js/pull/490#pullrequestreview-1245538661
@nikku @philippfromme I'm happy to implement this myself, if you think this is a positive addition.

I think we should ignore the browser validation as it's essentially useless. Would be great to have an attribute like novalidate for number inputs.
We should

be able to add a validate function to a number field (similar to the text field https://github.com/bpmn-io/properties-panel/blob/main/src/components/entries/TextField.js#L99)
show validation errors below the number field
only commit if valid


ribosome biogenesis and gene expression

Gene expression includes transcription , RNA processing (All), translation, protein maturation, mRNA export from the nucleus.
I wonder if it should therefore include all of ribosome biogenesis?
(RNA processing is a part of it, other parts are ribosome export etc)

To me that would be very misleading.

Pombe gene expression Guru, Jürg Bahler:
"
That's a tough one. Of course, ribosome biogenesis is ultimately required for gene expression via translation. But is quite indirect and removed from actual gene expression steps. So I probably would not have it as a child term of gene expression."
So I'll close this.


Update to support latest toml-rb 1.0.0 gem

Unfortunatelly there is no branch for 4.4.1 version so creating request to master.
Could you please create an "old stable" branch to use with older influxdb versions?

hey @igorfraa, I created this branch for you: https://github.com/bdangit/chef-influxdb/tree/4.4.x
Please rebase against this and we'll review.
Thanks!

closing in favor of #148


Bump the version of the tensorflow image in our tensorflow example

This example runs on Python 3.8, which we're about to drop support for.
I picked an arbitrary "newer but not too new" version which we seem to be able to run the example to completion on. My depth of knowledge is shallow here though! The code doesn't crash and the loss goes down; what more can you ask for?
Type of Change

[x] Example updates (Bug fixes, new features, etc.)

🚀 The docs preview is ready! Check it out here:     https://modal-labs-examples--frontend-preview-727a750.modal.run


unsupported: Unsupported manifest type: "application/vnd.docker.distribution.manifest.v2+json"

When pushing an image based on windows server core to an AWS Docker registry I get the following error:
_

unsupported: Unsupported manifest type: "application/vnd.docker.distribution.manifest.v2+json

_
The image is created on Windows Server 2016 and contains a very simple microservice built using the .NET framework 4.5
Here is the command I use and output I receive:

Update:
Version of Docker on Windows Server : Docker version 1.13.0-rc7
Also I've ran the same commands locally on my laptop using windows 10 (Docker version on laptop: 1.13.0-rc6 ) The only difference is all layers get pushed but I still get the same unsupported manifest type error.
fcce8c55821b: Pushed
097c55a86c36: Pushed
d04fd9623061: Pushed
f83e0c591482: Pushed
cdcc56b93609: Pushed
03cc226bcb9b: Pushed
c28d44287ce5: Pushed
f358be10862c: Pushed
unsupported: Unsupported manifest type: "application/vnd.docker.distribution.manifest.v2+json"

@MullaCode which version of the registry are running? This error indicates the registry is an older version and needs to be upgrade to at least registry 2.5 to get foreign layer support and support mentioned manifest type.

@dmcgowan I'm using Amazon EC2 Container Registry(ECR) - ECR does not make use of the standard Docker Registry software as it uses IAM for authentication and uses a custom storage backend. ECR implements the Docker Registry HTTP API V2 so as to be compatible with the official Docker registry software.

@MullaCode you will need to reach out to Amazon support to check if they are supporting Windows images and if not what their timeline is. You can try a different registry provider until then to make sure you are able to push/pull windows images without problems.

Hi @dmcgowan


Canary/generator fix

This PR fixes:
Generator.cs must not be outside of the Editor Assembly Definition because it uses UnityEditor and thus would prevent games from building
Cleaned up using statements in generator related classes.
Removed unused methods in Generator code
Fixed a potential bug (and at least resolving warnings) because IndexOf is culture specific

If I get this right, Templating.cs will fall apart when there are nested <%IF ... >  blocks.
It would be smarter to use an recursive approach

Yeah I was right about the thing with the nested-IF blocks.
I added a fix for that. the results can be checked here: https://repl.it/@soraphis/CautiousFocusedMicrocode

Thanks @soraphis ! Nifty implementation of the templating algorithm! ⭐
Got one question, even though I closed the PR. Have you checked that you allow the maintainer to push commits to the PR? I tried to push some small style tweaks in 2 commits to your PR, but got permission denied. It's really annoying. I might be doing something weird, but don't thinks so. I run the following commands:
git checkout -b soraphis-canary/generator-fix canary
git pull https://github.com/soraphis/unity-atoms.git canary/generator-fix

And then make my code changes. Then:
git add .
git commit -m "My changes"
git push https://github.com/soraphis/unity-atoms.git soraphis-canary/generator-fix

Then I'm getting:
 ! [remote rejected] soraphis-canary/generator-fix -> soraphis-canary/generator-fix (permission denied)
This is driving me nuts 😨

Have you checked that you allow the maintainer to push commits to the PR?

Github seems strange in this regard. when creating the PR there is the "allow maintainer to push" checkbox which is ticked. but after creating the PR it seems the checkbox on the right side gets disabled.
I now checked it, and I'll make sure in future to double check this after creating the PR.
Another thing in that regard you might want to consider, instead of pushing yourself to canary directly creating feature branches and creating PRs yourself, giving others some time (a day or two) to give a code review. (I mean its your repo and you can do as you like, its just a suggestion)

Hmm that is weird 🤔Would be great if you really make sure next time to check it!
I understand that it would be desirable that I create PRs. However, I've got a bunch of changes that I want to get through here pretty soon in order to release v2. I will reconsider this after I have released v2 / or before that but after all the changes I have in mind are done.


Module namespaces are missing proper prefix

E.g. https://github.com/aeternity/aepp-sdk-elixir/blob/2293280e0c863da2a808375ee9ed7080082bcd70/lib/core/channel.ex#L1
This makes it harder to use the codebase without naming conflicts.

solved with #121


chore: improve README.md

added sections on running tests, current limitations, and license
link to other docs
update slack link
add screenshot

Will resolve #67.
Question - what should go under future plans??

looks good to me :shipit:


get rid from the error & close issue #44

in line 176 we may destroy non existing select2 - this is causing the error when we have no select2 previously attached to the field
in line 175 i've added check for that

+1

+1

@aldeed Any chance you could accept this PR? Fix looks good and it looks like it will solve a problem many people are experiencing. Thanks!

@aldeed Yes, please merge 👍

@aldeed please merge this one 👍

@aldeed Thanks!
On Mar 26, 2017, 9:41 AM, at 9:41 AM, Eric Dobbertin<EMAIL_ADDRESS>wrote:

Merged #48.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/aldeed/meteor-autoform-select2/pull/48#event-1015678395


duplicateItems directive does not survive call to setChoices

Consider the following set of circumstances:

Choices constructed with duplicateItems: false in its initial config
Choices are populated via setChoices (e.g. as the result of a backend query)
An item is chosen
Choices are replaced via setChoices (e.g. as the result of a second backend query), and the new set of choices includes the same choice as was chosen before

Expected behavior: the item chosen in step 3 is not displayed as an option and/or cannot be chosen a second time.
Actual behavior: the item chosen in step 3 is displayed as an option, and can be chosen for a second time in spite of disallowing duplicateItems in the config.
Use case: I'm using Choices to have a user select recipients for a private message, where the recipient can be any registered username. As the user begins typing, the typed string is sent to the server to find all usernames with this prefix, and the list is returned and applied.
My code looks something like this:
        var choices = new window['Choices'](newElem, {
            'removeItemButton': true,
            'duplicateItems': false,
            'placeholderValue': 'Start typing a username...',
            'noChoicesText': '...',
            'itemSelectText': '',
            'searchFloor': 2,   // triggers search on 3 or more characters
            'shouldSort': false,
        });

        var lookupTimeout = null;

        goog.events.listen(newElem, 'search', function(event) {
            clearTimeout(lookupTimeout);
            lookupTimeout = setTimeout(serverLookup, 50);
        });

        goog.events.listen(newElem, 'choice', function(event) {
            // clear choices in the menu
            choices['setChoices']([], 'id', 'text', true);
        });

        var serverLookup = function() {
            utils.ajax.post('/api/userlookup', {'q': choices['currentValue']}, function(event) {
                var results = JSON.parse(event.target.getResponse());
                choices['setChoices'](results, 'id', 'text', true);
            });
        }

So if I  want to send a message to "SuperLongUsername" I type "sup" and can then select from a relatively short list of elements, before moving on to the next recipient. The list of recipients of a message should not include duplicates, but if I type "sup" a second time I can select "SuperLongUsername" a second time, in spite of the duplicateItems config.
A hacky workaround could scan through choices.currentState.items before the call to setChoices and remove any existing elements from the server response.

A bit of digging suggests this is because the duplicateItems config option is only checked in _canAddItem if the input is a text input.

I made a change in the last release to _canAddItem which may have solved this issue. That said, it sounds like you are after a flag to use when you use setChoices that will clear existing items, right?
That would be a really easy thing to implement if so. Let me know what you think

I don't think that's what I'm after here. Essentially the "problem" case (as seen in v2.7.8) is as follows:

initialize Choices on a multiselect <select> tag with duplicateItems set to false.
select an item.
use setChoices to replace the available options with a new list of options. Have this new list of options include the option that you already selected.
Choices does not prevent you from selecting the same option again.

Issue #162 describes a non-toy use case in which this is apparent. From my digging earlier it seemed like the duplicateItems option doesn't do anything if choices is initialized on a select tag. I'll test to see if the issue is resolved in your latest release tomorrow.

Ahh I see - yeah I can see the problem now. Let me investigate 👍

This should now be resolved as of version 2.8.2!
Let me know if you have any issues


Cors error with IMA sample tag

Hi @Kiro705
I have been testing the plugin with sample tag from https://developers.google.com/interactive-media-ads/docs/sdks/html5/client-side/tags and have observed the CORS error resulting in no playback of the ad
I am attaching a screenshot of the same

Here is the link to the video with the issue https://api.vadoo.tv/landing_page?vid=WK1aotg5SFG0qJRUCwysEa01jdFOh0SI
Any help would be appreciated. Thanks a lot

in your video tag

maybe you can delete 'crossOrigin' attribute and its value, and try again...
please cmiiw
🙏
Sent from Mobile Phone with Love, Flowers, and Gifts -
https://about.me/dioramayuanito
Pada tanggal Min, 26 Sep 2021 7.43 PM, Anil Chandra Naidu Matcha <
@.***> menulis:

Hi @Kiro705 https://github.com/Kiro705
I have been testing the plugin with sample tag from
https://developers.google.com/interactive-media-ads/docs/sdks/html5/client-side/tags
and have observed the CORS error resulting in no playback of the ad
I am attaching a screenshot of the same
[image: sample]
https://user-images.githubusercontent.com/4326215/134808512-2c35612b-fcd4-415b-9e20-0c194fff8a88.png
Here is the link to the video with the issue
https://api.vadoo.tv/landing_page?vid=WK1aotg5SFG0qJRUCwysEa01jdFOh0SI
Any help would be appreciated. Thanks a lot
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/googleads/videojs-ima/issues/1013, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAATWP4TWENZYFLYJDKWM3DUD4IPXANCNFSM5EYYFEDA
.

@dioramayuanito
Thanks for the suggestion. I removed it but it is causing no change https://api.vadoo.tv/landing_page?vid=WK1aotg5SFG0qJRUCwysEa01jdFOh0SI

@dioramayuanito @Kiro705 The issue was bad formatting of url due to the special characters inside the ad tag and is not related to this plugin, so I am closing the issue


Lookout v2 generated files

We tried going without committing generated files to version control. This has proven to be too painful in Go, so made a few changes:

Committing lookoutv2/gen
Removes statik from lookoutv2 in favor of embed.FS
make download now only downloads dependencies
Set sensible default in lookoutingesterv2 config

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@8f576b6). Click here to learn what that means.
 Consider uploading reports for the commit 6305605 to get more accurate results

Additional details and impacted files
@@            Coverage Diff            @@
##             master    #1888   +/-   ##
=========================================
  Coverage          ?   45.04%
=========================================
  Files             ?      187
  Lines             ?    26847
  Branches          ?        0
=========================================
  Hits              ?    12093
  Misses            ?    13891
  Partials          ?      863

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

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


Revert JUnit 5 integration through Test Harness

Test Harness has once more removed the JUnit 5 support.

- not used here -


Soft Bodies

Is there a way to control the soft bodies or add actuation? I want to design soft bodies that can have some sort of movement on their own.

There are a bunch of ways and it depends on your set up, but you can try some combination of the following:

using constraints as pistons by modifying length
setting position or rotation of certain parts as a motor
applying forces
applying velocity

The body manipulation example is a good place to start.
Also check out this awesome paper where the engine was used for something similar so may be helpful: Evolutionary Design of Mechanical Linkages  by Amanda Ghassaei, Joy Ming


更新 jsguide.html期 #656 #658

更新 jsguide.html期 #656 #658
Originally posted by @jiangjifu52 in https://github.com/google/styleguide/issues/656#issuecomment-997473119

Hello, I am interested in contributing to open source projects and would love to participate in any that you have available. I have experience in web Development and am eager to learn and grow my skills through working on these projects. Please let me know if there are any opportunities for me to get involved, I would greatly appreciate it. Thank you!


CB-16477: [In-Place Migration][7.2.12][AWS][mow-int] Restart of services with stale configurations is not issued for when starting OpsDB DH

As the root cause was the auto-start configuration setup for Knox. Just starting the services would not work as the knox service is up even before the RDC refresh is performed.
Changing the logic from just starting the services to restarting the services.
Made sure that the issue is not observed in the local dev environment.

waiting for the fixes for @tiborpopovics comments


Making data local should be a workflow step

Expected behavior
The operation open_dataset should be extended by a force_local: bool = False option and a local_ds_id: str = None.
If force_local == True and ds_id refers to a remote data source, then

local_ds_idis either given or will be set to a new ID which is made up of the ds_id and any given constraints.
if a local data source with ID local_ds_id already exists and is valid, then it will be opened
if a local data source with ID local_ds_id does not yet exist, it will be created by downloading the remote data, then the local version will be opened

If force_local == False the behavior is as it is now.
The new desired behavior is that we want to make the data access part of a workflow so the enclosing workspace can be shared and can run anywhere, regardless of the current state of the user's local data store.
Actual behavior
Local data source must be created before any workflow is created. If a workflow step's open_dataset operation then refers to such a local data source, it cannot be shared without telling how the local data source was named, which remote ID was used, and which constraints have been used to create it.
Specifications
Cate 0.9.0dev3

I fully agree.
Question: what will be the behaviour if the ds is not local and the remote store is not available?

Poff!

I'd like to see this in version 1.0 as this is how Cate should make datasets local in the future. It will also further simplify and clarify data access API, CLI and GUI.

Local data source:

id: generate a 32-digit hash from remote-ID, spatio-temporal constraints, variable names
title: title field of remote DS (if any, otherwise use remote ID) plus any spatio-temporal constraints, variable names in clear text

Remember to keep (or at least recognize) the local. ID prefix as current code is making use of it.

Remember the requirements for the data source ID:

it must be unique in the directory of the local file system
same remote IDs plus same constraints must produce the same local ID

To be discussed: allow local datasets to grow in time.

For ID my suggestion is to combine local prefix,  remote name, constrains hash
local.esacci.GHG.satellite-orbit-frequency.L2.CH4.multi-sensor.multi-platform.VARIOUS.ch4_v1-0.r1.78685637-a631-3eaa-993e-969fa6134da2
And any human-readable description keep in Title.

Made this a blocker because #314 depends on its resolution and is a cu_mandatory


Swift 4 snapshot support

@swizzlr @lgaches I'd thi working now? I tried it a few weeks ago and the key verification was failing

@hamin yes it's working fine for me ( https://hub.docker.com/r/lgaches/docker-swift/ ). I used this image to do some tests.

@lgaches interesting, the fingerprinting wasn't working for me when I tried it and I had to comment that part out. Perhaps they've updated that?

@lgaches thanks for the PR btw :)

FYI @swizzlr @lgaches I just updated /cc DockerHub automated builds. I added latest which would track master branch /cc @mbrandonw


Remove dependency on Echoe gem

Or just figure out how to disable the tasks we don't use...

Done.


[stable/jenkins] Revert direct connection fix in previous version

What this PR does / why we need it:
Fix created for direct connection enabled by default in kubernetes plugin version 1.20.2 is no longer needed (#18410). It was changed upstream to default to disabled in version 1.21.1 https://github.com/jenkinsci/kubernetes-plugin/pull/633
Which issue this PR fixes
Skips setting direct connect to false.
Special notes for your reviewer:
Reverting still causes issues if you happen to install 1.20.2 and using this helm chart. Also, not specifying the option at all makes
<directConnection>false</directConnection>

being injected to config.xml with each pod start without being handled by helm chart.
I don't think it's possible to configure this option via JCasC atm either.
Alternative would be to keep it but also adding the option if latest version of kubernetes plugin is specified, since it caused issues with semver comparison.
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @torstenwalter

/ok-to-test

/retest

/retest

Ping @torstenwalter - we need to get this in since the added semVer compare causes various issues for people...
Sorry for the noise.

@bergemalm Can you rebase it on master?

@bergemalm Can you rebase it on master?

Sure

Done. @torstenwalter

/lgtm

@mogaal @maorfr could you please review? :D

/retest

@bergemalm GitHub is still complaining about conflicting CHANGELOG file.

@bergemalm GitHub is still complaining about conflicting CHANGELOG file.

Yes, well another version of this chart was merged. Updating again...

Rebased again. @torstenwalter

/ok-to-test

/lgtm


[BUG] Service Bus is not annotated for nullability

Library name and version
Azure.Messaging.ServiceBus 7.17.3
Describe the bug
The ContentType property of the ServiceBusReceivedMessage class is not declared as nullable but it can be null.
Expected behavior
The ContentType property should be declared as nullable.
public string? ContentType { get; set; }

Actual behavior
The ContentType property is not declared as nullable.
public string ContentType { get; set; }

Reproduction Steps
var message = await _receiver.PeekMessageAsync(123);
if (message.ContentType.StartsWith("application/"))
{
}

Environment
.NET 8.0.200

Hi @vanillajonathan.   Thank you for reaching out and we regret that you're experiencing difficulties.  The Service Bus client library is intentionally not annotated for nullability.  Nullable reference annotations are something that we continue to evaluate for Azure SDK packages as the language and tooling evolves, but not something that we'll be enabling in the short term. There are several reasons for this, the most important being:

The Azure SDK strives to have a consistent set of patterns and feel across different libraries. As such, nullable reference annotations are not something that would be applied to individual libraries; it would be a decision that we need to apply to all of our current generation packages.

For most of our libraries, the service definitions do not adequately document which fields may be null. We continue to work with our service partners to improve these definitions, but it's a large effort that we expect to continue for some time.

Tooling still doesn't provide a thorough understanding of what breaking changes would be introduced by enabling nullable reference annotations. Avoiding breaking changes is one of the most important core tenants of the current Azure SDK generation; until we have confidence that we can prove that nullable reference annotations are safe for the public APIs that they were added to, the risk outweighs the reward.

Additional rationale and discussion can be found in #8880.

/unresolve That issue is several years old. Now is new times so it ought to be reconsidered.
This caused a bug for me and having the library annotated for nullability would improve the developer experience and reduce downstream bugs.
The Azure SDK would continue to be consistent across different libraries even with nullability since the API and behavior would remain the same. Nullability is just a compiler hint.

Adding nullability to an existing API that has been released is considered a breaking change and is not something that we would be adding in the current form.  To avoid inconsistencies, we do not currently have plans to annotate new members in existing libraries.   We are continuing to monitor changes in the .NET ecosystem and tooling and should a path become available to introduce annotations in a non-breaking way, we may reconsider at that point.   At present, this is not something that we will be adding.


Please guide me on a feature

I need to enable href and target for a image component in the component settings of a image element, please guide me on how to set please, best regards

You can update the image component with your traits and logic, read more about it here


Introduce weights for distance computation during ranking of configurations

When ranking configurations, it would be nice to allow setting weights for CartesianProductWeighted distance metric.

Addressed by #484


Add integration test for elasticsearch

https://github.com/spring-projects/spring-data-elasticsearch/blob/main/src/test/java/org/springframework/data/elasticsearch/junit/jupiter/SpringIntegrationTest.java
https://www.testcontainers.org/modules/elasticsearch/ (referenced by https://stackoverflow.com/questions/67801883/how-to-do-spring-data-elastic-search-integration-tests)
https://github.com/spring-projects/spring-data-elasticsearch/blob/main/src/test/java/org/springframework/data/elasticsearch/core/LogEntityTests.java

CityIntegrationTest with testcontainers is added , but not finished.

there's a new @DataElasticsearchTest annotation -> see https://docs.spring.io/spring-boot/docs/current/reference/html/features.html#features.testing.spring-boot-applications.autoconfigured-spring-data-elasticsearch


Fix Sphinx documentation

Description
Fixes all broken Sphinx doc + update with new structure
Type of change
Please check the options that are relevant.

[ ] Bug fix (non-breaking change that fixes an issue)
[ ] Proposes a change (non-breaking change that isn't necessarily a bug)
[ ] Refactor
[ ] New feature (non-breaking change that adds a new functionality)
[ ] Breaking change (fix or feature that would break some existing functionality downstream)
[ ] This is a unit test
[x] Documentation only change
[ ] Datasets Release
[ ] Models Release

Type of requested review

[ ] I want a thorough review of the implementation.
[x] I want a high level review.
[ ] I want a deep design review.

Checklist:

[x] I have performed manual end-to-end testing of the feature in my environment.
[ ] I have added Docstrings and comments to the code.
[ ] I have made changes to existing documentation where needed.
[ ] I have added tests that show that the PR is functional.
[ ] New and existing unit tests pass locally with my changes.
[ ] I have added relevant collaborators to review the PR before merge.
[ ] [Polymetis only] I ran on hardware (1) all scripts in tests/scripts, (2) asv benchmarks.

Codecov Report

Merging #981 (530116f) into main (c107ff5) will decrease coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #981      +/-   ##
==========================================
- Coverage   33.24%   33.16%   -0.09%
==========================================
  Files         347      346       -1
  Lines       34289    34045     -244
==========================================
- Hits        11399    11290     -109
+ Misses      22890    22755     -135

Impacted Files
Coverage Δ

lowlevel/minecraft/pyworld/physical_interfaces.py
78.98% <0.00%> (-1.92%)
:arrow_down:

task/task.py
86.36% <0.00%> (ø)

perception/robot/perception.py
58.57% <0.00%> (ø)

agents/droidlet_agent.py

interpreter/craftassist/tasks.py
74.63% <0.00%> (+0.18%)
:arrow_up:

agents/_agent.py
51.57% <0.00%> (+7.72%)
:arrow_up:


refactor: collapse TransactionError variants

Duplicate error variant - if we need to know if the error happened during unwind or execution, we should add appropriate traces for it instead. Not sure where it is possible for the error variant to be either unwind/execute as to be ambigious, so this might not make sense to remove. Open to suggestions

Codecov Report

Merging #2738 (c60133a) into main (defa64b) will decrease coverage by 53.86%.
The diff coverage is 0.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##             main    #2738       +/-   ##
===========================================
- Coverage   71.36%   17.51%   -53.86%
===========================================
  Files         504      504
  Lines       65514    65514
===========================================
- Hits        46755    11475    -35280
- Misses      18759    54039    +35280

Flag
Coverage Δ

integration-tests
17.51% <0.00%> (-0.01%)
:arrow_down:

unit-tests
?

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

Impacted Files
Coverage Δ

crates/storage/provider/src/transaction.rs
0.00% <0.00%> (-89.90%)
:arrow_down:

... and 355 files with indirect coverage changes

@rkrasiuk The block_number for those errors is the target block number? Surely it should be the block where the state root is invalid instead?

there is no way to figure out at which block the state root fails without performing additional computation. hence we log the target block for the state root calculation


Visual hints should be provided in a specific order: country's outline, location, and flag.

07a9c58fbdc94349d68f9a6c5d9b2fbdecd17a77


Shared volumes within containers are getting corrupted.

When mounting a shared volume within two images
php:
  image: php:fpm-alpine
  container_name: php
  volumes:
    - .:/var/www

gulp:
  build: .
  dockerfile: ./build/docker/gulp/Dockerfile
  container_name: gulp
  volumes_from:
      - php
  entrypoint: top -b

when i update from gulp the file on /var/www/test.css for example the change got reflected on the host machine, however not in php container.
actually at this point something really weird start happening, these characters start appearing on all over the file "���������....."
if i delete the file /var/www/test.css and create again with the new content, then no issues.
Client:
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   20f81dd
 Built:        Thu Mar 10 21:49:11 2016
 OS/Arch:      darwin/amd64

Server:
 Version:      1.11.1
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   5604cbe
 Built:        Wed Apr 27 00:34:20 2016
 OS/Arch:      linux/amd64

Containers: 3
 Running: 0
 Paused: 0
 Stopped: 3
Images: 30
Server Version: 1.11.1
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 127
 Dirperm1 Supported: true
Logging Driver: json-file
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 4.4.8-boot2docker
Operating System: Boot2Docker 1.11.1 (TCL 7.0); HEAD : 7954f54 - Wed Apr 27 16:36:45 UTC 2016
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 995.9 MiB
Name: ubuntu
ID: IAII:URKY:RGHO:H4UG:BB3N:LMXI:6FJM:DZRX:2GKT:N3RB:5BNR:5LW7
Debug mode (server): true
 File Descriptors: 28
 Goroutines: 86
 System Time: 2016-06-02T10:33:20.145533786Z
 EventsListeners: 0
 Init SHA1:
 Init Path:
 Docker Root Dir: /mnt/sda1/var/lib/docker
Username: rmilewski
Registry: https://index.docker.io/v1/
Labels:
 provider=virtualbox

looks like the solution lies here: https://frankooh.wordpress.com/2011/01/21/vboxsf-and-small-files/

Please provide the output of docker info.

@unclejack sorry, updated my post

i found the reason, actually the problem was with my http server. the answer lies here: https://frankooh.wordpress.com/2011/01/21/vboxsf-and-small-files/

i am using a virtual machine (vbox) as a webserver and connect both via shared folders, so i do not need to set up smb/nfs/sshfs or anything else. that way i can work with my ide on the webserver, but do not have one installed on my laptop. but there seems to be a problem with small files (about 2KB), e.g. .css-files. the apache delivers after small changes a css file, but not the modifed one. it is an old version with the same length of the new, although the length is like the new one and the timestamp is also renewed. so if your new .css-file is smaller then the old one, it has a padding of zeros. there is a workaround to add EnableSendfile Off and EnableMMAP Off into the apache.conf.


Implement usage-summary query

Abax recently added a new query to their API, which is not yet covered in the official documentation.
This is what it looks like:
Url: "/v1/vehicles/{vehicle-id}/usage-summary?from=<datetime>&to=<datetime>
Response:
{
 "PrivateUsageSummary: {
   int32 DistanceDrivenInMeters,
   int32 TotalTollStationsPassed
  },
 "CorporateUsageSummary: {
   int32 DistanceDrivenInMeters,
   int32 TotalTollStationsPassed
  }
}

This query will be expanded with further functionality in the future.

Fixed in #77


proposal: x/net/nettest: add MakeLocalPipe to construct local listener and connections

I'm currently implementing my own net.Conn type and am working on tests using nettest.TestConn: https://godoc.org/golang.org/x/net/nettest#TestConn.
The nettest.MakePipe function provides adequate functionality for my needs, but a fair amount of boilerplate is required to create a nettest.MakePipe that can:

set up a local net.Listener
dial and point a net.Conn at the listener
do appropriate cleanup and error handling

As it turns out, there's a pretty useful function to make a local pipe in one of the tests: https://go.googlesource.com/net/+/refs/heads/master/nettest/conntest_test.go
I propose we generalize and export this function for use with net.Listener and net.Conn implementations of any type. I'm happy to accept name suggestions, but my proposed signature and WIP documentation is as follows:
// MakeLocalPipe creates a local net.Listener and points another net.Conn at the
// listener, producing a MakePipe function suitable for use with TestConn.
//
// The listen function should produce a net.Listener, but should not invoke Accept or
// any other methods on the listener. The dial function receives the address of the
// listener, and should produce a net.Conn pointed at the listener. If dial is nil,
// net.Dial will be invoked with the network and address information from addr.
func MakeLocalPipe(
    listen func() (net.Listener, error),
    dial func(addr net.Addr) (net.Conn, error),
) nettest.MakePipe

Usage is as follows:
Producing a local pipe with a TCP listener and connection, using net.Dial as a default dial function.
nettest.TestConn(t, nettest.MakeLocalPipe(
    func() (net.Listener, error) {
        return net.Listen("tcp", ":0")
    },
    // dial: net.Dial(addr.Network(), addr.String())
    nil,
))

Producing a local pipe with a custom listener and connection implemented outside of the stdlib (https://github.com/mdlayher/vsock)
nettest.TestConn(t, nettest.MakeLocalPipe(
    func() (net.Listener, error) {
        return vsock.Listen(0)
    },
    func(addr net.Addr) (net.Conn, error) {
        a := addr.(*vsock.Addr)
        return vsock.Dial(a.ContextID, a.Port)
    },
))

I don't mind putting this code in my own repository or similar if deemed unnecessary, but it seems like this would be an appropriate addition to nettest, since it enables easy setup of scaffolding for use with nettest.TestConn.
/cc @dsnet @mikioh

Spoke with @acln0 and we came up with a possible alternative API that would have similar semantics, but would enable future extensibility as well. Something along the lines of:
type LocalPipe struct {
    // Same semantics, cannot be nil.
    Listen func() (net.Listener, error)

    // Same semantics: if nil, use net.Dial.
    Dial func(addr net.Addr) (net.Conn, error)

    // Room future extensibility, like perhaps:
    // If not nil, called to clean up any artifacts produced by the net.Listener, e.g.
    // UNIX socket files.
    // Cleanup func(l net.Listener) error
}

// MakePipe produces a MakePipe function using the configuration defined on LocalPipe.
func (lp *LocalPipe) MakePipe() nettest.MakePipe {}

However, we aren't sure that the extensibility would ever be needed.
I think it makes sense to keep the UNIX socket cleanup logic from the original test if net.Listener.Network() is "unix" or "unixgram".  I think it also makes sense to require the caller to deal with cleanup of any other socket artifacts from unknown families on their own.

I am in favor of this proposal. Having implemented this particular scaffolding logic in a number of different places already, it would be pleasant to have a canonical home for it.
With the alternative struct-based construction @mdlayher mentioned, perhaps a direct method is nicer:
func (lp LocalPipe) MakePipe() (c1, c2 net.Conn, close func(), err error)

Then, caller code makes use of the method value like so:
package vsock_test

func TestConn(t *testing.T) {
	vsocklp := netttest.LocalPipe{
		Listen: func() (net.Listener, error) {
			return vsock.Listen(0)
		},
		Dial: func(addr net.Addr) (net.Conn, error) {
			a := addr.(*vsock.Addr)
			return vsock.Dial(a.ContextID, a.Port)
		},
	}
	nettest.TestConn(t, vsocklp.MakePipe)
}

Thoughts, @mikioh?

Once @mikioh and @mdlayher agree here, this can be accepted.

Ping, @mikioh and @mdlayher.
Note that the crypto/tls package tests had what amounts to a copy of the nettest/conntest_test.go TestTestConn body, and we had some reliability problems with it on some systems. I submitted a few CLs to deflake tests (https://golang.org/cl/184157), by not assuming that every dial would succeed. I don't know if that's necessary in general, but if it is then that may influence the API design.

I'm happy to submit the code I have been using for this. I haven't heard anything from @mikioh in a while.
I can't say I've run into tests which sometimes fail to dial, but assuming both of my proposed hook functions continue to return errors, I wouldn't be opposed to adding a retry mechanism.


WebAssembly Support

2548c5e The main change of this PR adds WebAssembly/WASI variant as platform.
6d16075 This change is necessary to make swift-autolink-extract work.
For wasm target, swift-autolink-extract try to extract info from swiftmodule. But without target argument, compiler emits module as Mach-O format on macOS which is not supported by swift-autolink-extract. So SwiftPM need to pass target option when emitting swiftmodule.

This is a part of SR-9307 and #24684.

LGTM, thank you for working on this! I just have one minor comment about the availability of the new API.

@swift-ci smoke test

Sorry, I fixed test cases to fit this change 🙏

@swift-ci smoke test

I'm not sure why the smoke test on Linux failed 🤔
It seems to fail while building test suites. Is this related to cache?

@swift-ci smoke test linux

Passed 🎉


Certificate requirement

Doesn't this app require a  X.509 certificate to obtain app-only access token?

  That can be used in place of the X.509 certificate for the app-only call.
The sample provided on the documentation site, shows the call to get the app-only auth token via a POST like this:
// Line breaks are for legibility only.
POST /{tenant}/oauth2/v2.0/token HTTP/1.1
Host: login.microsoftonline.com
Content-Type: application/x-www-form-urlencoded
client_id=535fb089-9ff3-47b6-9bfb-4f1264799865
&scope=https%3A%2F%2Fgraph.microsoft.com%2F.default
&client_secret=qWgdYAmab0YSkuL1qKv5bPX
&grant_type=client_credentials
https://developer.microsoft.com/en-us/graph/docs/concepts/auth_v2_service

@lousimonetti
I had used token endpoint (available in azure portal after app registration) for getting the access token.
Unfortunately, the screenshots in the documentation do not match with actual sites which makes the work difficult.
Thanks for responding.


[BREAKINGCHANGE] TimeSeriesValueTuple null supported, connect_nulls option added

Updates to allow time series queries to return null values. Summary for changelog:

[BREAKINGCHANGE] TimeSeriesValueTuple value now accepts null
[FEATURE] Support connect_nulls option in time series panel
[BUGFIX] Do not show nulls as zero in tooltip

Examples
Recording (new panel option)
https://user-images.githubusercontent.com/9369625/221610277-e1eadd61-ba1e-467c-8811-06217b1ec61b.mp4
Screenshots
connect_nulls false ex:

connect_nulls true ex:

Checklist

[x] Pull request has a descriptive title and context useful to a reviewer.
[x] Pull request title follows the [<catalog_entry>] <commit message> naming convention using one of the following catalog_entry values: FEATURE, ENHANCEMENT, BUGFIX, BREAKINGCHANGE, IGNORE.
[x] All commits have DCO signoffs.
[x] Changes that impact the UI include screenshots and/or screencasts of the relevant changes.

points on the graphs will be more important now if the lines are not connected

Yeah that makes sense, as we discussed offline, I'm going to add a panel option to force points to show


detect authors urls and add to url list

detect authors urls and add to url list

Many thanks, @fromcouch!
Minor linting fail in the GitHub Actions:
> vendor/bin/phpcs --standard=./tools/phpcs.xml --ignore=*/tests/phpstan/*,*/admin/*,**/coverage/*,*.js,*/vendor/*,*/views/*.php ./

FILE: /home/runner/work/wp2static/wp2static/src/DetectAuthorsURLs.php
----------------------------------------------------------------------
FOUND 4 ERRORS AFFECTING 1 LINE
----------------------------------------------------------------------
 18 | ERROR | [x] No space after opening parenthesis is prohibited
 18 | ERROR | [x] No space before closing parenthesis is prohibited
 18 | ERROR | [x] Expected 1 space(s) after closing parenthesis;
    |       |     found 0
 18 | ERROR | [x] Space between opening control structure and closing
    |       |     parenthesis is required
----------------------------------------------------------------------
PHPCBF CAN FIX THE 4 MARKED SNIFF VIOLATIONS AUTOMATICALLY
----------------------------------------------------------------------

You may be able to run composer phpcbf to automatically fix those.
Please let me know if any issues getting those tests to pass and will assist.
Cheers,
Leon

Done @leonstafford


fix: negotiate contract definition with validity

What this PR changes/adds
Fixes the contract validity failure and the related timing issue.
Why it does that
Contract negotiation fails when the validity doesn't match with contract offer definition validity.
Further notes
Linked Issue(s)
Closes #2648 and #2657
Checklist

[x] added appropriate tests?
[x] performed checkstyle check locally?
[x] added/updated copyright headers?
[x] documented public classes/methods?
[x] added/updated relevant documentation?
[x] assigned appropriate label? (exclude from changelog with label no-changelog)
[x] formatted title correctly? (take a look at the CONTRIBUTING and Etiquette for pull requests for details)

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

Comparison is base (1000488) 64.60% compared to head (66df5cc) 64.61%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2679   +/-   ##
=======================================
  Coverage   64.60%   64.61%
=======================================
  Files         923      923
  Lines       18919    18922    +3
  Branches     1146     1146
=======================================
+ Hits        12223    12226    +3
  Misses       6247     6247
  Partials      449      449

Impacted Files
Coverage Δ

...iation/ConsumerContractNegotiationManagerImpl.java
92.76% <100.00%> (ø)

...iation/ProviderContractNegotiationManagerImpl.java
92.36% <100.00%> (ø)

...ctor/contract/offer/ContractOfferResolverImpl.java
100.00% <100.00%> (ø)

...ract/validation/ContractValidationServiceImpl.java
71.62% <100.00%> (ø)

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

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

@bscholtes1A Can you take a look at this as it resolves a few issues we have run across with contract validity?


Multiple actors per stakeholder

A stakeholder, like an energy supplier, can be different actors, like Eneco, Vattenfall, etcetera. To be able to specify this would give new opportunities for calculating business cases more in detail.

Transfering the issue from me to @MarjoleinSchwachofer


Drop Luc Perkins as Dockerfile maintainer

Luc no longer works for the CNCF. Drop the maintainer label on our container images.

/lgtm

Not a change to the live site
/approve


Youtube Cast didn't work for me

i installed RasberryCast for RasperryPi2 and cast feature didn't work either from web or mobile remote interface.
and i get these logs :
08-15 16:44:00 - DEBUG - Received URL to cast: https://www.youtube.com/watch?v=IIJ30SVJwuQ 08-15 16:44:00 - DEBUG - No subtitles for this stream 08-15 16:44:00 - INFO - Extracting source video URL... 08-15 16:44:00 - DEBUG - Parsing source url for https://www.youtube.com/watch?v=IIJ30SVJwuQ with subs :False 08-15 16:44:00 - ERROR - ERROR: no suitable InfoExtractor for URL https://www.youtube.com/watch?v=IIJ30SVJwuQ 08-15 16:44:00 - ERROR - Result is none, returning none. Cancelling following function. 08-15 16:44:00 - DEBUG - Full video URL fetched. 08-15 16:44:00 - INFO - Starting OMXPlayer now. 08-15 16:44:00 - INFO - Playlist empty, skipping.

Hi,
Could you try with another video? Like this one : https://www.youtube.com/watch?v=p3q5zWCw8J4
Also, could you try replacing https with http?
The error seems to come from youtube-dl, although I don't know why it doesn't works.
Also you can try to reinstall youtube-dl on your pi:
sudo pip uninstall youtube-dl
sudo pip install youtube-dl

Thank you for your response vincelwt
i fixed this issue by reinstalling youtube-dl but i get another issue.
08-15 23:24:13 - DEBUG - Remote page requested. 08-15 23:24:17 - DEBUG - Received URL to cast: https://www.youtube.com/watch?v=aMIESSL6W60 08-15 23:24:17 - DEBUG - No subtitles for this stream 08-15 23:24:17 - INFO - Extracting source video URL... 08-15 23:24:17 - DEBUG - Parsing source url for https://www.youtube.com/watch?v=aMIESSL6W60 with subs :False 08-15 23:24:17 - DEBUG - [youtube] aMIESSL6W60: Downloading webpage 08-15 23:24:18 - DEBUG - [youtube] aMIESSL6W60: Downloading video info webpage 08-15 23:24:18 - DEBUG - [youtube] aMIESSL6W60: Extracting video information 08-15 23:24:19 - DEBUG - [youtube] aMIESSL6W60: Downloading js player en_US-vflduS31F 08-15 23:24:21 - WARNING - "id" field is not a string - forcing string conversion 08-15 23:24:22 - DEBUG - CASTING: Youtube link detected, extracting url in maximal quality. 08-15 23:24:22 - ERROR - Error in launchvideo function or during downlading the subtitles 08-15 23:24:22 - ERROR - 'url' Traceback (most recent call last):   File "./server.py", line 79, in stream     launchvideo(url, False)   File "/home/pi/RaspberryCast/process.py", line 15, in launchvideo     out = return_full_url(url, sub)   File "/home/pi/RaspberryCast/process.py", line 71, in return_full_url     return video['url'] KeyError: 'url'


[azure-template-cpp] publish version 1.0.0-beta.1448524

Update vcpkg ports for Azure SDK release. This release may contain multiple ports.

Adding azure-template to release
cc: @danieljurek, @weshaggard