build failed with latest master branch

[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ core ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /apps/opt/tools/hygieia/core/src/main/resources
[INFO] skip non existing resourceDirectory /apps/opt/tools/hygieia/core/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ core ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 81 source files to /apps/opt/tools/hygieia/core/target/classes
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /apps/opt/tools/hygieia/core/src/main/java/com/capitalone/dashboard/model/Component.java:[57,31] cannot find symbol
symbol:   method replace(com.capitalone.dashboard.model.CollectorType,java.util.List<com.capitalone.dashboard.model.CollectorItem>)
location: variable collectorItems of type java.util.Map<com.capitalone.dashboard.model.CollectorType,java.util.List<com.capitalone.dashboard.model.CollectorItem>>
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] com.capitalone.dashboard:Hygieia ................... SUCCESS [  0.883 s]
[INFO] com.capitalone.dashboard:core ...................... FAILURE [  7.283 s]
[INFO] com.capitalone.dashboard:api ....................... SKIPPED
[INFO] com.capitalone.dashboard:jenkins-build-collector ... SKIPPED
[INFO] com.capitalone.dashboard:sonar-codequality-collector SKIPPED
[INFO] com.capitalone.dashboard:subversion-collector ...... SKIPPED
[INFO] com.capitalone.dashboard:github-scm-collector ...... SKIPPED
[INFO] com.capitalone.dashboard:versionone-feature-collector SKIPPED
[INFO] com.capitalone.dashboard:udeploy-deployment-collector SKIPPED
[INFO] com.capitalone.dashboard:jira-feature-collector .... SKIPPED
[INFO] com.capitalone.dashboard:jenkins-cucumber-test-collector SKIPPED
[INFO] com.capitalone.dashboard:chat-ops-collector ........ SKIPPED
[INFO] com.capitalone.dashboard:UI ........................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11.554 s
[INFO] Finished at: 2015-12-17T18:53:39-05:00
[INFO] Final Memory: 35M/360M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.0:compile (default-compile) on project core: Compilation failure
[ERROR] /apps/opt/tools/hygieia/core/src/main/java/com/capitalone/dashboard/model/Component.java:[57,31] cannot find symbol
[ERROR] symbol:   method replace(com.capitalone.dashboard.model.CollectorType,java.util.List<com.capitalone.dashboard.model.CollectorItem>)
[ERROR] location: variable collectorItems of type java.util.Map<com.capitalone.dashboard.model.CollectorType,java.util.List<com.capitalone.dashboard.model.CollectorItem>>

Travis builds are passing - https://travis-ci.org/capitalone/Hygieia/builds
Few questions: What's your java version? Did you see any maven dependency download error? If possible can you paste the top of the console log?

java -version
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
mvn clean install package
[INFO] Scanning for projects...
[INFO] Inspecting build with total of 13 modules...
[INFO] Installing Nexus Staging features:
[INFO]   ... total of 1 executions of maven-deploy-plugin replaced with nexus-staging-maven-plugin
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] com.capitalone.dashboard:Hygieia
[INFO] com.capitalone.dashboard:core
[INFO] com.capitalone.dashboard:api
[INFO] com.capitalone.dashboard:jenkins-build-collector
[INFO] com.capitalone.dashboard:sonar-codequality-collector
[INFO] com.capitalone.dashboard:subversion-collector
[INFO] com.capitalone.dashboard:github-scm-collector
[INFO] com.capitalone.dashboard:versionone-feature-collector
[INFO] com.capitalone.dashboard:udeploy-deployment-collector
[INFO] com.capitalone.dashboard:jira-feature-collector
[INFO] com.capitalone.dashboard:jenkins-cucumber-test-collector
[INFO] com.capitalone.dashboard:chat-ops-collector
[INFO] com.capitalone.dashboard:UI
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building com.capitalone.dashboard:Hygieia 1.5.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ Hygieia ---
[INFO]
[INFO] >>> maven-pmd-plugin:3.5:check (default) > :pmd @ Hygieia >>>
[INFO]
[INFO] --- maven-pmd-plugin:3.5:pmd (pmd) @ Hygieia ---
[INFO]
[INFO] <<< maven-pmd-plugin:3.5:check (default) < :pmd @ Hygieia <<<
[INFO]
[INFO] --- maven-pmd-plugin:3.5:check (default) @ Hygieia ---
[INFO]
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ Hygieia ---
[INFO] Installing /apps/opt/tools/Hygieia-master-latest/pom.xml to /apps/opt/home/oracle/.m2/repository/com/capitalone/dashboard/Hygieia/1.5.0-SNAPSHOT/Hygieia-1.5.0-SNAPSHOT.pom
[INFO]
[INFO] >>> maven-pmd-plugin:3.5:check (default) > :pmd @ Hygieia >>>
[INFO]
[INFO] --- maven-pmd-plugin:3.5:pmd (pmd) @ Hygieia ---
[INFO]
[INFO] <<< maven-pmd-plugin:3.5:check (default) < :pmd @ Hygieia <<<
[INFO]
[INFO] --- maven-pmd-plugin:3.5:check (default) @ Hygieia ---
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building com.capitalone.dashboard:core 1.5.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ core ---
[INFO]
[INFO] >>> maven-pmd-plugin:3.5:check (default) > :pmd @ core >>>
[INFO]
[INFO] --- maven-pmd-plugin:3.5:pmd (pmd) @ core ---
[WARNING] Unable to locate Source XRef to link to - DISABLED
[INFO]
[INFO] <<< maven-pmd-plugin:3.5:check (default) < :pmd @ core <<<
[INFO]
[INFO] --- maven-pmd-plugin:3.5:check (default) @ core ---
[INFO]
[INFO]
[INFO] --- apt-maven-plugin:1.1.3:process (default) @ core ---
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ core ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /apps/opt/tools/Hygieia-master-latest/core/src/main/resources
[INFO] skip non existing resourceDirectory /apps/opt/tools/Hygieia-master-latest/core/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ core ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 81 source files to /apps/opt/tools/Hygieia-master-latest/core/target/classes
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /apps/opt/tools/Hygieia-master-latest/core/src/main/java/com/capitalone/dashboard/model/Component.java:[57,31] cannot find symbol
symbol:   method replace(com.capitalone.dashboard.model.CollectorType,java.util.List<com.capitalone.dashboard.model.CollectorItem>)
location: variable collectorItems of type java.util.Map<com.capitalone.dashboard.model.CollectorType,java.util.List<com.capitalone.dashboard.model.CollectorItem>>
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] com.capitalone.dashboard:Hygieia ................... SUCCESS [  0.930 s]
[INFO] com.capitalone.dashboard:core ...................... FAILURE [  6.874 s]
[INFO] com.capitalone.dashboard:api ....................... SKIPPED
[INFO] com.capitalone.dashboard:jenkins-build-collector ... SKIPPED
[INFO] com.capitalone.dashboard:sonar-codequality-collector SKIPPED
[INFO] com.capitalone.dashboard:subversion-collector ...... SKIPPED
[INFO] com.capitalone.dashboard:github-scm-collector ...... SKIPPED
[INFO] com.capitalone.dashboard:versionone-feature-collector SKIPPED
[INFO] com.capitalone.dashboard:udeploy-deployment-collector SKIPPED
[INFO] com.capitalone.dashboard:jira-feature-collector .... SKIPPED
[INFO] com.capitalone.dashboard:jenkins-cucumber-test-collector SKIPPED
[INFO] com.capitalone.dashboard:chat-ops-collector ........ SKIPPED
[INFO] com.capitalone.dashboard:UI ........................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10.294 s
[INFO] Finished at: 2015-12-17T19:14:11-05:00
[INFO] Final Memory: 35M/360M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.0:compile (default-compile) on project core: Compilation failure
[ERROR] /apps/opt/tools/Hygieia-master-latest/core/src/main/java/com/capitalone/dashboard/model/Component.java:[57,31] cannot find symbol
[ERROR] symbol:   method replace(com.capitalone.dashboard.model.CollectorType,java.util.List<com.capitalone.dashboard.model.CollectorItem>)
[ERROR] location: variable collectorItems of type java.util.Map<com.capitalone.dashboard.model.CollectorType,java.util.List<com.capitalone.dashboard.model.CollectorItem>>
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :core

Please make sure you have the latest fork or clone  of master...

Strange. I am thinking if you can delete your .m2/repository directory (keeping ay settings.xml) and do a mvn clean compile...

My bad... did I tell you we are using Java 7 or 8?
http://stackoverflow.com/questions/24290452/the-method-replacestring-arraylist-is-undefined-for-the-type-hashmap

Travis is building with Java 8.

You need 1.8 on ur sandbox
Regards,
Keyur
On Dec 17, 2015, at 6:44 PM, hongluovz <notifications<EMAIL_ADDRESS>wrote:
I do have the latest master:
git remote show origin

remote origin Fetch URL: https://github.com/capitalone/Hygieia Push URL: https://github.com/capitalone/Hygieia HEAD branch: master Remote branches: AppDynamics tracked cloud-changes tracked gradle tracked jdamick-gradle tracked local-test-fix tracked master tracked readme-fixes tracked sample-updates tracked Local branch configured for 'git pull': master merges with remote master Local ref configured for 'git push': master pushes to master (up to date) [oracle@scsblnx-295720 Hygieia-master-latest]$ git pull Already up-to-date.

—
Reply to this email directly or view it on GitHubhttps://github.com/capitalone/Hygieia/issues/235#issuecomment-165625954.

Its building successfully withJDK 8
But, still the stash collector seems - we need to build separately...
[INFO]
[INFO] com.capitalone.dashboard:Hygieia ................... SUCCESS [  1.536 s]
[INFO] com.capitalone.dashboard:core ...................... SUCCESS [ 19.872 s]
[INFO] com.capitalone.dashboard:api ....................... SUCCESS [ 15.619 s]
[INFO] com.capitalone.dashboard:jenkins-build-collector ... SUCCESS [  4.561 s]
[INFO] com.capitalone.dashboard:sonar-codequality-collector SUCCESS [  1.944 s]
[INFO] com.capitalone.dashboard:subversion-collector ...... SUCCESS [  1.956 s]
[INFO] com.capitalone.dashboard:github-scm-collector ...... SUCCESS [  2.425 s]
[INFO] com.capitalone.dashboard:versionone-feature-collector SUCCESS [  4.269 s]
[INFO] com.capitalone.dashboard:udeploy-deployment-collector SUCCESS [  3.003 s]
[INFO] com.capitalone.dashboard:jira-feature-collector .... SUCCESS [  4.333 s]
[INFO] com.capitalone.dashboard:jenkins-cucumber-test-collector SUCCESS [  2.953 s]
[INFO] com.capitalone.dashboard:chat-ops-collector ........ SUCCESS [  3.758 s]
[INFO] com.capitalone.dashboard:UI ........................ SUCCESS [05:16 min]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 06:24 min
[INFO] Finished at: 2015-12-17T22:01:50-06:00
[INFO] Final Memory: 148M/834M
[INFO] ------------------------------------------------------------------------
Keyurs-MacBook-Air:Hygieia FamilyMac$

switched to JDK 1.8 and it fixed the build issue. Thank you all.


Problem Report Being Sent Before Thread Established

In aries_cloudagent/protocols/issue_credential/v2_0/routes.py
in the methods which initiate a credential exchange, namely:
credential_exchange_send_proposal -- line 838
credential_exchange_send_free_offer -- line 1045
credential_exchange_send_free_request -- line 1255
There is a call to report_problem at the line numbers mentioned above. However, while there will be an existing thread on both sides of the connection for "bound" requests, allowing the problem report to be delivered successfully, for these requests above, which initiate a new credential exchange, the credential exchange records have not yet been established on the partner side. Therefore, the report_problem call results in the partner raising a StorageNotFound error when it attempts to locate the nonexistent credential exchange thread. For example:
aries_cloudagent.storage.error.StorageNotFoundError: V20CredExRecord record not found for {'thread_id': 'b7c261f7-7a36-4413-bdb9-7cd93af3f50c'}, {'connection_id': 'ba0d694c-738d-4850-97cb-785a2a597562'}
If there's no case where the partner thread would already exist for these methods which begin the credential exchange, then the attempt to deliver the problem report to a non-existent thread should be avoided. If that makes sense, simply deleting the report_problem calls in those three methods would resolve this issue.
One fairly simple way to test this is to try and create a credential exchange with an empty credential subject.

Thanks for the report.  I agree with your analysis and solution.  Great if you could raise a PR for this.

This was reported in #1730 as well.

@swcurran PR #2519 created. Thanks for pointing out the earlier report.

Fixed with Merge of PR #2519. Thanks!


Add link to best practices slides

Just that :)

@AndreaVolkamer Check if it's ok now! :)

Result here: http://projects.volkamerlab.org/teachopencadd/external_resources.html


Devices with OS 1.2 or greater do not detect the preloaded image

Since resinOS upgraded to docker 1.10 in resinOS 1.2, the docker daemon changed the on-disk format for images. This means that currently this scrip loads images onto the .img with the docker 1.4 ondisk format and the supervisor fails to detect it.

closed by #20


Add custom user model for dynos

The custom fields are:

lat
lon
device name
address
serial
email
description

Also the model should be called sensor

Added


Update to go1.17

Summary
Update to go1.17 in go.mod
Ticket Link
None

Codecov Report

Merging #302 (955b24b) into master (ec2fd25) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #302   +/-   ##
=======================================
  Coverage   25.96%   25.96%
=======================================
  Files          73       73
  Lines        4156     4156
=======================================
  Hits         1079     1079
  Misses       2970     2970
  Partials      107      107

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 ec2fd25...955b24b. Read the comment docs.


Notifications for when you are forwarded sats from a post

Closes #458
Support configurable notifications when a post for which you are forwarded gets zapped
This is controlled by a new boolean flag in user settings

tACK f6f62ac
Did reset my database and created two new accounts; one on desktop, one on mobile. Enabled push notifications for both of them. Created a new anon post and forwarded 33% to both users.
Zapped that post with anon (anon is great for local development, lol) and both received push notifications.
However, I can see a you were forwarded 0 sats notification. (I only received 29 sats because of the 10% fee so that's fine)

@ekzyis looking at that screenshot again... are those two notifications from the same post? I see the top one has 100 sats, and the bottom one has 0 sats, so I am wondering if somehow there's a duplicate post there? I haven't had a chance to try to recreate it locally yet, I'll follow up once I do.

Ah, nice catch, didn't see the difference. Already deleted my database. I only created one post with that title but not sure when that notification popped up

I just followed the above steps but was not able to recreate the issue. To double-check:

Create user 1, user 2, user 3, user 4
Post as user 1, forwarding to user 2 (33%) and user 3 (33%)
Zap post 100 sats as user 4
Check notifications for user 2, only 1 notification present (with 33 sats being forwarded, the correct amount)

Could it be due to anon? I need to get LND setup so I can do invoices (I think?) to post as anon locally, so I didn't try that yet.
I also wonder if maybe there was some weird stale notification that indicated 0 sats? Not sure, I'll keep experimenting...

I mostly got the LND setup going using the docs in the repo. I'm able to generate invoices successfully. However, how am I supposed to pay them? I setup a second LND node in Polar (aliased as bob), opened channels between it and the first LND node I created (aliased as alice) which acts as SN, but the invoice payment seems to just hang infinitely if I try to pay from bob to alice. When trying to pay from alice, it fails saying no self-payments allowed, which makes sense. I also added bob to the sn docker network, in case that is necessary. I realize this isn't directly related to this issue, but any idea what I might be missing?

but the invoice payment seems to just hang infinitely if I try to pay from bob to alice

the worker must be running to confirm the invoices :)

Fantastic, thank you! I didn't realize the worker wasn't running... I thought it would have started up given it's included in the docker-compose file...

Oh hey this looks familiar

It's coming from here, the 'FEE' option. Since it's including unzapped items, you then see the "forwarded 0 sats" note.
@huumn why did we originally include 'FEE' for zapped notifications? Any concern with me removing 'FEE' from this IN clause? Otherwise, I could add AND "ItemAct"."userId" <> "Item"."userId" to filter out self-actions, which should also eliminate fees, but we could just remove fees from the query altogether?

I went ahead and removed FEE from the query. @ekzyis if you get a chance to re-test this, lmk if this works. I think this is the fix we need.

tested 8aacd87 which includes #464
I no longer get a you were forwarded 0 sats:

so LGTM :)
Oh, @huumn already merged this, lol


how multiple matched rules are dealt with

Sorry for an naive question. I try to understand what happens two or more rules are matched? do they all fired to give rise to different runs?
For example, I have the following K program:
module TEST-SYNTAX

  syntax STM ::= "i" | "a" | "b"

endmodule

module TEST

  imports TEST-SYNTAX

  configuration
  <T>
    <k> $PGM:STM </k>
    <out> .K </out>
  </T>

  rule <k> i => b </k>
  rule <k> i => a </k>
  rule <k> b => .K </k> <out> _ => "b" </out>
  rule <k> a => .K </k> <out> _ => "a" </out>

endmodule

A program for this language contain only "i" (without quotes).
If I kruns this program with the option --search, there is only solution (also I wish to have two). Do I misunderstand K at some point? how to obtain both expected runs from this program?
Here is the output of krun (I use k 3.5.2)
krun test.t --search
Search results:

Solution 1:
<T>
    <k>
        .K
    </k>
    <out>
        "a"
    </out>
</T>

Thank you very much.

Sorry for an naive question. I try to understand what happens two or more rules are matched? do they all fired to give rise to different runs?

Yes. With regular execution you will only see one of the runs, while --search will give you all possible runs.
For your example, it does look like it should give two solutions. It might be a bug in K 3.5. Could you try it with K 4.0?

Have you tried to add the [transition] tag to your rules?
Syntax:
rule Left => Right [transition]

@andreiarusoaie, right :-)
We had been defaulting to [transition] in the Java backend for a while but, yes, it was needed before, and it is still needed in the latest version.

Guys, let me remind you that we do not encourage you to use the "transition" attribute.  Instead, you should use the --transition option to kompile, and include all the rules that you want to consider as transitions there.  If you want all the rules to be transitions, then add "computational" to the list of transitions (--transition "computational")..

Hello, thank you for your answers. Also a similar question about how multiple applicable rules are dealt with, but now, in the definition of a function? when two or more rules in the definition of a function are applicable at the same time, is there an implicit priority which determines which rule is applied? Can we specifies an explicit priority for these rules?

The rules are applied non-deterministically. While some earlier versions of K did follow some conventions for rule application order, it would be best to not rely on them.
The cleanest way to prioritize rules is to use rewriting strategies. We have experimental support for them in K 4.0. If using the latest version of K is not an option for you, there was some limited support for strategies before. @andreistefanescu, do you know more about it by any chance?


Update lulu to 0.9.4

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Aloha!
One point to note - that's new to 0.9.4
After LuLu Installer.app runs the config script, it now also invokes a method to add the login item (see:  https://github.com/objective-see/LuLu/blob/790cd977bc13d28846faa0ec41d9299a14e71767/configure/Configure/Configure.m#L343)
AFAIK, there wasn't a way to do this via script/shell commands - so this had to be done in the objective-c code. Before the script invoked the main binary to do this, but had to do this via the 'open' command to ensure it ran in the context of the logged in user (vs. as root)...this method spawned a separate process, dock icon, etc...so it was simpler just to move this logic into the LuLu Installer.app. However, this means that now executing configure.sh isn't enough to install LuLu fully.
Would it help if I created a cmdline option that could be passed to the LuLu Installer.app that just took care of everything? (i.e. ran the script, installed the login item, etc etc)?


add back the accidentally deleted IsVisibleChatConversationStatus function

r? @mlsteele

The commits 6ff45b59b936...c70ceccceb9a introduce visual changes on linux. :mag_right: 1 changed

Changed: Paper_Key-Normal (before) (after)


Error in from_str_radix if radix > 18; avoid unfortunate interaction

from_str_radix: Error if radix is > 18
Radix 19 and 20 introduce 'i' and 'j' as digits and this conflicts with
how complex are parsed. Before this fix, it could parse
Num::from_str_radix("1ij + 1ij", 20) in a pretty surprising way.
The Num docs already describe a rule for our situation - we might not
support every radix in our implementation; we can return an error in
this case instead.
A new (internal) error kind is introduced for this.
It is necessary to preserve the previous panicking behaviour(?) for
radix > 36 (this is what primitive types do - but other types are
allowed to do differently, including never panicking).

Where and if to panic and where to check for the error involves some nonobvious choices. I'd prefer if "radix <= 18" is a precondition to calling "from_str_generic", i.e that this function doesn't have to care for possible 'i' as a digit and so on.
I'd also be fine to just have radix <= 16 as the requirement if that just seems easier to understand.
Playground link - showcase weird parses
As an example of a weird parse, "1i" is 38 as a real number in the type i32 with radix 20. But "1i + 1i" parses as the complex 38 + i in type Complex<i32> radix 20.

radix: 20
input: 1i
i32                             	Ok(38)
num_complex::Complex       	Ok(Complex { re: 0, im: 1 })
radix: 20
input: 1j
i32                             	Ok(39)
num_complex::Complex       	Ok(Complex { re: 0, im: 1 })
radix: 20
input: 1i + 1i
i32                             	Err(ParseIntError { kind: InvalidDigit })
num_complex::Complex       	Ok(Complex { re: 38, im: 1 })
radix: 20
input: 1ij
i32                             	Ok(779)
num_complex::Complex       	Ok(Complex { re: 0, im: 38 })
radix: 20
input: 1ij + 1ij
i32                             	Err(ParseIntError { kind: InvalidDigit })
num_complex::Complex       	Ok(Complex { re: 779, im: 38 })
radix: 20
input: 1ji
i32                             	Ok(798)
num_complex::Complex       	Err(ParseComplexError { kind: ExprError })
radix: 20
input: 1ji + 1ji
i32                             	Err(ParseIntError { kind: InvalidDigit })
num_complex::Complex       	Err(ParseComplexError { kind: ExprError })

That's an unfortunate oversight, but I agree that an error is the most reasonable thing we can do.

So I'm curious, how did you come to realize this? If it was in real use, then someone really did want a larger radix?

Oh, for some reason I was reading the from_str implementation and looked at how it handles i vs j (it looks hacky, but seems to cover all the cases). So I just noticed it, and I don't know any use case for this.
I have a feeling that the "<= 18" limit is irregular and it would seem better to only support <= 16

bors r+


[10.x] Remove unnecessary return statement in defaults method

This commit removes an unnecessary return statement in the 'defaults' method of the code. Previously, the method had a return statement that returned the result of the 'pipeline' method. However, since the return type of the 'defaults' method is void, the return statement was redundant and did not serve any purpose. Therefore, it has been removed in this commit to simplify the code and improve its clarity.

This changes behavior on a public method. While I have doubts this will get merged, at a minimum you will need to target the next major release, v11.


X.509 boolean values recognized on Windows and Linux, but not on OS X

I've created a self-signed CA with the mbedtls_cert_write command. This certificate works on Windows 10 and Fedora 21, but not on OS X 10.11 (El Capitan).
The Basic Constraints extension critical flag is recognized on Windows, Linux, and with openssl command on Mac OS X 10.11, but not by OS X Keychain app:

Also, the CA flag is not recognized on OS X.
Maybe OS X is expecting a value of 0xff (255) for TRUE, not 1 ?

In mbedtls_asn1_write_bool, BOOLEAN is written out with a 1. In BER, any non-zero value is 'true', but in DER, only 0xff is permitted.

http://jira-dev0.cambridge.arm.com/browse/IOTSSL-465

ARM Internal Ref: IOTSSL-508

@rainierwolfcastle FYI this bug is fixed by PR #320.


feat: add macos-14 builder for native m1 arm builds

See https://github.blog/changelog/2024-01-30-github-actions-introducing-the-new-m1-macos-runner-available-to-open-source/ for more details on how macos-14 references arm, and https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners for details on why macos-latest is still intel.

thanks!


Investigate deploying ClamAV for virus checking

We can use ClamAV to check all uploaded files for viruses. How should we do that?
TODO

investigate different solutions for deploying ClamAV:

AWS
local microservice via Docker

Related Tickets

#123 for related issues when deploying services as lambdas.

I came up with a few POCs for how we could do this, and follow a similar pattern for things like FITs, derivatives (if that becomes a thing again) etc.
given the limitations on lambda / fargate, i believe a microservice running in Docker is the best solution. We can fire put notifications to a queue, and have that microservice process the file, and then post the results back to scholarsphere. in my POC i'm simply posting the results to a slack endpoint, but the idea would be we could make that bit plug-able.
Questions:
we probably need to configure a prefix for the 'storage' store in shrine, so we can only send notices from that prefix to the queues. we also might want to use a different bucket for cache, or have that bit be more flexible, so we might want to, as part of a refactoring session, look at that shrine configuration class ( related #156 )
we might need a way to quarantine files in scholarsphere, this might be a post-release activity (we might not want to over-engineer something. a notice to service now might suffice? (based off a conversation in the standups a notice should suffice for now.)
I drew this up in miro to try an describe it. the sns / sqs bits can all be automated and injected into the application
https://miro.com/app/board/iXjVOf7OiEI=/


Solves unhandled rejections with Angular >= 1.5.9

Angular >=1.5.9 throws an Unhandled rejection when the promise doesn't have a catch function. I added just the catch function with a comment to solve this error.

good idea, thank you


add meta transactions store

[x] I have added a store for meta transactions

Issue Number
ADP-1784

bors try

bors retry

bors r+


please use proper versioning

currently, each and every APK at your releases seems to identify as
package: name='com.nostros' versionCode='1' versionName='1.0'

so not only can a user never know what version is installed, but Android cannot tell if an APK you want to install is newer or not either (Android uses versionCode to tell them apart). So for the currently latest release, it should be versionName: "<IP_ADDRESS>-alpha" and versionCode: 26 (as it's the 26th release; important with this one is just that you increase it with each version – how much you increase it is up to you, but you can never decrease it anymore without forcing all users to uninstall and reinstall).
Thanks in advance for taking care!

This is a good point and I agree.
However, that's probably left there unchecked on purpose since the app is not in stores right now.
What could be nice is to have the version of the app printed on some screen (eg: the bottom of Config screen).

Believe it or not today I was thinking about it but I had to investigate how to properly do it, thanks for the hints @IzzySoft I'll change it for the next release

https://github.com/KoalaSat/nostros/pull/110

What a coincidence :rofl: Thanks, yes: exactly that was what I meant. So with that PR merged, the next APK built would show up as I described.
As for "not in the stores": Uhuh, that was part of the background to my question. I'm running the largest 3rd-party F-Droid repo with currently more than 1k apps (see here) and was considering to integrate your app there. With proper versioning (and especially versionCode always increased on release), I could finally do that. So if you're OK with this: I could pick some screenshots from your release messages – or you could provide a selection of your choice, plus some app description maybe? Ideally that could be set up using Fastlane structures here in this repo; if I have description, screenshots & Co I could bundle a "starter package" for you.

What a coincidence 🤣 Thanks, yes: exactly that was what I meant. So with that PR merged, the next APK built would show up as I described.
As for "not in the stores": Uhuh, that was part of the background to my question. I'm running the largest 3rd-party F-Droid repo with currently more than 1k apps (see here) and was considering to integrate your app there. With proper versioning (and especially versionCode always increased on release), I could finally do that. So if you're OK with this: I could pick some screenshots from your release messages – or you could provide a selection of your choice, plus some app description maybe? Ideally that could be set up using Fastlane structures here in this repo; if I have description, screenshots & Co I could bundle a "starter package" for you.

If you can do it for me it would be super awesome, you can take the screenshot but just be aware the next feature is drastically changing the UI, but I assume we can change those images at any point on the repo.
@frontends crypto is helping with the branding so maybe he can help with the description 🙂

Excellent :)
@KoalaSat I think the version and build bump should be included as part of the GitHub actions flow you have for building. That way it's automatic without you worrying about it. The build (versionCode) bump could be pretty automatic, but the versionName might require manual input in case you increase a minor version 0.x.0 or a patch 0.0.x for example.

Yes I'm pretty sure there has to be some boilerplated GitHub action for that, I'll do the research, but probably of the action makes an extra commit obtaining the info from the triggered release can be fully automated, thanks for all the help!
Let us know if you need something else for the repo ⚡⚡

you can take the screenshot

Sorry to disappoint, but I'm not using Nostr so I'm not the best choice for this task. For starters, if you could provide the following, more can be added later:

short description (max 80 chars)
full description (a few lines describing the app and giving a clue of Nostr's concept so even those not familiar with it can get an idea). No need for a "fully polished" one, can always be improved later.
an icon (128x128 to 512x512 px) and some screenshots (again, 3..5 suffice for starters, can be replaced and amended later)

It's totally fine to provide that just in a comment here, I'd then prepare the Fastlane structures and offer them back here for integration if you prefer. Or you give it a try yourself and have me cross-check :wink:
Once the listing is up, it can always be improved and built upon – see my Fastlane Cheat Sheet which I already linked above. Seeing the app size getting close to the limits of my repo already (30M per app; Nostros is already at 26M), per-ABI builds might be a good idea; I'd then pick the armeabi (most wide-spread support on older devices, and most 64bit devices support it as well) or if you prefer the arm64 APK for my repo. Once the app leaves "alpha stage" and is considered ready for a broader audience, I could guide you to get it listed at F-Droid.org (with all 4 ABIs then; disclosure: I'm one of the maintainers there).

Hi! What do you think about something like this? I think this would be enough for now, we can always expand it later. @KoalaSat
Short description
The first Nostr client on Android. The only and truly uncensored social network.
Full description
Nostros is the first Nostr client for Android. Access a social network similar in appearance to Twitter, but decentralized and uncensored.
Nostros offers an extensive list of features that grows every day. Access the global feed or the feed of the people you follow. View all the content that you have liked, been mentioned or disliked.
You can also send tips to users through Lightning Network as well as associate your Nostr identity to your Twitter profile or domain.
Follow other users, or unfollow them. Indicate if you like their content, or if you don't like it. Comment on other people's posts or quote them.
Don't wait any longer and join the most social network thanks to Nostros.
Screenshots

Icons

Awesome! Thank you! Please @IzzySoft let us know if you need anything else

Awesome indeed! I'd just need the info if you would provide per-ABI builds. If not I can of course pick the "fat lady" – but then I could only hold the latest version available in my repo. A single ABI would most likely be below 15 M, so I could keep 2 versions (useful to prevent installation errors when a user e.g. just pulled the index right before a new version was added, and thus would try installing the version that was just purged – with 2 versions kept, it would still be there and the user would just get an update notification the next day).
Of course we could also move to per-ABI builds later – but depending on their setup, the switch might be a problem as usually each ABI has its specific versionCode (example: Flutter per default generates a code of <ABI> x 1000 + versionCode – so once my updater fetched the one with the highest ABI (4000 + versionCode) and it was the wrong one, switching to the other would mean users had to uninstall and re-install as you never can "downgrade" to a lower versionCode). This could of course be worked around by marking the first release with per-ABI builds prerelease (so my updater ignores it) and letting me know, so I can configure it accordingly on my end – and as soon as that's done the "pre-flag" can be removed again. We'd need some "constant patterns" in file names then so I can ensure the correct APK is fetched (usually *armeabi-v7a*.apk for ARMv7, *arm64*.apk for ARM64, and so on).
Just let me know your decision, and we're ready to go (as soon as the APK decided for is available).

@IzzySoft sorry for answering late but right now we are totally focused on migrating the UI, what do you recommend? Don't now and eventually change and use the pre-ABI or it's fine to just for with one big version for now?

As described it's preferable if I can hold more than one APK in my repo, so the per-ABI builds would be the way to go. And no pressure from my end: if your focus is now on migrating the UI, you probably won't release before that reached a "stable point". For the best "first impression", maybe wait for that – and take a look at per-ABI builds when the release comes close? Better have it lean and clean than haste and waste, do you agree? :smile:
An ETA would be nice to have – but if hard to give, I'll just wait and maybe chime in every now and then to see how things stand. I'll certainly do so when seeing a new release – but won't nag you twice a week :wink:
If you prefer going with the "fat lady" now and switch to per-ABI later, that can be done as well – see above for possible implications which are, hopefully, easily solved when planned in advance. I'd follow your preference then.

Hi @IzzySoft again, we are done with the UI and entering the testing stage to be prepared for the Beta version.
I have been investigating  a little bit all the info you provided (thank you!) and certainly we can try to go with the per-ABI build. 😄
My only doubt so far is how and from where you'll obtain the generated APK?

Perfect that was my thought, I'll work on the GitHub action to generate both

I make it work locally so I configured the github action, I'm planning to create a new release today/tomorrow so then we can test it out 💪
https://github.com/KoalaSat/nostros/pull/160

That looks great! So whether you decide for armeabi or arm64, at that size I can keep 2 copies in my repo (so on update even those not yet having the latest index won't get an error-on-install as the previous APK is still available). With the "fat lady" aka "universal" I could only keep one.
So once they're up, just let me know which one you'd prefer me to pick. Thanks a lot!

I think you mentioned you preffer to have arm64 on your repo right? feel free to decide which one 😃 I'm still generating the universal for people that directly goes to github to download it.

Also @FrontendCrypto I think with new UI those screenshots are obsolete

I think you mentioned you preffer to have arm64 on your repo right?

I used to take the armeabi APK for wider compatibility (and also for sustainability, supporting those using their hardware as long as it works while not neglecting that arm64 devices are around now for about 5 years, and being the majority of new devices). But I of course respect the wishes of the authors: so if you say you prefer me to pick arm64, I'm fine with that meanwhile (wasn't a year or 2 ago when 32bit devices were still more prominent than today).

I'm still generating the universal for people who directly goes to github to download it.

By all means: yes, please do! If you'd have the universal and all the per-ABI builds here, everyone would have the full choice. That said, while I can check for myself once the APKs are up: what pattern are you using for versionName? Will they all share the same? If not, where will they differ: last digit or first (e.g. Flutter by default and for extra crazyness has them differ in the first digit; so if you start with a 2001 armeabi you'd have no chance switching to arm64 having a 1002 with the next release, which to me is absolute nuts).

with new UI those screenshots are obsolete

Good point! I see you include some with your releases as well, so for starters I could pick some from there. Once set up, I can provide you the metadata in Fastlane format to integrate with your repo here. Then you can update description, screenshots and all to your liking and changes will be pulled along with each new release.

This is the pattern https://github.com/KoalaSat/nostros/blob/main/.github/workflows/android-build.yml#L56

Good point! I see you include some with your releases as well, so for starters I could pick some from there. Once set up, I can provide you the metadata in Fastlane format to integrate with your repo here. Then you can update description, screenshots and all to your liking and changes will be pulled along with each new release.

Perfect let's do it like you say

Ugh, guess I've chosen the wrong phrasing. I meant the "pattern" for versionCode. Would be good if e.g. armeabi had a smaller VC than arm64, so folks switching from an old 32bit device to a newer 64bit while transferring their apps and data would still be able to update from armeabi to arm64 then.
And great, I'll provide the metadata then (should I forget, be welcome to remind me). Looking forward to the next release then!

@IzzySoft here you go https://github.com/KoalaSat/nostros/releases/tag/v<IP_ADDRESS>-alpha, I hope everything is correct, please let me know if we need to change something

Thanks @KoalaSat! I've modified the description slightly (there are already 2 Nostr clients in my repo, so "the first" sounds a bit … strange :see_no_evil:). Will show up here with the next sync today around 7 pm UTC. If you like what you see there: be welcome to pick a badge to link there e.g. from your Readme :smiley:
As promised, here's the fastlane.zip with the metadata. Unzipped content should go directly to the document root (i.e. /fastlane). Feel free to replace the screenshots again (my framework compresses & resizes them – other places like F-Droid.org might keep them full-size) and build upon it (e.g. add per-release changelogs and a featureGraphic if you like – my Fastlane Cheat Sheet may be a guidance with that.
Well, all done then I guess – so we can close this issue?

Oh, PS: donations & Co. If you use Github's FUNDING.yml, those details will be picked up automatically with each release. It doesn't support BC, so I've added your BC address manually already here.

Thank you so much @IzzySoft I'll include the fastlane and check all your comments! this is great 🎉 🚀 !

Also I just remeber you mentioned you have some info about how to upload this to F-Droid, do you?

Gladly! Should there be any question left, just ask. Otherwise I guess we'll meet "over there" once you're ready :smiley:

One last question @IzzySoft , what's the frequency of updates? When should I expect your repo to get the latest version?

Within 24h of your tagging and attaching an APK. Updater runs once a day and publishes within an hour.
For more background: see here and here :wink:

Sorry for reusing this issue over and over @IzzySoft 😄 I think the category is not the right one,CNA I change it myself?

And another question from @FrontendCrypto , of we don't include pictures for the French version, will it be a fallback to the English version?

@KoalaSat what a coincidence! I just returned home from a meeting with frinds. Right at the time you wrote this comment, I discovered it when setting up a device with the F-Droid client – and returning home immediately fixed it :rofl: So it will be corrected with the next sync. Thanks for bringing it up! Strange it tried to separate the 3 Nostr clients that way with 2 different misspellings :see_no_evil: (that said, I still waiting for a catholic priest coming up with a 4th client called "PaterNostr" :speak_no_evil: :dash:

hahaha perfect thanks for taking care of us! 😄

Hi @IzzySoft. We have an issue. Description in full_description.txt differs from what I am seeing in your site. Any clues about why this could be happening?

Certainly. Fastlane was not yet set up on my end as you never signaled it's ready :rofl: Well, once a month my cross-checker would look for it, so I'd have noticed within a few days anyway – but as I did not yet it's not yet there. Enabled that now with the exception of screenshots; don't you think 30 screenshots is a bit overdoing it? If you link to an image gallery, that's certainly OK. But with metadata, I'd say 15 would be quite a lot already. While it's quite impressive what I see there (wow, really!): do you think all of them are needed there (especially kepping in mind people with a "cheap" data plan or on "less than ideal" connections/bandwidth)?

Yes, you are right. I created a PR reducing the number of images. I don't know about signal when is ready.

I created a PR reducing the number of images.

Thanks!

I don't know about signal when is ready.

I took care of that by subscribing to your PR, so I will receive a notification once it's merged :smile:

I created a PR reducing the number of images.

Thanks!

I don't know about signal when is ready.

I took care of that by subscribing to your PR, so I will receive a notification once it's merged :smile:

Oh! Sorry I completely misunderstood you 😅

No prob, we managed :rofl:

Hi again @IzzySoft an user just noticed that we had again some warnings of anti features https://apt.izzysoft.de/fdroid/index/apk/com.nostros the script https://github.com/iBotPeaches/Apktool/raw/master/scripts/linux/apktool didn't raised any problem and this time I have no clue of which library is the responsible

@KoalaSat you can always check with the libraries section in my repo's web interface. Or use my library scanner yourself, it's all FOSS :smiley: For a guide, please see: Identify modules in apps.

The culprit is MLKit, dragging in the other dependencies. Why do almost all Nostr clients include that one now? QR Codes I guess, but there are alternatives – apps like Conversations (XMPP) show that's possible.

I think your guess is correct I recently included a QRCode reader library, thanks for you help!

Thank you for taking these things seriously! Keeping my fingers crossed then you find an easy replacement that works to your full satisfaction :crossed_fingers:


This is concerning the Apollo Template

I have multiple users and would like to have different layouts for them and how is that configured in app.js

If you have any questions about our Premium Templates, please feel free to ask the link below for Apollo templates.
https://forum.primefaces.org/viewforum.php?f=99


Site Address on Create Webonary Site page not being populated from form data

When clicking on an application form on this page
https://www.webonary.org/wp-admin/network/sites.php?page=create-webonary-site
All fields are populated except the New Site Address Field.
All information is sent from the application form in the site request email

Phillip, I'm still not seeing the text in the field.


Unable to start kubelet after adding vsphere.conf file

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
I am trying configure/use vmware datastore to use it as volume(create static vmdk and/or create volume dynamically as per https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/policy-based-mgmt.html
and when I follow
https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/existing.html
to configure user and vsphere.conf for k8s v1.10.4 (version 1.9 and above) I am not able to start the kubelet service and further no operation can be done like kubectl create,get pods,get nodes
What you expected to happen:
after vsphere.conf setting kubelet should start and should be able to perform operation like create
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Kubernetes version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.4", GitCommit:"5ca598b4ba5abb89bb773071ce452e33fb66339d", GitTreeState:"clean", BuildDate:"2018-06-06T08:13:03Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.4", GitCommit:"5ca598b4ba5abb89bb773071ce452e33fb66339d", GitTreeState:"clean", BuildDate:"2018-06-06T08:00:59Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Cloud provider or hardware configuration: vsphere V 6.5

OS (e.g. from /etc/os-release):
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"

Kernel (e.g. uname -a):

Linux barnda129.inblrlab.avaya.com 3.10.0-862.3.2.el7.x86_64

Install tools:
Others:

create vsphere.conf in /etc/kubernetes
disk.EnableUUID is set to true for both master and worker node
added
--cloud-provider=vsphere
--cloud-config=/etc/kubernetes/vsphere.conf
in
/etc/kubernetes/manifests/kube-controller-manager.yaml
/etc/kubernetes/manifests/kube-apiserver.yaml
Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --cloud-provider=vsphere --cloud-config=/etc/kubernetes/vsphere.conf"   (at location /etc/systemd/system/kubelet.service.d/10-kubeadm.conf )
in master node
in worker node
Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --cloud-provider=vsphere"
at location /etc/systemd/system/kubelet.service.d/10-kubeadm.conf
Attached vspgere.conf vsphere.docx
Error Trace
Jul 31 12:36:11 barnda129 kubelet: E0731 12:36:11.688844   24258 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:461: Failed to list *v1.Node: Get https://<IP_ADDRESS>:6443/api/v1/nodes?fieldSelector=metadata.name%3Dbarnda129.inblrlab.avaya.com&limit=500&resourceVersion=0: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused
Jul 31 12:36:12 barnda129 kubelet: E0731 12:36:12.686611   24258 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:452: Failed to list *v1.Service: Get https://<IP_ADDRESS>:6443/api/v1/services?limit=500&resourceVersion=0: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused
Jul 31 12:36:12 barnda129 kubelet: E0731 12:36:12.688701   24258 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://<IP_ADDRESS>:6443/api/v1/pods?
vsphere.docx
fieldSelector=spec.nodeName%3Dbarnda129.inblrlab.avaya.com&limit=500&resourceVersion=0: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused
Jul 31 12:36:12 barnda129 kubelet: E0731 12:36:12.689943   24258 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:461: Failed to list *v1.Node: Get https://<IP_ADDRESS>:6443/api/v1/nodes?fieldSelector=metadata.name%3Dbarnda129.inblrlab.avaya.com&limit=500&resourceVersion=0: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused
Please let me know what is missing here

Can you please try to also deploy vsphere.conf on the workers and add --cloud-config= parameter? We run into the same issue and even though it's documented that the conf is not needed on the workers, it seems to break the kubelet.

I have done that before opening the issue here. That also didn't work.

Sorry for being not clear. What I meant is to also pass the vsphere.conf as --cloud-config parameter to each kubelet. Looks like you don't do that currently:

in worker node
Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --cloud-provider=vsphere"

However, looking at the logs it seems like communication between the API server and kubelet is blocked or API is not reachable. Is everything working as expected on the control plane?

Ok, that was not done. Will try that.

- --cloud-provider=vsphere
- --cloud-config=/etc/kubernetes/vsphere.conf

added above in /etc/kubernetes/manifests/kube-apiserver.yaml
/etc/kubernetes/manifestskube-controller-manager.yaml
/etc/systemd/system/kubelet.service.d/10-kubeadm.conf
of master node
and in worker node
- --cloud-provider=vsphere
- --cloud-config=/etc/kubernetes/vsphere.conf

in /etc/systemd/system/kubelet.service.d/10-kubeadm.conf
then restarted systemctl daemon-reload followed by systemctl restart kubelet.service worker and master
which results in error
Aug 22 14:46:51 barnda129 kubelet: E0822 14:46:51.272118    9409 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://<IP_ADDRESS>:6443/api/v1/pods?fieldSelector=spec.nodeName%3Dbarnda129.inblrlab.avaya.com&limit=500&resourceVersion=0: dial tcp <IP_ADDRESS>:6443: getsockopt: connection refused
If I remove     - --cloud-provider=vsphere
- --cloud-config=/etc/kubernetes/vsphere.conf
from /etc/kubernetes/manifests/kube-apiserver.yaml and kube-controller-manager.yaml, I dint see any error but  while creating pod with the example given https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/persistent-vols-claims.html
Aug 22 15:29:25 barnda135 kubelet: I0822 15:29:25.112493   23148 reconciler.go:207] operationExecutor.VerifyControllerAttachedVolume started for volume "pv0001" (UniqueName: "kubernetes.io/vsphere-volume/[<IP_ADDRESS>_DS1] volume/test") pod "pvpod" (UID: "f9ed41a6-a5f1-11e8-94ea-005056b3208e")
Aug 22 15:29:25 barnda135 kubelet: E0822 15:29:25.117281   23148 nestedpendingoperations.go:267] Operation for ""kubernetes.io/vsphere-volume/[<IP_ADDRESS>_DS1] volume/test"" failed. No retries permitted until 2018-08-22 15:29:57.117211852 +0530 IST m=+237.602265226 (durationBeforeRetry 32s). Error: "Volume not attached according to node status for volume "pv0001" (UniqueName: "kubernetes.io/vsphere-volume/[<IP_ADDRESS>_DS1] volume/test") pod "pvpod" (UID: "f9ed41a6-a5f1-11e8-94ea-005056b3208e") "

@GajaHebbar Looks like API server is not getting started correctly after you are adding flags
- --cloud-provider=vsphere
- --cloud-config=/etc/kubernetes/vsphere.conf

Please checkout manifest file for API server, and make sure /etc/kubernetes/ is mounted into the API server pod.
For kubernetes cluster deployed using kubeadm, generally /etc/kubernetes is not accessible to system pods.
you may need to move vsphere.conf file in /etc/kubernetes/pki/ or other accessible directory.
Please refer manifest files posted at - https://gist.github.com/divyenpatel/f5f23addca31b0a7da1647831539969f

Hi @divyenpatel ,
I am working with @GajaHebbar on this, we tried the configuration as mentioned here: https://gist.github.com/divyenpatel/f5f23addca31b0a7da1647831539969f , but after creating the pod we are encountering this error "Invalid configuration for device '0'."
The logs are as follows:
Aug 24 18:55:29 barnda135 kubelet: I0824 18:55:29.670835    5815 reconciler.go:207] operationExecutor.VerifyControllerAttachedVolume started for volume "pv0001" (UniqueName: "kubernetes.io/vsphere-volume/[<IP_ADDRESS>_DS1] volume/test") pod "pvpod" (UID: "e2b75b77-a7a0-11e8-9476-005056b3208e")
Aug 24 18:55:29 barnda135 kubelet: E0824 18:55:29.675404    5815 nestedpendingoperations.go:267] Operation for ""kubernetes.io/vsphere-volume/[<IP_ADDRESS>_DS1] volume/test"" failed. No retries permitted until 2018-08-24 18:57:31.67535422 +0530 IST m=+90113.195561718 (durationBeforeRetry 2m2s). Error: "Volume not attached according to node status for volume "pv0001" (UniqueName: "kubernetes.io/vsphere-volume/[<IP_ADDRESS>_DS1] volume/test") pod "pvpod" (UID: "e2b75b77-a7a0-11e8-9476-005056b3208e") "
Aug 24 18:55:30 barnda135 kubelet: E0824 18:55:30.545966    5815 kubelet.go:1640] Unable to mount volumes for pod "pvpod_default(e2b75b77-a7a0-11e8-9476-005056b3208e)": timeout expired waiting for volumes to attach or mount for pod "default"/"pvpod". list of unmounted volumes=[test-volume]. list of unattached volumes=[test-volume default-token-rcb68]; skipping pod
Aug 24 18:55:30 barnda135 kubelet: E0824 18:55:30.546053    5815 pod_workers.go:186] Error syncing pod e2b75b77-a7a0-11e8-9476-005056b3208e ("pvpod_default(e2b75b77-a7a0-11e8-9476-005056b3208e)"), skipping: timeout expired waiting for volumes to attach or mount for pod "default"/"pvpod". list of unmounted volumes=[test-volume]. list of unattached volumes=[test-volume default-token-rcb68]

@neeraj23 @GajaHebbar Do you see PVC bound to PV? Are you using PVC in the Pod Spec?
Can provide kubectl describe output for PV, PVC and Pod. We need to see the events section from kubectl describe output for failures.

Hi @divyenpatel , The VMs already have disk.enableUUID=1 set.
I have created the pv, pvc and pods using these three files
vpshere-volume-pvcpod.yaml.txt
vsphere-volume-pv.yaml.txt
vsphere-volume-pvc.yaml.txt
The pvc and pv  are shown to be in bound state. But I am not able to start a pod using the pv and pvc.
The describe output for pv, pvc and pod are as follows.
describe pod.txt
describe pv.txt
describe pvc.txt

I tried to create a pod using vsphere volume in another setup using this yaml file
test-pod.yaml.txt
But I get the error saying "Invalid configuration for device '0.'"
The output of kubectl describe pod is as follows.
describe pod.txt

I see you have following volumePath
volumePath: "[/Bangalore/datastore/<IP_ADDRESS>_DS1] volume/test.vmdk"

In the above path Bangalore, and datastore are datastore folders? If not, you have incorrect volumePath.
It should be as shown below.
If datastore sharedVmfs-0 is under datastore folder DatastoreFolder.
Here kubevols is the directory in the datastore in which vmdk is present.
volumePath: "[DatastoreFolder/sharedVmfs-0] kubevols/test.vmdk"

If datastore sharedVmfs-0 is under root / folder.
volumePath: "[sharedVmfs-0] kubevols/test.vmdk"

We have updated instructions for configuring vSphere Cloud Provider recently. Can you please follow and make sure vsphere.conf is correctly configured. - https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/existing.html

@divyenpatel  Looked in to the system and there were issues with datastore which was not accessible from the VM which was running kubernetes cluster, after re-configuring that and with new vsphere.conf file provided https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/existing.html. This issue is fixed


Feature request: Add bulk API to change alert state

Alerts management API
Currently, there is no way to change the alert state (Acknowledge / Close) for all the alerts generated by a specific alert rule.
The specific use-case is to automate alert resolution (bulk state changes) by an external tool using criteria such as alert rule and time range.
Thanks,
Sourabh

Thanks @sopatwar for the suggestion. We will update you once it's ready.

Thanks @assing for looking at this.
Any tentative ETA?

@sopatwar I don't have any ETA.


Add 2 new theme to the Terminal Portfolio

Fixes  #125 by @TechSpiritSS
Two new themes are added into the Terminal Portfolio (Vibrant and Galaxy)
Preview Link

1. Vibrant theme

2. Galaxy Theme

@dheerajchhatanidc That's great
It can be merged 👍

Great 🚀
Thanks @Arun9739 for reviewing the PR


App: Toucher

Awesome - thanks! Did you know there's a Bangle.on('swipe' event when you drag your finger left-right or right-left?

I didn't know :D
I will add that tonight :D
Thanks


Add a section about public key system usage in practice (encryption chapter)

This is essential to support the NCEA merit/ excellence RSA guide.
It will explain how public key is used to safely share a symmetric key which is then used for further communications.

It will explain how public key is used to safely share a symmetric key which is then used for further communications.

This is currently explained in a sentence within the chapter section.

Public key systems are generally slower than symmetric systems, so the public key system is often used to then send a new key for a symmetric system just once per session, and the symmetric key can be used from then on with a faster symmetric encryption system.


Memory leak patch

The patch fixes the issue of memory leak which becomes obvious in case of multiple files being uncompressed (either single for loop or  mp.Pool). See the issue  for more details.

Coverage increased (+2.6%) to 40.426% when pulling ea77a80b077b34b8179b07bb2deff7b74576d5ba on bmatv:master into a5f6774d33e862ca5504666326efbc1579f6a4ed on ionelmc:master.


Update focal_loss.py to consist with the original formula.

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Enhance the code to make it more easily comprehensible. As in the paper, pt denotes the probability, and the coefficient of Focal Loss is \alpha * (1 - pt) ** \gamma
Modification
Modified the computation method of the Focal Loss coefficient.

OK, now I add some comments and leave the code unchanged. @ryylcc

@yarkable Please fix the lint

@hhaAndroid done!


Refactor the WalkingControllers as set of libraries

With this PR the WalkingControllers repo will become a set of libraries.
Disclaimer: The PR is currently in draft and it is not ready to be reviewed.
@traversaro @S-Dafarra @bemilio

The PR is ready to be reviewed. @traversaro @S-Dafarra

By the way, note that if you install some libraries, then people may expect some kind of stability of the symbol exposed, unless the documentation does not suggest something different. For this reason, feel free to make some libraries private, in the sense that they can be used only by binaries in this project and are not installed.

Some minor comments: just a curiosity, there is any reason for having multiple ways to refer to the same library (source directory libStd_helper, header directory StdHelper, library name Std_helper) ?

Is there something you suggest? I tried to follow the structure presented in https://github.com/robotology/how-to-export-cpp-library.
Can you indicate a good practice?

Is there something you suggest? I tried to follow the structure presented in https://github.com/robotology/how-to-export-cpp-library.
Can you indicate a good practice?

Unfortunately this is something that is definitely not really uniform across C++ projects, however unless there is some specific reason, I would stick to the least possible numbers of directories, for example WalkingControllersStdHelper for the library (becuase it needs to have a unique name) and StdHelper for the directories.

@traversaro

Is there something you suggest? I tried to follow the structure presented in https://github.com/robotology/how-to-export-cpp-library.
Can you indicate a good practice?

Unfortunately this is something that is definitely not really uniform across C++ projects, however unless there is some specific reason, I would stick to the least possible numbers of directories, for example WalkingControllersStdHelper for the library (because it needs to have a unique name) and StdHelper for the directories.

Ok just to clarify,

the library name should become ${PROJECT_NAME}StdHelper
the folder structure could be the following one:.
|-- cmake
|   |-- AddInstallRPATHSupport.cmake
|   `-- ...
|-- src
|   |-- iDynTreeHelper
|   |   |-- include
|   |   |   `-- WalkingControllers
|   |   |       `-- iDynTreeHelper
|   |   |           `-- Helper.h
|   |   |-- src
|   |   |   `-- Helper.cpp
|   |   `-- CMakeLists.txt
|   |-- StdHelper
|   |   |-- include
|   |   |   `-- WalkingControllers
|   |   |       `-- StdHelper
|   |   |           |-- Helper.h
|   |   |           `-- Helper.tpp
|   |   |-- src
|   |   `-- CMakeLists.txt
|--  ...

I think this make sense.

To have libWalkingControllerStdHelper.so the target has to be set as WalkingControllerStdHelper. However, this has the drawback to have also the component like WalkingControllers::WalkingControllerStdHelper, while I would like to have WalkingController::StdHelper. Is there something that I miss?

To have libWalkingControllerStdHelper.so the target has to be set as WalkingControllerStdHelper (see here). However, this has the drawback to have also the component like WalkingControllers::WalkingControllerStdHelper, while I would like to have WalkingController::StdHelper. Is there something that I miss?

Here the answer!

@traversaro @S-Dafarra do you have any other suggestions? I was thinking of introducing a file for tracking the bugfix and the new features. Something similar to this

@traversaro @S-Dafarra do you have any other suggestions?

No, let's merge!

I was thinking of introducing a file for tracking the bugfix and the new features. Something similar to this

To be honest I found that structure (that was copied from YARP) a bit complex to mantain, as for each new release you need to add a file. For other repos I started using the format described in https://keepachangelog.com/en/1.0.0/ that is compact and has the advantage of being described somewhere (in that website).

CHANGELOG.md added

If for you it is ok, I can merge the PR

Ok for me!

Ok!


indexSelectedOption supported on parent node

Got it... I understand what this is doing now. This looks to see of indexSelectedOption is on a wrapping undefined parent? E.g.
  <auro-thing indexSelectedOption="2">
    <auro-menu id="auroMenu2" icon>
      <auro-menu-option data-value="Stops">Stops</auro-menu-option>
      <auro-menu-option disabled data-value="Price">(disabled) Price</auro-menu-option>
      <auro-menu-option data-value="Duration">Duration</auro-menu-option>
      <auro-menu-option data-value="Departure">Departure</auro-menu-option>
      <auro-menu-option data-value="Arrival">Arrival</auro-menu-option>
    </auro-menu>
  </auro-thing>

Question: Why would we support this? If the API is defined that indexSelectedOption is to be on auro-menu why would this be needed?
Originally posted by @blackfalcon in https://github.com/AlaskaAirlines/auro-menu/pull/58#discussion_r787112159

Turns out this wasn't actually broken and the problem was how auro-menu was imported into auro-dropdownmenu. The fix there


adding pandel distribution

I implemented a scipy-like pandel pdf that allows also random sampling, and has log-pdf and cdf available

Maybe @atfienberg or @JanWeldert can take a look, but i think safe to merge?

Right, the values can be chose upon instantiation! And there are some defaults that should not be crazy


Update login page design layout. Bold the form and submit buttons. Ad…

…d to styling.

Branch deployed successfully to vercel.


created dotPDN.paint.net (manifest 1.4)

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Does your manifest conform to the 1.2 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

I have prepared this PR for when packages made with manifest 1.4 are supported
Microsoft Reviewers: Open in CodeFlow

I have prepared this PR for when manifest 1.4 is supported

I'd also like to note that this doesn't contain all of the installer types that paint.net has. See https://github.com/microsoft/winget-pkgs/compare/master...Trenly:winget-pkgs:zips/paintdotnet-4.3.12?expand=1 for a complete manifest

I'd also like to note that this doesn't contain all of the installer types that paint.net has. See https://github.com/microsoft/winget-pkgs/compare/master...Trenly:winget-pkgs:zips/paintdotnet-4.3.12?expand=1 for a complete manifest

Since you have a PR already ready to go, would you like me to close this one?


Why is temp_offset an int8_t?

Question in title refers to ./bme68xmodule.c. Shouldn't temp_offset be a float rather than an int?

The temperature offset is part of the ambient temp calculation, and is to compensate for the impact of the internal heater in the BME688x. The compensated ambient temp is fed into the BSEC pressure and humidity calculations. As far as I can see it is an int in the C code as part of the bme68x_dev struct and later on deeper in the Bosch code it is cast to other types.
So here we are in the python module.
 int t_offs;
 …….
 …….
self->temp_offset = t_offs;
    self->bme.amb_temp = 25 - self->temp_offset;

You might also ask why 25?
My guess is that this is copied from the Arduino BSEC Integration examples.
Here we are in the temp compensation where is it cast to int32_t.
var1 = (((int32_t)dev->amb_temp * dev->calib.par_gh3) / 1000) * 256;

And here it is cast to a float for heater resistance
 var5 = (var4 + (var3 * (float)dev->amb_temp));

Bosch tend to use examples rather than documenting their API's, and as the core is closed source some of it is puzzling.
You could ask on the Bosch Sensortec forum, and there are some questions in this area like this one:
Q: The driver uses bme680_dev::amb_temp and BSEC  BSEC_INPUT_HEATSOURCE. Do both have to be set for correct compensation?
Example: amb_temp = 22C and BSEC_INPUT_HEATSOURCE 5C because the PCB is 5C warmer
A: If you know clearly about the temperature offset coming from PCB self heating,  then you can set this temperature offset as heat source as input when calling the lib to process the data.    Then you just need to use temperature value read from sensor and heat source ( 2 input of lib).  no need to set amb temperature into bsec lib.


fix(tag): set input dependency to correct version

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines: https://github.com/wc-catalogue/blaze-elements/blob/master/docs/CONTRIBUTING.md#commit
[x] There are no linting errors and code is properly formatted (your run before push yarn ts:format && yarn ts:lint:fix)
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x")
[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

Wrong version is set in tag/package.json which leads to errors on build
See #236 for details
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

I didn't add BREAKING CHANGE: as there is not really any breaking change it's just fixing bad release as someone in the past did release version input 2.0.0 for unknown reason. If you want can add it there but not sure if it's really necessary.

pls let's read what I've written one more time :) I think we are not on the same page

as discussed on internal status meeting, we can move forward as release will be resolved within another PR. thanks @elmariofredo


Test point

Will this script work without rebooting if phone test point  was shorted befor? Can we overcome through test point shortening the 4-5 attemts interruption?

just for later reference, this question was answered in the host repo:
https://github.com/SkyEmie/huawei-honor-unlock-bootloader/issues/52#issuecomment-673267924


Measure gas costs for monitor claimReward and claim functions

This issue keeps track of the new gas measurements to be taken for 0.10.0.
@palango says

Especially the monitor and claimReward functions of the MS contract would be nice, as that would help us to make estimated of how much gas the MS account should have in reserve. (Same for the OneToN claim)

The results should be included in raiden_contracts/constants.py.

I'm documenting the current way of gas measurements in #508.


Not all parameters from OpenAPI Spec are loaded

I have checked the following:

[X] I use the newest version of bruno.
[X] I've searched existing issues and found nothing related to my issue.

Describe the bug
In one of my enpoints I have this:
      parameters:
        - $ref: "#/components/parameters/scrlimit"
        - $ref: "#/components/parameters/iprlimit"
        - $ref: "#/components/parameters/querydate"
        - $ref: "#/components/parameters/client"
        - $ref: "#/components/parameters/frompattern"
        - $ref: "#/components/parameters/pg"
        - $ref: "#/components/parameters/ps"
        - $ref: "#/components/parameters/deviation_by"

Bruno 1.28.0 (and 1.23 I had before) only get these:
params:query {
  ~scrlimit:
  ~iprlimit:
  ~by:
}

So just the first two and the last one.
.bru file to reproduce the bug
There is no issue with the bru file itself. It's just that the import didn't get me all parameters.
Screenshots/Live demo link
I think description should be sufficient. I didn't include my 4400 line long OpenAPI spec. I can, if required.

Update: I downloaded my spec as JSON.
Import for that worked. Just the yaml is not imported completely.

Update 2:
I think I found the issue. It's not JSON vs. YAML it's references.
The JSON file I took from my running application, which already interpreted the YAML file and seems to have taken care for some of the references I use.
Here is a screenshot of a diff I did. Left side is a JSON version converted directly from the YAML I wrote. This one failed in Bruno.
On the right is the JSON which was properly loaded by Bruno.

I cannot share the full Spec, but I can (later) try to create a smaller spec revealing the same issue.
I use a lot of "$ref"s. They are not replaced with the actual code. Bruno does not generate input fields for parameters from $ref.


DSD-733: Updating the SearchBar's placeholder

Fixes JIRA ticket DSD-733
This PR does the following:

Makes the placeholder property in the textInputProps prop for the SearchBar component not required anymore.
Sets the default placeholder value to "Search terms"

How has this been tested?
Storybook and tests.
Accessibility concerns or updates

N/A

Checklist:

[ ] I have updated the Storybook documentation accordingly.
[ ] I have added relevant accessibility documentation for this pull request.
[ ] All new and existing tests passed.

Front End Review:

[ ] View the example in Storybook

Tugboat has finished building the preview for this pull request!
Link:

https://pr891-kbc7pzly35lo4cygeurjpbg4rx4vefbv.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/62263cdfaf445bb3158ef52c

Tugboat has finished building the preview for this pull request!
Link:

https://pr891-kbc7pzly35lo4cygeurjpbg4rx4vefbv.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/62263cdfaf445bb3158ef52c


TLS optimization on RAM possible? (ESP8266)

The support of encrypted communication with the broker is still EXPERIMENTAL. Anyhow it works quite well. The only but critical pain is the 20k RAM usage on the ESP8266. This is a vast amount on this small chip. Encryption to the broker is a must have today, therefore really glad to have this. Is there is somebody able to check, if we can optimize the RAM, maybe even make it slower this would be a big benefit. I do not see any commit to this library since nine months. Project in an Idle state?

In case anybody still has this problem: we can save a TON of memory (~15k in my experience) by utilising MFLN or Maximum Fragment Length Negotiation. The full description can be found here, but the jist is this:
#define SERVER "someserver.com"
#define PORT 443
#define MAX_FRAGMENT_LENGTH 512

WiFiClientSecure mqttsClient;
PubSubClient mqtt(mqttsClient);

void setupClient() {
// set trust anchors, X509 time, etc. normally
if (mqttsClient.probeMaxFragmentLength(SERVER, PORT, MAX_FRAGMENT_LENGTH ))
   mqttsClient.setBufferSizes(MAX_FRAGMENT_LENGTH , MAX_FRAGMENT_LENGTH );
...
}

I honestly use it in production even if the probe returns false, becaue it works.


Correct typo in readme

Fix ticket reference, as suggested by @AugustoFKL in https://github.com/sqlparser-rs/sqlparser-rs/pull/651#discussion_r986903035

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 85.636%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
10266

Relevant Lines:
11988

💛  - Coveralls


win32 dependency upgrade

support win32 3.0.0

Closed with commit https://github.com/dart-windows/filepicker_windows/commit/f142c77e4c1553f8d5e80cfa06e1eb20fbf20266


skyclient not working

after choosing the mods i want i open the launcher and starts the skyclient version but its always showing error. it is saying "unable to prepare assets to download"

Please make a ticket at https://inv.wtf/skyclient


buffer overflow after compiling with FORTIFY_SOURCE=3

Hi,
Archlinux has recently started building packages with -D_FORTIFY_SOURCE=3,
for example:  c++ -O2 -D_FORTIFY_SOURCE=3 -Dunix zpaqfranz.cpp -pthread.
This results in zpaqfranz crashing with the error:  *** buffer overflow detected ***: terminated.
The crash occurs when showing a multi-page help screen, e.g. zpaqfranz h full or zpaqfranz h a.
I am compiling with gcc 14.1.1

Thank you very much
Arch is rather "a strange beast", I'll check later today

Can you please check the attached pre-release?
Thanks
59_7p.zip

That has fixed the error for me.
Thanks!


[WIP] New interface

Still a work in progress, but I've been working on implementing the proposed rearchitecture from #17.

See my progress update here

Hallelujah a passing test run!
Who woulda thunk it?

What is the status on this? does this project have any future?

I have a local branch where I rewrote this project. It supports unified
with xstream.
There is some more work required to land it. This particular PR should be
closed, and I will push my new WIP branch up when I get back from holiday.
On 18/03/2017 3:05 AM, "Kristian Mandrup"<EMAIL_ADDRESS>wrote:

What is the status on this? does this project have any future?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cyclejs/cycle-time-travel/pull/24#issuecomment-287362472,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYUHXk7IKRtL3H3G7KfKp14ezto_MNIks5rmpMjgaJpZM4GHBVg
.

Yay!
On Fri, Mar 17, 2017, 20:44 Nick Johnstone<EMAIL_ADDRESS>wrote:

I have a local branch where I rewrote this project. It supports unified
with xstream.
There is some more work required to land it. This particular PR should be
closed, and I will push my new WIP branch up when I get back from holiday.
On 18/03/2017 3:05 AM, "Kristian Mandrup"<EMAIL_ADDRESS>wrote:

What is the status on this? does this project have any future?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<
https://github.com/cyclejs/cycle-time-travel/pull/24#issuecomment-287362472
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAYUHXk7IKRtL3H3G7KfKp14ezto_MNIks5rmpMjgaJpZM4GHBVg
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cyclejs/cycle-time-travel/pull/24#issuecomment-287439465,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAmyxxYPj8HwQTcIeuHNpCkTXdGz_Bf1ks5rmtRxgaJpZM4GHBVg
.


Set up as installable binary

Setting this up to be used as a command I can access anywhere via ironpress would be useful for CLI stuff like texture pipelines
Looking into the CLAP crate for this.

additional stuff that could be cool:

ability to spit out a default config for working off of
dry-run flag that reads a config but doesn't act on it?


⚠ Bofrost.at has degraded performance

In 59d61d9, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1443 ms

Resolved: Bofrost.at performance has improved in 7decd0b after 6 minutes.


[sw] Add missing extern declarations for WO MMIO functions

This fixes a linking issue when trying to use the new functions.

Damn, we missed this and I think it was fixed in #2097 by @alphan. Sorry @mcy. Do close if you agree it's fixed already.

Yup. I think me and Alphan raced that issue and I lost. =P


Dogfood ast transformation

Followup of https://github.com/gradle/gradle/issues/9516

@bot-gradle test QF

OK, I've already triggered QuickFeedback build for you.

@bot-gradle test QF

OK, I've already triggered QuickFeedback build for you.

@Mergifyio rebase

@bot-gradle test QF

OK, I've already triggered QuickFeedback build for you.

@bot-gradle test QF

OK, I've already triggered QuickFeedback build for you.

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test QF

Sorry some internal error occurs, please contact the administrator @blindpirate

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test SC

@bot-gradle test SC

OK, I've already triggered SanityCheck build for you.

OK, I've already triggered SanityCheck build for you.


Search not working in components

Although the geo fields are getting created in the tables for components with location custom field, none of the below approaches are able to search if the location field is inside the component. Below is the sample that I tried to pass as parameter. address is the component name and loc is location custom field.
$location[address][loc]
$location[address.loc]

Thank you for reporting this issue. We will strive to fix this by the next release.

Closed by #47


R: update vignettes

See

#1254
#1258

We won't be investing time in vignettes as documentation, and will instead focus on tested examples included in tabbed docs, so this can be closed.


screed loops endlessly on malformed fq

e.g. on this:
@895:1:37:17593:9954/1
GGTTGACGGGGCTCAGGGGGCGGCTGACTCCGAGAGACAGCAGCCGCAGCTGTCGTCAGGGGATTTCCGGGGCGGAGGCCGCAGACGCGAGTGGTGGAGGGAGAAGGCCTGACG

this:
import screed
for record in screed.open('foo.fq'):
   print record.name

will loop endlessly.

Apologies in advance if this is just spam.
If anyone is interested in trying to test the fastq parser further, I made this collection of bad FASTQs while trying to debug similar issues in a parser I wrote. Also biopython has this monstrosity that may be useful.\
Cheers,
Kevin
P.S., If you want to use those as test cases bundled with screed, they're yours.

That's brilliant - thanks, @kdmurray91!

(See #884 too)

i'm interested in working on this

@mr-c @ahaerpfer looks like the problem is here:
a malformed file may never escape the while loop, thereby never return a value for the upstream iterable
screed/fastq.py(38)fastq_iter()
35  	        # Extract the sequence lines
36  	        sequence = []
37  	        line = handle.readline().strip()
38  ->	        while not line.startswith('+') and not line.startswith('#'):
39  	            sequence.append(line)
40  	            line = handle.readline().strip()
41
42  	        data['sequence'] = ''.join(sequence)
in the case of the @ctb example, line is is ''.so

Would be great to handle the list of examples in https://github.com/ged-lab/khmer/issues/760#issuecomment-73407832 too!

[ ] Is it mergable?
[ ] Did it pass the tests?
[ ] If it introduces new functionality, is it tested?
[ ] Is it well formatted? Look at make pep8, make diff_pylint_report,
and make doc output. Use make format and manual fixing as needed.
[ ] Is it documented in the ChangeLog?
[ ] Was a spellchecker run on the source code and documentation after
changes were made?

@proteasome this is an issue - is there a pull request that you're working on somewhere?

@ctb @mr-c @proteasome: I have some more or less related comments here …
The while loop above simply fails to check if we have a line at all, so the quick fix for this issue to break out of the loop could be something like this:
-        while not line.startswith('+') and not line.startswith('#'):
+        while line and not line.startswith('+') and not line.startswith('#'):

However, this would still not solve some other parsing issues that exist, in particular around empty lines in the FASTQ file.  (I guess this also relates to issue #108.)
The current implementation of fastq_iter() behaves like this:

Silently stops parsing the FASTQ file at a blank line between individual records … looks rather dangerous to me.
Continues parsing after blank lines at certain positions within a particular record. (Implicit logic for continuation lines … ?)
Loops infinitely if quality information is missing for a record.

The above quick fix would change the behaviour as follows:

Now raises an IOError if quality information is missing.
Still silently stops parsing at blank lines between records. :-(
Chokes on all other empty lines with an IOError.

One thing that complicates matters is that we immediately throw away the newline character after reading a line from the stream:
    line = handle.readline().strip()

This way we can't reliably discern between just an empty line and EOF anymore (see https://docs.python.org/2/tutorial/inputoutput.html#methods-of-file-objects).
I'd volunteer to refactor fastq_iter() so that the behaviour is more consistent, incuding sensible error messages.  (Counting input lines and mentioning the line number in error messages might also help users). [Might take until after I'm back home from the conference.]
Open question here:

How to treat empty lines?  (I'd go with @mr-c's comment in #108 to be liberal in what we accept and simply discard them.)
Do you actually need a mechanism for continuation lines for bases and quality info?  If so this should probably be more explicit in the code, if not, the parser should also throw an error.

In the meanwhile if you want to go for the quick fix, I'll happily open a pull request for this [@proteasome has already left PyCon; don't know when he'll be online again].
Opinions, complaints, hints, pizza, … ?

Two thoughts --
first, we should work towards having tests in khmer for tricky fastq parsing for both the seqan (C++) and screed (Python) parsers; it's probably important to make sure they don't barf on too many different things.
second, I would be in favor of minimalistic changes to the existing parser unless we run into widespread real-world situations that indicate further problems.

If you want, I'll add a verbose C++ test driver and a series of tests to the jenkins build script. This way we can clone the broken fastq pool only on jenkins and not lump it into the khmer repo.

On Fri, Apr 17, 2015 at 05:20:51AM -0700, Kevin Murray wrote:

If you want, I'll add a verbose C++ test driver and a series of tests to the jenkins build script. This way we can clone the broken fastq pool only on jenkins and not lump it into the khmer repo.

More generally, I think we should be exposing the C++ parsing code via Python
and then we can simply do comparisons to make sure they return reasonably
consonant results... @camillescott, thoughts?

Specific issue fixed in https://github.com/dib-lab/screed/pull/38 but more discussion may be needed :).

This is fixed, no? Double-check for 2.0.

Fixed by dib-lab/screed#38; more discussion in #976.


cloud: update cloud sdk that supports fips 140 for cloud sdk (#16098)

This is an automated cherry-pick of #16098
What is changed and how it works?

Issue Number: Close #16907

What's Changed:
update the cloud sdk, include aws sdk and azblob sdk

Related changes

[ ] PR to update pingcap/docs/pingcap/docs-cn:
[ ] Need to cherry-pick to the release branch

Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Release note

None

/test

raftstore::test_stats::test_query_stats fails, but it does not relate to this PR. Merging...


ERROR:device_event_log_impl.cc(214)] [19:33:20.373] USB: usb_device_handle_win

After I compiled the program, rpa cannot find the elements and displays an error:
DevTools listening on ws://<IP_ADDRESS>:49624/devtools/browser/3180ed9d-ff51-4d58-897b-a40d33e090f1
[6664:9712:0614/193320.373:ERROR:device_event_log_impl.cc(214)] [19:33:20.373] USB: usb_device_handle_win.cc:1058 Failed to read descriptor from node connection: A device connected to the system is not working. (0x1F)
[6664:9712:0614/193320.377:ERROR:device_event_log_impl.cc(214)] [19:33:20.376] USB: usb_device_handle_win.cc:1058 Failed to read descriptor from node connection: A device connected to the system is not working. (0x1F)
[6664:9712:0614/193320.530:ERROR:device_event_log_impl.cc(214)] [19:33:20.531] Bluetooth: bluetooth_adapter_winrt.cc:1072 Getting Default Adapter
r.init(visual_automation = True,chrome_browser = False)
r.wait(2)
r.type('assets/final_date.png','14/06/2021')

Hey @Paulo-Galego,
because I was not able of replicating this issue, I did a little bit of research.
Also I am a little bit confused because of "chrome_browser=False", but do you use an chrome version above 90?
Hope it will help you,
fi-do

Adding on to @fi-do's reply, @Paulo-Galego is this error still happening for you?
RPA for Python talks directly to the Chrome browser using a websocket connection if chrome_browser = True (default). But it uses port 9222, above error messages is from port 49624. Is this a Linux system? Have you tried installing OpenCV and Tesseract from this link? Also, before doing r.init() can you add below line to show debugging output?
r.debug(True)


(persistency) The state is broken after reboot

If the server before reboot make a snapshot at index k (>0), in the current implementation commit_index is set to k-1 on reboot. This is to apply the snapshot at k after making a consensus at k.
However, this implementation may break the invariant snapshot_index <= commit_index because snapshot may be advanced by other thread than application thread. This leads to a state snasphot_index=k and commit_index=k-1, which is bad.

This is intended. Not a problem


Create Blog “google-custom-search”

Automatically generated by Netlify CMS

Browser metadata
Path:      /blog/google-custom-search/
Browser:   Chrome <IP_ADDRESS> on Windows 10
Viewport:  2560 x 1238 @0.75x
Language:  en-US
Cookies:   Enabled

Open in BrowserStack

Open Deploy Preview · Mark as Resolved


Error in java launcher.

I have two systems, both are running Windows 10, both having same java application installed and running well without Janel.
But when I try to run with Janel, one of the system run it without any issue and task manager shows custom process name instead of javaw.exe
But on another system I have done everything same, I have double check everything but not able to run the application with janel, it shows this error, "Error in java launcher. error occurred while attempting to find Java class wes/wplayer/client/Start"
Can you help me with this, please?
@michaelknigge

This error ("error occurred while attempting to find Java class ...") is thrown if Janel is not able to find the main class. I can only assume that there is something different on your systems. It seems to me that the JAR file, that contains the class "wes/wplayer/client/Start" is missing...


SendConfigurationApply function does not succeeds on account an AccountPolicy.

Details of the scenario you tried and the problem that is occurring
We use below resource in our guest configuration package for vms on Azure. When running the Get-GuestConfigurationPackageComplianceStatus with our package we get the error as seen in attached screenshot. The error says i cannot convert the string -1 to an int. But nowhere on the machine or the .mof file of the configuration the -1 value is  stated. This causes the guest configuration to show as non-compliant is azure.
Anyone able to debug this or running into the same problem?
Verbose logs showing the problem

Suggested solution to the issue
Please help!
The DSC configuration that is used to reproduce the issue (as detailed as possible)
 # Source: https://github.com/PowerShell/SecurityPolicyDsc/blob/dev/Examples/Resources/AccountPolicy/1-AccountPolicy_Config.ps1
    AccountPolicy AccountPolicies {
         Name                                        = 'PasswordPolicies'
         # 1.1.1 (L1) Ensure 'Enforce password history' is set to '24 or more password(s)'
         Enforce_password_history                    = 24
         # 1.1.2 (L1) Ensure 'Maximum password age' is set to '60 or fewer days, but not 0'
         Maximum_Password_Age                        = 60
         # 1.1.3 (L1) Ensure 'Minimum password age' is set to '1 or more day(s)'
         Minimum_Password_Age                        = 1
         # 1.1.4 (L1) Ensure 'Minimum password length' is set to '14 or more character(s)'
         Minimum_Password_Length                     = 14
         # 1.1.5 (L1) Ensure 'Password must meet complexity requirements' is set to 'Enabled'
         Password_must_meet_complexity_requirements  = 'Enabled'
         # 1.1.6 (L1) Ensure 'Store passwords using reversible encryption' is set to 'Disabled'
         Store_passwords_using_reversible_encryption = 'Disabled'
         # 1.2.1 (L1) Ensure 'Account lockout duration' is set to '15 or more minute(s)'
         Account_lockout_duration                    = 15
         # 1.2.2 (L1) Ensure 'Account lockout threshold' is set to '10 or fewer invalid logon attempt(s), but not 0'
         Account_lockout_threshold                   = 10
         # 1.2.3 (L1) Ensure 'Reset account lockout counter after' is set to '15 or more minute(s)'
         Reset_account_lockout_counter_after         = 15
      }

The operating system the target node is running
OsName                           : Microsoft Windows Server 2019 Datacenter
OsOperatingSystemSKU  : DatacenterServerEdition
OsArchitecture                 : 64-bit
WindowsVersion              : 1809
WindowsBuildLabEx         : 17763.1.amd64fre.rs5_release.180914-1434
OsLanguage                     : en-US
OsMuiLanguages            : {en-US}

Version and build of PowerShell the target node is running
Name                           Value

PSVersion                      7.2.0
PSEdition                      Core
GitCommitId                    7.2.0
OS                             Microsoft Windows 10.0.17763
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Version of the DSC module that was used
2.10.0

I have seen this fail to apply when the account_lockout_duration is set to 0 in the configuration.  If you update the dscresource module 'MSFT_AccountPolicy.psm1' to accept the range of values for this option to be (-1,99999) instead of (0,99999) for both the Set-TargetResource and Test-TargetResource functions.   These are around lines 118 and 293 in the source.


Add a debug plugin

For debugging, a plugin that dumps the content of the exposed data in ASCII to stdout/stderr would be useful.

this is best done from python

closed

@tpaluszk this is different. This issue is about a plugin to write the data exposed by the user in ASCII (something similar to the HDF5 plugin but ASCII based)

In GitLab by @tpaluszk on Jul 31, 2018, 14:19
Is this still a current issue after #83 was closed?


Unable to see build tasks after installing extension in VSTS

I installed the Dynamics 365 Build Tools extension from the Marketplace within my VSTS environment but the tasks are not visible. If I go to "Manage extensions" I saw that it was indeed installed. Are there some additional steps that I missed?
Kind regards,
Joris

Did an uninstall and installed it again and then the tasks appeared


It would be nice to be able to change the width of the FreakyAutoCompleteView list once it is displayed without needing to change the width of the control

Hi, I'm trying to create an app where screen space is very limited (my bad), and it would be nice to be able to enlarge the size of the list only while the user is selecting an option. The only way I can find right now is to change the width of the entire control.

I will have to make a bunch of native changes for this, I am not sure when this will be done or how doable even this is so you might have to wait for a while for this one.
To clarify if you add something visual that shows what you need it generally helps

Thank you for responding so quickly. Here, I am sending you a screenshot of an old app programmed in Swift. Thanks again. I was only mentioning it as a desirable feature, but so far the kit is working wonderfully for me.


Fix browser entry point

UMD builds should be listed in browser. main is traditionally meant for the server-side entry point (i.e. CJS)
https://docs.npmjs.com/cli/v7/configuring-npm/package-json#main
https://docs.npmjs.com/cli/v7/configuring-npm/package-json#browser
The library currently won't load in Vite / SvelteKit because of this

I think we could probably make main point to the esm build. Having main point the the UMD build which is only meant to be used in the browser is what's causing the problem.
I don't think bundlers can generally take UMD as input though I could be wrong on that. They definitely can take ESM though

@tambien did you have any thoughts about this?

 There's a lot of people using this link: https://unpkg.com/tone, and i worry that if it all of a sudden pointed to the esm module instead of build/Tone.js, it might mess up some live sites.

Thanks for taking a look. I've updated it so that it will continue to work for unpkg.
From https://unpkg.com:

If you omit the file path (i.e. use a “bare” URL), unpkg will serve the file specified by the unpkg field in package.json, or fall back to main.

Thanks for the merge! I have this same change pending in tambien/Piano if you'd be able to take a look and merge it there as well. Thanks!!