datanode's data can't be migrated

datanodes's log:
main.go:263: [debug] The Block:210 no chunkdata, so dont need copydata for Migrate

@hbytracy   thanks for issue and pr , I`m closing it


postaxial polydactyly

review these. there may be some confusion. e.g. classification under fingers when can affect toes

reviewed these and I think the classification is okay. closing


Using nkn file transfer question

Hello,
I am trying to get a feel for how to use nkn-file-transfer on my Windows 10 (x64) with Go v1.19.3 for which I was able to compile it with not problems.
In the default start up, I used the below and want to run it in a terminal CLI mode if possible instead of via a browser.
file\test> .\nkn-file-transfer.exe -host
Creating 8 clients...
Client 7.3.1cbd6952514278e2d80cf5c23125bcf47ff9f57632e6cb90ced600c989a1240e connect to node <IP_ADDRESS>:30002
Client 3.3.1cbd6952514278e2d80cf5c23125bcf47ff9f57632e6cb90ced600c989a1240e connect to node <IP_ADDRESS>:30002
Client 6.3.1cbd6952514278e2d80cf5c23125bcf47ff9f57632e6cb90ced600c989a1240e connect to node <IP_ADDRESS>:30002
Client 1.3.1cbd6952514278e2d80cf5c23125bcf47ff9f57632e6cb90ced600c989a1240e connect to node <IP_ADDRESS>:30002
Client 5.3.1cbd6952514278e2d80cf5c23125bcf47ff9f57632e6cb90ced600c989a1240e connect to node <IP_ADDRESS>:30002
Client 0.3.1cbd6952514278e2d80cf5c23125bcf47ff9f57632e6cb90ced600c989a1240e connect to node <IP_ADDRESS>:30002
Client 2.3.1cbd6952514278e2d80cf5c23125bcf47ff9f57632e6cb90ced600c989a1240e connect to node <IP_ADDRESS>:30002
Client 4.3.1cbd6952514278e2d80cf5c23125bcf47ff9f57632e6cb90ced600c989a1240e connect to node <IP_ADDRESS>:30002
Created 8 clients
Start sender in host mode at 1cbd6952514278e2d80cf5c23125bcf47ff9f57632e6cb90ced600c989a1240e

As I see it here, I am connected to 8 neighbors and this is where I have a couple of questions.
1.) To use the nkn-file-transfer.exe, don't I need to have an nkn node running so that it can access the mesh network?
2.) If this is started in "host" mode then do I not need to have a directory for files to be shared so that the other nodes can access, get a directory of those files, and then download one or more?
3.) Where do I specify a directory to store the files on the "host" side?
4.) How do I get a directory of all files across all of the nodes that are in "host" mode so that I can choose one to download?
My thoughts were that this was more of a P2P file sharing that aggregates files from across all nodes running the nkn-file-transfer in host mode, but could be wrong here.
Please clarify so that I have better feel for how it is supposed to work.
Thanks

Is there any updates on how this is used?
In particular, I am interested in the "host/get" mode since I am assuming that the "host" allows the user to get a directory of available files and then "get" one that they want, but could be wrong.
Thanks

This repo is deprecated since we now have better library (e.g. nkn-sdk-go) and ready to use software (e.g. nconnect). You might want to try https://github.com/nknorg/nconnect , it should work transparently with ssh or other tcp based file transfer app.

Thanks for letting me know about the depreciation of this library.
While the nconnect seems to be good for tunneling and such, I actually need a core basic example on transferring files from one address to another because what I am seeking is to find and existing application, or try to develop one, that will be a type of P2P filesystem so that users can place files in a local directory on their PC and those files will be shared throughout the NKN network to others.
I have been looking at various existing P2P filesystem solutions, but it may turn out that I may have to try and write something from scratch and was looking at the "nkn file transfer" as a possible base code to work with on this.
Is there another highspeed file transfer NKN CLI file transfer application around?
I may also need to figure out a type of database solution to integrate into it as well and maybe I can learn something from your chat or messaging examples.
Thanks again

UPDATE:
I am actually looking at Surge now to see if maybe it can be used as a base to build what I am seeking to do.
https://github.com/rule110-io/surge

It seems to have many features that I want already and perhaps I can figure out the code and build it into this new type of system with a mountable virtual drive and also able to work with a local private testnet network as well.
Thanks agian.


chore(release): 1.4.0 [skip ci]

1.4.0 (2020-07-09)
Bug Fixes

chart size fixed (78ffd10)
react versions reverted (03485e2)
release workflow (c77cc58)
resolve release error (519c5f6)
sample-data-west reverted (68816d3)
Trigger release and changelog generation (via GH Actions) (791ed49)
wrong import fixed (40c1a38)

Features

components and css refactor (30de2e1)
components and css refactor (b143f54)
components and css refactor (0cf0368)
components and css refactor (6e40cc2)
components and css refactor (1ecd4a0)
components and css refactor (8f7f0d3)
components and css refactor (a2b2f19)
components and css refactor (f1b511b)
components and css refactor (6f502ad)
components and css refactor (9758829)
styled-components introduced (e8fe1a7)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


docs: fix typo in "Netbird"

Fixes a small typo of the spelling "Netbird" in the documentation.

Thank you for the contribution, @amplitudesxd  :)


"Higher Logic" docs

explains the tricks used for hard and glitched in the logic files. some docs touchups as i saw them, as well.

Do you know about https://www.twitch.tv/collections/GE492sZzKxdd3w ?

https://www.twitch.tv/collections/GE492sZzKxdd3w

... I do now! Aha, ha,,,


feat(telemetry): validate distributions payload and tags

Description
Telemetry Metrics: Validate distributions payload and tags of each metric
Workflow

⚠⚠ Create your PR as draft (we're receiving lot of PR, it saves us lot of time) ⚠⚠
Follows the style guidelines of this project (See how to easily lint the code)
Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
Mark it as ready for review

Once your PR is reviewed, you can merge it ! :heart:

Let me handle the conflict


KVO observer leak when invalidating AFURLSessionManager

Use AFURLSessionManager to schedule some download tasks with completion handlers (in my case, I'm using an AFHTTPSessionManager subclass and creating the tasks with downloadTaskWithRequest:progress:destination:completionHandler:)
Before they all complete, call -invalidateSessionCancelingTasks:YES

For each pending task, you'll get a nice runtime error:
An instance 0x16f71cb0 of class __NSCFLocalDownloadTask was deallocated while key value observers were still registered with it. Observation info was leaked, and may even become mistakenly attached to some other object. Set a breakpoint on NSKVODeallocateBreak to stop here in the debugger. Here's the current observation info:
<NSKeyValueObservationInfo 0x16df01d0> (
<NSKeyValueObservance 0x16df0190: Observer: 0x16d19c70, Key path: state, Options: <New: YES, Old: YES, Prior: NO> Context: 0x24a414, Property: 0x16d403b0>
)

The observers were registered in -setDelegate:forTask: but never removed because the tasks are deallocated without URLSession:task:didCompleteWithError: being called. (Arguably this is NSURLSession's bug.)

i have the  same problem
An instance 0x1455ab80 of class __NSCFLocalDataTask was deallocated while key value observers were still registered with it. Current observation info: <NSKeyValueObservationInfo 0x146118d0> ( <NSKeyValueObservance 0x1464ec50: Observer: 0x14531c50, Key path: operationCount, Options: <New: NO, Old: NO, Prior: NO> Context: 0x0, Property: 0x1464eb70> )
when using AFN3.0  ,only happened once in  iOS 8.4


can not install

Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:
An error occurred while installing hitimes (1.2.3), and Bundler cannot continue.
Make sure that gem install hitimes -v '1.2.3' succeeds before bundling.
Warning: this Gemfile contains multiple primary sources. Using source more than once without a block is a security risk, and may result in installing unexpected gems. To resolve this warning, use a block to indicate which gems should come from the secondary source. To upgrade this warning to an error, run bundle config disable_multisource true.Gem::RemoteFetcher::FetchError: Errno::ECONNRESET: Connection reset by peer - SSL_connect (https://rubygems.org/gems/hitimes-1.2.3.gem)

Looks like a temporary issue of rubygems.
Please reopen if you still experience this!
Works for me:
$ curl -vL 'https://rubygems.org/gems/hitimes-1.2.3.gem' >/dev/null
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying <IP_ADDRESS>...
* Connected to rubygems.org (<IP_ADDRESS>) port 443 (#0)
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
* Server certificate: *.rubygems.org
* Server certificate: COMODO RSA Domain Validation Secure Server CA
* Server certificate: COMODO RSA Certification Authority
* Server certificate: AddTrust External CA Root
> GET /gems/hitimes-1.2.3.gem HTTP/1.1
> Host: rubygems.org
> User-Agent: curl/7.43.0
> Accept: */*
>
< HTTP/1.1 302 Moved Temporarily
< Server: nginx
< Date: Sun, 06 Dec 2015 14:30:43 GMT
< Content-Type: text/html
< Content-Length: 154
< Connection: keep-alive
< Location: https://rubygems.global.ssl.fastly.net/gems/hitimes-1.2.3.gem
<
* Ignoring the response-body
{ [154 bytes data]
100   154  100   154    0     0    128      0  0:00:01  0:00:01 --:--:--   128
* Connection #0 to host rubygems.org left intact
* Issue another request to this URL: 'https://rubygems.global.ssl.fastly.net/gems/hitimes-1.2.3.gem'
*   Trying <IP_ADDRESS>...
* Connected to rubygems.global.ssl.fastly.net (<IP_ADDRESS>) port 443 (#1)
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
* Server certificate: a.ssl.fastly.net
* Server certificate: DigiCert SHA2 High Assurance Server CA
* Server certificate: DigiCert High Assurance EV Root CA
> GET /gems/hitimes-1.2.3.gem HTTP/1.1
> Host: rubygems.global.ssl.fastly.net
> User-Agent: curl/7.43.0
> Accept: */*
>
< HTTP/1.1 200 OK
< x-amz-id-2: jTl0a6H0yHW41DjxNuoMDWslZISCid5u+1OgrSOvDocctJMDBC/ngAvFHOAm26AqSU5TZL3bfco=
< x-amz-request-id: B89C34CE9ECD86CA
< x-amz-version-id: iPNjWNO8Z.vvw8WMKivy1ehQK.Qugau9
< Last-Modified: Sun, 13 Sep 2015 07:49:44 GMT
< ETag: "a2750dd9364f99a74c49be6b39f1324f"
< Server: AmazonS3
< Via: 1.1 varnish
< Fastly-Debug-Digest: 8b49344cd6b5e1b2795c763c4dab577b1669b31ff640c71b28b97951ebbdacae
< Content-Type: application/octet-stream
< Content-Length: 31744
< Accept-Ranges: bytes
< Date: Sun, 06 Dec 2015 14:30:44 GMT
< Via: 1.1 varnish
< Age: 2317
< Connection: keep-alive
< X-Served-By: cache-iad2138-IAD, cache-fra1241-FRA
< X-Cache: HIT, HIT
< X-Cache-Hits: 1, 1
< X-Log-Message: for=request method=GET path=/production.s3.rubygems.org/gems/hitimes-1.2.3.gem fwd="<IP_ADDRESS>" status=200 bytes=31744 cache=HIT, HIT cache_hits=1, 1 timing="(null)"
<
{ [15526 bytes data]
100 31744  100 31744    0     0  21344      0  0:00:01  0:00:01 --:--:--  139k
* Connection #1 to host rubygems.global.ssl.fastly.net left intact


Recurrence Local TimeZone StartTime and UTC Format

The instructions for setting a datetime using the Power Automate Scheduled Flow step Recurrence is unclear when using date timezones. It also, does not correspond with how the Recurrence outputs appear after a flow is run.
The instructions for "Configure Advanced Options" has a disconnect between steps 3 and 4.
_3. In the Time zone field, select a time zone from the dropdown list to specify whether the Start time reflects a local time zone, Coordinated Universal Time (UTC), or other time zone.

In the Start time field, enter a start time in this format: YYYY-MM-DDTHH:MM:SSZ_

If you select a local timezone other than UTC, and then put the Start Time in the format YYYY-MM-DDTHH:MM:SSZ, it will be incorrect because the datetime format is UTC due to the Z at the end.
This also has a disconnect with the outputs when the flow is run, because it will show the local timezone, but the date time is from UTC, but it is not in UTC format. The output will be in (M/D/YYYY, hh:mm:ss tt) and will not show that it is from UTC.
For example, if you set the local timezone to: (UTC +12:00) Auckland, Wellington
And then put the Start Time as: 2023-03-21T09:00:00
This will assume you would like the flow to run at 9:00 am at Auckland Wellington timezone.
However, the output of the flow will show: 3/20/2023, 8:00:00 PM
This is the date time in the UTC timezone without a timezone identifier.
So is the schedule set for 9:00 AM Auckland, Wellington? Or is it set for 8:00 PM UTC?
While the times might be the same now during daylight savings, will it be different during standard time when 9:00 AM in Auckland Wellington is 9:00 PM UTC.
It is a subtle difference and difficult to interpret when scheduling monthly flow runs that do not have additional advanced options like hour of day that are used in weekly or daily schedules.
These instructions need to be clarified about how the Start Time is set and formatted, and what Power Automate will use as the start time in local or UTC.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 5ba2e127-56bc-5910-3af6-30030cf58c1f
Version Independent ID: c8fea93d-3d8d-bf8e-af7d-ae853a936843
Content: Run flows on a schedule in Power Automate - Power Automate
Content Source: articles/run-scheduled-tasks.md
Service: power-automate
Sub-service: cloud-flow
GitHub Login: @MSFTMan
Microsoft Alias: deonhe

Interesting, this would explain why my flow is not running when I expect it to.


hsl() may be broken

Version<EMAIL_ADDRESS>Here is a screenshot from photoshop showing the color codes for a particular blue.

// Outputs: #D6E4FF (Wrong!)
export const blueHsl = hsl(220, 1, 0.92).toHexString()

// Outputs: #004EEB (Correct!)
export const blueRgb = rgb(0, 78, 235).toHexString()

HSB (HSV) is a different color space than HSL.  😄
When I was creating the ColorHelper initially, I thought about adding in every color space, but the math to go between all the color spaces would have bloated the library.  Since web only supports HSL and RGB, I decided that was a good line to draw.

Ah, I see. My bad. Thanks for clearing this up. I’m closing the issue.


UX for loading authorisation

When you hard refresh it takes about a second to check authorization. We could show a dedicated UI for this scenario (for pages that care) so it doesn't look like the site is just slow.

Looks like the slowness is a localhost only issue. I might come back to this if it is seen live.


[docs] Final Doc Tidy Up

Needs a more linear, less complicated flow

All Configs
Better Guides Flow
Ensure Uniform Naming Conventions
Include the "important" points - Reactive stateful single Page checkout, Separate Store
All README's including root

Update Packages with Individual Repos

Generators

Spree SMTP Error

All is done, just need to:

implement generators
add webkit prefixes to logo placement
Ensure YUIDoc stuff is accurate


Make a decision about minimal requirements

PHP
Symfony2

Imho, for v2.0 we should use

PHP 5.6 (supported until 28 Aug 2017) or 5.5 (until 10 Jul 2016)
Symfony 2.7 (as the latest lte)


add storage_tiering_debug_log option to plugin_specific_configuration

The new parameter could be...
"plugin_specific_configuration": {
    "storage_tiering_debug_log" : "true",
}

If the code sees this setting set to true, fire rodsLog() when a data object is moved from one tier to another.
An alternate suggestion is to use a numerical storage_tiering_log_level (probably 6, 7, 8 to match iRODS, in general (default of 5 is relatively quiet)) and write more to the rodsLog appropriately.  6 would write when a file has been moved, 7 would show more context/timing/logic, 8 would add ... ?

Consider the usage of strings mapping back to the rodsLog.h values:
LOG_DEBUG10
LOG_DEBUG9
LOG_DEBUG8
LOG_DEBUG7
LOG_DEBUG
LOG_DEBUG6

which will define the actual log level for the storage tiering plugin.  This will keep the plugin in sync with future log improvements.


Contact Form

Within the profile page for faculty https://metadata.libraries.psu.edu/profile/bio  to upload there should be a contact form or at the very least an email link:
<EMAIL_ADDRESS>for help

I added a "Support" link to the upper-right navigation in the profile management interface. It's just an email link for now. If a separate page with a contact form would be better, then we'll just need to discuss a few details about how that form should behave.


fix the problem of compilation failure on the 3.10 kernel

fix the problem of compilation failure on the 3.10 kernel.

@landley Please help review the code. thanks!

The 3.10 kernel shipped in 2013 and https://landley.net/toybox/faq.html#support_horizon is 7 years. The last LTS bugfix to that kernel (.108) was almost 4 years ago. Why are you trying to build under that kernel, and do you really need lsattr? (Can you switch it off in the .config instead?)
Hmmm... That said, the two symbols were added to the UAPI headers more recently, https://github.com/torvalds/linux/commit/68ce7bfcd995 added FS_INLINE in 2016. The proper fix would be to add #ifndef SYMBOL/#define/#endif stanzas to lib/portability.h with a comment about when they expire.

Except linux/fs.h isn't #included for portability.h to modify, blah. Alright, lemme take a stab at this...

Commit 281f30dde58c


Biolink type-based filtering

Offer a way for users to filter search results in the UI based on their biolink types.
A search on concepts_indexusing the /search endpoint will currently return concepts with unrestricted biolink types. If a user, for example, searches asthma, but is only interested specifically in phenotypes related to asthma, they have to look through a bunch of extraneous results to get to what they really want to see.
There should be some sort of filter menu to zero-in on results more easily in the UI.

There's also the consideration of adding the filtration functionality directly into DUG for more effective API pagination (i.e. if someone searches for asthma but only want to see phenotypes, they may only get 3 results on the first/x page if filtration is done via the UI.
It's probably best to just leave it to the UI, at least for now.

Since this has been added, I've felt that it doesn't quite fit into the overall layout of the page, since it is somewhat demanding of horizontal room which isn't very available in its current position.
In the future, I think it would make sense to refactor the filter select menu UI into a "filter" dropdown that allows for further specialization, e.g.:

Concept type
Between x and y number of studies or >z number of studies

Same for CDEs
Same for knowledge graphs

Perhaps other metrics I haven't thought of
Clear all filters

Again, ideally all of these filters are implemented as query parameters of the /search API endpoint. This facilitates better pagination, especially for highly filtered searches.

For example, if I search heart, I'm going to get 150+ results/10+ pages, but if I filter to only results with 5+ related studies, there may only be 20 results left. This means there's likely a lot of empty pages if implemented client-side through the UI, rather than the API.

In Jira


Jenkins/Github multiple downloads problem

Hi, I'm having an issue downloading each EssentialsX plugin straight from Jenkins, because of the fact that your plugin only seems to support downloading the first jar available, so for example:
Downloading EssentialsX from Jenkins, it only always downloads the first jar and I'm unable to automatically download EssentialsXChat/Discord/Spawn
Downloading AuthMeReloaded from Jenkins, it downloads the first jar, which on the site is actually the javadoc jar, which is not even the plugin.
Please, if it's possible, add support to search a specific jar name or use custom links from where the plugin should download (by that I mean like searching EssentialsX-.jar or EssentialsXChat-.jar on Jenkins and have the plugin download the first jar it sees)
Thank you so much for your plugin as it works perfectly except for this small issue 😊

Thank you for your kind words! And sorry for not replying, as I have been a bit busy lately. Multiple artifacts are an interesting issue to implement as to how to let people choose which artifacts or jars to download. I'll look into adding this feature and fixing AutoMeReloaded Jenkins, and I will let you know why I do it!.

Hey, I am so sorry for not working on this. I have very bad time management and almost forgot about this so sorry. Since I have some free time now, I have made a beta build that would fix the AuthMeReloaded Jenkins while I am working on implementing multiple artifacts. It would be great if you could test it out and let me know if it works as intended.

@Kaerix

Hey @Kaerix I have now also added multi-artifact support in this [build] (https://cdn.discordapp.com/attachments/1103725182314614834/1249880259411841117/autoupdateplugins-7.0.jar?ex=6668e933&is=666797b3&hm=92ecbe7e307aba3a20432e3a9b806dcd983eb7f79bf1a53fc6e657e085868eaa&). For example, if you want essentials chat, you can do
ymlEssentialsXChat: https://github.com/EssentialsX/Essentialsmulti[3]Since its 3rd artifact in the release So basically, for any multi-artifact plugins on github, paste their normal link and add multi[num], where num is the artifact number. So for essentials chat, it would be: https://github.com/EssentialsX/Essentials + multi[3] = https://github.com/EssentialsX/Essentialsmulti[3].

Let me know if you want me to add anything else! This is implemented in the new released version.

Wonderful, thank you so much! Will test later today

Hey @Kaerix So the AuthMeReloaded is already fixed because in code I have made it so that it automatically ignores sources/legacy/javadoc jars and downloads the right one. Though I do see how having a multiartifacts option in there might potentially helpful for other Jenkins. Are you aware of any other Jenkins that have multiple actual plugin jars, such as Essentials? By the way, instead of multi[num], I will just make it so that you only have to put [num] at the end.

Oh, okay! There is also https://ci.lucko.me/job/spark/
For me, EssentialsX jenkins multi downloads would be essential for my server to work, as the only versions that support 1.20.6 are the dev versions, most easily downloaded from their Jenkins page

Thank you for linking me to these jenkins. I see now why multi artifacts would be useful for jenkins as well. Here so I'll do this, to avoid confusion I'll remove auto checks for javadocs/sources/etc jar, but users can specify what jar they want from jenkins as well by doing [num] at end.

Hey @Kaerix Are you able to test this build I have added the Jenkins multi artifact support. Also, now for multi-artifacts, you don't have to do multi[num]; you just need [num] at the end. Please let me know if there are any issues.

Also, one caveat I think could be an issue is for example, when I want to download AuthMeVelocity from Modrinth. I need the Paper version of the plugin. But the Modrinth page hosts both types (Velocity and Paper) of the plugin on one page. Does your plugin distinguish between those or only the latest will be downloaded?

It's great to hear it's working! Also, for Modrinth, I did realize that caveat and have already implemented auto-platform checking and it will download the right platform builds, but I'm glad that you found that out and informed me.


Force shield

Introduce:

Force Glove equipment
Force Shield skill

with preliminary model
preliminarily uses hand gun animations

For future reference: Make pull requests smaller. If refactoring is required for certain features, than those refactors should be done with preceding pull requests.


How to split word document by section?

Closing all issues as this repo is being archived and will no longer be maintained by Microsoft. The project is licensed for continued use and development by forking to your own repo.


There was a bit of noise in the videos recorded by camera plugin on IOS

I use the latest version of camera  plugin to record videos.But I found that there was a bit of noise at the beginning of the videos recorded by the plugin on IOS, while it goes well in Android. Also,I found that the example given by official has the same problem. It seems that it goes well while I use the earphone to collect audio.
I was wondering if anyone is aware of this issue or can offer advice on how to work around them. Thank you!
link

I have the same issue. You can hear it at the beginning of this video.
https://firebasestorage.googleapis.com/v0/b/hiretime-staging.appspot.com/o/video%2F1558181125609..mp4?alt=media&token=1a4c64c3-ae88-4242-81c9-e33b2216c5b0
I also found that when i use the same CameraController to record a second video. This does not happen

@lmgh88 did you find a solution ?
I have the same issue. You can hear it at the beginning of this video.
https://firebasestorage.googleapis.com/v0/b/hiretime-staging.appspot.com/o/video%2F1558181125609..mp4?alt=media&token=1a4c64c3-ae88-4242-81c9-e33b2216c5b0
I also found that when i use the same CameraController to record a second video. This does not happen

I still have no solution yet

I finally found the Solution. On iOS after initialising the CameraController you need to call:
await controller.prepareForVideoRecording();

This removed the weird click for me

I tried it, and still having that noise at the beginning....


String column results end with a zero byte

When reading results of a SELECT with a varchar column, it always ends with an extra zero byte:
nz:admin@localhost:5580/test=> create table test_select (a varchar(256));
CREATE TABLE
nz:admin@localhost:5580/test=> insert into test_select (a) values ('some value without zero bytes');
INSERT 1
nz:admin@localhost:5580/test=> select * from test_select;
┌───────────────────────────────────┐
│                 A                 │
├───────────────────────────────────┤
│ some value without zero bytes\x00 │
└───────────────────────────────────┘
(1 row)

We tried reproducing this issue but we were not able to observe extra zero bytes appended with a string in output of SELECT query. Could you please provide us nzgo logs and relevant program that is causing this issue.

Here's a debug log: nzgolang_nz94009.log
The program is github.com/xo/usql, which calls db.Query(), scans results into a string, and prints them.

I started debugging into rows.Scan() and looks like this is what the driver returns:
> database/sql.(*Rows).Scan() /usr/local/Cellar/go/1.16.2/libexec/src/database/sql/sql.go:3144 (PC: 0x42158cd)
Warning: debugging optimized function
  3139:		}
  3140:		if len(dest) != len(rs.lastcols) {
  3141:			return fmt.Errorf("sql: expected %d destination arguments in Scan, not %d", len(rs.lastcols), len(dest))
  3142:		}
  3143:		for i, sv := range rs.lastcols {
=>3144:			err := convertAssignRows(dest[i], sv, rs)
  3145:			if err != nil {
  3146:				return fmt.Errorf(`sql: Scan error on column index %d, name %q: %w`, i, rs.rowsi.Columns()[i], err)
  3147:			}
  3148:		}
  3149:		return nil
(dlv) p sv
database/sql/driver.Value(string) "some value without zero bytes\x00"

This is how it looks when read through nzsql:
TEST.ADMIN(ADMIN)=> select a, length(a) from test_select;
               A               | LENGTH
-------------------------------+--------
 some value without zero bytes |     29
(1 row)

https://github.com/IBM/nzgo/pull/27 resolved the issue. Closing this.

Great, thanks for the quick fix! Will you be tagging a new version?


LilyGO T-Beam Supreme: add OLED and PMU support

Checklist
By completing this PR sufficiently, you help us to review this Pull Request quicker and also help improve the quality of Release Notes

[x] Please provide specific title of the PR describing the change

Description of Change
This draft PR is created upon request by the TinyUF2 developer.
https://github.com/adafruit/tinyuf2/pull/265#issuecomment-1333278352

can you also include the board to the ci yml file. I should run it locally, but kind of lazy for now.

the board is already in the list since October 17th:
https://github.com/adafruit/tinyuf2/pull/252/commits/b7a53a57d609ef8f0235f983824868e3115a8c39


Remove build dependency on golang

Title: Remove build dependency on golang
Description:
While marketed as always compatible, recent versions of go break especially around how modules work. Rather than embed this problem into Envoy, causing other tensions like go's platform matrix, could we not depend on go? At least for release builds?
These are the files I can see that reference go source. There may be some incidental dependencies on go binaries I'm not aware of, but perhaps could be handled differently or isolated from a release.
./generated/docs/_downloads/ef307e1c6786b51ee38110d4bc3a839b/resource.go
./examples/dynamic-config-cp/resource.go
./examples/ext_authz/auth/grpc-service/main.go
./examples/ext_authz/auth/grpc-service/pkg/auth/users.go
./examples/ext_authz/auth/grpc-service/pkg/auth/v3/auth.go
./examples/load-reporting-service/server/lrs_server.go
./examples/load-reporting-service/main.go
./examples/grpc-bridge/server/service.go
./api/test/build/go_build_test.go

Relevant Links:
https://github.com/Homebrew/homebrew-core/pull/83413 - go 1.17 upgrade of homebrew. Even if it is a red herring, even having someone validate if envoy build works or not costs them hours for the build to complete or fail. Removing the need to think about go, would save a lot of ecosystem time.

@moderation the below did happen and it did say problem downloading go, and it only happened on arm64
==> /opt/homebrew/opt/bazelisk/bin/bazelisk build --compilation_mode=opt --curses=no --show_task_finish
Last 15 lines from /Users/thebots/Library/Logs/Homebrew/envoy/01.bazelisk:
ERROR: An error occurred during the fetch of repository 'go_sdk':
   Traceback (most recent call last):
	File "/private/tmp/envoy-20210827-59011-735pgh/.brew_home/_bazel/6734651a1108d63ae9e743df04c9a20c/external/io_bazel_rules_go/go/private/sdk.bzl", line 98, column 13, in _go_download_sdk_impl
		fail("unsupported platform {}".format(platform))
Error in fail: unsupported platform darwin_arm64
ERROR: Error fetching repository: Traceback (most recent call last):
	File "/private/tmp/envoy-20210827-59011-735pgh/.brew_home/_bazel/6734651a1108d63ae9e743df04c9a20c/external/io_bazel_rules_go/go/private/sdk.bzl", line 98, column 13, in _go_download_sdk_impl
		fail("unsupported platform {}".format(platform))
Error in fail: unsupported platform darwin_arm64
ERROR: Analysis of target '//source/exe:envoy-static' failed; build aborted: unsupported platform darwin_arm64
INFO: Elapsed time: 83.843s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (18 packages loaded, 7 targets configured)
FAILED: Build did NOT complete successfully (18 packages loaded, 7 targets configured)

Whether or not you (an expert) are able to have a perfect working environment isn't the motivation of this issue. It is if the distraction caused by go and there have been, not just this one, is a required distraction or an optional one.
I can already tell you are in favor of keeping it, but let's not pretend everyone else's experiences and time loss never happened

PS it is a good point to try to fix homebrew  #17500 hopefully can switch things to ad-hoc after the fact fixes to proactive part of a release. You'd get less non-experts commenting issues like this if the project team owned all their releases.

I'm going to close this out as this is not going to realistically happen.

You'd get less non-experts commenting issues like this if the project team owned all their releases.

In a world of infinite resources this sounds great. We don't live in such a world. Help appreciated.


Creating a snapshot and running the snap results in "device too busy" error

Environment: on either Ubuntu 20.04 or Fedora 34, I checkout the repo:
https://github.com/kontainapp/guide-examples.git
$ git checkout sm/newexamples
$ cd examples/java)/insta-start-spring-boot/

# build the application docker image
$ make build

# in terminal 1 (runs the application)
$ make run

# in terminal 2 (makes snapshot docker image)
$ make snapshot

# then after making snapshot try to run snapshot docker image
$ make runsnapshot

Shows following errror:
$ docker run --runtime=krun --rm -it --name=KM_instaspringboothello_snap -p 8080:8080 kontainguide/insta-start-spring-boot-snap
15:44:43.805698 km_fs_recover_fd     2066 km      can not dup2 /opt/kontain/java/lib/modules to 4: Device or resource busy
OpenJDK 64-Bit Server VM warning: Exception java.lang.ClassFormatError occurred dispatching signal SIGTERM to handler- the VM may need to be forcibly terminated

From the dup2() man page:
" EBUSY  (Linux only) This may be returned by dup2() or dup3() during a race condition with open(2) and dup()."
It doesn't seem like there should be a race when recovering a snapshot'ed fd.
I guess we could pause and retry the dup2() call.

SOrry, I did not mean to close this.


Battery level status

Hi,
I have a lot of sensor on Smartthings and a sensor battery level %40 and a lot of log battery level low pls add options battery level. If I wanna level %10 send log.

Will do.  I'm away at a conference this week.  I'll see what I can do next week.


Adding a preloader in website

i would like to add a preloader in website please assign me this issue under gssoc

/assign-me

Please don't hardcode a delay...just add the preloader

Please don't hardcode a delay...just add the preloader

okay

I would like to work on this issue, please assign this to me.
@trishanu-init

@TheNikhilRaj I am assigning this to you as @dhairyagothi did not create a PR for this issue

Thank you @trishanu-init

@trishanu-init I would like to work on this issue, please assign to me under GSSoC'24

@Ayesha-Siddiqua88 don't hard code a delay!!....assigned

no one can able to do
please assign it to me i will do it @trishanu-init
and please add level 2 badge at least its hard to add a preloader in those different files of NEXT

@dhairyagothi assigned to you!!


Fix broken tests in Travis CI

Some test runs are still broken:

centos-6
rhel-6
debian-6
opensuse-leap-42
sles-11
sles-12

Yes, I know, I know:-D

I'll have a look once I'm back from parental leave (end of September)


Boxplot tooltip marker color

Version
4.2.1
Reproduction link
https://jsfiddle.net/cdsk5urL/1/
Steps to reproduce
Look at the screenshot or open the jsfiddle and hover on a boxplot. Notice that the tooltip shows as marker color the borderColor.

I believe it should display the color, not the border color, since it is more prominent on the box.
What is expected?
To see the color as the marker color on the tooltip.
What is actually happening?
The borderColor is shown as marker color on the tooltip.

Anyone has a solution on this matter?


⚠ GitLab Server has degraded performance

In a9b5aaf, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 7004 ms

Resolved: GitLab Server performance has improved in de39fa4.


spl: implement try_deserialize for Metaplex accounts to ensure initialization

Currently Metaplex accounts are deserialized using safe_deserialize().
This is unsafe however, because safe_deserialize in turn calls is_correct_account_type() which also accepts uninitialized accounts (checks that the discriminator is either the expected key or Key::uninitialized).
This PR fixes this by implementing try_deserialize for both Metadata and MasterEdition account wrappers and introducing the required manual check.

why would the try_deserialize_unchecked functions use safe_deserialize and not try_deserialize?


[DO NOT COMMIT YET, Experimental] release mode2 (llvm-12-release)

Same changes as in #672, currently forcing Release mode for the purpose of testing. Once it gets a clean bill of health, I will remove the changes in CMakeList.txt in the top dir.

@jenkins-droid test this please

@AlexandreEichenberger can we close?


Discussion: throw debug errors only in developer mode

Redux has a lot of debug checks that are intendent for developers like this checks in dispatch().
This checks are mostly useless in production mode. In think redux can adopt the idea of prop-types and do this checks only in development mode (by wrapping them in process.env.NODE_ENV check so they are removed in production build).
I've made some changes (just commented out all error checks to remove this code from build) to see how it affects production bundle.
Current size of redux.min.js: 6440B (2396B with zopfli)
With error checks removed: 3528B (1487B with zopfli)
So removing this code in production build gives almost 2x decrease of bundle size.
The drawback is that this will break backward compatibility (I don't really think someone relies on this behaviour but anyway).

Dan has said why this is the case before: https://github.com/reduxjs/redux/issues/771#issuecomment-142259143

Why in this project huge checks doesn't wrap into if(process.env.NODE_ENV...)

These checks actually throw exceptions. They're not just warnings. If they were wrapped in if (...), then production and development behavior would differ, which is bad. If developer misses a problem and the problem makes it into production, it will eventually throw (because sanity checks actually check for important mistakes that will cause errors in production), but in a different place. You'll have weird stack traces that you can't possibly reproduce in development. For these reasons, if some behavior throws, it has to throw both in development and production.

I think to restate Dan's point, those aren't just "checks for developers", they are fundamental behaviors of Redux. We detected an error and will throw accordingly. That's not a developer-only concern; it matters in production as well.

Ok, the other idea is to use minified errors like react does
https://reactjs.org/docs/error-decoder.html/

If developer misses a problem and the problem makes it into production, it will eventually throw (because sanity checks actually check for important mistakes that will cause errors in production), but in a different place.

The same thing is also correct for prop-types checks - but they are disabled for production to minify the build. I don't really see big difference here.

Removing errors also greatly affects performance
function counter(state, action) {
  if (typeof state === 'undefined') {
    return 0
  }

  switch (action.type) {
    case 'INCREMENT':
      return state + 1
    case 'DECREMENT':
      return state - 1
    default:
      return state
  }
}

console.time();
var store = Redux.createStore(counter)
for (let i = 0; i < 1000000; i++) {
  store.dispatch({ type: 'INCREMENT' })
  store.dispatch({ type: 'INCREMENT' })
  store.dispatch({ type: 'DECREMENT' })
}
console.timeEnd();

version from master runs this code for 350ms
version with removed error logging runs this code for 20ms

@mad-gooze : I would find it very surprising for error checks to affect behavior that much.
Thus far, you haven't actually shown which code you've even changed.  If you can put together a fork of the Redux repo that shows exactly what you're changing and a benchmarks repo that demonstrates the differences, I can maybe glance at it briefly.  But, I generally agree with Tim on this one.

The benchmark there is a red herring anyways. As we discussed when last changing isPlainObject, dispatch isn't really the bottleneck. It's the subscribers that contain the bulk of the work, typically a UI update with something like React.


rgw: move default bucket quota conf vars to global

"rgw override bucket index max shards" and
"rgw bucket default quota max objects" were in the
client section of the ceph.conf and not being
applied, this commit moves them to global
Resolves: bz#1391500
Signed-off-by: Ali Maredia<EMAIL_ADDRESS>

jenkins test kraken-ansible2.2-update_cluster


items.map is not a function (defaultValue vs defaultItem issue)

Description
Error appears in admin sidepanel editor when adding then editing a list of objects, whereby the nested object in the list also has a list of objects, and those objects have a ui prop in the schema
Steps to reproduce
import linkSchema from "../schemas/linkSchema"
import headerSchema from "../schemas/headerSchema"
import bodyRichText from ".tina/schemas/bodyRichText"
import tableSchema, { tableFields } from "../schemas/tableSchema"

const pagesCollection: any = {
  label: "Pages",
  name: "pages",
  path: "content/pages",
  format: "mdx",
  fields: [
    {
      name: "multiTables",
      list: true,
      type: "object",
      fields: [
        {
          type: "object",
          label: "Headers",
          name: "headers",
          list: true,
          ui: {
            defaultValue: {
              colspan: 1,
              bg: "white",
              color: "black",
            },
          },
          fields: [
            { type: "rich-text", name: "name", label: "Header Name" },
            { type: "string", name: "bg", label: "Header Background Color", component: "color" },
            { type: "string", name: "color", label: "Text Color", component: "color" },
            { type: "string", name: "colspan", label: "Colspan" },
            { type: "string", name: "width", label: "Header Width" },
            { type: "string", name: "height", label: "Header Height" },
          ],
        },

Expected result
It should not error when clicking edit of the list item
Actual result
items.map is not a function

Environment
Mac Os 12.4
"@chakra-ui/react": "1.x",
    "@emotion/react": "11.x",
    "@emotion/styled": "11.x",
    "@tinacms/cli": "0.60.25",
    "blitz": "0.45.4",
    "framer-motion": "5.x",
    "lodash": "4.17.21",
    "next-tinacms-cloudinary": "3.4.3",
    "polished": "4.2.2",
    "react": "18.0.0",
    "react-dom": "18.0.0",
    "styled-components": "5.3.5",
    "tinacms": "0.68.11"
  },
  "devDependencies": {
    "@tinacms/cli": "0.60.14",
    "@types/react": "18.0.1",
    "eslint": "7.32.0",
    "husky": "7.0.4",
    "lint-staged": "11.3.0-beta.2",
    "prettier": "2.7.1",
    "pretty-quick": "3.1.3",
    "typescript": "~4.5"
  },

Tinacms Package Versions
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>

Tools

Tool
Version

browser
Chrome 103

os
Mac OS 12.4

node
16.13.0

npm
8.1.0

Seems like I'm able to fix by replacing 'defaultValue' within the ui property to the function 'defaultItem'

Is defaultItem used for a list? or an object? @tinacms/maintainers
This doc says its used for objects:
https://tina.io/docs/schema/#default-value-for-objects
But this doc says its used specifically for lists:
https://tina.io/docs/reference/types/object/#as-a-list

I mean, ideally this should not throw an error, or at least it should warn the user 'hey you are trying to use defaultValue, but you should instead be using defaultItem instead' ?
I somehow managed to fix this by mistake... and i recommend leaving the title of the post as it is so that people who also get this error can find it, at least until this is fixed or a better error message is added.

and i recommend leaving the title of the post as it is so that people who also get this error can find it, at least until this is fixed or a better error message is added.

So correct me if I'm wrong, but I believe the "items.map" is within your page not something within Tina. It's blowing up because there's no default value set, but your page is trying to iterate through it.

No the error is coming from Tina itself

I added some thoughts in this thread on how I'd expect defaultValue vs defaultItem to behave.

We've updated the bahaviour of defaults, so there is no longer a "defaultValue". This bug should no longer be an issue.
https://tina.io/blog/tina-version-0.69.13


Insert link option is selectable even in read-only mode

Description
We have the rich text editor opened in a disabled mode and it works fine but even if the RTE is disabled (i.e. in the read-only mode) the link icon is still clickable. Refer below image -

Please suggest as to how we can fix this.

Is this the only one? Or the paragraph dropdown has the same behavior?

Yes, the issue is for both.


compilation error

I am kinda stuck with this one and can't figure it out.
2usmhalliday2:kustomize-sops halliday$ go build -buildmode plugin -o $OUTDIR/kustomize-sops.so kustomize-sops.go 2usmhalliday2:kustomize-sops halliday$ kustomize build --enable_alpha_goplugins_accept_panic_risk Error: generating legacy configMaps and secrets: secretgenerator: [{{ mysecrets  {[] [] } [{go kustomize-sops [CAT DOG]}]} }]: NewResMapFromSecretArgs: plugins: : plugin.Open("/Users/halliday/.config/kustomize/plugin/kvSources/kustomize-sops"): plugin was built with a different version of package gopkg.in/yaml.v2

i have to do a bit of work, the upstream has changed. Let me make a change to it compiles again.
To workaround, you can checkout kustomize 2.0.1 and then build.
That is the challenge these goplugins create, they area highly brittle.

resolved w/ 18a373d65d51d59497d465c9c4faffc1bee7343a.
updated instructed, added go.mod


[BUG] Fixed depreceated is_ajax

is_ajax was depreceated with 3.1 - see here. This PR fixes the few usages.

@SchrodingersGat ready for merge


Exclude abilities from play log except warrior's

Codecov Report

Merging #83 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #83   +/-   ##
=======================================
  Coverage   90.41%   90.41%
=======================================
  Files          80       80
  Lines        1012     1012
  Branches      154      154
=======================================
  Hits          915      915
  Misses         82       82
  Partials       15       15

Impacted Files
Coverage Δ

packages/warriorjs-core/src/LevelLoader.js
91.3% <ø> (ø)
:arrow_up:

packages/warriorjs-core/src/Unit.js
100% <ø> (ø)
:arrow_up:

packages/warriorjs-cli/src/utils/getLevelConfig.js
100% <ø> (ø)
:arrow_up:

packages/warriorjs-core/src/Warrior.js
100% <100%> (ø)
:arrow_up:

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 58629ad...7440c81. Read the comment docs.


Update main from deepmind

update the main branch from deepmind.

cl/518592927

It's there, isn't it?


why build fail

root@instance-1:/opt/jupyter/study_pytorch/lpth/important_rnn/onnx/Netron-1.1.0# python3 setup.py build
running build
running build_py
error: can't copy 'node_modules/protobufjs/dist/protobuf.js': doesn't exist or not a regular file

Need to run npm install first to restore the packages containing these files.


Add option for including path in all results

@MJCD I don't understand, can you maybe add a more detailed description/examples?

Hi there. Long time and frequent user of walk-sync here. I think what's being suggested here is that it would be nice to optionally include the full path to each file. When I using walk-sync, I almost always end up constructing the full path, like this:
const path = require('path')
const basePath = path.join(__dirname, 'some/dir')
const walk = require('walk-sync')

// extra mapping needed to get full paths
const filenames = walk(basePath).map(relativePath => {
  return path.join(basePath, relativePath)
})

// and when using walk.entries:
walk.entries(basePath).forEach(entry => {
  entry.fullPath = path.join(basePath, entry.relativePath)
  // etc...
})

Adding support for an option like fullPath would be convenient.

I just looked in the source and it appears there's an option called includeBasePath that does exactly this (but only for the default function not for `.entries), which is great! It's just not documented in the README. If this library is still maintained, I'd be happy to open a PR adding this option to the documentation.

1.0.0

🎉

Thanks very much for your assistance on this. Kudos to @stefanpenner


Lint

Hurray for XO v0.41

I did not update since it break the VS code extension 😢. Which makes linting so much harder (must to npx xo before every commit)

Is there an open issue about it? In my case I just had to update the global XO

Closing this in favor of a comma-dangle-only PR

Is there an open issue about it? In my case I just had to update the global XO
I am talking about ⬇
https://github.com/SamVerschueren/vscode-linter-xo/issues/91


Issue VACCUM SQL directive to prevent the DB from keeping old Seeds.

I signed it!

I'd consider this also a security issue (and if not, at least a matter of 'tidiness') to securely delete the seeds, see also the documentation of VACUUM (third bullet in the top list).

Is that semicolon needed? The other instances of mDatabase.execSQL don't end in semicolon.

I've filed this internally as b/129332125 because…
--
FYI: The version in Google Play Store / Apple App store is not the same as this opensource version. They've diverged. This opensource version is also unlikely to end up in the app stores. This open source version doesn't get much love, but I'll accept well-written pull requests. But don't expect this feature to be implemented by Google.

(will merge this anyway after you confirm the semicolon thingy)

Either is good.  Thanks!


reorganize export files

Problem solved
Short description of the bug fixed or feature added
Changes made

[ ] Public API changes: list the public API changes made if any
[ ] Internal API changes: explain the internal logic changes

How to test

[ ] Automated tests: link to unit test file
[ ] Manual tests: step by step instructions on how to test

Contributor NFT
Paste in your wallet address below and we will airdrop you a special NFT when your pull request is merged.
Address:

PR-Codex overview
This PR focuses on syncing in-app wallet exports between web and native platforms.
Detailed summary

Synced inAppWallet exports between web and native platforms
Updated paths for inAppWallet in various files
Added in-app.native.ts for native platform exports

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#3304  👈
#3300
#3298
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @joaquim-verges and the rest of your teammates on  Graphite

Merge activity

Jun 14, 2:49 PM EDT: Graphite rebased this pull request after merging its parent, because this pull request is set to merge when ready.


Add regex to check if name is valid

Restricts to the same names that are allowed for docker containers.
Prevents users from creating services that cannot start because their
names cannot be used as part of docker containers. fixes #897
Signed-off-by: Drew Erny<EMAIL_ADDRESS>

[Current coverage][cc-pull] is 52.98%

Merging [#898][cc-pull] into [master][cc-base-branch] will increase coverage by 0.22%

File .../test/deepcopy.pb.go (not in diff) was modified. more

Misses -9
Partials -6
Hits +15

File ca/config.go (not in diff) was modified. more

Misses +1
Partials +2
Hits -3

File ...chestrator/global.go (not in diff) was modified. more

Misses -10
Partials -4
Hits +14

@@             master       #898   diff @@
==========================================
  Files            70         70
  Lines         11144      11146     +2
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           5880       5906    +26
+ Misses         4437       4420    -17
+ Partials        827        820     -7

[][cc-pull]

Powered by Codecov. Last updated by [30b6317...c537e2d][cc-compare]
[cc-base-branch]: https://codecov.io/gh/docker/swarmkit/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/docker/swarmkit/compare/30b631712fba78747b29ca2b44fb71e04ad8d0b7...c537e2de992c6896dd698c0bfea20344d5696fa8
[cc-pull]: https://codecov.io/gh/docker/swarmkit/pull/898?src=pr

Forgot test. Added them.

I think we should use NamePattern from https://github.com/docker/docker/blob/master/utils/names.go

I agree, but I also don't know how that affects the vendoring...

@dperny We should really restrict these to dns compatible names. Services also have to be used for DNS.
Check out #192.

We should copy-paste that pattern: [a-zA-Z0-9][a-zA-Z0-9_.-].
Also, maybe it's better not to allow the . at this stage. /cc @stevvooe

i'm gonna spend some time tomorrow thinking about a regular expression for dns compatible names. i'll abandon and fall back to just copying the docker regex if it proves prohibitively difficult to write a regular expression.

The regexes in docker/distribution/reference may come in handy.

On Jun 9, 2016, at 20:47, Drew Erny<EMAIL_ADDRESS>wrote:
i'm gonna spend some time tomorrow thinking about a regular expression for dns compatible names. i'll abandon and fall back to just copying the docker regex if it proves prohibitively difficult to write a regular expression.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Ok, I reduced the number of characters to a subset that i know to be compatible with DNS. I removed the _ and . characters as acceptable. This might not be the broadest possible range, but it's definitely safe.

No, sorry, this is still wrong. Domain names cannot end in hyphen, and neither should swarm names.

alright now it's correct.

Bumping this to P0 - it's a blocker

@aluzzardi @stevvooe made changes as suggested.

is there something i can do differently in the future to make sure that i get it right the first time?

This is on us.
Naming, the hardest problem in computer science, is hindered by bikeshedding, semantic discussion, colloquialism, sensitivity, true meaning and even technical considerations.
Not to mention that this PR involves regular expressions.
LGTM. Good job!

@dperny My bad, I've mistaken this for an issue rather than a PR last night, that's why I was asking if someone could get it done.
LGTM, thanks!


Is there a reason for partial package.json in dist directory?

This package seems to ship with a partial package.json in the dist directory because of this line:
https://github.com/wheresrhys/fetch-mock/blob/4b54e6db42a3e87700ef37a27a7a4d7df29cb3d7/Makefile#L50
I was having several weird eslint issue around this package, and I think I've tracked them down to this. This isn't a valid package.json file according to npm docs.
The popular eslint plugin eslint-plugin-import attempts to find package names from resolved file paths:
https://github.com/benmosher/eslint-plugin-import/blob/7aea664b8f6859aa9e8a0d808ab71cf96576f299/src/core/packagePath.js#L15-L18
This means in certain cases eslint will find this bad package.json and not be able to find a package name for the corresponding file.
It seems like ideally there would be no package.json included in the dist directory, but if one is necessary it should probably be complete and valid. If a direction can be decided upon here I can probably work on a PR.

You should really configure your linter to ignore everything in node_modules - you don't maintain this code so shouldn't be linting it.
Those partial package.json's are recommended by various tutorials for publishing mixed esm/commonjs modules.


Update .gitignore

@Damirka432 can you explain this change? I believe Foundry defaults to cache folder unless that changed recently?

Will close this for now, but feel free to reopen if there are additional suggestions. Thanks!


@conda-forge-admin,please add bot automerge

Additional comment:
No response

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/ml-wrappers-feedstock#3.


dbObject doesn't pick up fields provided via many_many through

Affected Version
Affects 4.0 - 4.4.
Description
When you create a relation using many_many and through, and fetch that relation, extra fields on the through-object are dropped into the DataObject's record. However, they aren't recognised as "real" fields and so relObject() fails if you use this. In the example below, this prevents you from putting "Status.Name" as a column on a grid-field that displays them.
Not sure if this is strictly a bug but it does limit the usefulness of many-many through in a modeladmin context.
Steps to Reproduce
class A extends DataObject {
    private static $many_many = [
        'B' => [
            'through' => AB::class,
            'from' => 'A',
            'to' => 'B',
        ],
    ];
}

class B extends DataObject {
}

class AB extends DataObject {
    private static $has_one = [
         'A' => A::class,
         'B' => B::class,
        'Status' => Status::class,
    ];
}

class Status extends DataObject {
    private static $db = [
        'Name' => 'Varchar',
    ]
}

// This will succeed
echo A::get()->first()->B()->first()->StatusID;

// But this will fail.
echo A::get()->first()->B()->first()->relObject('Status')->Name;

Help us with step-by-step instructions.
Expected results
// This would be true
assert(A::get()->first()->B()->first()->dbObject('Status') instanceof Status)

// This would work
echo A::get()->first()->B()->first()->dbObject('Status')->Name;

Implementation notes
When a DataObject is being fetched through a many-many relation, its schema is not the same as a standard fetch of that dataobject - it has additional columns selected. As well as dumping these in the record, schema checks such as those carried out in fieldSpec() should also recognise those fields.
This would also ideally apply to writing records, so that Status could be written on a detail form opened by such a gridfield.

It turns out that this is bogus – I just needed to use "AB.Status" in the above example.


MCUboot not confirm image when flashing by OpenOCD

Describe the bug
When an App uses MCUboot as bootloader it needs confirm any "clean/new" image at first boot. This always worked on Zephyr until pre-2.5.0 version. Now, it was detected that an image flashed using OpenOCD is not confirming images anymore. This was detected with frdm-k64f, nrf52840dk_nrf52840 and nucleo-f767zi. One possible consequence is an infinite loop that tries boot the board.
To Reproduce
Steps to reproduce the behavior:

git checkout master

git fetch upstream

git rebase upstream/master

west update

cd ..

ls
bootloader  modules  net-tools  tools  zephyr

west build -b frdm_k64f -d build/mcuboot-frdm_k64f bootloader/mcuboot/boot/zephyr

west flash -d build/mcuboot-frdm_k64f

west build -b frdm_k64f -d build/app zephyr/samples/subsys/mgmt/updatehub

west sign -t imgtool -d build/app --no-hex -- --version 1.0.0 --pad --key bootloader/mcuboot/root-rsa-2048.pem

west flash -d build/app --bin-file build/app/zephyr/zephyr.signed.bin

see error

Expected behavior
The recent flashed Image confirm at first boot.
Impact
At least stop development with newer Zephyr versions.
Logs and console output
*** Booting Zephyr OS build zephyr-v2.5.0-2840-g363af20fc4a6  ***
I: Starting bootloader
I: Primary image: magic=good, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: primary slot
I: Swap type: none
I: Bootloader chainload address offset: 0x20000
I: Jumping to the first image slot
*** Booting Zephyr OS build zephyr-v2.5.0-2840-g363af20fc4a6  ***

[00:00:03.001,000] <inf> eth_mcux: ETH_0 enabled 100M full-duplex mode.
[00:00:03.002,000] <inf> main: UpdateHub sample app started
[00:00:03.002,000] <inf> main: Confirming the boot image
[00:00:03.002,000] <err> main: Error to confirm the image
[00:00:03.002,000] <inf> main: Network disconnected
uart:~$
[00:00:11.006,000] <inf> main: Network connected
[00:00:11.006,000] <inf> main: Starting UpdateHub polling mode
[00:00:11.006,000] <inf> updatehub: SHA-256 verification on download and from flash
[00:00:11.006,000] <err> updatehub: The current image is not confirmed
[00:00:11.006,000] <err> updatehub: Image is unconfirmed. Rebooting to revert back to previousconfirmed image.*** Booting Zephyr OS build zephyr-v2.5.0-2840-g363af20fc4a6  ***
I: Starting bootloader
I: Primary image: magic=good, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: primary slot
I: Swap type: none
I: Bootloader chainload address offset: 0x20000
I: Jumping to the first image slot
*** Booting Zephyr OS build zephyr-v2.5.0-2840-g363af20fc4a6  ***

[00:00:03.001,000] <inf> eth_mcux: ETH_0 enabled 100M full-duplex mode.
[00:00:03.002,000] <inf> main: UpdateHub sample app started
[00:00:03.002,000] <inf> main: Confirming the boot image
[00:00:03.002,000] <err> main: Error to confirm the image
[00:00:03.002,000] <inf> main: Network disconnected
uart:~$

Environment (please complete the following information):

OS: Linux
Toolchain Zephyr SDK 0.12.3
Zephyr version: 2.5.99 (mainline)

Additional context
All variants that UpdateHub uses are working at b0bd14b5fa. This includes proper boot, network and upgrades. I hope we can find a solution or a possible missing config to re-enable the feature.

To make it easy to reproduce:
git checkout master
git fetch upstream
git rebase upstream/master
west update

Apply this diff
diff --git a/samples/hello_world/prj.conf b/samples/hello_world/prj.conf
index b2a4ba5910..2db4bd6f2c 100644
--- a/samples/hello_world/prj.conf
+++ b/samples/hello_world/prj.conf
@@ -1 +1,7 @@
-# nothing here
+CONFIG_LOG=y
+CONFIG_BOOTLOADER_MCUBOOT=y
+CONFIG_MCUBOOT_IMG_MANAGER=y
+CONFIG_FLASH=y
+CONFIG_REBOOT=y
+CONFIG_IMG_MANAGER=y
+CONFIG_MPU_ALLOW_FLASH_WRITE=y
diff --git a/samples/hello_world/src/main.c b/samples/hello_world/src/main.c
index 6c5c8a27dc..a00464c3ba 100644
--- a/samples/hello_world/src/main.c
+++ b/samples/hello_world/src/main.c
@@ -5,9 +5,21 @@
  */

 #include <zephyr.h>
-#include <sys/printk.h>
+#include <dfu/mcuboot.h>
+
+#define LOG_LEVEL CONFIG_LOG_LEVEL_INFO
+#include <logging/log.h>
+LOG_MODULE_REGISTER(hello_world);

 void main(void)
 {
-       printk("Hello World! %s\n", CONFIG_BOARD);
+       LOG_INF("Hello MCUboot World!");
+
+       if (boot_write_img_confirmed() < 0) {
+               LOG_ERR("Error to confirm the image");
+       }
+
+       if (boot_is_img_confirmed()) {
+               LOG_INF("Everything is working.");
+       }
 }

Move out Zephyr dir:
cd ..

For frdm-k64f
west build -b frdm_k64f -d build/mcuboot-frdm_k64f bootloader/mcuboot/boot/zephyr
west flash -d build/mcuboot-frdm_k64f

west build -b frdm_k64f -d build/app zephyr/samples/hello_world
west sign -t imgtool -d build/app --no-hex -- --version 1.0.0 --pad --key bootloader/mcuboot/root-rsa-2048.pem
west flash -d build/app --bin-file build/app/zephyr/zephyr.signed.bin

*** Booting Zephyr OS build zephyr-v2.5.0-3527-g89ec3d82adf1  ***
I: Starting bootloader
I: Primary image: magic=good, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: primary slot
I: Swap type: none
I: Bootloader chainload address offset: 0x20000
I: Jumping to the first image slot0*** Booting Zephyr OS build zephyr-v2.5.0-3527-g89ec3d82adf1  ***
[00:00:00.005,000] <inf> hello_world: Hello MCUboot World!
[00:00:00.005,000] <err> hello_world: Error to confirm the image
[00:00:00.005,000] <err> hello_world: The current image is not confirmed

For nrf52840dk_nrf52840
west build -b nrf52840dk_nrf52840 -d build/nrf52840dk_nrf52840 bootloader/mcuboot/boot/zephyr
west flash -d build/nrf52840dk_nrf52840

west build -b nrf52840dk_nrf52840 -d build/app zephyr/samples/hello_world
west sign -t imgtool -d build/app -- --version 1.0.0 --pad --key bootloader/mcuboot/root-rsa-2048.pem
west flash -d build/app --hex-file build/app/zephyr/zephyr.signed.hex

*** Booting Zephyr OS build zephyr-v2.5.0-3321-g126da28620d7  ***
I: Starting bootloader
I: Primary image: magic=good, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: primary slot
I: Swap type: none
I: Bootloader chainload address offset: 0xc000
I: Jumping to the first image slot
*** Booting Zephyr OS build zephyr-v2.5.0-3321-g126da28620d7  ***
[00:00:00.005,737] <inf> hello_world: Hello MCUboot World!
[00:00:00.005,798] <err> hello_world: Error to confirm the image

For nucleo_f767zi
west build -b nucleo_f767zi -d build/nucleo_f767zi bootloader/mcuboot/boot/zephyr
west flash -d build/nucleo_f767zi

west build -b nucleo_f767zi -d build/app zephyr/samples/hello_world
west sign -t imgtool -d build/app -- --version 1.0.0 --pad --key bootloader/mcuboot/root-rsa-2048.pem
west flash -d build/app --hex-file build/app/zephyr/zephyr.signed.hex

*** Booting Zephyr OS build zephyr-v2.5.0-3321-g126da28620d7  ***
I: Starting bootloader
I: Primary image: magic=good, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: primary slot
I: Swap type: none
I: Bootloader chainload address offset: 0x40000
I: Jumping to the first image slot
*** Booting Zephyr OS build zephyr-v2.5.0-3321-g126da28620d7  ***
[00:00:00.005,000] <inf> hello_world: Hello MCUboot World!
[00:00:00.005,000] <err> hello_world: Error to confirm the image

CC: @nvlsianpu , @de-nordic , @utzig

The title of this issue suggests the problem is related to OpenOCD, but I don't think that's the case since you've reproduced it on frdm_k64 (pyocd), nrf52840dk_nrf52840 (jlink), and nucleo_f767zi (openocd).

I just run some tests with MCUboot and smp_svr on latest master and everything is working correctly. hello_world does not write the image flags, so I assume you have modified it to use updatehub, which calls boot_set_confirmed from MCUboot, set a breakpoint there and check what condition fails. Also, there's no need to confirm an image unless you're doing a test upgrade, and there's no need to pass --pad to imgtool if you're flashing the image in the primary slot.

Hi @utzig ,
The smp_svr is not part of this use case. The procedure described here should work, at least it worked till Dec/20 for all these boards.
This issue happen when an external agent install a clean image at some slot (in this case at first slot, it could be second). And yes, I'm interested to use boot_set_confirmed because UpdateHub uses test upgrade.
Here, I created a test application and a step by step procedure. If this procedure fail to confirm this MCUboot Hello World test image, it is impossible to use any firmware upgrade strategy with Zephyr that instructs MCUboot to perform a test upgrade.
If there were changes and I need update UpdateHub, it is OK. I just need know what are the proper steps.

I guess I missed much of the previous description, but I confirmed the issue and run it in the debugger, and the issue happens here:
https://github.com/mcu-tools/mcuboot/blob/master/boot/bootutil/src/bootutil_public.c#L586
This line checks that the image copy_done flag is set, which it is not because no upgrade was performed, and thus it fails to write the confirmed flag. Someone can track down where this changed recently /cc @nvlsianpu

@nandojve Thanks for report. I must have overlooked the issue.

@utzig

https://github.com/mcu-tools/mcuboot/blob/master/boot/bootutil/src/bootutil_public.c#L586

This line checks that the image copy_done flag is set, which it is not because no upgrade was performed, and thus it fails to write the confirmed flag. Someone can track down where this changed recently /cc @nvlsianpu
So yes, current implementation of in MCUboot bootutill public is more strict than the one before. I would just remove the check of copy-done flag. Actually if image is running after DFU, it must have been verified.
Only exclusion is image flashed directly by programing interface while mcuboot has disabled primary slot check.


change kernel cfg of drm from y to m to fix the pwm issue #1180

- What I did
I was trying to fix the startup problem of the LCD driver in yocto.And I find that the kernel config in yocto of drm is different
with raspbianOS.So I change it same with raspbianOS. And it works fine.
Interestingly, I also find that the PWM issue I create in https://github.com/agherzan/meta-raspberrypi/issues/1180 was fixed.

Lgtm although I wonder if it will affect images booting out of initramfs

Oh, it's already test with booting out of initramfs. And it works fine.

Interesting. Can you please add your rationale in git log and have a format as per https://meta-raspberrypi.readthedocs.io/en/latest/contributing.html? Thanks.

Thanks for your guidance. The git log is updated now. Please let me know if there is any further work I need to do.

@bigbearishappy is this issue specific to the kirkstone branch? Are you able to give it a spin on the master branch too?

@bigbearishappy is this issue specific to the kirkstone branch? Are you able to give it a spin on the master branch too?

I think it's not a issue specific to kirkstone. I will have a try with master and create a PR if it's needed.

Please do so that we don't miss it as new versions evolve. Thanks.

@bigbearishappy can you please push this to the branches mentioned above as MRs?


ndk armeabi missing

In our project, we use ndk like this
ndk {
abiFilters "armeabi"
}, and it make a "Class not found exception".
And i found Sonar does not have armeabi libs.
Now i manualy copy libs to armeabi, but it is not friendly to other developers in our project.
Will sonar solve this problem in recent release ?

armeabi was deprecated in NDK r16 and removed in r17. We currently don't have any plans on supporting it. It should still be possible to manually build Sonar and the extensions by pointing it at an older SDK and setting the appropriate abiFilters.

All right, may be i can try to write a script or sth to do this~~
Thank u all the way~~


Update package.json

Coverage decreased (-0.1%) to 35.235% when pulling 6e2ea783d73049182b87360785b52348882bbebe on benjin/addDependency into 710d0462d8d81373aa2bc0f36f88955c902cb173 on main.


Changing SD card

Hi, i followed your guide and installed arm9loaderhax & AuReiNAND on my O3DS the thing is i got a 8GB sd card on my 3DS and i want to change it for one with at least 16GB, so i was wondering is there a way to make the change without having to redo all the proccess?
PS: Great work with the guide =D

Read the FAQ :P


Bug: A stale wsserver.py prevents new app from opening

System
MacOS Sequoia 15.1 (24B83) arm64
Issue Description
When attempting to (re)open the ATV Remote app, the main window is briefly visible but then the app crashes/closes.
ps aux | grep "ATV" showed several stale processes still running, interfering with the new app's startup.
Workaround

The pkill "ATV Remote" command will kill all related processes and allows a new ATV Remote.app to start

Stale processes
the347           11467   0.0  0.2 412581424  53088   ??  S     1:12PM   0:02.99 /Applications/ATV Remote.app/Contents/Frameworks/ATV Remote Helper (GPU).app/Contents/MacOS/ATV Remote Helper (GPU) --type=gpu-process --field-trial-handle=1718379636,488578797432545079,6026224567748839752,131072 --disable-features=CookiesWithoutSameSiteMustBeSecure,SameSiteByDefaultCookies,SpareRendererForSitePerProcess,WindowCaptureMacV2 --gpu-preferences=SAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAAABgAAAAAAAoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADYAwAAAAAAANgDAAAAAAAASAEAACgAAABAAQAAAAAAAEgBAAAAAAAAUAEAAAAAAABYAQAAAAAAAGABAAAAAAAAaAEAAAAAAABwAQAAAAAAAHgBAAAAAAAAgAEAAAAAAACIAQAAAAAAAJABAAAAAAAAmAEAAAAAAACgAQAAAAAAAKgBAAAAAAAAsAEAAAAAAAC4AQAAAAAAAMABAAAAAAAAyAEAAAAAAADQAQAAAAAAANgBAAAAAAAA4AEAAAAAAADoAQAAAAAAAPABAAAAAAAA+AEAAAAAAAAAAgAAAAAAAAgCAAAAAAAAEAIAAAAAAAAYAgAAAAAAACACAAAAAAAAKAIAAAAAAAAwAgAAAAAAADgCAAAAAAAAQAIAAAAAAABIAgAAAAAAAFACAAAAAAAAWAIAAAAAAABgAgAAAAAAAGgCAAAAAAAAcAIAAAAAAAB4AgAAAAAAABAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAGAAAAEAAAAAAAAAAAAAAABwAAABAAAAAAAAAAAAAAAAgAAAAQAAAAAAAAAAAAAAAKAAAAEAAAAAAAAAAAAAAACwAAABAAAAAAAAAAAAAAAA0AAAAQAAAAAAAAAAAAAAAOAAAAEAAAAAAAAAABAAAAAAAAABAAAAAAAAAAAQAAAAYAAAAQAAAAAAAAAAEAAAAHAAAAEAAAAAAAAAABAAAACAAAABAAAAAAAAAAAQAAAAoAAAAQAAAAAAAAAAEAAAALAAAAEAAAAAAAAAABAAAADQAAABAAAAAAAAAAAQAAAA4AAAAQAAAAAAAAAAQAAAAAAAAAEAAAAAAAAAAEAAAABgAAABAAAAAAAAAABAAAAAcAAAAQAAAAAAAAAAQAAAAIAAAAEAAAAAAAAAAEAAAACgAAABAAAAAAAAAABAAAAAsAAAAQAAAAAAAAAAQAAAANAAAAEAAAAAAAAAAEAAAADgAAABAAAAAAAAAABwAAAAAAAAAQAAAAAAAAAAcAAAAGAAAAEAAAAAAAAAAHAAAABwAAABAAAAAAAAAABwAAAAgAAAAQAAAAAAAAAAcAAAAKAAAAEAAAAAAAAAAHAAAACwAAABAAAAAAAAAABwAAAA0AAAAQAAAAAAAAAAcAAAAOAAAAEAAAAAAAAAAKAAAAAAAAABAAAAAAAAAACgAAAAYAAAAQAAAAAAAAAAoAAAAHAAAAEAAAAAAAAAAKAAAACAAAABAAAAAAAAAACgAAAAoAAAAQAAAAAAAAAAoAAAALAAAAEAAAAAAAAAAKAAAADQAAABAAAAAAAAAACgAAAA4AAAAIAAAAAAAAAAgAAAAAAAAA --shared-files --seatbelt-client=38
the347           11464   0.0  0.3 450558176 113200   ??  S     1:12PM   5:26.58 /Applications/ATV Remote.app/Contents/MacOS/ATV Remote
the347           11486   0.0  0.2 449989152  64080   ??  S     1:12PM   0:24.55 /Applications/ATV Remote.app/Contents/Frameworks/ATV Remote Helper (Renderer).app/Contents/MacOS/ATV Remote Helper (Renderer) --type=renderer --field-trial-handle=1718379636,488578797432545079,6026224567748839752,131072 --disable-features=CookiesWithoutSameSiteMustBeSecure,SameSiteByDefaultCookies,SpareRendererForSitePerProcess,WindowCaptureMacV2 --lang=en-US --app-path=/Applications/ATV Remote.app/Contents/Resources/app.asar --no-sandbox --no-zygote --num-raster-threads=4 --enable-zero-copy --enable-gpu-memory-buffer-compositor-resources --enable-main-frame-before-activation --renderer-client-id=5 --no-v8-untrusted-code-mitigations --shared-files
the347           11483   0.0  0.4 450364528 148416   ??  S     1:12PM   5:04.16 /Applications/ATV Remote.app/Contents/Frameworks/ATV Remote Helper (Renderer).app/Contents/MacOS/ATV Remote Helper (Renderer) --type=renderer --field-trial-handle=1718379636,488578797432545079,6026224567748839752,131072 --disable-features=CookiesWithoutSameSiteMustBeSecure,SameSiteByDefaultCookies,SpareRendererForSitePerProcess,WindowCaptureMacV2 --lang=en-US --app-path=/Applications/ATV Remote.app/Contents/Resources/app.asar --no-sandbox --no-zygote --num-raster-threads=4 --enable-zero-copy --enable-gpu-memory-buffer-compositor-resources --enable-main-frame-before-activation --renderer-client-id=4 --no-v8-untrusted-code-mitigations --shared-files
the347           11482   0.0  0.0 411177328  15984   ??  S     1:12PM   0:00.11 /Applications/ATV Remote.app/Contents/Frameworks/ATV Remote Helper.app/Contents/MacOS/ATV Remote Helper --type=utility --utility-sub-type=network.mojom.NetworkService --field-trial-handle=1718379636,488578797432545079,6026224567748839752,131072 --disable-features=CookiesWithoutSameSiteMustBeSecure,SameSiteByDefaultCookies,SpareRendererForSitePerProcess,WindowCaptureMacV2 --lang=en-US --service-sandbox-type=network --shared-files --seatbelt-client=47

Further investigation
By manually running start_server.sh, we can see a crash-loop on AttributeError: 'bool' object has no attribute 'keyboard'
$ ~/Library/Application\ Support/ATV\ Remote/start_server.sh
...
 connection is CONNECTING
< GET / HTTP/1.1
< Sec-WebSocket-Version: 13
< Sec-WebSocket-Key: nFleKlZ49DUOFzT08KrZ7g==
< Connection: Upgrade
< Upgrade: websocket
< Host: localhost:8765
> HTTP/1.1 101 Switching Protocols
> Upgrade: websocket
> Connection: Upgrade
> Sec-WebSocket-Accept: /qNpriUUokH9UrwsQdG4bsjDuiE=
> Date: Sat, 09 Nov 2024 17:41:44 GMT
> Server: Python/3.9 websockets/13.1
connection open
= connection is OPEN
< TEXT '{"cmd":"kbfocus","data":""}' [27 bytes]
connection handler failed
Traceback (most recent call last):
  File "/Users/the347/Library/Application Support/ATV Remote/env/lib/python3.9/site-packages/websockets/legacy/server.py", line 245, in handler
    await self.ws_handler(self)
  File "/Users/the347/Library/Application Support/ATV Remote/wsserver.py", line 259, in ws_main
    await parseRequest(j, websocket)
  File "/Users/the347/Library/Application Support/ATV Remote/wsserver.py", line 144, in parseRequest
    kbfocus = active_device.keyboard.text_focus_state == pyatv.const.KeyboardFocusState.Focused
AttributeError: 'bool' object has no attribute 'keyboard'
! failing connection with code 1011
= connection is CLOSING
> CLOSE 1011 (internal error) [2 bytes]
connection closed
...
[repeats until killed]

@bsharper I have not tried deleting that directory, but the pyatv version doesn't seem to be the issue here.
The AttributeError is on the other side of the expression

kbfocus = active_device.keyboard.text_focus_state == pyatv.const.KeyboardFocusState.Focused
AttributeError: 'bool' object has no attribute 'keyboard'

@jklewa Good observation. Both sides of the comparison are from pyatv, active_device is whatever pyatv.interface.AppleTV instance is returned from pyatv.connect, and the other is just a const for the keyboard focus.
Also are you using v1.1.1 or v1.1.3? I think there are some minor fixes in v1.1.3 related to startup sequencing where the app would ask if the keyboard was open without being paired properly. The fact that the error you shared was seeing the initial boolean value for active_device this might be what you're seeing, and using the updated version and re-pairing should fix it.
It's possible only the Airplay protocol is connecting, and the Companion protocol isn't. If you pair with your Apple TV again, you should see 2 pairing screens. Text input is handled by the Companion protocol (I believe), so it's possible if it's only using the Airplay protocol it might not be connecting properly.
You can also try clearing out the settings by opening the app then pressing Cmd+option+i to open Development Tools. Then go to the Console and type localStorage.clear() by the > in the bottom and press enter. Then press cmd+R to refresh the app and close the Dev Tools window. You should see a "first time" popup if this worked correctly. Then pair again and see if the issue is still happening.
Good luck and let me know if it works for you.

@bsharper At the time, I was running v1.1.1. Since then, I've been running a fork of main and haven't experienced the bug again.

I think I've seen this bug, normally pressing Cmd+R causes a refresh/reload and fixes it for me at least.
Ultimately I'd like to get away from using a separate Python library for communication with the ATV. This codebase looks like it does because that's how it worked in earlier versions (there was an integrated node.js library that communicated with ATV directly). Then Apple changed the protocol used to communicate with ATVs and the only library that supported it was the wonderful pyatv. But that means calling Python from electron, which is easier said than done if you want something to be cross platform.
And you're right about the duplicates of the wsserver.py file, I'll try to clean that up. The one in build is turned into pyscripts.js by create_python_embed.js.

@bsharper Though our wsserver.py and such are out of sync in my personal fork, this b538afcb37d2d4f3522d1cb5584bf51857a224df is how I cleaned up the duplicated files in build & server, and made app/pyscripts.js a prebuild step.

Wow that's a lot of cleanup!
If you want to modify wsserver.py or any of those other files while debugging things, you can create an empty file called skip_file_write in the directory where wssserver.py and other files get written to (~/Library/Application Support/ATV Remote for example), and the program won't write those files again until skip_file_write is deleted.

I think I can close this, as the original description doesn't accurately describe what is happening here.
The app isn't "crashing", it's immediately being hidden. Not a great user experience but they can still open to app through the menu bar icon.


Can lax.pow Improve Performance

Hi all,
The exponentiation is a considerable cost of the basis generation. We may be able to curb that by incorporating one of lax.interger_pow or lax.pow instead of using ** which is treated as np.power.

So there have been some interesting developments regarding this. Firstly, lax.integer_pow is not jit comilable. This is not surprising since the source code uses a while loop. The algorithm does appear to be faster than lax.pow so it may be worth investing some time in making this optimisation. However, looking at the algorithm it does not look like I will be able to make it compile without sacrificing the things that make it fast.

Secondly, using lax.pow instead of ** will make a difference I believe because it will kill convert_dtype in the jaxpr.

I don’t think we are especially worried about fast compiled basis generation, and I am surprised if jax and lax elementary arithmetic options make much of a difference?
———————————————
Dr Benjamin Pope (he/him)
Lecturer in Astrophysics
University of Queensland
benjaminpope.github.io

From: Jordan Dennis @.>
Sent: Wednesday, January 4, 2023 2:04:51 PM
To: LouisDesdoigts/dLux @.>
Cc: Subscribed @.***>
Subject: Re: [LouisDesdoigts/dLux] Can lax.pow Improve Performance (Issue #169)
So I have implemented this and it seemed to make a small difference (particularly outside of compilation.
—
Reply to this email directly, view it on GitHubhttps://github.com/LouisDesdoigts/dLux/issues/169#issuecomment-1370436933, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABN6YFJOXYB5AJFSMBQ3ZRLWQTSFHANCNFSM6AAAAAATPG3GOY.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Yeah so, if you look at the jaxpr a lot of the np functions do type checking and extra broadcasting (presumably for safety in the general case). If you check issue #178 you'll see me accelerate some operations by avoiding these assumptions.


Active class on topbar .app-header not header

Changed .sidebar-nav li a, header li a to .sidebar-nav li a, .app-header li a so that it doesn't do that for ALL header DOM elements that have a li inside. Maybe developers include header elements in their custom pages. But it's unlikely they'll include elements with app-header which is part of the navbar styling.

A new inspection was created.

A new inspection was created.

The inspection completed: No new issues


Display output from installation step

Hi @grimbough - I wanted to bring up a suggestion/question about the build/install/check action. The issue we noticed recently is that if the installation of the package fails, e.g. since some dependency is not available, no output is displayed (see e.g. https://github.com/fmicompbio/mutscan/actions/runs/3273531248/jobs/5385851425#step:12:149). As a comparison, if we instead run rcmdcheck() manually, we immediately see what the problem is (see e.g. https://github.com/fmicompbio/mutscan/actions/runs/3279945799/jobs/5400120351#step:12:24). I'm wondering what you think about not redirecting stdout/stderr, or maybe to automatically upload the install-out.txt file as an artifact in case of failure (actually I was trying to do this, but I could not locate the file - https://github.com/fmicompbio/mutscan/actions/runs/3273531248/jobs/5385851425#step:15:20). Or maybe there's a better option that I'm not considering.

I think my intention was for the next line with cat mutscan.install-out.txt was to print the contents and let some see any issues.  However it looks like if it fails then you don't get to run that line, so it's a bit useless.  I'll have a look and get back to you.

Hi @csoneson
It took me a little while to remember why the action was written the way it is.  I don't really want to stop the redirect because pushing the output of the R CMD INSTALL step to a text file and then using that in the subsequent R CMD check is a weird undocumented method that the Bioc build system uses to speed things up.  IIRC there can occasionally be edge cases where this works differently from the standard procedure, which is why I try to emulate it here.
I've added another step to the action that will print the contents of .install-out.txt regards of whether the steps before are successful or not.  Hopefully this helps identify problems that would otherwise be printed to screen e.g.
https://github.com/grimbough/biocActionsExamples/actions/runs/3295837347/jobs/5434855932#step:6:167
I've also added the location of the install log as an output to the action, so you can use that to upload the log as artefact if that's also useful.  You can see an example of that in:
https://github.com/grimbough/biocActionsExamples/actions/runs/3295837347/workflow#L75-81
Those examples of for the devel tag of the actions, but I've merged the changes into v1 and they should already be available to you.  Let me know how it works out.

Brilliant, thank you @grimbough! The printing of the installation log works great (and this is actually enough for us).
Uploading the file seems to cause issues with the path on both Windows and macOS: https://github.com/fmicompbio/mutscan/actions/runs/3296114516/jobs/5435397086. It seems that also in your example there is an issue finding the file, but the upload still works later on (maybe as it's in the working directory rather than the parent directory?): https://github.com/grimbough/biocActionsExamples/actions/runs/3295837347/jobs/5434855932#step:6:166

Thanks for pointing that out.  I do like an error that still produces the correct result!  I turns out that you can't normalizePath() on a file that doesn't exist yet, but you do get back the original input, which was sufficient my example to still find the log file.  I've amended that action to try and do that a bit better.  Hopefully it works cross platform.

Thank you! I think it is still looking one level too high - e.g. in your example here it can't find the file, and in my case it can't find the file /Users/runner/work/mutscan.install-out.txt (here), but /Users/runner/work/mutscan/mutscan.install-out.txt seems to exist (here).
It's not really clear to me what the issue is - could it be that here the job is already executed in the designated working directory, so there's no need to specify it again here?

Ok, I think I've tested this properly now.
The first example you listed above was actually the original, definitely failing, version of the code.  I think I must have it "only re-run failing workflows" and so that part wan't executed again.
None the less the problem still stood, and your suggestion about already running the appropriate directory was correct.  I was then resolving a relative path again that didn't need to happen.  I think I can just get away with a getwd() to find the location that step is working in.
This workflow run tests on all three platforms and also root and sub-folder locations for the package to be tested.  Hopefully I've resolved the issue!

I can confirm that this now also works as expected for our repository. Thanks a lot for the quick fix!


[AutoRelease] t2-azurestackhci-2024-07-25-42542(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/5372
Recording test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=1851

issue link:https://github.com/Azure/sdk-release-request/issues/5372


fix: fetch query when any instance is enabled

This PR fixes #823.
In updateConfig some() was used in a way that doesn't make sense to me. I think this is the way it should be, but let me know if there is anything special about it.

Wonderful!

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Support the Cadl @key decorator

The August MVP target service has model properties with the @key decorator. See https://github.com/microsoft/cadl/blob/main/docs/tutorial.md#built-in-decorators
Design TBD

Per internal discussion, the @key decorator is used primarily for server-side reasons, and should not have a bearing on client generation:

It is used in conjunction with @autoRoute in some interface templates to dynamically create the path for operations based on the fields in the resource and parent relationships between resources.  It would have no bearing on the http representation if you are using @route.  Practically, though, this concept is the same as the idea of a database key, if you were modeling an end-to-end application with a rest api and a database
Generally, for any Azure API linting rules should direct you toward whether you need an @key field in a model or not

We will not do anything to support this in the C# generator at present.


Failed invest transactions: Value out of bounds

Describe the bug
While trying to invest small amounts, I get this error on Ethereum Mainnet:
Transaction failed
value out-of-bounds (argument=null, value={"type":"BigNumber","hex":"-0x0310c9c23a42e565"}, code=INVALID_ARGUMENT, version=abi/5.4.1) Please try again later.

Then hit invest.
See error

Expected behavior
No error and wallet pop up.
Screenshots

Desktop (please complete the following information):

OS: MacOS
Browser: Chrome 103.0.5060.53

Cleaning up old issues, please reopen if applicable


fix grammatical errors and typos

It's awesome, in simple words. I've gone through all the docs and it's pretty fine now. Just a few typos, now fixed

Awesome! Much appreciated :)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[WIP] instrument_server update

Some long required love for instrument_server. Summary of changes:

Remove json dependency, which should lower the number of server dependencies required to install the gem (json inadvertently requires the ruby-dev package on Ubuntu, which installs the build-essential package, which seems like overkill for what we're doing here)
Remove the requirement that an API key be provided when issuing instrument_server restart or instrument_server stop.
Allow configuring the reporting interval, and change the default interval to 30s.
Change the default location of the PID and log files to $HOME/the_file. The previous location, /tmp/, could cause the PID to be cleaned out from underneath the process.
Allow the PID location and log file location to be specified at startup.
Try to ensure the process has started successfully before detaching, and fail loudly if it has not.
Output the number of metrics sent at each reporting interval.
Add a slim framework for writing custom metric scripts (CUSTOM_METRICS.md), as well as some initial examples of how to use it. Documentation as well.
Set the required Ruby version to 1.9.
Monolithic instrument_server script broken apart into several files to ease w/ maintenance

Marked as [WIP] because this many changes deserves some discussion, as well as:

[ ] Test custom metrics scripts to verify desirable behavior
[ ] Add better installation instructions for various OS flavors
[ ] Add other examples as deemed necessary
[ ] Rotate log on user signal

why $HOME/the_file and not /var/run/blahblah?

RE: why $HOME and not /var/run, in some cases /var/run/ can be owned by a higher privileged user, and I don't want to encourage escalating this processes' privileges if it's going to be executing scripts on that user's behalf. I figured the user can always set it to /var/run if they have a pref.

From @spacetc62: The shellwords escaping can be omitted in favor of Process.spawn's arguments passing interface.

might want to have a non-ruby example script, just to show how that would feel?

Reading more about the way to accomplish things like net counters in Docker, it basically means we have to run these scripts as root. I can't say I'm a big fan of ever telling a user to run potentially untrusted scripts as root, I really want this process to execute as a lower privileged user if at all possible.
I'm going to modify the docker script to give instructions to the user on what to do as root to make this happen, I think that's the most reasonable compromise for now.

Lots of updates. Along w/ the gem, we also can ship a tarball or package that has no external dependencies. When you install the package, it also will install itself into system startup. Along with these changes, we now also support loading the config in via /etc/instrumental.yml.
Since we can now come in via system startup, I've also modified the script to drop privileges to a safer user than root when starting up.
I've tested the packages on the following OS':

Ubuntu 10.04, 12.04 14.04, 14.10 (64 bit) - deb installation
CentOS 5 and 7 ( My 6 installation was buggy, can't install on VMWare ) (64 bit) - rpm installation
Debian 5, 6 and 7 (64 bit) - deb installation
CoreOS 653  - tgz installation

I've also added some utility methods to build the tarballs and deb / rpms, and ship them to packagecloud for apt / yum repo distribution. I will add a task to add a build.md file for more information about this.
Installation instructions are now in INSTALL.md, though they are pretty bare atm. I'll flesh out a bit more as I finish cleanup on this branch.

Testing these packages by hand is pretty arduous btw. I feel like there's either a good 'scripting vagrant' or hijack some CI service to run a full integration test of installing a package, adding it to system startup, and running it, such that we have some guarantees on everything running okay.

postgres probably wouldn't be the worst addition to the examples, and I wonder if mariadb/aurora would be easy to adapt for the mysql one.

P.S. this is rad, man

Yeah, definitely agreed re: Postgres. If I can I'd like to have something for all the infra we use in this gem, so we can take advantage of it as well.
And thanks! :)

mongo, mysql, redis, postgres, memcache, (kinesis?,) pusher, (unicorn?,) nginx, kestrel, others?

Cloudwatch would be pretty nice too, I think.

Ready for re-review at this point. May be some more cleanup and some unit tests to add in here, but any future features I'd like to defer to a new release.

Version updates errrywhere, and :+1:

:+1: reviewed, did not run / test locally.

:+1:


Privacy Error: Private Modifier

// zDAI ERC20 States string private _name;   string private _symbol; uint8 private _decimals;
The private modifiers in "ZeroCollateral.sol" does not make a variable invisible. Miners have access to all contracts’ code and data.
Please review for more detail:
https://solidity.readthedocs.io/en/develop/contracts.html#visibility-and-getters

Hey @nruppatel133. Thanks so much for this issue. We're actually deleting ZeroCollateral.sol for an upgraded suite of contracts as this was just a proof of concept.


Add case-insensitive String.Replace overloads

Added overloads for String.Replace so that they now accept
StringComparison and CultureInfo as input parameters.

Hi @ChrisEelmaa, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

@tarekgh
added the same code to osx/windows. I didn't update the native side, as I presume it's already done(the native dlls are coming from coreclr right)?
https://github.com/dotnet/corefx/issues/1271

CC @jkotas

@jkotas could you confirm @ChrisEelmaa question as I have been away from corert for awhile.

I didn't update the native side, as I presume it's already done

@ChrisEelmaa It is done, but we need to pick up the update package that includes your changes. Could you please update the version of Microsoft.NETCore.Native package in src/packaging/netcoreapp/project.json and src/packaging/packages.targets  to 2.0.0-beta-25021-03? (It is the latest version at https://dotnet.myget.org/feed/dotnet-core/package/nuget/Microsoft.NETCore.Native.)

hm didn't as well as expected:
Failure to restore a package: Unable to resolve 'Microsoft.NETCore.App (>= 2.0.0-beta-25021-03)' for '.NETCoreApp,Version=v2.0'.

The package to update is Microsoft.NETCore.Native.  You have made the changes for Microsoft.NETCore.App.

oops my bad, should be good now.

@ChrisEelmaa Thank you!


Added extra Input for embeddings model

Description
Earlier, the engine used same model for embeddings and LLM. Added extra optional input in case someone wants to use separate models for both.
Fixes # (issue)
New Package?
Did I fill in the tool.llamahub section in the pyproject.toml and provide a detailed README.md for my new integration or package?

[x] Yes
[ ] No

Version Bump?
Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

[x] Yes
[ ] No

Type of Change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Added new unit/integration tests
[ ] Added new notebook (that tests end-to-end)
[x] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] I have added Google Colab support for the newly added notebooks.
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I ran make format; make lint to appease the lint gods

@logan-markewich I don't know what is causing this issue. I am new to GitHub so I am not familiar with linting.