binary: improve tests for invalid numbers

We should have separate tests for:

alphabetic characters at the beginning of a valid binary number
alphabetic characters at the end of a valid binary number
alphabetic characters in the middle of an otherwise valid binary number
invalid digits (e.g. 2)

If the test suite for binary has test cases that cover these edge cases, this issue can safely be closed.
See https://github.com/exercism/x-common/issues/95

we currently have:
  @tag :pending
  test "invalid binary is decimal 0" do
    assert Binary.to_decimal("carrot") == 0
  end

  @tag :pending
  test "invalid binary is decimal 0 II" do
    assert Binary.to_decimal("convert01") == 0
  end

  @tag :pending
  test "invalid binary is decimal 0 III" do
    assert Binary.to_decimal("10convert") == 0
  end

  @tag :pending
  test "22 is not a binary number" do
    assert Binary.to_decimal("22") == 0
  end

looks like this is all in place, unless "carrot" should be replaced by "1carrot0"

I think 1carrot0 should come in addition to carrot.


Plugin is broken and appears to be abandonware

worth checking with vladimir…? has 4 more commits, see https://github.com/vsch/jsondiff


macOS Host Application

The macOS Host Application link is missing. Can you please add it, to the latest version?
Thank you in advance.

@francescorinaldi
Hi,
www.arducam.com/downloads/app/ArduCAM_Host_V2.0_Mac.app.zip
If you have any problems,please refer http://www.arducam.com/knowledge-base/arducam-typical-problems-arduino-uno/
to find answer.
Let us know if you need more help.
Regards,
ArduCAM support team.

It doesn't work. MacOSX 10.12.6

Just download and its is working with Mojave 10.14.5. However it only captures JPG images and I need BMP Images that are not working correctly on the Windows version of the same software!

@bakerbrown
If you want to get BMP images, you can use our Window version here
https://github.com/ArduCAM/Arduino/tree/master/ArduCAM/examples/host_app/ArduCAM_Host_V2.0_Windows

The MacOs one does not open properly on version Catalina 10.5.7.  Can you guys please post an update that will work on this version?  I don't mind if it's just JPGs.


"No reply" sender email

Transactional emails have a sender of<EMAIL_ADDRESS>which is not in the user's interest. It may be the case that there is a problem with the email (broken links, missing information, etc) and replying to the email is the only way the user can proceed. We will set our sender or reply-to to go to our Zendesk instance.
Tasks:

[ ] Customise Zendesk such that the email ends in "digital.justice.gov.uk" because "ministryofjustice.zendesk.com" is not acceptable for government transactional email.
[ ] Update application config

cc @helenmott @tomwm

@milror00 i think this is something we can/should do as part of updating the way we use zendesk


YARN-11429. Improve the updateTestDataAutomatically in TestRMWebServices.

Description of PR
The goal is to have the same json formatting options when using the updateTestDataAutomatically helper function.
How was this patch tested?
I verified that the updated JSON content is the same as before:
# before
➜  /Users/tdomok/Work/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/resources/webapp git:(YARN-11429) for f in *.json; do echo -n "$f "; cat $f | jq | md5sum; done
scheduler-response-AbsoluteMode.json 3cd84395f2864bbfcab55d1f81be5f44  -
scheduler-response-AbsoluteModeLegacyAutoCreation.json 4dbd90be628a52fa16eac0bde3774d6d  -
scheduler-response-PerUserResources.json eda777af4bf2f6cbfd3dc4b1a0ac945a  -
scheduler-response-PercentageMode.json 9a1dbd77cb034390092a553bfb04c078  -
scheduler-response-PercentageModeLegacyAutoCreation.json 9ca117ab46a4eb8be261650d26b17ae4  -
scheduler-response-WeightMode.json b87bc438cc66619e16edec4acef1dafb  -
scheduler-response-WeightModeWithAutoCreatedQueues-After.json 4265fb1c65813a44989f9f77cbd5e862  -
scheduler-response-WeightModeWithAutoCreatedQueues-Before.json a239664f30b71478991b0504a66dc4a5  -
scheduler-response.json 6e5b607d133ddf4e00eda23842b274db  -

# after
➜  /Users/tdomok/Work/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/resources/webapp git:(YARN-11429) for f in *.json; do echo -n "$f "; cat $f | jq | md5sum; done
scheduler-response-AbsoluteMode.json 3cd84395f2864bbfcab55d1f81be5f44  -
scheduler-response-AbsoluteModeLegacyAutoCreation.json 4dbd90be628a52fa16eac0bde3774d6d  -
scheduler-response-PerUserResources.json eda777af4bf2f6cbfd3dc4b1a0ac945a  -
scheduler-response-PercentageMode.json 9a1dbd77cb034390092a553bfb04c078  -
scheduler-response-PercentageModeLegacyAutoCreation.json 9ca117ab46a4eb8be261650d26b17ae4  -
scheduler-response-WeightMode.json b87bc438cc66619e16edec4acef1dafb  -
scheduler-response-WeightModeWithAutoCreatedQueues-After.json 4265fb1c65813a44989f9f77cbd5e862  -
scheduler-response-WeightModeWithAutoCreatedQueues-Before.json a239664f30b71478991b0504a66dc4a5  -
scheduler-response.json 6e5b607d133ddf4e00eda23842b274db  -

For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'YARN-11429. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 57s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
jsonlint
0m  0s

jsonlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 10 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
45m 26s

trunk passed

+1 :green_heart:
compile
1m  7s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
1m  0s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
checkstyle
1m  2s

trunk passed

+1 :green_heart:
mvnsite
1m 10s

trunk passed

+1 :green_heart:
javadoc
1m  7s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 54s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
2m 12s

trunk passed

+1 :green_heart:
shadedclient
23m 11s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 53s

the patch passed

+1 :green_heart:
compile
0m 56s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
0m 56s

the patch passed

+1 :green_heart:
compile
0m 50s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
0m 50s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 43s

the patch passed

+1 :green_heart:
mvnsite
0m 51s

the patch passed

+1 :green_heart:
javadoc
0m 45s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 41s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
1m 58s

the patch passed

+1 :green_heart:
shadedclient
22m 31s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
118m 48s

hadoop-yarn-server-resourcemanager in the patch passed.

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

229m 52s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5736/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5736

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets jsonlint

uname
Linux 3a552020f5c1 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / e92a9dd6facdd0cd7d318ebd7e4cdde594272c0e

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5736/1/testReport/

Max. process+thread count
935 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5736/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

Thanks @tomicooler for the update, looks good to me, and improves the readability.
It's not strictly related to this patch, and probably not in its scope, but I don't really get why are we doing the following flow for a simple JSON pretty print: string -> JSON POJO (lib#1) -> string -> create an ObjectMapper per pretty print (it's a really heavyweight object, it should be reused) -> JSON POJO (lib#2) -> string again. This is much-much slower than necessary. Probably this should be refactored later.
Regardless I'll merge this now, and create a followup ticket.


How to add Facebook Live and Youtube Live stream options?

Hi,
I am new to this. How can I stream OBS output to multiple channels. I mean, OBS gives option for only one channel. I don't find any settings inside your App. I am using macOS 10.14.6 with OBS 25. Kindly suggest where can I change settings to add options for multiple destinations.
Regards,
JBeuria

Hi,
I am new to this. How can I stream OBS output to multiple channels. I mean, OBS gives option for only one channel. I don't find any settings inside your App. I am using macOS 10.14.6 with OBS 25. Kindly suggest where can I change settings to add options for multiple destinations.
Regards,
JBeuria

I am wondering the same thing.  I was really hopeful that this was the answer to the problem that I was having, but right now it just takes the OBS feed and does nothing with it

This app isn't for broadcasting.  It is for receiving.  When you launch it you're creating an open RTMP server on your computer.  This isn't a replacement for OBS.  You can use OBS to view and/or re-broadcast any RTMP stream you're receiving by tuning into it with a "Media Source" element in OBS studio set to the URL you see in the stream drop down.


SMTP: "HELO can't be [<IP_ADDRESS>]"

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App version
6.202
Where did you get the app from?
Google Play
Android version
11
Device model
No response
Steps to reproduce
Some mail providers seem to forbid SMTP connections when the HELO hostname is <IP_ADDRESS>.
I found the history to this change originating in #2793 (changed in PR #3798).
The question came back in issue #4428.
I have read theses issues and understand that it has been changed so for privacy reasons, and agree that sending the actual real IP or hostname would be detrimental to privacy. However, I believe we can try to find another value that won't be blocked by mail providers. This could potentially be an opt-in option in each SMTP server settings. I'd be ready to make a PR if that is something you would be willing to accept. We could have a select option with values like <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS> and a final value of "Send actual IP address (not recommended)". This way the user still is in control of what is sent and can still use the app even if the mail provider denies privacy conserving values (most providers won't be willing to change their server configuration on user requests).
Expected behavior
Being able to send mail to servers denying the <IP_ADDRESS> HELO hostname
Actual behavior
Connection to the SMTP server rejected due to a forbidden value of <IP_ADDRESS> in the HELO message

Logs
No response

No update on this subject?

Yes disappointing no one is addressing this.  My hosting service is one that does not allow a local host address for HELO.
Seeing an old forum post where someone was insisting K9 had it right and the rest of the world needed to change got me thinking and reading RFCs (aaahhhrrgghh). As far as I can see RFC 5321 from 2008 is still current.  Quoting part 4.1.3.-Address Literals:
"Sometimes a host is not known to the domain name system and communication (and, in particular, communication to report and repair the error) is blocked.  To bypass this barrier, a special literal form of the address is allowed as an alternative to a domain name.  For IPv4 addresses, this form uses four small decimal integers separated by dots and enclosed by brackets such as [<IP_ADDRESS>]..."
<IP_ADDRESS> is a local host address, not the address of the host.  SMTP servers that reject this have the right to do so.  But this is where it gets tricky.
Thunderbird plays by the book, it uses the IP4 address of the client.  Yes that is what the RFC wanted but who wants an IP address off their local LAN subnet sent to the world, it's meaningless, and a minor security weakness.  To its credit, T-bird has an advanced config setting where you can set HELO whatever you want (and I have).
My suggestion is that K9 should follow T-bird, use the local IP4 address but provide a setting to change it.
But if you are going to use a non-compliant value then either a fixed fictitious private address, e.g. <IP_ADDRESS>, or any resolvable fqdn like k9mail.app would work better than the local host address.  Given where Google/Yahoo are going with SPF and DKIM there is also a risk they too will start blocking the local host address.
The old RFC is really the problem here as in a NAT world this parameter is pointless.

rfc 5321 is in reference to smtp -- machine-to-machine/port 25 mail transfer. a more appropriate rfc for discussion of mail submission standards is 6409 - "message submission for mail". as documented, the MTA (message transfer agent) is free to refuse a message for any number of reasons (and not liking the ipnumber on the HELO/EHLO, while not explicitly mentioned, could be one), however, rejecting or bouncing is always referenced as the subsequent handling that should take place. dropping the message on the floor/into the trash (or explicitly sending it to /dev/null as one provider does) is not a documented option in the specification.

Hi njeyaakili.
You are correct, 6409 does say how an MSA should handle message rejection, and I bet you are correct that many fail to do this as described too!
But that isn't the subject of this bug.  This bug is about how k9 incorrectly populates the HELO command and the need to fix that.
6409 is based on 5321, with bits added on.  Quote 3.1 "The protocol used is ESMTP [SMTP-MTA], with additional restrictions or allowances as specified here."  "SMTP-MTA" is a normative reference to RFC 5321 (see references section 12.1).  As HELO format is not one of these restrictions/allowances it remains as defined by 5321.
As a comparison I had a look at how FairEmail populates HELO.  It uses an fqdn dummy.faircode.eu, which if you browse to it https://dummy.faircode.eu gets you a brief description of why it is used for HELO and how FairEmail has settings to modify it.
Strictly speaking this is not 5321 compliant either, not identifying the host, but it gets the job done better than a local host IP.

This issue was raised for K9 a long time ago.  Yet Thunderbird Android still has the issue.  Any progress?
Surely if using the Thunderbird name the Android version should align with the desktop version?
At the moment some users will find Thunderbird desktop can send mail but Thunderbird Android can't as their ISP blocks using the local host address.

Thunderbird for Android is going to be amazing, but it isn't the magic pill to fix all the issues and be just like Desktop. Thunderbird for Android is based on K-9 Mail, so it inherits both the good and the missing. We haven't had a chance to focus on this, but if someone would like to take a stab at it I'm sure we can provide some guidance and potentially setup something similar.
I'd like to avoid too many options and preferences, maybe a good first step would be for someone to propose how this could look to remain compatible in a way that we could provide sensible defaults. Maybe there is a way to detect the scenario and only include the dummy helo domain if 127.0.01 is rejected. Maybe there is another IP we could use instead? I'm sure some of you have done some research into this area.

Thanks for that kewisch.  Your point about too many options is well made.  My keep it simple suggestion, do what the desktop version does and use the device IP address.  That is RFC compliant (though not perfect), and would stop those ISPs who block the local host address.
I'm not a dev - is this hard or trivial?

Thanks for your work Kewish, but I have the same issue on my main email provider, it works perfectly with Thunderbird Desktop, I agree with mutaunt

I suspect this will be somewhere between hard and trivial. Actually changing the IP address isn't a big deal, it is more putting thought into what is the "right thing" to do, and making sure all corner cases are covered. If there are UI options then that would make it a bit more difficult. If there is complex logic or the need to retry that would also make it more difficult to implemet.

If Thunderbird desktop uses the device IP, I think that would be a reasonable first step.  I understand the desire to limit config options, so changing the IP from loopback to the device IP seems like a fair compromise to me, at least for now.  It would at least (hopefully) get folks moving who use hosting providers that block the loopback, because right now we don't have any other option but to use a different app.  I fought with Hostgator's support team, but they are not budging.

We use a loopback address specifically so we don't leak the internal IP address of the device. We also don't want to have to contact an external service to get the device's public IP address just so we can use it with the EHLO command (servers that actually care about the IP address get it from the connection, not the EHLO argument).
That pretty much leaves us with sending static data. So far we've learned that some providers don't accept "localhost", others don't accept "<IP_ADDRESS>". I think FairEmail's approach of using a fully-qualified domain name is a good next approach to try. I suggest we use ehlo.thunderbird.net.


Add to awesome list

https://github.com/sindresorhus/awesome/blob/master/create-list.md

Missing criteria:
Neural art - Creating art and manipulating images using deep neural networks.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Requirements for your pull request

You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration.
Your entry should be added at the bottom of the appropriate category.

Requirements for your Awesome list

Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
Entries have a description, unless the title is descriptive enough by itself. It rarely is though.

To verify that you've read all the guidelines, please add comment with just the word unicorn.
The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.

Go to the top and read it again.


move [Website] url to query param

Refs #3714

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @calebcartwright!

  Generated by :no_entry_sign: dangerJS against bff9f3b88f840ec11c1ecdc255f97e7e9ab835a3


Add TLS to Hive Metastore

/retest

I think this looks much better. We'll need to create a template for these secrets next, and add that template secret hash to the hive-metastore-statefulset in a follow-up PR.

/lgtm
/approve


undefined reason why a release was rejected

verbose: [decide] Orange.Is.the.New.Black.S06.2160p.NF.WEBRip.DDP5.1.x264-NTb - no match for beyond-hd-api torrent Orange Is the New Black S06 2160p NF WEBRip DDP 5.1 x264-NTb - undefined (cached)

what version of cross-seed are you running?

2.9.1

Do you have a reliable way to reproduce this bug?
Can you inspect your cache and search for the relevant cache entry? It should be under decisions > Orange.Is.the.New.Black.S06.2160p.NF.WEBRip.DDP5.1.x264-NTb > some BHD url. Specifically, check what the decision is.

I will let you know in a few

v2.9.3 also has more diagnostics for this bug

I found it in the cache. I'm guessing this is the entry you'd be interested in.  All of the releases in the cache had a decision key except for this one
"https://beyond-hd.me/torrents/orange-is-the-new-black-s06-2160p-nf-webrip-ddp-51-x264-ntb.13525": {
        "firstSeen":<PHONE_NUMBER>422,
        "lastSeen":<PHONE_NUMBER>318
      },

Here's the output using 2.9.3
cross-seed search --verbose --torrent-dir /volume1/data/Torrents/cross-seed/cross-seed-input/tmp/ --trackers beyond-hd-api
verbose: [configdump] {
  jackettServerUrl: 'http://<IP_ADDRESS>:9117',
  jackettApiKey: '[REDACTED]',
  trackers: [ 'beyond-hd-api' ],
  torrentDir: '/volume1/data/Torrents/cross-seed/cross-seed-input/tmp/',
  outputDir: '/volume1/data/Torrents/cross-seed/cross-seed-output',
  searchAll: true,
  verbose: true,
  action: 'save',
  rtorrentRpcUrl: 'http://<IP_ADDRESS>:10000/RPC2',
  offset: 0,
  delay: 5,
  includeEpisodes: true
}
info: Validating your configuration...
verbose: [jackett] making search with query "bscdjpstabgdspjdasmomdsenqciadsnocdpsikncaodsnimcdqsanc"
verbose: [rtorrent] Calling method download_list with params []
info: Your configuration is valid!
info: Found 1 torrents, 1 suitable to search for matches
info: [1/1] Searching for Orange.Is.the.New.Black.S06.2160p.NF.WEBRip.DDP5.1.x264-NTb
verbose: [jackett] making search with query "Orange Is the New Black S06"
verbose: [decide] Orange.Is.the.New.Black.S06.2160p.NF.WEBRip.DDP5.1.x264-NTb - no match for beyond-hd-api torrent Orange Is the New Black S06 1080p BluRay x264 DTS 5.1-ROVERS - its size does not match (cached)
verbose: [decide] Orange.Is.the.New.Black.S06.2160p.NF.WEBRip.DDP5.1.x264-NTb - no match for beyond-hd-api torrent Orange is The New Black S06 BluRay 1080p DTS-HD MA 5.1 AVC REMUX-FraMeSToR - its size does not match (cached)
verbose: [decide] Orange.Is.the.New.Black.S06.2160p.NF.WEBRip.DDP5.1.x264-NTb - no match for beyond-hd-api torrent Orange Is the New Black S06 720p BluRay DTS x264-DEMAND - its size does not match (cached)
verbose: [decide] Orange.Is.the.New.Black.S06.2160p.NF.WEBRip.DDP5.1.x264-NTb - no match for beyond-hd-api torrent Orange Is the New Black S06 2160p NF WEBRip DDP 5.1 x264-NTb - undefined (cached)
verbose: [decide] Orange.Is.the.New.Black.S06.2160p.NF.WEBRip.DDP5.1.x264-NTb - no match for beyond-hd-api torrent Orange Is the New Black S06 1080p NF WEBRip DDP 5.1 x264-NTb - its size does not match (cached)
info: Done! Found 0 cross seeds from 1 original torrents

admin@DiskStation /v/h/admin> cross-seed --version
2.9.3

interesting; so the code must be saving cache entries somewhere with no decision.


added 'p' tag bottom style for narrower section

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fixes #31
Test URLs:

Original: https://www.sunstar.com/

Before: https://main--sunstar--hlxsites.hlx.live/

After: https://--sunstar--hlxsites.hlx.live/

[ ]  If you are adding a new block or a variation to an existing block, please fill below:
Block library path: https://--sunstar--hlxsites.hlx.page/tools/sidekick/library.html?plugin=blocks&path=/sidekick/blocks/&index=0

@rrrragas , can you sync your branch with the latest from main and update the PR? I see a lot of visual differences being reported here.

@rrrragas , can you sync your branch with the latest from main and update the PR? I see a lot of visual differences being reported here.

@sdmcraft updated.. there are couple of visual differences. please let me know if we still can keep padding bottom for 'p' or not

Closed based on this discussion per which this can be done purely through document authoring.


Review functionality around timestamps

I feel that something is not quite right when it comes down to handle timestamps in the RADIUS packet, need to ensure it's all good and smooth

Fixed by df34059


feat(filter): reliability monitor as a separate class to handle reliability logic

Problem
Based on https://github.com/waku-org/js-waku/issues/2075, the logic to detect messages that were missed from the Filter protocol were being detected inside of the Filter SDK implementation. This leads to a tight couple of primary objective of FilterSDK, and reliability goals.
This obstacle also extends to adding further actions that might be taken with additional protocols such as Store pings, and LightPush retries for certain messages.
Solution
Decouple reliability logic into a new ReliabilityMonitor class.
Notes

Best reviewed per commit
Partially resolves #2075

Contribution checklist:

[ ] covered by unit tests;
[ ] covered by e2e test;
[ ] add ! in title if breaks public API;

@danisharora099 just to double check is this PR main and https://github.com/waku-org/js-waku/pull/2127 should be dropped or vice versa?


Support soft affinity scheduling for Gluten

(you don't have to strictly follow this form)

Support soft affinity scheduling for Gluten.

A clear and concise description of what is the intended usage scenario is.

Describe the solution you'd like

A clear and concise description of what you want to happen.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

Done in PR 498


Add Doxygen build and fix all warnings

The C++ code was documented for some time but Doxygen build process was not included. This change now introduces Doxygen builds and fixes all documentation warnings.

@charlesbluca @wence- I'd appreciate your review here sometime next week. Sorry that it is such a long PR, fortunately ~2.8k lines are just the Doxyfile, whereas the remaining is mostly missing documentation.

would it make sense to add codespell as a pre-commit check in this PR as well? There are a few typos that might be easier to review and correct by adding that check and running through the changed files.

This is a great idea, I didn't know codespell but was wondering if something like that existed. I've now added codespell and fixed typos it identified.

Thanks again @charlesbluca , I've addressed the points you raised. 🙂

Thanks for the review @charlesbluca !

/merge


Can't update - deploy fails

This error still persists:
✘ Invoking deployment process: FAILED

 -----------------------------------STDERR-----------------------------------
 o spawn args '-Dmodule_root_dir=/opt/app/tmp/bundle/programs/server/npm/sacha:juice/node_modules/juice/node_modules/jsdom/node_modules/contextify',
 gyp info spawn args '--depth=.',
 gyp info spawn args '--no-parallel',
 gyp info spawn args '--generator-output',
 gyp info spawn args 'build',
 gyp info spawn args '-Goutput_dir=.' ]
 gyp info spawn make
 gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
 gyp info ok
 npm WARN package.json<EMAIL_ADDRESS>No description
 npm WARN package.json<EMAIL_ADDRESS>No repository field.
 npm WARN package.json<EMAIL_ADDRESS>No README data
   % Total % Received % Xferd Average Speed Time Time Time Current
                                  Dload Upload Total Spent Left Speed
  0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed to connect to localhost port 80: Connection refused
 Latest deployment failed! Reverted back to the previous version.
 -----------------------------------STDOUT-----------------------------------
 ) Release/obj.target/contextify/src/contextify.o
   SOLINK_MODULE(target) Release/obj.target/contextify.node
   SOLINK_MODULE(target) Release/obj.target/contextify.node: Finished
   COPY Release/contextify.node
 make: Leaving directory `/opt/app/tmp/bundle/programs/server/npm/sacha:juice/node_modules/juice/node_modules/jsdom/node_modules/contextify/build'

 ><EMAIL_ADDRESS>install /opt/app/tmp/bundle/programs/server/node_modules/fibers
 > node ./build.js

 `linux-x64-v8-3.14` exists; testing
 Binary is fine; exiting
<EMAIL_ADDRESS>node_modules/underscore

<EMAIL_ADDRESS>node_modules/semver

<EMAIL_ADDRESS>node_modules/fibers

<EMAIL_ADDRESS>node_modules/source-map-support
 └──<EMAIL_ADDRESS><EMAIL_ADDRESS> Waiting for MongoDB to initialize. (5 minutes)
 connected
 app stop/waiting
 app start/running, process 2738
 Waiting for 15 seconds while app is booting up
 Checking is app booted or not?
 app stop/waiting
 app start/running, process 2768
 ----------------------------------------------------------------------------

When I remove juice package, same error, just a different package name.

Started TaskList: Deploy app 'Tele_VDDA' (linux)
[<IP_ADDRESS>] - Uploading bundle
[<IP_ADDRESS>] ✔ Uploading bundle: SUCCESS
[<IP_ADDRESS>] - Setting up Environment Variables
[<IP_ADDRESS>] ✔ Setting up Environment Variables: SUCCESS
[<IP_ADDRESS>] - Invoking deployment process
[<IP_ADDRESS>] ✘ Invoking deployment process: FAILED
    -----------------------------------STDERR-----------------------------------
      '-Dvisibility=default',
    gyp info spawn args   '-Dnode_root_dir=/home/ubuntu/.node-gyp/0.10.33',
    gyp info spawn args   '-Dmodule_root_dir=/opt/Tele_VDDA/tmp/bundle/programs/server/npm/sacha:juice/node_modules/juice/node_modules/jsdom/node_modules/contextify',
    gyp info spawn args   '--depth=.',
    gyp info spawn args   '--no-parallel',
    gyp info spawn args   '--generator-output',
    gyp info spawn args   'build',
    gyp info spawn args   '-Goutput_dir=.' ]
    gyp info spawn make
    gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
    gyp info ok
    npm WARN package.json<EMAIL_ADDRESS>No description
    npm WARN package.json<EMAIL_ADDRESS>No repository field.
    npm WARN package.json<EMAIL_ADDRESS>No README data

    /usr/lib/node_modules/wait-for-mongo/bin/wait-for-mongo:14
        throw err;
              ^
    Error: TIMEOUTED_WAIT_FOR_MONGO
        at null._onTimeout (/usr/lib/node_modules/wait-for-mongo/lib/waitForMongo.js:20:14)
        at Timer.listOnTimeout [as ontimeout] (timers.js:112:15)
    -----------------------------------STDOUT-----------------------------------
    3456:27017]
    wait-for-mongo: failed to connect to [123456:27017]
    wait-for-mongo: failed to connect to [123456:27017]
    wait-for-mongo: failed to connect to [123456:27017]
    wait-for-mongo: failed to connect to [123456:27017]
    wait-for-mongo: failed to connect to [123456:27017]
    wait-for-mongo: failed to connect to [123456:27017]
    wait-for-mongo: failed to connect to [123456:27017]
    wait-for-mongo: failed to connect to [123456:27017]
    wait-for-mongo: failed to connect to [123456:27017]
    wait-for-mongo: failed to connect to [123456:27017]
    wait-for-mongo: failed to connect to [123456:27017]
    wait-for-mongo: failed to connect to [123456:27017]
    wait-for-mongo: failed to connect to [123456:27017]
    wait-for-mongo: failed to connect to [123456:27017]
    wait-for-mongo: failed to connect to [123456:27017]
    wait-for-mongo: failed to connect to [123456:27017]
    wait-for-mongo: failed to connect to [123456:27017]
    wait-for-mongo: failed to connect to [123456:27017]
    wait-for-mongo: failed to connect to [123456:27017]
    ----------------------------------------------------------------------------

Completed TaskList: Deploy app 'Tele_VDDA' (linux)

I tried to install  Telescope on EC2 and got above error, can someone help me fix that? Thanks

I have Telescope running on EC2 (deployed again last night).  Can you connect to your database with a mongo shell using the same credentials in your mup.json?  Are you trying to use oplog?  If so, what do your env variables look like? (without sharing passwords obviously)

Also, try just giving Mup more time to deploy, and running mup logs -f
while you're deploying. Sometimes if there's long migrations Mup cuts off
before the deploy process is done.
On Sat, Feb 7, 2015 at 12:27 AM, Jeremy Shimko<EMAIL_ADDRESS>wrote:

I have Telescope running on EC2 (deployed again last night). Can you
connect to your database with a mongo shell using the same credentials in
your mup.json? Are you trying to use oplog? If so, what do your env
variables look like? (without sharing passwords obviously)
—
Reply to this email directly or view it on GitHub
https://github.com/TelescopeJS/Telescope/issues/530#issuecomment-73253413
.

Hi jshimko and SachaG, Thanks for yours help.

yes, I can connect to my database with mongo shell with the same credentials.
I am not using oplog
I had increased Mup time to even 6000

Here is my mup logs -f:
thangdx@thangdx:~/DeployedApp/VDDA$ mup logs -f
Meteor Up: Production Quality Meteor Deployments
[<IP_ADDRESS>] Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.
[<IP_ADDRESS>] Exception in callback of async function: Error: failed to connect to [123456:27017]
at [object Object]. (/opt/Tele_VDDA/app/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/connection/server.js:536:74)
at [object Object].emit (events.js:106:17)
at [object Object]. (/opt/Tele_VDDA/app/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:150:15)
at [object Object].emit (events.js:98:17)
at Socket. (/opt/Tele_VDDA/app/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/connection/connection.js:516:10)
at Socket.emit (events.js:95:17)
at net.js:440:14
at process._tickCallback (node.js:419:13)
Any advice?
Thanks

If I had to guess (which I do), I'd say your database isn't configured correctly in your mup.json (or there's a JSON syntax error that's causing it to not be read properly)...
Error: failed to connect to [123456:27017]
And from your earlier post...
wait-for-mongo: failed to connect to [123456:27017]
That looks to me like you're trying to connect to a database at 123456 on port 27017.  Obviously not a valid IP or domain name.
Also FYI, running mup logs -f is for watching the current live logs.  It starts by showing you the most recent 15 lines and then monitors for new additions.  You should run that while you're deploying to get more detailed info as it happens.  The other option is to run something like mup logs -n 300 to get the last 300 lines in the logs.  It won't keep updating live with new logs, but it gets more of the history (what you pasted in your last message doesn't really give a lot of detail).

Thank jshimko, below is my mup.json:
{
// Server authentication info
"servers": [
{
"host": "<IP_ADDRESS>",
"username": "ubuntu",
//"password": "password"
// or pem file (ssh based authentication)
"pem": "/home/thangdx/Downloads/dxt040907.pem"
}
],
// Install MongoDB in the server, does not destroy local MongoDB on future setup
"setupMongo": false,
// WARNING: Node.js is required! Only skip if you already have Node.js installed on server.
"setupNode": true,
// WARNING: If nodeVersion omitted will setup 0.10.33 by default. Do not use v, only version number.
"nodeVersion": "0.10.35",
// Install PhantomJS in the server
"setupPhantom": true,
// Application name (No spaces)
"appName": "Tele_VDDA",
// Location of app (local directory)
"app": "/home/thangdx/DeployedApp/VDDA",
// Configure environment
"env": {
"ROOT_URL": "http://qlda.org",
"MONGO_URL": "mongodb://thang:thang123456@dogen.mongohq.com:10050/qlda_telescope"
},
// Meteor Up checks if the app comes online just after the deployment
// before mup checks that, it will wait for no. of seconds configured below
"deployCheckWaitTime": 600
}

Assuming your info is all correct, that looks right.  I use pretty much the same setup and it works fine for me.  There has to be a small detail you're missing somewhere.
Sorry, I don't know what else to recommend at this point other than to make sure you're credentials and URL's are correct.

Yes, jshimko. I must do something wrong, I will double check every-steps and find out. Thank you very much.

SUCCESS! after recreating database. Thank you guys for helps.

:+1:

Hi Gentlemen, I am attempting to deploy Meteor/Telescope (DigitalOcean + Compose.io) but no success. I received the following error message a few seconds ago. Would you have any recommendations? Eric

Pretty sure Meteor requires Node 0.10.3x right now. Looks like you're using the current stable (0.12.0). Try changing your mup config and starting over with a fresh server.

SUCCESS!!! Shout out to jshimko!

:+1:

I have the same problem as you guys had. Could somebody help me out ?
[<IP_ADDRESS>] ✘ Invoking deployment process: FAILED
-----------------------------------STDERR-----------------------------------
p ERR! cwd /opt/comicsprout/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt
gyp ERR! node -v v0.12.2
gyp ERR! node-gyp -v v1.0.3
gyp ERR! not ok
npm WARN package.json<EMAIL_ADDRESS>No description
npm WARN package.json<EMAIL_ADDRESS>No repository field.
npm WARN package.json<EMAIL_ADDRESS>No README data
child_process: customFds option is deprecated, use stdio instead.
../src/coroutine.cc: In function ‘void* find_thread_id_key(void*)’:
../src/coroutine.cc:90:3: warning: ‘thread_id’ may be used uninitialized in this function [-Wmaybe-uninitialized]
   if (tls == thread_id) {
   ^
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (7) Failed to connect to localhost port 80: Connection refused
Latest deployment failed! Reverted back to the previous version.
-----------------------------------STDOUT-----------------------------------
rget) Release/obj.target/fibers.node: Finished
COPY Release/fibers.node
make: Leaving directory /opt/comicsprout/tmp/bundle/programs/server/node_modules/fibers/build' 	Installed in /opt/comicsprout/tmp/bundle/programs/server/node_modules/fibers/bin/linux-x64-v8-3.28/fibers.node`
<EMAIL_ADDRESS>node_modules/underscore
<EMAIL_ADDRESS>node_modules/eachline
└──<EMAIL_ADDRESS>
<EMAIL_ADDRESS>node_modules/chalk
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS>
<EMAIL_ADDRESS>node_modules/semver

<EMAIL_ADDRESS>node_modules/source-map-support
└──<EMAIL_ADDRESS><EMAIL_ADDRESS>
<EMAIL_ADDRESS>node_modules/fibers
Waiting for MongoDB to initialize. (5 minutes)
connected
comicsprout stop/waiting
comicsprout start/running, process 12827
Waiting for 30 seconds while app is booting up
Checking is app booted or not?
comicsprout stop/waiting
comicsprout start/running, process 12930

Please try node version 0.10.36 in your mup.json file, then run 'mup setup' again, and 'mup deploy'

I have it by default. The following is my mup.json :
{
// Server authentication info
"servers": [
{
"host": "myhost",
"username": "root",
//"password": "mypassword"
// or pem file (ssh based authentication)
"pem": "~/.ssh/id_rsa"
}
],
// Install MongoDB in the server, does not destroy local MongoDB on future setup
"setupMongo": false,
// WARNING: Node.js is required! Only skip if you already have Node.js installed on server.
"setupNode": true,
// WARNING: If nodeVersion omitted will setup 0.10.36 by default. Do not use v, only version number.
"nodeVersion": "0.10.36",
// Install PhantomJS in the server
"setupPhantom": true,
// Application name (No spaces)
"appName": "comicsprout",
// Location of app (local directory)
"app": "/Users/matejhlavacka/Meteor/Comic/",
// Configure environment
"env": {
"ROOT_URL": "http://comicsprout.com",
"MONGO_URL": "mongodb://username:userpassword@dogen.mongohq.com:10062/telescope-comic-sproute"
},
// Meteor Up checks if the app comes online just after the deployment
// before mup checks that, it will wait for no. of seconds configured below
"deployCheckWaitTime": 30
}

Now that you pointed that out, I realized I installed Node.js while setting up droplet in DigitalOcean. So it's already-preinstalled. Have to figure out the way how to undo that.

I would simply create a fresh droplet.
2015-04-13 2:46 GMT-07:00 Matej Hlavacka<EMAIL_ADDRESS>
Now that you pointed that out, I realized I installed Node.js while
setting up droplet in DigitalOcean. So it's already-preinstalled. Have to
figure out the way how to undo that.
—
Reply to this email directly or view it on GitHub
https://github.com/TelescopeJS/Telescope/issues/530#issuecomment-92294218
.

Yes, create a fresh Ubuntu 14.04 installation, with nothing pre-installed.

Thanks for advice, it's working now :+1:

No problem.
2015-04-16 0:55 GMT-07:00 Matej Hlavacka<EMAIL_ADDRESS>
Thanks for advice, it's working now [image: :+1:]
—
Reply to this email directly or view it on GitHub
https://github.com/TelescopeJS/Telescope/issues/530#issuecomment-93670231
.

Hello! I'm trying to Install Telescope app to Digital Ocean Server! Which Server Ubuntu need i to take for the I)nstallation? and which version of the Telescope App?
i get this back :
`Started TaskList: Deploy app 'MyTestApp' (linux)
[<IP_ADDRESS>] - Uploading bundle
[<IP_ADDRESS>] - Uploading bundle: SUCCESS
[<IP_ADDRESS>] - Setting up Environment Variables
[<IP_ADDRESS>] - Setting up Environment Variables: SUCCESS
[<IP_ADDRESS>] - Invoking deployment process
[<IP_ADDRESS>] x Invoking deployment process: FAILED
-----------------------------------STDERR-----------------------------------
npm WARN package.json<EMAIL_ADDRESS>No description
npm WARN package.json<EMAIL_ADDRESS>No repository field.
npm WARN package.json<EMAIL_ADDRESS>No README data
npm WARN cannot run in wd<EMAIL_ADDRESS>node npm-rebuild.js (wd=/opt/MyTestApp/tmp/bundle/programs/server)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (7) Failed to connect to localhost port 80: Connection refused
Latest deployment failed! Reverted back to the previous version.
-----------------------------------STDOUT-----------------------------------
<EMAIL_ADDRESS>node_modules/ansi-regex
<EMAIL_ADDRESS>node_modules/ansi-styles

<EMAIL_ADDRESS>node_modules/chalk

<EMAIL_ADDRESS>node_modules/escape-string-regexp

<EMAIL_ADDRESS>node_modules/has-ansi

<EMAIL_ADDRESS>node_modules/strip-ansi

<EMAIL_ADDRESS>node_modules/supports-color

<EMAIL_ADDRESS>node_modules/eachline

<EMAIL_ADDRESS>node_modules/type-of

<EMAIL_ADDRESS>node_modules/amdefine

<EMAIL_ADDRESS>node_modules/asap

<EMAIL_ADDRESS>node_modules/underscore

<EMAIL_ADDRESS>node_modules/meteor-promise

<EMAIL_ADDRESS>node_modules/promise

<EMAIL_ADDRESS>node_modules/source-map-support

<EMAIL_ADDRESS>node_modules/semver

<EMAIL_ADDRESS>node_modules/source-map

<EMAIL_ADDRESS>node_modules/fibers
Waiting for MongoDB to initialize. (5 minutes)
connected
MyTestApp stop/waiting
MyTestApp start/running, process 1690
Waiting for 30 seconds while app is booting up
Checking is app booted or not?
MyTestApp stop/waiting
MyTestApp start/running, process 1794
----------------------------------------------------------------------------

Space-Odysseys-Mac-Pro:MyTestApp cyberspace$
and my mup setup set file is here :
`{
// Server authentication info
"servers": [
{
"host": "<IP_ADDRESS>",
"username": "root",
"password": "Password",
// or pem file (ssh based authentication)
// WARNING: Keys protected by a passphrase are not supported
//"pem": "~/.ssh/id_rsa"
// Also, for non-standard ssh port use this
//"sshOptions": { "port" : 49154 },
// server specific environment variables
"env": {}
}
],
// Install MongoDB on the server. Does not destroy the local MongoDB on future setups
"setupMongo": false,
// Application name (no spaces).
"appName": "MyTestApp",
// Install PhantomJS in the server

"setupPhantom": true,
// Location of app (local directory). This can reference '~' as the users home directory.
// i.e., "app": "~/Meteor/my-app",
// This is the same as the line below.
"app": ".",
// Configure environment
// ROOT_URL must be set to your correct domain (https or http)
"env": {
"PORT": 80,
"ROOT_URL": "http://www.MyTestApp.com",
"MONGO_URL": "mongodb://MyTestApp:password@aws-us-east-1-portal.18.dblayer.com:12189,aws-us-east-1-portal.19.dblayer.com:11519/MyTestApp?ssl=true"
},
// Meteor Up checks if the app comes online just after the deployment.
// Before mup checks that, it will wait for the number of seconds configured below.
"deployCheckWaitTime": 30,
// show a progress bar while uploading.
// Make it false when you deploy using a CI box.
"enableUploadProgressBar": true
}
where is the problem att, therefor it was installed the sails.js ... maybe i need a fresh droplet from digital ocean.?
thanks for help!

Yes, I think a fresh droplet might work better. Although right now there's also some issues with Mup, so you could also try Heroku or Galaxy.


[stable/gocd] Adding agent.hostAliases (similar to server.hostAliases)

What this PR does / why we need it:
Adding hostAliases for agents.
Special notes for your reviewer:
server.hostAliases was added for server in #6724.
agent.hostAliases  are the same changes, but for agents.

/assign @varshavaradarajan

/lgtm /approve

/lgtm

/ok-to-test

Not sure how I should interpret it — it's merged, but tests failing (but afterwards)? No further changes needed?

@MPV -- The build is failing for bumping up the chart version, whereas it has already been taken care as part of the PR.
Ideally, it shouldn't have merged the PR with a pending/failed check.
@unguiculus -- can you provide some more information on the failure of the check and PR being merged without verifying the required check?

/retest

Sorry - that was probably me - I should have cancelled the /lgtm and ran the tests first - now it first got merged, then tested, and it conflicted with itself since it was already merged.

So no further action needed here?
Let me know and I'll remove my branch etc.


Is it possible to provide a Proc along with a if?

Is it possible to do something like this?
field(:user_name) { |user| user.name } , if: ->(_field_name, _user, _options) { user.active? }
From the docs, I can see that we can pass a Proc but not sure if we can pass it along with an if

Hi Bennet-Sunder,
Yes you can. You will need to add the if construct inside the field method and then create a block afterward.
The syntax will be something like this:
field(:user_name, if: ->(_field_name, user, _opts) { user.active? }) do |user, _options|
  user.name
end


How to get an AssetEntity or asset id from a file path

I am using https://github.com/KasemJaffer/receive_sharing_intent so a user can share a photo to my app. I get a SharedMediaFile object, this contains the file path -I would like to convert this to an AssetEntity so I can standardise my code for viewing photographs but I cannot find a way to do this?
Thank you

AssetEntity only represents existing assets in the device's gallery, which is readable and public for all apps, see https://github.com/fluttercandies/flutter_photo_manager#from-id. The only way to achieve this is to save the file from the path using saveImageWithPath to create a new entity.
Closing as it's not planned.

I also have a similar use case, where i tried the solution @AlexV525 you suggested and it is working perfectly fine, but it just creates an duplicate file in the device, which can be a issue, as some users can select larger files.
If we could have a way to fetch the assetEntity  based on the asset path, that would make more sense in this particular case scenario.
It will be very useful if it can be supported by the plugin.
Thankyou!


Added more clarity to units

Thought elaborating on the units might help a new front-end user a little more, especially since the superconducting literature is split between linear and angular units.

Stated this package assumes planks constant $h = 1$
Everything is in linear freq
Gave a few examples

Let me know if I got anything wrong and I'll update it! Thanks again for maintaining such a useful package!

Hi @clarkmiyamoto - awesome to get your contribution here, thank you! I'd like to ask @petergthatsme for input before merging, as he is the origin of all units choices and functionality in scqubits.
I'd like to inject my own opinion on two points:

The statement that literature usually specifies EC/(2pi) etc. is confusing to me.
Saying that "we assume h=1" may not fully capture what's going on - at least it leaves room for confusion what that would imply for how to specify temperature/thermal energies k_B T. (As a separate aside, working in units where h=1 is not an assumption but a choice; we "set" h=1 is more appropriate than "assume".)

@petergthatsme: looking forward to your lead on this, and thanks @clarkmiyamoto for your patience as we discuss this. You picked an important point, and clarity on that is crucial!

No worries, thanks for getting back so quickly!

Ah I meant to expose how $E_C / 2 \pi, E_J / 2\pi, \alpha / 2\pi$, etc. in literature usually implies linear frequency. But honestly, that notation also confuses me hahah.
Ah sorry for the sloppy language, yes "set" is more appropriate. And as for thermal energies, I haven't had to work w/ those so I'll let someone else write about that.

I'll wait for Peter's feedback then make edits.

Thanks for for your pull request @clarkmiyamoto and my apologies for such a slow response.
Regarding items above:

Maybe as Jens suggests, you can get rid of the $E_C/2\pi$, etc. comment (I do know what you're saying, but in case it's confusing to some).
yeah, saying "we set h=1" seems fine to me... I think users pass temperatures in Kelvin to various methods, so k_B T is not something they have to calculate explicitly themselves.

Anyway, if you don't mind, please make the changes above, and we can merge.
Thank you again for your input and help with your pull request!

Hi @jkochNU @petergthatsme, apologies for the slow response time. I just started grad school and haven't been coding as much! I just made a push w/ your feedback. Let me know if you folks have any other comments/concerns.


fragment not recognised, or get message never used :)

Im dumping log here, will write more details later
/Users/mpth/Git/snip/web/src/common/fragments/cook-book-user.graphql
  1:2  error  [NoUnusedFragments] Fragment "CookBookUser" is never used  @graphql-eslint/validate-against-schema

/Users/mpth/Git/snip/web/src/common/fragments/cook-book.graphql
  1:2   error    [NoUnusedFragments] Fragment "CookBook" is never used                                                             @graphql-eslint/validate-against-schema
  1:31  warning  Field "id" must be selected when it's available on a type. Please make sure to include it in your selection set!  @graphql-eslint/require-id-when-available
  3:10  warning  Field "id" must be selected when it's available on a type. Please make sure to include it in your selection set!  @graphql-eslint/require-id-when-available
  4:13  error    [KnownFragmentNames] Unknown fragment "CookBookUser"

So one file its saying not used, then the other is complaining. I added my schema and all operations to the eslint config. Hopefully correct will debug more tomorrow

2 different issue. see:

https://github.com/dotansimha/graphql-eslint/issues/219
https://github.com/dotansimha/graphql-eslint/issues/89


ZeroDivisionError when using class_mode=None with ImageDataGenerator.flow_from_directory()

Here's the script to run to see the exception. One can run it like python imggen_reproduce.py /tmp/somedir_that_you_donot_care_about. After a quick glance at the source, it seems like class_mode is not used in the DirectoryIterator constructor to prevent self.nb_sample from being set to 0, which ultimately becomes self.n in the base Iterator.
Some reporters of a previous bug (#4699) have reported that this "works" when you create an additional directory under the directory passed to flow_from_directory(). However, I don't think this is ideal, for semantically, there is no class/label when dealing with test images.
My proposal to fix this is to set self.nb_sample = number of valid image files in the input directory when self.class_mode is None and not self.classes, in DirectoryIterator::__init__. The second clause in the condition will help prevent breakage of code that has hacked its way around this issue by creating an additional directory (or we don't have to be afraid of breaking, it's up to you). Please let me know if you are okay with this, and if you have any ideas (including calling this issue a non-issue :)), and I can accordingly prepare a quick PR (or not).

Just wanted to say that I also found this behavior confusing. I'm attempting to use DirectoryIterator.flow_from_directory on a directory containing test images (not labeled) which I want to pass to predict_generator. I had to put all my images in an arbitrarily named folder in order to use the function.


WIP: Feature/composition

Missing type checking
Requires serialization to be merged.

Closes Issue https://github.com/jmmartinez/easy-just-in-time/issues/2


Calico is breaking routes after datastore lost

I am not sure if this is error in configuration or just default behavior of Calico node but when Calico is not able to connect to datastore (which for me is kubernetes) is changing already available routes to incorrect one (is switching all routes from tunl0 to ens3).
With this behavior all pods are losing possibility to connect each other. According to me all settings shouldn't be changed so at least what is working will still work.
Calico version  v3.3.0
Kubernetes v1.11.7
Ubuntu Xenial
Step to reproduce:

turn off all kubernetes masters

When masters up:
default via <IP_ADDRESS> dev ens3
<IP_ADDRESS>/24 via <IP_ADDRESS> dev tunl0  proto bird onlink
<IP_ADDRESS>/24 via <IP_ADDRESS> dev tunl0  proto bird onlink
blackhole <IP_ADDRESS>/24  proto bird
<IP_ADDRESS> dev cali748e9b88830  scope link
<IP_ADDRESS> dev caliafdf243cde7  scope link
<IP_ADDRESS> via <IP_ADDRESS> dev ens3
<IP_ADDRESS>/16 dev docker0  proto kernel  scope link  src <IP_ADDRESS> linkdown
<IP_ADDRESS>/24 dev ens3  proto kernel  scope link  src <IP_ADDRESS>
When masters down:
default via <IP_ADDRESS> dev ens3
<IP_ADDRESS>/24 via <IP_ADDRESS> dev ens3  proto bird
<IP_ADDRESS>/24 via <IP_ADDRESS> dev ens3  proto bird
blackhole <IP_ADDRESS>/24  proto bird
<IP_ADDRESS> dev cali748e9b88830  scope link
<IP_ADDRESS> dev caliafdf243cde7  scope link
<IP_ADDRESS> via <IP_ADDRESS> dev ens3
<IP_ADDRESS>/16 dev docker0  proto kernel  scope link  src <IP_ADDRESS> linkdown
<IP_ADDRESS>/24 dev ens3  proto kernel  scope link  src <IP_ADDRESS>

@bartlomiejsawicki Could you clarify if this is what you're seeing after the installation (without any changes to master or any node) or if this only happens when you 'turn off' the master? Are you seeing if any pods are restarting or unhealthy?
I'd expect lots of things to go wrong if the datastore is not reachable, are you trying to test a specific scenario with this test?

This is situation during HA test. One of scenario is to turn off all masters and check if application is still working. It was ok when CALICO_IPV4POOL_IPIP was set to OFF(so without IPIP) test was successful.
When changed to default which is ALWAYS (IPIP enabled) stopping masters is causing routes to be changed. As soon as masters are back, routes are correct again.
It would be nice to prevent somehow updates of the routes when no datastore. It is better to not touch than break when no information about cluster state.

Ah, I think I know this one. I suspect you're hitting an issue that was fixed by this PR: https://github.com/projectcalico/libcalico-go/pull/1057
It seems to have be present in v3.5.5 and later. Could you try a newer release and let us know if that fixes your issue?

Thank you, after upgrading to 3.9.0 there is no problem.


BACKLOG-8206 hide fields implementation and descriptions for JsonInput

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dpentaho.resolve.repo=http://ivy-nexus.pentaho.org/content/groups/approved -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -Dpentaho.resolve.repo=http://ivy-nexus.pentaho.org/content/groups/approved -Dtestreports.dir=bin/reports/integration-test -f engine/build.xml jacoco-integration checkstyle publish-local
ant -Dpentaho.resolve.repo=http://ivy-nexus.pentaho.org/content/groups/approved -Dtestreports.dir=bin/reports/unit-test -f plugins/kettle-json-plugin/build.xml clean-all resolve jacoco && ant -Dpentaho.resolve.repo=http://ivy-nexus.pentaho.org/content/groups/approved -Dtestreports.dir=bin/reports/integration-test -f plugins/kettle-json-plugin/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/core/injection/InjectionSupported.java
  engine/src/org/pentaho/di/core/injection/bean/BeanInjectionInfo.java
  engine/test-src/org/pentaho/di/core/injection/MetaBeanLevel1.java
  plugins/kettle-json-plugin/src/org/pentaho/di/trans/steps/jsoninput/JsonInputMeta.java
  plugins/kettle-json-plugin/src/org/pentaho/di/trans/steps/jsoninput/messages/messages_en_US.properties

Newly Broken Tests:
org.pentaho.di.trans.steps.jsoninput.JsonInputMetaInjectionTest.test:
:red_circle: org.pentaho.di.core.exception.KettleException
org.pentaho.di.core.exception.KettleException:
Property 'ACCEPT_FILE_NAMES' not found for injection to class org.pentaho.di.trans.steps.jsoninput.JsonInputMeta

	at org.pentaho.di.core.injection.bean.BeanInjector.setProperty(BeanInjector.java:96)
	at org.pentaho.di.core.injection.BaseMetadataInjectionTest.check(BaseMetadataInjectionTest.java:91)
	at org.pentaho.di.trans.steps.jsoninput.JsonInputMetaInjectionTest.test(JsonInputMetaInjectionTest.java:96)

:red_circle: junit.framework.AssertionFailedError
junit.framework.AssertionFailedError: Some properties where not tested: [FILE_REQUIRED, FILE_SIZE_FIELDNAME, SOURCE_FIELD_IS_FILENAME, SOURCE_IN_FIELD, INCLUDE_SUBFOLDERS, FILE_EXTENSION_FIELDNAME, FIELD_NAME, FIELD_TRIM_TYPE, FILENAME, FIELD_GROUP, FILE_LAST_MODIFICATION_FIELDNAME, FIELD_PRECISION, SOURCE_FIELD_NAME, FIELD_FORMAT, FIELD_REPEAT, FILE_HIDDEN_FIELDNAME, FIELD_PATH, FIELD_LENGTH, FIELD_DECIMAL, FILE_URI_FIELDNAME, FILE_ROOT_URI_FIELDNAME, FIELD_TYPE, FILEMASK, FILE_SHORT_FILE_FIELD

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.core.auth.core.impl.DefaultAuthenticationConsumerFactory

Branch Change: -7.14%:small_red_triangle_down:
Complexity Change: -7.69%:small_red_triangle_down:

org.pentaho.di.core.injection.bean.BeanInjectionInfo

Branch Change:  + 3.61%
Complexity Change:  + 2.81%
Instruction Change:  + 1.45%
Line Change:  + .75%

org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change:  + .78%
Complexity Change:  + 1.03%
Instruction Change:  + .16%

org.pentaho.di.job.entries.evaluatetablecontent.JobEntryEvalTableContent

Branch Change:  + 2.02%
Complexity Change:  + 2.13%
Instruction Change:  + .34%

org.pentaho.di.job.entries.getpop.MailConnectionMeta

Branch Change:  + 1.00%
Complexity Change:  + 1.41%
Instruction Change:  + .30%

org.pentaho.di.job.entries.sql.JobEntrySQL

Instruction Change:  + 3.28%
Line Change:  + 3.87%

org.pentaho.di.job.entries.waitforsql.JobEntryWaitForSQL

Branch Change: -.66%:small_red_triangle_down:
Complexity Change: -.93%:small_red_triangle_down:
Instruction Change: -.13%:small_red_triangle_down:

org.pentaho.di.trans.step.StepMeta

Instruction Change:  + .19%
Line Change:  + .27%

org.pentaho.di.trans.steps.checksum.CheckSumMeta

Branch Change:  + 1.32%
Complexity Change:  + 1.43%
Instruction Change:  + .33%
Line Change:  + .54%

org.pentaho.di.trans.steps.combinationlookup.CombinationLookupMeta

Instruction Change: -.04%:small_red_triangle_down:

org.pentaho.di.trans.steps.constant.ConstantMeta

Instruction Change:  + .10%

org.pentaho.di.trans.steps.csvinput.CsvInputMeta

Instruction Change: -.05%:small_red_triangle_down:

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Instruction Change: -.09%:small_red_triangle_down:

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Branch Change: -.66%:small_red_triangle_down:
Complexity Change: -.41%:small_red_triangle_down:
Instruction Change: -.50%:small_red_triangle_down:
Line Change: -.24%:small_red_triangle_down:

org.pentaho.di.trans.steps.ifnull.IfNullMeta

Branch Change:  + 2.00%
Complexity Change:  + 1.89%
Instruction Change:  + .17%

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change: -1.18%:small_red_triangle_down:
Complexity Change: -1.35%:small_red_triangle_down:

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change:  + .07%

org.pentaho.di.trans.steps.sortedmerge.SortedMergeMeta

Instruction Change:  + .18%

org.pentaho.di.trans.steps.symmetriccrypto.symmetriccryptotrans.SymmetricCryptoTransMeta

Branch Change: -3.33%:small_red_triangle_down:
Complexity Change: -1.85%:small_red_triangle_down:
Instruction Change: -.28%:small_red_triangle_down:

org.pentaho.di.trans.steps.synchronizeaftermerge.SynchronizeAfterMergeMeta

Instruction Change:  + .04%

Integration test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.core.injection.bean.BeanInjectionInfo

Branch Change:  + 1.67%
Complexity Change: -2.30%:small_red_triangle_down:
Instruction Change:  + 1.05%
Line Change: -.36%:small_red_triangle_down:

License header violations

:heavy_exclamation_mark: Copyright year is not the current year on engine/src/org/pentaho/di/core/injection/InjectionSupported.java. Found 2015. Was expecting 2016

:heavy_exclamation_mark: Copyright year is not the current year on engine/test-src/org/pentaho/di/core/injection/MetaBeanLevel1.java. Found 2015. Was expecting 2016

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dpentaho.resolve.repo=http://ivy-nexus.pentaho.org/content/groups/approved -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -Dpentaho.resolve.repo=http://ivy-nexus.pentaho.org/content/groups/approved -Dtestreports.dir=bin/reports/integration-test -f engine/build.xml jacoco-integration checkstyle publish-local
ant -Dpentaho.resolve.repo=http://ivy-nexus.pentaho.org/content/groups/approved -Dtestreports.dir=bin/reports/unit-test -f plugins/kettle-json-plugin/build.xml clean-all resolve jacoco && ant -Dpentaho.resolve.repo=http://ivy-nexus.pentaho.org/content/groups/approved -Dtestreports.dir=bin/reports/integration-test -f plugins/kettle-json-plugin/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/core/injection/InjectionSupported.java
  engine/src/org/pentaho/di/core/injection/bean/BeanInjectionInfo.java
  engine/test-src/org/pentaho/di/core/injection/MetaBeanLevel1.java
  plugins/kettle-json-plugin/src/org/pentaho/di/trans/steps/jsoninput/JsonInputMeta.java
  plugins/kettle-json-plugin/src/org/pentaho/di/trans/steps/jsoninput/messages/messages_en_US.properties
  plugins/kettle-json-plugin/test-src/org/pentaho/di/trans/steps/jsoninput/JsonInputMetaInjectionTest.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.core.injection.bean.BeanInjectionInfo

Branch Change:  + 3.61%
Complexity Change:  + 2.81%
Instruction Change:  + 1.45%
Line Change:  + .75%

org.pentaho.di.job.entries.evaluatetablecontent.JobEntryEvalTableContent

Branch Change: -1.01%:small_red_triangle_down:
Complexity Change: -1.06%:small_red_triangle_down:
Instruction Change: -.17%:small_red_triangle_down:

org.pentaho.di.repository.kdr.KettleDatabaseRepositoryCreationHelper

Branch Change: -1.64%:small_red_triangle_down:
Complexity Change: -.69%:small_red_triangle_down:
Instruction Change: -2.43%:small_red_triangle_down:
Line Change: -3.70%:small_red_triangle_down:

org.pentaho.di.trans.steps.calculator.CalculatorMetaFunction

Branch Change: -8.70%:small_red_triangle_down:
Complexity Change: -3.08%:small_red_triangle_down:
Instruction Change: -.74%:small_red_triangle_down:
Line Change: -.90%:small_red_triangle_down:

org.pentaho.di.trans.steps.checksum.CheckSumMeta

Branch Change:  + 1.32%
Complexity Change:  + 1.43%
Instruction Change:  + .33%
Line Change:  + .54%

org.pentaho.di.trans.steps.constant.ConstantMeta

Instruction Change: -.10%:small_red_triangle_down:

org.pentaho.di.trans.steps.csvinput.CsvInputMeta

Instruction Change: -.05%:small_red_triangle_down:

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Instruction Change: -.09%:small_red_triangle_down:

org.pentaho.di.trans.steps.dbproc.DBProcMeta

Instruction Change: -.11%:small_red_triangle_down:

org.pentaho.di.trans.steps.excelwriter.ExcelWriterStepMeta

Branch Change:  + 1.28%
Complexity Change:  + .78%
Instruction Change:  + .08%

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change:  + 1.04%
Complexity Change:  + 1.05%
Instruction Change:  + .14%
Line Change:  + .37%

org.pentaho.di.trans.steps.ifnull.IfNullMeta

Branch Change: -2.00%:small_red_triangle_down:
Complexity Change: -1.89%:small_red_triangle_down:
Instruction Change: -.17%:small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change:  + 3.53%
Complexity Change:  + 4.05%
Instruction Change:  + .35%
Line Change:  + .97%

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Instruction Change: -.08%:small_red_triangle_down:

org.pentaho.di.trans.steps.setvalueconstant.SetValueConstantMeta

Instruction Change: -.14%:small_red_triangle_down:

org.pentaho.di.trans.steps.sortedmerge.SortedMergeMeta

Instruction Change: -.18%:small_red_triangle_down:

org.pentaho.di.trans.steps.symmetriccrypto.symmetriccryptotrans.SymmetricCryptoTransMeta

Branch Change:  + 3.33%
Complexity Change:  + 1.85%
Instruction Change:  + .28%

org.pentaho.di.trans.steps.synchronizeaftermerge.SynchronizeAfterMergeMeta

Instruction Change: -.04%:small_red_triangle_down:

org.pentaho.di.trans.steps.systemdata.SystemDataMeta

Branch Change:  + 2.04%
Complexity Change:  + 2.04%
Instruction Change:  + .32%
Line Change:  + .81%

org.pentaho.di.trans.steps.tableoutput.TableOutputMeta

Branch Change: -.91%:small_red_triangle_down:
Complexity Change: -.82%:small_red_triangle_down:

org.pentaho.di.trans.steps.uniquerows.UniqueRowsMeta

Instruction Change: -.18%:small_red_triangle_down:

org.pentaho.di.trans.steps.webservices.WebServiceMeta

Branch Change:  + 1.79%
Complexity Change:  + 1.19%
Instruction Change:  + .07%

Integration test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.core.injection.bean.BeanInjectionInfo

Branch Change:  + 1.67%
Complexity Change: -2.30%:small_red_triangle_down:
Instruction Change:  + 1.05%
Line Change: -.36%:small_red_triangle_down:

org.pentaho.di.trans.step.BaseStep

Branch Change:  + .29%
Complexity Change:  + .18%
Instruction Change:  + .05%
Line Change:  + .08%


Some questions about validation

We want to test the model on the validation set in 'calculte_validation_accuracy' function.  But we has been trained 5 epochs, it's still not into the validation stage. How can we quickly validate the model?

Hey Yang,
Validation on the target set is enabled only at the last scale (e.g. n=N), because till this stage we do not handle full resolution images. If you wish the code to validate please train the model up to the last scale.
Additionally, you can change the behavior of the code to support such a feature. I assume that the files that needs to to be changed are core/training.py and  data_handlers/cityscapes_dataset.py.
Shahaf.

How many scales are there?

3 total. It is configurable of course.


Toggle Mottagnings-mode (alternative verification)

Add functionality that when active:

[ ] disables the /verify begin <kth-email> and /verify submit <verification-code> commands
[ ] adds a /verify nØllan <nØllegrupp_code> which verifies the user, and adds
(a) the årskursroll for nØllan,
(b) the nØllegruppsroll corresponding to  <nØllegrupp_code>,
(c) the @Datasektionen roll, and
(d) gives the user access to course channels of their current period.

Note: this issue is high priority and should be implemented asap.

Seems to correctly enable and disable commands on branch feat/mottagnings-mode now. Behavior of the commands needs to be verified though. Not sure if we assign a nollan role yet, if that's a requirement?

Further requirements for toggle (from @lucubrator):

[x] Mottagningsmode feedback should not be ephemeral
[ ] Create subcommand that returns current mode/state [i.e. mottagningsmode get]
[ ] Add 'True'/'False' parametrar [i.e. mottagningsmode set]


Get rid of PostCSS warnings during build process

I've been getting this warning message while compiling Heml files into HTML:
Without "from" option PostCSS could generate wrong source map and will not find Browserslist config. Set it to CSS file path or to "undefined" to prevent this warning.
I tried upgrading PostCSS version but the warning still exists. It's not harmful but it'll be nice to figure out how to get rid of it. I'm using Yarn for the build script.
Thanks a lot!

Hi,
This also happens for me using HEML build cli.


  I got them cleared out using weave reset and
eval $(weave env --restore)
if I launch a scope container without weave running, I can get to the scope GUI, but of course that's worthless.  If I then start weave, nothing updates in the scope GUI to reflect that.  If, after I've started weave, I scope stop and then scope launch  I get:

Everybody's pal 404.
Thoughts?

A development!
When I kill one of the sigproxies, suddenly I can access scope again instead of a 404, thus:
https://gist.github.com/faddat/006797a9a4d6639681aa
When I then try to hit weave I get a:

Hi Jacob; could you please send the output of docker -v, weave version and docker images | grep scope
Also could you please put the result of docker logs weavescope in a gist?

Hi Jacob; any chance reproducing this?  I think this is the same cause as #608 (weave not achieving quorum), so I'm going to close as dupe.


spirv-fuzz: TransformationAddBitInstructionSynonym should check integer signedness

TransformationAddBitInstructionSynonym introduces synonyms to bit instructions (e.g. OpBitwiseOr) by extracting all bits from the operands of those binary instructions and performing the binary operation on them manually. It uses OpBitFieldUExtract to extract bits and OpBitFieldInsert to insert them back into the constant. Those two instructions require some of their operands to have the same signedness. However, common bit instructions the transformation can be applied to (e.g. OpBitwiseOr) have no such requirement. Thus, it is possible to end up with the following error when the transformation is applied.
Expected Base Type to be equal to Result Type: BitFieldUExtract
  %964 = OpBitFieldUExtract %uint %int_n1 %uint_0 %uint_1

@afd This might be a good first issue.

@Vasniktel Could you do a PR that adds a disabled test that should pass but fails due to this issue? I.e., a transformation that should be inapplicable but that is currently applicable due to this? If you could add comments to the test explaining why it should pass then that would give whoever takes this issue a good starting point.

To those who will work on this issue, I've added a disabled test in #4180 that crashes because of this bug.

Thinking about extending spirv-fuzz to OpenCL kernels, this check should be performed only for shaders, since OpenCL kernels have no signedness semantics (the signedness in OpTypeInt should always be 0).

I think I've understood the transformation and currently working on this issue. Sorry for late :)
@afd, @Vasniktel ping.
after check test in #4180 I think  %39 = OpNot %200 %5 ; bit instruction  fails because %200 is OpTypeInt and %5 is OpConstant and when changed one of them to be like another it pass. So, Do you want to check if it is not the same type ignore it, and look for the next instruction? @Vasniktel!

I have found some opcodes needed to support in the futures  OpShiftRightLogical, OpShiftRightArithmetic, OpShiftLeftLogical, OpBitReverse, OpBitCount.
Also some TODOs e.g. #3792, #3791
Are you want to consider it as new cases for support? to enhance the transformation.
@afd, @Vasniktel  ping.

I'm not sure about adding support for more instructions - might be a good idea. This issue is not about that, though.
In SPIR-V each integer type can either be signed or unsigned. Usually, instructions don't care about the signedness. For example, OpNot instruction, which negates all of the bits of an integer and is equivalent to ~ operator in C, can have its operand signed as well as unsigned. Additionally, the result type doesn't have to match with the argument. Thus, the result can be signed and the operand can be unsigned.
There are some instructions that have restrictions on signedness. For example, OpBitFieldSExtract, OpBitFieldUExtract and OpBitFieldInsert have a restriction that the result type and one of the operand types must be equal (i.e. either both signed or unsigned - https://www.khronos.org/registry/spir-v/specs/unified1/SPIRV.html#OpBitFieldSExtract). This restriction is what we need to fix. As a solution, you could:

Check in the IsApplicable that the operands of the bitwise instruction have the same signedness. If not - return false.
Make sure that the fuzzer never applies a transformation to a bitwise instruction with differently signed operands.

Thanks, @Vasniktel for the clarification.  Regarding the solution I have read its specification, I think that I've thought about and applied some of it, also I will check the second point, thanks for your suggestion.


feat(sandbox): add checkbox for translatable property

What?
Added new checkbox 'Translatable' to easily develop by being able to turn on and off the functionality. This PR includes the following changes:

Adding a new checkbox to manipulate the translatable property
Renaming the Options title of a section to Settings
Reflecting changes of translatable and storyLang inside the code block

Why?
JIRA: EXT-2240

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

Current dependencies on/for this PR:

#361  👈
#360
main

This stack of pull requests is managed by Graphite.

I just realized that this PR should not have been stacked. We will need to release a new version of field-plugin library and then redeploy the sandbox.

@BibiSebi anything else you need me to review about this PR? :)

@eunjae-lee no, this is just blocked by the field plugin release which is blocked by the storyfront release :D


Add alerting and notification to manifests

Description
Add alerting and notification to manifests
Issues Resolved
N/A
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #3214 (ce96114) into main (57936ae) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main    #3214   +/-   ##
=======================================
  Coverage   92.90%   92.90%
=======================================
  Files         167      167
  Lines        4622     4622
=======================================
  Hits         4294     4294
  Misses        328      328

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Maybe get rid of braces in the object construction syntax

Currently we have (taken from runtime.007):
ast = new Q::CompUnit {
    block: new Q::Block {
        parameterlist: new Q::ParameterList {},
        statementlist: new Q::StatementList {
            statements: []
        }
    }
};

Suggesting to use this instead:
ast = new Q::CompUnit(
    new Q::Block(
        new Q::ParameterList(),
        new Q::StatementList([])
    )
);

That is, object construction ends up being just positional parameters in a call-like syntax after the new keyword (like in Java).
I'm suggesting this because with the help of #299, the biggest reason for having the block syntax in the first place (like C#) — being able to specify object properties by name — goes away.

It strikes me that this issue is better tackled after dict has been separated out of object, as in #184.

Which it has now, after #470.


Port autogen sample from agentic cook book

Create a sample reproducing the travel agency work here: https://github.com/microsoft/agenticcookbook
Let's use the autogen-agentchat API for this.

@ekzhu I can take this one, can you please assign it to me?


fix: updating handling of a new service with the old one

Hi @marcopiraccini
in this PR I will handling the case of

adding a new service to an existing application with/without a plugin

and the result is the following
https://github.com/platformatic/meraki/assets/25035977/ad218c59-3719-446e-8536-6679cbe74103

https://www.loom.com/share/6fea4542564f4d749e766e185c600793
https://www.loom.com/share/e85648d530074722b5cce3b63cf297c3


[BUG] - dex is not playing anything

Dex is adding music to the queue on request but never playing anything.

I would like to work on this.

Assigned!
You can start now.

Thanks! 😇


Can't compile

I'm trying to compile code but got error: ESP.h no such file or directory.
I've installed all recommended libraries and board. I've tried with board:

ESP32 Dev Module
LOLIN D32

and result is the same.
Arduino: 1.8.13 plaftorm: linux
Any ideas?

Can you check your Arduino folder? The  ESP.h file on my system (macos) is located here ~Documents/Arduino/hardware/espressif/esp32/cores/esp32
and the projects folders location is: ~Documents/Arduino/projects

I've managed to compile. It's looks that ESP32 libraries are not ready for linux environment where capital letters in file names does matter. I've do make a lot of symlinks like:
ESP.h -> Esp.h
WifiClient.h -> WiFiClient.h
WiFiUDP.h -> WiFiUdp.h
ledblink.H -> ledblink.h
wificonnect.H -> wificonnect.h etc
Generally: esp32-common library and espressif esp32 arduino package is NOT Linux friendly and require a lot of polishing.

Thanks for sharing with me. I will fix the file name issues.


Update existing json data with Survey Results data

Overview of the Pull Request:
Updated existing json data with Survey Results data.
Out of scope

any change required for the components as the result of data update;

How Has This Been Tested?
Feel free to compare to https://docs.google.com/spreadsheets/d/1haLfKR2pTJQQ9g1M--FrGoSHE6RN8NERwZ3vV5WH-ZY/edit#gid=0
Pull Request Checklist:
Make sure the following checkboxes[ ] are checked with x before sending your PR -- thank you!
~- [ ] Have you included a link Trello card / Github issue and written sufficient description to help others review your work?~

[x] Is your pull request up-to-date with main branch?
[x] Have you checked That code is well formatted? Did npx prettier --check . return no warnings/errors?
[x] Have you written instructions on how to test that your changes work as expected?
[x] Have you tested your work thoroughly on your local machine to ensure you are not breaking anything?

Excellent job on the data crunching/aggregation work @OlaShabalina !
Since I'm not as across the formulas and calculations used, it'd be nice to get @oonamcmanus 's feedback on this too, just to make sure the numbers look kosher 👍🏽
A couple of other minor points to suggest:

should we try to keep all our results rounded to 2 significant decimal places? (e.g, 1.23, 10.42, etc). Most of the results in the JSON file already are, but there are some that aren't (e.g:

Excellent job on the data crunching/aggregation work @OlaShabalina !
Since I'm not as across the formulas and calculations used, it'd be nice to get @oonamcmanus 's feedback on this too, just to make sure the numbers look kosher 👍🏽
A couple of other minor points to suggest:

should we try to keep all our results rounded to 2 significant decimal places? (e.g, 1.23, 10.042, etc). Most of the results in the JSON file already are, but there are some that aren't (e.g: total-co2-emissions-tonnes, Trip Count["Emission"]["Count"])
The average trip distance & emission calculations in the 'Overview' section need to be rounded to 2 significant decimal places; that's a code change here and here. Were you thinking of making this change in this PR, or a separate PR Olga?

hey @hqtan , this is not the data, this is the formula in that component, once the data is updated we will need to fix that in the component itself.

Hi @OlaShabalina 👋🏽 ,
You're spot on re the Trip Count["Emission"] results 👍🏽
Only one of them need to be rounded to 2 significant decimal places (the emissions count for car). I've highlighted that in the above code snippets.
Re the average trip distance & emission calculations, that is indeed done in the results page itself, so there will need to be some changes to the relevant lines of code to round the averages to 2 significant decimal places. We can make that change on a separate PR 👍🏽
I think this will be ready to merge once the value of Trip Count["Emission"] for car has been rounded 👍🏽

Hi @hqtan,
Accepted your changes.
Apologies, I did't round it initially because I personally prefer to have consistency within the numbers (when all numbers within the graph are rounded to the same decimal point). But it's just me ;-)


💥 Change the shape of the output DataFrame of extract_dataframe

extract_dataframe used to return N rows for each neuron where N is the
number of neurite types in the input config.
per neuron.
Since extract_dataframe input is a list of neuron, it is more natural to
return exactly one row per neuron.
Use a MultiIndex on the columns to hold the metrics for each neurite type
instead of having the neurite type appear in the index (axis=0).
Before:

name
neurite_type
metric A
metric B

0
no-axon
axon
val A
val B

1
no-axon
apical_dendrite
val A'
val B'

After:

neuron
axon
apical_dendrite

name
metric A
metric B
metric A
metric B

0
no-axon
val A
val B
val A'
val B'

Ping @arnaudon @adrien-berchet since you are the only actual users of extract_dataframe

Ping @arnaudon @adrien-berchet since you are the only actual users of extract_dataframe

I am using it too.

I am using it too.

I was wondering why it was not a multiindex btw when using it.

I was wondering why it was not a multiindex btw when using it.

Looks good! That will make our life a bit easier indeed!

Looks good! That will make our life a bit easier indeed!

I agree, it looks a better format to me, should simplify things a bit.

I agree, it looks a better format to me, should simplify things a bit.

Oh. I did not know that this function was so popular :blush:

Oh. I did not know that this function was so popular :blush:

Looks good to me too :)
And it seems that Travis CI was also not disabled in this repository.

Looks good to me too :)
And it seems that Travis CI was also not disabled in this repository.

Lol the CI is actually not running tox. I'll fix that first.

Lol the CI is actually not running tox. I'll fix that first.

retest this please

retest this please


CB-10536. Add internal API to get usersync status

This is similar to my previous pull request. I identified one more API that we'll need to call internally.
See detailed description in the commit message.
An internal usersync status API is added to the FMS
to allow internal actors to retrieve status of usersync
operations.

run tests

run tests

Where are my manners. I forgot to say "please!"

Where are my manners. I forgot to say "please!"


There are no release versions. Please mark the current code with a release version

Support Requests should not be opened as issues and should be handled in the following ways:
On StackOverflow using the angular-tree-component tag
In our slack support channel at https://angular-tree-component.herokuapp.com/
We wanted to use the component but we saw that there are no release versions yet. Is it possible to mark the current code with a release version?

Done.


Disable "missing-fields" warning in Lua LSP by default

Hello,
I think it would be a great idea to extend lua_ls settings to ignore noisy warnings that are irrelevant for a beginner.
From:
    lua_ls = {
        Lua = {
            workspace = { checkThirdParty = false },
            telemetry = { enable = false },
        },
    },

To:
    lua_ls = {
        Lua = {
            workspace = { checkThirdParty = false },
            telemetry = { enable = false },
            diagnostics = {
                disable = { "missing-fields" },
            },
        },
    },

Reference: https://github.com/LuaLS/lua-language-server/wiki/Settings#diagnosticsdisable
I cannot see any template for suggestions, so I hope I won't be automatically dismissed 😊
Kind Regards

I'm confused by this. The missing fields indicators are one of the basic features of every LSP. I see this in Python as well as Lua.
From where I sit it's a desirable feature.
Why do you want to turn them off?
Unless people in the community feel very strongly about this I'd prefer we not make this change.

As a beginner, I was more confused about the fact that a major part of config was underlined because of these warnings and I thought I am expected to fix the warnings in order to repair this config. However I understand your point - I just shared my initial user's experience with this configuration.

Thanks very much for the idea. I just think it's throwing the baby out with the bathwater :) Closing this for now.

i agree, i thought my config was broken,
but i vote for
    lua_ls = {
        Lua = {
            workspace = { checkThirdParty = false },
            telemetry = { enable = false },
            -- NOTE: Toggle below if Lua LSP Warnings are too much
            -- :help Link
            -- diagnostics = { disable = "missing-fields" },
        },
    },

@wommy what is the :help Link for? Not sure it's related to the issue?

@wommy Please generate a PR for this and, obviously minus the :help link, I'll merge it. I like how this signposts the way for people who want this disabled but doesn't short circuit the lsp defaults.

Just some related items I've spotted whilst looking for a solution to this.
A pull request in nvim-cpm to fix this is open  🎉
An issue in treesitter, but looks like it isn't a priority
And finally there is an example of how to supress the warnings using a mix of ---@diagnostic disable: missing-fields, ---@diagnostic enable: missing-fields, and ---@diagnostic disable-next-line: missing-fields.

i was trying to echo how TJ has the :help's peppered throughout,
but i had another appointment so i just typed up something quick and i thought thatd be clear
as im just trying to make the transition from the vimscript to lua myself, im totally unfamiliar,
is there a way to point to lua-language-server/settings#diagnosticsDisable
what should be pointed to? is there something equivalent / better?

https://github.com/nvim-lua/kickstart.nvim/pull/511

@wommy I don't think there is a help entry for that, at least I could not found one. Using the http link should work just as fine, or leaving the comment as is is probably also good enough.

https://github.com/nvim-lua/kickstart.nvim/pull/511 got merged


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


PR 1 - Implement toolkit csharp samples

Sample List -
1.bot-people-picker-adaptive-card/csharp
2.bot-receive-channel-messages-withRSC/csharp
3.bot-sso-adaptivecard/csharp
4.bot-teams-authentication/csharp
5.bot-type-ahead-search-adaptive-cards/csharp


Handle unknown residues in PDB structures.

Now I remove the X residues, the predictions are still good.


chore(main): release 0.1.2

:robot: I have created a release beep boop
0.1.2 (2022-12-18)
Bug Fixes

Set regex flags g, m, and i (1ee13ab)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/paulschuberth/regex-extract-action/releases/tag/v0.1.2 :sunflower:


Rename "zulip" system bot realm to "zulipinternal"

Folks sometimes get confused when using e.g. manage.py list_realms in production that there's usually a realm with the name `` (aka the empty string), which is the one they use, and one with the name zulip, which if their hostname is zulip.example.com, sounds a lot like it's the one they want.
We should fix this in these ways:

[x] Have manage.py list_realms print the actual full domains/URLs of the organizations.
[x] Rename zulip to zulipinternal.
[ ] Spell the root domain as ., not '', at least for management commands.
[x] Migrate the development environment to also have a zulipinternal realm, via patching populate_db.

@zulipbot claim

@zulipbot abandon

@zulipbot claim

@timabbott for the third part, I changed the database default from HOST: '' to HOST: '.' in settings.py. Am I going in the right direction.

@zulipbot abandon

Marked off a few more tasks that are complete.  I'm not 100% confident we actually want to do the '' -> . migration; we should discuss the question again before investing time in such a migration.

I think it's not worth doing; closing as resolved.


Modular DriverResult

What is the expected enhancement?
With #220 coming to an end, the first step of #148 will soon be implemented.
As outlined there, the second step was the investigation of whether the Transformer classes can benefit from these new properties. I.e. the following work flow change:

Current: Driver -> QMolecule/Watson -> Transformer -> Property -> SecondQOp
Proposed: Driver -> QMolecule/Watson -> Property -> Transformer -> SecondQOp
The reason we should investigate this is that we are potentially working towards cutting out the QMolecule/Watson step alltogether (at least from the public API view).

I propose to tackle this issue by introducing a new DriverResult base class:
class DriverResult:
    def __init__(self, ...):
        self.properties: Dict[str, Property] = ...

    @abstractmethod
    def from_legacy_driver_result(result: Union[QMolecule, WatsonHamiltonian]) -> DriverResult:

    @abstractmethod
    def interpret(result: EigenStateResult) -> None:
        # In-place interpretation

We could then have an Electronic(Structure)DriverResult and a Vibrational(Structure)DriverResult. These would gather all the properties which can be extracted from a driver and collects them for further processing by Transformer instances.
These objects would then also be stored in the Problem._molecular_data variables. This would then also allow us to centralize the .interpret() method as part of the properties gathered in each DriverResult rather than having the result_interpreter spread out over the problem modules.
Being containers of all properties available in a calculation, they can be passed to a Transformer granting access to all property data. Assertions on required properties would need to be done by the Transformer instance itself (e.g. if it requires both, ElectronicEnergy and ParticleNumber, etc...)

Closed by #263


Delet all integrals

Hi,
at the moment it isn´t possible to "delete all integral" if you work with the full screen. You have to leave the full screen, than you can see the red box with "yes" and "no".
Kind regard,
Eva

@evaziegler
right now you are right this actual what happen, but let me check if i can solve this problem or not.
I will let you know once i check it.

@evaziegler
i fixed the problem, so you can now see the delete modal and other types of modal even if you in the full screen mode


Package Requested

[X] I would like someone else to build the manifest.
[ ] I would like help so I can submit the manifest.
[ ] I have performed a search and couldn't find this package.
[ ] I have checked that the installer for this package is not a standalone or portable executable or a .zip file
[ ] I think there is a new version available and I have provided the URL.

Please provide the following information
Publisher: KDE e.V.
Publisher Url: http://kde.org
Package Name: KDE.Kile.Nightly
Description: http://apps.kde.org/kile
Package Version: master-1378
Installer URL: http://binary-factory.kde.org/view/Windows 64-bit/job/Kile_Nightly_win64/lastSuccessfulBuild/artifact/kile-master-1378-windows-msvc2019_64-cl.exe
Current Package Identifier (for new versions): master-1378

Duplicate of #39190
Please post your KDE requests here


[EPIC] Automate the creation and management of recurrent tasks

We have at least two types of recurrent tasks that we know when we need to do and we know hot to do them

gathering billing info about clusters
regenerating deployer credentials for smce clusters

Currently they are tracked by @yuvipanda I believe in this calendar
Proposal
While this is a great approach to not forget about them for long periods of time, there is still the risk of missing to open them in time to be prioritized. They also consists of a bunch of repetitive tasks that we need to do on the Engineering board, after their creation to make them ready to be worked on.
We should consider automating this efforts:
- [ ] https://github.com/2i2c-org/infrastructure/issues/4903
- [ ] https://github.com/2i2c-org/infrastructure/issues/4904
- [ ] https://github.com/2i2c-org/infrastructure/issues/4905

Scheduling recurring tasks is something that was thinking about in https://github.com/2i2c-org/meta/issues/1498 .  While the overall procedure is out of scope for this epic, there are some GitHub issue scheduling subtasks that I think fit in this epic.


License this under CC0

Publishing this as CC0 makes sense, as all data here
is trivially derived from Wikidata data (which itself
is CC0).
I chose to create a LICENSE file, even though CC0 is not
a license, for the sake of consistency.
CC0 text taken from:
https://creativecommons.org/publicdomain/zero/1.0/legalcode.txt

Note: @filbertkm and I were the only people ever submitting data to this.

Great move, thanks guys!


[cfe] Missing bounds check on type annotations

Consider the following program:
class A<X> {}
class B<X> extends A<X> {}
class C<X1, X2> {}

typedef G<X1 extends A<X1>, X2 extends A<X1>> = C<X1, X2>;

void f(G<dynamic, A<A<dynamic>>> x) {}

G<dynamic, A<A<dynamic>>> x = throw 0;

class D {
  G<dynamic, A<A<dynamic>>> x = throw 0;
  static G<dynamic, A<A<dynamic>>> y = throw 0;
}

void main() {
  G<dynamic, A<A<dynamic>>> x = throw 0;
}

This program is accepted with no compile-time errors by dart --enable-experiment=nonfunction-type-aliases (f2dfe3a8be24db64c924541c2775ef496171c02b). However, each occurrence of the type G<dynamic, A<A<dynamic>>> should be flagged as an error: It is not regular-bounded (because, 1st type argument, dynamic <: A<dynamic> does not hold), and it is not super-bounded (because, 2nd type argument, A<A<Never>> <: A<Never> does not hold), and every malbounded type should be flagged as a compile-time error.

cc @stefantsov


Reset option in Camera Settings

For using the same transforms in multiple places, I would implement Default for CameraInputState. This allows you to just write *camera_state = CameraInputState::default(); The other fields can just default to false or whatever the zero value is.
If you want your commits to be on top of the upstream branch, you should use rebase to avoid the merge commits with git rebase upstream/main. If you don't have any different commits on your fork, you should be able to just do a git pull from upstream.

How's this?

Looks good.