text:
Config for avoiding rootfs shifts/mitigating failures with snapshots

I'd like to add a flag or config to avoid performing operations that would cause an id shift on the container rootfs. In other words, this would allow something like the following flow:
lxc config set mycontainer raw.idmap "both 1000 1000"
lxc start --disallow-id-shift mycontainer   # fails
lxc snapshot mycontainer pre-shift-snapshot
lxc start mycontainer                       # succeeds after remapping

# some time later
lxc delete mycontainer/pre-shift-snapshot

# or, if the remapping was interrupted
lxc restore mycontainer pre-shift-snapshot

AFAICS the same would be needed for lxc publish since that may also perform shifts under the hood.
I'd love to hear any thoughts on whether this seems sane, or if there's a better way to go about this before an in-kernel remapping solution is ready :) I'm happy to post PRs, of course.
Alternatives
One other idea I had was a config to have LXD internally perform a snapshot before shifting ids, and then remove the snapshot afterward. That felt a bit too much like it's moving policy into LXD though, and it seems weird that a start or publish operation would also create a snapshot... On the other hand, I think this would be easier for other LXD users to utilize.
The other idea was for Chrome OS's LXD control daemon tremplin to check the id maps itself via the volatile.* configs to know when to perform a snapshot, but that seems very brittle. IMO the concrete id map at runtime, aside from any manually mapped ids like "both 1000 1000", shouldn't be the business of anything except LXD.
Background
On Chrome OS it's not improbable that our VM will be inadvertently shut down while shifting the container's rootfs ids. This could be due to a power failure, kernel panic in VM guest or host, or a Chrome crash (yes, Chrome crashing will cause our VM/LXD instances to require shutdown :). We saw a few users hitting this in crbug.com/894299.
Until there's a solution to leave these ids unshifted on disk, we would like to ensure that we take a snapshot before performing id shifts. Our downstream tracking bug for this is crbug.com/912360.

I think it should actually be pretty simple for tremplin to determine whether a shift is going to happen by comparing volatile.last_state.idmap to volatile.idmap.next, if they differ, a shift will occur on startup.
In theory we could introduce a security.protection.shift config key which if set to true would prevent any shifting operation, requiring the user to set it to false temporarily as needed, though the check above may be enough until we get to shiftfs.
@sforshee is currently working on porting the shiftfs patches to 4.19 and I'm expecting to have the initial LXD support for it done in January with it shipping to our users as part of Ubuntu 19.04 in April.
That will unfortunately not be mainline at that point and it's still not completely clear what the mainline solution will end up being, whether that's just merging shiftfs or some VFS rework to make it possible to do this without being a filesystem, but shiftfs will be a clean standalone virtual filesystem so backporting it and maintaining a kernel with it shouldn't need much effort.

If you're comfortable with programs other than LXD examining volatile.last_state.idmap and volatile.idmap.next then I think that addresses my concerns with letting tremplin deal with that state.
I could see the security.protection.shift config key being useful just to protect users who want to run lxc publish. But if this doesn't seem like a super useful addition for LXD, I can just update the reddit crostini wiki to encourage snapshotting and we can close this :)

security.protection.shift should be easy enough to implement that if you think it's worth it to prevent potential issues with lxc publish, it's probably fine to do so.
Snapshots when published, at least on btrfs and zfs, get copied read-write, then shifted, exported and discarded, so even if something bad happens mid publish, the snapshot itself should be fine and so the protection doesn't need to extend to them.
So it'd effectively only control startup time shifting of the container itself and be only relevant on systems where shifting is used (so will be ignored when shiftfs is available).

authors: smibarber stgraber


text:
lxd/backup : update the error msg when "backup/index.yaml" can't be found

Signed-off-by: Gabriel Mougard gabriel.mougard@gmail.com

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

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

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

jenkins: test this please

source: gharchive/pull-request

repo: lxc/lxd

license_type: permissive

license_source: bigquery


text:
xattr: Support empty values

Signed-off-by: Stéphane Graber stgraber@ubuntu.com

LGTM! Thanks for fixing it that quickly :-)

@brauner jenkins looks pretty happy with this

authors: morphis stgraber


text:
Update Ubuntu packages

Hi !
The "python3-pylxd" packages for the Focal, Groovy and Hirsute versions of Ubuntu are still pointing to the 2.2.10
Can you push the latest version to these repositories ?
Thanks :)

We don't maintain the packages in Ubuntu/Debian - you're probably best contacting the Debian maintainers - https://tracker.debian.org/pkg/python-pylxd

source: gharchive/issue

authors: mazerty sparkiegeek

repo: lxc/pylxd


text:
fix activity path of AndroidManifest

com.lyft.domic.samples.redux.rxredux.MainActivity is wrong activity path.
I fix to '(com.lyft.domic.samples.mvvm).MainActivity. it's a mvvm sample.

Ah, I guess refactoring touched that, thanks!

authors: artem-zinnatullin satoshun

repo: lyft/domic

license_source: github-api


text:
fix: failed data loading/refreshing in TaskExecutionDetails

TL;DR
Fixes a failure to load data in the TaskExecutionDetails view when coming from a page where the TaskExecution has already been loaded an is in a final state.
Also fixes a refresh issue with child NodeExecutions on that page.
Type

[x] Bug Fix
[ ] Feature
[ ] Plugin

Complete description
The enabled flag on useQuery is meant to delay running a dependent query until data from the parent is available. We were abusing it a little bit by attempting to use it to return cached data from a query without running the query. A better implementation of this is to conditionally set the staleTime to Infinity and disable refetch in the case where we want to just use whatever cached data is available. This updates useCondtionalQuery to follow that logic.
Also fixed an issue where the NodeExecutions list on the TaskExecutionDetails page was not refreshing when the parent generator task succeeded but the spawned NodeExecutions were still in progress. This required adding a refetchInterval to the query and fixing the logic in the shouldEnableQuery function.
Tracking Issue
https://github.com/lyft/flyte/issues/672

Codecov Report

Merging #142 (fcab137) into master (d8daf6c) will decrease coverage by 0.10%.
The diff coverage is 68.42%.

@@            Coverage Diff             @@
##           master     #142      +/-   ##
==========================================
- Coverage   74.43%   74.32%   -0.11%
==========================================
  Files         415      414       -1
  Lines        7310     7310
  Branches     1154     1159       +5
==========================================
- Hits         5441     5433       -8
- Misses       1869     1877       +8

Impacted Files
Coverage Δ

src/components/App/App.tsx
85.71% <ø> (-0.50%)
:arrow_down:

src/components/data/QueryAuthorizationObserver.tsx
29.41% <ø> (ø)

src/components/hooks/useFetchableData.ts
91.07% <ø> (-1.79%)
:arrow_down:

src/components/data/apiContext.ts
61.90% <20.00%> (-32.22%)
:arrow_down:

...utions/TaskExecutionDetails/TaskExecutionNodes.tsx
57.57% <33.33%> (ø)

src/components/Navigation/ProjectSelector.tsx
100.00% <100.00%> (ø)

...rc/components/Navigation/SearchableProjectList.tsx
100.00% <100.00%> (ø)

src/components/hooks/useConditionalQuery.ts
100.00% <100.00%> (ø)

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 dd62120...fcab137. Read the comment docs.

Codecov Report

Merging #142 (fcab137) into master (d8daf6c) will decrease coverage by 0.10%.
The diff coverage is 68.42%.

@@            Coverage Diff             @@
##           master     #142      +/-   ##
==========================================
- Coverage   74.43%   74.32%   -0.11%
==========================================
  Files         415      414       -1
  Lines        7310     7310
  Branches     1154     1159       +5
==========================================
- Hits         5441     5433       -8
- Misses       1869     1877       +8

Impacted Files
Coverage Δ

src/components/App/App.tsx
85.71% <ø> (-0.50%)
:arrow_down:

src/components/data/QueryAuthorizationObserver.tsx
29.41% <ø> (ø)

src/components/hooks/useFetchableData.ts
91.07% <ø> (-1.79%)
:arrow_down:

src/components/data/apiContext.ts
61.90% <20.00%> (-32.22%)
:arrow_down:

...utions/TaskExecutionDetails/TaskExecutionNodes.tsx
57.57% <33.33%> (ø)

src/components/Navigation/ProjectSelector.tsx
100.00% <100.00%> (ø)

...rc/components/Navigation/SearchableProjectList.tsx
100.00% <100.00%> (ø)

src/components/hooks/useConditionalQuery.ts
100.00% <100.00%> (ø)

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 dd62120...fcab137. Read the comment docs.

:tada: This PR is included in version 0.19.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 0.19.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

repo: lyft/flyteconsole


text:
Switching from using model Metadata -> TaskMetadata

TaskMetadata will be maintained as a shadow and allows decoupling of
protocol buffer types from contributor code and user code. This allows
more flexiblity
another prime motivation behind this change is that - it allows making the interface less verbose. This makes it trivial to support default values for metadata.

I think I'm not seeing the bigger picture.  At least I don't understand how this is a decoupling?  Ultimately, at serialization time, the Python class will have to be converted into the model class right?  I feel like this is more delaying the coupling rather than decoupling.
Which is fine, but I don't understand what this enables.  +1 if you want.  I think it's okay to use the model sometimes though - like currently we use the dynamic job spec model, literal map and parameter map models, all the literal models, auth, labels, annotations, etc.  I don't think we should create parallel classes for all those.

can you take a look at test failures?

authors: katrogan kumare3 wild-endeavor

repo: lyft/flytekit


text:
Update bazel-gazelle version

The current bazel version complains about use of cfg="data" on an attribute in the old version of bazel-gazelle. The current release doesn't have this problem.

@rodaine can you approve this to fix CI?

repo: lyft/protoc-gen-validate


text:
Can't truly uninstall

When I disable and uninstall this plugin, and after restarting on all devices, it continues to create the Daily Planner directory and new day planner file. This is driving me crazy; it's bad enough I'm considering nuking my vault and apps entirely to remove it.

Well, I nuked the whole Vault and made a new one.  Now, the old vault, with the same name, keeps getting made so that “Daily Planner” can be made with the daily note file underneath.  This is crazy.  I guess I could setup a chronjob to delete the dir every day, but what do I have to do here?  I fully reinstalled Obsidian and it still keeps happening.

Okay, I think I figured it out.
I had moved on from my old vault on only 3 out of 4 devices. So the last one, that I forgot about, was still making that daily note constantly.
Can probably mark as solved.

repo: lynchjames/obsidian-day-planner

license: MIT


text:
Adapt to new nICEr API

After https://github.com/lynckia/nrappkit/pull/4 and https://github.com/lynckia/nICEr/pull/2 are merged, need to update licode to work with changed nICEr api.
This PR is showing how I did it. Not sure it is 100% correct, but it works in our environment and now is on testing stage.
Note: need to change GIT_TAG for project_nicer in erizo/src/third_party/nicer.cmake to new value.

This looks promising! thanks a lot for the contribution, why do you want to update nICEr? are there new features?

Mostly because of stability issues: we often see disconnection with "Ica failed" error. For some clients it happens during almost each session.
On our side we still have ability to switch between libnice and nicer, and when we switch to the latest libnice it works more stable. But you decided to go with nICEr, this is why we tried the latest version of it. For now I can say - it works better.
During merging I saw such new features:

changed ice-restart logic
mDNS support

I merged these commits in another PR to fix a couple of cases, thanks for the contribution

authors: jcague vpoddubchak

repo: lynckia/licode

license: mit


text:
fix(sbb-tag): fix styles

Preflight Checklist

[x] I have read the Contributing Guidelines for this project.
[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the pull request tracker for a Pull Request (PR) that matches the one I want to submit, without success.

Issue
This PR fixes an issue reported by Aleksandar from team Lynx, related to both storybook and his aem environment:
Tag elements are not correctly displayed
Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)

See Review Guidelines for more information what is checked during review process.
Changes
Changes in this pull request:

fixed tag element display (background, border, animations)

Browsers
I tested the build on the following browsers:

[x] Firefox Desktop
[x] Chrome Desktop
[ ] Edge Desktop
[x] Safari Desktop
[x] Chrome Mobile
[x] Safari Mobile

Screen readers
I tested the build on the following browsers:

[ ] JAWS Firefox Desktop
[ ] JAWS Chrome Desktop
[ ] NVDA Firefox Desktop
[ ] NVDA Chrome Desktop
[ ] VoiceOver Safari Desktop
[ ] VoiceOver Chrome Desktop
[ ] VoiceOver Safari Mobile
[ ] Android Accessibility Suite Chrome Mobile

Pull request type

Please check the type of change your PR introduces:

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Does this introduce a breaking change?

[ ] Yes
[x] No

Other information

The ellipsis seem to be broken

working on it

Codecov Report

Merging #1516 (47821d4) into master (ab917b0) will decrease coverage by 1.62%.
The diff coverage is 62.05%.

@@            Coverage Diff             @@
##           master    #1516      +/-   ##
==========================================
- Coverage   54.85%   53.22%   -1.63%
==========================================
  Files          49       82      +33
  Lines        1659     3438    +1779
  Branches      406      958     +552
==========================================
+ Hits          910     1830     +920
- Misses        671     1474     +803
- Partials       78      134      +56

Impacted Files
Coverage Δ

...mponents/sbb-accordion-item/sbb-accordion-item.tsx
0.00% <0.00%> (-37.21%)
:arrow_down:

src/components/sbb-clock/sbb-clock.tsx
0.00% <0.00%> (ø)

src/components/sbb-link/sbb-link.tsx
59.57% <ø> (-31.86%)
:arrow_down:

src/components/sbb-logo/sbb-logo.tsx
0.00% <ø> (ø)

src/components/sbb-menu-action/sbb-menu-action.tsx
61.90% <ø> (ø)

src/components/sbb-menu/sbb-menu.tsx
25.89% <ø> (ø)

...ts/sbb-navigation-action/sbb-navigation-action.tsx
71.42% <ø> (ø)

...onents/sbb-navigation-list/sbb-navigation-list.tsx
84.00% <ø> (ø)

...ts/sbb-navigation-marker/sbb-navigation-marker.tsx
53.19% <ø> (ø)

...mponents/sbb-checkbox-group/sbb-checkbox-group.tsx
30.61% <30.61%> (ø)

... and 65 more

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

pushed fixes for ellipsis + active state + focus outline + minor bug on firefox

repo: lyne-design-system/lyne-components


text:
NameError (uninitialized constant DeviseTokenAuth::Concerns::User::BCrypt)

I get error when doing multiple API requests in my ROR application running this gem which is deployed on heroku using Puma (based on this article https://devcenter.heroku.com/articles/deploying-rails-applications-with-the-puma-web-server). Especially the error occurs when I have set Puma parameter -w (defining number of workers) to amount bigger than 1. Interestingly the error does not occur when I have set parameter -t (number of threads) to amount biger than 1. So it is probably solely connected to web concurrency defined by puma workes. Please see below details of the error:
app[web.1]: NameError (uninitialized constant DeviseTokenAuth::Concerns::User::BCrypt):
app[web.1]:   vendor/bundle/ruby/2.0.0/gems/devise_token_auth-0.1.30/app/models/devise_token_auth/concerns/user.rb:111:in token_is_current?' app[web.1]:   vendor/bundle/ruby/2.0.0/gems/devise_token_auth-0.1.30/app/models/devise_token_auth/concerns/user.rb:86:in valid_token?'
app[web.1]:   vendor/bundle/ruby/2.0.0/gems/devise_token_auth-0.1.30/app/controllers/devise_token_auth/concerns/set_user_by_token.rb:40:in set_user_by_token' app[web.1]:   vendor/bundle/ruby/2.0.0/gems/devise_token_auth-0.1.30/lib/devise_token_auth/controllers/helpers.rb:115:in current_user'
app[web.1]:   vendor/bundle/ruby/2.0.0/gems/devise_token_auth-0.1.30/lib/devise_token_auth/controllers/helpers.rb:103:in authenticate_user!' app[web.1]:   vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:424:in block in make_lambda'
app[web.1]:   vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:143:in call' app[web.1]:   vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:143:in block in halting_and_conditional'
app[web.1]:   vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:229:in call' app[web.1]:   vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:229:in block in halting'
app[web.1]:   vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in call' app[web.1]:   vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:166:in block in halting'
app[web.1]:   vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:229:in call' app[web.1]:   vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:229:in block in halting'
app[web.1]:   vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:86:in call' app[web.1]:   vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.9/lib/active_support/callbacks.rb:86:in run_callbacks'

I am having this issue aswell

thanks @andersonbrandon

@booleanbetrayal any plan to release new gem version?

Would like to get a new gem version out in the next couple of days, but am waiting for one changeset to make it in. In the meantime, you could always point to master:
gem 'devise_token_auth', :git => 'https://github.com/lynndylanhurley/devise_token_auth.git', :branch => 'master'

ok, thanks!!!

authors: booleanbetrayal danielBlowingNose salmanasiddiqui toshimaru

license: WTFPL


text:
⚠ App has degraded performance

In aa42580, App (https://mesirve.app) experienced degraded performance:

HTTP code: 200
Response time: 395 ms

Resolved: App performance has improved in 45a4b08.

repo: lynot/mesirve-status


text:
💡 Implement React Testing Library

Feature Request 👨🏼💻
Implement React Testing Library for project testing 🧪
Use Case ✍🏼
As developers, we want to ensure the stability and reliability of our project by implementing a robust testing framework. By introducing React Testing Library, we aim to facilitate the testing process and improve the overall quality of our codebase.
Possible Solution 💡

Install React Testing Library as a project dependency.
Create separate folders for the tests.
Integrate testing into the project's development workflow.
List all current components that need to be tested (make US 🏷)

Components To Test :
/App

Header
Footer
NavBar
LayerByMode
CopyUrlButton
Code
ActiveLink
/utils

encodedObjectValues
formatUrlWithQuery
loadFont

/hooks

useInputChange
useInputDateChange
useSelectedFont

/forms

colorInput
FontPicker
input
inputDate
selectInput

/remotion

/molecules

AvatarWithCaption
IconWithCaption
TalkDetails

authors: Boyadjie CruuzAzul


text:
去除搜索结果中无版权的音乐

发现现在的搜索结果中会出现无版权的音乐，然后播放会提示请求异常之类的提示。能否考虑直接将无版权的音乐在搜索结果中去除或者提示出来呢。

这个是接口问题，我也不知道哪些有版权哪些无版权，不打算处理这个问题

authors: lyswhut maoshibai

repo: lyswhut/lx-music-desktop


text:
功能添加请求:1、歌手专辑页面;2、歌手所有单曲页。

1、专辑页可以更好定位歌手某专。比如:今天我想听《八度空间》,明天我想听《七里香》(手动狗头);
2、歌手所有单曲页。是为了更好(懒)的听当前歌手的所有歌曲或下载。比如:今天我想沉浸在某胖伦的音乐海洋,不许其他任何人 打扰。(再次狗头)

太对了，强烈请求添加，呜呜呜


text:
Ray caster output tensors size

Hi @lzhnb,
Thanks for the library. I am trying to employ it to do some ray casting on meshes. The question I have is what size the depths, normals, and primitive_ids tensors should have? I tried to initiate the tensors with torch zeros of size [n, 1], [n, 3], and [n, 1] accordingly but get wrong outputs consisting of all 10 for depths, -1 for primitive ids, and 0 for normals.
Thanks in advance.

Nevermind, seems like my rays were just not pointing onto the surface. Upon further inspection I found that everything works fine.


text:
Update package.json

Hi @m-avagyan,
There is missing react-i18next package in dependencies,
and @types/react-i18next (This is a stub types definition. react-i18next provides its own type definitions, so you do not need this installed.) here
Thanks

Hi @rkmsnc , thanks for contribution 🙌

authors: m-avagyan rkmsnc


text:
[WIP] Add ICMPv4 sockets

Add support for ICMP sockets
Add tests for ICMP sockets
Rename proto-type features to socket-type
Update documentation

Resolves: #64

See src/socket/icmp.rs:137-174 for the updated API using bind.

@dlrobertson The updated API doesn't look quite right. Shouldn't you be binding to the identifier field in the IP header rather than IP endpoint? Imagine you are implementing a traceroute program. With the current API this is completely impossible.

To send and receive ICMP messages that are not associated with a specific TCP/UDP port number (e.g., Echo, Echo Reply, Timestamp, Timestamp Reply, Information Request, Information Reply), the socket has to be bound to a specific ICMP identifier. The ICMP identifier is a 16-bit field present in bytes 5/6 in the header of these messages. Only messages containing the right identifier can be sent or received through a safe raw ICMP socket of this type.

So it isn't the identifier in the IP header (I was wrong in my previous comment) it is the identifier in the Icmp message. I used the IpEndpoint port value for consistency with other implementations and for the case where you're binding to ICMP error responses to a UDP port. Then the socket creation takes an additional parameter that determines how the port value of the bound IpEndpoint works. As a result, the current API includes the following two cases.
Bind to ICMP error responses for UDP packets sent from port 53.
use smoltcp::socket::{Socket, IcmpSocket, IcmpSocketType};
// Created with type Udp. IpEndpoint::port is truely a port.
let mut icmp_socket = match IcmpSocket::new(rx_buffer, tx_buffer, IcmpSocketType::Udp) {
     Socket::Icmp(socket) => socket,
     _ => unreachable!()
};
icmp_socket.bind(53).unwrap();

Bind to ICMP messages with the identifier 0x1234
use smoltcp::socket::{Socket, IcmpSocket, IcmpSocketType};
// Created with type Icmp. IpEndpoint::prt is actually the 16 bit identifier
let mut icmp_socket = match IcmpSocket::new(rx_buffer, tx_buffer, IcmpSocketType::Icmp) {
    Socket::Icmp(socket) => socket,
    _ => unreachable!()
};
icmp_socket.bind(0x1234).unwrap();

I chose to implement this using a parameter added to socket creation, but this could also be accomplished using an enum passed to bind. I'm starting to realize the use IpEndpoint makes sense for C, but I think it would be more readable if I use some sort of enum.

Ah, I see. Yes, I think a dedicated enum IcmpEndpoint would be best.

How important is it to keep the standard bind API? E.g. How bad would it be if we ended up with something like.
let mut socket = ...
socket.bind(IcmpEndpoint::Identifier(0x1234))

When bind is only given a u16 it gets to be a bit ambiguous. In theory bind could keep the same signature. Then we could implement the setting of the sockets endpoint with something like the following.
match self.socket_type {
    SocketType::Udp => self.endpoint = IcmpEndpoint::Udp(endpoint.into()),
    SocketType::Icmp => {
        let tmp_endpoint: IpEndpoint = endpoint.into();
        self.endpoint = IcmpEndpoint::Icmp(tmp_endpoint.port),
    }
}

There's no "standard bind API", we do not try to implement POSIX. There aren't ICMP sockets in POSIX anyway. So, do the most clear thing.

Rebased on master and updated the ping example. I got it to work on my system, but otherwise I did very little testing of it.

After the comments above are fixed this is ready to be merged.

Thanks for the reviews. The final product was much much better than the first few revisions

authors: dlrobertson whitequark

repo: m-labs/smoltcp


text:
ModuleNotFoundError when importing mpu6050

the smbus installation worked, I was able to test the i2c and that works. I also got no errors when installing through pip install. However as soon as I try to run a script in Python3, it says that:
Traceback (most recent call last):
File "/home/pi/Documents/gyrompu.py", line 1, in
import mpu6050 as mpu6050
ModuleNotFoundError: No module named 'mpu6050'

I've read some threads about similar issues and it looks like it's all coming from using Python 3

seems like the issue is within Python because it is working when I'm using a script that's located in the same directory as the mpu6050.py

same issue

@sutanu86 Did you install the package? If so, how?
@chancelier did you use the same python version for installing the package as for running it?

Hi, I just released a version that might help for different platform: Jetson nano, raspberry pi, Beaglebone, pyboard, ODROID and more.
It is based on mr Tijn package.
https://github.com/romybompart/py_imu_mpu6050
https://pypi.org/project/py-imu-mpu6050/
Now that is working in different platform I will add self_calibration functions and
Magnetometer support

git clone https://github.com/Tijndagamer/mpu6050.git
cd mpu6050
sudo python setup.py install

Hello, you can see what is the directory that save the files when you install the mpu6050, for example in my case add in ./.local/lib/python2.7/site-packages... if you run you can try to run with python2 <filename.py>

git clone https://github.com/Tijndagamer/mpu6050.git
cd mpu6050
sudo python setup.py install

This didn't work for me.
"ModuleNotFoundError: No module named 'smbus'"

authors: EbGu3 JohnAllen MarCixn chancelier gwonglapierre m-rtijn romybompart sutanu86


text:
fix: signature for pairwise mapping

Fixed signature for map_pairwise_serial! and map_pairwise_parallel! for CellListPair type.
Currently, the package fails for the following example:
using CellListMap

box = Box([100,100,100],20)
b1 = [[100,100,100] .* rand(3) for _ in 1:10]
b2 = [[100,100,100] .* rand(3) for _ in 1:10]
cl = CellList(b1, b2, box)

CellListMap.map_pairwise_serial!((x,y,i,j,d2,output)->output, nothing, box, cl)

because keyword show_progress is by default show_progress which is not defined elsewhere.

Please let me know if you experience any other issue. Thanks again.

authors: drelatgithub lmiq


text:
awesome font url broken for ipv.save(offline=true)

I get the following error:
HTTPError: 404 Client Error: Not Found for url: http://fontawesome.io/assets/font-awesome-4.7.0.zip

Hi Timo,
that should be fixed in master, by https://github.com/maartenbreddels/ipyvolume/pull/104
cheers,
Maarten

authors: TimoFriedri maartenbreddels

repo: maartenbreddels/ipyvolume


text:
Nudge app appears off center when it's opened on an external monitor, then the user disconnects from monitor

When an update is past due, Nudge cannot be dismissed by the "Later" or "I understand" buttons (expected). However, if the user is working off an external monitor, when they unplug and work on the main laptop screen, Nudge does not recenter itself. This prevents the user from fully see and interact with Nudge.
Possible fix: https://developer.apple.com/documentation/appkit/nswindow/1419090-center

I think I have fixed it: https://github.com/macadmins/nudge/commit/ce198c101ff2e2758eed6e1c38be1d6d5a8fe87e
Please try this version: https://github.com/macadmins/nudge/releases/tag/v.1.0.0.02202021001333

It took two commits, but confirmed with @macbm that this fixes it. It will take Nudge 60 seconds to fix this as it's tied to the nudgeRefreshCycle key that defaults to 60 seconds, but that's the best I can do without increasing CPU usage and polling this constantly (which I don't think is worth the effort).

authors: erikng macbm

repo: macadmins/nudge


text:
🛑 MacManager (portal.macalegin.com) is down

In 03f3ebd, MacManager (portal.macalegin.com) (https://portal.macalegin.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MacManager (portal.macalegin.com) is back up in f11c4c2 after 9 minutes.

repo: macalegin-admin/status


text:
Searchbox showing incorrect options for some region queries

Type 1-1 in the search box and the first option shown is 1--19-21.

It's suggesting the 20b region around position 1 in chromosome 1, so chromosome 1, start -19, end 21.

repo: macarthur-lab/gnomadjs


text:
npm release is out of date

https://www.npmjs.com/package/angular-selectize2 reports version 1.2.3.
Please release an updated version for npm.

It looks like you tried to update package.json to include the 3.0.1 version number but the v3.0.1 tag is below that commit.  So when npm looks up the v3.0.1 tag, it gets the v3.0.1 code (I think) but the package.json file that gets downloaded still says v.1.2.3, which can lead to issues when using npm or other tools like npm-shrinkwrap cuz they'll get tripped up on the version number in that file.  Perhaps just moving the git v3.0.1 tag a few commit forward would help.  Or publishing a v3.0.2 with everything in sync?

Agreed, I've created #151 to add a main entry to package.json, but it won't help if npm isn't being updated.

I think you should be able to reference the GitHub repo directly in your package dependencies if npm isn't current.

I wonder if this is the reason that I can't get it to load within my app.js file while using webpack...

authors: SteveShaffer adiakritos avaragado chrisparton1991 cudasteve


text:
Fix Hungarian default date format and add Hungarian translations

Hey,
I fixed the Hungarian default date format as it was incorrect, you can find more information here:
https://en.wikipedia.org/wiki/Date_and_time_notation_in_Hungary#Date
Also I added translations for the Hungarian language!

Thank you @tamasori, since I am going to release a more stable version soon, I will keep this PR on hold and apply your changes directly. I will add you as contributor for reference

Ok, thank you @macmotp

All your changes have been included into the new release, thanks!

authors: macmotp tamasori

repo: macmotp/locale


text:
Bug displaying unicode characters above BMP with "syntax on"

From @GoogleCodeExporter on March 16, 2015 9:26
What steps will reproduce the problem?
Set syntax on (latex for instance) and add a calligraphic A in math mode
(U+1D49C) between parenthesis, itself and between dollars $(A)$. I use
EversonMono font.

What is the expected output? What do you see instead?
I expect it to be displayed properly but sometimes, a space is displayed after
the A, shift the rest of the line up to the $

What version of MacVim and OS X are you using (see "MacVim->About MacVim"
and  "Apple Menu->About This Mac" menu items, e.g. "Snapshot 40, 10.5.6
Intel")?
Snapshot 73

Please provide any additional information below.

Attached the screenshots of normal buggy display, normal display and syntax off
display.

Original issue reported on code.google.com by harold.c...@gmail.com on 9 Jan 2015 at 2:09
Attachments:

bug1.tiff
bug2.tiff
bug3.tiff

Copied from original issue: douglasdrumond/macvim#524

For what it's worth, I can still reproduce this as well as of snapshot 76:

Copy this character: 𝒜 (the Unicode character referenced in the original post; hopefully Github preserves it).
Launch MacVim, paste the character inside a set of parentheses and type some text after (so you have a line like "(𝒜) hello." Make sure there's a line below this text.
Exit insert mode, move the cursor to the start of the line. Move left and right between the first and second lines and note how the display of the line shifts, sometimes visually truncating the last character in the line.

I can't reproduce it.

@jpetrie could you write more specific way to reproduce the issue? for example

Open an empty MacVim window
Enter insert mode
Paste "(𝒜) hello." and enter return.
Input "aaaa"
Exit insert mode
...

I can still see it by doing the following:

Make sure the Core Text renderer is enabled.
Launch MacVim or otherwise open a new, empty buffer.
Enter insert mode.
Paste the text inside quotes: " (𝒜) test" (that's space, open-paren, 𝒜, close paren, space, 'test')
Exit insert mode
Use h and l to scrub the cursor along the line, particular to the start of the line, observe the rendering artifacts.

what is 'the rendering artifacts'?? snapshot-81, 10.11, I can't see any issue. could you record screencast?

@jpetrie are you using snapshot-80 or earlier version?

snapshot-81 has no problem.

Yeah, it's fixed in 81+.

authors: douglasdrumond jpetrie splhack

repo: macvim-dev/macvim

license: Vim


text:
Refresh causes unknown endpoint

Current use of React BrowserRouter can not reload correctly after refresh

Could be fixed with React HashRouter

Maybe  redirect to "/" url.

Fixed with "/* endpoint that returns index.html from build.

Fixed with "/* endpoint that returns index.html from build.

repo: macwille/club-webstore


text:
Handle failed image upload in image block

If a the image upload fails, Sir Trevor will still create an empty image block, which can cause rendering problems.

That's an interesting one, if I have a failed image upload I still end up seeing the image (now as a base64 file) in an image block but adds a warning to inform that the image failed.
Although thinking about it, I don't use the default image block I've been using Image-extended so that might have something to do with it.
Admittedly, there could do with a way of replacing the uploaded image block without first removing it but that's more of a usability issue than anything else and isn't much of an issue at that.

Going through old issues as part of a block creation / config idea i'm working on.
It'll address bad uploads and allow re-uploading without deleting the block. Also you'll be able to say whether the image element is required, which will allow us to force re-upload or the user will need to delete the block before being able to save and submit the data.
As a side note. This would make image blocks easier to build rather than replicating and editing each time someone wants to customise a field.

Coolbeans, it's not a critical end of the world as we know it kinda issue but It's nice to know it's being looked at.

@raffij Is this feature still in progress?

This can also happen with a video block.

I thought the validation regex tweaks prevented that from happening on the vids? I'll see if i've got time this weekend and see if I can see how to validate the video block

@SgtOddball it's something i need to fix anyway for one of our projects.
The decision is whether an invalid video block should be ignored, or fail validation before a url is posted.

Ahh ok, I'd think that invalid blocks should be ignored otherwise a video link that becomes invalid later on could cause issues as it's already been accepted previously as valid (unless it gets re-evaluated each time the block is rendered).

That's my thinking too.

Just stumbled into this too. It seems that the current image block can no longer detect if an image upload failed in any way. The Promise will always trigger the success method, no matter what the server responded.
So, it is completely possible that i read the code wrong, but the image block (and maybe other blocks using the uploader and/or cancellable-promise) is no longer able to react to any problems during upload.

authors: SgtOddball ToBe998 ilyaporopudas raffij rnjailamba

repo: madebymany/sir-trevor-js


text:
Wrong RFC state

http://why-cant-we-have-nice-things.mwl.be/events shows https://wiki.php.net/rfc/invalid_strings_in_arithmetic as implemented, but the vote was canceled and it was put under discussion again.

I'm guessing the code is giving the votes priority over the status at some point, cause from a votes standpoint it would have been implemented. Will look into it.

authors: Anahkiasen kelunik


text:
Fixes render="publish" does not work when used with an expression

based url #354.  This is handy for rendering the main content of a page to get better SEO love.

Perfect. Thanks!

authors: chirino madoublet

repo: madoublet/respond


text:
[IMPAC-603] Create dashboard from template + designer mode

"Create from template" feature
Fix currencies drop-down when dashboard changed
Fix alerts settings button

@xaun I think this is ready - can you please review?

@xaun : up please, the release is tomorrow... thanks.

repo: maestrano/impac-angular


text:
Plague Inc.: The Cure

Game name: Plague Inc.: The Cure
Engine version: i dunno
Platform: PC
Error message: Элемент с тем же ключом уже был добавлен.
Stack trace:    в System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
в System.Collections.Generic.Dictionary2.Insert(TKey key, TValue value, Boolean add)    в uTinyRipper.PlatformGameStructure.AddFile(IDictionary2 files, String name, String path)
в uTinyRipper.PlatformGameStructure.CollectSerializedGameFiles(DirectoryInfo root, IDictionary2 files)    в uTinyRipper.MixedGameStructure.CollectFromDirectory(DirectoryInfo root, IDictionary2 files, IDictionary2 assemblies, ISet1 dataPathes)
в uTinyRipper.MixedGameStructure..ctor(IEnumerable1 pathes)    в uTinyRipper.GameStructure.CheckMixed(List1 pathes)
в uTinyRipper.GameStructure.Load(List1 pathes, LayoutInfo layinfo)    в uTinyRipper.GameStructure.Load(IEnumerable1 pathes, LayoutInfo layinfo)
в uTinyRipperGUI.MainWindow.LoadFiles(Object data)

No promises, but you can try my AssetRipper fork.

No promises, but you can try my AssetRipper fork.

Yooooo, an absolute legend, it works

repo: mafaca/UtinyRipper


text:
Chromium link in regions.html is broken

The link in "Some applications, like Chromium, actually still do this in their own window decorations." doesn't seem to work. The code is still there, but the code search interface doesn't seem to like the "rcl" parameter.
Maybe a link to the git repo is more stable: https://chromium.googlesource.com/chromium/src/+/d7d447a09a95eb7ad399eb8512f677a66e127d69/ui/views/window/window_shape.cc#12

the wonder of the modern web

Replaced with the URI you suggested.

authors: magcius zmodem

repo: magcius/xplain


text:
Clarification request about the algorithm used here vs the Unicode text segmentation guidelines

Hi!
First: Thanks for this handy crate!
I compared the results of this crate against what https://unicode.org/reports/tr29/#Word_Boundaries mandates and was surprised to find some differences. I then checked the algorithm used by your crate and realized that it is a more pragmatic approach.
I wonder whether this is done on purpose (in which case it might make sense to explain it in the README) or whether this is an oversight?
The https://crates.io/crates/unicode-segmentation crate seems to claim to do it the "official" way (Disclaimer: I do not claim that I fully checked every rule and confirmed that it is correct) and comes to the conclusion that the example from the documentation at https://crates.io/crates/words-count should be 18 words long.
What is your thought on this?

This crate doesn't follow the rules in Word Boundaries.
In Chinese composition,  I believe Chinese punctuation marks need to be counted as words. That's why Rust是由 Mozilla 主導開發的通用、編譯型程式語言。 counts 20 words (including 、 and 。).  You can get the same result in LibreOffice Writer.

Also, you can try "a-good-word".
use unicode_segmentation::UnicodeSegmentation;

fn main() {
    let s = "a-good-word";

    println!("{:?}", words_count::count(s));

    println!("{:?}", s.unicode_words().collect::<Vec<&str>>());

    println!("{:?}", s.split_word_bounds().collect::<Vec<&str>>());
}

This crate tells you a-good-word is a word, while the unicode_words function in unicode-segmentation returns ["a", "good", "word"].
In LibreOffice Writer, a-good-word is counted as one word.

Thanks for the clarification! I can totally understand that sometimes a unicode standard may not exactly be what one would want. I have sent a suggestion how to potentially clarify this a bit more in the README :). It might make sense to reference https://crates.io/crates/unicode-segmentation, but I left it out for now and will leave that up to you!

authors: Ablu magiclen

repo: magiclen/words-count


text:
Is the only way to access metrics via serde?

Hi,
Maybe I'm not reading the documentation correctly, but I'm trying to access the metrics generatd by the library (to format and print to the console) and it seems the only way to do so is to roundtrip via some serde serializer? I feel like I'm missing something.

Hi,
Generated metric registries are regular Rust structs, so you can access the different metrics directly, and do whatever reading or transforms you need.  Metrics implement Serialize to hook various back-ends that require different formats, notably Prometheus which is supported since 0.4.

Ok, it sounds like I'm using the library incorrectly? For example, using the library manually I have
#[derive(Default, Debug)]
pub struct Perf {
    fps: Throughput,
}

fn main() {
    let metrics = Perf::default();
    let fps = &metrics.fps;
    loop {
        measure!(fps, expensive()))
        // println!("{}", fps.mean())
    }
}

However, the internal Histogram isn't visible, so I can't call fps.mean()?. Am I supposed to implement my own Throughput type?

Hmm, that's an oversight, I feel like we should expose the inner histogram.  Would you like to open that PR?

authors: magnet nemosupremo

repo: magnet/metered-rs