Implementing Refresh Token Mechanism for Enhanced Authentication

Description:
In response to limitations encountered with JWT token expiration in our application's authentication system, this PR proposes the implementation of a refreshToken mechanism. This enhancement aims to bolster security, improve user experience, and optimize scalability.
Benefit:

Enhanced Security: Introducing refresh tokens provides an additional layer of security, allowing seamless token refreshment without requiring users to reauthenticate frequently.
Improved User Experience: Users will experience uninterrupted sessions as refresh tokens mitigate abrupt logouts caused by expired JWT tokens.
Scalability: By reducing reauthentication requests, especially in high-traffic scenarios, implementing refresh tokens enhances the application's scalability.

Proposed Solution:

RefreshToken Endpoint: Introduce a /refresh endpoint responsible for issuing new JWT tokens upon receiving a valid refresh token. This endpoint will handle token expiration, invalidation, and rotation securely.

Additional Considerations:

Token Expiry: Define appropriate expiry times for refresh tokens to balance security and usability.
Security Measures: Implement token revocation, rate limiting, and rotation to mitigate security risks effectively.
Compatibility: Ensure compatibility with existing JWT authentication implementations and libraries for seamless integration.

Implementation Details:

Backend Changes: Modify the authentication service and database schema to accommodate refreshToken functionality securely.
API Endpoints: Define the /refresh endpoint for checking refresh tokens. Specify expected behavior, input/output formats, and security measures to be implemented.

Testing Plan:

Comprehensive testing will be conducted to validate the functionality of the refreshToken mechanism, including scenarios like token expiration, invalidation, and rotation.
Integration tests will ensure compatibility with existing JWT authentication implementations and libraries.

Hey @sayan404 Sir Please Checkout PR.


Timeout in pkg test is too short.

Parts of the test pkg/intl/test/date_time_format_file_even_test time out on our arm and mips simulators occasionally because timeouts hard-coded into the test are too small.

This issue has been moved to dart-lang/intl#27.


incoming / outgoing stream count wrong for the client

So this wasn't actually a bug, but just a super-weird naming of variables: for a client outgoing streams would be counted using the variable numIncomingStreams and incoming streams using numOutgoingStreams. This naming is so confusing that it might justify the bug label anyway ;)


Generated C++ event handlers should be virtual (again)

Hi there,
I upgraded from wxGlade 0.6.3 to 0.8.3 and noticed that the newer version does not export C++ event handler methods as virtual anymore. 83dafbc9de68fc9fa3188b03e7eacf0e110ded3b introduced this, the first release with this was 0.7.1.  83dafbc9de68fc9fa3188b03e7eacf0e110ded3b states that

The wx documentation states "The member function that handles an event
does not have to be virtual."

which might be true, but the event handlers being virtual really relly helps the IMO quite common use case where one subclasses the wxGlade-generated C++-classes. In fact, non-virtual event-handlers break existing projects like this one here where with 0.8.3-generated code only the base class's methods are called although they're overriden in the subclass.
Is this meant to used differently now? If not, I suggest to revert 83dafbc9de68fc9fa3188b03e7eacf0e110ded3b, although I don't know the exact reasons it was actually introduced.
PS: I'm aware of https://sourceforge.net/p/wxglade/mailman/message/36706324/ and willing to test this.

I don't know why that was changed at all.
The latest commit in the master branch has the virtual methods again. I would not want to change this in the 0.8 or 0.9 series if not absolutely necessary. Test cases are not adjusted yet. I will do so after feedback.
Would you mind trying? The structure of the generated code is different from before. It should look more like what a human being would write. As I can't easily test C++, it would be great to receive feedback on this. In Python things are working fine.
Next on the list will then be the dynamic event binding...

Thanks for the swift reply! I fear, though, that 89400ab242856eba71586cbe55d023061ed81801 did not (yet) fix the issue, for me, adding virtual to https://github.com/wxGlade/wxGlade/blob/master/codegen/cpp_codegen.py#L627 did it. Really not sure about those two code paths though.
I also encountered a separate issue which I reported as #371, will need to dig a bit more into this.

Do the event handlers in the C++ files need to have the virtual keyword as well?
void All_Widgets_Frame::onStartConverting(wxCommandEvent &event)  // wxGlade: All_Widgets_Frame.<event_handler>
{
    event.Skip();
    // notify the user that he hasn't implemented the event handler yet
    wxLogDebug(wxT("Event handler (All_Widgets_Frame::onStartConverting) not implemented yet"));
}

Do the event handlers in the C++ files need to have the virtual keyword as well?
void All_Widgets_Frame::onStartConverting(wxCommandEvent &event)  // wxGlade: All_Widgets_Frame.<event_handler>
{
    event.Skip();
    // notify the user that he hasn't implemented the event handler yet
    wxLogDebug(wxT("Event handler (All_Widgets_Frame::onStartConverting) not implemented yet"));
}

Nope, only the headers.

OK, then things should work now. Please test.

That's it, thanks for the weekend work! ;-)


Meetings: Remove 3/1 Regular Board Meeting

A Regular Board Meeting on 03/01/2021 is showing on the site. It was created by mistake and has been deleted in Legistar. Please remove it from the website.

@shrayshray You should be able to remove this event from the site yourself, thanks to the changes in #697. Let me know if you have any questions / issues?

@hancush yes, sorry! I was having trouble with the login but figured it out and removed the event.

Sooo satisfying to hear it worked, though, @shrayshray! :-)


problem installing cloudnode in mac

Hey,
got an error installing cloudnode-cli in mac...
The error that told me to post here goes like...
npm ERR! Could not create /usr/local/lib/node_modules/___cloudnode-cli.npm
npm ERR! error installing<EMAIL_ADDRESS>Error: EACCES, permission denied '/usr/local/lib/node_modules/___cloudnode-cli.npm'
npm ERR! Error: EACCES, permission denied '/usr/local/lib/node_modules/___cloudnode-cli.npm'
npm ERR! Report this entire log at:
npm ERR!     http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR<EMAIL_ADDRESS>npm ERR!
npm ERR! System Darwin 11.2.0
npm ERR! command "node" "/usr/local/bin/npm" "install" "cloudnode-cli" "-g"
npm ERR! cwd /Users/nitinthewiz/Documents/TurnTable/bhangra
npm ERR! node -v v0.6.5
npm ERR! npm -v 1.1.0-alpha-6
npm ERR! path /usr/local/lib/node_modules/___cloudnode-cli.npm
npm ERR! code EACCES
npm ERR! message EACCES, permission denied '/usr/local/lib/node_modules/___cloudnode-cli.npm'
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/nitinthewiz/Documents/TurnTable/bhangra/npm-debug.log
npm not ok
Also, the debug log mentioned there, I've uploaded at - nitinkhanna.com/npm-debug.log
I have absolutely no idea what happened here. I'm a subversion guy! :P
I installed npm and node.js using the node.js installer for mac on their website and then gave the command -
npm install cloudnode-cli -g
and bam! This error. Just wanna play around with node.js and cloudno.de is free, so went there... But this error stops me from experimenting...
Awaiting a reply from you! :)

Run it with sudo.


Add knob for forceDirection

Enact-DCO-1.0-Signed-off-by: Roy Sutton<EMAIL_ADDRESS>Issue Resolved / Feature Added
Resolution
Additional Considerations
Links
Comments

@webOS101  - should this be closed out for the changes in https://github.com/enactjs/enact/pull/1754?

Yes, @webOS101. This is fully incorporated into #1754.


[INFORMATIONAL] Sequence number wrongly validated

Severity: [INFORMATIONAL]
Auditor: Halborn
Code: Aptos Core or Suzuka
Sequence number wrongly validated
The tick transaction pipe is supposed to compare the transaction sequence number with the account sequence number from its database, but it does not. This is not exploitable as another validation mechanism in VM prevent users from using wrong sequence numbers.
However as the codebase can change, from a security-in-depth principle it is better to fix the potential risk: protocol-units/execution/opt-executor/src/executor/transaction_pipe.rs#L63

We can double-check, but the mempool should accept or reject based on the validity of the sequence number. Hence, the status here should account for the above.

Duplicate of #415?

Duplicate of https://github.com/movementlabsxyz/movement/issues/415?

Yes


feat: support play-billing v5

@m1ga Maybe combine into your PR? I started it as a v4 upgrade and then moved to v5 sequentially.

I think you have all changes in already so I'll close mine :smile: :+1:

Okay 😄 Will keep it open until tested by some more apps. I attached a binary for reference.


Mods stop working when folder names have unusual letters

This is a weird issue that's been reported since the 0.1.x releases, I can't find the logic behind it, heavy testing needs to be made to identify the issue. It seems pretty random too.
For example:

With this Lincoln Continental from MadDriver I even had problems with the folder name that seens to be using unusuall letters. Even when putting the blank folder "Lincoln Continental Sedan (53А) 1962" without any content in the modloader directory it randomly disables other mods. Very strange and took me some time to figure it out.

This happens because Loader::ModInformation::Scan has a ::scoped_gdir that does not signal failure. Since we don't use WinAPI Wide API, when we go after a non-ASCII directory it'll fail and will essentially read the modloader/ directory.
Either:

Make proper unique support.
Or throw a exception (and of course catch it at the correct place) when scoped_gdir and such fails.
Or both!

Unicode support, now! :p

My two cents:
https://pastebin.com/aYaBhtR5
Caused by U+200E character. Look at the "ai upscaled weapon textures + icons" folder name.


Bump minimum go version to 1.14

We should bump the base golang version to 1.14, most libs have moved on to at least 1.14.

related: https://github.com/cloudevents/sdk-go/issues/567 bumping to 1.14 seems to help the nats client work.


index task SUCCSEFUL but segments don't show up

Hi,
I see the segments in HDFS and MySql.  The coordinator web console shows the datasource "impression" we created.
However, when clicking on impression datasource in the web console, there are no data segments shown and displaying "loading" forever.
And doing a time boundary query on historical node, shows empty data set:
{
"queryType" : "timeBoundary",
"dataSource": "impression"
}
result: []

If you provide guidance how to investigate this, I am available to take this investigation task, but right now I don't know where to take this from. Does overlord need to announce by creating objects in zookeeper with the newly published segments?
Just to mention, I also restarted all java processes: I killed all java processes including zk, then started zk on all nodes , then coordinator and historical. To no avail. Same. No data :(

misconfig at the historical node: when we put hdfs://master:43234:///path it worked


Scale quantile via DAAL

Hello @PokhodenkoSA! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file sdc/daal_overloads.py:

Line 59:1: E402 module level import not at top of file

@PokhodenkoSA to control number of threads use this
https://github.com/IntelPython/daal4py/blob/master/src/daal4py.cpp#L604


update TimeoutSampler call using self.status

Short description: small update in wait_for_status_success()
More details:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
Bug:

!verified

@dbasunag please cheryy-pick to 2.1.42 branch


Documentation for VCAP_APPLICATION environment variable

In the documentation for application environment variables, the details of a few VCAP_APPLICATION  attributes are misleading and wrong (http://docs.run.pivotal.io/devguide/deploy-apps/environment-variable.html#VCAP-APPLICATION ):

application_id: With commit https://github.com/cloudfoundry/dea_ng/commit/3e1c2be17ca5dcd4073fdccbbb36620aba70d233  , this attribute is also added to the VCAP_APPLICATION variable. However, this is not documented at all.

instance_id: This represents the GUID of the application instance and not the "GUID that identifies the application". Instead, it is the 'application_id' field which identifies the application.

Requesting an update of the docs to clear these issues.

In a related note, for the fields "application_version" and "version", the docs state that it is a "GUID that identifies a version of the application that was pushed. Each time an application is pushed, this value is updated". However, I found that even upon restarting an app (cf restart APP_NAME), the application version is updated.
Can the documentation be updated to reflect this as well? I hope this is the intended behavior

Hello there @abhikco,
This has been updated in the Cloud Foundry docs. Take a look here.
If you think anything else needs to be updated, please let us know.
Thanks,
@jberkhahn & @wendorf
CF CAPI Team

@jberkhahn : Thanks ! This looks fine


write example on how to have lightnode that is capable of receiving transaction in mempool

Describe the feature
this would be helpful!
Additional context
No response

closing because we already have this
https://github.com/paradigmxyz/reth/blob/f4255216c78e78ae94ca8927f9f8f2afccb0d69c/examples/network-txpool/src/main.rs#L7-L7


pkg/cover, pkg/mgrconfig: account for PLT when calculating arm64 modu…

…le offset
On ARM64 Linux kernel performs extra trickery when calculating the offset of the .text section. In particular, it overrides sizes and alignments of the .plt and .text.ftrace_trampoline sections, ignoring what is written in the ELF headers.
This patch factors out the module loading code into elfSimulateModuleLoad(), makes the necessary adjustments to account for the changed section attributes, and adds tests for elfSimulateModuleLoad().
Because the size of .text.ftrace_trampoline depends on the kernel version, we also introduce the is_kernel_6_1_or_earlier config parameter that is used to calculate the correct size.

Before sending a pull request, please review Contribution Guidelines:
https://github.com/google/syzkaller/blob/master/docs/contributing.md

At this point I really begin to wonder if there's a more straightforward way to figure out correct module offsets without having to keep our code and that of the kernel in sync.
Could the /proc/kallmodsyms output help here?

/proc/kallmodsyms was never submitted, but turns out we have /sys/module/*/sections/.text.
@necipfazil even tried to add support for it in https://github.com/google/syzkaller/pull/4025, and we can revive that patch.
The only problem I see is that syz-cover currently accepts the output of /proc/modules, which contains incorrect addresses - we'll probably need to stop supporting it.

@ramosian-glider is this PR still needed now that https://github.com/google/syzkaller/pull/4512 is merged?

No, let's close it. Thanks for noticing!


v2: please change the obsolete JsonDictionaryContract.PropertyNameResolver to JsonDictionaryContract.DictionaryKeyResolver

You already updated JsonContractResolver in v3 to meet new Newtonsoft.Json contracts.
Please apply the changes for v2 also, otherwise it does not work with latest Newtonsoft.Json (I cannot use an old one because of other dependencies).

If you can use V3 in that application, I'd highly recommend it. The message format is compatible with v2 (a service using v2 can consume messages from v3 and produce messages that can be consumed by v3).
I'm worried that updating v2 will cause all kinds of issues.

Hi,
Thanks for the answer.
Unfortunately, there is no MSMQ support in v3 as far as I know but in our
projects we are still using this.
BTW: I created a pull request with required changes for v2 :)
Alexey
Am 05.09.2017 22:30 schrieb "Chris Patterson"<EMAIL_ADDRESS>
If you can use V3 in that application, I'd highly recommend it. The
message format is compatible with v2 (a service using v2 can consume
messages from v3 and produce messages that can be consumed by v3).
I'm worried that updating v2 will cause all kinds of issues.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MassTransit/MassTransit/issues/941#issuecomment-327294132,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF1MoBCOOR9C6Z6wdieP060M9UY3lHwMks5sfa9zgaJpZM4OY9dx
.


Unmarshaling data using a struct with the jose.JSONWebKeySet struct embedded stopped working on v4.0.3

We are trying to update go-jose from 4.0.2 to 4.0.3 in the SPIRE and go-spiffe projects, but unit tests are failing with 4.0.3.
Looking at #130, it can be seen the introduction of the UnmarshalJSON method in the JSONWebKeySet type, which influences the way that a json.Unmarshal works when unmarshaling data using a struct with the jose.JSONWebKeySet type embedded. This is because now it can be called during the decoding process, as the decoder now encounters this Unmarshaler that can be called but the result is that the struct that holds the jose.JSONWebKeySet struct does not get the fields properly populated (e.g. the RefreshHint field).
I'm not quite sure if we are doing something wrong in our side. To see if this change is related with the failure, I deleted this function from the 4.0.3 code and the parsing / decoding works as expected, with the tests passing.
I would really appreciate some help to find a solution here. Thanks!

Hm, that's an interesting use case. I see you have this type:
type bundleDoc struct {
	jose.JSONWebKeySet
	SequenceNumber *uint64 `json:"spiffe_sequence,omitempty"`
	RefreshHint    *int64  `json:"spiffe_refresh_hint,omitempty"`
}

And you're saying that if you parse, e.g. https://github.com/spiffe/go-spiffe/blob/94335b268274926928c08fc5ce21f12a4e1ea044/v2/bundle/spiffebundle/testdata/spiffebundle_valid_2.json#L62-L63 into it, the SequenceNumber and RefreshHint fields do not get populated?
It seems like this is some surprising behavior of Go's encoding/json in how it unmarshals into structs with embedded structs in them. https://pkg.go.dev/encoding/json

To unmarshal JSON into a value implementing Unmarshaler, Unmarshal calls that value's [Unmarshaler.UnmarshalJSON] method,

The surprising interaction here is that bundleDoc implements Unmarshaler, because it has the UnmarshalJSON function, because it embeds a struct that has that function. And of course its implementation of UnmarshalJSON is the one on JSONWebKeySet, which only knows about the JSONWebKeySet and doesn't even have a way to assign fields on the parent struct.
This does break running code like yours, so I'm inclined to revert and publish a new release, and possibly retract 4.0.3. The new release would be breaking with regards to 4.0.3. Anyone who already started relying on JSONWebKeySet to accept unrecognized keys would start getting an error. However, between the two types of breakage I think the one where you get an error is preferable to the one that could be silently missed by anyone without solid tests. Kudos to spire and spiffe for having those tests, and thanks for letting us know.

Fixed in v4.0.4: https://github.com/go-jose/go-jose/releases/tag/v4.0.4

Thank you so much for the quick turnaround!
I was able to confirm that this is fixed in the 4.0.4 release, with our tests passing. Thanks again @jsha and @mcpherrinm.


Add Section for Datasets?

I'm currently working on a project that requires a seed spanglish code-switched dataset and would love to see recommendations on where I could find these. Thank you!

Hi @tnagar72 thank you for reaching out. I plan to have a big update the repo, including the latest papers using LLMs which is very relevant on current use cases. I found some cool papers in the last months and datasets creation using LLMs. I will let you know when the repo is updated! Stay tuned!


ghost site crashing 502 BAd Gateway

Hi
Since I upgraded to Ghost 0.9.0, my site keeps crashing every 16-24h, output of npm-debug.log below:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'start',
1 verbose cli   '--production' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info prestart<EMAIL_ADDRESS>6 info start<EMAIL_ADDRESS>7 verbose unsafe-perm in lifecycle true
8 info<EMAIL_ADDRESS>Failed to exec start script
9 verbose stack Error<EMAIL_ADDRESS>start: node index
9 verbose stack Exit status 134
9 verbose stack     at EventEmitter. (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:214:16)
9 verbose stack     at emitTwo (events.js:87:13)
9 verbose stack     at EventEmitter.emit (events.js:172:7)
9 verbose stack     at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:24:14)
9 verbose stack     at emitTwo (events.js:87:13)
9 verbose stack     at ChildProcess.emit (events.js:172:7)
9 verbose stack     at maybeClose (internal/child_process.js:818:16)
9 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
10 verbose pkgid<EMAIL_ADDRESS>11 verbose cwd /var/www/redacted/ghost
12 error Linux 3.13.0-71-generic
13 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" "--production"
14 error node v4.2.4
15 error npm  v2.14.12
16 error code ELIFECYCLE
17 error<EMAIL_ADDRESS>start: node index
17 error Exit status 134
18 error Failed at the<EMAIL_ADDRESS>start script 'node index'.
18 error This is most likely a problem with the ghost package,
18 error not with npm itself.
18 error Tell the author that this fails on your system:
18 error     node index
18 error You can get their info via:
18 error     npm owner ls ghost
18 error There is likely additional logging output above.
Restarting the service works fine for a while, and then same crasha  few hours later.

@xiolo Sorry to hear you're having trouble!
Can you please swing by our slack channel and ask for help there? We can provide better support there than in the Github issue tracker, and if this turns out to be an actual issue with Ghost this issue can be reopened.
Thanks! 😄


Can you upload this library to maven central repository?

Can you upload this to maven central repository? it would be easy for developers to add this library into their projects.
thanks.

+1

Hey, there are a pull request from JitPack team to add this library to the repository.
I did pull this to my fork, although I implemented pt-BR translations, and a Spacing hiding when no pictures taken.
If you wanna check it while @asantibanez  don't answer, just check mine or Jitpack fork.
mine on: https://github.com/wviana/Patio
Jitpack on: https://github.com/jitpack-io/Patio

Done. Thanks @wviana for your contribution as well as @jitpack-io for making it available through gradle.


The Svelte example is 404

The Svelte example was there a week ago but is now 404. Does it mean Vite + Svelte is actually not supported?
I could recreate the original example with no problem. But when I use a Svelte component library in the remote app, it fails to build.
Related discussion: https://github.com/module-federation/module-federation-examples/discussions/4049
I think the problem is Svelte allows exporting components without compiling them into Javascript, i.e. they remain as .svelte files, and Vite and ESBuild do not know how to handle them. Unfortunately, my knowledge in this area is very limited. The only thing I can do is to try different config options and plugin orders. Now seeing the official example is 404, I think I have to consider giving up and going back to React.

It was removed here: https://github.com/module-federation/module-federation-examples/pull/4086. Maybe this helps.

It was removed here: module-federation/module-federation-examples#4086. Maybe this helps.

Thanks. I will subscribe that thread. Tbh at this point I have given up implementing Module Federation in my Vite+Svelte project. I'm studying Vite/Rollup's options and hooks for accomplishing micro-frontends with shareable chunks. Though Vite currently has a bug that complicates things.

We are working on a new version of this package, as @KaiVolland mentioned the examples are not available anymore.
Thanks


Are there any examples to parse EDI 204 From this library

Hi , it seems we cannot find a model or a interchange for Edi 204 for this library , i am seeing some issues logged in git-hub for this , is there any chance of an interchange existing.

Hi and thanks for your interest in EDI.Net
unfortunately there is no test sample for the transmission you are referring to.
You could try asking a question on stackoverflow with the tag edi-net in order to reach a broader audience.
Last there are good examples you can checkout inside the repository under the tests project.
If you get something to work and want to share back feelfree to open a pull request.
Regards,
C.


Notebook: Decision trees

See the spreadsheet for details

Content
Programming

VR
VR

Ideas/prereqs:
trees vs linear models
Direct link
https://jupyter.olney.ai/hub/user-redirect/git-pull?repo=https%3A%2F%2Fgithub.com%2Fmemphis-iis%2Fdatawhys-content-notebooks&subPath=Decision-trees.ipynb&app=lab

Closing with https://github.com/memphis-iis/datawhys-content-notebooks/commit/eea6a3f33c3f9adb2be42946226818091407a926 to clear the board.
We can reopen for future revisions.


Create generic xrdcp stageout plugin

Just talked to @hufnagel and it seems another setup was done for AWS, so this would really be a generic plugin. I'm marking it as medium prio, feel free to change it if you consider so.


Add grapi

https://github.com/izumin5210/grapi

You can develop and deploy API servers blazingly fast ⚡
Easy code generator

application (inspired by rails new and create-react-app)
gRPC services and their implementations (inspired by rails g (scaffold_)controller)

User-friendly protoc wrapper (inspired by protoeasy)
Provides gRPC and HTTP JSON API with single implementation by using grpc-gateway
Generates codes based on google's API design guideline

↑
I signed it!


Produce batch time metrics

To be able to see how long it took to to produce a batch to pass to monitoring systems to work out if producing timeout is to low or Kafka is being overloaded.
Expired issues where batch's get stuck in a retry loop because the batch is timing out and no way to diagnose this.

What span of time are you attempting to capture, and with what information?
I was thinking to add this to ProduceBatchMetrics, but the ProduceBatchWritten hook is only called on batches that are successfully produced.
Do you want to capture from the moment a record enters Produce through ... when? If you want to capture failures, do you mean for the batch duration to be called on every failure&retry, or only the final failure at which point the promise is called?

Yeah I had a look  at produce batch metrics and thought it was the wrong place.
More interested on the Kafka request time then when a message gets put on the produce queue as this is when the ProduceRequestTimeout value is used and what causes a retry to happen.  So would be good for this time taken to be recorded for each retry.
I am not interested in capturing failures at the moment, but maybe its worth tracking these somehow generally, as RecordRetries can be left unbounded and the  promise may never be called to allow for tracking of produce errors. So you could just end up with producing being stuck and no way to investigate.
I like the hook system as its useful to switch in and out different tools but maybe making harder to add error case handling.

So, do you want essentially the time that a record was in the client? If so, couldn't you set r.Context before producing with a key indicating "producing now", and then check time.Since that key once the promise is called?

Not forgotten about this been looking at if the data we get from tracing is good enough for this

Yeah trace span metrics for producing is giving good results atm closing.


Update BUILD_UBUNTU.md

@kenCode-de Please use the Edit button at the top of the page to modify this pull request to target develop branch.

??

I cannot accept pull requests into master branch. Please target develop branch.


feat(canary-react): added custom column widths

added ability to provide a column width percentage value to set table column widths

Summary
Added ability to customise the width of ic-data-table columns. The IcDataTableColumnObject now accepts a numeric percentage width parameter which, if provided, should be between 1 and 100.
For all columns in a table where the width is not provided, their width is calculated automatically by dividing up equally the remaining  space.
Checklist

[x] Commit subject includes component name (i.e. feat(canary-web-component): [ic-] ....)
[x] Component tag has been updated with unstable. (i.e. ic-**unstable**-<component_name>).
[x] Updated type references to new component tag where relevant (i.e. IcUnstable<Component_Name>).
[x] npm run build has been re-run.
[x] Component has a story.
[x] Component has been accessibility tested.
[x] Component has unit and e2e tests.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Duncan 855555 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Heya, sorry that we didn't address your contribution! This repository has been inactive for a while and we're going to archive it because canary work is now performed in the main ic-ui-kit repo, closing this PR in preparation.
It looks like Column Width functionality was implemented in Data Tables in September too, hopefully that meets your needs :)


[AutoDiff] Cleanup 1: Remove gradient synthesis and ban #gradient.

As we've finished generalized differentiability, we start to remove legacy code from the compiler. The first step is to remove gradient synthesis from the core transform.
Gradient synthesis was the phase of differentiation that replaced #gradient(f) with a function call to f's gradient function. This had lots of mathematical problems, and is no longer necessary under generalized differentiability because all differential operators are now defined as stdlib functions.

Changes

Remove gradient synthesis code paths along with any mentions of "gradient" from the core transform.
Remove VectorNumeric.init(_:) -- it was used by gradient synthesis to initialize a 1 value. The removal brought up a couple of crashers with initializing a 0 tangent vector. When a zero needed to be materialized, the compiler tried to find VectorNumeric.init(_:) instead of VectorNumeric.zero. The good thing is that it's only affecting one or two tests so I just commented them out for now. Fixing this is my immediate next step.
In the process of migrating tests, I found a verification failure in the seed initialization for the adjoint/pullback of indirect calls whose original function is followed by a tuple_extract when only one result is active. It tried to seed the adjoint/pullback using the entire tuple, but it should pass the active result's adjoint element instead. I fixed that for both VJP mode and non-VJP mode.
Migrate tests to use functional differential operators.

Disable the tensor runtime AD test because there's a segfault when we use the pullback(at:in:) operator. I will fix this in a separate PR.
After the switch, the diagnostics test shows that errors are no longer accumulating for some reason, but the compiler is still able to emit correct error messages for each error case. I commented out all except one case of diagnostics checks in autodiff_diagnostics.swift because this can be investigated later.

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow


Added Public Key Encryption circuit

Implemented the public key encryption circuit in src/[pk_encryption_circuit.rs as described in #16
Added the scripts for generating the inputs for the pk_encryption_circuit

Okay , I will remove the unwanted code and make the required changes as mentioned  in the comment


Fix home topic edit form layout

The UI has been refactored by #30191 , so here are 2 choices:

Backport #30191
Apply this quick fix

Before:

After:

https://github.com/go-gitea/gitea/pull/30191 seems to big too backport, lets go with this.


Proper way to get files for a branch?

So far I've come up with the code below (which does work):
r, err := git.PlainOpen(repository)
handleError(err, fmt.Sprintf("Problem opening repository %s", repository))
branches, err := r.Branches()
handleError(err, "Problem accessing branches")
branches.ForEach(func(b *plumbing.Reference) error {
	fmt.Println("Branch:", b.Name(), "hash:", b.Hash())
	if b.Name == branchName {
		commit, _ := r.CommitObject(b.Hash())
		files, _ := commit.Files()
		files.ForEach(func(f *object.File) error {
			fmt.Println("File Name:", f.Name)
			return nil
		})
	}
	return nil
})

But the portion where I'm looping through all the branches and checking the name seems like it's not ideal.  I had been hoping that I could get the files for a branch by using config.Branch like below:
branch, err := r.Branch(branchName)
// some how use this to get the hash that I care about
commit, _ := r.CommitObject(b.Hash())

But I can't figure out any way to get a hash from config.Branch.  Is it possible to do what I'm trying in the second example or is the first example I provided the best way to get files for a branch?

You can get the reference to a branch without iteration:
ref, err := r.Reference(plumbing.ReferenceName("refs/heads/master"), false)

or
ref, err := r.Reference(plumbing.NewBranchReferenceName("master"), false)

So in full:
ref, err := r.Reference(plumbing.ReferenceName("refs/heads/master"), false)
if err != nil {
    panic(err)
}

commit, err := r.CommitObject(ref.Hash())
if err != nil {
    panic(err)
}

files, err := commit.Files()
if err != nil {
    panic(err)
}

files.ForEach(func(f *object.File) error {
    fmt.Println("File Name:", f.Name)
    return nil
})


[download_dsyms] min version

Feature Request
Hi,
Right now the download dsym tool can look up for a specific or latest version. I would like to be able to specify a min version too.
Thanks,
H.
Motivation Behind Feature

I am on a project that has been running for long with a release around every other week. Many versions are no longer supported or have just very few users left for us. Since this is whole process may be long (downloading and updating crashlytics), I want to be able to set a min version in which i am interesting to do so.
Feature Description

Just a parameter for a min version or build number to download dsyms.
Alternatives or Workarounds

Since this is whole process may be long (downloading and updating crashlytics),

Could you elaborate on that please? I am not sure I understand. What exactly "may be long"?
Can you share the output you are currently getting?

Hi @janpio,
I am now in version 5.4.3, and when i ran the tool it checks and downloads dsym starting on version 1.2.3. Since most of those versions are not interesting to me anymore, I would like to set a min version to start with.
H.

Hi @janpio,
Here is some output with verbose:

hernan: ~/Projects/Polarsteps/sled (master) $ bundle exec fastlane --verbose
[✔] 🚀
DEBUG [2019-01-03 09:42:35.96]: Checking if there are any plugins that should be loaded...
DEBUG [2019-01-03 09:42:35.96]: Loading 'fastlane-plugin-changelog' plugin
INFO [2019-01-03 09:42:35.96]: gem 'fastlane-plugin-changelog' is already installed
DEBUG [2019-01-03 09:42:35.96]: Loading 'fastlane-plugin-appicon' plugin
INFO [2019-01-03 09:42:35.96]: gem 'fastlane-plugin-appicon' is already installed
+---------------------------+---------+-----------------------------------+
|                              Used plugins                               |
+---------------------------+---------+-----------------------------------+
| Plugin                    | Version | Action                            |
+---------------------------+---------+-----------------------------------+
| fastlane-plugin-changelog | 0.12.0  | read_changelog update_changelog   |
|                           |         | emojify_changelog stamp_changelog |
| fastlane-plugin-appicon   | 0.14.0  | android_appicon appicon           |
+---------------------------+---------+-----------------------------------+

Successfully loaded Appfile at path '/Users/hernan/Projects/Polarsteps/sled/fastlane/Appfile'
- app_identifier: 'com.polarsteps.Polarsteps'
- itc_team_id: '327596'
- team_id: 'DH3BP5LCYL'
-------
Successfully loaded Appfile at path '/Users/hernan/Projects/Polarsteps/sled/fastlane/Appfile'
- app_identifier: 'com.polarsteps.Polarsteps'
- itc_team_id: '327596'
- team_id: 'DH3BP5LCYL'
-------
INFO [2019-01-03 09:42:36.10]: ------------------------------
INFO [2019-01-03 09:42:36.10]: --- Step: default_platform ---
INFO [2019-01-03 09:42:36.10]: ------------------------------
INFO [2019-01-03 09:42:36.10]: Welcome to fastlane! Here's what your app is setup to do:
+--------+-------------------+--------------------------------------------+
|                         Available lanes to run                          |
+--------+-------------------+--------------------------------------------+
| Number | Lane Name         | Description                                |
+--------+-------------------+--------------------------------------------+
| 1      | ios update_icons  | Generate icon files                        |
| 2      | ios refresh_dsyms | Refresh symbols on Fabric.                 |
| 3      | ios beta          | Push a new beta BETA build to TestFlight   |
| 4      | ios publish       | Push a new beta RELESE build to TestFlight |
| 0      | cancel            | No selection, exit fastlane!               |
+--------+-------------------+--------------------------------------------+
 [2019-01-03 09:42:36.10]: Which number would you like run?
2
WARN [2019-01-03 09:42:38.68]: Running lane `ios refresh_dsyms`. Next time you can do this by directly typing `fastlane ios refresh_dsyms` 🚀.
INFO [2019-01-03 09:42:38.68]: Driving the lane 'ios refresh_dsyms' 🚀
INFO [2019-01-03 09:42:38.68]: ----------------------------
INFO [2019-01-03 09:42:38.68]: --- Step: download_dsyms ---
INFO [2019-01-03 09:42:38.68]: ----------------------------
Successfully loaded Appfile at path '/Users/hernan/Projects/Polarsteps/sled/fastlane/Appfile'
- app_identifier: 'com.polarsteps.Polarsteps'
- itc_team_id: '327596'
- team_id: 'DH3BP5LCYL'
-------
Successfully loaded Appfile at path '/Users/hernan/Projects/Polarsteps/sled/fastlane/Appfile'
- app_identifier: 'com.polarsteps.Polarsteps'
- itc_team_id: '327596'
- team_id: 'DH3BP5LCYL'
-------
Successfully loaded Appfile at path '/Users/hernan/Projects/Polarsteps/sled/fastlane/Appfile'
- app_identifier: 'com.polarsteps.Polarsteps'
- itc_team_id: '327596'
- team_id: 'DH3BP5LCYL'
-------
Successfully loaded Appfile at path '/Users/hernan/Projects/Polarsteps/sled/fastlane/Appfile'
- app_identifier: 'com.polarsteps.Polarsteps'
- itc_team_id: '327596'
- team_id: 'DH3BP5LCYL'
-------
Successfully loaded Appfile at path '/Users/hernan/Projects/Polarsteps/sled/fastlane/Appfile'
- app_identifier: 'com.polarsteps.Polarsteps'
- itc_team_id: '327596'
- team_id: 'DH3BP5LCYL'
-------
Successfully loaded Appfile at path '/Users/hernan/Projects/Polarsteps/sled/fastlane/Appfile'
- app_identifier: 'com.polarsteps.Polarsteps'
- itc_team_id: '327596'
- team_id: 'DH3BP5LCYL'
-------
Successfully loaded Appfile at path '/Users/hernan/Projects/Polarsteps/sled/fastlane/Appfile'
- app_identifier: 'com.polarsteps.Polarsteps'
- itc_team_id: '327596'
- team_id: 'DH3BP5LCYL'
-------
Successfully loaded Appfile at path '/Users/hernan/Projects/Polarsteps/sled/fastlane/Appfile'
- app_identifier: 'com.polarsteps.Polarsteps'
- itc_team_id: '327596'
- team_id: 'DH3BP5LCYL'
-------
Successfully loaded Appfile at path '/Users/hernan/Projects/Polarsteps/sled/fastlane/Appfile'
- app_identifier: 'com.polarsteps.Polarsteps'
- itc_team_id: '327596'
- team_id: 'DH3BP5LCYL'
-------
Successfully loaded Appfile at path '/Users/hernan/Projects/Polarsteps/sled/fastlane/Appfile'
- app_identifier: 'com.polarsteps.Polarsteps'
- itc_team_id: '327596'
- team_id: 'DH3BP5LCYL'
-------
WARN [2019-01-03 09:42:38.74]: To not be asked about this value, you can specify it using 'username'
 [2019-01-03 09:42:38.74]: Your Apple ID Username for App Store Connect<EMAIL_ADDRESS>INFO [2019-01-03 09:42:44.93]: Login to App Store Connect<EMAIL_ADDRESS>Reading keychain entry, because either user or password were empty
Loading session from<EMAIL_ADDRESS>Looking for App Store Connect Team with ID 117134767
INFO [2019-01-03 09:42:47.59]: Login successful
INFO [2019-01-03 09:42:48.22]: Looking for dSYM files for com.polarsteps.Polarsteps
DEBUG [2019-01-03 09:42:49.43]: Found train: 2.7.1, comparing to supplied version:
DEBUG [2019-01-03 09:42:50.09]: Found build version: <IP_ADDRESS>, comparing to supplied build_number:
DEBUG [2019-01-03 09:42:50.09]: Build_version: <IP_ADDRESS> matches , grabbing dsym_url
DEBUG [2019-01-03 09:42:51.58]: dsym_url:
INFO [2019-01-03 09:42:51.58]: No dSYM URL for <IP_ADDRESS> (2.7.1)
DEBUG [2019-01-03 09:42:51.58]: Found build version: <IP_ADDRESS>, comparing to supplied build_number:
DEBUG [2019-01-03 09:42:51.58]: Build_version: <IP_ADDRESS> matches , grabbing dsym_url
DEBUG [2019-01-03 09:42:53.01]: dsym_url:
INFO [2019-01-03 09:42:53.01]: No dSYM URL for <IP_ADDRESS> (2.7.1)
DEBUG [2019-01-03 09:42:53.01]: Found build version: <IP_ADDRESS>, comparing to supplied build_number:
DEBUG [2019-01-03 09:42:53.01]: Build_version: <IP_ADDRESS> matches , grabbing dsym_url
DEBUG [2019-01-03 09:42:54.87]: dsym_url:
INFO [2019-01-03 09:42:54.87]: No dSYM URL for <IP_ADDRESS> (2.7.1)
DEBUG [2019-01-03 09:42:54.87]: Found train: 2.7.3, comparing to supplied version:
DEBUG [2019-01-03 09:42:55.47]: Found build version: <IP_ADDRESS>, comparing to supplied build_number:
DEBUG [2019-01-03 09:42:55.47]: Build_version: <IP_ADDRESS> matches , grabbing dsym_url
DEBUG [2019-01-03 09:42:56.91]: dsym_url:
INFO [2019-01-03 09:42:56.91]: No dSYM URL for <IP_ADDRESS> (2.7.3)
DEBUG [2019-01-03 09:42:56.91]: Found build version: <IP_ADDRESS>, comparing to supplied build_number:
DEBUG [2019-01-03 09:42:56.91]: Build_version: <IP_ADDRESS> matches , grabbing dsym_url
DEBUG [2019-01-03 09:42:58.34]: dsym_url:
INFO [2019-01-03 09:42:58.34]: No dSYM URL for <IP_ADDRESS> (2.7.3)
DEBUG [2019-01-03 09:42:58.34]: Found build version: <IP_ADDRESS>, comparing to supplied build_number:
DEBUG [2019-01-03 09:42:58.34]: Build_version: <IP_ADDRESS> matches , grabbing dsym_url
[...]
INFO [2019-01-03 09:43:36.89]: No dSYM URL for <IP_ADDRESS> (2.1.4)
DEBUG [2019-01-03 09:43:36.89]: Found train: 4.3.6, comparing to supplied version:
DEBUG [2019-01-03 09:43:37.73]: Found build version:<PHONE_NUMBER>40, comparing to supplied build_number:
DEBUG [2019-01-03 09:43:37.73]: Build_version:<PHONE_NUMBER>40 matches , grabbing dsym_url
DEBUG [2019-01-03 09:43:39.55]: dsym_url: http://iosapps.itunes.apple.com/apple-assets-us-std-000001/....
INFO [2019-01-03 09:43:39.78]: 🔑  Successfully downloaded dSYM file for 4.3.6 -<PHONE_NUMBER>40 to 'com.polarsteps.Polarsteps-4.3.6-201812211140.dSYM.zip'
DEBUG [2019-01-03 09:43:39.78]: Found train: 4.3.7, comparing to supplied version:
[...]
INFO [2019-01-03 09:56:33.77]: -------------------------------------------
INFO [2019-01-03 09:56:33.77]: --- Step: upload_symbols_to_crashlytics ---
INFO [2019-01-03 09:56:33.77]: -------------------------------------------
INFO [2019-01-03 09:56:34.08]: Extracting '/Users/hernan/Projects/Polarsteps/sled/com.polarsteps.Polarsteps-2.3-2.3.2.dSYM.zip'...
INFO [2019-01-03 09:56:34.08]: $ unzip -qo /Users/hernan/Projects/Polarsteps/sled/com.polarsteps.Polarsteps-2.3-2.3.2.dSYM.zip
INFO [2019-01-03 09:56:34.32]: Uploading '892973D1-F54F-3192-9CCF-7813E636EFC9.dSYM'...
DEBUG [2019-01-03 09:56:34.32]: upload_dsym using command: /Users/hernan/Projects/Polarsteps/sled/Pods/Fabric/upload-symbols -a 05fcd0e25cb44ff7c3b303fa8c2672ce0c762637 -p ios /private/var/folders/43/zfgk09cj3dd6klwdh79zdjcw0000gn/T/d20190103-1501-19j9ciu/892973D1-F54F-3192-9CCF-7813E636EFC9.dSYM
INFO [2019-01-03 09:56:36.33]: Uploading 'C2C6AA48-5F8F-3595-943E-77DFD5914BF2.dSYM'...
DEBUG [2019-01-03 09:56:36.33]: upload_dsym using command: /Users/hernan/Projects/Polarsteps/sled/Pods/Fabric/upload-

That whole flow goes for ~1 hour.
Hope this logs helps.
Thanks
H.


Fix crate version: 0.11 -> 0.10

The crate version was already bumped. We never released 0.10, hence there's no need to jump straight from 0.9 to 0.11.

@thomastaylor312 I just noticed, before tagging 0.11, that we never had the 0.10 release.


封装 mongodb eloquent

简单封装 mongodb eloquent, 方便业务中使用 mongodb

Is this still in development? I search hard any mysql alternatives like postgresql or mongodb, is there possibility that at least one of these two will be available in Hyperf3? Postgresql is much better in use than mysql, mongodb is much faster which correlates with swoole/hyperf speed orientating.
As always, very appreciate all of the hard work you do guys, i research hyperf last 4 month and the only thing i can say - bravo! Already write 70% of template project with all of the required thing that usual project need, simplicity of coding and beauty of code in this framework very impress 👍


force quote strings with spaces

Hi,
libreoffice version 4 (yeah, it's ancient ...) does not import fields with embedded whitespaces correctly. For instance a field with contents  "hi" there will be exported to  ;""hi"" there; , but libreoffice does not honour the seperator tripping over later fields.
Even Excel 2010 does not import  ;""hi"" there; correctly: It displays the double quote chars, not a single one.
With the supplied patch, the field will be exported as ;"""hi"" there"; which leads to correct exports in both libreoffice 4 and excel 2010.

Errr, The travis-ci error seems to be unrelated to my patch?


Add TraceEventInfo for TraceItem

This adds a new TraceItem::EventType union member - TraceEventInfo. This allows event info for invocations of a trace or tail worker to show up when tailing it (i.e. attaching a tail to a tail worker).
TraceEventInfo only contains an array "traces" of objects with a single "scriptName", i.e. the script that the script you're tracing was tracing. There's hypothetically more that could be included on these items, but any sort of recursive could ballon the size of these events or even get into circular references, so it's kept simple for now.

I have read the CLA Document and I hereby sign the CLA

This work is to ultimately support a wrangler tail session on a tail worker - without a differentiating event on the TraceItem, the tail session does not know what to do with the trace and drops it.
Additionally, the question remains as to whether the "traces" property on the TraceEventInfo should actually be "tails" or "tailItems" (the naming story doesn't seem to be settled there)

👏 @matthewdavidrodgers

this probably needs to hold a sec, we probably want to change "traces" per product decisions

this probably needs to hold a sec, we probably want to change "traces" per product decisions

Updated to change "traces" to "consumedEvents" as well as updating class names (TraceEventInfo -> TailEventInfo and TraceEventInfo::TraceItem -> TailEventInfo::TailItem) so that generated ts types match product names better.
This is now ready to go


Promote ViewPose-related APIs.

As discussed in #4707, the ViewPose APIs were mostly @internal for some reason. They also lacked documentation.
Also relevant to that discussion, prevent ViewDetails.clipVector setter from doing unnecessary work and raising events when the clip didn't actually change.

@skirby1996 @calebmshafer please notify me if you create the 3.5 release branch before this merges - I'll have to backport it.


Chapter 2.3 too large

Chapter 2.3, Objects and Control Flow is too large and unfocused.  It would be better to split the control flow exercises out to their own chapter, and the Struct exercises to another, allowing a full chapter entirely focused on CLOS.  Chapters on Control Flow and Structs might fit better in Part One.
The single exercise on the Meta-Object Protocol is also deficient; it should serve merely as an introduction to the subject, with an extra credit chapter following immediately after to present MOP in full.

Additional notes for this issue—
Migrate to Part 1, separate chapters on:

Structs
Control Flow

Expand 2.3 into separate chapters on:

Generic Programming (incl. Generic Functions + Methods)
Classes, Inheritance, and more CLOS Goodies
the Meta-Object Protocol

The MOP chapter can be closer to the end of Part Two.


Test new circleci config

Just seeing if this works.

(narrator: it doesn't)
I should blacklist gh-pages.


qiskit-terra 0.21.2 incompatible installation error

When installing qiskit-research, I get the following message:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. qiskit-research 0.1.dev399+g88b5dec requires qiskit-terra==0.21, but you have qiskit-terra 0.21.2 which is incompatible.
Is the dependency such that qiskit-research will not work with terra 0.21.2? If I try to downgrade terra, pip says that qiskit 0.37.2 requires terra 0.21.2.

I've relaxed the qiskit-terra requirement. Please merge main and try again.

Closing as this is likely fixed. Let me know if you still have issues.


⚠ Bofrost.be has degraded performance

In 9e6211a, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 998 ms

Resolved: Bofrost.be performance has improved in 768a68a after 9 minutes.


Error message in prod when uploading supply quotation form, only experienced by one user.

Error message in prod when uploading supply quotation form, only experienced by one user.:

From error logs it looks like this is the line that throws the error https://github.com/LSFLK/MedicinesforLK-AdminAPI/blob/336e8f9efd7731aeae1b3dbc84c444ab9aab9fda/csv_processor.bal#L97

Basically it looks like there was a period that dosn't follow the format mm yyyy.

We understood that this was due to accidentally edited data in the supply quotation csv form. We sent the user the correct CSV file. This error did not persist.


run Alphafold locally

Hi there,
I'm running Alphafold on a computer cluster, I wanted to make a PAE plot like those shown on Alphafold database and colab results. Where are these PAE data? Which file should I use?
Thanks

It's in result_model_{1,2,3,4,5}.pkl, a pickle file. You can write a script to draw the figure on cluster or download it.

Present only if using pTM models: predicted pairwise aligned errors (predicted_aligned_error contains a NumPy array of shape [N_res, N_res] with the range of possible values from 0 to max_predicted_aligned_error, where 0 means most confident). This can serve for a visualisation of domain packing confidence within the structure.

In the end of #92, there is a guideline on how to make similar plots. But I did not figure out how to # Color the structure by per-residue pLDDT and # Display lines at chain boundaries.

It's in result_model_{1,2,3,4,5}.pkl, a pickle file. You can write a script to draw the figure on cluster or download it.

Present only if using pTM models: predicted pairwise aligned errors (predicted_aligned_error contains a NumPy array of shape [N_res, N_res] with the range of possible values from 0 to max_predicted_aligned_error, where 0 means most confident). This can serve for a visualisation of domain packing confidence within the structure.

@Zuricho I only find PAE data in multimer results, do you know how to get these data for a monomer run? How do I know if I'm running using pTM models or not?
Thanks in advance.

Hi @ttianchen ! You can specify the models used by issuing the --model_names=model_1_ptm,model_2_ptm,model_3_ptm,model_4_ptm,model_5_ptm flag. You can also use AlphaFold Multimer (2.1.0) for monomers by issuing the flag --model_preset=monomer_ptm.
To plot results, you might find this software that I wrote helpful: https://github.com/mattarnoldbio/alphapickle

Hi @ttianchen ! You can specify the models used by issuing the --model_names=model_1_ptm,model_2_ptm,model_3_ptm,model_4_ptm,model_5_ptm flag. You can also use AlphaFold Multimer (2.1.0) for monomers by issuing the flag --model_preset=monomer_ptm. To plot results, you might find this software that I wrote helpful: https://github.com/mattarnoldbio/alphapickle

@mattarnoldbio Thanks, I'll give it a try.


Is it really work with Palwolrd?

Both Single mode and Interactive mode will report i/o timeout and exit after executing THE FIRST command and printing the output in 10 seconds.

rcon.yaml
palworld:
  address: "<IP_ADDRESS>:25575"
  password: "xxx"
  log: "palworldRCON.log"
  type: "rcon"
  timeout: "1s"

It works, i used today on my server and i did not get this timeout error.
It's something on your own.

It works, i used today on my server and i did not get this timeout error. It's something on your own.
Try increases this timeout.

I tryed 60s, Still exit in 10s.

对中文支持有问题，如果都是英文用户就不会有这个问题

对中文支持有问题，如果都是英文用户就不会有这个问题

我还以为你说的是系统环境，刚刚看了下似乎是因为数据中有中文字符

It seems to be caused by non-ascii characters in the data.
Wait me to recheck at midnight.

仔细研究了一下，应该是PalWrold服务器的问题，packet size与实际的不符

Experiencing the same issue with non-ASCII characters in ShowPlayers command, seems like the few last bytes are being cut-off (the Steam UID of the last player is not fully formed) and the command times-out. Any ideas on how to overcome this issue?

Experiencing the same issue with non-ASCII characters in ShowPlayers command, seems like the few last bytes are being cut-off (the Steam UID of the last player is not fully formed) and the command times-out. Any ideas on how to overcome this issue?

It can be confirmed that it is a problem with the palworld server, and we should only have to wait for the official to fix this bug for the time being.
However, if it needs to be used in the business, I made a tool palworld-server-tool to alleviate this problem through exception handling and database.

Just to confirm, I'm having the same issue with the high ascii characters, etc.


Lose focus of smtp email input

Description
Lose focus from SMTP email input.
Changes
Screencast from 27-10-24 14:31:34.webm
Related Issues

https://github.com/threefoldtech/tfgrid-sdk-ts/issues/3540

Checklist

[ ] Tests included
[ ] Build pass
[ ] Documentation
[x] Code format and docstrings
[x] Screenshots/Video attached (needed for UI changes)

Please address unsuccessful check


Changes from master related to routes and dhcp

Remove route fix script as route issue is fixed in latest plugin
Remove dhcp hotfixes as not needed
Allow multiple clusters (dhcpd) on same shared network

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: yussufsh
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [yussufsh]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/cc @bpradipt @Prajyot-Parab

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Prajyot-Parab, yussufsh
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Prajyot-Parab,yussufsh]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: bpradipt, Prajyot-Parab, yussufsh
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Prajyot-Parab,bpradipt,yussufsh]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Add latent prob and latent rng functions for hmm

Summary
Solves issue #1846. Adds two functions for hidden Markov models with discrete latent states which take values over {1, ..., K}.
The first function, hmm_latent_marginal_prob(), returns the matrix of posterior probabilities for each latent variable across all states, {1, ..., K}. Because the latent variables are not independent, we make it clear that these are marginal probabilities and should therefore not be used to sample latent variables. The outcome is discrete, therefore there is no differentiation.
The second function, hmm_latent_rng(), samples latent variables from their posterior distribution.
These two functions take in the same arguments as hmm_marginal_lpdf(). The arguments are checked using a new function, hmm_check().
Tests
For hmm_latent_marginal_prob, we test the probabilities for the simple cases where we have two states, K = 2, and the transition matrix (i) always transitions to the first state and (ii) is the identity matrix. In (ii), we set the observational density to be the same for both states, meaning the posterior probability is determined by the initial state, rho.
For hmm_latent_rng, we test the function for case (ii). The identity transition matrix implies the latent states are all identical, so it suffices check this equality and then examine the distribution of the first state. This distribution is Bernoulli, parameterized by rho, and, following the example of bernoulli_rng_test.cpp, we use a chi squared test.
I'm open to running more tests.
Release notes
Add two functions for hmm models that (i) evaluate the marginal posterior probability of each latent state and (ii) sample latent states from their posterior distribution.
Checklist

[x] Math issue #(1846)

[x] Copyright holder:  Charles Margossian, Columbia University and Michael Betancourt, Symplectomorphic, LLC
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[ ] the basic tests are passing

[x] unit tests pass (to run, use: ./runTests.py test/unit/math/prim/prob/hmm_marginal_test.cpp, test/unit/math/prim/prob/hmm_latent_marginal_prob_test.cpp,
test/unit/math/prim/prob/hmm_latent_rng_test.cpp,
test/unit/math/prim/err/hmm_check.hpp)
[ ] header checks pass, (make test-headers)
[ ] dependencies checks pass, (make test-math-dependencies)
[ ] docs build, (make doxygen)
[x] code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

Charles---is it you or Columbia that owns your copyright?  For researchers
it's Columbia, but I'm not sure about grad students.
Also, I can review this later.
On Wed, May 6, 2020 at 1:58 AM Stan buildbot<EMAIL_ADDRESS>wrote:

Name Old Result New Result Ratio Performance change( 1 - new / old )
gp_pois_regr/gp_pois_regr.stan 5.14 5.11 1.01 0.63% faster
low_dim_corr_gauss/low_dim_corr_gauss.stan 0.02 0.02 0.98 -1.8% slower
eight_schools/eight_schools.stan 0.09 0.09 1.02 1.54% faster
gp_regr/gp_regr.stan 0.22 0.23 0.99 -0.65% slower
irt_2pl/irt_2pl.stan 6.49 6.45 1.01 0.69% faster
performance.compilation 86.95 84.57 1.03 2.74% faster
low_dim_gauss_mix_collapse/low_dim_gauss_mix_collapse.stan 7.53 7.54 1.0 -0.17%
slower
pkpd/one_comp_mm_elim_abs.stan 20.27 20.05 1.01 1.07% faster
sir/sir.stan 92.05 94.75 0.97 -2.93% slower
gp_regr/gen_gp_data.stan 0.05 0.05 0.96 -3.99% slower
low_dim_gauss_mix/low_dim_gauss_mix.stan 2.98 3.06 0.97 -2.77% slower
pkpd/sim_one_comp_mm_elim_abs.stan 0.32 0.31 1.03 3.21% faster
arK/arK.stan 1.74 1.75 1.0 -0.38% slower
arma/arma.stan 0.76 0.77 0.99 -1.33% slower
garch/garch.stan 0.56 0.57 0.99 -0.99% slower
Mean result: 0.996975759835
Jenkins Console Log
https://jenkins.mc-stan.org/job/Math Pipeline/view/change-requests/job/PR-1868/4/consoleFull
Blue Ocean
https://jenkins.mc-stan.org/blue/organizations/jenkins/Math Pipeline/detail/PR-1868/4/pipeline
Commit hash: a241ad0
https://github.com/stan-dev/math/commit/a241ad0f20d187d8ba6c29b2f297d31ecceb177c
Machine information ProductName: Mac OS X ProductVersion: 10.11.6
BuildVersion: 15G22010
CPU:
Intel(R) Xeon(R) CPU E5-1680 v2 @ 3.00GHz
G++:
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr
--with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 7.0.2 (clang-700.1.81)
Target: x86_64-apple-darwin15.6.0
Thread model: posix
Clang:
Apple LLVM version 7.0.2 (clang-700.1.81)
Target: x86_64-apple-darwin15.6.0
Thread model: posix
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/math/pull/1868#issuecomment-624456734, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZ2D76D3BXASHF7QHP7RDDRQD4BRANCNFSM4MZ6RBOQ
.

This branch should now be ready for a final review.

Thanks!  I probably won't be able to get to this before Thursday morning, but can do it then.

@bob-carpenter can I get a final review for this? It should be pretty much ready.

Sorry---spaced reviewing this.  There seems to be a conflict in the code now, but just in the HMM marginal lpdf, so no idea where it could've come from.

Conflict resolved. Atom actually has an amazing feature for this!


Stop multiple form submissions

Is there a best practice solution for this issue with redux-form.  I am not sure that I can trust that "submitting" is set fast enough.

Do you return a Promise in onSubmit method? Otherwise form will think that submit is finished and set submitting to false

I am returning a Promise in the onSubmit so I do have access to the
"submitting" variable.  I was just not sure it got set fast enough to
prevent a double submission.
On Mon, Apr 11, 2016 at 8:08 AM Umidbek Karimov<EMAIL_ADDRESS>wrote:

Do you return a Promise in onSubmit method? Otherwise form will think
that submit is finished and set submitting to false
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/erikras/redux-form/issues/795#issuecomment-208364969

Yes it's set instantly so no double submission.

So I would have to check the status of submitting in my onSubmit handler?

@nmaves That's how I've done it in the past. You could also disable your button by passing in disabled={submitting}


TypeScript types

I have a prototype implementation of types for this package, with some type-level shenanigans so that you get exact types on the result as long as you pass the config directly to parseArgs. E.g.:
let { values, positionals } = parseArgs({
  options: {
    foo: { type: 'string', multiple: true },
    bar: { type: 'boolean' },
    evil: { type: 'string', multiple: Math.random() < 0.5 },
  },
});
let foo: string[] = values.foo; // works
let bar: boolean | undefined = values.bar; // works
let evil: string[] | string | undefined = values.evil; // if we can't precisely infer `multiple`, we can't say if it's an array or not
positionals[0]; // error: since we did not explicitly specify `allowPositionals: true`, the `positionals` array must be empty

Any feedback before I submit them upstream? You can play around with the types in the playground linked, no need to install anything.

The magic to make it work is a bit opaque to me, but the results look good from experimenting. The strict: false ones are annoyingly inexact, but look accurate! And careful callers will need to cope.

@bakkot the types seem solid to me, I appreciate that there are useful affordances, e.g., having typing for arrays, having the array default to empty if allowPositionals not set.
@bakkot could we publish the types to both to node:util and to pkgjs/parseargs in DefinitelyTyped, alternatively is there an easy way to for us to reference the node:util types when using parseArgs, and we can document this in the README?

There’s no easy way in DT for one package to reference the types for another, so the best approach i think is to duplicate them in both DT packages.

@bcoe Since you control parseArgs, you can include the types for it in the package itself rather than putting them on DefinitelyTyped. And in that case, yes, you can re-export the types for the version of parseArgs in  node:util from DefinitelyTyped, once those exist.
That said, it looks like types from 18.0.0 are still WIP, so I'm probably not going to submit these for util.parseArgs for a while yet. Maybe it makes sense to just provide them for pkgjs/parseargs for now? And in that case, would you be OK with having them live in this repo instead of DefinitelyTyped for the moment?

I find it vastly superior for types to be in DT instead of the package directly, since it avoids conflating the semver of the implementation with that of the types.

My comments are at a non-expert level.
To keep the version numbers sane and allow parseArgs package to include changes which have not yet landed in node, I was expecting separate type definitions (even it matching) for parseArgs package and node:util. Rather than one referencing the other.
As for whether to include in package, a comment each way!
I'm not concerned about the conflation of types and code by publishing within package. I consider the types part of the package.
However, the TypeScript publishing guidance, https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html#handbook-content says:

If your types are generated by your source code, publish the types with your source code. Both TypeScript and JavaScript projects can generate types via declaration.
Otherwise, we recommend submitting the types to DefinitelyTyped, which will publish them to the @types organization on npm.

Nice work @bakkot!! I copied your TS Playground and included some light suggestions, specifically:

Copy/pasted the Exact and IsEqual utility types from type-fest

Use Exact to error on unknown config properties
Use IsEqual to infer various boolean configs e.g. IsStrict, IsAllowPositionals, IsMultiple

Restructured all type conditions to avoid negated types (e.g. IsStrict extends true : true-branch : false-branch)
Tentatively renamed inference types as it is common to type import them in scripts and imo would be a good idea to establish a solid naming convention

@aaronccasanova Neat! Comments:

Re: "Shouldn't foo values also have undefined"
Uhh I guess you're right. I assumed that multiple options would be present as an empty array if not passed, but that doesn't seem to be the case.

Your changes have broken some of the types. Specifically, evil is now inferred as string | undefined, whereas the correct type is string[] | string | undefined (because the point of the evil property is that we don't know if it's multiple or not). The ExtractIsStrict thing you're doing is meaningfully different from the IfDefaultsTrue and IfDefaultsFalse helpers I had, which handle true, false, and boolean (i.e. present but not known to be either true or false) as distinct cases.

I assumed that multiple options would be present as an empty array if not passed, but that doesn't seem to be the case.

Yeah, we don't traverse the config and set defaults on the parsed results. The update is simply adding undefined to the true-branch of IsMultiple extends true:

Specifically, evil is now inferred as string | undefined, whereas the correct type is string[] | string | undefined

I'm seeing the correct types.

The ExtractIsStrict thing you're doing is meaningfully different from the IfDefaultsTrue and IfDefaultsFalse helpers I had, which handle true, false, and boolean (i.e. present but not known to be either true or false) as distinct cases.

We can confidently infer strict since we default to true and validate the input is a boolean. My thinking was we only have to check is if the input is explicitly false but perhaps there are holes in that logic.

I'm seeing the correct types.

That's because you're looking at a variable which is explicitly annotated with that type. Look at the type for values.evil (or remove the string[] from the type annotation and see that it still checks).

We can confidently infer strict since we default to true and validate the input is a boolean. My thinking was we only have to check is if the input is explicitly false but perhaps there are holes in that logic.

The hole is, knowing that it is definitely a boolean and is not known to be true does not tell you it's definitely false. The type system might just not be able to tell which it is.

Oh I see! Hmm now I'm wondering if that applies to all the Extract default utilities in my prototype.

For strict and allowPositionals it doesn't end up mattering because the types for "not know to be strict" are the same as the types for "known not to be strict", but the distinction is relevant for multiple.

Welp, I totally understand the rationale for IfDefaultsTrue and IfDefaultsFalse now! 👍 I love the composition in ParsedPositionals:

I tested every permutation and it's very robust 👏
Here is an updated prototype reverting the IsEqual/Extract utilties. This version includes:

Updated naming conventions
Errors for unknown config properties
Proposed type fix for values.foo when the option is not provided to the CLI

As mentioned above, these are light suggestions so feel free to dismiss 🙂

Nice, LGTM.

There is not currently any TSDoc, or indeed JSDoc, for offering guidance beyond the types?
For example in Visual Studio Code, where I think the documentation is coming via autodownloaded TypeScript definition files, I see rich assistance for path.resolve:

Whereas currently for parseArgs I see raw:

@shadowspawn Good catch, updated with the description from the readme (slightly wordsmith'd for this context):
/**
 * Provides a high-level API for command-line argument parsing. Takes a
 * specification for the expected arguments and returns a structured object
 * with the parsed values and positionals.
 *
 * `config` provides arguments for parsing and configures the parser. It
 * supports the following properties:
 *
 *   - `args` The array of argument strings. **Default:** `process.argv` with
 *     `execPath` and `filename` removed.
 *   - `options` Arguments known to the parser. Keys of `options` are the long
 *     names of options and values are objects accepting the following properties:
 *
 *     - `type` Type of argument, which must be either `boolean` (for options
 *        which do not take values) or `string` (for options which do).
 *     - `multiple` Whether this option can be provided multiple
 *       times. If `true`, all values will be collected in an array. If
 *       `false`, values for the option are last-wins. **Default:** `false`.
 *     - `short` A single character alias for the option.
 *
 *   - `strict`: Whether an error should be thrown when unknown arguments
 *     are encountered, or when arguments are passed that do not match the
 *     `type` configured in `options`. **Default:** `true`.
 *   - `allowPositionals`: Whether this command accepts positional arguments.
 *     **Default:** `false` if `strict` is `true`, otherwise `true`.
 *
 * @returns The parsed command line arguments:
 *
 *   - `values` A mapping of parsed option names with their string
 *     or boolean values.
 *   - `positionals` Positional arguments.
 *
 */

Took another pass and caught two more edge cases:

An empty config object should resolve empty parse results e.g.

const results = parseArgs()
const results = parseArgs({})

type ActualResults = {
  values: { [longOption: string]: string | boolean | string[] | boolean[] | undefined }
  positionals: string[];
}

type ExpectedResults = {
  values: {}
  positionals: [];
}

strict:false and multiple: true should resolve(string | boolean)[] instead of string[] | boolean[] e.g.

// Dynamic config
const config: Config = {
  strict: false,
  options: { foo: { type: 'string', multiple: true } }
}
const {values} = parseArgs(config)

type ActualValues = {
  [longOption: string]: string | boolean | string[] | boolean[] | undefined
}

type ExpectValues = {
  [longOption: string]: string | boolean | (string | boolean)[] | undefined
}

Nice!
Re: tests, one minor nit: I find it hard to read when there's non-local aliases for the actual results. E.g.
Expect<IsEqual<ParseArgs<{ strict: false }>['positionals'], ParsePositionals>>

vs
Expect<IsEqual<ParseArgs<{ strict: false }>['positionals'], string[]>>

or
type ExpectedValues = {
  foo: ParseResultsValue<string>;
  bar: ParseResultsValueMultiple<boolean>;
  baz: ParseResultsValueMultipleUnknown<boolean>;
}

vs
type ExpectedValues = {
  foo: string | undefined;
  bar: boolean[] | undefined;
  baz: boolean[] | boolean | undefined;
}

Totally! This hit to readability also occurs in the usage...

Perhaps it's best to scrap the ParseResults* utilities. I mainly initialized them to establish a relationship between the results inference types and the test cases and avoid human error (i.e. typos).
Here is an update removing the extraneous ParseResults* utilities.

Note: If folks want to test these types locally simply copy/paste the entire playground into an index.d.ts file at the root of the parseArgs repo and add this minimal tsconfig.json:
{
  "compilerOptions": {
    "strict": true,
    "allowJs": true,
    "checkJs": true
  }
}

The visible type names might need to be more qualified to disambiguate when used in node:util?
For example, currently have:
type ConfigOptions = { [longOption: string]: OptionConfig };

(Noticed when testing using copy-paste instructions from above, thanks.)

@bakkot Great job!
It looks like v18 of @types/node is already published. Perhaps it’s time to add types for parseArgs() as well?

@mrazauskas I'm waiting on https://github.com/pkgjs/parseargs/pull/129 to land so we can do the types all at once. But if that stalls much longer I'll open a PR to DefinitelyTyped, yeah.

OK, node PR landed. Types need to be updated to recognize the optional boolean in the config and to support the new tokens property in the output (which should be omitted if the tokens boolean is definitely absent or is false, present if it is definitely true, and otherwise optional). The type for tokens should be something like
type Token =
  | { kind: 'option', index: number, name: string, rawName: string, value: string | undefined, inlineValue: boolean | undefined }
  | { kind: 'positional', index: number, value: string }
  | { kind: 'option-terminator', index: number }
type Tokens = Token[]

It's actually possible to do way better than that for option tokens if the options config is passed; I will play with it a bit and see how good I can get it.

Opened https://github.com/DefinitelyTyped/DefinitelyTyped/pull/61512 with the types roughly as discussed here (except with good types for tokens. Would appreciate any reviews on that PR.

A whole lot of accurate typing assistance, thanks @aaronccasanova and @bakkot .

parseArgs is now available in @types/node@18.
A PR has been opened to copy these for @pkgjs/parseargs:

https://github.com/DefinitelyTyped/DefinitelyTyped/pull/61997
https://github.com/DefinitelyTyped/DefinitelyTyped/pull/15919/files

Nothing for node 16 yet.

The new default in the input option configuration has not been added to types yet.


optimize joins and make iterators chainable to improve performance

Closes #63
With the optimization rule to squash joins into a single GitRelation we have the opportunity to make the iterators chainable to reuse the previous step to compute the next instead of computing most of them a lot of times, which will bring a considerable speedup to the overall usage of the SparkAPI.
This commit renders getFiles obsolete, but it will be kept for now for compatibility reasons (or convenience, in some cases).
What this implements is a way for the RootedRepoIterator to manage two iterators at the same time: the internal iterator (that is, the thing being iterated at the moment) and an optional previous iterator. For every row of the previous iterator, the internal iterator is loaded for that row and fully iterated until there are no more items. Then the previous iterator is advanced again and so on until the previous iterator is empty.
So, for example, to iterate files efficiently, we would have a BlobIterator, whose prevIter would be a CommitIterator, whose prevIter would be a ReferenceIterator, whose prevIter would be a RepositoryIterator.
The benefit of this is that if we have 500 repositories, but only 1 matches, only 1 repository will make it to the ReferencesIterator and so on, instead of having to iterate every single thing for every repository.
Only very specific filters are supported at the iterator level:

RepositoryIterator: by "id"
ReferenceIterator: by "repository_id" and "name"
CommitIterator: by "repository_id", "reference_name", "hash" and "index"
BlobIterator: no specific iterator-level filters, spark will take care of it, since this is the last step in every computation

The rest of the filters (or any condition that is not an "IN" or an "=") will be handled by spark, which means it will be slower because they will be processed only to be discarded in the end.

rebased and ready to be merged once our travis lord is green


Single param without equal sign or value shouldn't cause an empty result

See code here.
var sqs = require('simple-query-string')
  , query = '?key'
  , result = sqs.parse(query)

console.log(result)

// outputs: {}

// should output: { key: null }

Fixed in release 1.3.1!
Thanks!


Cannot find module 'babel-preset-env' from ...

Since i moved to gulp 4 i can't build vendor and custom js file because of this.
❌  ===> ERROR: Cannot find module 'babel-preset-env' from '/Applications/MAMP/htdocs/eranum/wp-content/themes/eranum'

Did you mean "@babel/env"?

Ah nevermind. I recreated the setup after upgrading to gulp4. Everything is now fine.
Sorry Ahmad ;)

Yes, just reinstall the latest version. You should be fine. It was an earlier error in v2.4 I think. Everything related to babel is not namespaced with @babel for obvious reasons after v7.


Fix: Check existence of template content before formatting SMS content

When there's no template code is selected in the SMS provider editor page, the formatted SMS body ended up with unnecessary characters.

This fix checks if the template code exists before formatting the code.
Note: Updated all places but only tested with Twillio as I only got Twillio account

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

@mdilshan you are adding the same code to each implementation. Why not add the code in https://github.com/casdoor/casdoor ?

Should make it in: https://github.com/casdoor/casdoor , closed here

@mdilshan you are adding the same code to each implementation. Why not add the code in https://github.com/casdoor/casdoor ?

Well the code is already duplicated ( Per each SMS provider ) in here, so went with the same pattern and only some SMS providers uses the template. So better to add it in here.


v1.6.3 Release

[x] Check that there are no outstanding issues / PR that block the release which have not been backported / addressed
[x] Update GitHub project and create v1.6.4 project
[x] Update PRs / issues that were added to the v1.6.3 project, but didn't make it into this release into the v1.6.4 project

[x] Issues marked with needs-backport/1.6
[x] PRs marked with needs-backport/1.6

[x] Push PR against the v1.6 release branch with the following items completed:

[x] Update the VERSION file to represent X.Y.Z+1
[x] Update Helm chart documentation

[x] update versions in install/kubernetes/quick-install.yaml
[x] update version tag in install/kubernetes/cilium/values.yaml

[x] Update the cilium_version and cilium_tag variables in examples/getting-started/Vagrantfile (we don't do this past v1.4 due to our need for custom iproute2 packaging)
[x] Update the AUTHORS file
[x] Generate the NEWS.rst addition based off of the prior release tag, add to NEWS.rst
[x] Add all modified files using git add and create a pull request with the title Prepare for release vx.y.z. Add the backport label to the PR which corresponds to the branch for which the release is being performed.

[x] Build cilium image and push to Dockerhub
[x] Build cilium-operator image and push to Dockerhub
[x] Build cilium-docker-plugin image and push to Dockerhub
[x] Upload binaries to S3
[x] Push tags to GitHub (v1.6.3, 1.6.3)
[x] Create a GitHub release with the following format:

Summary of Changes
------------------
**Important Bug Fixes**
**Enhancements**
**Documentation**
etc...
Changes
-------
```
<< contents of NEWS.rst for this release >>
```
Release binaries
----------------
<< contents of snippet outputed by uploadrev >>

[x] Preview the description and then publish the release
[x] Announce the release in the #general channel on Slack
[x] Bump the version of Cilium used in the Cilium upgrade tests to use the new release (not applicable to this release)
[x] Update the versions in REAMDE.rst
[ ] Update the external tools and guides to point to the released Cilium version:

[ ] kops (tracked by https://github.com/cilium/cilium/issues/9375 )
[ ] kubespray (tracked by https://github.com/cilium/cilium/issues/9374 )

Updates to downstream integrations are tracked by separate tickets now; closing this issue.


change JSON field names to camelCase

https://issues.redhat.com/browse/ECOPROJECT-253
Signed-off-by: Yaron Dayagi<EMAIL_ADDRESS>

Please run make generate manifests to update generated files.
Make sure that
https://github.com/jakub-dzon/k4e-operator/blob/35f1efee0d5f61e376db6e5d81e7028443a128ce/internal/yggdrasil/yggdrasil.go#L259
works correctly after the changes; I think it might be broken.

u mean device-worker and not Yggdrasil, correct?

Please run make generate manifests to update generated files.
Make sure that
https://github.com/jakub-dzon/k4e-operator/blob/35f1efee0d5f61e376db6e5d81e7028443a128ce/internal/yggdrasil/yggdrasil.go#L259
works correctly after the changes; I think it might be broken.

u mean device-worker and not Yggdrasil, correct?

Operator.
device-worker sends hardware information to operator in model defined by swagger.yaml and https://github.com/jakub-dzon/k4e-operator/blob/35f1efee0d5f61e376db6e5d81e7028443a128ce/internal/yggdrasil/yggdrasil.go#L259 function maps swagger model to CR model. All  utils.Copy calls might be problematic, because they marshal one data type to JSON and unmarshall it to another.


wip auth feature and settings sync

this needs to use stable JSON stringify in the settings watcher to prevent extra notifications H/T @101arrowz


Displaying a highlighted "custom" version of GABC underneath the text (MEI -> "custom" GABC). The highlighting should go on the pitches (or locs) rather than the syllables.

@martha-thomae For the query "a b c", this is output for the custom GABC.
(example 1)

(example 2)

What do you think? The code for this is a bit of a mess so I will have to make it more readable, but for now it works :)


Error building/running docker for V2

Hi there,
I am following instructions to build V2 on my local machine, and I see that compilation is successful.
However it fails during docker launch. This is a learning exercise for me to build software using GO.
Please find attached build logs.
Any help is appreciated.
Thanks.

vagrant@staffjoy-v2:~/golang/src/v2.staffjoy.com$ make dev-build
make clean
make[1]: Entering directory /home/vagrant/golang/src/v2.staffjoy.com' rm -rf vendor/ make[1]: Leaving directory /home/vagrant/golang/src/v2.staffjoy.com'
bash ci/build.sh
[WARN]	Lock file may be out of date. Hash check of YAML failed. You may need to run 'update'
[INFO]	Downloading dependencies. Please wait...
[INFO]	--> Found desired version locally cloud.google.com/go debdc0ca0113dd546ebebeb2000c9d938059f41d!
[INFO]	--> Found desired version locally github.com/certifi/gocertifi a61bf5eafa3aee233ec8043e9da052447e5463dd!
[INFO]	--> Found desired version locally github.com/dgrijalva/jwt-go d2709f9f1f31ebcda9651b03077758c1f3a0018c!
[INFO]	--> Found desired version locally github.com/dpapathanasiou/go-recaptcha 962f1d77fed91285eb86c988e3ae8e7948e554c8!
[INFO]	--> Found desired version locally github.com/elazarl/go-bindata-assetfs 9a6736ed45b44bf3835afeebb3034b57ed329f3e!
[INFO]	--> Found desired version locally github.com/fatih/structs dc3312cb1a4513a366c4c9e622ad55c32df12ed3!
[INFO]	--> Found desired version locally github.com/getsentry/raven-go 379f8d0a68ca237cf8893a1cdfd4f574125e2c51!
[INFO]	--> Found desired version locally github.com/go-gorp/gorp c87af80f3cc5036b55b83d77171e156791085e2e!
[INFO]	--> Found desired version locally github.com/go-sql-driver/mysql 0b58b37b664c21f3010e836f1b931e1d0b0b0685!
[INFO]	--> Found desired version locally github.com/gogo/protobuf a9cd0c35b97daf74d0ebf3514c5254814b2703b4!
[INFO]	--> Found desired version locally github.com/golang/appengine 926995697fa8241be2dc73eb318666e24f44ed51!
[INFO]	--> Found desired version locally github.com/golang/glog 23def4e6c14b4da8ac2ed8007337bc5eb5007998!
[INFO]	--> Found desired version locally github.com/golang/oauth2 3c3a985cb79f52a3190fbc056984415ca6763d01!
[INFO]	--> Found desired version locally github.com/golang/protobuf df1d3ca07d2d07bba352d5b73c4313b4e2a6203e!
[INFO]	--> Found desired version locally github.com/google/go-querystring 9235644dd9e52eeae6fa48efd539fdc351a0af53!
[INFO]	--> Found desired version locally github.com/google/google-api-go-client adba394bac5800ff2e620d040e9401528f5b7615!
[INFO]	--> Found desired version locally github.com/gorilla/context 08b5f424b9271eedf6f9f0ce86cb9396ed337a42!
[INFO]	--> Found desired version locally github.com/gorilla/csrf 50eb875b7d37289a5819742f0d60fa5c890fced9!
[INFO]	--> Found desired version locally github.com/gorilla/mux 0eeaf8392f5b04950925b8a69fe70f110fa7cbfc!
[INFO]	--> Found desired version locally github.com/gorilla/securecookie 667fe4e3466a040b780561fe9b51a83a3753eefc!
[INFO]	--> Found desired version locally github.com/gorilla/sessions ca9ada44574153444b00d3fd9c8559e4cc95f896!
[INFO]	--> Found desired version locally github.com/grpc-ecosystem/grpc-gateway a8f25bd1ab549f8b87afd48aa9181221e9d439bb!
[INFO]	--> Found desired version locally github.com/grpc/grpc-go 708a7f9f3283aa2d4f6132d287d78683babe55c8!
[INFO]	--> Found desired version locally github.com/intercom/intercom-go 2f809a5bfee1c01cbef2dd76453ef0f9123e289e!
[INFO]	--> Found desired version locally github.com/jteeuwen/go-bindata bbd0c6e271208dce66d8fda4bc536453cd27fc4a!
[INFO]	--> Found desired version locally github.com/keighl/mandrill 6a59523fcf7d27e9230141f0e2563ba976a92b8f!
[INFO]	--> Found desired version locally github.com/pkg/errors 645ef00459ed84a119197bfb8d8205042c6df63d!
[INFO]	--> Found desired version locally github.com/russross/blackfriday 5f33e7b7878355cd2b7e6b8eefc48a5472c69f70!
[INFO]	--> Found desired version locally github.com/shurcooL/sanitized_anchor_name 1dba4b3954bc059efc3991ec364f9f9a35f597d2!
[INFO]	--> Found desired version locally github.com/Sirupsen/logrus 4b6ea7319e214d98c938f12692336f7ca9348d6b!
[INFO]	--> Found desired version locally github.com/stretchr/testify f390dcf405f7b83c997eac1b06768bb9f44dec18!
[INFO]	--> Found desired version locally github.com/ttacon/builder 7f152c3cf4714fd6318739f8f3dbcd14c2a18b39!
[INFO]	--> Found desired version locally github.com/ttacon/libphonenumber 5cb77679a4c77d45f2496c9ed8e60b5eec03bb47!
[INFO]	--> Found desired version locally github.com/urfave/negroni fde5e16d32adc7ad637e9cd9ad21d4ebc6192535!
[INFO]	--> Found desired version locally golang.org/x/crypto 7682e7e3945130cf3cde089834664f68afdd1523!
[INFO]	--> Found desired version locally golang.org/x/net ffe101cce3477a6c6d8f0754d103bb0a84ec1266!
[INFO]	--> Found desired version locally golang.org/x/oauth2 3c3a985cb79f52a3190fbc056984415ca6763d01!
[INFO]	--> Found desired version locally golang.org/x/sys 8f0908ab3b2457e2e15403d3697c9ef5cb4b57a9!
[INFO]	--> Found desired version locally golang.org/x/time 711ca1cb87636abec28122ef3bc6a77269d433f3!
[INFO]	--> Found desired version locally google.golang.org/api adba394bac5800ff2e620d040e9401528f5b7615!
[INFO]	--> Found desired version locally google.golang.org/appengine 926995697fa8241be2dc73eb318666e24f44ed51!
[INFO]	--> Found desired version locally google.golang.org/grpc 708a7f9f3283aa2d4f6132d287d78683babe55c8!
[INFO]	--> Found desired version locally gopkg.in/intercom/intercom-go.v2 2f809a5bfee1c01cbef2dd76453ef0f9123e289e!
[INFO]	--> Found desired version locally github.com/davecgh/go-spew 2df174808ee097f90d259e432cc04442cf60be21!
[INFO]	--> Found desired version locally github.com/pmezard/go-difflib d8ed2627bdf02c080bf22230dbb337003b7aba2d!
[INFO]	Setting references.
[INFO]	--> Setting version for github.com/go-sql-driver/mysql to 0b58b37b664c21f3010e836f1b931e1d0b0b0685.
[INFO]	--> Setting version for github.com/dpapathanasiou/go-recaptcha to 962f1d77fed91285eb86c988e3ae8e7948e554c8.
[INFO]	--> Setting version for github.com/go-gorp/gorp to c87af80f3cc5036b55b83d77171e156791085e2e.
[INFO]	--> Setting version for github.com/gorilla/mux to 0eeaf8392f5b04950925b8a69fe70f110fa7cbfc.
[INFO]	--> Setting version for github.com/getsentry/raven-go to 379f8d0a68ca237cf8893a1cdfd4f574125e2c51.
[INFO]	--> Setting version for github.com/golang/glog to 23def4e6c14b4da8ac2ed8007337bc5eb5007998.
[INFO]	--> Setting version for github.com/golang/appengine to 926995697fa8241be2dc73eb318666e24f44ed51.
[INFO]	--> Setting version for github.com/gogo/protobuf to a9cd0c35b97daf74d0ebf3514c5254814b2703b4.
[INFO]	--> Setting version for github.com/certifi/gocertifi to a61bf5eafa3aee233ec8043e9da052447e5463dd.
[INFO]	--> Setting version for github.com/golang/oauth2 to 3c3a985cb79f52a3190fbc056984415ca6763d01.
[INFO]	--> Setting version for github.com/dgrijalva/jwt-go to d2709f9f1f31ebcda9651b03077758c1f3a0018c.
[INFO]	--> Setting version for github.com/fatih/structs to dc3312cb1a4513a366c4c9e622ad55c32df12ed3.
[INFO]	--> Setting version for github.com/elazarl/go-bindata-assetfs to 9a6736ed45b44bf3835afeebb3034b57ed329f3e.
[INFO]	--> Setting version for github.com/gorilla/context to 08b5f424b9271eedf6f9f0ce86cb9396ed337a42.
[INFO]	--> Setting version for github.com/gorilla/csrf to 50eb875b7d37289a5819742f0d60fa5c890fced9.
[INFO]	--> Setting version for github.com/gorilla/securecookie to 667fe4e3466a040b780561fe9b51a83a3753eefc.
[INFO]	--> Setting version for github.com/golang/protobuf to df1d3ca07d2d07bba352d5b73c4313b4e2a6203e.
[INFO]	--> Setting version for github.com/google/google-api-go-client to adba394bac5800ff2e620d040e9401528f5b7615.
[INFO]	--> Setting version for github.com/google/go-querystring to 9235644dd9e52eeae6fa48efd539fdc351a0af53.
[INFO]	--> Setting version for github.com/grpc/grpc-go to 708a7f9f3283aa2d4f6132d287d78683babe55c8.
[INFO]	--> Setting version for github.com/jteeuwen/go-bindata to bbd0c6e271208dce66d8fda4bc536453cd27fc4a.
[INFO]	--> Setting version for github.com/keighl/mandrill to 6a59523fcf7d27e9230141f0e2563ba976a92b8f.
[INFO]	--> Setting version for github.com/gorilla/sessions to ca9ada44574153444b00d3fd9c8559e4cc95f896.
[INFO]	--> Setting version for github.com/stretchr/testify to f390dcf405f7b83c997eac1b06768bb9f44dec18.
[INFO]	--> Setting version for github.com/intercom/intercom-go to 2f809a5bfee1c01cbef2dd76453ef0f9123e289e.
[INFO]	--> Setting version for github.com/grpc-ecosystem/grpc-gateway to a8f25bd1ab549f8b87afd48aa9181221e9d439bb.
[INFO]	--> Setting version for github.com/pkg/errors to 645ef00459ed84a119197bfb8d8205042c6df63d.
[INFO]	--> Setting version for github.com/ttacon/builder to 7f152c3cf4714fd6318739f8f3dbcd14c2a18b39.
[INFO]	--> Setting version for github.com/russross/blackfriday to 5f33e7b7878355cd2b7e6b8eefc48a5472c69f70.
[INFO]	--> Setting version for github.com/shurcooL/sanitized_anchor_name to 1dba4b3954bc059efc3991ec364f9f9a35f597d2.
[INFO]	--> Setting version for github.com/Sirupsen/logrus to 4b6ea7319e214d98c938f12692336f7ca9348d6b.
[INFO]	--> Setting version for github.com/urfave/negroni to fde5e16d32adc7ad637e9cd9ad21d4ebc6192535.
[INFO]	--> Setting version for github.com/ttacon/libphonenumber to 5cb77679a4c77d45f2496c9ed8e60b5eec03bb47.
[INFO]	--> Setting version for golang.org/x/crypto to 7682e7e3945130cf3cde089834664f68afdd1523.
[INFO]	--> Setting version for github.com/davecgh/go-spew to 2df174808ee097f90d259e432cc04442cf60be21.
[INFO]	--> Setting version for golang.org/x/net to ffe101cce3477a6c6d8f0754d103bb0a84ec1266.
[INFO]	--> Setting version for golang.org/x/oauth2 to 3c3a985cb79f52a3190fbc056984415ca6763d01.
[INFO]	--> Setting version for google.golang.org/api to adba394bac5800ff2e620d040e9401528f5b7615.
[INFO]	--> Setting version for github.com/pmezard/go-difflib to d8ed2627bdf02c080bf22230dbb337003b7aba2d.
[INFO]	--> Setting version for golang.org/x/sys to 8f0908ab3b2457e2e15403d3697c9ef5cb4b57a9.
[INFO]	--> Setting version for google.golang.org/appengine to 926995697fa8241be2dc73eb318666e24f44ed51.
[INFO]	--> Setting version for gopkg.in/intercom/intercom-go.v2 to 2f809a5bfee1c01cbef2dd76453ef0f9123e289e.
[INFO]	--> Setting version for golang.org/x/time to 711ca1cb87636abec28122ef3bc6a77269d433f3.
[INFO]	--> Setting version for google.golang.org/grpc to 708a7f9f3283aa2d4f6132d287d78683babe55c8.
[INFO]	--> Setting version for cloud.google.com/go to debdc0ca0113dd546ebebeb2000c9d938059f41d.
[INFO]	Exporting resolved dependencies...

Target //www:docker up-to-date:
bazel-bin/www/docker-layer.tar
INFO: Elapsed time: 0.431s, Critical Path: 0.00s

INFO: Running command line: bazel-bin/www/docker
Skipping ed58ca89a41518132e9c36c4e1851c670c8bc5764b63c5b5444cd31606dbe1b1, already loaded.
Skipping 4f1262fa8ea8bbbec4ae8a63c61953dea599cfee97a55ad216cc56d0cca560ed, already loaded.
Skipping 041c32df74204140dc63efde1441a4883a9c6206056b8122c5dc07e3f0a0b89d, already loaded.
Tagging 041c32df74204140dc63efde1441a4883a9c6206056b8122c5dc07e3f0a0b89d as bazel/www:docker
Error parsing reference: "041c32df74204140dc63efde1441a4883a9c6206056b8122c5dc07e3f0a0b89d" is not a valid repository/tag: invalid repository name (041c32df74204140dc63efde1441a4883a9c6206056b8122c5dc07e3f0a0b89d), cannot specify 64-byte hexadecimal strings
ERROR: Non-zero return code '1' from command: Process exited with status 1.
make: *** [dev-build] Error 6

@rmalla1  Looks like Bazel isn't telling docker to tag it with "sha256:"
See this commit for fix: https://github.com/bazelbuild/bazel/commit/80ea129f7dfee37536110b2949c5a33f369fee10

For a quick fix locate the following in ci/dev-build.sh
# Run the build and upload to GKE
bazel run //$target:docker

and change it to:
# Run the build and upload to GKE
# bazel run //$target:docker
bazel build //$target:docker
cat bazel-bin/$(echo $target)/docker | sed -e 's/tag ${name}/tag sha256:${name}/' > .docker.v2
sudo mv .docker.v2 bazel-bin/$(echo $target)/docker
chmod +x bazel-bin/$(echo $target)/docker
bazel-bin/$(echo $target)/docker

This will add the sha256 tag appropriately then load all the docker layers like bazel run would have

Thanks Evan. It works now.