How to troubleshoot LMDB ?

org.fusesource.lmdbjni.LMDBException: Invalid argument
After 1-10 successful transactions with large number of writes to 8 different databases it fails on database.put in particular database. Sometimes the problem is with document of size 210KB, first one, but at other times it works fine with that document and fails on smaller ones. Could anyone please point me in a right direction ?
Issue can be reproduced my project and about any large document. I'm wondering does anyone uses LMDB via lmdbjni in production ?
Thanks

This is actually LMDB native that return a EINVAL. Hard to know exactly what the problem might be. As you can see from C code there are a few cases where this can happen, like incorrect flags, invalid transactions etc.  Hope this helps.
int
mdb_put(MDB_txn *txn, MDB_dbi dbi,
    MDB_val *key, MDB_val *data, unsigned int flags)
{
	MDB_cursor mc;
	MDB_xcursor mx;
	int rc;

	if (!key || !data || !TXN_DBI_EXIST(txn, dbi, DB_USRVALID))
		return EINVAL;

	if (flags & ~(MDB_NOOVERWRITE|MDB_NODUPDATA|MDB_RESERVE|MDB_APPEND|MDB_APPENDDUP))
		return EINVAL;

	if (txn->mt_flags & (MDB_TXN_RDONLY|MDB_TXN_BLOCKED))
		return (txn->mt_flags & MDB_TXN_RDONLY) ? EACCES : MDB_BAD_TXN;

	mdb_cursor_init(&mc, txn, dbi, &mx);
	mc.mc_next = txn->mt_cursors[dbi];
	txn->mt_cursors[dbi] = &mc;
	rc = mdb_cursor_put(&mc, key, data, flags);
	txn->mt_cursors[dbi] = mc.mc_next;
	return rc;
}

Well, that sorta helps, thank you.
I've inserted code that prints a list of present keys, before storing new data, there is no overwrite happening. But now it fails after a few commits while attempting to create cursor for write transaction - and I think that means it's something with transaction itself, do you know if there are any limits on single transaction size ?

Can you provoke the error consistently every time? If not, then it might be a concurrency issue. For example, you may not share transactions between threads. Or maybe you commit/abort the transaction by mistake at some point?
Try isolate the problem, remove code, keep only minimum needed. Then provoke the error again. If you can't reproduce the error from there then move backward by adding more and more code back until you hit the problem.

Thanks, error happens inconsistently (I've removed all multi-threading) on some of transactions, sometimes it's totally fine to add particular document, and sometimes it fails. I'll try another kv-storage to see if issue will persist.

Me and Ben are doing a rewrite of LMDB using JNR-FFI which is almost finished now. You could try that if you want?
https://github.com/lmdbjava/lmdbjava

You should take a look at mdbx from this guys https://github.com/ReOpen/ReOpenLDAP
It's a rewrite of LMDB from Russian company, they use it in production. It only supports linux. I think you mentioned rewrite of LMDB driver, not database itself ? BoltDB is the most famous LMDB rewrite and it is considerably slower, but pure GO, and guys claim it's code is much cleaner.

Poor choice of words. This is not a rewrite of LMDB only the Java and JNI code around it. It should be more robust since its using libffi (not hawtjni) https://sourceware.org/libffi.

Just for history, If someone will google similar problem.
Found cause - closing database after closing environment, I'm wandering why it could work for a few attempts. LMDB could be strange sometimes, but it's  awesome. On my rig it's 2x MapDB on write speed, and write speed is its "weak spot".

@kk00ss Could you please advise why I'm getting same error while doing this ?
val parentTxn = env.createReadTransaction()
val txn = env.createTransaction(txnParent, true) // exception occurs here

exception stack-trace
Exception in thread "main" org.fusesource.lmdbjni.LMDBException: Invalid argument
	at org.fusesource.lmdbjni.Util.checkErrorCode(Util.java:44)
	at org.fusesource.lmdbjni.Env.createTransaction(Env.java:451)

DB is open in write mode.

Hi, there's another driver you would be better off using. It's from the
same team. As this one.
On Jun 19, 2017 18:54, "unoexperto"<EMAIL_ADDRESS>wrote:

@kk00ss https://github.com/kk00ss Could you please advise why I'm
getting same error while doing this ?
val parentTxn = env.createReadTransaction()
val txn = env.createTransaction(txnParent, true) // exception occurs here
exception stack-trace
Exception in thread "main" org.fusesource.lmdbjni.LMDBException: Invalid argument
at org.fusesource.lmdbjni.Util.checkErrorCode(Util.java:44)
at org.fusesource.lmdbjni.Env.createTransaction(Env.java:451)
DB is open in write mode.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/deephacks/lmdbjni/issues/72#issuecomment-309483608,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADz6Eksf--23HPTAQz_XZYT8YN9dxrxSks5sFpm2gaJpZM4JBKK7
.

@kk00ss I'd love to use it!! In fact I wrote first implementation using lmdbjava which is much faster than lmdbjni but it doesn't support custom comparator that I need :( Here is the issue: https://github.com/lmdbjava/lmdbjava/issues/56
Could you please suggest what to do ?

I would go for implementing that comparator. Should be easier then getting
this driver to work.
On Jun 19, 2017 19:35, "unoexperto"<EMAIL_ADDRESS>wrote:

@kk00ss https://github.com/kk00ss I'd love to use it!! In fact I wrote
first implementation using lmdbjava which is much faster than lmdbjni but
it doesn't support custom comparator that I need :( Here is the issue:
lmdbjava/lmdbjava#56 https://github.com/lmdbjava/lmdbjava/issues/56
Could you please suggest what to do ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/deephacks/lmdbjni/issues/72#issuecomment-309495459,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADz6Ekv4FHOEUUuDKE6srAKn1Xhq8piLks5sFqM0gaJpZM4JBKK7
.

@unoexperto That error code is reported by LMDB and its hard to tell what you're doing wrong from the snippet you posted.

Regarding the comparator, we have not yet tried to implement it for lmdbjava but is supect that its possible using JNR. You could try implementing it yourself and post a PR.

@krisskross @kk00ss I'll be happy to contribute but I looked into it and couldn't find example of passing java callback to https://github.com/jnr/jnr-ffi Does it support it ?

Not sure. Haven't looked at the API. Ask them if you don't find it.

In another (closed source) project I have JNR-FFI handling a callback. Here's a (slightly redacted) method signature I put into the Library class, ApiErrorCode process(String filename, Callback callback). The callback interface itself:
import jnr.ffi.Pointer;
import jnr.ffi.annotations.Delegate;

  public interface Callback {
    @Delegate
    CallbackReturn next(Pointer sys, Pointer msg);
  }

Feel free to contribute a PR for the LmdbJava ticket 56 and I'll be happy to review.

Feel free to contribute a PR for the LmdbJava ticket 56 and I'll be happy to review.

FYI LmdbJava 0.6.0 and above now has mdb_set_compare support for user-defined comparators.

INFO: org.fusesource.lmdbjni.LMDBException: Invalid argument
Am getting this exception while setting maxreaders in LMDBJNI...
Env env = new Env();
env.open(LMDB_DIR);
env.setMaxReaders(150);
db = env.openDatabase("sub");
Env is created and initialized in the given path.. But I cannot set maxreaders in LMDBJNI as exception arises. If I skip setting maxreaders, then also am getting exception
org.fusesource.lmdbjni.LMDBException:MDB_READERS_FULL : Environment maxreaders limit
reached
at org.fusesource.lmdbjni.Util.checkErrorCode
at org.fusesource.lmdbjni.Env.createTransaction
at org.fusesource.lmdbjni.Env.createReadTransaction
at org.fusesource.lmdbjni.Database.get(Database.java:170)
Kindly resolve this issue  as this is banging my head for more than a week... Since am new to java programming... Thanks in advance

@Johny-Kirth perhaps try https://github.com/lmdbjava/lmdbjava. It has an up-to-date tutorial and this may make it easier for you to get started.


PubSub Example Errs

Expected Behavior
I would expect to have working pubsub example that I can follow without issues. I would not expect to see a Java exception.
Actual Behavior
The subscriber logs from the pubsub example throws a Java exception while following these instructions from the README.
 Both Dapr and your app logs will appear here.

ℹ
terminated signal received: shutting down
✅  Exited Dapr successfully
❌  Error exiting App: exit status 1

Key errs are below:
== APP == Exception in thread "main" java.lang.reflect.InvocationTargetException
== APP == Caused by: java.lang.ClassNotFoundException: io.dapr.examples.pubsub.Subscriber

Steps to Reproduce the Problem
Follow PubSub README here

/assign

@RidhamModh Please, use Dapr runtime version 1.12.0-rc.3 since there is a bug in 1.10 and 1.11 that does not forward the error correctly. When running dapr init, use dapr init --runtime-version=1.12.0-rc.3


demo script for remoting scenarios

Need demo.ps1 script and corresponding markdown authored for beta1 scenarios, both SSH and WSMan remoting

We need demos for:

[ ] PSRP over SSH with the new parameter sets
[ ] PSRP over WSMan from Linux w/ NTLM auth

@SteveL-MSFT @joeyaiello Where can we find these demos?

@alexandair the SSH one is here: https://docs.microsoft.com/en-us/powershell/scripting/learn/remoting/ssh-remoting-in-powershell-core?view=powershell-6
I thought we had docs for enabling NTLM on Linux, but can't seem to find it.  @joeyaiello ?


About model performance on RealPhoto60

Thank you for the outstanding work! I have tested your code and discovered that some of the generated images fall short of the realism achieved by SUPIR and SeeSR. For your reference, I have included several examples below, arranged from left to right, top to bottom: LQ, SUPIR, SeeSR, and HoliSDiP. Results of HoliSDiP on RealPhoto60 (https://drive.google.com/file/d/1mDwJZcUFK5k2oaOdYEliFXAMvgCtqtIF/view?usp=drive_link)

Hi @yyang181,
Thank you for highlighting these samples and for your feedback!
I have two questions to clarify:

Did you remove the manually added prompts (L34-43 in test.py of SUPIR, and L246-247 in test_seesr.py of SeeSR) during your testing of SUPIR and SeeSR? From my observation, these prompts can significantly influence the quality of the outputs. For our testing, we removed all such additional prompts to fairly demonstrate the true capabilities of our model.
Could you share your observations about the overall performance across the entire dataset?

We appreciate your input and will continue refining our model to push advancements in this field.

Hi @yyang181,
Thank you for highlighting these samples and for your feedback!
I have two questions to clarify:

Did you remove the manually added prompts (L34-43 in test.py of SUPIR, and L246-247 in test_seesr.py of SeeSR) during your testing of SUPIR and SeeSR? From my observation, these prompts can significantly influence the quality of the outputs. For our testing, we removed all such additional prompts to fairly demonstrate the true capabilities of our model.
Could you share your observations about the overall performance across the entire dataset?

We appreciate your input and will continue refining our model to push advancements in this field.

Thanks so much for your reply.
Q1: I use the original test code for SUPIR and SeeSR without removing the manually added prompts. Those prompts are commonly adopted in SR tasks and are proven to be effective. Does HoliSDiP support such manually added prompts, like "Cinematic, High Contrast, ultra HD", to improve the quality of outputs?
Q2: I use OESDiff Evalution Metrics code to check the performance and below is the reported indexes on RealSR.
==== My observation Average Metrics for [RealSRVal_crop128] =====
PSNR: 25.1365 SSIM: 0.7148 LPIPS: 0.3173 DISTS: 0.2361 CLIPIQA: 0.7231 NIQE: 5.8020 MUSIQ: 70.0355 MANIQA: 0.6497 CLIPIQA+VITL14_512: 0.5727 | FID: 132.461434 | FID Runtime: 5.87 sec
==== HoliSDiP Paper for RealSR =====
PSNR: 23.5303 SSIM: 0.6883 LPIPS: 0.3165 DISTS: /          CLIPIQA: 0.7109 NIQE: /           MUSIQ: 69.7217 MANIQA: 0.5741 CLIPIQA+VITL14_512:  /          | FID: / |              FID Runtime:/ sec

Hi @yyang181,

You can also try to add these prompt in L332-333 of our testing code. However, we didn't put the effort in fine-tuning these prompts, as they are not our core contribution.
The top row of performance is based on which model? My original question aims to use the same settings (w/o additional prompts) to compare these three models (SeeSR, SUPIR, HoliSDiP) for a fair comparison. Also, you can try our evaluation code to produce the reported results.

Hi @yyang181,

You can also try to add these prompt in L332-333 of our testing code. However, we didn't put effort in fine-tuning these prompts, as they are not our core contribution.
The top row of performance is based on which model? My original question aims to use the same settings (w/o additional prompts) to compare these three models (SeeSR, SUPIR, HoliSDiP) for a fair comparison. Also, you can try our evaluation code to produce the reported results.

I think the segmentation map of real world's LR is not accurate.. Maybe you should the result of 1stage model(such as Real-ESRNet) to extract the seg map?


Use RunSettingsFilePath from when using dotnet test

Description
Uses the RunSettingsFilePath from project file when specified and falls
back to the one specified in console, or the default setting if none are
provided.
The path to the settings file can be specified in multiple ways,
for example as a path relative to the project file. This enables
dotnet test to be invoked against the project file directly.
<RunSettingsFilePath>$(ProjectDir)..\example.runsettings</RunSettingsFilePath>

Alternatively path can also be specified relatively to solution file, but that will
only work when running dotnet test against the solution. On the other hand the
setting will be the same in all projects.
<RunSettingsFilePath>$(SolutionDir)\example.runsettings</RunSettingsFilePath>

The setting file can be overridden by specifying --settings from the command line
to give flexibility in providing alternative runsettings.
Related issue
Fixes #2265

@ViktorHofer You might want to take a look at this one.

The path to the settings file can be specified in multiple ways

My understand was that we can point to any runsettings file anywhere on disk. Your description indicates that we can only point to a project level or solution level runsettings file. Is that correct?

You can point to a file anywhere on the disk.
The given examples use paths relative to a project or solution file, because I assumed that is what people will want to do most often. But you are not limited to do just that. You can use absolute path as well.

Great, just wanted to make sure of that. Thanks.


add hdp 2.6.2-205

Add support for HDP 2.6.2-205 and <IP_ADDRESS>-40.
http://s3.amazonaws.com/public-repo-1.hortonworks.com/index.html#/HDP/centos7/2.x/updates/<IP_ADDRESS>
http://s3.amazonaws.com/public-repo-1.hortonworks.com/index.html#/HDP/centos7/2.x/updates/<IP_ADDRESS>

There are changes needed for the repo recipe too... see for example https://github.com/caskdata/hadoop_cookbook/pull/333/files


fix: disable pipes on both children and parent properties

Fixes #1185

Wanted to do a bit of refactoring to clean some of the path handling up in general here, so closing this in favor of that, but thanks for reporting the bug and this implementation 👍


WIP [depends on #1743] Openstack infra heat stack and parameters collection

Adding heat stacks and params to OpenstackInfra. Just 3 last commits are relevant, rest are dependencies.
This is first step of scaling OpenStack, using ManageIQ. I am adding minimum required for refresh:
stack - so we can see status of scaling and scale stacks
parameters - so we can get parameters used for scaling, like current counts of scaled hosts
Second patch is showing it in the UI, in the detail page of the provider.
Since you will be working on the full Heat refresh, I will use that in the future. Again with abstracting the functionality and using it in both OpenStack providers. This is just temporary quick heat refresh so I don't duplicate effort in this area.
Third patch are basic tests

@gmcculloug @bzwei Please review.

@ladas, can you add an explanation to the PR body?  I believe I know, but it would help with reviewing it. Thanks

@blomquisg adding description, sorry about that :-)

@JPrause @jvlcek sorry for the spam, the commit here is just dependency, please review gem change here #1354

@Ladas We will begin the work for Heat refresh soon, this or next sprint. I will consolidate the need for both openstack cloud and infra. I am OK with your existing work. It is your choice whether you want to hold this PR or merge it first (subject to be refactored)

@bzwei If the dependencies of this will be merged soon, I think we can merge this. I might have some time left at the end of our sprint, so I could theoretically do the Heat refresh for both, if you want. It shouldn't take more than couple of days, given it's basically done for Amazon.

@Ladas That will be great if we can have the complete support for openstack orchestration refreshing in one merge. Collection logic of stacks for cloud and infra should share the same code. The inventory saving logic should share same code for all (AWS, OpenStack, OpenStackInfo). We have save_inventory_cloud and save_inventory_infra separated. We may introduce a module for saving inventory orchestration and share it.

@bzwei Right, the saving code should be very similar. Though I might probably start with OpenStack saving code and then try to merge it with AWS, cause I expect some differences.
We might want this patch merged in first, since it's needed for Scaling of the OpenStack cloud. I would send another PR with full refresh. My estimate is getting onto this somewhere in the end of the next week. So let me know if you will not start on this sooner. :-)

@Ladas ... looks like a legit test failure with floating ips, maybe?

@blomquisg hm, not sure how this code could affect amazon tests

removing wip, #1743 merged

@blomquisg I am trying to send test patch if it helps. But no way this code affects that area. Maybe it's test ordering bug @jrafanie talked about?
@jrafanie the last commit is a fix of the test failure, have you seen such failure?

Thanks @Ladas, you're on the right track.  I think that last commit SHOULD not be needed.  The fact that FloatingIp.count went from 5 to 0 and now a subsequent ClouldNetwork assertion failing is a symptom of something else being wrong:
  1) EmsRefresh::Refreshers::Ec2Refresher will perform a full refresh
     Failure/Error: CloudNetwork.count.should                == 3
       expected: 3
            got: 0 (using ==)

@Ladas Is the ec2_refresher_spec test failing in isolation for you? Or with the larger ems_refresh suite?  bin/rspec spec/models/ems_refresh?
@bzwei in afced0e4a58a5961a7059fb11a7599530cc03a38, you modified the FloatingIp.count from from 4 to 5 and CloudNetwork from 1 to 3.  Can you take a look at @Ladas's code change to try to understand why spec/models/ems_refresh/refreshers/ec2_refresher_spec.rb is failing?

@jrafanie thanks, I will check it out tomorrow. Btw. locally running spec:models, I see even more failures in more providers :-(

@jrafanie so running
rake spec SPEC=spec/models/ems_refresh/refreshers/ec2_refresher_spec.rb
fails for me locally with the same error

@jrafanie @blomquisg gah, it's the saving methods conflicting with cloud. I'll fix that

@jrafanie @blomquisg ok, it should pass now. Saving code, unline parsing, is only one class for everything, so including the same method for saving stack has overwritten it for cloud and messed cloud up. Too many modules. :-)


Monsterbox fixes

This makes the following changes to the monsterbox:

Makes the text and lines the full width of the column and has the border spill into the margin and column separator.
Removes excess spacing after (and also before for monsterboxnbg) so there is not excess space between stat blocks when there are multiples.
Grouped basic, stats, and details sections to contain the color change.to those sections.
Adjusted spacing line spacing (mostly to get it back to the way it was).
Only the challenge rating number needs to be supplied now.
Adjusted \hline point height (for those who can tell the difference between .03 tikz units).
Added non-breaking spaces to \dice macro to keep the "10 (3d4 + 3)" together on 1 line.

There is a lot going on in this PR. So I would appreciate anyone's help who can look over this one for unintended consequences.

Added non-breaking spaces to \dice macro to keep the "10 (3d4 + 3)" together on 1 line.

Just a note that D&D books don't use non-breaking spaces here at all.
E.g. MM p.47 (Death Knight, Longsword); MM p.297 (Vampire, Bite).

Just a note that D&D books don't use non-breaking spaces here at all.
E.g. MM p.47 (Death Knight, Longsword); MM p.297 (Vampire, Bite).
P.S.: May be should be a non-default option (\dice* etc.)?

Thanks, I was having trouble finding any examples. I will revert that change.
My licensor is interested in not having the dice roll break over a line. So I guess my best option is to save the \dice command wrap it in an \mbox to keep it from breaking.
\let\dnddice\dice
\renewcommand{\dice}[1]{\mbox{\dnddice{#1}}}

I will have to play with it a bit to make sure it works the way that I want.


Fix opencensus agent to be java6 compatible.

Fixes https://github.com/census-instrumentation/opencensus-java/issues/616

Changes Unknown when pulling 273aea7bf29777c77a36fdee0bbbae47ac1ef9e8 on bogdandrutu:agentfix into ** on census-instrumentation:master**.

Codecov Report

Merging #619 into master will increase coverage by 0.03%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #619      +/-   ##
============================================
+ Coverage     75.42%   75.45%   +0.03%
  Complexity      703      703
============================================
  Files           128      128
  Lines          3328     3329       +1
  Branches        308      307       -1
============================================
+ Hits           2510     2512       +2
  Misses          755      755
+ Partials         63       62       -1

Impacted Files
Coverage Δ
Complexity Δ

...in/java/io/opencensus/contrib/agent/Resources.java
57.14% <100%> (+7.14%)
3 <0> (ø)
:arrow_down:

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 9209e54...273aea7. Read the comment docs.

Thanks!
Not yet sure, why how/why this issue surfaced - potentially it indicates an issue with Retrolambda (or maybe again the execution order of gradle tasks).
I haven't seen the issue before and cannot reproduce it (without this change, of change). If you happen to have additional input, PLKM.


Fix DeserializeStage to ensure output messages correctly contain the correct rows for each batch

Description

DeserializeStage now performs a copy of the rows needed for each batch, ensuring each output ControlMessage now has a unique MessageMeta and underlying DataFrame
Works-around issue where calling SlicedMessageMeta::get_mutable_info().checkout_obj() returns the entire DataFrame
This unfortunately means that DeserializeStage will require the GIL.
Remove unused make_output_message method
Avoid some redundant code in SlicedMessageMeta (unrelated but I was in this part of the code).

Closes #2002
By Submitting this PR I confirm:

I am familiar with the Contributing Guidelines.
When the PR is ready for review, new or existing tests cover these changes.
When the PR is ready for review, the documentation is up to date with these changes.

/merge


Improvement on US phone numbers bonfire

Challenge Bonfire: Validate US Telephone Numbers needs an improvement.
I'm struggling because I don't know why "6505552368" isn't a US phone numbers, maybe adding a link to explain how US phone numbers are build can be a good decision for non US resident.

Thanks for reporting the issue, @florianpnn!
That is a valid US phone number. But look at the test case more closely:
assert.deepEqual(telephoneCheck("(6505552368)"), false);

The number is wrapped inside brackets, which is not a valid form of writing phone numbers. It would have been valid if only the first three digits were wrapped in brackets, but in this case, the entire number is wrapped in brackets.
I am closing the issue because I believe that resolves your issue. Feel free to reopen if you feel it didn't (or need further clarification) :)

I had a lot of trouble with this bonfire as well, because of<PHONE_NUMBER>). After reading this, it was apparent it should fail because it doesn't match one of the criteria, but it wasn't apparent to me or my program at the time :)


Able to perform many parallel re-interviews for battery devices

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?
NO, my problem is NOT within Z-Wave JS UI
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
What causes the bug?
I can submit an "unlimited" (not sure the real number, I tried around 50) re-interview requests to a sleeping node, and all requests are honored.
What do you observe?
The driver will perform all interview steps N times in parallel for every request.
What did you expect to happen?
The driver would ignore the duplicate requests and only perform one re-interview.
Steps to reproduce the behavior:
It can be reproduced in either HA w/the integration, or zwave-js-ui, but the former is easier if you want to issue a lot of commands. Use re-interview in zwave-js-ui a few times for the same effect.

Go to the device page in HA for a sleeping device
Click on the '...' overflow menu
Click re-interview
Click "Start re-interview" as many times as desired, e.g. 50 times. Clicking on the button won't show much feedback, but it is sending the commands to the driver
Wake up the sleeping device to being the interview
Observe the driver is performing all N interviews at the same time

Device information
Any sleeping device presumably.
How are you using node-zwave-js?

[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker image (latest)
[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker image (dev)
[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[X] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
version:
node-zwave-js branch: 10.2.0
zwave-js-ui branch: 8.0.0
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
Don't know, this is a new device
If yes, where did it work?
No response
Attach Driver Logfile
zwavejs_current.log

yeah, I think the real number is whatever your machine can handle 🙈


Client portal myCalendar reservation specification - UI + API

myCalendar API
Based on https://learn.microsoft.com/en-us/graph/api/resources/booking-api-overview?view=graph-rest-1.0
The Client Portal provides customers access to the content and services provided by an organisation. One service which is needed in the future is a reservation booking service.  This would allow customers to book and manage service appointments with staff members of the organisation.  The organisation would then need a way to create and manage their bookable services, and match available staff to customers based on mutual availability.
Some of the noteworthy challenges involved

Displaying available booking time slots taking business hours and staff availability into account
Ensuring that a staff member is available before a customer can book an appointment
Limiting / specifying the length of a particular service appointment (for example, an appointment with a social worker regarding a child should last 1 hour by default)
Making sure that appointments are booked or cancelled reasonably far enough in advance
Sending notifications when a booking is created / updated
Sending reminders to customers/staff at certain intervals

Directly integrating with Microsoft’s Booking API via Microsoft’s Graph API requires a Microsoft 365 Business Premium subscription (22 dollars per user/month). For this reason, it makes sense to create our own API for local development and testing.
https://www.microsoft.com/en-us/microsoft-365/business/compare-all-microsoft-365-business-products
—————————————
The myCalendar API includes the following resources:
Main resources
bookingBusiness
bookingStaffMember
bookingService
bookingAppointment
bookingCustomer
bookingSchedulingPolicy
bookingCustomQuestion
bookingReminder
bookingBusiness
The top level object in the API.  Example properties include

Business name
Contact info
Scheduling policy (see bookingSchedulingPolicy resource)

Related business objects such as

appointments
customers
services
staff members

bookingStaffMember
Represents staff members of the bookingBusiness. Example properties include

List of staff member names
Roles
Email addresses
Whether staff have notifications enabled
Properties to control scheduling based on either the business hours, the personal calendar of the staff member, or a combination of both.
workingHours: The range of hours each day of the week that the staff member is available for booking. By default, they are initialised to be the same as the businessHours property of the business.
useBusinessHours: True means the staff member's availability is as specified in the businessHours property of the business. False means the availability is determined by the staff member's workingHours property setting.
availabilityIsAffectedByPersonalCalendar: API would verify the staff member's availability in their personal calendar in Microsoft 365, before making a booking
etc.

bookingService
Information related to the service being provided by a bookingBusiness.  Example properties include

The service name
Location where the service takes place
The staff who provide the service
Default duration of the service
Scheduling policy (see bookingSchedulingPolicy resource)
Notes
postBuffer: The time to buffer after an appointment for this service ends, and before the next customer appointment can be booked
preBuffer: The time to buffer before an appointment for this service can start
etc.

bookingAppointment
Represents a customer appointment for a bookingService performed by a set of staff members.  Example properties include

Represent the customers for this appointment
Reminders a customer specified for this appointment
The amount of time to reserve before and after the appointment
Notes from the booking staff member
Start dateTime
etc.

bookingCustomer
Represents a customer of the bookingBusiness.  Example properties include

Customer address
Customer name
Email
Phone number

bookingSchedulingPolicy
Provide the ability to select staff members for a booking, and provide properties for managing booking time durations and lead times.  Example properties include

maximumAdvance: Maximum number of days in advance that a booking can be made.
minimumLeadTime: The minimum amount of time before which bookings and cancellations must be made.
timeSlotInterval: Duration of each time slot
sendConfirmationsToOwner: Send notifications to business email when a booking is made
Etc.

bookingCustomQuestion
Properties to represent questions to ask a customer when making a reservation.  Example properties include

Question value
Answer values
Answer input types (text, radio button, select, etc.)

bookingReminder
Represents when and whom to send an email reminder. Example properties include

Specify the offset (how often to send reminders)
Message value
Message recipients

Create a new booking

Confirmation of booking + Viewing all of my bookings

Initial mock UI

Uses mock data and cannot actually be edited
Is implemented only for DESKTOP view

Booking management view

Cancel booking

Edit booking


Traverse from a5_town_start to a5_malah (no automatic movement) v.0.6.4

Bot can traverse anywhere even to revive merc etc but if traversing to malah the cursor just hovers a little to my left and does nothing, If I press the mouse button to move to the location pointed by the bot myself the pathing works and vendor is found. Its like the mouse click to move is not initiated by the bot?!

Found the problem, correct operation seems to require the force_move key to been set correctly.
Should maybe added as a hint to the params file.

Hello.
Could you please tell me how to assign a key to "force_move" option?
I don't have this option in the in-game keyboard setup and I'm stuck.
Regards


Chunk Size and Certificate Size Misuse in GetCertificateChain Command

NCC report page 30

This has been fixed before the release of the report in #169


API: UniTask.Delay is inconsistent with .NET Task.Delay

I read your announcement blog post and UniRx.Async looks pretty cool. However, the inputs to Delay seem confusing:
public static UniTask<int> Delay(int delayFrameCount, PlayerLoopTiming delayTiming = PlayerLoopTiming.Update, CancellationToken cancellationToken = default(CancellationToken))
public static UniTask Delay(TimeSpan delayTimeSpan, PlayerLoopTiming delayTiming = PlayerLoopTiming.Update, CancellationToken cancellationToken = default(CancellationToken))

They're the same except for the first argument, which makes sense except that it's easy to confuse them. Also, .NET's Task.Delay takes milliseconds or a TimeSpan (both are effectively the same thing), so this is doubly confusing.
I'd suggest to rename the framecount variant to avoid user confusion.
Suggestions: Defer, Wait, Skip, FrameDelay.

Thanks, yes i agree.
UniRx exists DelayFrame method.
I'll change DelayFrame to next update.

6.1.0(6.1.2) includes this changes.


Add note to readme about puppetserver JRUBY

Need to add to docs:
ini_setting { "Change jruby to 9k":
    ensure  => present,
    setting => 'JRUBY_JAR',
    path    => "/etc/sysconfig/puppetserver",
    key_val_separator => '=',
    section => '',
    value   => '"/opt/puppetlabs/server/apps/puppetserver/jruby-9k.jar"',
    show_diff => true,
    notify  => Class['puppetserver::service']
  }

See https://github.com/petems/petems-hiera_vault/issues/5, #14 and possibly #18

Note added to Readme (8b54fbe735d6bb9862c2f2eca6853e84b3518947)


Create liquidhaskell.yml

Thanks for your contribution @nikivazou. I changed the category to linter, as we only separate between formatters and linters at the moment. It would be nice to have more fine-grained categories, but that would require some extra relabelling work. Hope that's fine.


Use Size Limit to calculate size

I read 7.0 changelog and was very happy reducing project file size. Great work, @Andarist.
And I bring a good thing for you — Size Limit. It is a special tool to calculate project cost of users. It is highly accurate and gives you important feedback for optimization.

It doesn’t just take file size. JS file in npm package could have one size, but bloat few times when webpack or Rollup will add a file to bundle. For instance, JS file could have a big dependency. Or it could use process in the wrong way and bundler will add process polyfill. This is why Size Limit emulate the real case. It creates the empty project in the memory, adds your library as dependency and then checks project bundle size.
Size Limit has awesome npx size-limit --why tool which shows you the reason for this size. Here is  current results:

(Note, that PropTypes still in the bundle, this is why Size Limit’s size is bigger)
Of course, Size Limit is not just a rando tool from the Internet. It is used by PostCSS, Autoprefixer, Material UI. And Size Limit’s feedback really improved the size of this projects (you can find examples in Size Limie readme).
If you like the idea to use this special tool for checking the size, please check my PR. update-size must be called only after building step. Did I make PR right?

Thanks for the PR! I was considering using some dedicated tool for this (i've looked briefly into size-limit too). I'm not opposed to using one - especially I'd like to chose 1 tool and configure more packages with it.
The problem I have is that it's IMHO those measurements are often hard to get right (each situation is different) and often they might misinform the people looking at them. I.e. I don't believe we should count webpack's runtime wrapper - this is not the cost of a module. Also I don't quite think prop-types package should be counted here either - most people have it in their bundles anyway, so it wouldn't be an added cost. While I remove propTypes now in production mode, it's not possible (at least I don't know how) to remove the import 'prop-types' declaration because of ESM static nature.
I agree that one thing is what's the size of the module itself, one thing is what's the size of the module and its dependencies and I think both are valuable metrics.
Open question - I'm wondering how we should measure tree-shakeable libraries. Let's take polished lib as an example - it's totally tree-shakeable so it's actual cost may vary A LOT, because it depends on the actual usage and not on what a library in question provides.
Don't take me wrong - I would very much like to chose some tool for the job. This answer is more of a discussion starter right now than a direct response to this PR.

Also I don't quite think prop-types package should be counted here either - most people have it in their bundles anyway, so it wouldn't be an added cost.

@Andarist I removed prop-types from size calculation

I.e. I don't believe we should count webpack's runtime wrapper - this is not the cost of a module.

We didn’t have a perfect way to calculate the real cost since all projects (which will use your module) are different. The only thing we can try to select a better way from available.

Open question - I'm wondering how we should measure tree-shakeable libraries. Let's take polished lib as an example - it's totally tree-shakeable so it's actual cost may vary A LOT, because it depends on the actual usage and not on what a library in question provides.

The bundler way to calculate size is perfect for this case. We can emulate project which uses only some of the functions and sees project size after tree-shaking (since there is a limits in tree-shaking this bundler-way will show mistakes in using tree-shaking).

it's not possible (at least I don't know how) to remove the import 'prop-types' declaration because of ESM static nature.

I think there is a Bable plugin for it. If I understood you correctly.

We didn’t have a perfect way to calculate the real cost since all projects (which will use your module) are different. The only thing we can try to select a better way from available.

I agree, but I'm also wondering if rollup shouldnt be used instead as baseline because it bundles only what's really provided by the lib. As to i.e. process misusage & such - we could just lint it, make an audit instead of measurement for such things. Not sure if it's better - just thinking out loud.

The bundler way to calculate size is perfect for this case. We can emulate project which uses only some of the functions and sees project size after tree-shaking (since there is a limits in tree-shaking this bundler-way will show mistakes in using tree-shaking).

Maybe it would be good to incorporate some ideas from https://github.com/TrySound/rollup-plugin-size-snapshot

I think there is a Bable plugin for it. If I understood you correctly.

I'm using it here, but what I meant is that it can remove Comp.propTypes = {}, but it cannot remove import PropTypes from 'prop-types' for prod builds (unless package consumers use it).
Could u rebase against master?
Question - does size-limit stores last value somewhere? What's important to me is to track size changes, but not necessarily to setup a threshold.

Question - does size-limit stores last value somewhere (like if I would setup CI integration)?

Yeap, you can have .size-limit.js config with the limit. But I didn’t add the limit since I didn’t found .travis.yml or test script in package.json.
I added the config. Just add size-limit script to your test suit.

Could u rebase against master?

Done

If plugin removed only require() (I tested only them) but not import, you can always remove any import by browsers in package.json. And it is the good reason to create an issue, removing import is easy.

That's the problem - plugin can remove require because it's dynamic, so it can just wrap call to it in NODE_ENV check, but imports cannot be wrapped because they are static. Not sure how to work around this issue on library's side (in application it's easy - u have to just remove it, but in lib u want to keep import for dev builds but remove for prod).
I'll respond to the rest some time later.

Here is a article with a reasons behind Size Limit metrics
https://evilmartians.com/chronicles/size-limit-make-the-web-lighter

Any updates? The project anyway use library size metric, Size Limit just make it more accurate.

@Andarist done :+1:

Thanks for keeping up with me 👍


Add reading and writing example

I ran into issues trying to get a duplex pipeline working. It took me a few hours to figure out I should have been using tokio_util::codec::Framed. This PR attempts to add a duplex pipeline example showing:

How to set up a duplex pipeline
How to use none SymmetricallyFramed transport to serialize/deserialize to and from a Request and Response struct.
How to send and receive after each other

Started a new project using tokio-serde, couldn't figure out how to do Framed and ran into my own PR....
@carllerche any chance we could merge this?


Sharable data on Public Data Sharing page is outdated

On the Public Data Sharing page (https://www.openhumans.org/public-data/), the list of sharable data is outdated:
23andMe (genotyping data)
American Gut (gut microbiome profiling)
Fitbit (Health and activity data)
Jawbone (Health and activity data)
GoViral (viral surveillance and profiling)
Harvard PGP (whole genome data)
RunKeeper (GPS activity tracking)
Wild Life of Our Homes (environmental microbiome profiling)

fixed by #595


Implement reading xctestrun files and multiple cleanups

Removed a bunch of unnecessary abstractions and generally moved
towards a bundle-centric instead of an app-centric world view.

Clean up errors by reworking BP_ERROR to BP_SET_ERROR that handles
the error == nil case.

Changed the name of a bunch of properties to better match what's in
the .xctestrun files.

Check that the app we're given is actually built for the
iphonesimualtor and not for iphoneos.

Since we're getting environment variables and commandline arguments
from the .xctestrun file now, they are properly expanded.

@ob Oh, it would also be great if you could include the testing of the parsing of the xctestrun file

@ob I cannot find the change to the docs that describe this option. Can you point me to where this is, or, if you haven't yet, can you add it to the README.md?

When I run this, I am getting this error:
[17:57:48]: ▸ {97954} 20170613.175748 [  ERROR ] (BP-1) hostBundleId: (null) or hostBundlePath: /Users/lyndsey.ferguson/repo/ios/fastlane/__TESTROOT__/UI Testing-iphonesimulator/MyAwesome.app is null

It looks like __TESTROOT__ is not being replaced in this case

This may still have some issues with UI tests. The tests do not seem to be ever started. I've been waiting 10 minutes and nothing has started testing yet. Normally I do see the tests started after a few minutes:
bluepill  -c /tmp/bluepill_options.json || true
[21:21:39]: ▸ {12932} 20170613.212139 [  INFO  ] This is Bluepill v1.0.2-58-g7719d40
[21:21:39]: ▸ {12932} 20170613.212139 [  INFO  ] Running with 4 simulators.
[21:21:39]: ▸ {12932} 20170613.212139 [  INFO  ] Packed tests into 5 bundles
[21:21:39]: ▸ {12932} 20170613.212139 [  INFO  ] Started Simulator 1 (PID 12953).
[21:21:39]: ▸ {12953} 20170613.212139 [  INFO  ] (BP-1) Running Tests. Attempt Number 1.
[21:21:39]: ▸ {12953} 20170613.212139 [  INFO  ] (BP-1) [Attempt 1] Create Simulator
[21:21:40]: ▸ {12932} 20170613.212140 [  INFO  ] 1 Simulator still running. [1]
[21:21:40]: ▸ {12932} 20170613.212140 [  INFO  ] Using 324 of 1064 processes.
[21:21:40]: ▸ {12932} 20170613.212140 [  INFO  ] Started Simulator 2 (PID 12956).
[21:21:40]: ▸ {12953} 20170613.212140 [  INFO  ] (BP-1) Running in NON-headless mode...
[21:21:40]: ▸ {12956} 20170613.212140 [  INFO  ] (BP-2) Running Tests. Attempt Number 1.
[21:21:40]: ▸ {12956} 20170613.212140 [  INFO  ] (BP-2) [Attempt 1] Create Simulator
[21:21:41]: ▸ {12956} 20170613.212141 [  INFO  ] (BP-2) Running in NON-headless mode...
[21:21:41]: ▸ {12953} 20170613.212141 [  INFO  ] (BP-1) Simulator 5953144F-3CB1-4B4E-9376-C44FF68FD489 achieved the BOOTED state
[21:21:41]: ▸ {12953} 20170613.212141 [  INFO  ] (BP-1) Completed: [Attempt 1] Create Simulator 5953144F-3CB1-4B4E-9376-C44FF68FD489
[21:21:41]: ▸ {12956} 20170613.212141 [  INFO  ] (BP-2) Simulator A9B1C263-452B-43FD-8AB8-A8982DB80EEC achieved the BOOTED state
[21:21:41]: ▸ {12953} 20170613.212141 [  INFO  ] (BP-1) [Attempt 1] Install Application
[21:21:41]: ▸ {12956} 20170613.212141 [  INFO  ] (BP-2) Completed: [Attempt 1] Create Simulator A9B1C263-452B-43FD-8AB8-A8982DB80EEC
[21:21:41]: ▸ {12956} 20170613.212141 [  INFO  ] (BP-2) [Attempt 1] Install Application
[21:21:41]: ▸ {12932} 20170613.212141 [  INFO  ] Started Simulator 3 (PID 12965).
[21:21:42]: ▸ {12965} 20170613.212142 [  INFO  ] (BP-3) Running Tests. Attempt Number 1.
[21:21:42]: ▸ {12965} 20170613.212142 [  INFO  ] (BP-3) [Attempt 1] Create Simulator
[21:21:43]: ▸ {12932} 20170613.212143 [  INFO  ] Started Simulator 4 (PID 13007).
[21:21:44]: ▸ {12965} 20170613.212144 [  INFO  ] (BP-3) Running in NON-headless mode...
[21:21:45]: ▸ {13007} 20170613.212145 [  INFO  ] (BP-4) Running Tests. Attempt Number 1.
[21:21:45]: ▸ {13007} 20170613.212145 [  INFO  ] (BP-4) [Attempt 1] Create Simulator
[21:21:45]: ▸ {13007} 20170613.212145 [  INFO  ] (BP-4) Running in NON-headless mode...
[21:21:45]: ▸ {12965} 20170613.212145 [  INFO  ] (BP-3) Simulator B6F723DF-ECDA-4942-B0C2-EA11111C4393 achieved the BOOTED state
[21:21:45]: ▸ {12965} 20170613.212145 [  INFO  ] (BP-3) Completed: [Attempt 1] Create Simulator B6F723DF-ECDA-4942-B0C2-EA11111C4393
[21:21:45]: ▸ {12965} 20170613.212145 [  INFO  ] (BP-3) [Attempt 1] Install Application
[21:21:46]: ▸ {13007} 20170613.212146 [  INFO  ] (BP-4) Simulator 3F4D669D-7115-4FE9-9C08-338680DFF44F achieved the BOOTED state
[21:21:46]: ▸ {13007} 20170613.212146 [  INFO  ] (BP-4) Completed: [Attempt 1] Create Simulator 3F4D669D-7115-4FE9-9C08-338680DFF44F
[21:21:46]: ▸ {13007} 20170613.212146 [  INFO  ] (BP-4) [Attempt 1] Install Application
[21:22:11]: ▸ {12932} 20170613.212211 [  INFO  ] 4 Simulators still running. [1, 2, 3, 4]
[21:22:11]: ▸ {12932} 20170613.212211 [  INFO  ] Using 562 of 1064 processes.
[21:22:41]: ▸ {12932} 20170613.212241 [  INFO  ] 4 Simulators still running. [1, 2, 3, 4]
[21:22:41]: ▸ {12932} 20170613.212241 [  INFO  ] Using 570 of 1064 processes.
[21:22:51]: ▸ {12953} 20170613.212251 [  INFO  ] (BP-1) Completed: [Attempt 1] Install Application
[21:22:51]: ▸ {12953} 20170613.212251 [  INFO  ] (BP-1) [Attempt 1] Launch Application
[21:22:51]: ▸ {13007} 20170613.212251 [  INFO  ] (BP-4) Completed: [Attempt 1] Install Application
[21:22:51]: ▸ {13007} 20170613.212251 [  INFO  ] (BP-4) [Attempt 1] Launch Application
[21:22:51]: ▸ {12953} 20170613.212251 [  INFO  ] (BP-1) Async Launch Returned[Attempt 1] Launch Application
[21:22:51]: ▸ {13007} 20170613.212251 [  INFO  ] (BP-4) Async Launch Returned[Attempt 1] Launch Application
[21:22:52]: ▸ {12956} 20170613.212252 [  INFO  ] (BP-2) Completed: [Attempt 1] Install Application
[21:22:52]: ▸ {12956} 20170613.212252 [  INFO  ] (BP-2) [Attempt 1] Launch Application
[21:22:52]: ▸ {12965} 20170613.212252 [  INFO  ] (BP-3) Completed: [Attempt 1] Install Application
[21:22:52]: ▸ {12965} 20170613.212252 [  INFO  ] (BP-3) [Attempt 1] Launch Application
[21:22:52]: ▸ {12965} 20170613.212252 [  INFO  ] (BP-3) Async Launch Returned[Attempt 1] Launch Application
[21:22:52]: ▸ {12956} 20170613.212252 [  INFO  ] (BP-2) Async Launch Returned[Attempt 1] Launch Application
[21:23:12]: ▸ {12932} 20170613.212312 [  INFO  ] 4 Simulators still running. [1, 2, 3, 4]
[21:23:12]: ▸ {12932} 20170613.212312 [  INFO  ] Using 654 of 1064 processes.
[21:23:42]: ▸ {12932} 20170613.212342 [  INFO  ] 4 Simulators still running. [1, 2, 3, 4]
[21:23:42]: ▸ {12932} 20170613.212342 [  INFO  ] Using 665 of 1064 processes.
[21:24:12]: ▸ {12932} 20170613.212412 [  INFO  ] 4 Simulators still running. [1, 2, 3, 4]
[21:24:12]: ▸ {12932} 20170613.212412 [  INFO  ] Using 659 of 1064 processes.
[21:24:28]: ▸ {12953} 20170613.212428 [  INFO  ] (BP-1) Launch succeeded
[21:24:28]: ▸ {12953} 20170613.212428 [  INFO  ] (BP-1) No error
[21:24:28]: ▸ {12953} 20170613.212428 [  INFO  ] (BP-1) Completion block for launch
[21:24:28]: ▸ {12953} 20170613.212428 [  INFO  ] (BP-1) Calling completion block with: (null) - 15148
[21:24:28]: ▸ {12953} 20170613.212428 [  INFO  ] (BP-1) Completed: [Attempt 1] Launch Application
[21:24:28]: ▸ {12965} 20170613.212428 [  INFO  ] (BP-3) Launch succeeded
[21:24:28]: ▸ {12965} 20170613.212428 [  INFO  ] (BP-3) No error
[21:24:28]: ▸ {12965} 20170613.212428 [  INFO  ] (BP-3) Completion block for launch
[21:24:28]: ▸ {12965} 20170613.212428 [  INFO  ] (BP-3) Calling completion block with: (null) - 15147
[21:24:28]: ▸ {12965} 20170613.212428 [  INFO  ] (BP-3) Completed: [Attempt 1] Launch Application
[21:24:28]: ▸ {13007} 20170613.212428 [  INFO  ] (BP-4) Launch succeeded
[21:24:28]: ▸ {13007} 20170613.212428 [  INFO  ] (BP-4) No error
[21:24:28]: ▸ {13007} 20170613.212428 [  INFO  ] (BP-4) Completion block for launch
[21:24:28]: ▸ {13007} 20170613.212428 [  INFO  ] (BP-4) Calling completion block with: (null) - 15149
[21:24:28]: ▸ {13007} 20170613.212428 [  INFO  ] (BP-4) Completed: [Attempt 1] Launch Application
[21:24:28]: ▸ {12956} 20170613.212428 [  INFO  ] (BP-2) Launch succeeded
[21:24:28]: ▸ {12956} 20170613.212428 [  INFO  ] (BP-2) No error
[21:24:28]: ▸ {12956} 20170613.212428 [  INFO  ] (BP-2) Completion block for launch
[21:24:28]: ▸ {12956} 20170613.212428 [  INFO  ] (BP-2) Calling completion block with: (null) - 15146
[21:24:28]: ▸ {12956} 20170613.212428 [  INFO  ] (BP-2) Completed: [Attempt 1] Launch Application
[21:24:42]: ▸ {12932} 20170613.212442 [  INFO  ] 4 Simulators still running. [1, 2, 3, 4]
[21:24:42]: ▸ {12932} 20170613.212442 [  INFO  ] Using 685 of 1064 processes.
[21:24:58]: ▸ {12956} 20170613.212458 [  INFO  ] (BP-2) Daemon ready to execute test plan (protocol version 22)
[21:24:58]: ▸ {12953} 20170613.212458 [  INFO  ] (BP-1) Daemon ready to execute test plan (protocol version 22)
[21:24:58]: ▸ {12965} 20170613.212458 [  INFO  ] (BP-3) Daemon ready to execute test plan (protocol version 22)
[21:24:58]: ▸ {13007} 20170613.212458 [  INFO  ] (BP-4) Daemon ready to execute test plan (protocol version 22)
[21:24:58]: ▸ {12965} 20170613.212458 [  INFO  ] (BP-3) Test plan started!
[21:24:58]: ▸ {12953} 20170613.212458 [  INFO  ] (BP-1) Test plan started!
[21:24:58]: ▸ {12956} 20170613.212458 [  INFO  ] (BP-2) Test plan started!
[21:24:58]: ▸ {13007} 20170613.212458 [  INFO  ] (BP-4) Test plan started!
[21:25:12]: ▸ {12932} 20170613.212512 [  INFO  ] 4 Simulators still running. [1, 2, 3, 4]
[21:25:12]: ▸ {12932} 20170613.212512 [  INFO  ] Using 685 of 1064 processes.
[21:25:42]: ▸ {12932} 20170613.212542 [  INFO  ] 4 Simulators still running. [1, 2, 3, 4]
[21:25:42]: ▸ {12932} 20170613.212542 [  INFO  ] Using 685 of 1064 processes.
[21:26:12]: ▸ {12932} 20170613.212612 [  INFO  ] 4 Simulators still running. [1, 2, 3, 4]
[21:26:12]: ▸ {12932} 20170613.212612 [  INFO  ] Using 684 of 1064 processes.
[21:26:42]: ▸ {12932} 20170613.212642 [  INFO  ] 4 Simulators still running. [1, 2, 3, 4]
[21:26:42]: ▸ {12932} 20170613.212642 [  INFO  ] Using 685 of 1064 processes.
[21:27:12]: ▸ {12932} 20170613.212712 [  INFO  ] 4 Simulators still running. [1, 2, 3, 4]
[21:27:12]: ▸ {12932} 20170613.212712 [  INFO  ] Using 685 of 1064 processes.
[21:27:42]: ▸ {12932} 20170613.212742 [  INFO  ] 4 Simulators still running. [1, 2, 3, 4]
[21:27:42]: ▸ {12932} 20170613.212742 [  INFO  ] Using 682 of 1064 processes.
[21:28:12]: ▸ {12932} 20170613.212812 [  INFO  ] 4 Simulators still running. [1, 2, 3, 4]
[21:28:12]: ▸ {12932} 20170613.212812 [  INFO  ] Using 683 of 1064 processes.
[21:28:42]: ▸ {12932} 20170613.212842 [  INFO  ] 4 Simulators still running. [1, 2, 3, 4]
[21:28:42]: ▸ {12932} 20170613.212842 [  INFO  ] Using 684 of 1064 processes.
[21:29:13]: ▸ {12932} 20170613.212913 [  INFO  ] 4 Simulators still running. [1, 2, 3, 4]
[21:29:13]: ▸ {12932} 20170613.212913 [  INFO  ] Using 685 of 1064 processes.
[21:29:43]: ▸ {12932} 20170613.212943 [  INFO  ] 4 Simulators still running. [1, 2, 3, 4]
[21:29:43]: ▸ {12932} 20170613.212943 [  INFO  ] Using 685 of 1064 processes.
[21:30:13]: ▸ {12932} 20170613.213013 [  INFO  ] 4 Simulators still running. [1, 2, 3, 4]
[21:30:13]: ▸ {12932} 20170613.213013 [  INFO  ] Using 684 of 1064 processes.
[21:30:43]: ▸ {12932} 20170613.213043 [  INFO  ] 4 Simulators still running. [1, 2, 3, 4]
[21:30:43]: ▸ {12932} 20170613.213043 [  INFO  ] Using 685 of 1064 processes.

@lyndsey-ferguson Please give the latest a shot, I fixed a bug I introduced while cleaning up that inverted UITargetAppPath and testHostPath

I fetched the branch and re-ran it. The simulators are started, it looks like the test-runner app is installed, but I do not see the actual app-to-be-tested installed.

@lyndsey-ferguson could you push a test case in BluepillRunnerTests which takes in a .xctestrun file to reproduce the error you saw? That would be much easier for us to debug.

I built the BPSampleApp and edited the Scheme so that the second test was skipped. When I ran bluepill with the bluepill_options (included), it had a number of problems (see attached log)
bluepill_logging_with_sampleapp.txt
bluepill_options.json.txt

I must have made a mistake somewhere. I am have sha acf566261954ae5d40f7e16585253a52ff9f30c9 and testing is working fine. It is running without any issues on my actual project. Here's the options.json file:
{
  "xctestrun-path":"../artifacts/test/build/uitests/Build/Products/XCUI Tests_iphonesimulator10.3-i386.xctestrun",
  "num-sims":4,
  "error-retries":5,
  "failure-tolerance":2,
  "only-retry-failed":true,
  "device":"iPhone 5s",
  "runtime":"iOS 10.1",
  "stuck-timeout":600,
  "test-timeout":600,
  "quiet":true,
  "output-dir":"/Users/lyndsey.ferguson/repo/ios/artifacts/tests",
  "reuse-simulator":true
}

@lyndsey-ferguson do you mean this PR works for you?

@oliverhu yes, it works for me

cool, I'll do a last check, squash the commits and merge.

squashed in #162

@lyndsey-ferguson are you sure this pr works for you.. the paths for test host and bundle seem wrong 🤔

nvm, it should work.


SCSS: Fixed exponential selector pattern

This resolves #1498.

Just to confirm, &.class-name would no longer select the & symbol as part of it?

No, it's still part of it.
& is included in [^@;{}()], so nothing changed apart from performance. I don't know why it was extra in the first place...


Disable FullResultWrite in DQ by default

We see that queries fail sometimes with this setting enabled with an error:
{
    "code": 500,
    "message": "Error resolving path //tmp/yql/aleksandr.gaev/910caf6a-9a0b2b92-dd29139a-b1f3f662/@dynamic",
    "attributes": {
        "host": "",
        "pid": 1,
        "tid":<PHONE_NUMBER>370468400,
        "thread": "Automaton",
        "fid":<PHONE_NUMBER>2781655000,
        "datetime": "2024-09-02T08:38:22.326511Z",
        "trace_id": "db6092f9-69f2f06e-9ce9cd4d-7333e9cc",
        "span_id":<PHONE_NUMBER>665213000,
        "method": "Get"
    },
    "inner_errors": [
        {
            "code": 500,
            "message": "Node //tmp/yql has no child with key \"aleksandr.gaev\"",
            "attributes": {
                "host": "",
                "pid": 1,
                "tid":<PHONE_NUMBER>370468400,
                "thread": "Automaton",
                "fid":<PHONE_NUMBER>2781655000,
                "datetime": "2024-09-02T08:38:22.326487Z",
                "trace_id": "db6092f9-69f2f06e-9ce9cd4d-7333e9cc",
                "span_id":<PHONE_NUMBER>665213000
            }
        }
    ]
}

Somehow DQ says that result should be in a table and never creates it.
Somehow it is flaky. Resending query multiple times fixes it, although logs for the query are the same except pulling the result part.

Shipped!


wordle.py: fix word scoring

Previously the word scoring did not match the scoring in the online wordle game. This change fixes the calc_score method.
In the online version, each character in the secret can only be used once to 'light up' a tile. If there are repeated letters in the guess, letters in the guess are matched first if they are in the same position.
More concretely, here are some examples of the previous / new behavior:

secret
guess
previous scoring method
new scoring method

ylems
neeld
12321
11321

abbey
abaca
33212
33111

banal
union
12112
12111

banal
alloy
22211
22111

banal
annal
22333
22333

There is a Reddit post with more details.

One of the examples in the comment is incorrect. The code works as expected, but calc_score("banal", "annal") returns "21333" not "22333".

oops, sorry, good catch


Unstable depth stream

Info

Camera Model
D435i

Operating System & Version
Linux (Ubuntu 16)

Issue Description
Hi, I use D435i to detect objects. I extract surface normals from depth data. But depth data constantly changes (like fluctuating) even when the camera is stationary. Therefore, normal test scores are always different in my algorithm. Is this normal or is there a way to fix it (get stable depth data)?

Normals are very sensitive to noise.
Did you try to first post-process by using edge preserving temporal and spatial filters, as per our white paper?

Thank you for your reply. Yes, I use temporal and spatial filters. I tried to increase laser power from the controls in the Realsense Viewer app. It got a bit better, but fluctuating continues. Is it possible to enhance depth data using rgb frame data or anything else?

Using the temporal and spatial filter as agrunnet described is the best way to reduce the noise. Using the high accuracy preset may also help in some cases.
Please let us know if you have any other question. Thank you.


Opening multiple books causes resource management problems.

Summary
Hey!
So I'm building an Expo application that uses epubjs-react-native.
If I open more than, say 4 different epub files from my device, I get "Opening..." until I reboot my device.
I'm pretty sure the issue is due to no method for destroying instances of old readers, and they accumulate up, using the devices resources.
Is there any way to get around this? Like any way to get a reference to the rendition and clean it up/destroy it?
What platform(s) does this occur on?
iOS
What workflow(s) does this occur on?
Expo Workflow
Environment (or package.json)
{
"name": "screens",
"version": "1.0.0",
"main": "expo/AppEntry.js",
"scripts": {
"start": "expo start",
"android": "expo start --android",
"ios": "expo start --ios",
"web": "expo start --web"
},
"dependencies": {
"@epubjs-react-native/core": "^1.4.5",
"@epubjs-react-native/expo-file-system": "^1.1.3",
"@epubjs-react-native/file-system": "^1.1.3",
"@expo-google-fonts/lora": "^0.2.3",
"@expo/vector-icons": "^14.0.2",
"@microsoft/fetch-event-source": "^2.0.1",
"@react-native-async-storage/async-storage": "^1.23.1",
"@react-native-community/hooks": "^3.0.0",
"@react-navigation/bottom-tabs": "^6.5.20",
"@react-navigation/native": "^6.1.17",
"@react-navigation/stack": "^6.3.29",
"@types/react": "~18.2.79",
"axios": "^1.7.2",
"eventsource": "^2.0.2",
"expo": "~51.0.14",
"expo-av": "~14.0.6",
"expo-document-picker": "~12.0.2",
"expo-file-system": "~17.0.1",
"expo-font": "~12.0.7",
"expo-image-manipulator": "^12.0.5",
"expo-linear-gradient": "^13.0.2",
"expo-sqlite": "~14.0.4",
"expo-status-bar": "~1.12.1",
"express": "^4.19.2",
"openai": "^4.52.0",
"openai-api": "^1.3.1",
"react": "18.2.0",
"react-native": "0.74.2",
"react-native-fs": "^2.20.0",
"react-native-gesture-handler": "^2.17.1",
"react-native-paper": "^5.12.3",
"react-native-safe-area-context": "^4.10.5",
"react-native-screens": "^3.32.0",
"react-native-svg": "^15.3.0",
"react-native-webview": "^13.10.3",
"react-navigation": "^5.0.0",
"typescript": "~5.3.3",
"ws": "^8.17.1"
},
"devDependencies": {
"@babel/core": "^7.20.0"
},
"private": true
}
Your .epub file
No response
Minimal reproducible example
No response
I confirm that i have

[X] I looked for a solution to my problem in other open and resolved issues
[X] I checked the examples provided solve my problem
[X] I have verified that my problem is not caused by a third-party library
[X] I cloned the project environment examples and still the problem persists
[X] I'm using the latest available version of the library and its complements

Never mind, it was caused by the javascript I was injecting running in the background even after the instance of the book was closed.


ModuleNotFoundError: No module named 'pytube3'

When I tried pytube3 instead of pytube, I get the following error:

Use from pytube import YouTube instead. The package is called pytube3 but the module is called pytube.

It's now working for me. I'm able to download videos now. Thanks for your help buddy.

No worries


scalaz-7.2.12

Codecov Report

Merging #1153 into release-0.15.x will decrease coverage by 0.04%.
The diff coverage is n/a.

@@                Coverage Diff                 @@
##           release-0.15.x    #1153      +/-   ##
==================================================
- Coverage           69.03%   68.99%   -0.05%
==================================================
  Files                 211      211
  Lines                4428     4428
  Branches              444      444
==================================================
- Hits                 3057     3055       -2
- Misses               1371     1373       +2

Impacted Files
Coverage Δ

...server/middleware/authentication/NonceKeeper.scala
92.59% <0%> (-7.41%)
:arrow_down:

core/src/main/scala/org/http4s/Uri.scala
85.45% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Missing dependencies

Local install:
Command: pip install -r requirements.txt
Output:
  Attempting uninstall: charset-normalizer
    Found existing installation: charset-normalizer 2.0.4
    Uninstalling charset-normalizer-2.0.4:
      Successfully uninstalled charset-normalizer-2.0.4
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
triton 2.0.0 requires cmake, which is not installed.
triton 2.0.0 requires lit, which is not installed.
...

Hmm, I don't believe triton 2.0.0 is a requirement for the model to run so I'm not sure where pip is trying to install that from, maybe for some CUDA thing.
A quick conda list for the environment that should be created has the following for packages starting with t:
tk                        8.6.12               he1e0b03_0    conda-forge
torch-geometric           2.3.1                    pypi_0    pypi
torchaudio                2.0.2                 py311_cpu    pytorch
torchvision               0.15.2                py311_cpu    pytorch
tqdm                      4.66.1                   pypi_0    pypi
traitlets                 5.9.0                    pypi_0    pypi

And a similar output when running pip list
threadpoolctl      3.2.0
tomlkit            0.12.1
torch              2.0.1
torch-geometric    2.3.1
torchaudio         2.0.2
torchvision        0.15.2
tqdm               4.66.1
traitlets          5.9.0
typing_extensions  4.7.1
tzdata             2023.3

I will add cmake and lit, and hopefully that will work.

I am closing this issue. Planning and testing will restart from scratch for the next release.


Materialize Classified "Abandoned"

With outstanding pull requests with mostly no feedback from project members it's safe to say this project is now abandoned.

Certainly looks like it.

It is not. See the current branches.

@DanielRuf Indeed. There's activity around but no releases for almost 1 year now and the PRs and issues are just piling up. axios is in a similar situation. Tough world this open source thing.
Since other people have asked about this in #6319 and @Dogfalo is saying the main contributors are taking a break, maybe we should put a big fat message in the readme saying "We're on a break, stop asking if the project is abandoned!" :smile:

Also if people need a release they can support the project and often also fund it. There is https://materializecss.com/support-us.html

@Dogfalo

Are these releases only available for your backers on Patreon offering you $2,160 per month?

@Pierstoval you have to substract the costs / fees from this number.
As you can see there is some progress on the current branches.
I think at the moment others things are more important than this.

Yep, indeed about the fees.
However, about this:

As you can see there is some progress on the current branches.

I'm sorry but I must disagree: the commit activity graph tells me otherwise. Latest commit is  38e1fc58 (Date: 2020-02-24 17:51:24 -0800) and this doesn't really seem like "recent activity", especially when considering the fact that most of the latest commits in other branches (notably gh-pages) are unrelated to any bugfix/fixtures, and the latest commit related to a PR is cb1f7b7a (#6471) which was like six months ago.
I really don't want to seem displeasant, and if I do, I sincerely apologize.
I mostly speak for the voice of the many people that await a new release, not only for features but mostly for fixes, since PRs are not merged. And since the package is not declared abandoned, people are quite not confident in making a fork and maintain it.
There's the solution for "seeking contributors" announcements in order to give some people the right to merge PRs and create releases, like Impress.js did a couple of years back when Bartaz declared not to want to maintain the lib anymore, or change the ownership. Or declare it abandoned.
I totally understand there are more important things than the state of Materialize, I know what it is to be a maintainer. It's just that the future about the project is quite unclear, and some clarifications could be really helpful for the community, and maybe lead the path for a fork that wouldn't move too far from Materialize's spirit in the first place :)
As said, I don't want to rush, I'm asking questions, I hope the team is doing well :)

There's the solution for "seeking contributors" announcements in order to give some people the right to merge PRs and create releases, like Impress.js did a couple of years back when Bartaz declared not to want to maintain the lib anymore, or change the ownership. Or declare it abandoned.

Well, @tomscholz and me had some rights a while ago but since this is hosted under the private account of one of the maintainers there will not happen much in the near future I guess.
@acburst @Dogfalo please let's move this to an org, invite all past contributors and give them rights to do reviews and some should also be able to merge PRs (I could help with that like I did in the past).
https://github.com/materialize

If there will be no change in the next two weeks I will go ahead, create a new org and do all the required steps to bring materialize forward.

🎉

If there will be no change in the next two weeks I will go ahead, create a new org and do all the required steps to bring materialize forward.

There you go: https://github.com/materializecss/materialize
Who wants to join?

Thank you @DanielRuf for helping bring the project forward.
Lets try a different approach here, if we can get 5 people to post here who are interested in helping out with the project and we have that we can create a team in the official org instead of trying to divide the existing community.

Lets try a different approach here, if we can get 5 people to post here who are interested in helping out with the project and we have that we can create a team in the official org instead of trying to divide the existing community.

At least me.

I think @Pierstoval and @doughballs too.

Yup 👍

Hey 😀

Yeah 👍

@tomscholz what about you? Would you like to help again?

@Dogfalo is 5 a deal breaker? Or could we proceed with 4?

I'm a new to this project (using it for a project at work) but would be happy to help where I can.

Yea it does not have to be 5, although it is definitely preferred that it is someone who has contributed before

I understand. I think it would be wise to get things moving and not let the opportunity pass - start to build confidence, stop any more users dropping off - even small changes/announcements at this stage would send out a good signal. I haven't contributed previously but I'm very willing and I'm already helping the community in whatever ways that I can.
It would be great to know if there is a plan (and if not, let's make one!)

Yea it does not have to be 5, although it is definitely preferred that it is someone who has contributed before

Aha, the old "A" team have clearly proven themselves.
checks out

First: let's fix the XSS issues in autocomplete (and some others), I guess 😉

@Pierstoval still, this would be breaking changes. Nothing that we should do in a patch release.
My statement still stands. If you accept user input you should ensure to sanitize it. Because if we fix this we have to introduce a new attribute which allows unsanitized input / does not apply the changes (like dangerouslySetInnerHTNL of react).

This is why we need a plan of action - is @Dogfalo going to lead? Like any other project, it will work better if someone leads and we have a clear vision.

I think a good starting point is the documentation. The main thing cropping up on Gitter and Stack Overflow is the undefined options variable in every vanilla JS init. If people copy and paste, the code doesn’t work - this is not good. The examples need fleshing out too.

@doughballs I didn't encounter this for a while now, do you think you can create/copy an issue for this onto the new repo? 😉

@doughballs I didn't encounter this for a while now, do you think you can create/copy an issue for this onto the new repo? 😉

Yes, done.
https://github.com/materializecss/materialize/issues/1
This is elementary stuff. I consider documentation errors unacceptable - it crops up every few days in Gitter and even SO.
Next up the most common issue is the select (selecting wrong option on mobile). Now I don't understand this issue, but I know how to fix it with the patched select.js file. We shouldn't be asking users to serve patches like this.
After this, dropdown. (The only fix I know is to remove the animation)

We have a short-term roadmap now 😉

@Dogfalo - can we PM to discuss this? Quicker than messaging back and forth.

@Dogfalo @acburst please let us know when you plan to take the next steps.
Otherwise I guess we have to take the next steps ourself. Would be great to do the next steps together.

@occirol might be also interested to help.

i just be happy to be able to use a up to date framework that isnt so confusing or complex. im sick of using bootstrap and others are just to confusing for my little brain, im more of a backend coder so a frontend noob friendly framework is badly needed.

@DanielRuf @Dogfalo
any updates? wanted to get this CSS framework rolling again.
I have some polyfills for some of the js function to push up if needed.
Thanks

@OliverwengFiltered you are very welcome to contribute to https://github.com/materializecss/materialize when you find some time.

I think Materialize's team is not continue this project. So @DanielRuf, @Pierstoval, @doughballs, @OliverwengFiltered and me can create new project based on Materialize v1.
Roadmap:

New name
New logo
New domain & website
Rebuild project structure
Remove jQuery
Update depencies (waves, normalize, animejs etc.)
Solve issues

We can create new version in a short time!
If you agree with me, let's start!
(send me your skype address for skype group<EMAIL_ADDRESS>

* New name

not needed

* New logo

not needed

* New domain & website

work in progress

* Rebuild project structure

not sure what you mean

* Remove jQuery

already happened in materialize 1.0.0 ;-)

* Update depencies (waves, normalize, animejs etc.)

on our roadmap

* Solve issues

on our roadmap
Please see https://github.com/materializecss/materialize =) PRs and issues are very welcome. You can already contribute.

New name

not needed, this is a fork which will continue the work

New logo

not needed, this is a fork which will continue the work

New domain & website

work in progress

Rebuild project structure

not sure what you mean

Remove jQuery

already happened in materialize 1.0.0 ;-)

Update depencies (waves, normalize, animejs etc.)

on our roadmap

Solve issues

on our roadmap
Please see https://github.com/materializecss/materialize =) PRs and issues are very welcome. You can already contribute.

Hey @DanielRuf,

New name
Like semantic-ui -> fomantic-ui

New logo
Like semantic-ui -> fomantic-ui

Rebuild project structure
Create a new project structure. For example; development of Bower does not continue.

Remove jQuery
Materialize v1.0.0 is still support jQuery ;)

Please see https://github.com/materializecss/materialize =https://github.com/materializecss/materialize) PRs and issues are very welcome. You can already contribute.
It's your project and does not appeal to us! Only contributer you in there.

Hey @ecoztas,

It's your project and does not appeal to us! Only contributer you in there.

There is 5 members in the org as for now. We are still in the organization process, yet. So @DanielRuf may be the only contributor as for now but as stated, you are very welcome to already contribute.

New name
New logo

No, no need, we keep the name, it will be probably the org name + materialize - we want to make the switch as easy as possible. We do not want to reinvent the wheel and allow people to easily switch back if needed.
The goal is to fix the open bugs and keep everything else (name, logo and so on) as far as possible.

Create a new project structure. For example; development of Bower does not continue.
Not the goal of the fork. We will probably remove the bower.json file in the far future. Nothing that has to be done now.

Materialize v1.0.0 is still support jQuery ;)

Not a short-term goal of the fork.

It's your project and does not appeal to us! Only contributer you in there.

Not sure what you mean. Everyone is possible to create issues at https://github.com/materializecss/materialize/issues and open PRs at https://github.com/materializecss/materialize/pulls, this is a normal fork =)
Contributor is everyone, collaborators are these with more rights (members of the org - see the small label on each comment, I'm the owner of the org with all needed rights). You can fork the fork, change things and open PRs, like with every normal repo - this is the normal contribution process.

New name
New logo

No, no need, we keep the name, it will be probably the org name + materialize - we want to make the switch as easy as possible. We do not want to reinvent the wheel and allow people to easily switch back if needed.
The goal is to fix the open bugs and keep everything else (name, logo and so on) as far as possible.

Create a new project structure. For example; development of Bower does not continue.
Not the goal of the fork. We will probably remove the bower.json file in the far future. Nothing that has to be done now.

Materialize v1.0.0 is still support jQuery ;)

Not a short-term goal of the fork.

It's your project and does not appeal to us! Only contributor you in there.

Not sure what you mean. Everyone is possible to create issues at https://github.com/materializecss/materialize/issues and open PRs at https://github.com/materializecss/materialize/pulls, this is a normal fork =)
Contributor is everyone, collaborators are these with more rights (members of the org - see the small label on each comment, I'm the owner of the org with all needed rights). You can fork the fork, change things and open PRs, like with every normal repo - this is the normal contribution process.

Also I'm not the only active contributor. I have merged some of the open PRs like you can see in the commits at https://github.com/materializecss/materialize/commits/v1-dev and in the compare view at https://github.com/Dogfalo/materialize/compare/v1-dev...materializecss:v1-dev
Like already mentioned: goal is to get the open PRs merged / closed as far as possible. And also the open issues. This is the short-term goal to release a maintained version with fixes for known issues.

As I'm mentioned as a contributor, please know that I'm mostly here for code reviews, as I don't (yet?) have the time to work on it quickly. I might have some time in the upcoming year, but I have a lot of other projects to work on, so I'm in the new org for discussion, architecture and review, and I'd be really glad to help any willing contributor to go further :)

No worries. Even reviews are contributions and every contribution is very welcome.

As for me, I can probably spend a bit of time most days, but I haven't contributed before, so not sure how useful I can be, beyond suggesting improvements and solutions to current issues. Happy to learn the ropes but would need some guidance.

@tomscholz what about you? Would you like to help again?

Hi :)
I know it's a little bit late to the party, but not responding at all seemed rude.
I'm no longer doing that much frontend work and haven't used materialize in over 2 years, so my answer is unfortunately no :(
I wish you all the very best and hope the development on the project comes back to life. The move to fork the project was definitely the right choice.
-Tom

@tomscholz no problem. And thanks for your feedback.

MaterializeCSS is a great project, and it's made the frontend development world a better place. But it's been YEARS since @Dogfalo et al. intended to continue development, and they've been actively soliciting donations this whole time with a duplicitous assertion that they'll use it for development. "Any amount would help support and continue development on this project"
It calls Alvin Wang and Alan Chang's integrity into question. Stop begging for money, or at least be honest about what you intend to do with it.

Cut the losses, switch to MDC from Google.

@assistcontrol @MaximBalaganskiy see https://github.com/materializecss/materialize which is a fork which will bring a new release in the near future.

It's true that we haven't released in a while, but we are not abandoning the project. We will figure out a dev/release schedule that works well for us to continue delivering updates

Could you also make a note on your paid themes that you're no longer providing support/answering emails for the paid themes? Seems rather poor taste to claim that there is support when there isn't.

Abandoned project. Sadly no support.

@subhasishdas159 This repo indeed seems abandonned, that's why the community has made a fork with a new org in order to maintain it: https://github.com/materializecss/materialize


Python 3.5.2 - doesn't work

Hi, great initiative!
But it seems not working on fresh python:
#pip3 list |grep bitrix24
bitrix24-python-sdk (1.0.1)
#python3
Python 3.5.2 (default, Oct  1 2016, 13:12:23)
[GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.38)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from bitrix24 import Bitrix24
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: cannot import name 'Bitrix24'
>>>

also if you'll try
python 3.5.2 (default, Oct  1 2016, 13:12:23)
[GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.38)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from bitrix24 import bitrix24
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.5/site-packages/bitrix24/bitrix24.py", line 9, in <module>
    from multidimensional_urlencode import urlencode
  File "/usr/local/lib/python3.5/site-packages/multidimensional_urlencode/__init__.py", line 1, in <module>
    from urlencoder import urlencode  # noqa
ImportError: No module named 'urlencoder'

multidimensional_urlencode is not yet python3 compatible. Is it necessary to form url parameters string? Because I see that B24 can get parameters inside POST body:
POST /rest/user.get.json HTTP/1.1
Accept: application/json, */*
Accept-Encoding: gzip, deflate
Connection: keep-alive
Content-Length: 55
Content-Type: application/json
Host: ktc.bitrix24.ua
User-Agent: HTTPie/0.9.6

{
    "ID": "14",
    "auth": "myauth"
}

HTTP/1.1 200 OK
{
    "result": [
        {
            "ACTIVE": true,
            "EMAIL"<EMAIL_ADDRESS>            "ID": "14",
            "LAST_NAME": "Будкин",
            "NAME": "Валентин",
        }
    ],
    "total": 1
}

on python 3.6 does not work
>>> from bitrix24 import bitrix24 Traceback (most recent call last):   File "<stdin>", line 1, in <module>   File "d:\OneDrive\WORC\Python\bitrix24\.env\lib\site-packages\bitrix24\bitrix24.py", line 9, in <module>     from multidimensional_urlencode import urlencode   File "d:\OneDrive\WORC\Python\bitrix24\.env\lib\site-packages\multidimensional_urlencode\__init__.py", line 1, in <module>     from urlencoder import urlencode  # noqa ModuleNotFoundError: No module named 'urlencoder'

@Nikovit, looks like you don't follow project requirements.

@Nikovit, now multidimensional_urlencode works on python 3.6 too.


Add a check for 'replaced by' and 'consider' fields

Hi @balhoff
We need a check to make sure that the values in the 'replaced by' and 'consider' fields are of the format GO:nnnnnnn
Thanks, Pascale

Ah !

I dont have a string feeling about 'consider', although most curation interfaces will not be able to use that directly, perhaps a comment is better? We can change that later if we encounter other examples? What do you think?

I'll keep it restricted to GO, at least until we run into an issue. 'cell' was the only example I thought of, and we must have avoided replaced_by on purpose due to GO annotation use cases.

ERROR: Non-GO replacement for obsolete term: http://purl.obolibrary.org/obo/GO_0097458 refers to non-GO term: CL:0000540

neuron part / neuron

ERROR: Non-GO replacement for obsolete term: http://purl.obolibrary.org/obo/GO_0044464 refers to non-GO term: CL:0000000

cell part/ cell

ERROR: Non-GO replacement for obsolete term: http://purl.obolibrary.org/obo/GO_0097223 refers to non-GO term: CL:0000019

sperm part/ sperm
@cmungall Do we want these kinds of replacements? If we do, we must be missing a lot.


Fix/gofmt

This PR fixes go fmt and go imports for TAS and introduces a check for each in the github actions file.

/lgtm


Optionally quoted identifier for column and index name

CREATE TABLE `table1` (`column1` INTEGER, KEY `index1` (column1));
is a valid MySQL create statement that is currently refused by Scheman.

:+1: :+1: :+1:


Implement a custom event for modal dismiss

Sometimes it is necessary to execute custom logic on modal close (see #262). Currently we have associated this custom logic to the close button, but a modal can be closed also clicking on the X button on the top right corner or clicking outside the modal, so at the moment a static backdrop has been set to force the user to close the modal only by clicking on the button. Since this can be annoying it should be better to define a custom Svelte event to execute this custom logic for each closing method.

Note that another way of closing the modal is via the esc key (which is not prevented by the static backdrop).

Interesting! But the esc key is not working to close all things I'd be expecting. For example, I often press esc to close a log window on the job page and that isn't working. Not sure whether the log display is a different model, but would be great to have that match the same closing functionality (and for example also work with esc)

But the esc key is not working to close all things I'd be expecting.

Yes, I confirm.
This current issue concerns the specific case of the task-edit modal, where we are looking for the best way to perform an action upon closing the modal (typically a reset of some changes that were eventually discarded by closing the modal). Once we manage to fully clean up this specific example, we'll replicate all around the repo - aiming for as much homogeneity as possible.


Autonomous

#41

No need to rush and merge, i'm just living it here so we can compare throughout future changes.


WIP Wasm executor

This is awesome! :D
Could you add building the WASM example to CI, so that it doesn't bitrot?

@Dirbaio Also needs https://github.com/embassy-rs/critical-section/pull/2 right now, not sure if there is another workaround you can think of?


🚧Replace custom guards

Complete The Item Below

[X] I have updated the title without removing the 🚧 emoji.

Description
Replace the custom guards with built-in dotnet guards.  The custom guards to be replaced are the EnsureThat.ParamIsNotNull() and EnsureThat.StringParamIsNotNullOrEmpty() guards.

The custom guard EnsureThat.ParamIsNotNull() should be replaced by the dotnet guard ArgumentNullException.ThrowIfNull()
The custom guard EnsureThat.StringParamIsNotNullOrEmpty() should be replaced by the dotnet guard ArgumentException.ThrowIfNullOrEmpty()
The following files should be refactored:

Testing/VelaptorTests/Guards/EnsureThatTests.cs
Velaptor/Content/Sound.cs
Velaptor/Content/TextureLoader.cs
Velaptor/Content/AtlasLoader.cs
Velaptor/Content/AtlasData.cs
Velaptor/Content/Fonts/Font.cs
Velaptor/Content/SoundLoader.cs
Velaptor/Content/Texture.cs
Velaptor/NativeInterop/FreeType/FreeTypeErrorEventArgs.cs
Velaptor/NativeInterop/GLFW/GlfwErrorEventArgs.cs
Velaptor/NativeInterop/OpenGL/GLInvoker.cs
Velaptor/OpenGL/GpuBufferNameAttribute.cs
Velaptor/OpenGL/ShaderNameAttribute.cs
Velaptor/OpenGL/GLErrorEventArgs.cs

Note

The exception messages that are generated by the new dotnet guards are different than the custom guard.  This means the unit tests will all need to be updated as well.
There are many files to be refactored, but we are completing the work in chunks that are dispersed among additional issues.

Acceptance Criteria
### ToDo
- [ ] All instances in the files listed below with the custom guard `EnsureThat.ParamIsNotNull()` replaced by the dotnet guard `ArgumentNullException.ThrowIfNull()`
- [ ] All instances in the files listed below with the custom guard `EnsureThat.StringParamIsNotNullOrEmpty()` replaced by the dotnet guard `ArgumentException.ThrowIfNullOrEmpty()`

### The following files are refactored:
- [ ] `Testing/VelaptorTests/Guards/EnsureThatTests.cs`
- [ ] `Velaptor/Content/Sound.cs`
- [ ] `Velaptor/Content/TextureLoader.cs`
- [ ] `Velaptor/Content/AtlasLoader.cs`
- [ ] `Velaptor/Content/AtlasData.cs`
- [ ] `Velaptor/Content/Fonts/Font.cs`
- [ ] `Velaptor/Content/SoundLoader.cs`
- [ ] `Velaptor/Content/Texture.cs`
- [ ] `Velaptor/NativeInterop/FreeType/FreeTypeErrorEventArgs.cs`
- [ ] `Velaptor/NativeInterop/GLFW/GlfwErrorEventArgs.cs`
- [ ] `Velaptor/NativeInterop/OpenGL/GLInvoker.cs`
- [ ] `Velaptor/OpenGL/GpuBufferNameAttribute.cs`
- [ ] `Velaptor/OpenGL/ShaderNameAttribute.cs`
- [ ] `Velaptor/OpenGL/GLErrorEventArgs.cs`

ToDo Items

[X] Change type labels added to this issue.  Refer to the Change Type Labels section below.
[X] Priority label added to this issue.  Refer to the Priority Type Labels section below.
[ ] Issue linked to the correct milestone (if applicable).

Issue Dependencies
No response
Related Work
No response
Additional Information:
Change Type Labels

Change Type
Label

Bug Fixes
🐛bug

Breaking Changes
🧨breaking changes

New Feature
✨new feature

CICD Changes
♻cicd

Config Changes
⚙config

Performance Improvements
🏎performance

Code Doc Changes
🗒documentation/code

Product Doc Changes
📝documentation/product

Priority Type Labels

Priority Type
Label

Low Priority
low priority

Medium Priority
medium priority

High Priority
high priority

Code of Conduct

[X] I agree to follow this project's Code of Conduct.

I'll take this.


Buttons on right, looked misplace on pages with single fields

Issue:  We now have pages that only have a single field (think CIS Scan app.) and now the cancel, yaml, create buttons look out of place on the right.

@vincent99 - did you want to move these back to center or are you ok with them on the right?

Closing... no comments.


Reynolds ONLY SST and Ice Concentration with a land-sea mask from @rcullath

I used rt1_4_10_geosit_1 and added: proc_SST_FRACI_reynolds_quart.F90 for the purpose of making SST and sea ice concentration files using a land-sea mask from @rcullath.
cc: @lcandre2, @mssolomo, @elakkraoui<EMAIL_ADDRESS>@rtodling
@mssolomo, if you want to build this code make sure this PR is merged into develop. For that @sdrabenh would be able to help!
For testing, the input file would look like:
20060301
20060302
/gpfsm/dnb42/projects/p17/production/GEOS5odas-5.00/RC/OBS/REYN/2006/amsr-avhrr-v2.20060301.nc
/discover/nobackup/rcullath/Pub/lsmask_int.repair.nc
720
1440

Thanks for letting me know.
Richard Cullather
ESSIC, University of Maryland at College Park
c/o NASA/GSFC Code 610.1 (Bldg. 33 / Rm. G114)      Tel: +1<PHONE_NUMBER>
8800 Greenbelt Road                                 Fax: +1<PHONE_NUMBER>
Greenbelt, MD 20771                   e-mail<EMAIL_ADDRESS>
From: Matthew Thompson<EMAIL_ADDRESS>Sent: Thursday, March 17, 2022 2:54 PM
To: GEOS-ESM/GMAO_Shared<EMAIL_ADDRESS>Cc: Cullather, Richard I. (GSFC-610.1)[UNIVERSITY OF MARYLAND]<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: [EXTERNAL] Re: [GEOS-ESM/GMAO_Shared] Reynolds ONLY SST and Ice Concentration with a land-sea mask from @rcullath (PR #239)

@mathomp4 approved this pull request.

Approve for CMake

-
Reply to this email directly, view it on GitHub<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FGEOS-ESM%2FGMAO_Shared%2Fpull%2F239%23pullrequestreview-913552837&data=04%7C01%7Crichard.cullather%40nasa.gov%7C757ed7f9b71c47d1fe7408da08478241%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637831400469931355%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=oVs8WGZiraF21%2Fw7i7zLj2De%2BlkU%2FcPbxaDCo0tkrhY%3D&reserved=0>, or unsubscribe<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPJB4W5GQNFL4B2XY4O2VOTVAN5UJANCNFSM5NHJDZ6Q&data=04%7C01%7Crichard.cullather%40nasa.gov%7C757ed7f9b71c47d1fe7408da08478241%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637831400469931355%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=FMy2%2F8O%2BxmX%2FjogWJJWTdkeEwlVkDeqLrP2oQfITKqU%3D&reserved=0>.
Triage notifications on the go with GitHub Mobile for iOS<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7Crichard.cullather%40nasa.gov%7C757ed7f9b71c47d1fe7408da08478241%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637831400469931355%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=GTcqFa%2BF9sFDv2ENiJu7fKg9KqyxjsymCW1FEtKV7E0%3D&reserved=0> or Android<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04%7C01%7Crichard.cullather%40nasa.gov%7C757ed7f9b71c47d1fe7408da08478241%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637831400469931355%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2BlBm%2Bs4sS8GuQFeZEfN6pGUSogpiTm4OP4POJErLscs%3D&reserved=0>.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Thanks for letting me know.
Richard Cullather
ESSIC, University of Maryland at College Park
c/o NASA/GSFC Code 610.1 (Bldg. 33 / Rm. G114)      Tel: +1<PHONE_NUMBER>
8800 Greenbelt Road                                 Fax: +1<PHONE_NUMBER>
Greenbelt, MD 20771                   e-mail<EMAIL_ADDRESS>
From: Scott Rabenhorst<EMAIL_ADDRESS>Sent: Thursday, March 17, 2022 2:56 PM
To: GEOS-ESM/GMAO_Shared<EMAIL_ADDRESS>Cc: Cullather, Richard I. (GSFC-610.1)[UNIVERSITY OF MARYLAND]<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: [EXTERNAL] Re: [GEOS-ESM/GMAO_Shared] Reynolds ONLY SST and Ice Concentration with a land-sea mask from @rcullath (PR #239)

Merged #239<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FGEOS-ESM%2FGMAO_Shared%2Fpull%2F239&data=04%7C01%7Crichard.cullather%40nasa.gov%7C494508fa421c47616e3e08da0847bd7d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637831401463193692%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=c6FDYzKiSl24M286jpfGeXt2FQ%2Fr5lIxeB3ymqxdSMM%3D&reserved=0> into main.

-
Reply to this email directly, view it on GitHub<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FGEOS-ESM%2FGMAO_Shared%2Fpull%2F239%23event-6261383779&data=04%7C01%7Crichard.cullather%40nasa.gov%7C494508fa421c47616e3e08da0847bd7d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637831401463350398%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=HfnEi%2Fj0qepyw5%2BHs7%2Fbzyz%2BcQ6tF9s1ilGq0d%2BtcYI%3D&reserved=0>, or unsubscribe<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPJB4WZKHB2LKMZVLTH3YVTVAN52XANCNFSM5NHJDZ6Q&data=04%7C01%7Crichard.cullather%40nasa.gov%7C494508fa421c47616e3e08da0847bd7d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637831401463350398%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=PxNgKVFt1z7G9u3HgFFZIbWNzPgEmwT3cQ0ru2lJ3OE%3D&reserved=0>.
Triage notifications on the go with GitHub Mobile for iOS<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7Crichard.cullather%40nasa.gov%7C494508fa421c47616e3e08da0847bd7d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637831401463350398%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ThLn9MHT0VqAF0%2FUpikz8WFL66%2BSiuEgr9n0x4GLLEE%3D&reserved=0> or Android<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04%7C01%7Crichard.cullather%40nasa.gov%7C494508fa421c47616e3e08da0847bd7d%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637831401463350398%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=B7i9AbUMm%2Bo7SPe6bL%2BBapxhJKw6pu70L7FlfPQGwxA%3D&reserved=0>.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


 Now press the up arrow 4 times and get git status and press Enter to execute it. If you press the down arrow after that, you'll get git difftool (The next item following git status).
For some reason, this feature got broken after I've installed posh-git. Now, pressing the up arrow always starts from the most recent command in history. Even if you execute a command from the history, pressing the down arrow afterwards gives nothing. You still have to press the up arrow and start from the beginning.
Is there any way to fix this?

Hrm...I'm not able to reproduce this. You can't see my keystrokes, but my last two commands are from hitting Down then Enter in succession.

Sorry, it appears to be my fault. The fact is, the 32 bit version of the PowerShell was normal, but the 64 bit version had this problem. Also, 32 bit version's ExecutionPolicy was set to "Restricted" mode. So there was no posh-git in the 32 bit PowerShell, which made me think the problem was with the posh-git itself. Without trying uninstalling posh-git and checking whether the problem still existed, I've filed an issue here. After I'd seen your comment, I've uninstalled posh-git only to realize the problem was still there.
For the next two hours I frantically and hopelessly tried understanding what was wrong (randomly uninstalling modules, running PowerShell in admin mode, deleting random keys from regedit), I don't know why and how but on of those steps fixed it.

I don't know why and how but one of those steps fixed it.

An accurate summary of computering in 2016. Glad it's not our fault. :smiley:


Bluetooth: shell: Add advertising options one-time and directed privacy

Add advertising option for undirected one-time advertising, and
directed advertising using identity, and peer direct is RPA option.
Signed-off-by: Joakim Andersson<EMAIL_ADDRESS>

@jhedberg any objections to merging this?


Default route possible?

Is it possible to have a default route that, for example, would return a 404 for any request that does not match an existing route?
e.g. in Express
app.get(/.*/, (req, res) => {
  res.status(404).send();
  //res.json({ status: ":(" });
});

https://stackoverflow.com/questions/37988122/404-fallback-route-in-express

Actually, it's not a 404 that gets returned by default. Its a 204 No Content which is confusing.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/204

I'm sorry, I linked to the wrong line, this is the correct one:
https://github.com/tsndr/cloudflare-worker-router/blob/main/index.js#L359

Hi. You closed this issue but I don't see how the recent release addresses this and there seems to be no update to the README.
Did I miss something? Thx

Oh, I was thinking that you just wanted 404 to be returned as default, which is already the case, so I closed it.

Here you go :) #19

Released with v1.3.7


#29: Improve GUI for Fusion >= 16

Closes #29

move preview mode label to the left
clear button full width
layer display name label

Forgot to reset the master from upstream to fork, my bad.