text:
Verbose crash in Python

Using the library in Python throws an exception when I create a YoutubeDL object with 'verbose'=True as option param and I use the download method (also checked with other methods and same result).
ydl_opts = {
        'format': 'bestaudio/best',
        'postprocessors': [{
            'key': 'FFmpegExtractAudio',
            'preferredcodec': 'mp3',
            'preferredquality': '192',
        }],
        'outtmpl': dst,
        'verbose': True
    }

ydl=youtube_dlc.YoutubeDL(ydl_opts)
ydl.download([url])

I get the exception;
python  : 'str' object has no attribute 'write'

The problem was related to the Kivy library. The utils.write_string method uses sys.stderr for printing all messages, but the kivy library creates a special system environment. I solved this, printing in console directly.
I edited utils.write_string method as follows:
def write_string(s, out=None, encoding=None):
    if out is None:
        out = sys.stderr
    assert type(s) == compat_str

    if sys.platform == 'win32' and encoding is None and hasattr(out, 'fileno'):
        if _windows_write_string(s, out):
            return

    if ('b' in getattr(out, 'mode', '')
            or sys.version_info[0] < 3):  # Python 2 lies about mode of sys.stderr
        byt = s.encode(encoding or preferredencoding(), 'ignore')
        out.write(byt)
    elif hasattr(out, 'buffer'):
        enc = encoding or getattr(out, 'encoding', None) or preferredencoding()
        byt = s.encode(enc, 'ignore')
        if type(out.buffer) == str:
            print(s)
            out.write(s)
        else:
            out.buffer.write(byt)
    else:
        out.write(s)
    out.flush()

license: Unlicense


text:
Implements the Schrödinger-Föllmer algorithm.

See this:
https://github.com/blackjax-devs/blackjax/issues/601

I dont know about this algorithm so I will just assume Adrian you know what you are doing haha

source: gharchive/pull-request

repo: blackjax-devs/blackjax

license_type: permissive

license_source: bigquery


text:
🛑 BlackPirateX Cloudflare Mirror is down

In 775b7a8, BlackPirateX Cloudflare Mirror (https://mirror2.blackpiratex.com) was down:

HTTP code: 404
Response time: 164 ms

Resolved: BlackPirateX Cloudflare Mirror is back up in 938a4fe.

source: gharchive/issue

repo: blackpirateapps/uptime

license: MIT

license_source: github-api


text:
🛑 Barker is down

In 8f5c56d, Barker (https://barker.wemiller.com/) was down:

HTTP code: 502
Response time: 334 ms

Resolved: Barker is back up in f1b5365 after 30 minutes.

repo: blaineam/statussi


text:
Update Hangman Game Template

Update Button/UI Structure
Utilize the Theme System for the Button/UI
Add You Won, or You Lost Screen for when a Game is over, that will take you back to the Lobby List to find a New Game

This will also Refresh the List
Create Settings Menu
Add Mute Button
Add Global Volume Slidebar
Add UI Volume Slidebar
Create Scrolling Credits Menu with Json (Name, Title, Url)
Add Blazium Logo/Branding to the Template
Basic UI Sfx
Basic Music (Main Menu, Lobby List, Hangman Game, Win/Lose Screen)

I would like to add:

Removing the password CheckButton. The text of password should be by default enabled, and if you type anything, it just gets a password to the lobby.
Max Players -> LineInput as well, instead of using Label. Ofc gotta filter for numbers but that's easy.

authors: Bioblaze TheYellowArchitect

repo: blazium-engine/example-game-hangman


text:
Added blue-theme

Added ocean theme, proposed in #34

@blenderskool can you please review this ?

repo: blenderskool/untab


text:
Clearing array by .length= 0 not working

Hi I'm using your fork in a project (thanks!) and I found out that setting the length to 0 of an array kills bindings and does not update the view.
See: https://jsfiddle.net/qx5091vd/2/
Is this something that can be implemented or is using one of the array methods the only way to go?

Its a limitation. See vue docs https://vuejs.org/v2/guide/list.html#Caveats
Vue uses a similar techniq

Thanks for the info!

authors: blikblum naranjamecanica

repo: blikblum/rivets


text:
Pathing module settings don't get disposed when the module is disabled.

REF: https://discord.com/channels/531175899588984842/534492012263636992/886839303370579989

Resolved in v0.12.2.

repo: blish-hud/Pathing


text:
Adds coinbase-wallet-sdk

Description

Adds support for the updated coinbase-wallet-sdk and deprecates walletlink.
Checked against locally run demo:

Checklist

[x] The version field in package.json is incremented following semantic versioning
[x] The box that allows repo maintainers to update this PR is checked
[x] I tested locally to make sure this feature/fix works
[ ] This PR passes the Circle CI checks

@erin-at-work Let us know when this is ready for review!
Closes #885

@aaronbarnardsound This is now updated, checked & ready for review! LMK of any changes!

Hey @erin-at-work, this looks great and everything works as expected, thanks for the PR! I was thinking we could simplify/shorten the naming so that the folder name is just packages/coinbase and the module name would be @web3-onboard/coinbase. What do you think?
Also if we could update the demo package so that it uses the new Coinbase package instead of the deprecated WalletLink package that would be great.

Hey @erin-at-work, this looks great and everything works as expected, thanks for the PR! I was thinking we could simplify/shorten the naming so that the folder name is just packages/coinbase and the module name would be @web3-onboard/coinbase. What do you think?

Made the update!

Also if we could update the demo package so that it uses the new Coinbase package instead of the deprecated WalletLink package that would be great.

Maybe it should be done on a followup PR after the package is published?

Maybe it should be done on a followup PR after the package is published?
Yeah good point, that would probably best.
Thanks for making those naming changes. One last thing we need to do is to increment the version on the WalletLink package so that those changes get published to a new version and then we are good to go.

One more thing, could you please remove the yarn.lock file that is in the packages/coinbase folder. Since it is a monorepo, the yarn.lock lives at the root.

Actually I can do that, so all good.

Actually I can do that, so all good.

Sorry I missed this.. Thank you! 🙏

authors: aaronbarnardsound erin-at-work


text:
possible bug

There is a possible mismatch between the origins of coordinates used by scatter/line objects and by
the brush tool.
In the picture attached the green square has coordinates: (0,0), (0,1000), (50,0), (50,1000).
The reddish rectangle below is area selected by brush. Coordinates of its lower left and upper right corners are shown between square braces. One can see that y-coordinates have positive values while they are expected to be negative (lower than y-coordinates of our "non-negatively defined" rectangle).
Any ideas on what is going on?

Hi @sergeyfridrikh, are the scales of the green rectangle and the Brushselector the same?

@rmenegaux Great question. How do I check for that? From what I can see not only the two scales (in its conventional meaning) are different, but there is a clear off-set between the two frames of reference.

@sergeyfridrikh Did you use pyplot or the object model?

@dmadeka I think it is pyplot.

@dmadeka @rmenegaux Below is the function that draws the plot in question. As well as I can see scatter plot and BrushSelector use the same scales for x-axis as well as for y-axis.

def DisplayDriftPlot(self, plotTypeAreaOrIntensity, selectedChannelData, preproInputAllDictionaryResults, var_max):

    self.plotTypeAreaOrIntensity = plotTypeAreaOrIntensity
    self.channelData = selectedChannelData
    self.preproInputDictionaryResults = preproInputAllDictionaryResults

    scatter_chart_area, x_sc, y_sc, ax_x, ax_y = all_plots.Prepare_Scatter_Plot(
                self.channelData, plotTypeAreaOrIntensity, var_max)

    self.brush_selector = BrushSelector(x_scale = x_sc, y_scale = y_sc, marks = [scatter_chart_area], color = 'red')

    self.db_scat_brush = HTML(value = '[]')

    self.brush_selector.observe(self.brush_callback, names = ['brushing'])

    self.line = Lines(x = [1,2,3],
                      y = [var_max/2., var_max/2., var_max/2.],
                      scales = {'x': x_sc, 'y': y_sc},
                      colors = ['red'],
                      display_legend = False,
                      labels = ['Line chart'],
                      visible = False)

    self.line2 = Lines(x=[0, 1000],
                      y=[0, 0],
                      scales={'x': x_sc, 'y': y_sc},
                      colors=['green'])

    self.line3 = Lines(x=[0, 1000],
                       y=[50, 50],
                       scales={'x': x_sc, 'y': y_sc},
                       colors=['green'])

    self.line4 = Lines(x=[0, 0],
                       y=[0, 50],
                       scales={'x': x_sc, 'y': y_sc},
                       colors=['green'])

    self.line5 = Lines(x=[1000, 1000],
                       y=[0, 50],
                       scales={'x': x_sc, 'y': y_sc},
                       colors=['green'])

    plotTitle = 'Area' if plotTypeAreaOrIntensity is 'area' else 'Intensity'

fig_scat_brush = Figure(marks = [scatter_chart_area, self.line, self.line2, self.line3, self.line4, self.line5],
axes = [ax_x, ax_y],
title = plotTitle + ' - Interactive Scatter Plot',
interaction = self.brush_selector)
    fig_scat_brush = Figure(marks = [scatter_chart_area, self.line],
                            axes = [ax_x, ax_y],
                            title = plotTitle + ' - Interactive Scatter Plot',
                            interaction = self.brush_selector)

    display(VBox([fig_scat_brush]))

Can you check if you get the same behaviour with scalex and scaley.allow_padding set to false (before creating the figure).

authors: dmadeka maartenbreddels rmenegaux sergeyfridrikh

repo: bloomberg/bqplot


text:
node search: environment attributes not available in helper methods

Adding this change to aid in debugging:
diff --git a/lib/cluster-def-gem/lib/cluster_def.rb b/lib/cluster-def-gem/lib/cluster_def.rb
index a37260d..991de0f 100644
--- a/lib/cluster-def-gem/lib/cluster_def.rb
+++ b/lib/cluster-def-gem/lib/cluster_def.rb
@@ -84,6 +84,7 @@ module BACH
         end
         # validate node ids
         if (cluster_def.select{ |row| validate_node_number?(row[:node_id]) == false }).length.positive?  then
+          puts cluster_def
           fail "Retreived cluster data appears to be invalid -- node IDs must be positive integers between 0 and 256 (1..255)"
         end
     end

Currently getting the following error:
d/75-persistent-net-generator.rules", "preferred_disk_drivers"=>["ahci"], "early_command"=>"  udevadm trigger; udevadm settle --timeout=30 ; \\\n  set -- $(vgs --rows --noheadings | head -n 1); \\\n  for vg in \"$@\"; do \\\n    echo Removing volume group $vg \\\n      >> /tmp/early_command.out; \\\n    lvm vgremove -f \"$vg\" \\\n      >> /tmp/early_command.out; \\\n  done; \\\n  for d in `ls /dev/sd[a-z]*`; do \\\n    echo Removing LVM PVs from $d \\\n      >> /tmp/early_command.out 2>&1; \\\n    lvm pvremove -f $d \\\n      >> /tmp/early_command.out 2>&1; \\\n    echo Erasing first blocks on $d \\\n      >> /tmp/early_command.out 2>&1; \\\n    dd if=/dev/zero of=$d bs=64M count=16 \\\n      >> /tmp/early_command.out 2>&1; \\\n  done\n"}, "admin_users"=>[], "interface"=>"eth0", "pxe_interface"=>"eth1", "server"=>"10.0.100.3", "vip"=>"10.0.100.3", "dhcp_range"=>"10.0.100.14 10.0.100.250", "dhcp_subnet"=>"10.0.100.0", "proxy"=>"http://devproxy.bloomberg.com:82", "hostname"=>"bcpc-bootstrap"}
http://10.0.100.3
Retreived cluster data appears to be invalid -- node IDs must be positive integers between 0 and 256 (1..255)
/opt/chef/embedded/lib/ruby/gems/2.3.0/gems/cluster_def-0.1.0/lib/cluster_def.rb:88:in `validate_cluster_def'
/opt/chef/embedded/lib/ruby/gems/2.3.0/gems/cluster_def-0.1.0/lib/cluster_def.rb:112:in `parse_cluster_def'
/opt/chef/embedded/lib/ruby/gems/2.3.0/gems/cluster_def-0.1.0/lib/cluster_def.rb:140:in `fetch_cluster_def_http'
/opt/chef/embedded/lib/ruby/gems/2.3.0/gems/cluster_def-0.1.0/lib/cluster_def.rb:124:in `fetch_cluster_def'
/var/chef/cache/cookbooks/bcpc/libraries/utils.rb:193:in `fetch_all_nodes'
/var/chef/cache/cookbooks/bcpc/libraries/utils.rb:232:in `get_head_nodes'
/var/chef/cache/cookbooks/bcpc/recipes/mysql.rb:219:in `from_file'

node['bcpc']['boostrap']['cluster_def_path'] is not being populated when the URL for the cluster-definition is being generated from the ruby gem class BACH::ClusterDef
made sure the attribute is there in my environment:
knife environment show Test-Laptop
chef_type:           environment
...
json_class:          Chef::Environment
name:                Test-Laptop
override_attributes:
  bcpc:
    bootstrap:
      cluster_def_path: /cluster-def/

got it working. forgot to upload my environment.
oops

repo: bloomberg/chef-bach


text:
Forked Smoke-Tests

Currently tests are serialized so if one fails, all following tests won't even be run. We want to make sure every test is able to be run to test every service. The best way to do this is using fork + join + decision. If one of these fails, it won't goto a fail path and end oozie execution because all fail/success paths goto the join. Once all tests are done, a decision is used to check if lastErrorNode() was populated or not which would indicate whether or not something failed.
Also removed a duplicate line from job properties.

LGTM

LGTM

authors: NinjaLabib bijugs ronny-macmaster


text:
[BUG] Error 280

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

Bloxstrap Version
v2.8.1
What problem did you encounter?

I have never seen a error in Bloxstrap, how to fix it?
Bloxstrap Log
N/A

Enable "Fresh reinstall roblox on next launch" in the Bloxstrap menu, should maybe fix it

dont intentionally downgrade your roblox

repo: bloxstraplabs/bloxstrap


text:
Can't update profile image

Describe your problem
I am trying to update user profile picture and it only set to black, tried other files and checked logs, no luck.
Could only catch this message in DevTools Console:
"Form contains a file input, but is missing method=POST and enctype=multipart/form-data on the form.  The file will not be sent."
The problem doesn't happen on local webserver, once pushed to remote the problem start to occur.
The rest works, content can be created, images can be uploaded to the posts.
Expected behavior
User profile image is updated.
Actual behavior
User profile image goes black.
Steps to reproduce the problem
Go to user profile and attempt to update picture
Bludit version

Bludit Version
3.8.1

Bludit Codename
APA

Bludit Build Number
20190228

Tested this on my own blog based on B3.8.1, and admin img changes without a single problem.
I would double check if it's not a deployment problem from localhost.

Oh my, I did type a comment a while ago and apparently forgot to submit it.
I haven't seen this problem with directly accessed instance however once it was moved behind reverse proxy the problem occurred.
I need to double check that, will add some info later this week.

Check in your browser the dev console when you are uploading the image, if you recevid some error. also the tab network.

Finally, got my hands there.
Confirmed - our reverse proxy messes something up here.
Nothing unusual on Network tab, POST request went normal:
{"status":0,"message":"Image uploaded.","filename":"test.png","absoluteURL":"https:\/\/counself.com\/site\/blog\/bl-content\/uploads\/profiles\/test.png","absolutePath":"\/app\/site\/blog\/bl-content\/uploads\/profiles\/test.png"}
Stay tuned.

In the end it turned out that php worker tried to use ./bl-content/tmp folder for processing uploaded files but the folder wasn't there and it couldn't create it due to lack of permissions and didn't report it anywhere.
That happened as we use docker volume for ./bl-content folder where only root user could create a missing folder.

authors: Joduai dignajar fisklask

repo: bludit/bludit

license: mit


text:
REVM triggers Uniswap reentrancy guard

When trying to make Swap on uniswap using the method swapExactETHForTokensSupportingFeeOnTransferTokens it returns a REVERT UNISWAP V2: LOCKED
There's no loops in my code
Before the revert it stops at PC 19213, the revert being 19215
Some people reported the same error on Hardhat in 2020
Ok(ResultAndState { result: Revert { gas_used: 85902, output: b"\x08\xc3y\xa0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0 \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x11UniswapV2: LOCKED\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0" }

Not revm related as reentrency is purely a bytecode logic

authors: NianSol rakita

repo: bluealloy/revm


text:
Feature Request: Add GitHub Search / Theme / Monospaced Font

Hi!
First of all, thanks for this great extension.
Second, I think it'd be useful to have GitHub as a search provider too, since the extension kinda looks like it could be targeted for tech people (hence the brackets and all...? At least that's what it looks like to me.)
I've actually implemented this locally, so let me know if I should go ahead and submit a PR.
Another thing I thought would be cool, was to have a theme along the lines of "Monokai" or some other color scheme like that, and have the brackets be a different color from the rest (to sort of emulate syntax highlighting).
Also, maybe a monospaced font too (like Roboto Mono for example) ...
Basically to make it look more like a code editor ^_^
Thanks!

Thank you for the suggestions! No need to put in a PR for that, I'll throw that in real quick on the next update since it really doesn't take long to do.
As far as additional fonts and color options, I'll be working on this for a future update and will definitely consider a monospaced font option. :)

Hello, I've just released an update that adds GitHub as a search option. Thank you.

Hi! Thank you for adding this feature.
I can't get it to work tho.
Whenever I select the "GitHub" option, it just behaves like the "Google" option.
It displays "Google" in the input placeholder and the search also goes to Google.
All the other search engines work fine.

Ops, I just noticed there's already an issue on this. #24

Thanks for the report. I hope to get to that this weekend. I swear I tested it first ;)

Seems to be fixed after the last update. Thanks! :)

authors: bluecaret p-realinho

repo: bluecaret/carettab


text:
build schema_validators dict for bluesky issue #1197

A dict 'schema_validators' is constructed of jsonschema.Validator instances. The intention is that this dict be imported by code wanting to validate JSON.
Motivation and Context
This change is in support of using jsonschema>3: https://github.com/bluesky/bluesky/issues/1197.
jsonschema.validate() is currently used in bluesky but has been deprecated. The 'new' method is to extend a jsonschema validator class which takes about 4 lines of code. I suggest putting those 4 lines in event-model and caching one validator for each schema.
How Has This Been Tested?

This looks on track so me so I have gone ahead and marked it as ready for review so that CI will start running against it.
Please update all the places that we use jsonschema.validate , such as https://github.com/bluesky/event-model/blob/54e925915b29fe77c9207887a73c2562dc2f6578/event_model/init.py#L73
to use these validators instead. Please also update the requirements.txt to specify the minimum version of jsonschema that supports this new usage.

I think I have corrected those embarrassing oversights.

Haha, not at all! Very useful PR for Week 3 on the team!

PEP8 compulsion. I was weak.
On Thu, May 23, 2019 at 3:50 PM Maksim Rakitin notifications@github.com
wrote:

@mrakitin approved this pull request.
Looks good to me, thanks @jklynch https://github.com/jklynch!
Left a minor question regarding imports, otherwise good to go.
In event_model/init.py
https://github.com/bluesky/event-model/pull/79#discussion_r287105685:

-all = ['DocumentNames', 'schemas', 'compose_run']
+import jsonschema
+import numpy
Why did those imports moved from their original places?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bluesky/event-model/pull/79?email_source=notifications&email_token=ABCI2RLNPV7RQS3FFNCVHF3PW3YO5A5CNFSM4HOWEV32YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOBZR237I#pullrequestreview-241413629,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABCI2RMAIQQC6VMKR2JKWL3PW3YO5ANCNFSM4HOWEV3Q
.

I don't think we ever really decided whether we would adopt the "builtins, then external libs, then package-local libs" breakdown, but I have heard it argued for and I am happy to adopt it.

Per quick Slack check-in with @mrakitin we are indeed all on the same page that this is a good and reasonable compulsion. Thanks again @jklynch!

I really like it though, as I expressed it some time ago myself. PyCharm normally does it for you "for free" ("Optimize imports" menu or something like that).

authors: danielballan jklynch mrakitin

repo: bluesky/event-model


text:
FooDetector should have a consistent initialiser pattern.

FooDetector is an implementation of StandardDetector, with a FooController (which takes a FooDriver) and a HDFWriter.
class FooDetector(StandardDetector):
    """A Foo StandardDetector writing HDF files"""

    _controller: FooController
    _writer: HDFWriter

    def __init__(<SOME ARGS>):
        self.drv = driver  # Must be child of device to be staged
        self.hdf = hdf  # Must be child of device to be staged

        super().__init__(
            FooController(self.drv),
            HDFWriter(
                self.hdf,
                directory_provider,
                lambda: self.name,
                ADBaseShapeProvider(self.drv),
                **scalar_sigs,
            ),
            config_sigs=config_sigs or (self.drv.acquire_time,),
            name=name,
        )

Each facility has a particular standard (which may be kept to varying degrees of rigour) for how the child component (.drv, .hdf) epics addresses extend the prefix of their parent device.
Diamond also has the particular limitation that our device factory functions (which primarily are init methods, but do not necessarily need to be) must have the args prefix and name.

The current Diamond wrapper function looks like this, with the complexity that some StandardDetector implementations (The Aravis that are used as OAVs, but not those used on the test rigs) have CAM instead of DRV.
def DLSFoo(prefix: str, name: str) -> FooDetector:
    driver = FooDriver(prefix + "DRV:")
    hdf = HDFWriter(prefix + "HDF5:")
    return FooDetector(driver=driver, hdf=hdf)

DLS has no such standards unfortunately...
@DiamondJoseph what do you think about?
def DLSFoo(prefix: str, name: str) -> FooDetector:
    return FooDetector(prefix=prefix, drv_suffix="DRV:", hdf_suffix="HDF:")

In which case we could default to the NSLS-II versions:

class FooDetector:
    def __init__(self, prefix: str, drv_suffix=":cam1", hdf_suffix=":HDF1"):
         ....

Also I would like to make all names optional, defaulting to "" so they can be used with DeviceCollector...

That patttern works for me, happy with those defaults (good argument to push for standardisation later)

I'm happy with @coretl's solution too.
In general when porting DLS stuff we have been trying to adopt PV naming standards and persuade the controls team to change PV names. @DominicOram has had some success in this and I think it's a good strategy going forward, so I think we are allowed to assume we follow a standard. That said the use of globals makes it more difficult to cater for the 1% that do not.
I also think that detectors should look as much like other ophyd devices as possible, which the proposed solution satisfies because name and prefix and the only things you must pass.

I'll put together a change to standardise the detectors we have so far, something for the docs too

In general when porting DLS stuff we have been trying to adopt PV naming standards and persuade the controls team to change PV names. @DominicOram has had some success in this and I think it's a good strategy going forward, so I think we are allowed to assume we follow a standard.

Although we aren't going to make this PV name change as a pre-requisite of adopting ophyd, we must be able to run alongside Malcolm so we will need to do FooDetector(prefix=prefix, drv_suffix="DRV:", hdf_suffix="HDF:") for some considerable amount of time.
Also the NSLS-II conventions are technically against our PV naming conventions, which are all caps, but then all areaDetector PVs are anyway so I'm not sure I care...

That said the use of globals makes it more difficult to cater for the 1% that do not.

My suggestion ditched the globals, you get NSLS-II naming by default, and you have to specify if different. No DLS defaults here...

I also think that detectors should look as much like other ophyd devices as possible, which the proposed solution satisfies because name and prefix and the only things you must pass.

I see no reason to make name required. We have DeviceCollector and soon https://github.com/DiamondLightSource/dodal/issues/483, both of which call set_name after __init__, so I really don't want name to become required anywhere...

Also, just to clarify, I wasn't suggesting we write DLSFoo anywhere, but actually:
@device_factory
def saxs() -> PilatusDetector:
    return PilatusDetector("BL22I-EA-PILAT-01:", drv="DRV:, hdf="HDF:")

@device_factory
def waxs() -> PilatusDetector:
    return PilatusDetector("BL22I-EA-PILAT-02:", drv="DRV:, hdf="HDF:")

Not as DRY as it could be, but at least it's explicit

Why is this required for compatibility with Malcolm?

Why is this required for compatibility with Malcolm?

So we can gradually migrate scans over. Only change one thing at a time.

authors: DiamondJoseph callumforrester coretl

repo: bluesky/ophyd-async


text:
Enh use monitor

This is code notes from a discussion with @prjemian and @danielballan which does to seperate things:

Tell EpicsMotor to automonitor more things (which should drastically speed up mtr.read_configuration()
re-threads EpicsSignal.get(..., use_monitor=True) back through to the control layer layer + sets a per-Signal default (which tracks auto-monitor).

Simple test code with EPICS motor record instance (running in a docker container on the same workstation, BTW): sky:m1
#!/usr/bin/env python3

from ophyd import EpicsMotor
import time

m1 = EpicsMotor("sky:m1", name="m1")
m1.wait_for_connection()
m1.read_configuration()

def test(count=1):
    for _i in range(count):
        m1.read_configuration()

n = 10000
t0 = time.time()
test(n)
dt = (time.time() - t0) / n
print(f"{n} times, {dt*1000:.3f}ms per time")

ophyd origin master
(bluesky_2020_9) prjemian@poof ~/.../Bluesky/ophyd $ git checkout master
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.
(bluesky_2020_9) prjemian@poof ~/.../Bluesky/ophyd $ /tmp/test_automonitor.py
10000 times, 1.611ms per time

ophyd  tacaswell:enh_use_monitor
(bluesky_2020_9) prjemian@poof ~/.../Bluesky/ophyd $ git checkout enh_use_monitor
Switched to branch 'enh_use_monitor'
Your branch is up-to-date with 'tom/enh_use_monitor'.
(bluesky_2020_9) prjemian@poof ~/.../Bluesky/ophyd $ /tmp/test_automonitor.py
10000 times, 0.210ms per time

Convincing!
Is this demo sufficiently robust?  Needs to test at a beam line that experiences a read timeout error (APS 8-ID-I or 9-ID-C).

The speedup is an order of magnitude faster using values cached from CA monitors.

For comparison, test the ophyd.sim.motor simulated motor:
In [1]: from ophyd.sim import motor as m1

In [2]: import time

In [3]: m1.wait_for_connection()
   ...: m1.read_configuration()
Out[3]:
OrderedDict([('motor_velocity', {'value': 1, 'timestamp': 1603820951.6882622}),
             ('motor_acceleration',
              {'value': 1, 'timestamp': 1603820951.6883285})])

In [4]: def test(count=1):
   ...:     for _i in range(count):
   ...:         m1.read_configuration()
   ...:
   ...: n = 10000
   ...: t0 = time.time()
   ...: test(n)
   ...: dt = (time.time() - t0) / n
   ...: print(f"{n} times, {dt*1000:.3f}ms per time")
10000 times, 0.018ms per time

In [5]: m1
Out[5]: SynAxis(prefix='', name='motor', read_attrs=['readback', 'setpoint'], configuration_attrs=['velocity', 'acceleration'])

In [6]:

This is an order of magnitude faster than the CA monitor case.  Why?  SynAxis.get() has a simpler call stack than EpicsMotor.get()?

The speedup is an order of magnitude faster using values cached from CA monitors.

An I suspect you would get an extra order of magnitude if you were talking to an IOC on an actual remote host due to network round-trip times (we have seen 10-20ms read_configuration times on the floor!).

This is an order of magnitude faster than the CA monitor case. Why?

It %prun in IPython should get you a nice line profile, my knee-jerk guess is that even with this change we are still descending into the pyepics call stack where as with SynAxis everything in "soft" signals and does not call deeper than the Ophyd methods.

I can test run with an IOC on a remote host.  Am running a long test on an APS host now.  Next will be to pick either USAXS (more likely) or XPCS (instrument in use by SPEC users now).

@tacaswell The PV read timeout problem happens with EpicsSignal and EpicsSignalRO objects, as well.  Can we make a @classmethod to change the default auto_monitor=True for EpicsSignalBase?

rebased and ready for review.

@danielballan : In time for the 1.6.0 release?

Yes. I hope we’ll tag 1.6.0 Monday. One issue left, plus updating the release notes PR.

authors: danielballan prjemian tacaswell

repo: bluesky/ophyd


text:
Liveview 1.0.0 support

The Liveview 1.0 just got release, but this project doesn’t seem to support it yet.
Could you update the dependencies? Let me know if I can help!
Thanks!

Thanks @DamascenoV, could you pls open a PR

merged #99

authors: DamascenoV bluzky


text:
🛑 ERM4SN-Demo is down

In 11e01c3, ERM4SN-Demo (https://demo.erm4sn.com) was down:

HTTP code: 500
Response time: 8604 ms

Resolved: ERM4SN-Demo is back up in 31146bf after 7 minutes.

repo: bmoers/upptime


text:
java is not compiled with debug info

Hello,
The plugin currently compiles the instrumented java source without debug info [-g:vars].
We are using Spring framework, which can rely on variable names in debug info when autowiring beans.  Adding this plugin to our build causes tests to fail, because Spring can no longer autowire many beans.
Is it possible to compile with java debug info instead?

I believe this can be closed when I finish merging PR#53. I will look at the demo and see if it could be turned into a simple integration test to cover this issue as well.

Merged the PR and added integration tests

authors: Alex-Vol awittig

repo: bmuschko/gradle-clover-plugin


text:
Add recipes for mavros

Hi all,
This pull request is very similar to the work done in https://github.com/bmwcarit/meta-ros/pull/424, but with the differences:

Download tarball instead of checking out a git repository.
The change in config.cmake.in uses what is done in the automatically generated files as reference for setting mavlink_INCLUDE_DIRS variable.
The mavlink files are in fact stored under /opt/ros/indigo, where it should be, based on the Ubuntu distribution. The last time I checked building with that #424, they were conflicting with another mavlink installation (one that goes to the standard locations).
The license checksum variables are set consistently with what has been done in other recipes in this repository.
Build and run dependencies set (although it seems that the current version of #424 apparently has fixed that).

@JochiPochi Your comments on this are very appreciated, since you've been working on this too for a while.
Best regards,
Gustavo Sousa

Oh, the CI check failed because the patch file was missing the Upstream-Status tag. I'll update it.

Just updated the patch file. I just wanted to note that https://github.com/mavlink/mavlink-gbp-release/pull/5 has the patch for fixing patch/config.cmake.in instead of config.cmake.in. As far as I understand, the releases are done automatically with the bloom toll, which supposedly would use patch/config.cmake.in.

good idea on calling this ros-mavlink. I just recently stumbled with it interfeering with the mavlink recipe from https://github.com/koenkooi/meta-uav too. Was that the one you were talking about as well?
Thanks for submitting the PR to the mavlink project, I've been wanting to get rid of needing a patch for some time.
@bulwahn mavlink/mavlink-gbp-release#5  is a ROS Kinetic release but that should work fine for us I think. On that note though, what are the components on meta-ros that make us an indigo release? Since we compile from source does it matter if we grab indigo or kinetic releases for future recipes?

good idea on calling this ros-mavlink. I just recently stumbled with it interfeering with the mavlink recipe from https://github.com/koenkooi/meta-uav too. Was that the one you were talking about as well?

Yep.

Thanks for submitting the PR to the mavlink project, I've been wanting to get rid of needing a patch for some time.

@bulwahn mavlink/mavlink-gbp-release#5 is a ROS Kinetic release but that should work fine for us I think. On that note though, what are the components on meta-ros that make us an indigo release? Since we compile from source does it matter if we grab indigo or kinetic releases for future recipes?

I think another option would be asking them to backport the patch to indigo. But if we can fix on a Kinetic release known for working with Indigo too, then I think we would be fine.

good idea on calling this ros-mavlink

The meta-ros layer is an indigo distribution because the recipes' versions match the provided versions in the distribution.yaml in the indigo directory of the rosdistro repository. This is the place where all ROS package maintainers report new package releases and the ROS core team tests and integrates them. I have a script that checks if the versions in the distribution.yaml file and in meta-ros match and if not creates recipe update git commits automatically. I use this script about once every month to keep meta-ros roughly up to date. Of course, it is no problem for us to decide to make exceptions to that stated above if we consider it to be a better solution. We are our own maintainers and I am pragmatic about such decisions and changes, as long as it is documented somewhere and can be found for later development changes.

I am not a fan of prefixing it with ros- because the layer would contain many duplicate recipes with very similar content. I instead would prefer to maintain a second branch for a second distribution. Users probably do not want to combine recipes of different distribution and the proposed solution would not allow that either compared to maintaining two branches. For maintaining two branches, I want to first get a CI testing set up; this is something on my todo list for a couple months now, and I am slowly progressing on that.

@guludo @JochiPochi If you two have decided on a common pull request, just close the one that would be obsolete and tell me when the other pull request is ready to merge, I will then test building it and then merge it (next week once I am back from vacation).

Hi @bulwahn

I am not a fan of prefixing it with ros- because the layer would contain many duplicate recipes with very similar content.

That makes sense for ros-<distro>- prefixes and your solution with separate branches makes sense. But I don't see how the prefix ros- would cause duplicate recipes.

Oh, I just saw now that there's a create-ros-recipe.py script. I should've seen that before writing patches by hand hehe.

@guludo @JochiPochi If you two have decided on a common pull request, just close the one that would be obsolete and tell me when the other pull request is ready to merge, I will then test building it and then merge it (next week once I am back from vacation).

@JochiPochi Are you okay with using this pull request?

@guludo Tentatively yes. I haven't finished running my mavros tests. I'll inform you asap.
@bulwahn If all the tests pass I'll modify my PR to only include mavros, that way this PR will have to be merged first and #434 second.

Only prefixing with ros might work, but I dislike the resulting names for some standard packages, e.g. roslaunch would be called ros-roslaunch, similar for rostest, rospy and roscpp. So then it seems better to add the ros prefix selectively when there is the possibility of name clashing; that is just as you did for mavlink, and I think that is currently the best solution.

There are actually two scripts for creating recipes by two other authors in the scripts directory; unfortunately both scripts are still far away from perfect and complete. So I also still write all new recipes by hand.

Hey @guludo, All seemed good, I only have two comments:

This PR is missing a recipe for mavros_extras that is part of the tarball. Here's a commit I made to supplement it, feel free to grab it and add it here or modify it accordingly.

Can you be a little bit more verbose on the mavlink recipe commit message on why the patch for mavlink was necessary? Not for me but for the gitlog. The incorrect path is a common problem when writing recipes for wild cmake projects so I just want to make sure that is documented. That was the reason why I separated the mavlink recipe and the patch in separate commits on my PR.

Other than that it's all good, I'll be happy to close #424 and use this one instead once those two points are addressed :) Thanks for picking up the slack I was introducing, I was having trouble finding time to fix the issues with my implementation!

@JochiPochi I'd be happy to cherry-pick that commit here. I just had one comment regarding the dependencies though.

@guludo Here's another commit with a less paranoid dependency list to match the package.xml file

@JochiPochi Thanks for the commit adding mavros_extras! I've added more information on the commit message for ros-mavlink and cherry-picked your commit. Hopefully it's now ready to be merged.

Btw, sorry for the delay on doing the fixes :-)

No worries on the delay.
On the other hand, there is a typo on the commit I told you to cherrypick. I fixed that sometime ago but I forgot to update it here.
I should have sent branch links instead of commit links as that way my force push fixes would have showed. So that's my fault:
Here's the branch: https://github.com/cyphyworks/meta-ros/commits/mavros-extras
Would you mind cherry picking the latest commit from there again please? This time I tested it instead of doing a quick fix :)
As soon as that happens it will be ready for merge in my opinion

@JochiPochi Done :-)

I ran a quick test build with bitbake ros-mavlink mavros mavros-extrason a clean and fresh build environment with this build configuration :
Build Configuration:
BB_VERSION        = "1.32.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "fedora-23"
TARGET_SYS        = "i586-oe-linux"
MACHINE           = "qemux86"
DISTRO            = "nodistro"
DISTRO_VERSION    = "nodistro.0"
TUNE_FEATURES     = "m32 i586"
TARGET_FPU        = ""
meta              = "master:db7799747b263507427e325638353142ae79403c"
meta-oe
meta-python
meta-multimedia   = "master:18d518a03d7d55b69f7ff4b19916c7006220c3e9"
meta-ros          = "guludo-mavros-v2:4abde38c557402f63ad04cb414cb8179eecf2bbe"

Bitbake then fails with:
 CMake Error at /home/lukas/dev/openembedded.org/openembedded-core/build/tmp-glibc/sysroots/x86_64-linux/opt/ros/indigo/share/catkin/cmake/catkinConfig.cmake:83 (find_package):
|   Could not find a package configuration file provided by "tf" with any of
|   the following names:
|
|     tfConfig.cmake
|     tf-config.cmake
|
|   Add the installation prefix of "tf" to CMAKE_PREFIX_PATH or set "tf_DIR" to
|   a directory containing one of the above files.  If "tf" provides a separate
|   development package or SDK, be sure it has been installed.
| Call Stack (most recent call first):
|   CMakeLists.txt:7 (find_package)
|
|
| -- Configuring incomplete, errors occurred!
| See also "/home/lukas/dev/openembedded.org/openembedded-core/build/tmp-glibc/work/i586-oe-linux/mavros-extras/0.17.4-r0/build/CMakeFiles/CMakeOutput.log".
| WARNING: /home/lukas/dev/openembedded.org/openembedded-core/build/tmp-glibc/work/i586-oe-linux/mavros-extras/0.17.4-r0/temp/run.do_configure.7763:1 exit 1 from 'cmake ${OECMAKE_SITEFILE} /home/lukas/dev/openembedded.org/openembedded-core/build/tmp-glibc/work/i586-oe-linux/mavros-extras/0.17.4-r0/mavros-0.17.4/mavros_extras -DCMAKE_INSTALL_PREFIX:PATH=/usr -DCMAKE_INSTALL_BINDIR:PATH=bin -DCMAKE_INSTALL_SBINDIR:PATH=sbin -DCMAKE_INSTALL_LIBEXECDIR:PATH=libexec -DCMAKE_INSTALL_SYSCONFDIR:PATH=/etc -DCMAKE_INSTALL_SHAREDSTATEDIR:PATH=../com -DCMAKE_INSTALL_LOCALSTATEDIR:PATH=/var -DCMAKE_INSTALL_LIBDIR:PATH=lib -DCMAKE_INSTALL_INCLUDEDIR:PATH=include -DCMAKE_INSTALL_DATAROOTDIR:PATH=share -DCMAKE_INSTALL_SO_NO_EXE=0 -DCMAKE_TOOLCHAIN_FILE=/home/lukas/dev/openembedded.org/openembedded-core/build/tmp-glibc/work/i586-oe-linux/mavros-extras/0.17.4-r0/toolchain.cmake -DCMAKE_VERBOSE_MAKEFILE=1 -DCMAKE_NO_SYSTEM_FROM_IMPORTED=1 -DCMAKE_PREFIX_PATH='/home/lukas/dev/openembedded.org/openembedded-core/build/tmp-glibc/sysroots/qemux86/opt/ros/indigo;/home/lukas/dev/openembedded.org/openembedded-core/build/tmp-glibc/sysroots/qemux86/usr;/home/lukas/dev/openembedded.org/openembedded-core/build/tmp-glibc/sysroots/x86_64-linux/opt/ros/indigo;/home/lukas/dev/openembedded.org/openembedded-core/build/tmp-glibc/sysroots/x86_64-linux/usr' -DCMAKE_INSTALL_PREFIX:PATH='/opt/ros/indigo' -DCATKIN_BUILD_BINARY_PACKAGE=ON -DSETUPTOOLS_DEB_LAYOUT=OFF -DCATKIN_ENABLE_TESTING=0 ${PACKAGECONFIG_CONFARGS} -Wno-dev'
| ERROR: Function failed: do_configure (log file is located at /home/lukas/dev/openembedded.org/openembedded-core/build/tmp-glibc/work/i586-oe-linux/mavros-extras/0.17.4-r0/temp/log.do_configure.7763)
ERROR: Task (/home/lukas/dev/github.com/bmwcarit/meta-ros/recipes-ros/mavros/mavros-extras_0.17.4.bb:do_configure) failed with exit code '1'

So it seems some build dependencies where overly optimized away in the recipe.
Here also another remark: As I understand you created these commits together, you might want to add some kind of acknowledgement of that in the commit message. But that is of course up to you two.

Hi @bulwahn,
I'll do a fresh build here and correct the errors. Thanks.

Here also another remark: As I understand you created these commits together, you might want to add some kind of acknowledgement of that in the commit message. But that is of course up to you two.

Yes, of course! I'll do it. In those situations it would be nice if git allowed multiple commit authors.

Yep, the recipes got over optimized indeed. Looks like I had tf build already from a separate program. It is only used for mavros-extras so I added it to my recipe. @guludo once more if you cherrypick the last commit on my branch that should solve the problem. The rest of your recipes are good as they are.
I did scratch builds of just mavros and mavros-extras this time so there should be no compilation error again.

I think that finding some of the mistakes I made through the course of this PR took a lot longer than I wish they did. Do you know of a better way to check that a recipe doesn't use previously build packages on temp if they aren't explicitly cited on the dependency list other than making scratch builds? (They take too long, even on a 10 core machine)
I think I've seen bitbake showing warning about those from time to time but not sure how to make it error on those instead of just go as a warning

Here also another remark: As I understand you created these commits together, you might want to add some kind of acknowledgement of that in the commit message. But that is of course up to you two.

@guludo, I'd be more than happy if the mavros-extras commit is the only one on my name, if you are okay with it. And that should show with the cherrypick, what do you think?

@JochiPochi Great. I was going to test the recipes separately today, but I'll just cherry pick your commit again then. :-)

@bulwahn @JochiPochi's commit re-cherry-picked and previous commits amended to add more accurate authorship information.

I ran bitbake ros-mavlink mavros mavros-extras on a clean and fresh build environment with this build configuration:
Build Configuration:
BB_VERSION        = "1.32.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "fedora-23"
TARGET_SYS        = "i586-oe-linux"
MACHINE           = "qemux86"
DISTRO            = "nodistro"
DISTRO_VERSION    = "nodistro.0"
TUNE_FEATURES     = "m32 i586"
TARGET_FPU        = ""
meta              = "master:dc24d785282eb13521cff084677f49de226c316b"
meta-oe
meta-python
meta-multimedia   = "master:18d518a03d7d55b69f7ff4b19916c7006220c3e9"
meta-ros          = "guludo-mavros-v3:4d18537b4abbc5a8a14a96e57434240fa690642b"

There are no errors and no warnings and I will merge this pull request now. Please close the other open pull request. Thanks a lot.

authors: JochiPochi bulwahn guludo

repo: bmwcarit/meta-ros


text:
feat: Tron support

Description

Issue ticket number and link

Types of changes

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

Checklist

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

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-widget

/qa-deploy:canonical-bridge-widget

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

/qa-deploy:canonical-bridge-ui

repo: bnb-chain/canonical-bridge


text:
Add hyperterm-chester-dark theme

Checklist:

[x] The title for my package or theme uses its npm title (hyperterm-plugin-example)
[x] The link for my package or theme uses the npmjs.com link (https://npmjs.com/package/hyperterm-plugin-example)
[x] There is a visual representation of what my plugin does in the repo. (Plugin: screenshot or gif || Theme: screenshot of the colors within HyperTerm)
[x] VERY IMPORTANT: I've written a short (one sentence) description for my package or theme of why it's awesome and deserves to be on the list.

Could you please add a slightly more descriptive description of why you think hyperterm-chester-dark is an awesome theme?
Just asking, as awesome-hyperterm is intended to be a curated list of the best HyperTerm packages, themes, and resources available, so we want to make sure the package, theme, and resource list items say why we think they're the most awesome!

Hey @evgenTraytyak, could you please add the theme to the bottom of the list? Thanks!

Hey @evgenTraytyak - closing this for now. If you're able to go through and resolve the aforementioned requests, feel free to update the README.md and re-open. Thanks!

authors: bnb evgenTraytyak matheuss

repo: bnb/awesome-hyperterm


text:
Synchronization date is wrong

Hi!
I have Cozy installed on a Raspberry PI at home. Since the last Kresus update, the "Last synchronization with your bank" field is wrong. I manually updated it and the date that appears is 1 day too early. I think it appeared with the last update.

Thanks for the report! It does look strange, especially because nothing has really changed on that matter. Are you using the master or the incoming branch? Can you make sure your Rpi time settings are correct? What timezone are you in?

Hey @EtienneM, any news here?

Sorry I was overwhelmed with work.
And I am truly sorry because it was just a problem with my NTP configuration on the server... Shame one me :sweat:

No problem, thanks for keeping me up to date!

authors: EtienneM bnjbvr

repo: bnjbvr/kresus


text:
Deploy windows notification script to windows target only

Probably just add condition to Resources directory (Lib.csproj) - there are only windows resources right now and its pointless to deploy them on other platforms.
I personally tried to use some built-in properties (RuntimeIdentifier/RuntimeIdentifiers/TargetPlatform ...) during build but they are ignored afterwards (read that explicitly in the log).
Dont wanna introduce custom property for this since it would still require mechanism what OS you are using during development or do we even care if there is a small build overhead that is not necessary for other platforms except Windows?

It could be fixed in Releaser project to delete unneeded files before zipping.

authors: Bobris JanVargovsky

repo: bobril/bbcore


text:
Change time aggregation automatically based on date input

Currently uses the following criteria based on the difference between start and end dates.

year if >= 3 years, else
month if >= 3 months, else
day

If the user changes the time aggregation selector after loading the page, then it uses whatever the user last selected. The auto time aggregation is handled independently for LocationPage and ComparePage.
Note I also had to make some fixes to get the test suite running again.

ping @vlandham

repo: bocoup/mlab-vis-client


text:
Fix error getting xValues to match number of bins

Resolves #124. The was a problem where xValues missed the last bin. Now we get it:

ping @vlandham


text:
Fixing some small rendering bugs

As mentioned in #36, one of my earlier commits that set the body position: absolute; inadvertently made the content width smaller. I have set left: 0; and right: 0; on the body now to make the content fit the page width again. I also removed width: 100% from .section div because it was spilling off the edge of the scenario div.

I've removed the position absolute

authors: danielbodart theangrydev

repo: bodar/yatspec


text:
Fix typo in player screen.

It's just a typo. One of my coworkers (@niklanus) saw this during your presentation in ODD.

@mcavallo gracias!

authors: bodymovin mcavallo

repo: bodymovin/bodymovin


text:
Create additional info blocks

You can make your resume less official by adding more entertaining info, like your hobbies and interest, or what do you like, some interactive content or joke, easter egg, etc.

working on ot


text:
invalid response cookies

Any chance of adding a flag or something to disable the messages? they are redundant anyway because, apart from the message, the value is immediately sanitized and passed on. this happens on google and youtube - related to https://github.com/bogdanfinn/tls-client/issues/23

https://github.com/Carcraftz/fhttp/commit/bd427df5ca71127d2c167131e61e3ea3cfc1bd4b

@erg43hergeg should be implemented in b707dce

repo: bogdanfinn/tls-client


text:
Replace "watch"

Replace watch with node-watch in order to get a more streamlined codebase.
https://www.npmjs.com/package/node-watch

Oh, and make an interface for it, such that the IO isn't so weird and proprietary

repo: boginw/notable


text:
Preparation of meeting and guide for development of dynamic model calculations

The following actions are to do, in order to prepare the meeting and the guide:

[x] #320

[x] #321

[x] #322

All goals achieved. Issue can be closed

authors: KrzysztofKaczmarzyk bogumilchilinski

repo: bogumilchilinski/dynpy


text:
Estudar DNS

Estudar DNS para construção da URL na porção servidor.

Publicado no canal da disciplina o vídeo com resumo do conteúdo de terceiros sobre os conceitos básicos de DNS:

Como funciona a Internet?
A Importância do DNS nas redes, explicada pelo NIC.br
Nivelamento de protocolo DNS e configuração de DNS reverso (OPCIONAL)
O que é DNS?
Servidores raiz do DNS


text:
unknown mail transport error

Sometimes mails are stuck in the queue with error description "unknown mail transport error".
When I log into the container and run postqueue -f, the mails go through. Not sure if this is an issue with the container image or the receiving end, I have some logging that says :

warning: private/smtp socket: malformed response"
Read 141 chars: 250-secure-smtpnodes.otherdomain

Any clues on how to do a root cause analysis ?

.nl??250-PIPEL"

I don't know if I can help you much.
However, you do seem to have an error/warning regarding btree hash. This was removed in the latest versions of Alpine, so if possible, you should try switching to lmdb first and see if that fixes the issue.

thank you the response.
I am however still confused on how to try to move to lmdb ? Does this require me to install this on the docker container and as such build a custom container based on your Dockerfile ?
Thanks!

Any postfix config that you may have that uses external files (such as aliases) which look like this: something = btree:/path/to/file or something = hash:/path/to/file need to be replaced with something = lmdb:/path/to/file

authors: bokysan komasoftware

repo: bokysan/docker-postfix


text:
Expand volumeClaimTemplates spec

Use the full volumeClaimTemplates spec to avoid manifest diffs when using ServerSideApply/Diff.
Example:

Thanks for the commit!

authors: bokysan horjulf


text:
Adds duration prop to modals

Adds prop duration in milliseconds before a modal hides itself.
Value of undefined or -1 naturally does not trigger a hide()
<FadeModal ref="TaskComplete" duration={5000} />

Looks good to me.

Thanks for maintaining @BrandonWade. When will the latest commit be on NPM?

I'll try and get it up later today. We're trying to get the package transferred over to us from the original owner on NPM which is taking awhile

The new version should be available on NPM now; sorry for the delay!

authors: BrandonWade Jaywaa

repo: bold-commerce/reboron


text:
encodeToRot13

https://github.com/bologov/js-assignments/blob/34d0e7ec0df2e5f01a943f8869f7d57294c076df/task/01-strings-tasks.js#L240-L253
Непонятная магическая цифра 26. Обычно для понимания заводят константу:
const lettersCount = 26;

str.charAt(i) вызывается в цикле кучу раз, обычно в таких случаях заводят переменную, чтобы сократить кол-во вычислений.
И в принципе, задание можно решить одим вызовом метода https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/replace .

https://github.com/bologov/js-assignments/blob/add0164d92bbb9de75dc18c595f91e56d7260724/task/01-strings-tasks.js#L230-L237
if (letter.toUpperCase() >= "N") {
            return String.fromCharCode((letter.charCodeAt(0) - lettersCount + 13));
        }
        return String.fromCharCode((letter.charCodeAt(0) + 13));

Тут очень много дублируется, по идее можно упростить до
return String.fromCharCode((letter.charCodeAt(0) + 13 - lettersCount  * (letter.toUpperCase() >= "N")));

repo: bologov/js-assignments


text:
Feat: Update Mission Modal Blueprint w/ new (WIP) Rating component

Jira
http://vjira2:8080/browse/BDS-2089
Summary
Updates the existing Mission Modal blueprint with updated design comps; new Rating component.

Details

Includes a fix for a tiny z-index related issue I ran into while using the new Card component's background layer.
Also includes some demo JS to show the submit button requiring a rating to be chosen.

How to test

Review updated Modal blueprints (before and after submitting) -- any large red flags or updates needed in order to get this out the door?

@sghoweri Nice job putting this together so quickly. I added some inline comments/questions. Let me know what you think.
Also, the background image isn't visible for me locally or on feature branch: https://feature-update-mission-modal.boltdesignsystem.com/pattern-lab/?p=blueprints-t1-mission-landing--test-with-modal

@danielamorse I should have a fix for that pushed up very shortly -- the image is there... it's just not showing up due to the related updates I pushed up to address @mikemai2awesome's feedback.

@sghoweri @danielamorse
I took care of my own comments above with the latest PR, plus the following:

Made sure the white part of the background image does not crash with with text at any viewport.
Made design judges on a few utility classes and removed them. We shouldn't be overriding so much for minimal gains.

PR was released with v2.21.0

repo: boltdesignsystem/bolt


text:
🛑 Bomberos Coyhaique is down

In 2e407c7, Bomberos Coyhaique (https://bomberoscoyhaique.cl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Bomberos Coyhaique is back up in 065b72c after 14 minutes.

repo: bomberosalas/status


text:
🛑 Bomberos Coyhaique is down

In fcbba55, Bomberos Coyhaique (https://bomberoscoyhaique.cl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Bomberos Coyhaique is back up in 0acfd6a after 10 minutes.


text:
Automate GUI testing with macros

You could automate simple GUI tests specified in the integration tests by writing macros. Simple things like verifying that an error message pops up, when the user tries to run a plugin with a wrong kind of image. For example "Verify that the ConnectivityWrapper plugin shows an error message if the user tries to run it with a non binary image".
There might be a way to automate the running of these test macros, but even having them around as manually runnable files would help in testing that everything still works after changes.

I've learned how to automate most tests in JUnit with the help of Mockito the mocking framework. It's more convenient to run these automatically in the IDE or with Maven instead of launching macros.


text:
🛑 Radarr is down

In 2816ca1, Radarr ($URLS_RADARR) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Radarr is back up in 95a4d96.


text:
undefined binding error(s) if null value present.

A query with null value would throw a undefined binding(s) error.
User.forge({ name: null }).fetch()

Is it better to generate SQL
SELECT * FROM users WHERE name IS NULL

rather than throw a binding error ?

I've only a concern about this change
var foo = null if(bar == false){foo = "jack";} User.forge({ name: foo }).fetch()
in this case maybe the developer want to know with an error if the variable is null

authors: Playrom chenghung

repo: bookshelf/bookshelf


text:
Fix API reference

This PR fixes lots of Doxygen broken links and errors that have probably been accumulating over time.

This PR fixes lots of Doxygen broken links and errors that have been probably accumulating over the years.
Here is a summary of the errors and how errors in each category were fixed:

Reference to Concept that doesn't exist in doxygen.
Searching for .../boost/beast/http/message_generator.hpp:56: warning: unable to resolve reference to 'BuffersGenerator' for \\ref command

Generating XML output for class .../boost/libs/beast/include/boost/beast/core/buffers_generator.hpp:139: warning: unable to resolve reference to 'BuffersGenerator' for \ref command

Doxygen does not support concepts. It seems like some people use @interface as a workaround to document concepts, but that requires the toolchain to understand we are doing that.

Doxygen required the fully qualified name at some points.
Parsing file .../boost/libs/beast/include/boost/beast/core/buffers\_range.hpp...../boost/libs/beast/include/boost/beast/core/buffers\_range.hpp:123: warning: unbalanced grouping commands

Searching for .../boost/beast/http/fields.hpp:102: warning: unable to resolve reference to 'field::unknown' for \\ref command

Searching for .../boost/beast/http/fields.hpp:638: warning: @copybrief or @copydoc target 'basic\_fields::equal\_range(boost::beast::http::field) const' not found

Generating docs for compound boost::beast::http::chunk_.../boost/libs/beast/include/boost/beast/websocket/error.hpp:20: warning: unable to resolve reference to 'beast::websocket::stream' for \\ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:287: warning: unable to resolve reference to 'async_base' for \ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:300: warning: unable to resolve reference to 'async_base' for \ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:335: warning: unable to resolve reference to 'complete' for \ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:335: warning: unable to resolve reference to 'complete_now' for \ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:337: warning: unable to resolve reference to 'beast::allocate_stable' for \ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:344: warning: unable to resolve reference to 'complete_now' for \ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:376: warning: unable to resolve reference to 'complete' for \ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:376: warning: unable to resolve reference to 'complete_now' for \ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:378: warning: unable to resolve reference to 'beast::allocate_stable' for \ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:194: warning: unable to resolve reference to 'async_base' for \ref command

.../boost/libs/beast/include/boost/beast/core/async_base.hpp:278: warning: unable to resolve reference to 'async_base' for \ref command

.../boost/libs/beast/include/boost/beast/http/fields.hpp:427: warning: unable to resolve reference to 'string_view' for \ref command

.../boost/libs/beast/include/boost/beast/http/fields.hpp:445: warning: unable to resolve reference to 'string_view' for \ref command

.../boost/libs/beast/include/boost/beast/http/fields.hpp:468: warning: unable to resolve reference to 'string_view' for \ref command

.../boost/libs/beast/include/boost/beast/http/fields.hpp:484: warning: unable to resolve reference to 'string_view' for \ref command

.../boost/libs/beast/include/boost/beast/http/fields.hpp:501: warning: unable to resolve reference to 'string_view' for \ref command

.../boost/libs/beast/include/boost/beast/http/fields.hpp:427: warning: unable to resolve reference to 'string_view' for \ref command

.../boost/libs/beast/include/boost/beast/http/fields.hpp:445: warning: unable to resolve reference to 'string_view' for \ref command

.../boost/libs/beast/include/boost/beast/http/fields.hpp:468: warning: unable to resolve reference to 'string_view' for \ref command

.../boost/libs/beast/include/boost/beast/http/fields.hpp:484: warning: unable to resolve reference to 'string_view' for \ref command

.../boost/libs/beast/include/boost/beast/http/fields.hpp:501: warning: unable to resolve reference to 'string_view' for \ref command

Maybe there's a way to make Doxygen better understand relative references, but I'm not aware of such an option.

Type has changed in a previous commit.
Searching for .../boost/beast/http/span_body.hpp:24: warning: unable to resolve reference to 'span' for \\ref command

@param name mismatch. Whenever this happened, I've updated the @param from the function declaration instead of updating the declaration.
Generating XML output for class boo.../boost/libs/beast/include/boost/beast/_experimental/test/stream.hpp:235: warning: argument 'ioc' of command @param is not found in the argument list of boost::beast::test::basic_stream< Executor >::basic_stream(ExecutionContext &context, typename std::enable_if< std::is_convertible< ExecutionContext &, net::execution_context & >::value >::type *=0)

.../boost/libs/beast/include/boost/beast/_experimental/test/stream.hpp:235: warning: The following parameter of boost::beast::test::basic_stream::basic_stream(ExecutionContext &context, typename std::enable_if< std::is_convertible< ExecutionContext &, net::execution_context & >::value >::type *=0) is not documented:
parameter 'context'

.../boost/libs/beast/include/boost/beast/core/buffers_generator.hpp:138: warning: argument 'handler' of command @param is not found in the argument list of boost::beast::async_write(AsyncWriteStream &stream, BuffersGenerator generator, CompletionToken &&token) -> typename net::async_result< typename std::decay< CompletionToken >::type, void(error_code, std::size_t)>::return_type

.../boost/libs/beast/include/boost/beast/core/buffers_generator.hpp:138: warning: The following parameter of boost::beast::async_write(AsyncWriteStream &stream, BuffersGenerator generator, CompletionToken &&token) -> typename net::async_result< typename std::decay< CompletionToken >::type, void(error_code, std::size_t)>::return_type is not documented:
parameter 'token'

Macros that weren't being properly replaced in Doxygen. I've adjusted doc/Jamfile to make Doxygen understand these.
.../boost/libs/beast/include/boost/beast/_experimental/test/stream.hpp:439: warning: argument 'handler' of command @param is not found in the argument list of boost::beast::test::basic_stream< Executor >::async_read_some(MutableBufferSequence const &buffers, ReadHandler &&handler BOOST_ASIO_DEFAULT_COMPLETION_TOKENexecutor_type)

.../boost/libs/beast/include/boost/beast/_experimental/test/stream.hpp:439: warning: The following parameter of boost::beast::test::basic_stream::async_read_some(MutableBufferSequence const &buffers, ReadHandler &&handler BOOST_ASIO_DEFAULT_COMPLETION_TOKENexecutor_type) is not documented:
parameter 'BOOST_ASIO_DEFAULT_COMPLETION_TOKEN'

.../boost/libs/beast/include/boost/beast/_experimental/test/stream.hpp:519: warning: argument 'handler' of command @param is not found in the argument list of boost::beast::test::basic_stream< Executor >::async_write_some(ConstBufferSequence const &buffers, WriteHandler &&handler BOOST_ASIO_DEFAULT_COMPLETION_TOKENexecutor_type)

.../boost/libs/beast/include/boost/beast/_experimental/test/stream.hpp:519: warning: The following parameter of boost::beast::test::basic_stream::async_write_some(ConstBufferSequence const &buffers, WriteHandler &&handler BOOST_ASIO_DEFAULT_COMPLETION_TOKENexecutor_type) is not documented:
parameter 'BOOST_ASIO_DEFAULT_COMPLETION_TOKEN'

An extra error we got was
xslt-xsltproc-dir libs/beast/doc/html/beast_HTML.manifest
Error: no ID for constraint linkend: "beast.ref.".

I have no idea where this is coming from.

@evanlenz any idea about that last one?

The 4.8 issue is fixed, merging. Clearly fixing a bunch of things, the last one can be a separate issue.

repo: boostorg/beast


text:
remove type aliases

we should get rid of our aliases for error_code, result, et. al. and just use them directly from system.
This is just a replicate of this issue: https://github.com/boostorg/url/issues/743
The solution for Boost.URL was: https://github.com/boostorg/url/commit/96438f683e09e20183fab1b6059fa7f1b0ffe67d

Duplicate of #881

authors: alandefreitas grisumbras

repo: boostorg/json


text:
Space in home directory

On OSX, the command "boot2docker shellinit" is failing when my home directory path has a space in it.
tobenhaus-nb:~ kraney$  $(/usr/local/bin/boot2docker shellinit)
Writing /Volumes/600GB SSD/Users/kraney/.boot2docker/certs/boot2docker-vm/ca.pem
Writing /Volumes/600GB SSD/Users/kraney/.boot2docker/certs/boot2docker-vm/cert.pem
Writing /Volumes/600GB SSD/Users/kraney/.boot2docker/certs/boot2docker-vm/key.pem
bash: export: `SSD/Users/kraney/.boot2docker/certs/boot2docker-vm': not a valid identifier

poking this too

this is a duplicate of #715

authors: SvenDowideit kraney


text:
'value' slot prop on the BTd 'cell(*)' slot is not using the 'formatItem' function

Missing feature is from
bootstrap-vue
Docs
https://bootstrap-vue.org/docs/components/table#custom-empty-and-emptyfiltered-rendering-via-slots
Describe the missing feature
The 'value' slot prop on the BTd 'cell(*)' slot in the BTableLite component is not using the 'formatItem' function as it was in bootstrap-vue.
BTableLite.vue

BoostrapVue (mixin-tbody.js)

From 'bootstrap-vue' documentation

Validations

[X] Have tested with the latest version. This is still alpha version and sometime things change rapidly.
[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided link is to the documentation of the missing feature.

Is next on the TODO list. Hopefully I remember lol

Is next on the TODO list. Hopefully I remember lol

Great! I'm trying to get some time to potentially contribute to this project to help push it over to release 1.0.0.

authors: Melordship VividLemon

repo: bootstrap-vue-next/bootstrap-vue-next


text:
Fix cleanup errors while serving with existing clone on windows

See commit comments for details

appreciate it! released in 0.1.2

authors: pajoma steven-terrana

repo: boozallen/mkdocs-yamp-plugin


text:
Update Song “index”

Automatically generated by Netlify CMS

👷 Deploy Preview for suricate processing.

Name
Link

🔨 Latest commit
f6a944a139ef76a4bb9b37019a02ed8a4ce84b0d

🔍 Latest deploy log
https://app.netlify.com/sites/suricate/deploys/6517f19d30cc630008cc456b

repo: bop/VueDN


text:
sync good part from https://github.com/borball/sno-agent-based-installer

sync the good part from https://github.com/borball/sno-agent-based-installer

done

repo: borball/mno-with-abi


text:
BulkInsert throws InvalidCastException when entity has shadow property

Given the following setup
-- Database schema
CREATE TABLE [dbo].[RootEntity]
(
    [Id] [UNIQUEIDENTIFIER] NOT NULL PRIMARY KEY
)

CREATE TABLE [dbo].[LeafEntity]
(
    [Id] [UNIQUEIDENTIFIER] NOT NULL PRIMARY KEY,
    [RootEntityId] [UNIQUEIDENTIFIER] NOT NULL,
    CONSTRAINT FK FOREIGN KEY ([RootEntityId]) REFERENCES [RootEntity]([Id])
)

// Entities
public class RootEntity
{
    public Guid Id { get; set; }
    public List<LeafEntity> Leaves { get; set; }
}

public class LeafEntity
{
    public Guid Id { get; set; }
}

// DbContext
public DbSet<RootEntity> RootEntities { get; set; }

protected override void OnModelCreating(ModelBuilder modelBuilder)
{
    EntityTypeBuilder<RootEntity> rootBuilder= modelBuilder.Entity<RootEntity>();
    rootBuilder.ToTable("RootEntity");
    rootBuilder.HasKey(e => e.Id);
    rootBuilder.Property(e => e.Id).IsRequired();
    rootBuilder.HasMany(e => e.Leaves).WithOne().HasForeignKey("RootEntityId");

    EntityTypeBuilder<LeafEntity> leafBuilder= modelBuilder.Entity<LeafEntity>();
    leafBuilder.ToTable("LeafEntity");
    leafBuilder.HasKey(e => e.Id);
    leafBuilder.Property(b => b.Id).IsRequired();
}

Aggregate root RootEntity has zero or many LeafEntity instances. LeafEntity references RootEntity through the RootEntityId column which is not exposed by the model, but configured through a shadow property.
Now consider the following snippet:
var rootEntity = new RootEntity { Id = Guid.NewGuid(), Leaves = new List<LeafEntity>() };
var leafEntity = new LeafEntity { Id = Guid.NewGuid() };
rootEntity.Leaves.Add(leafEntity);

using (var ctx = new RootEntityContext(options))
{
    ctx.RootEntities.Add(rootEntity);
    ctx.BulkInsert(new[] { rootEntity });
    // Next statement throws "InvalidCastException:
    // Invalid cast from 'System.String' to 'System.Guid'".
    ctx.BulkInsert(rootEntity.Leaves);
}

Executing the code above throws an System.InvalidCastException exception.
I traced the code against commit 2f98b75c, but I have the same issue with NuGet EFCore.BulkExtensions v2.5.2. I think the problem is caused by the following line https://github.com/borisdj/EFCore.BulkExtensions/blob/2f98b75c247e3c8d8822696064892a4224393343/EFCore.BulkExtensions/SqlBulkOperation.cs#L329
This piece of logic assumes the first shadow property is always a discriminator column which, in this case is not true.
I am attaching SampleProject.zip to illustrate the issue.

I have lookup into the issue.
DiscriminatorColumn could be isolated the following way:
var discriminatorColumn = tableInfo.ShadowProperties.Count == 0 ? null : tableInfo.ShadowProperties.Where(a => a == "Discriminator").FirstOrDefault();
However there is another problem, to get the value of FK Shadow property.
Until this gets solved, the easiest solution for the issue would be to simply in LeafEntity add FK property:
public Guid RootEntityId { get; set; }
public virtual RootEntity RootEntity { get; set; }

I also have this problem, our logic is almost the same. I have updated @jobinpas example to match my code.
// Entities
public class RootEntity
{
    public Guid Id { get; set; }
    public List<LeafEntity> Leaves { get; set; }
}

public class LeafEntity
{
    public Guid Id { get; set; }
    public RootEntity Root { get; set; }
}

// DbContext
public DbSet<RootEntity> RootEntities { get; set; }

protected override void OnModelCreating(ModelBuilder modelBuilder)
{
    EntityTypeBuilder<RootEntity> rootBuilder= modelBuilder.Entity<RootEntity>();
    rootBuilder.ToTable("RootEntity");
    rootBuilder.HasKey(e => e.Id);
    rootBuilder.Property(e => e.Id).IsRequired();
    rootBuilder.HasMany(e => e.Leaves).WithOne().HasForeignKey("Root");

    EntityTypeBuilder<LeafEntity> leafBuilder= modelBuilder.Entity<LeafEntity>();
    leafBuilder.ToTable("LeafEntity");
    leafBuilder.HasKey(e => e.Id);
    leafBuilder.Property(b => b.Id).IsRequired();
}

Is there any information about when this might be fixed?

Same problem here. So +1 to fix this

The fix from @borisdj  works for me.
We have a Shadow property that isn't a discriminator. This causes the exception, but with this it is fixed.
To bad I now can't use the package (until I manage to rid the shadow property from our model).
Could you please include this fix in the EfCore2.2 branch?

I have the same issue..
btw why are you setting value of this column to entity type name?
columnsDict.Add(discriminatorColumn, type.Name);
Should be better to have default null? :)
Or is expected to get an Invalid cast exception?
Thanks for any feedback!

FK Shadow Property is now supported, version 3.2.1+

authors: 304NotModified Thepriestdude borisdj jobinpa pajacz samneefs


text:
New definitions: JSnoX

Defintions for JSnoX (https://github.com/af/jsnox, https://www.npmjs.com/package/jsnox)
Library for using ReactJS without JSX

@stkb thanks mate!

authors: stkb vvakame

repo: borisyankov/DefinitelyTyped


text:
Make Network test manyValidators more reliable

This has a fix for the flaky ManyValidators test plus a few trivial changes that were in PR 2270.
As more changes are required in the other PR I think it is worth getting these merged first.

source/agora/node/Ledger.d(1571,32): Error: function agora.node.Ledger.Ledger.acceptBlock(in Block block) is not callable using argument types (const(Block), string, ulong)

source/agora/node/Ledger.d(1571,32): Error: function agora.node.Ledger.Ledger.acceptBlock(in Block block) is not callable using argument types (const(Block), string, ulong)

Forgot to compile again. Will update.

I see now there are quite a few redundant string file = __FILE__, int line = __LINE__.
I'll tidy them up also as it is just dead code.

I pushed an update to remove more dead code in the last commit.

Very nice!

authors: Geod24 hewison-chris kchulj

repo: bosagora/agora


text:
Docu intro

This will give an introduction to perun protocol, state channel, perun and go-perun.
Signed-off-by: Anagha Sukumaran sukumaran.anaghak@in.bosch.com

PR submitted to upstream repo and has been merged.

authors: anagha-ks manoranjith

repo: boschresearch/dst-doc


text:
cmd/scollector: Track process PIDs.

As requested by @kylebrandt .
:eyeglasses: @gbrayut @captncraig

From Bosun chat for reference:
stianovrevage	[6:28 AM]
Hi guys, I'm looking at https://github.com/bosun-monitor/bosun/blob/master/cmd/scollector/collectors/processes_windows.go but cannot figure out why the ID reported is not the correct PID...
kylebrandt	[7:48 AM]
PID is not submitted, just ids are generated from a bucket for numbers
stianovrevage	[8:58 AM]
Why?
dima.medvedev	[9:14 AM]
Mainly because opentsdb has a hard limit on tag values
[9:15]
I don't remember how it's done in windows, but linux process collector tries to make process ids unique for one running scollector instance.
[9:16]
Also, it's still possible to identify process via their process start time.
stianovrevage	[9:24 AM]
Ok, thanks for a good answer :smile:
kylebrandt	[9:24 AM]
Also some services might recycle processes frequently
stianovrevage	[9:36 AM]
True, but would be nice to have the option of including PID, for us who don't run into high cardinality issues
[9:36]
image-name + pid should be pretty safe I would think
kylebrandt	[9:38 AM]
Could send it as a metric
[9:38]
Never really thought about that before, it would be strange, but functional
[9:40]
linux.proc.id_pid or something. Where you host,id,name are tags and the value is the corresponding pid at the time (edited)
[9:43]
I think perfmon has that actually (WMI)
[9:43]
A metric like that
stianovrevage	[9:43 AM]
Yep, and just reference that when you actually need to find the process
[9:43]
Yes, it has CurrentID I think
[9:43]
Which is the current PID

Tested locally... LGTM

authors: alienth gbrayut kylebrandt

repo: bosun-monitor/bosun


text:
feature/MIL-20: API Endpoints

As stated in #407, we are expected to provide both Application and Annotation APIs as a collection along with links to the Swagger documentations. I've put the links, provided a brief explanation on how to authorize a request, provided Run Postman button and four examples of API calls: registration, uploading an art item, creating an online exhibition and putting an art item on sale.

Merged without conflicts

users/profile/ is documented as auth/profile
users/profile/users not in collection
auth/account/delete not in collection
artitems/me/followings not in collection
artitems/tags not in collection
api/v1/auth/artitems/int:artitemid/comments/int:id no auth
bid, like, password reset, exhibition, recommendation, tags not in collection
But can always refer to swagger for documentation and testing

Merged without conflicts

authors: BElifb KarahanS ooodogodogodogo


text:
Bug = sent to a proxy of a JS Array does not work

This is actually a double bug:
-Sending = from Pharo to a JS object over the bridge does not actually send = to JS object.
-For JS arrays the implementation of = works only with literals.

Bug fixed in the latest commit

repo: bouraqadi/PharoJS


text:
Chunked upload uploading a 0 byte chunk at the end

[x] I have checked that the SDK documentation doesn't solve my issue.
[x] I have checked that the API documentation doesn't solve my issue.
[x] I have searched the Box Developer Forums and my issue isn't already reported (or if it has been reported, I have attached a link to it, for reference).
[x] I have searched Issues in this repo and my issue isn't already reported.

Description of the Issue
I’m upgrading a project from boxsdk to box-sdk-gen. My unit test covering chunked uploading failed because it expected 3 chunks, but box-sdk-gen uploads 4. The last one is an empty byte string.
Steps to Reproduce
My code is wrapped up in a Django storage class and I don't have the time to minimize it. But roughly what's happening is:
box_client.chunked_uploads.upload_big_file(
    file=BytesIO(b"test content"),
    file_name="test.txt",
    file_size=12,
    parent_folder_id=folder_id,
)

Where the https://upload.box.com/api/2.0/files/upload_sessions endpoint is mocked to return:
"part_size": 4,
"total_parts": len(content) // 4,

12 // 4 = 3, but the client uploads and verifies an empty 4th chunk.
Expected Behavior
No empty chunk - that didn't occur on boxsdk.
Error Message, Including Stack Trace
No error, just waste of resources.
Screenshots
n/a
Versions Used
Python SDK: 1.5.0
Python: 3.11

Hi @adamchainz,
thanks for reaching us. We will investigate this issue and try to fix it asap.
Best,
@lukaszsocha2

Hi @adamchainz,
the fix is now available in the new v1.5.1 release.

Thank you, I’ve upgraded in my client project and can confirm the fix.

repo: box/box-python-sdk-gen


text:
Add "--list--updated--modules" cli option

One solution to this common question. Adds --list-updated-modules to the CLI to see what, if any, newer puppet module versions are available based on one's Puppetfile. Ensures Boxen's GitHub token will be temporarily set as GITHUB_API_TOKEN to not hit API limits.

@dgoodlad what do you think?

+1

At a glance this looks fine to me but I'll take some time to test it over the next few days, what do you think @mikemcquaid?

Can we push the style fixes to a new PR (or skip them entirely)? It's pretty hard to review this as-is due to them :sob:

Will do.
On Fri, Mar 20, 2015 at 1:25 AM Mike McQuaid notifications@github.com
wrote:

Can we push the style fixes to a new PR (or skip them entirely)? It's
pretty hard to review this as-is due to them [image: :sob:]
—
Reply to this email directly or view it on GitHub
https://github.com/boxen/boxen/pull/170#issuecomment-83955732.

@mikemcquaid rebased and moved the style fixes to another PR. :whale2:

@seanknox Makes sense to me. Now you're an owner: merge when you're happy :+1:

@seanknox Are you still interested in shipping this?

authors: dsisnero jacobbednarz mikemcquaid seanknox tarebyte

repo: boxen/boxen


text:
fix/authenticated-user-routed-to-dashboard-route

Fix: #535
Fixed the problem, where the authenticated user will not be able to head in landing page.

@rohitmondal03 We will review shortly but could you please apply the prettier config we have in the root folder on this file please. The formatting change is larger than the actual change and hard to notice the real diff.

Should I change the tab size ??

Our prettier config is here - https://github.com/boxyhq/saas-starter-kit/blob/main/.prettierrc

Can you look into this ?

@shartrooper  I'm not getting this issue. Can you tell hiw you got the issue ?

@shartrooper I'm not getting this issue. Can you tell hiw you got the issue ?

I cloned your fork, installed dependencies, and run the app with "npm run dev" command. This happens just after logging in.

repo: boxyhq/saas-starter-kit


text:
Resizing

I know you have some resizing code unused with some notes on it. Wondering what the hesitation implementing or what you would want it to look like. I would be willing to take it on, if that would help.

Related

authors: BWheatie ShalokShalom

repo: boydm/scenic


text:
Property xml improvements

Preferring "rock permeability" in new xml
Only applying string lookup table to discrete (not continuous) properties
Quiet argument when loading or saving a model
Allowing hyphens in recurrent keywords in Nexus vdb handling

Nexus is a trademark of Halliburton

Codecov Report
Base: 78.64% // Head: 78.54% // Decreases project coverage by -0.10% :warning:

Coverage data is based on head (8abea5e) compared to base (3615e5d).
Patch coverage: 49.12% of modified lines in pull request are covered.

:exclamation: Current head 8abea5e differs from pull request most recent head f2882fc. Consider uploading reports for the commit f2882fc to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #585      +/-   ##
==========================================
- Coverage   78.64%   78.54%   -0.11%
==========================================
  Files         178      177       -1
  Lines       29908    29949      +41
==========================================
+ Hits        23520    23522       +2
- Misses       6388     6427      +39

Impacted Files
Coverage Δ

resqpy/multiprocessing/multiprocessing.py
21.25% <0.00%> (-0.27%)
:arrow_down:

resqpy/multiprocessing/wrappers/blocked_well_mp.py
0.00% <0.00%> (ø)

resqpy/rq_import/_import_nexus.py
41.61% <0.00%> (-1.11%)
:arrow_down:

resqpy/olio/vdb.py
54.92% <15.38%> (-0.66%)
:arrow_down:

resqpy/model/_forestry.py
79.04% <100.00%> (+0.09%)
:arrow_up:

resqpy/model/_model.py
90.03% <100.00%> (+0.03%)
:arrow_up:

resqpy/multiprocessing/wrappers/grid_surface_mp.py
71.61% <100.00%> (-0.65%)
:arrow_down:

resqpy/multiprocessing/wrappers/mesh_mp.py
78.26% <100.00%> (ø)

resqpy/property/_collection_add_part.py
80.24% <100.00%> (+0.16%)
:arrow_up:

resqpy/property/_collection_create_xml.py
98.70% <100.00%> (+0.01%)
:arrow_up:

... and 7 more

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.

@emmanesbit, I've allowed several changes to get bundled into this pull request (sorry). Please focus on the property xml changes for any review.  The vdb import piece has been separately tested and does not need further review.  Similarly for the multiprocessing changes.

authors: andy-beer codecov-commenter

repo: bp/resqpy


text:
feat(download): 实现客户端直链下载

已解决
1.测试安卓客户端视频以及音乐直链下载功能可用，前提为所有文件来源为AList。
2.网盘有的文件会重定向下载到网盘直链，网盘没有的文件但归AList管理也可下载，会走服务器流量中转。
未解决
1.测试外挂字幕视频，只会下载视频文件本身，不会携带下载字幕文件，且由于安卓客户端无法单独手动下载字幕文件。
2.暂未测试文件夹的下载，下载到其他设备。
注意点
1.媒体质量需要选择不转码类型，Original。
2.下载位置最好选Download文件夹，这样其他应用可以访问下载内容。
3.下载后的视频外部打开方式只有几个，暂不知道原因。
4.客户端的下载原本就是经常失败且不会重试，需要手动清理后台重新进入任务栏就会弹出进度条。
测试截图

thanks for your work


text:
Migrate properties panel to new architecture

What should we do?
Migrate properties panel to new architecture (similar to https://github.com/bpmn-io/bpmn-js-properties-panel).

[x] Check if everything is ready for DMN -> no new elements needed

[x] camunda/camunda-modeler-design#62
[x] camunda/camunda-modeler-design#63

[x] Prepare for migration - keep only essential files
[ ] Adapt and copy bpmn-js-properties-panel project to fit dmn's needs

Focus only on drd for now (even tho we provide properties panel for the decision-table and literal-expression views, we aren't using them)
Use #536
[x] Do migration for dmn provider
[ ] Do tests for dmn provider
[ ] Do migration for camunda provider
[ ] Do tests for camunda provider

New prop panel will be here: https://github.com/bpmn-io/dmn-js-properties-panel/tree/next
Why should we do it?
The goal is to have all properties panels used in Camunda Modeler cohesive and conforming with the new properties panel architecture.

Update:
A functional version of the new prop panel is available here. Currently, it is only available for the dmn provider. Run with npm run start:dmn.

Currently working on testing the dmn props (id, name). I'm using selection.select(shape) to test these (like done in bpmn-js-properties) but this doesn't work, due to this bug: https://github.com/bpmn-io/bpmn-js-properties-panel/issues/533. Trying to find a workaround so we can still test these without having to shift focus.

Update:

Properties panel working for drd, including dmn and camunda providers

Missing

ensure properties panel works on view changes
tests on implicit root - can't be copy-pasted from bpmn-js-properties-panel:

const { modeler } = await createModeler(diagramXml, {
   shouldImport: false,
   propertiesPanel: {}
 });

 const canvas = modeler.get('canvas');
 const rootElement = canvas.getRootElement();

 // assume
 expect(rootElement.isImplicit).to.be.true;

 ....

The drdModeler is only accessible after the import via modeler._viewers, so modeler.get(service) is not available before that. These tests needs to be adapted to work for dmn

repo: bpmn-io/dmn-js-properties-panel


text:
HTML

HTML
User Story
As a bootcamp student
I want the prework notes to be structured on a webpage
so that I can easily find and read information
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I visit the website in my browser
THEN I see four boxes titled HTML, CSS, Git, and JavaScript with associated notes listed

HTML has been added


text:
Make Marks  more homogeneous

I would like all the Marks to be more homogenous in the API and in the implementation, this would simplify the code in the library, allowing to put more logic in the Mark.ts implementation.
I feel like the only fully-featured mark is the Scatter, so I guess it is a good starting point to try mimicking its behavior in other marks.
There are different points on which we can work towards this path:
Hovered and selected style
The hovered styling is not implemented everywhere and should be very similar to the selected styling.
There should be the following attributes in all marks:

hovered_style: Dict (counterpart of the selected_style attribute)
unhovered_style: Dict (counterpart of the unselected_style attribute)
hovered: Int or List of Int (counterpart of the selected attribute)

Map

[ ] There is hovered_styles with an s, should it be renamed to hovered_style ?

[ ] unhovered_style missing

[ ] hovered missing

[ ] There is an hover_highlight which should be removed (setting it to False is equivalent to setting hovered_style to the empty dict)

[ ] There is selected_styles with an s, should it be renamed to selected_style?

Graph

[x] hovered_style
[x] unhovered_style
[ ] hovered_point should be renamed in hovered (similar to selected)

ScatterBase

[x] hovered_style
[x] unhovered_style
[ ] hovered_point should be renamed in hovered (similar to selected)

Lines, Hist, BoxPlot, Bars, OHLC, GridHeatmap

[ ]  hovered_style missing
[ ] unhovered_style missing
[ ] unhovered missing

Stroke and fill
I suppose stroke styling and fill styling should follow a similar logic.
In order to slightly follow what the Scatter is doing, I suppose it would be nice to have in all marks:

fill: Bool (whether or not the marks are filled)
colors: List of Color (default fill colors, cycling if there are more marks than color values)
stroke_color: Color or None (stroke color, if None, the stroke will have the same color as the fill color)
stroke_width: Float

Scatter

[x] fill missing
[x] colors missing
[ ] stroke should be renamed stroke_color
[x] stroke_width

Hist

[ ] fill missing
[x] colors missing
[ ] stroke should be renamed stroke_color
[ ] stroke_width missing

Bars

[x] fill missing (see #1025)
[x] colors missing
[ ] stroke should be renamed stroke_color
[x] stroke_width missing (see #1025)

BoxPlot
?
OHLC, Pie

[ ] fill missing
[x] colors missing
[ ] stroke should be renamed stroke_color
[x] stroke_width

Graph

[ ] fill missing
[ ] colors missing
[ ] stroke should be renamed stroke_color
[ ] stroke_width missing

Map

[ ] fill missing
[x] colors missing
[x] stroke_color missing
[ ] stroke_width missing

GridHeatmap

[ ] Should null_color be rename colors? (After all, colors will be the default color in other marks)
[ ] stroke should be renamed stroke_color
[ ] stroke_width missing

Lines
I feel like Lines and FlexLine should remain special cases, as colors refers to the stroke, the stroke being what is displayed by default, not the filling.
Opacities
The default_opacities attribute in Scatter behaves like colors, it is a list of values, values are reused if the list is smaller than the number of points. It should behave the same in other marks.
Scatter

[ ] default_opacities should be renamed opacities, just like it was done before in other marks (see #1011)

Lines

[ ] Should we keep fill_opacities? Or just opacities that will apply to the stroke and fill.

Map, Graph, GridHeatMap

[ ] opacities missing

Bars

[x] opacities are not reused if the list is too short (Fixed #1121)

Other marks are just fine, they seem to implement opacities correctly.

Bars vs Scatter
[ ] Labels/Names (names in Scatter, Labels in Bars)

authors: SylvainCorlay martinRenou

repo: bqplot/bqplot


text:
Is group-hover supported in styled components?

I have added group-hover under the visibility module array in tailwind.js. I have then added it in my styled component as
 const Hover = styled.div’
  ${tw ‘invisible group-hover:visible’};
‘

It however doesn’t seem to be applying. All other tailwind styling is working as expected. Is there any thing I need to specifically do to get group-hover working?

Hey @shawnmmatthews
group-hover is supported in the tailwind.macro alpha, which you can try if you’re using Tailwind v1: npm install tailwind.macro@next
import tw from 'tailwind.macro';

const Hover = tw.div’invisible group-hover:visible’;

Thanks!

authors: bradlc shawnmmatthews

repo: bradlc/babel-plugin-tailwind-components


text:
teacher mode

Implement teacher mode:

statistics are neither recorded nor shown
all lessons and steps are unlocked
"to current step" button is unavailable

When the user returns back to learner mode, he/she continues from the last step he visited before turning on teacher mode.

I like the current minimalist implementation of this mechanism and I hope users will enjoy it too.

repo: braille-systems/learn-braille


text:
Allow scrolling of app description on task submission/process page or add a way to show possible input options

Currently, when submitting a new task on the process page the description of the app is cut off. This is a problem when the app description describes the possible options you can use as inputs for the app. For example, the Laplace beltrami app has a string input labeled 'normalization'. The user can input four possible strings: none, 'index', 'area' or 'areaindex', but the only way the user knows what options they can input is by reading the app description.
I think we should add the capability to scroll the app description when submitting a new task. I also think it would be helpful if we could list next to the input boxes what the possible options are.

Yes, we should display the full description of the app while submitting the task.
Although.. it sounds like we should add a new input type of "enum" where we let user select from possible values.
In the app input config, it could look like this.
"normalization": {
    "type": "enum",
    "default": "areaindex",
    "values": [
     {
        "value": "none",
        "label": "None",
        "desc": "Don't perform any normalization"
    },
     {
        "value": "area",
        "label": "2D Area",
        "desc": "Uses the area of the 2D structure as in Reuter et al. 2006."
    },
    {
        "value": "index",
        "label": "Eigenvalue Index",
        "desc": "Divide the eigenvalues by their index to account for linear increase of Eigenvalue magnitude (Weyl's law in 2D) as suggested in Reuter et al. (2006) "
    },
    {
        "value": "areaindex",
        "label": "Area Index",
        "desc": "divide the eigenvalues by their index to account for linear increase of Eigenvalue magnitude (Weyl's law in 2D) as suggested in Reuter et al. (2006) "
    }
    ]
}

yes, I like the enum input type!

@kitchell
I've released an update to allow you to use enum input type.
You can replace your "normalization" configuration with the one that I've posted yesterday.

perfect! thank you.

authors: kitchell soichih

repo: brain-life/core-warehouse


text:
Test pull request for CI testing

Created Spring Boot server and added image loading.
Resolved #32.
Resolved #33.
Resolved #34.

This was a test only to check whether the tests work fine.


text:
Switch from Markdown to XML

Anthropic recommends XML, and in testing other models, XML comes out ahead, especially for complex prompts. I'll work on converting and testing jar3d with XML.
Comparison of RAW, Markdown, XML, and JSON prompt formatting

Sounds like an interesting approach. I've found that it works well with Markdown, and is easy to read/update however it would be interesting to see results with XML.

authors: john-adeojo manjaroblack


text:
onCancelled Method not called for paypal custom integraton.

I also updated the issue
https://github.com/braintree/braintree-web/issues/71
I am still having issues with the onCancelled not being called. This is what we are doing.
including the braintree library from:
js.braintreegateway.com/v2/braintree.js
And we are using paypal custom integration as
braintree.setup(clientToken, "paypal", {
container: this.paypalContainerId,
singleUse: false,
onPaymentMethodReceived: function (obj) {
this.setPayPalPaymentInfo(obj);
this.expandPayPal();
}.bind(this),
onUnsupported: function(){
this.setPayPalPaymentInfo(null);
this.collapsePayPal();
}.bind(this),
onCancelled: function(){
this.setPayPalPaymentInfo(null);
this.collapsePayPal();
}.bind(this)
});
I can verify that the onPaymentMethodReceived is being called. But the onCancelled method is not called anymore.
Any help is appreciated. Thanks!.

You're right! We're working on getting a fix out. This is a duplicate of issue #89—you can keep up with things there.

authors: EvanHahn vijaykumar-krishnaswamy

repo: braintree/braintree-web


text:
Add notes.

In gitlab by @mrkrstphr on Sep 20, 2017, 17:00
null

In gitlab by @mrkrstphr on Sep 21, 2017, 08:45
added ~2693279 label

In gitlab by @mrkrstphr on Sep 21, 2017, 08:39
added ~2696625 label

In gitlab by @mrkrstphr on Sep 21, 2017, 08:50
removed ~2693279 label

In gitlab by @mrkrstphr on Sep 21, 2017, 08:49
closed via commit 60df370b64c1ee11b558c62e01d2f407720a31c9

repo: branchology/branchology


text:
Break out code into separate modules

General reorganization and improvements

Codecov Report

Merging #6 (3b8953b) into master (c05aaf8) will decrease coverage by 22.12%.
The diff coverage is 33.92%.

@@             Coverage Diff             @@
##           master       #6       +/-   ##
===========================================
- Coverage   60.00%   37.87%   -22.13%
===========================================
  Files           1        5        +4
  Lines          40       66       +26
===========================================
+ Hits           24       25        +1
- Misses         16       41       +25

Impacted Files
Coverage Δ

src/Database/Persist/Monad/Class.hs
0.00% <0.00%> (ø)

src/Database/Persist/Monad/SqlQueryRep.hs
25.00% <25.00%> (ø)

src/Database/Persist/Monad.hs
57.14% <50.00%> (-2.86%)
:arrow_down:

src/Database/Persist/Monad/Shim.hs
75.00% <75.00%> (ø)

src/Database/Persist/Monad/TestUtils.hs
83.33% <83.33%> (ø)

Continue to review full report at Codecov.

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