mini.bufremove Set dummy file type

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md

Module(s)
mini.bufremove
Description
Hi, it would be nice to be able to add autocomands on the bufremove created buffers.
As for now, when I try to add some functions in an empty filetype, it has an impact on other parts of neovim, so it would really nice to explicitly set a pattern on this file.
Thank you!

Hello!
Sorry, but I completely don't understand what you are asking for.
'mini.bufremove' doesn't create any buffers. Quite the opposite.
Which "file" do you mean in "...it would really nice to explicitly set a pattern on this file"?

Hi! Thank you for the quick answer.
I was thinking if it would be possible to access the winbar remaining after having removed the buffers. In that sense, I was thinking about an option of creating a dummy file when no more buffers are left on my window layout.
What I was trying to achieve is to customize the window bar after all buffers are removed. I would need a way of explicitly get an event on winenter/bufenter when all the buffers are removed, a way of setting a pattern on that event for that concrete window
Thank you!

I was thinking if it would be possible to access the winbar remaining after having removed the buffers. In that sense, I was thinking about an option of creating a dummy file when no more buffers are left on my window layout.

There is always some buffer present as long as Neovim is showing some window. As :h windows-intro says: "A window is a viewport on a buffer.". So as long as there is window ('winbar' of which you want to customize), there is a buffer.
So yes, I stand corrected that 'mini.bufremove' does create a buffer if user wants to unshow the last buffer.
I don't think adding some special filetype to it is a good design, because the whole idea behind that buffer is to be a generic scratch buffer.

What I was trying to achieve is to customize the window bar after all buffers are removed. I would need a way of explicitly get an event on winenter/bufenter when all the buffers are removed, a way of setting a pattern on that event for that concrete window

I would suggest one of at least these choices:

Make your 'winbar' work on scratch buffers (ones with vim.bo.buftype equal to 'nofile').
Make your 'winbar' explicitly count number of open (and possibly listed) buffers. See :h nvim_list_bufs() and :h buflisted().
Use BufEnter or BufWinEnter event to compute that number of buffers.

So with this in mind, unfortunately I don't think this suggestion will end up in 'mini.bufremove'.

Hi, thanks for the info. I will try your suggestions.
My problem with nofile is that it matches other things, but I haven't tried the other things.
Thank you so much!


Add Farnborough College of Technology

Website: https://www.farn-ct.ac.uk
>1 Year IT-related course: https://www.ucfarnborough.ac.uk/course/ba-hons-games-design-and-games-development/GDG1/

@DanielBradbury4 First stage of verification passed, official domain is farn-ct.ac.uk as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@DanielBradbury4 Pull request merged. Thank you!


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 10:12:29 on 2023.05.26
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 3, errors out: 0
Original problem ID: 22563
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=22563

Problem has been resolved in 6m 0s at 10:18:29 on 2023.05.26
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 22563


encrypt handshake

We should consider encrypting the handshake, with a key derived from the password via some suitable KDF. This was suggested in HackerNews.
#82 presents one use case. Another is that it allows us to populate the handshake with more information without needing to be concerned about its potential value to an attacker.
Finally, this closes off some possible attack vectors against the handshake, such as #912 (though note that simply encrypting the handshake is not enough to solve that one; the framing needs to change).

Why do we need some special encryption for the handshake?  The only things actually required to set up the usual encryption for the TCP connection are the other end's public key and the version negotiation.
The key pair is randomly generated.  Having version negotiation unencrypted doesn't seem like a big risk (TLS is plagued by downgrade attacks, but that is due to its long history and rampant parameterization, so I don't think the same concerns apply to weave).

Why do we need some special encryption for the handshake?

Well, that's the topic of the discussion in that HN thread :)

HN-driven development.

quite :)

Well, it would be good to avoid multi-phase handshakes. So if we want to permit arbitrary, potentially sensitive, information in the handshake, then it needs to be encrypted.

Maybe I'm misunderstanding, but you think that avoiding a round trip when establishing a TCP connection is worth having some special encryption scheme for the handshake?

Perhaps, yes.

How about we do the simple thing first, and elaborate it when a user tells us "hey, it would be really great if weave took a few milliseconds less to establish an encrypted connection"?

How about we do the simple thing first

Fair enough. Remind me, what problem are we trying to solve with that? #912? #82? Or something else?

Well, the problem I'd really like to solve is to be able to add to the information exchanged when a connection is established without worrying about whether it is sensitive.
Yes on #912: given what will need to change, it looks like it can be addressed for free (the public key is a fixed length blob, so sending it pre-gob is easy).
No on #82: I think this will address the "to prevent spoofing" part of that issue, but there is a bunch of other work needed there.

@dpw I believe you are working on this. -> assigning


Importing opengsn/gsn cause testcafe typed TestFn to be wrongly typed

Override @types/mocha from opengsn/gsn/node_modules using an empty @types/mocha folder(https://github.com/microsoft/TypeScript/issues/18588#issuecomment-652019495) so we don't have conflicting types from testcafe and mocha in the integration test (causes linting to fail)!

Closing this due to inactivity.


Added UUID to Conversations

UUID is now properly attached to each Conversation. A new UUID is created for each Conversation.

great job!


Treat @ts directives as special

Hey, thanks for a great plugin!
This PR makes the plugin treat comments like
// @ts-ignore Ignore the next line because (long reason exceeding 80 characters and making the line very long)

as special. These comments affect how TypeScript treats the next line and therefore must not be wrapped into multiple lines.

Makes perfect sense, I'll merge your changes immediately. Thanks for the contribution :)
v0.9.3 will be released some time this week including this PR.


Add cluster

Does not redirect or give any prompts after adding a cluster

Added prompts based on the edge cases.

Needs edge case to not allow the cluster to be added if the url plus port is already being used.


My/fix red fixes

Fix capitalising and redirects pointing to categories.

Hi, thanks for this. I am not confident about the first_lower -> firstcap (81aee5416771), but it does look like : (09c5d7880) is a significant problem.  For each problem, it would be really helpful if you could create a bug in our bug tracker Phabricator, so we can better understand the problem and discuss how to reproduce and fix them, with unit tests to prevent regressions.  The direct link to create a bug is https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?projects=pywikibot-core
Also, any software changes need to be submitted to Gerrit, which is our change control tool.
See https://www.mediawiki.org/wiki/Manual:Pywikibot/Gerrit . If you're having trouble with Gerrit, you can use this tool to help getting started: https://tools.wmflabs.org/gerrit-patch-uploader


Managing the instance of target.

Almost API requires the instance of target.
So developer needs to pass the target from the fragment to the fragment.
That's a little inconvenience.

Fixed.


Replace deprecated gulp-util

gulp-util has been deprecated recently. Continuing to use this dependency may prevent the use of your library with the recently released version 4 of Gulp, it is important to replace gulp-util.
Your package is popular but still relying on gulp-util, it would be good to publish a fixed version to npm as soon as possible.
See:

https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
https://github.com/gulpjs/gulp-util/issues/143

thanks for your contribution. sorry for taking such a long time to review this.


Show list of crate features

Showing a list of available features for a crate would be very useful, as it would allow users to at a glance see what features a crate has

Duplicate of https://github.com/rust-lang/docs.rs/issues/590


Update LinkProps to support Next.js 13  component

The current implementation doesn't fully support the latest update to the < Link > component. In previous versions we had to put an < a > as child in the < Link > component and add attributes such as "target" and "title" to it. Since some time this is not needed anymore, but this package doesn't support these attributes yet.

@cvolant can you publish this code on npm?

@mborecki Done.


feat: add ERC721 to genesis state

Pull Request type

Feature

What is the current behavior?
The current genesis state doesn't have ERC721 as part of the genesis state, the PR aims to make support for it along with the relevant test for its mint functionality.
Resolves: #567
What is the new behavior?

The ERC721 implementation will be added, along with tests.
This will also ensure that when the UDC is added to the genesis state #530, even if declare doesn't work, users can deploy ERC721 to Madara.
Does this introduce a breaking change?
NO.

The deployed contract is from openzepplin, the MintableBurnable version is deployed, here is the link for the same.

lgtm 🚀


Refine performance baseline selection logic

Context
See https://github.com/gradle/gradle-private/issues/2571
This PR refines performance baseline selection logic:

Rename minimumVersion to minimumBaseVersion. If minimumBaseVersion is 6.0, a 6.0-nightly can be used.
Throw an error if all versions are filtered out by minimumBaseVersion.
Several unit tests are added to cover these logic.

@wolfs Sure! I'll change the target to release.


Bugdom: Add virtual mouse support, fix inverted joystick on rg351 dev…

Just a quick update to Bugdom.
Added a virtual mouse via gptokeyb to navigate the menus on non touchscreen devices and fix the inverted controls the on the RG351P/M and RG351V"

Checked Zip and .sh file all looking good.


Cleanly shutdown proxy healthchecks on restart

Closes #1503.
This pull request adds a Stop method to the Upstream interface for safely shutting down the running goroutines.
The Stop function is registered with the Caddy controller's OnShutdown handler during setup so that the kill signal is propagated to all consumers.
I added some tests to check that healthchecks don't get sent after upstreams receive their kill signals.

 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.

Hey @MixedMessages - thanks for your PR! Sorry it has taken me a while to get around to it. Been busy preparing some other stuff for a new release in a couple weeks.
I noticed GitHub now shows when people are first-time contributors. That is cool. Thank you for contributing. :)
At a glance, this change looks quite good, but I will need a chance to review it in more detail, hopefully soon, but definitely before the next release -- unless another collaborator beats me to it.

No problem! I updated the PR based on the feedback you gave, so this should be good to go for reviewing again.
I've been programming in Go for ~2 years now, thanks for the compliment on my concurrency skills 😄

Excellent -- thank you very much, @MixedMessages !
I'm going to invite you to be a Collaborator on the repo so you can submit PRs in the future from a branch rather than a fork. You can also help review pull requests. Look forward to having you a part of our community!


Feature request: select multiple transactions

It would be nice if you could select multiple transactions at a time, to add them all to a group, or delete them, etc.

#502


Coverity CID #1271338 Side effect in assertion

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/518/

AU check failed! https://ci.trafficserver.apache.org/job/autest-github/505/

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/509/

Intel CC build successful! https://ci.trafficserver.apache.org/job/icc-github/634/

Linux build successful! https://ci.trafficserver.apache.org/job/linux-github/2097/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/2201/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/762/

[approve ci]

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/543/

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/533/

AU check failed! https://ci.trafficserver.apache.org/job/autest-github/530/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/2226/

Intel CC build successful! https://ci.trafficserver.apache.org/job/icc-github/659/

Linux build successful! https://ci.trafficserver.apache.org/job/linux-github/2122/

clang-analyzer build failed! https://ci.trafficserver.apache.org/job/clang-analyzer-github/787/

[approve ci]


[progressbar]: add support for variable width

Description

Bar loaders should support any width. It seems like we could specify all sub parts as percentages.
Why do you need this feature or component?

Someone asked how to do this with an indeterminate loader and was given the response that they must create their own styles and keyframes.
Additional context

I'm not sure if this is intentional, if so, then we should probably document it on the spectrum site or here.
synced to jira: https://jira.corp.adobe.com/browse/CSS-132

An example that seems to be doing it with just right and left properties https://codepen.io/holdencreative/pen/vEVbwv

FYI, just got back from a dive into css animation performance, we probably don't want to use left/right, it's apparently a general no no
still randomly thinking about this one, maybe something along these lines instead so we can take advantage of translateX
https://jsfiddle.net/snowystinger/r1t76cwv/1/

@pfulton Do you know if this is still an outstanding question or has this issue been resolved during our rework of the component?

@castastrophe with the new tokens definition, it looks like Design has specified that this component should have min and max width values: (see here in Spectrum Tokens)—but, we do make --mod-* prefixed overrides available for this, so if folks wanted to customize it, they could.
I don't know if that fully addresses the topic of conversation here, but it's an answer!

@pfulton Thank you so much!  I'll close this out but @snowystinger, feel free to reopen if needed.


pomatez.exe flagged in virus total

https://www.virustotal.com/gui/file/85fa93ae1cb1db40455f938719bcaa0cd0ea7a93e2aae3d364c09091fecb1fbb?nocache=1

Sometimes the installer can be flagged as that. I'll need to check if thats been flagged up on the electron-builder repo.
I've never heard of Gridinsoft tbh and it seems the only one flagging it up so it may not be raised as an issue. Itll be a false positive though usually if its widespread electron-builder do fix it.

As there don't seem to have been any more reports of this I will assume its gone :) Also it was only Gridinsoft


No issues here just a question

@zedman2000 I was wondering if you know of any mod creator's that keep up to date with their mods because I am looking to get some help with a project as that I am not a mod creator I have a few ideas for a mod pack that I am trying to get created for a YouTube series in the future once blocklauncher is updated for the mcpe 0.16.0 official updated and I will most likely ask you and your friends that play mcpe to come and join me on the journey of a pretty epic modded game play. So I send you this invite in hopes for your help with a huge mod pack

Firstly, please close this so Zhouwei doesn't have to.
Second, thanks for the invite.  I probably will not have time to play.  I have been busy with my family as well as learning to weld.  I would be happy to help you as I can with your "huge modpack".  For the most part, the issue is when modders overlap used items.
Third, @ck1988 I think all mod creators are keeping up with their mods.  I think the only reason there is a DIP in MOD creation/updates now is due to ADDON support as well as the uncertainty of what will happen with 0.16.  Most minor mods can be included using just an ADDON.
Personally, all my mods that I have tested seemed to work as of 0.15.6.  I've not updated anything specifically for 0.15.9.  I know that a few of my mods will need to be updated.  In fact, I'm not even sure if anyone can download my mods.  Google Drive changed some features and I had to move everything to MediaFire, however I never finished that process yet.  I also have 5 mods in the works.  3 Epic Level, 3 normal, 3 small.  1 Normal and 2 small are done (one released), however I need to document and make the instructions / documentation before I release the others.  As that needs to be done, I've just been waiting for 0.16 before I push these out.  In total, I have 6 in various stages of completion.
The 3 EPIC ones, I have 1 about 80% coded but needs a multi-threaded game engine.  I've finished the planning for the engine, but it needs code.  The other one is conceptual but fully planned and already has buy-in from various MCPE celebrities.  The last one is 90% coded, but the HUD (human interface) is giving me trouble.  I worked with a producer/director to ensure that the story behind it is really EPIC!  As for the HUD, I provided what I have to a few other modders and everyone agrees that I am terrible at that kind of thing!  I agree!  However, a wise man once told me "Better is the enemy of good enough" and I think when I have some time, I'll be forging forward with that EPIC mod next.  Although, looking at my notes, it seems that one has an issue whereupon the MCPE game engine is not able to provide enough block information to one of my detection algorithms fast enough.  I'll have to re-write that algorithm to account for that.  Probably just eliminate the feature that is provided by that algorithm.
Of the normal mods, as I said, one is done and just needs documentation.  The other two have enough code to prove that the MCPE game engine can handle what I need it to do.  If I setup an area in a creative world to tickle the code, everything seems to work as intended.  That means I should be able to take that code and wrap in all the logic needed to ensure that someone can't bugger up their game.  Unfortunately, that is the code that takes the longest to write.  Figure if I had time to work on it, ~2 months of weekend nights of code and testing.  Not a lot of time, but time that I've been spending on welding up Go Karts.
The little mods, I released one and then I got busy with life.  The others are sitting there waiting.  One is written, three are conceptual and as I said, one was released.
There's also some stuff I want to do to cleanup my older mods - reorganize features/etc. so that they can play nicer together feature-wise.  Such as the Super Door Operator.  It has the ability to plant things...that should be separated as some people do not need that, or since we have pistons now, some people do not want to have the door feature.  Plus there is redstone that I need to add into it.  All the little things need to get worked out and what-not.
Anyway, feel free to contact me on Twitter to continue this.

@zedman2000 ok I will be closing this hit me up on Facebook Howard Ramey it should be a pic of me and I can give you the details on the mod pack that I am looking to create.

@ck1988 I'm not on Facebook.  I do use Twitter, but only marginally.

@zedman2000 can't find you
Here is my name on Twitter
@RameyHoward


Add N-dimensional board support

Will require vector-based player directions.
Will require rendering the board in console and GUI (though GUI would likely be more user-friendly)


Possible bug with redis database engine

Found a bug? Please fill out the sections below. 👍
Issue Summary
We started getting the following error:
TypeError: Cannot read properties of null (reading 'toString')     at Redis.<anonymous> (/workspace/node_modules/@boxyhq/saml-jackson/dist/db/redis.js:98:58)
When I debugged the issue the keys it is trying to load and which produces the error are starting with 'saml:tracer' and when I look at the database there is no such items anymore and I think this is correct since saml:tracer TTL is set to 7 days in the code. So why the getAll is trying to still load such items and should there at least be some safety check before calling toString for the values.
Steps to Reproduce
Not fully sure about this, but this is our best guess currently what happened. Redis database should be in use naturally to reproduce this issue.

Have faulty SAML configuration and try login (trace produced)
Wait 7 days and try the login again
The following error gets produced since the tracer data has expired and not available in the database

I am not sure is this a bug in the redis engine implementation for not having safety checks for data being null or is the issue somewhere else some other data not getting expired since not sure why it tries to load those keys. I see the createdAt / modifiedAt database paths having the references to the traces, but not the saml:tracer path at all anymore.
If you think this is not a bug any help would be appreciated to figure out what could have caused this situation to happen.
Technical details

Node.js version: 20.x
Saml-jackson version: 1.30.0
Anything else that you think could be an issue.

Thanks for reporting this @sconix, we will investigate it and get back to you.

@sconix I can confirm we are able to reproduce this issue and will work on a fix soon. It is related to the keys we preserve for sort order but don't have the same TTL applied on it.

Thank you! That was what I was able to deduct as well, but was not sure since did not yet have time to look into other engines how they handle this situation or do they etc. I appreciate the quick response!

@sconix Will be fixed in v1.32.0 (currently building)

@sconix  v1.32.0 is ready


feat(doc): Update documentation for vara-buildsetup

Move vara-buildsetup existing documentation from README to docs folder
Add information about various environment variables

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 1

See the complete overview on Codacy


.zarf-state.yaml could use a bit more robustness

Two potential improvements on the current condition of the .zarf-state.yaml file.

Add a check (and warning log / confirmation dialog if not in --confirm) that a .zarf-state.yaml file already exists.

Right now the code only checks for a .zarf-state.yaml file in the current directory. This can create several issues, most of them revolving around the fact that we will be leaving behind lingering state files (zarf destroy only removes the state file if it's in the same directory you ran the command from) and the fact that if we init in one directory and switch directories before the zarf deploy command we will no longer be able to find the state file to reference which leads to an unclear set of logs.

This can be replicated by running the following commands:
./zarf init
mkdir testdir && cd testdir
../zarf destroy --confirm
ls -la ../.zarf-state.yaml -> it is still there after it was supposed to be destroyed.

this is a valid point, I wouldn't be opposed to just doing an /etc/zarf thing instead, might actually be cleaner to put all state things there instead.  Thoughts?

This will get resolved by #153


Message decoding/encoding in workers using transferable objects?

Has this been considered as an alternative to node cluster? #412 Might have less overhead and provide more fine grained parallelism (e.g. a single connection).

Yes and no. Message parsing and formatting will happen in native modules to speed it up, so won't be done via workers.
Closing as we won't be moving it towards workers. We will provide an interface for the native module incase you decide to implement yourself in js.


Switch ASETAgency to new fork

This mod has been adopted by a new maintainer.

https://spacedock.info/mod/3248/ASET Consolidated Agency
https://github.com/StoneBlue/ASET-Consolidated-Agency

Error: 2185 [1] FATAL CKAN.NetKAN.Program (null) - Could not get the mod from SpaceDock, reason: Mod not published. Authentication needed.

Done!.. Sorry it took so long

Done!.. Sorry it took so long

No worries, 3 days is still pretty quick, and it was easy enough to set it aside and do other things. Cheers!


Selendroid as a Maven Dependency

I am leaving this mostly as a help for Java developers who may had trouble getting Selendroid standalone  added to their project as a maven dependency, and got NoClassDefFound exceptions.
Add

org.apache.commons
commons-exec
1.3

to you pom.xml to fix this problem. This is especially relevant if you are getting weird errors like NoClassDefFound.
The issue i want to bring up for the selendroid team is that this maven dependency should have been included with the selendroid-standalone dependency to avoid this particular problem in the first place.
But we're in the process of moving to gradle now - https://github.com/selendroid/selendroid/pull/998
and in that PR it's updating commons-exec to 1.3
So... I don't think we're going to 'fix' the maven parts, since the next release will likely be done with gradle. Going to close this issue for that reason.


[Gally]: master <- dev

Automatically created by Git-Ally

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Complete refactoring: move validate_application_context() from ubkg-api to hs-ontology-api

fyi @shirey @yuanzhou
Statement of problem
The ubkg-api contains code that checks for application context. This code should be in the hs-ontology-api.
Solution

Copy validate.py to hs-ontology-api.
Update pointers in hs-ontology-api to use the version of validate.py in hs-ontology-api instead of the version in ubkg-api.
Remove validate.py from ubkg-api.

@AlanSimmons to complete your solution list, we'll also need to

Move the test calls specified in test_api.sh that use the application_context to hs-ontology-api test script
Move the unit test cases that use the application_context to the hs-ontology-api

@yuanzhou A couple of notes:

You are correct in that the test calls in the test_api.sh script need to be modified. The issue, however, is not that the script contains calls that it should be in hs-ontology-api, but that the calls erroneously contain the application_context parameter. The current set of calls is specific to ubkg-api endpoints. It is a matter of removing from the calls the reference to application_context, not moving the calls themselves.
I'm not sure whether the tests in test_controllers.py would work in their current form. The "expected response" JSONs referenced (e.g., sennet_expected_responses/valueset_organs.json) are ignored by .gitignore. We'd need to regenerate them. This seems like something that we need to rearchitect, so that the expected results of tests are stored in a form accessible to anyone who needs to regression test--i.e., not ignored, but in a path in the repo. I'll create a separate issue.


Super ports searcher.

Hi.
May you consider, when the time allow, the implementation of a port searcher along lines with Gentoo EIX ( it also does some others things that doesn't matter on Ravenports )?
EIX have a pretty nice and informative output with a lot of useful information about the Gentoo ebuilds:

Also, with a tool printing that kind of information about the ports, would be feasible to have the OPTIONS set in the command line instead of ncurses, which I think would be more efficient/faster.
I mean, something along line with:
ravenadm set-options portname -opt1 -opt2 +opt3
Thanks!

Interesting idea! Eix is close to a must-have on Gentoo (no idea why they don't include it in world). In the long run something like this might be worth the effort but I don't see anything like it coming in short term.
Also if you're familiar with Gentoo: Currently ravenadm cannot build packages on that platform. I suspect Gentoo's sandbox to get in the way, but I don't have a deep enough understanding of the topic. Do you perhaps have any idea?

Sorry, I don't and I don't have used Gentoo since about two and a half years. However the guy behind Paludis would certainly point you to the right direction.
He is often ON on Freenode but I cant' remember his nick now ( I think it is 'babyflakes' ). I will look around today and if I find him I point this topic. I've talked with him before about ravenports.

So, he/she said @kraileth is one who have good knowledge of the Gentoo build system. I will try to point him to here ( I am actually mentioning e is here already ).

So, the sandbox can be disabled but it is a better to idea to understand why the sandbox is complaining.
Ps. I do a lot of nick confusion sometimes, as you should already be noted.

@kraileth could you provide/attach some build log on Gentoo? So to make it easier to see what/how it is failing.
Thanks!

You may find something useful on these places:
WIKI Project:Sandbox
Sandbox Source Code

So people at #gentoo-portage ( grknight to be more specific ) told me to be able to build ports/packages on Gentoo it should comply with the Gentoo PMS ( Package Manager Specification ).
Also, they alerted Gentoo does not have a OS sandbox. The building process ( emerge, I suppose ) invoke a sandbox as protection.

@lebarondemerde Thanks for doing this investigation work! I don't think that Raven would ever try to become an official Gentoo package manager - while Gentoo is all about flexibility (and thus building everything from source by default), Raven is focused on providing binary packages (and port options are there to support variant packages).
Raven's Linux packages are in fact usable on Gentoo: After extracting the bootstrap tarball and syncing the repo information, software can be installed. What does NOT work is actually building new packages on Gentoo. If ravenadm is invoked to build some port, strange things happen (it looks like the build chroot cannot be entered or something) and I suspect that Gentoo does something differently regarding chroots.
I think it should eventually be possible to do ports development on Gentoo, too. But it's probably not a top priority issue. I don't have any Gentoo boxes at home anymore and we have other Linux distos that Raven does not work on at all (e.g. Red Hat / CentOS) that really need some love. However I have 200+ Gentoo servers at work, so it was a logical thing to at least test that platform. And of course it would be nice to get rid of the problem anyways. Raven is meant to be universal after all! ;)

Regarding the Gentoo chroot comment above, I believe the issue is that ravenadm assumes chroot is at /usr/sbin/chroot, but on Gentoo it's at /usr/bin/chroot.   I am able to build packages after creating a symlink from /usr/bin/chroot to /usr/sbin/chroot as a workaround.

by the way, there is now a freenode IRC channel (#ravenports)

making a note of gentoo.  The different location of chroot is the only thing breaking support?

Yes, I believe so in my limited testing.  After applying the chroot workaround, I can successfully do step 8 in the Linux quickstart, then run generate-repository and install the package from the local repository.


Create a cacheble version of userStats with only number_of_flashcards

use new method getFlashcardCounts() of userStatsService

Is is in any proso-apps-js release, yet?

1.2.3


Attach docs should reference search_path setting

https://github.com/duckdb/duckdb-web/blob/c253b025f868e0926eef9be3526ec41fadcf6b1b/docs/sql/statements/attach.md?plain=1#L57C119-L57C119
This mentions the catalog search path but I think that's a little too vague still
It could use an example using either set schema or set search_path directly to drive this point home.
An example of using search_path would be:
D attach ':memory:' as db1;
D attach ':memory:' as db2;
D create table db1.tbl1 (i integer);
D create table db2.tbl2 (j integer);
D set search_path='db1,db2';
D select * from tbl1;
┌────────┐
│   i    │
│ int32  │
├────────┤
│ 0 rows │
└────────┘
D select * from tbl2;
┌────────┐
│   j    │
│ int32  │
├────────┤
│ 0 rows │
└────────┘

Both of these SELECT queries would fail if search_path was not set, because tbl1 and tbl2 would need to be qualified explicitly

Great suggestion, I worked this into a PR.


Unhandled c2s stanza: iq; xmlns=urn:xmpp:mam:tmp

I'm using latest version of mod_mam on prosody and I'm seeing this error in logs.
stanzarouter                              debug	Unhandled c2s stanza: iq; xmlns=urn:xmpp:mam:tmp

You can see on mod_mam page that XEP-0313 has changed.
https://code.google.com/p/prosody-modules/wiki/mod_mam
I think this was already fixed for stanza.io: https://github.com/otalk/stanza.io/issues/42

+1 on this
Any chances for switching to stanza.io 7.x?

Switching to stanza.io 7.x is planned

Kaiwa now uses stanza.io 7


Support traversing a local directory

It could be useful to just traverse a local directory and explore its content with sparql.anything

This would require the engine to recognize that (a) location is a local path and (b) location is an existing directory. When this is the case, the engine should delegate to a special FS2RDF triplifier. The Facade-X representation will use containers for folders and files and key/value pairs for their properties?

This would require the engine to recognize that (a) location is a local path and (b) location is an existing directory. When this is the case, the engine should delegate to a special FS2RDF triplifier. The Facade-X representation will use containers for folders and files and key/value pairs for their properties?


[Mutant Year Zero] Fixed buddy checkbox

Changes / Comments
The check for buddy under relationships was erroneously a radio button, this has been fixed in this version (v2.04).
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[x] Does the pull request title have the sheet name(s)? Include each sheet name.
[x] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.

@nmbradley Can you please confirm that this was merged and published, since this doesn't seem to have updated any sheets neither in Dev or Production server?
There are only small changes but easily verifiable - the sheet version attribute and a change from radiobutton to checkbox, and none appear in any game I have tested yet.
Thanks in advance!


Upgraded but npm -v still returns old

It seemed to have updated, I got a success message, but when I ran npm -v it still says old version. Any help would be appreciated.

Checked system for npm installation:
According to PowerShell: C;\Program Files\nodejs
According to npm: C;\Users\ts220\AppData\Roaming\npm
Decided npm is installed in C:\Program Files\nodejs
upgrading npm...

Upgrade finished. your new npm version is 6.5.0. Have a nice day!
PS C;\Windows\system32> npm -v
6.4.1
PS C;\Windows\system32>

I have the same issue. Its because my npm is here: \AppData\Roaming\npm in windows 10. It upgrades the c:/program files/nodejs which isn't the one actually used.
Look at your according to NPM line


Update app.go

NB:  I might've misunderstood this:
https://github.com/cosmos/cosmos-sdk/commit/222fd6cd358b05af8ba08deb64f7ee311c91755f#commitcomment-65011785

From v0.45 docs

For a new module foo, InitGenesis is called by RunMigration only when foo is registered in the module manager but it's not set in the fromVM. Therefore, if you want to skip InitGenesis when a new module is added to the app, then you should set its module version in fromVM to the module consensus version:
app.UpgradeKeeper.SetUpgradeHandler("my-plan", func(ctx sdk.Context, plan upgradetypes.Plan, fromVM module.VersionMap) (module.VersionMap, error) {
    // ...

    // Set foo's version to the latest ConsensusVersion in the VersionMap.
    // This will skip running InitGenesis on Foo
    fromVM[foo.ModuleName] = foo.AppModule{}.ConsensusVersion()

    return app.mm.RunMigrations(ctx, fromVM)
})

But there are no new modules, and I don't see new any consensus version in SDK modules, and no migrations scripts
v0.44.5...v0.45.0

Thank you for that @giansalex.


Racecar instrumentation adapter

Convert Datadog instrumentation for Racecar to OpenTelemetry.
See

Datadog porting guide
Semantic Conventions
Datadog implementation

Racecar uses rdkafka once https://github.com/open-telemetry/opentelemetry-ruby/issues/919 is complete I intend to close this out as the instrumentation will be covered by including rdkafka instrumentation.

Maybe you already know but #919 does not work with racecar. The racecar gem does not use the rdkafka API that is instrumented (each and each_batch), it uses poll and poll_batch instead:
https://github.com/zendesk/racecar/blob/73f424f36324f4161f820f6558097a704cbb3316/lib/racecar/runner.rb#L66-L80


Enabled the EPEL repo on all of the nodes in the Vagrantfile.

A number of the exercises uses packages in the EPEL repo. As a convenience, all of the nodes should have that repository enabled while bootstrapping to eliminate one more manual step and any confusion that could arise from missing that step.

do we want to add ansible in the vagrant file like how https://github.com/dfederlein/ansible-tower-demo/blob/master/Vagrantfile has it?


Dependency locking fails for Kotlin Multiplatform project: "Configuration ':kotlinScriptDefExtensions' is locked but does not have lock state"

Expected Behavior
Dependency locking does not fail for Kotlin Multiplatform project
Current Behavior
Dependency locking fails for Kotlin Multiplatform project
Context (optional)
Given a Kotlin Multiplatform project with Dependency Locking enable, run ./gradlew check.
Observe that Gradle fails with an unhelpful error
Execution failed for task ':urlencoder-lib:compileKotlinJvm'.
> Failed to calculate the value of task ':urlencoder-lib:compileKotlinJvm' property 'scriptExtensions$kotlin_gradle_plugin_common'.
   > Could not resolve all dependencies for configuration ':urlencoder-lib:kotlinScriptDefExtensions'.
      > Locking strict mode: Configuration ':urlencoder-lib:kotlinScriptDefExtensions' is locked but does not have lock state.

Steps to Reproduce
Run ./gradlew check in the attached project.
urlencoder.zip
Gradle version
8.2.1
Build scan URL (optional)
No response
Your Environment (optional)
No response

Sorry that you're having trouble with Gradle!
Your issue appears to be a question about how to use Gradle. Your question might be answered in Gradle documentation or on our community Slack or forums. Find links to these resources on help.gradle.org.
If you think you have come across a Gradle bug, please file a new issue describing the problem and how to reproduce it.
If you think Gradle is missing a feature, please file a new issue describing your use case for the feature.

Related to

#25756

See docs.
You need to generate a lock file for kotlinScriptDefExtensions in urlencoder-lib.


Performance bad on own video?

Dear authors:
Thanks for sharing this fancy idea work, it looks really novel and effective! But when i try to test it on my own video, such as several people meeting video in a room, I found it performs badly. I guess it may due to the relatively small face and not-so-clear sound recorded.
But when i try another good-quality video:
https://user-images.githubusercontent.com/4252555/120441602-50fb2580-c3b7-11eb-8326-bc3d3159d92c.mp4
It looks still not-so-good, especially compared with the demo video publish by you. I wonder is there any difference to run the code? or any one come across the same situation???  Thank you.

You can try segmenting the video with a shot boundary detector first.


Bump bounds

Probably best to merge #95 first

Can you rebase this on #95

I actually had to work on this on top of #96 otherwise it wouldn't build for me, but decided to split it out to make independent PRs so it could be merged before the other one given the diff is easier to review (though possibly harder to replicate the testing I did for each successive bound bump where as the other one only needs two cases - before and after 5.2).
I don't have a preference myself in this case, is chaining the PRs preferable here?

I don't mind chaining PRs personally. In principle I'm interested in merging both of these but I wanted to verify the build worked for me and from what I remember one of them doesn't build without the other. If you could make a single PR with two diff commits the review will be both easy to review in chunks and still capture the proper dependency order.

one of them doesn't build without the other
still capture the proper dependency order.

More specifically, this repo may or not build out of the box depending on which package snapshot one's build tool is looking at. If http2 <5.2 is used, the repo should build and so would this PR.
At any rate, I rebased #95 in here to make it unconditionally build since it's accidentally a dependency when using an up-to-date snapshot, unless one's package's constraints prevent newer http2.


Add support for event loop and basic network listeners, and a general-purpose memory allocator

In your general purpose allocator, the part where it actually needs to do the syscall to allocate memory is unimplemented.
I have a suggested solution! This allocator can accept another allocator upon initialization, which it uses to make the underlying raw_alloc allocations.
Then the user of this API can pass in a DirectAllocator, which always calls the system API to allocate/free directly.
You can see this pattern in std/special/build_runner.zig.

This is quite a lot of exciting stuff. Can you break this into a series of smaller, independently unit-tested, easier-to-review pull requests?

Closing this PR, and I will reopen a number of smaller independent ones as suggested.

@bscheinman @andrewrk What is the latest on this?
Can we get a PR/Issue open to start working on networking?

Here's something
https://gist.github.com/andrewrk/d48c8c9ca0fb67bf6d7c0bed744d82ce
I've got some work in a branch too. More work planned after Pointer Reform (see #770) is done.

@andrewrk cool -- there is a lot of work that has been put into this PR.
Would it be better to directly hack on std or build-out a module and then integrate later?
Is there a google hang-out or something that we can join to work on hacking together?
Sorry to ask here! Thanks!

there is a lot of work that has been put into this PR.

Everything this PR does exists in std.event using coroutines. I have yet to document that language feature though. The general purpose allocator in this PR was never finished.

Would it be better to directly hack on std or build-out a module and then integrate later?

I know @tiehuis likes to build out separate repositories before submitting a pull request to zig. You're welcome to make pull requests directly against std. I would recommend first filing an issue with a proposal explaining the use case that you're trying to solve and how you propose going about solving it - that way if it's something already planned or related to something already planned we can figure out the best way to go about it.

Is there a google hang-out or something that we can join to work on hacking together?

The #zig channel on freenode is a good place to collaborate with the zig community.

Sorry to ask here! Thanks!

No worries. Hope to see you around


Add issue template

First version of issue template - largely inspired (copied) from DuckDB's repo
Fixes https://github.com/duckdb/pg_duckdb/issues/223

I think the form will probably drive us crazy.

Totally agreed. I think that's easily solvable by adding a second issue template that we can choose, called something like "Issues reported by maintainers". As long as 90% of users will click the "Bug report" option we'll get the benefit of both.


Release?

Would it be possible to send out an alpha release?
I don't mind conda-forge packaging.

This also probably depends on names

Fair

It seems (at least from #36) that dask-streams is the working title for this work. Would it be possible to do all the name changing in the near future? I'm happy to PR this in, but I don't want to break everyone's PRs. I'm hoping that we can package/ship an alpha/beta version of this by Sept 5th?

I'm fine with breaking all my PR's for name change. We can probably vote between us since it's only @mrocklin @danielballan you and I.

👍

I think that is buy-in from all the major contributors, so dask-streams it is! @mrocklin are there any major changes (aside from the name change) associated with attaching dask to the name (eg licence change)?

Sorry for my absence recently.  I'll try to merge/release/push docs
sometime today.
On Fri, Aug 4, 2017 at 6:55 AM, Christopher J. Wright <
<EMAIL_ADDRESS>wrote:

I think that is buy-in from all the major contributors, so dask-streams
it is! @mrocklin https://github.com/mrocklin are there any major
changes (aside from the name change) associated with attaching dask to
the name (eg licence change)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mrocklin/streams/issues/35#issuecomment-320255264,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AASszAtuN0Y2FJ7fuKAA3aJfZY2ZtOq5ks5sUyLAgaJpZM4OXOek
.

Are there other barriers to release? (aside from tagging it)

I can do this any time.  We might want basic API docs first?  This doesn't
really block though.
On Tue, Aug 15, 2017 at 3:38 PM, Christopher J. Wright <
<EMAIL_ADDRESS>wrote:

Are there other barriers to release? (aside from tagging it)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mrocklin/streamz/issues/35#issuecomment-322566916,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AASszJC_EnoLq-sHdf6IhQ8xnzz2VWxeks5sYfO6gaJpZM4OXOek
.

I'd prefer sooner rather than later (I'm going to use this in a release of software next week). When we have a tag let me know I'll put it up on conda-forge. Are we still tied to distributed master?

I've added docs, screwed around with the README, released, and pushed to PyPI here: https://pypi.python.org/pypi/streamz/0.0.1

If you send a PyPI username I'll add you to the list

Ok, will do also I will put up a conda-forge recipie

(Will close when conda-forge is up)


Added support for the extended stargazers API in Github V3 API

Github has added starred_at date to stargazers when stargazers are requested with a special (new) version on the REST API. Added support for the version and a type representing the additional information.

Good question, maybe it should have both versions supported


Opening the modeling app from the CLI with a path that does not exist shows a blank page

When testing the the manual check list for the latest cut release I found an edge case we are missing when opening files and folders.
Preexisting working workflows
This opens the folder default and works.
/home/kevin-nadro/Downloads/Zoo\ Modeling\ App-0.25.5-x86_64-linux.AppImage /home/kevin-nadro/Documents/zoo-modeling-app-projects/default

This opens an empty folder and creates a blank main.kcl
rm /home/kevin-nadro/Documents/zoo-modeling-app-projects/empty/main.kcl

/home/kevin-nadro/Downloads/Zoo\ Modeling\ App-0.25.5-x86_64-linux.AppImage /home/kevin-nadro/Documents/zoo-modeling-app-projects/empty

Bug
$ ./Zoo\ Modeling\ App-0.255.255-x86_64-linux.AppImage /home/dog/cat/mouse

don't worry about the version updater number there, I've tested this on the local package, a real v0.25 and this app updater one

error messages in the terminal
Loading project at startup: /home/dog/cat/mouse
Checking for update
Error: ENOENT: no such file or directory, stat '/home/dog/cat/mouse'
[25939:1001/095127.135049:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
Update for version 0.255.255 is not available (latest version: 0.25.5, downgrade is disallowed).
checkForUpdatesAndNotify called, downloadPromise is **null**

What the application looks like, it will hang forever on this blank page.

Possible solutions

[ ] ?
[ ] ?
[ ] ?
[ ] ?

guptaarnav took care of this one :)

Closed by https://github.com/KittyCAD/modeling-app/pull/4161


Run relevant unit tests on both indexes

Required for all non-trivial PRs

[ ] Rebased/mergable
[ ] Tests pass
[ ] CHANGELOG.md updated

This PR ensure that where appropriate, unit tests are run on both indexes using sub-tests. Benchmarks have also been updated in a similar way.
In terms of the tests package tests, I found that the test output was too noisy when using Go's verbose -v mode, which itself is useful for seeing the sub-test result output. Therefore I've added a new -vv flag for that package, if the server logs are desirable output. /cc @mark-rushakoff @aanthony1243.
Finally, regarding the tests package, all queries for each test will now run as sub-tests.
go test -v github.com/influxdata/influxdb/tests -vv

=== RUN   TestStore_Cardinality_Compactions/inmem
[I] 2017-08-10T15:21:33Z Using data dir: /tmp/influxdb-tsdb-960455470 service=store
panic: test executed panic(nil) or runtime.Goexit

goroutine 87907 [running]:
testing.tRunner.func1(0xc42056f110)
	/usr/local/go/src/testing/testing.go:622 +0x55f
runtime.Goexit()
	/usr/local/go/src/runtime/panic.go:366 +0x15c
testing.(*common).SkipNow(0xc42005f860)
	/usr/local/go/src/testing/testing.go:555 +0x59
testing.(*common).Skip(0xc42005f860, 0xc420479e60, 0x1, 0x1)
	/usr/local/go/src/testing/testing.go:536 +0x7d
github.com/influxdata/influxdb/tsdb_test.testStoreCardinalityCompactions(0xc42005f860, 0xc4201300d0)
	/root/go/src/github.com/influxdata/influxdb/tsdb/store_test.go:766 +0x142
github.com/influxdata/influxdb/tsdb_test.TestStore_Cardinality_Compactions.func1(0xc85fad, 0x5)
	/root/go/src/github.com/influxdata/influxdb/tsdb/store_test.go:823 +0x155
github.com/influxdata/influxdb/tsdb_test.TestStore_Cardinality_Compactions.func2(0xc42056f110)
	/root/go/src/github.com/influxdata/influxdb/tsdb/store_test.go:827 +0x72
testing.tRunner(0xc42056f110, 0xc4205b1c00)
	/usr/local/go/src/testing/testing.go:657 +0x108
created by testing.(*T).Run
	/usr/local/go/src/testing/testing.go:697 +0x544
FAIL	github.com/influxdata/influxdb/tsdb	78.467s

@jwilder that must be a flaky test


copying an empty folder into itself seems to create an infinity amount of empty folder in itself

Describe the bug
copying an empty folder into itself seems to create an infinity amount of empty folder in itself
To Reproduce
Steps to reproduce the behavior:

copy an empty folder
open this folder
paste the folder from the clipboard
files uwp crashes

Expected behavior
files uwp shouldn*t crash, instead there should be only one copy of the folder in this folder and not an infinity amount
Desktop (please complete the following information):

OS Version: Windows 10 1909
App version: 0.7.5

This has been fixed with 0ace5ecc98cab6b5c0fdc4d80c7c7ba7ee078dfc. These changes should roll out when v0.7.6 is released.


Hide graph when no data is selected

Proposed solution for #145.
Essentially just hides the graph and displays the message "Please select some countries to display." if there exists available data but no visible country is displayed. If there is no data available at all (e.g. Australia, deaths) the original message remains.
As always, feedback and review are welcome.

nice... one slight detail:  select region -> choose one of the countries (e.g. US) -> deselect all
the headline for the region US is states/territories but the label showing up after deselect all still says "Please select some countries to display."
aside that hiding the whole graph instead of simply hiding the doubling time line and label looks unusual but maybe the better and cleaner choice... more explicit that way

Laziness on my part, mostly. I could either change the text to be more neutral (i.e. instead of countries, say locations) or add more checks. I would go for the first option, as that doesn't overload the index.html file and it wouldn't need to be looked after should other regions with different names for states (like prefectures and districts or cantons).
Not showing the line at all and just having an empty graph, showing nothing more than gridlines, seems to me the option that looks worse, and it also doesn't say anything else about what an user is supposed to do.
I remembered checking the issue tracker, and this also seems to solve #147.

haha i was still thinking about a suggestion for a neutral sentence working for both the countries as well as the states/territories while you already committed the new patch adding an automatic switch for the text ;) cool! works and i like it.
and yep as i said it just looked unfamiliar at first seeing the grid getting removed. but it is the better choice and decision! :)

Noticed that the page already displays the correct name for the locations on the list, so it was a matter of using that name in the message. Unsure on how to deal with capitalization in the middle of a sentence though.
Lighthouse seemed to timeout

hmmm how about to apply the toLowerCase method to regionType to get a lower case output?

hmmm pity. only approval worked within the commit. hoped for some thumbs up emoji there as well ;) but looks good that way :)

Thanks @MrSpiffyClean for this, and @rpkoller for reviewing! Will plan to merge this tomorrow.
The changes look good, very neat & minimal solution.
The only thing I'm wondering is whether we still require the checks involving covidData.length now that we have this new check. I'm assuming that we do, but want to go back and check.
(From what I recall, the covidData.length check was created to ensure the graph doesn't display until the data first loads, and also that the graph is hidden when there is not data for the parameters, e.g. Deaths in Australia.)


FR: wildcard fqext with constraints

Is your feature request related to a problem? Please describe.
selecting R1/pass1 is annoying.
Describe the solution you'd like
Let's try to make it a wildcard with constraints from a list (containing these two as defaults), and allow users to set others.
(optional) Additional context
In config.smk, the any_given and global wildcard constraints give us a setup to do this.

Yes would be nice! How does this work with downloaded files? How would it decide what to call those?

Pick the last option from each list. That way the user added extensions are selected if given, and otherwise either of the pre-defined ones (I guess _pass_1 and _pass_2).

This feature wasn't implementable as suggested due to the constraints on wildcards in Snakemake.
-The program requires all wildcards to be present in all outputs, which doesn't allow wildcards for fqext1 and fqext2 in the same rule.
-Dictionaries do not work either, as their key (wildcard.samples) is evaluated after expanding the rule in/output.
-Finally, functions are not allowed in a rule output.
An alternative solution has been added: if a file can be found in the fastq_dir with a matching sample name, but a mismatched fqext, a temporary symlink will be created and used for the pipeline.
fqext1 and fqext2 will remain options in the config, as they determine the default extension Snakemake will use (and they pop up in the QC files).
Changes can be found in branch Powerwolf :metal:


Image from README seems incorrect

README.md contain this image:

dkjson part looks wrong or at least weird for me: it's clear that time with and without lpeg is always the same.

Thank you for reporting the issue. Now the result of benchmark is updated.


Add MandarisMoore.com

Adding personal blog to the list

Thanks for submitting @mandaris ! Have a great weekend!


Renamed all instances of parameters to parametersMap

Renamed all instances of parameters to parametersMap and set the new parametersMap access to WRITE_ONLY to expose it to scripts using TestRunner. The original parameters properties are now READ_ONLY and will be used for solely for interfacing with test reporting.
Bump version to 0.1.3-SNAPSHOT.

@ichengchang Ivan, please follow the Jira ticketing norms for test-related work as well.


drop Cargo.lock

It's already in .gitignore, so let's check it out of .git

hey, no, do not drop the lockfile! That's what ensures reproducible builds


New release

Could you release a new version? I'm mainly interested in getting Python 3 to work, which was done in https://github.com/commonsmachinery/blockhash/commit/07268aeaeef880e0749bd22331ee424ddbc156e0, but is not included in the latest release. Relevant is https://github.com/NixOS/nixpkgs/pull/149400 which currently needs to use the master blockhash version to allow removal of Python 2.

Hey @Infinisil , I've released 0.3.2 here:
https://github.com/commonsmachinery/blockhash/releases/tag/v0.3.2
Does this solve the problem?

Awesome thanks, yes it does!


Url alias

Can an alias be given to the URL type column?
For example, in the LINK type column,
url = www.google.com
alias = Google
The aim is to not show the actual url but an alias name instead.
Thx in adv

column tyep LINK ? maybe do you mean column type HTML ?
can you show your code / init jexcel

column tyep LINK ? maybe do you mean column type HTML ?
can you show your code / init jexcel

Apologise for using the wrong term. it is URL column type.

Referring to the documentation - https://jexcel.net/v5/examples/email-and-links , how can we display GOOGLE instead of https://www.google.com

Apologise for using the wrong term. it is URL column type.

Referring to the documentation - https://jexcel.net/v5/examples/email-and-links , how can we display GOOGLE instead of https://www.google.com

Ok, it’s on version Pro, i see only on version CE.
And i don’t know if on pro version you have a feature for make a label. I don’t think so.

Ok, it’s on version Pro, i see only on version CE.
And i don’t know if on pro version you have a feature for make a label. I don’t think so.

Ok, Shall i make this issue in pro github?

Ok, Shall i make this issue in pro github?

Ok, I created this issue in pro-version. Thx!

Ok, I created this issue in pro-version. Thx!


Add custom favicon

In the public folder, maybe we could add a custom favicon, than the pdefault react logo? Thank you.

@CodingSpecies is this issue being done or still we need to add the favicon ?

@ShlokMohanty this issue I have not began working on. Thanks

If you want I can, but I will have to find a favicon, that won't affect copy right, unless we use something by eddiehub?

maybe using something like this for the branding repo?

If you want I can, but I will have to find a favicon, that won't affect copy right, unless we use something by Eddiehub?

@CodingSpecies can we take the permission on this from @eddiejaoude ?

Yes, That is a good idea @ShlokMohanty

I'd say you can just do it. In case eddie isnt fine with it, the PR will get closed but you still get your green squares for it (: So go for it 😄

Please discuss here :- https://github.com/EddieHubCommunity/LinkFree/discussions/206

Great discussion everyone 👍 , I think using the EddieHub mascot for the favicon is a great idea, until we have something more specific

@CodingSpecies can I work on this issue ? I am a beginner and want to start my journey in open source ,so can you assign me this issue ?

@Yash621 I have begun adding this to a pr, but what we need is a real favicon that is suitable to this project, as what I am doing is a temporary favicon. If you would like, you could find a favicon that doesn’t go against copyright and we can use. Thank you!

okay ,I will try to do it ,thank you!!

Reopening due we only have added a temporary favicon

Could I be assigned to this issue? btw is their a specific reason for the favicon being temporary so that I can take care of it?

Not stale yet (comment to remove stale)

is there anyone available???i need to contribute to this project

@darkknight20032001 yes, we are here to help. If you wish to contribute, feel free. See the discussion, as there is favicons and inspirations there: https://github.com/EddieHubCommunity/LinkFree/discussions/206
Any help or questions feel free to ask.

Why is the label as "🚧 status: blocked". Is this issue not being worked on as of now?

@KendallDoesCoding this issue is blocked as we have a discussion #206
Where we are making logos for this project. Once we finalise on a logo, this issue will no longer be blocked!

@KendallDoesCoding this issue is blocked as we have a discussion #206 Where we are making logos for this project. Once we finalise on a logo, this issue will no longer be blocked!

Ok cool!

We have one of the EddieHub mascots for the favicon, so I will close this for now


Fix redirects for v3.14

Description

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Deploy preview for calico ready!
Built with commit ee38c53a35bfb54c47c966fd020ff7859f481db9
https://deploy-preview-3531--calico.netlify.app

Deploy preview for calico ready!
Built with commit e1b9a9f2630dd0e3ad03ac63fa33d6a4414d3934
https://deploy-preview-3531--calico.netlify.app


Cannot start viewer after closing

Whenever I run a simulation, close it, and restart a second one the window only shows a black screen. Do other people have this issue as well?

You mean after you close your program and then restart it? Or close the viewer programmatically and then reopen it?

The latter. Excuse me, I should have included a minimal example. Running mujoco viewer's sample.py multiple times within the same python script leads to a black window the second time on my machine:
import mujoco
import mujoco_viewer

while True:
    model = mujoco.MjModel.from_xml_path("humanoid.xml")
    data = mujoco.MjData(model)

    # create the viewer object
    viewer = mujoco_viewer.MujocoViewer(model, data)

    # simulate and render
    for _ in range(100):
        mujoco.mj_step(model, data)
        viewer.render()

    # close
    viewer.close()

Hi @surgura
Thanks for the minimal example.
I could reproduce the problem, and it seems to have happened because mujoco context wasn't being freed (only made available after mujoco 2.1.2)
Could you retry after updating mujoco-python-viewer? This will also update your mujoco to 2.1.5

Definitely working now. Thank you very much for the quick effort!

Nice!


MethodChannel.invokeMethod should be generic API.

(Filed at the request of @Hixie)
MethodChannel.invokeMethod currently returns Future<dynamic> though it should be one of a few types (yes, a perfect opportunity for union types, but anyway). A better would be to make it generic in some way MethodChannel.invokeMethod<T>(...) or MethodChannel<T> depending on how MethodChannel is used... I've only looked at it extremely superficially.

cc @mravn-google @goderbauer

I guess with Dart 2 a generic invokeMethod would make sense. I don't think a generic MethodChannel does; the same channel is often used to relay values of different types back to Dart, depending on which methods was invoked.

an alternative would be to put a discussion of this matter in the documentation for the method. right now it's not clear what type to expect back.

That is because the MethodChannel class itself carries no knowledge of that. It all depends on the codec with which an instance is constructed. The documentation for invokeMethod currently says as much, though we may be able to make it more explicit, by digging that information out of the paragraph on parameters.
We could also duplicate information from StandardMessageCodec in the documentation for MethodChannel. I didn't do that originally because the message codec and method channel are orthogonal concepts. However, the StandardMessageCodec does govern the behavior of a MethodChannel constructed with default parameters. So maybe there is little damage done by coupling the two concepts in documentation.

sure. i think we could make it clearer with examples, a discussion of how the type is determined front the either side, etc.

I will say the existing process for casting compound types on the customer side is pretty dang subtle for the average developer. I had to very carefully write
invokeMethod('getLocation').then((result) => result.cast<String, double>()
and more intricate:
receiveBroadcastStream().map<Map<String, double>>((element) => element.cast<String, double>())
and I probably understand type systems better than the average programmer. I'm hoping general programmers don't have to figure this out. So, if we can make our users lives easier with a less cast-confusing API, that's great!

@efortuna Yes, it would be nice if there was a way to avoid or side-step List<dynamic> and Map<dynamic, dynamic>. The standard codec is designed to work with heterogenous data carrying no external type metadata. It is forced to produce List<dynamic> in the same way that a JSON decoder is when faced with [42,87,103,...--- for the next element may not be a number. Where JSON always uses Map<String, dynamic>, the standard codec does not force String keys, and so we end up with Map<dynamic, dynamic> too.
Since https://github.com/flutter/flutter/pull/15414 you can extend the standard codec and do whatever suits your situation better, including typed deserialization, at the cost of some additional coding.

Documentation with examples has been added. Closing this.


Disable FunctionalTests.DatabaseErrorPageSampleTest.DatabaseErrorPage_ShowsError...

...  on non-Windows or fix it to run xplat.
Currently hits "System.PlatformNotSupportedException: Integrated Security is not supported on non-Windows platform." errors rather than the expected issues.
On a related note, strongly suggest adding --quiet to the script in this repo's .travis.yml file. The expected log is far too long for Travis to display.

Self-assigning

af97bcd (got offline squirrel from @ryanbrandenburg)

Download the log, you're making future peoples lives more painful by adding --quiet

What useful information does --quiet mask? It should be the default.


Disable automatic selection of first result

Being able to disable the automatic selection of the first result would be incredibly useful.
For example, when tokensAllowCustom is enabled, it is not intuitive to press Ctrl+Enter to create the custom tag instead of the suggested tag. If there was an option to disable selecting search results, so that a custom tag can be added or the search result can be manually clicked/selected.

Hi thanks for your suggestion, I added a new option dropdownSelectFirstItem, true by default to let you choose your behavior. Just put it to false and the plugin will work as you want.
Let me know if it's work for you before I publish the new release.


add --on-error flag to replace --fail-fast

Description
Adds and exposes the flag on-error that allows
users to choose between 'fail' and 'recover' (ie:
fail-fast and best-effort) error handling modes.
Also sets some fault constructors to fail-fast
so that we don't let errors slip through.
Does this PR need a docs update or release note?

[x] :white_check_mark: Yes, it's included

Type of change

[x] :sunflower: Feature

Issue(s)

#1970

Test Plan

[x] :zap: Unit test

@gmatev @vkamra could I get a review on the general change here, please?  Abin has already given the granular code changes a thumbs up.

@ryanfkeepers - this also changes the default behavior for backup - correct? The flag looks good - I do want to understand the motivation behind the behavior change.

If I understand the behavior change correctly, we now default to stopping immediately as opposed to best effort. This is a change form before.
Is this correct? If yes, why the change? Seems to me that we want to do as much as we can so the default should be the opposite.

@vkamra @gmatev Good questions.  The concern came from reviews across the error handling migration.  Since the codebase currently has scattered error handling, we always failFast in some places, even when we could continue.  Worries were expressed that a switch to best effort in those locations might cause overly lax handling in error cases with unexpected consequences.
This change to default to failFast behavior is to ensure that we will continue to hard stop at those locations while the handling migration is underway, and that we can return the default to best effort once things have settled.  The new flag format will help support this transition to ensure that if or when we swap the default again, existing flag declarations will maintain the same behavior (and be easier to script altogether).

@ryanfkeepers - couple of follow ups:

recover needs to be changed to continue
Can we hold of on changing the default value for --on-error? My concern is that we will start failing earlier in locations where we do not want to. For places where we absolutely need to fail hard - we shouldn't be using opts.FailFast anyway.


Run on ESP32-C3-32S Kit board

Hello @fkohlgrueber
Thank you for providing this LED example. As a total beginner this is really helpful.
I am trying to get it running on my "ESP-C3-32S-Kit ESP32 WiFi+Bluetooth Development Board". I can build and flash fine but run into troubles when running. espmonitor gives me the following output:
ESP-ROM:esp32c3-api1-20210207
Build:Feb  7 2021
rst:0x3 (RTC_SW_SYS_RST),boot:0xc (SPI_FAST_FLASH_BOOT)
Saved PC:0x403d153e
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fcd6100,len:0x172c
load:0x403ce000,len:0x928
load:0x403d0000,len:0x2ce0
entry 0x403ce000
←[0;32mI (35) boot: ESP-IDF v4.4-dev-2825-gb63ec47238 2nd stage bootloader←[0m
←[0;32mI (35) boot: compile time 12:10:40←[0m
←[0;32mI (35) boot: chip revision: 3←[0m
←[0;32mI (38) boot_comm: chip revision: 3, min. bootloader chip revision: 0←[0m
←[0;32mI (45) boot.esp32c3: SPI Speed      : 80MHz←[0m
←[0;32mI (50) boot.esp32c3: SPI Mode       : DIO←[0m
←[0;32mI (55) boot.esp32c3: SPI Flash Size : 4MB←[0m
←[0;32mI (60) boot: Enabling RNG early entropy source...←[0m
←[0;32mI (65) boot: Partition Table:←[0m
←[0;32mI (69) boot: ## Label            Usage          Type ST Offset   Length←[0m
←[0;32mI (76) boot:  0 nvs              WiFi data        01 02 00009000 00006000←[0m
←[0;32mI (83) boot:  1 phy_init         RF data          01 01 0000f000 00001000←[0m
←[0;32mI (91) boot:  2 factory          factory app      00 00 00010000 003f0000←[0m
←[0;32mI (98) boot: End of partition table←[0m
←[0;32mI (102) boot_comm: chip revision: 3, min. application chip revision: 0←[0m
←[0;32mI (110) esp_image: segment 0: paddr=00010020 vaddr=3c030020 size=0bac8h ( 47816) map←[0m
←[0;32mI (125) esp_image: segment 1: paddr=0001baf0 vaddr=3fc8ae00 size=01be0h (  7136) load←[0m
←[0;32mI (128) esp_image: segment 2: paddr=0001d6d8 vaddr=40380000 size=02940h ( 10560) load←[0m
←[0;32mI (137) esp_image: segment 3: paddr=00020020 vaddr=42000020 size=263d0h (156624) map←[0m
←[0;32mI (167) esp_image: segment 4: paddr=000463f8 vaddr=40382940 size=08484h ( 33924) load←[0m
←[0;32mI (174) esp_image: segment 5: paddr=0004e884 vaddr=50000000 size=00010h (    16) load←[0m
←[0;31mE (174) esp_image: invalid segment length 0x7b4a←[0m
←[0;31mE (178) boot: Factory app partition is not bootable←[0m

I fear that the binary might be too large (debug is 9.8mb, release is 3.5mb) for my device, as it only has 2mb of flash. Running espflash --board-info gives me this:
Chip type:         ESP32-C3 (revision 3)
Crystal frequency: 40MHz
Flash size:        2MB
Features:          WiFi
MAC address:       ...

Which is for some reason not the same as espmonitor. (4MB vs 2MB, 80MHz vs 40MHz).
Do you think the binary size is the problem here?
I have already tried making the binary smaller by using some instructions from min-sized-rust. Unfortunately this is not enough to bring it below 2mb.
Edit: After some tinkering I could bring down the ELF size to ~400kb by adding strip = "symbols" to my Cargo.toml. However now I'm getting a new error:
ESP-ROM:esp32c3-api1-20210207
Build:Feb  7 2021
rst:0xc (RTC_SW_CPU_RST),boot:0xc (SPI_FAST_FLASH_BOOT)
Saved PC:0x40382154
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fcd6100,len:0x172c
load:0x403ce000,len:0x928
load:0x403d0000,len:0x2ce0
entry 0x403ce000
←[0;32mI (35) boot: ESP-IDF v4.4-dev-2825-gb63ec47238 2nd stage bootloader←[0m
←[0;32mI (35) boot: compile time 12:10:40←[0m
←[0;32mI (35) boot: chip revision: 3←[0m
←[0;32mI (38) boot_comm: chip revision: 3, min. bootloader chip revision: 0←[0m
←[0;32mI (45) boot.esp32c3: SPI Speed      : 80MHz←[0m
←[0;32mI (50) boot.esp32c3: SPI Mode       : DIO←[0m
←[0;32mI (55) boot.esp32c3: SPI Flash Size : 4MB←[0m
←[0;32mI (60) boot: Enabling RNG early entropy source...←[0m
←[0;32mI (65) boot: Partition Table:←[0m
←[0;32mI (69) boot: ## Label            Usage          Type ST Offset   Length←[0m
←[0;32mI (76) boot:  0 nvs              WiFi data        01 02 00009000 00006000←[0m
←[0;32mI (83) boot:  1 phy_init         RF data          01 01 0000f000 00001000←[0m
←[0;32mI (91) boot:  2 factory          factory app      00 00 00010000 003f0000←[0m
←[0;32mI (98) boot: End of partition table←[0m
←[0;32mI (102) boot_comm: chip revision: 3, min. application chip revision: 0←[0m
←[0;32mI (110) esp_image: segment 0: paddr=00010020 vaddr=3c020020 size=07798h ( 30616) map←[0m
←[0;32mI (123) esp_image: segment 1: paddr=000177c0 vaddr=3fc8a600 size=01b8ch (  7052) load←[0m
←[0;32mI (128) esp_image: segment 2: paddr=00019354 vaddr=40380000 size=06cc4h ( 27844) load←[0m
←[0;32mI (140) esp_image: segment 3: paddr=00020020 vaddr=42000020 size=1fb2ch (129836) map←[0m
←[0;32mI (163) esp_image: segment 4: paddr=0003fb54 vaddr=40386cc4 size=037ech ( 14316) load←[0m
←[0;32mI (166) esp_image: segment 5: paddr=00043348 vaddr=50000000 size=00010h (    16) load←[0m
←[0;32mI (172) boot: Loaded app from partition at offset 0x10000←[0m
←[0;32mI (175) boot: Disabling RNG early entropy source...←[0m
←[0;32mI (192) cpu_start: Pro cpu up.←[0m
←[0;32mI (204) cpu_start: Pro cpu start user code←[0m
←[0;32mI (204) cpu_start: cpu freq: 160000000←[0m
←[0;32mI (204) cpu_start: Application information:←[0m
←[0;32mI (207) cpu_start: Project name:     esp-idf←[0m
←[0;32mI (212) cpu_start: App version:      affc3f6-dirty←[0m
←[0;32mI (217) cpu_start: Compile time:     Nov 30 2021 17:43:53←[0m
←[0;32mI (223) cpu_start: ELF file SHA256:<PHONE_NUMBER>000000...←[0m
←[0;32mI (229) cpu_start: ESP-IDF:          4.3.1←[0m
←[0;32mI (234) heap_init: Initializing. RAM available for dynamic allocation:←[0m
←[0;32mI (241) heap_init: At 3FC8D010 len 00032FF0 (203 KiB): DRAM←[0m
←[0;32mI (247) heap_init: At 3FCC0000 len 0001F060 (124 KiB): STACK/DRAM←[0m
←[0;32mI (254) heap_init: At 50000010 len 00001FF0 (7 KiB): RTCRAM←[0m
←[0;32mI (261) spi_flash: detected chip: generic←[0m
←[0;32mI (265) spi_flash: flash io: dio←[0m
←[0;31mE (269) spi_flash: Detected size(2048k) smaller than the size in the binary image header(4096k).

I don't think that the size of the binary (I guess you're measuring the size of the elf file?!) is the problem here, but rather an alignment issue. Segments need to have 4-byte alignment if I remember correctly. I've seen the invalid segment length error too a couple of times and there's also some issues mentioning it (see here and here).
For me, using esp-idf-sys's native build feature fixed the issue and I didn't have any problems afterwards. You can take a look at rust-esp32-std-demo, which is updated frequently. I think you should be able to get the example running by simply adding the native feature to esp-idf-sys and probably doing a clean build.
I'll try to update this repo to use native build soon. Let me know if you still have issues.

I've pushed an update that activates the native build (and updates dependencies). Let me know if it works for you.

Thank you very much! I could successfully build the project with the native feature. But only after setting the env var ESP_IDF_INSTALL_DIR=path/to/my/.espressif. The automatic esp-idf install fails.
Additionally I can only build the project in debug mode currently because of some path length limitation. So cargo build instead of cargo build --release.
The running binary still produces this output:
ESP-ROM:esp32c3-api1-20210207
Build:Feb  7 2021
rst:0x1 (POWERON),boot:0xc (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fcd6100,len:0x172c
load:0x403ce000,len:0x928
load:0x403d0000,len:0x2ce0
entry 0x403ce000
←[0;32mI (30) boot: ESP-IDF v4.4-dev-2825-gb63ec47238 2nd stage bootloader←[0m
←[0;32mI (30) boot: compile time 12:10:40←[0m
←[0;32mI (30) boot: chip revision: 3←[0m
←[0;32mI (33) boot_comm: chip revision: 3, min. bootloader chip revision: 0←[0m
←[0;32mI (40) boot.esp32c3: SPI Speed      : 80MHz←[0m
←[0;32mI (45) boot.esp32c3: SPI Mode       : DIO←[0m
←[0;32mI (50) boot.esp32c3: SPI Flash Size : 4MB←[0m
←[0;32mI (55) boot: Enabling RNG early entropy source...←[0m
←[0;32mI (60) boot: Partition Table:←[0m
←[0;32mI (64) boot: ## Label            Usage          Type ST Offset   Length←[0m
←[0;32mI (71) boot:  0 nvs              WiFi data        01 02 00009000 00006000←[0m
←[0;32mI (78) boot:  1 phy_init         RF data          01 01 0000f000 00001000←[0m
←[0;32mI (86) boot:  2 factory          factory app      00 00 00010000 003f0000←[0m
←[0;32mI (93) boot: End of partition table←[0m
←[0;32mI (98) boot_comm: chip revision: 3, min. application chip revision: 0←[0m
←[0;32mI (105) esp_image: segment 0: paddr=00010020 vaddr=3c030020 size=08700h ( 34560) map←[0m
←[0;32mI (118) esp_image: segment 1: paddr=00018728 vaddr=3fc8a400 size=00c6ch (  3180) load←[0m
←[0;32mI (122) esp_image: segment 2: paddr=0001939c vaddr=40380000 size=06c7ch ( 27772) load←[0m
←[0;32mI (135) esp_image: segment 3: paddr=00020020 vaddr=42000020 size=26130h (155952) map←[0m
←[0;32mI (162) esp_image: segment 4: paddr=00046158 vaddr=40386c7c size=036ach ( 13996) load←[0m
←[0;32mI (165) esp_image: segment 5: paddr=0004980c vaddr=50000000 size=00010h (    16) load←[0m
←[0;32mI (171) boot: Loaded app from partition at offset 0x10000←[0m
←[0;32mI (174) boot: Disabling RNG early entropy source...←[0m
←[0;32mI (191) cpu_start: Pro cpu up.←[0m
←[0;32mI (199) cpu_start: Pro cpu start user code←[0m
←[0;32mI (199) cpu_start: cpu freq: 160000000 Hz←[0m
←[0;32mI (199) cpu_start: Application information:←[0m
←[0;32mI (202) cpu_start: Project name:     libespidf←[0m
←[0;32mI (207) cpu_start: App version:      1←[0m
←[0;32mI (212) cpu_start: Compile time:     Nov 30 2021 21:40:16←[0m
←[0;32mI (218) cpu_start: ELF file SHA256:<PHONE_NUMBER>000000...←[0m
←[0;32mI (224) cpu_start: ESP-IDF:          68cf4ef←[0m
←[0;32mI (229) heap_init: Initializing. RAM available for dynamic allocation:←[0m
←[0;32mI (236) heap_init: At 3FC8BFC0 len 00034040 (208 KiB): DRAM←[0m
←[0;32mI (242) heap_init: At 3FCC0000 len 0001F060 (124 KiB): STACK/DRAM←[0m
←[0;32mI (249) heap_init: At 50000010 len 00001FF0 (7 KiB): RTCRAM←[0m
←[0;32mI (256) spi_flash: detected chip: generic←[0m
←[0;32mI (260) spi_flash: flash io: dio←[0m
←[0;31mE (264) spi_flash: Detected size(2048k) smaller than the size in the binary image header(4096k). Probe failed.←[0m
←[0;32mI (275) sleep: Configure to isolate all GPIO pins in sleep state←[0m
←[0;32mI (281) sleep: Enable automatic switching of GPIO sleep configuration←[0m
←[0;32mI (289) cpu_start: Starting scheduler.←[0m

There is still a warning (?) related to the flash size. I'm not sure if it matters but I can make it go away by providing espflash with a custom bootloader and partition table.
For the record: I got the bootloader.bin by building a hello_world project from the esp-idf like this:
idf.py set-target esp32c3
idf.py menuconfig
idf.py build

In the menuconfig step I configured the flash size to 2MB and disabled auto-detect. Then my partition file looks like this:
# Name,   Type, SubType,  Offset,   Size,  Flags
nvs,      data, nvs,      0x9000,  0x6000,
phy_init, data, phy,      0xf000,  0x1000,
factory,  app,  factory,  0x10000,  1M,

Flash with:
espflash --bootloader bootloader.bin --partition-table table.csv COM3 target/riscv32imc-esp-espidf/debug/esp32c3-idf-led-example

Now I guess the example is running. However I see no log output or LED lighting up. Maybe I have to find the correct GPIO pin first...

Thanks @brookman for the detailed explanation! I was using this example as well and got similar problems, which I could solve with your hints. I also have the exact same board you have but I don't get the LED to run. I looked into the schematics and it would seem that this board does not use a WS2812 led but three individual pins:

(source: https://www.waveshare.com/w/upload/4/46/Nodemcu-esp-c3-32s-kit-schematics.pdf)
Did you adjust your example as well accordingly?

Furthermore, I just noticed that the code may not be running at all, since I don't see any info messages within the program output after the I (269) cpu_start: Starting scheduler. message. Any hint would be quite appreciated.

@javiser seems like I broke the logging output during one of the updates. I also don't get any output after the Starting scheduler message. I've pushed an update that should fix the logging.

Regarding the LED: if your dev board doesn't have a WS2812 LED but uses three separate pins, you can simply drive a high signal on one of them to see whether the LED works.

@javiser seems like I broke the logging output during one of the updates. I also don't get any output after the Starting scheduler message. I've pushed an update that should fix the logging.

Yes, that fixes the problem!

Regarding the LED: if your dev board doesn't have a WS2812 LED but uses three separate pins, you can simply drive a high signal on one of them to see whether the LED works.

Yes, I thought about that. But I am trying still to find out how to do that. I have been playing around with Rust and a couple of boards during the last couple of weeks and it seems that all the solutions and examples are different :disappointed:

Embedded Rust is still evolving, that's why examples might look different. In general, you'll want to use a hardware abstraction layer (hal) crate for your board. For the esp32c3, you can use esp-idf-hal. Hal crates provide one layer of abstraction on top of the raw device specific memory addresses you'd otherwise need program yourself. There's another crate called embedded-hal which contains traits for common peripherals found on microcontrollers. embedded-hal provides traits that are then implemented by hal crates for boards (e.g. esp-idf-hal).
Blinking your on-board led should be as simple as toggling the output of one of the gpio pins. For example, if you want to toggle gpio pin 4, you'd need get the corresponding object from the hal crate. This object has the type Gpio4, which implements embedded-hals OutputPin trait. You can then simply call set_high() and set_low() on that object to toggle the output.
Here's a diff showing how this repo's code can be modified to make it happen:
diff --git a/Cargo.toml b/Cargo.toml
index b1fa713..e1c18a7 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -11,6 +11,8 @@ anyhow = {version = "1", features = ["backtrace"]}
 log = "0.4"
 esp-idf-sys = { version = "0.30", features = ["binstart", "native"] }
 esp-idf-svc = "0.36.2"
+esp-idf-hal = "0.32.3"
+embedded-hal = "0.2.6"

 [build-dependencies]
 embuild = "0.28"
diff --git a/src/main.rs b/src/main.rs
index 187434f..137dfdd 100644
--- a/src/main.rs
+++ b/src/main.rs
@@ -6,6 +6,9 @@ use std::thread;
 use anyhow::*;
 use log::*;

+use esp_idf_hal::peripherals::Peripherals;
+use embedded_hal::digital::v2::OutputPin;
+
 use esp_idf_sys;

 use crate::led_strip::Led;
@@ -16,6 +19,20 @@ fn main() -> Result<()> {
     // Bind the log crate to the ESP Logging facilities
     esp_idf_svc::log::EspLogger::initialize_default();

+    // simple blinky output pin
+    let peripherals = Peripherals::take().unwrap();
+    let pins = peripherals.pins;
+
+    let mut led = pins.gpio4.into_output()?;
+
+    loop {
+        led.set_high()?;
+        thread::sleep(Duration::from_millis(1000));
+        led.set_low()?;
+        thread::sleep(Duration::from_millis(1000));
+    }
+
+    /*
     info!("Let's use the esp32c3 rgb led!");

     let mut led = Led::new(
@@ -46,4 +63,5 @@ fn main() -> Result<()> {
         led.fade_to(L, L, H, NUM_STEPS, DURATION)?;
         led.fade_to(H, L, H, NUM_STEPS, DURATION)?;
     }
+    */
 }

Let me know if that helps.

Wow! Awesome! So many thanks for the help! That worked like a charm! I still need to dig in the specs for that board, I tried with GPIO18 and that activated a yellow built-in led and GPIO19 activated the white one. I was used to the fantastic documentation from Adafruit and this one is not that nice.
Thanks again for your help!

Yeah, that's all still pretty much work in progress. esp-idf-hal unfortunately also doesn't have docs available on docs.rs, but you can build them locally using cargo doc --open. You can also join the esp-rs matrix group and ask for help there: https://matrix.to/#/#esp-rs:matrix.org


Feature/core #26

We were missing a dropout in the encoder

Codecov Report

Merging #87 into develop will increase coverage by 5.67%.
The diff coverage is 97.74%.

@@             Coverage Diff             @@
##           develop      #87      +/-   ##
===========================================
+ Coverage    92.85%   98.52%   +5.67%
===========================================
  Files           22       32      +10
  Lines          672      952     +280
===========================================
+ Hits           624      938     +314
+ Misses          48       14      -34

Impacted Files
Coverage Δ

...asses/nn/models/classification/alexnet/__init__.py
100.00% <ø> (ø)

glasses/utils/ModuleTransfer.py
100.00% <ø> (ø)

setup.py
0.00% <0.00%> (ø)

test/test_ResNet.py
100.00% <ø> (ø)

...lasses/nn/models/classification/resnet/__init__.py
94.44% <66.66%> (-0.25%)
:arrow_down:

...ses/nn/models/classification/mobilenet/__init__.py
98.79% <98.79%> (ø)

glasses/nn/blocks/residuals.py
100.00% <100.00%> (ø)

glasses/nn/models/__init__.py
100.00% <100.00%> (ø)

glasses/nn/models/classification/__init__.py
100.00% <100.00%> (ø)

...sses/nn/models/classification/densenet/__init__.py
100.00% <100.00%> (ø)

... and 26 more

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 02ca64e...ec497e0. Read the comment docs.


Add io.Writer method

@chewxy Just to be clear is this issue to implement the io.Writer interface on Rope? I.e. func (r *Rope)  Write(p []byte) (n int, err error). Should this append or overwrite the current Rope contents? If so, I can take this, I think.

Yes. Correct on all points. Please do take this. Thanks
On 22 Oct. 2017 5:02 am, "Chris Marshall"<EMAIL_ADDRESS>wrote:
@chewxy https://github.com/chewxy Just to be clear is this issue to
implement the io.Writer interface on Rope? I.e. func (r *Rope) Write(p
[]byte) (n int, err error). Should this append or overwrite the current
Rope contents? If so, I can take this, I think.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/chewxy/skiprope/issues/4#issuecomment-338421062, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAczUnKovHALPWfociBfwENiqNfOdajEks5sujGmgaJpZM4P9nS8
.


Typo "Serch" should be "Search"

https://github.com/aws-samples/retail-demo-store/blob/b80137c6edb2c975c50221fcaba46b6abadd7b99/aws/cloudformation-templates/services/service/_template.yaml#L154

I just cloned the project and fixed the typo on a 'bugfixes' branch i created, just created a pull request a little bit earlier

this has been fixed along with other PR. Thanks for reporting !


Additional Scope and Ref Functions

There isn't an issue. This is just an addition for more functionality

GetRef is bugged, super easy to end up in undefined behaviour, either with a local variable that has been deleted while still in scope, or a ref that points to memory that has already been deleted (see examples below)
The issue is that passing in a T& implies that the caller still owns the memory, but you are passing that into shared_ptr which implies it is taking over ownership of the memory
struct Foo
{
    bool& deleted;
    ~Foo() { deleted = true; }
};

TEST(RefTest, RefDeletesInScopeValue)
{
    bool deleted = false;
    Foo foo { deleted };

    {
        auto ref = GetRef<Foo>(foo);
    }

    // foo is still in scope but has been deleted by the ref going out of scope
    EXPECT_FALSE(deleted);
}

TEST(RefTest, RefPointsToReclaimedMemory)
{
    bool deleted = false;
    auto fnReturnRef = [&]() -> Ref<Foo> {
        Foo foo{ deleted };
        return GetRef<Foo>(foo);
    };

    auto ref = fnReturnRef();

    // foo was deleted when it went out of scope so ref points to reclaimed memory
    EXPECT_FALSE(deleted);
}


Not far to 1,337 commits!

When the commit count ticks over to 1337, keep your changes local for a few hours so we can say weird things related to that number! :P

Its not an issue though

No, it's not an issue, but it's just a bit of fun. :P

It's an issue if people don't leave it. :P

Yo-ho-ho and a bottle of rum I read th' number wrong somehow. We actually have a pretty long way to be off. :P I'll close 'tis.

For now.
oO
•


Can't create or modify users

When you go into an existing user the information showing in the fileds are for another one and will now allow you to commit changes
here is a video with the behavior
https://drive.google.com/open?id=1z87dLQ7T-UCah2s2vnZAVZrIxZ5jbxC_

I can't reproduce this in our instance of MetaDeploy. I suspect your browser or a password manager is mistaking this for a login form and autofilling the username.

welp
you are correct
seems to be something caused by last pass
I had to run it on incognito mode with our the extension


Code folding on cell magics (e.g. %%file)

It would be great to have code folding on cells beginning with a cell magic, just as cells beginning with comments can be folded.
Cell magics must always appear on the first line, so cells with a cell magic cannot have a comment header. However, because cell magics use a special character ('%'), perhaps folding can be activated for both '%' and '#'?

This is easy to implement as additional folding mode. See PR #207

Closed by #207


autofocus failes with realteak cam

autofocus on realteak 0bda:5876 webcam (Lenovo 330 ideapad) does not work.
Additional Focus Option missing

I don't know anything about how to configure autofocus with javascript, sorry.
As mentioned in the README jsQR is designed to have no webcam specific implementation details. Rather the API is designed to take in image data and output any QR codes found within. Handling reading image data from the webcam and passing it to jsQR is the responsibility of the consumer, and as such you'll know more than me


Snap to bottom and right

So I'm wondering if the right behaviour is not to snap to the bottom or right, unless you are also snapped to the opposite edge? So full height (or width) controllers resize with the window, but smaller (or bigger) don't.

So I'm wondering if the right behaviour is not to snap to the bottom or right, unless you are also snapped to the opposite edge? So full height (or width) controllers resize with the window, but smaller (or bigger) don't.

Yeah, I agree.
Try this as the basic behaviour. And we will see how it feels.

This seems to be working.
Snapping to top and bottom works with a single Controller, as intended.
It still works when we go fullscreen, but not when we hide the menus.
But we may also want to create a Snapped column with 2 controllers. This would also be nice to have.

Snapping to the right is also partially working ( with a single full width controller ).
I can see that because the border it's adjusted automatically.
But opening the Sidebar still pushes the Controller out of the screen.

I'd also like to have snapping to the right, with multiple vertical columns.
This way all columns would be kept on the screen, when I change the widths.

But which window should be resized when you enter or exit fullscreen/focus mode? The bottom one? All of them

Maybe all of them, proportionally.

But opening the Sidebar still pushes the Controller out of the screen.

How should the behavior be like when opening sidebar windows?

I think, opening for resizing the Sidebar should result in the same behavior, as resizing a Controller ( placed the left side ).

If the Controllers are snapped to the right, all Controllers would be scaled proportionally.
If not, they could be pushed out of the screen.

And snapping to the right/bottom should only happen, when we interact directly with the Controller that snaps:

So we can move or resize the Controller placed on the right, to snap it to the canvas right edge.
But, opening the Sidebar ( or resizing a Controller placed on the left ), should only lead to resizing all Controllers, if they are already snapped to the right edge.

Maybe all of them, proportionally.

I think it would be more intuitive if Controllers always resize, if they are snapped to the right.

Yeah, makes sense. It would be like resizing the entire browser window, Controller windows should proportionally adapt both vertically and horizontally.

So once we start snapping a stack (eg two controllers connected vertically) to the bottom, there suddenly emerge all sorts of other questions.
How do they share the resize?
What happens if there is another controller connected to the side (but not snapping to the top or bottom). Does it move? resize? What if it is connected to a stack on one side, and a full height controller on the other?
This really isn't core business for the controller, and I could spend a long time fiddling with it and we would keep finding cases that should behave differently, not to mention introducing and having to find bugs.
I would need a lot of convincing...

So... I'm going to close this. Feel free to start a topic in the discussions (like we have for aesthetics) if you want to try to work out exactly how it would work in an ideal case...

Yeah, once we test this and create more configurations, we could see if it needs some improvements.
I haven't yet settled on an ideal configuration.


Basic macOS-support

Enable usage on macOS: Add platform "Darwin" to informationservice.py to make app run on macOS

add .DS_Store to .gitignore

Hey, I am curious, I do not have a mac.
Does the app start for you and is usable?
Which backends work for you? Probably only virtual camera and opencv webcam?

Hi,
yes. The app is starting and displays correctly.
„Same“ experience as in linux.
The App is also available in local Network.
As you mentioned, backends are only Virtual webcam and webcamvc2. I have gphoto2 installed, but its not in the backends-list.
If I can help with testing on mac, feel free to contact me :)

Hm, I could add automated tests for Mac also. Not sure how gphoto performs on mac


Task 1148 ( maximum_ascii_value) : Edit Task definition to include ASCII information.

Fixes #629

Thanks!


doc(core): update changeset for decide -> choose renaming

decide has been renamed to choose in #1095.

Thanks, I've missed this!


Fixed 4 test-cases, which were completing too quickly

Fixed 4 test-cases, which were completing too quickly

Thank you @slice4e !


[Bug]: normalize path on rootDir and testMatch  are different

Version
27.5.1 (@testing-library/react 14.0.0)
Steps to reproduce
cd /d X:
yarn create react-app project
cd project
yarn test
Expected behavior
1 tests found
Actual behavior
No test found
Additional context
Working on Win10
X: is a network path resolving to \\server\home\username
react-script create config with
 {     rootDir: "X:\\project,     testMatch: [         "<rootDir>/src/**/__tests__/**/*.{js,jsx,ts,tsx}",         "<rootDir>/src/**/*.{spec,test}.{js,jsx,ts,tsx}"     ] }
In jest-config/build/normalize.js:
function normalizeRootDir(options.rootDir = 'X:\\\\project'){ _jestUtil().tryRealpath(options.rootDir) resolves to \\server\home\username\project
But in jest-config/build/utils.js:
_replaceRootDirTags(rootDir = '\\\\\\\\server\\\\home\\\\username\\\\project',  config = '<rootDir>/src/**/__tests__/**/*.{js,jsx,ts,tsx}')
path resolves to X:\server\home\username\project
if I disable line _jestUtil.tryRealpath in normalize.js normalizeRootDir() resolves to X:\\project and _replaceRootDirTags() resolves to X:\\project\\src\\**\\__tests__\\**\\*.{js,jsx,ts,tsx}
Environment
System:
   OS: Windows 10
Node: v18.14.1

If I disable the line shown above, test will work, but code coverage is not working.