When there is a problem with one of the mailboxes, just skip it

What did you do?
When I set up multiple mailboxes, if there is a problem with one of the mailboxes, the logic here will reject the sending of notifications from all other normal mailboxes. Is this reasonable? Is it possible to skip the mailbox in question?
// notify/email/email.go
// Notify implements the Notifier interface.
func (n *Email) Notify(ctx context.Context, as ...*types.Alert) (bool, error) {
... ...
	for _, addr := range addrs {
		if err = c.Rcpt(addr.Address); err != nil {
			return true, errors.Wrapf(err, "send RCPT command")
		}
	}
... ...

What did you expect to see?
skip the email which has problem, and send messages to other normal emails
What did you see instead? Under which circumstances?
it will skip all emails.

I think this seems reasonable @magiceses, would you be open to the idea of a contribution?

I think we should just skip the email which is not normal after retry some times , and continue to send email to other emails.
there are some changes in my project:
// notify/email/email.go
// Notify implements the Notifier interface.
func (n *Email) Notify(ctx context.Context, as ...*types.Alert) (bool, error) {
... ...
	retryStrategy := []retry.Option{
		retry.Attempts(3),
		retry.Delay(time.Second),
		retry.DelayType(retry.FixedDelay),
	}
	for _, addr := range addrs {
		if err = retry.Do(func() error {
			if errRetry := c.Rcpt(addr.Address); errRetry != nil {
				return errRetry
			}
			return nil
		}, retryStrategy...); err != nil {
			level.Warn(n.logger).Log("msg", fmt.Sprintf("send RCPT command %s", err.Error()))
		}
	}
... ...

@gotjosh what do you think the idea?

On second thought, this is not as straightforward as I initially thought.
Basically, the returned boolean on Notify is to control whether we should retry or not. The return true as part of the existing logic means we'll attempt to retry the notification later.
However, this process is not incremental - if we try to execute an RCPT to 3 addresses and 1 fails, we'll attempt to sent them all over again.
I think the existing logic is correct in the sense that to preserve the integrity of the message we succeed the command in all mailboxes or none of them.
I'd need to gather substantial evidence that going with an incremental approach where perhaps the retry logic can keep track of which mailboxes are successful as we retry is a significant improvement as this would be quite an invasive change.
What are your thoughts on this?

I don't recall anything on top of my head. One reason could be that it's more explicit to fail the notification (say that the receiver has 3 recipients, 2 are invalid and the last person isn't on duty) and rely on the ``AlertmanagerClusterFailedToSendAlerts` alert to fix the problem early.
Having said that, the other approach makes sense too and I'd be ok with a new option to decide whether the receiver fails hard or tries its best. There still needs to be a metric to detect invalid recipients and alert on.

@gotjosh @simonpasquier  Excuse me, based on what has been discussed above, how should we proceed?
I prefer to modify the logic of this piece and skip the abnormal recipients after the receiver fails hard or tries its best.

I think we can introduce an option to enable the skipping of recipients as part of the receiver.

Recipients are part of an email type receiver, some invalid recipients should not affect other recipients receiving alerts, just like the way email servers handle it. So I think it's more reasonable to add some metrics for alerting admin, but it's unnecessary to introduce an option to control whether invalid recipients are skipped or not. 😊

I'd still prefer an option to control the behavior, we can always change the default over time and even get rid of it eventually after we're confident that it's what all users expect.

+1


LTS - ?

From prior comments it appears that muhqu is no longer supporting DTERM.  It is one of my favorite things about my Mac setup, I've been using it for 10 years and am about to move over to an M2.  I'm open to supporting the project financially so we can get long term support going.  My company does Qt programming in C++ so Objective C is outside of our area of expertise.  If anybody is interested in collaborating on this let me know.  Presumably somebody who knows how to compile DTERM and can add functionality via objective C.  You can write me via the contact information on my company website, cepuder.com.

Yes, you are right, I'm no longer supporting dterm as I have not used it for several years as I mostly use the integrated terminal of VS Code…
However, I've just checked out dterm from git and opened it in X Code 15 on my mac M1 running macOS 13 and it's compiling and running out of the box… The command line ./build.sh script seems broken, but it compiles from XCode UI.
I'm sorry, but I don't have an active apple developer profile, so I can not provide any signed binaries, but you might want to simply build it yourself.

@aburda I've just published a new release which I've build on my M1 mac… https://github.com/muhqu/dterm/releases/tag/1.7.86-33877ef
Let me know if it is working for you.

@muhqu - Excellent many thanks.  I'll give it a try.  I would also like to add some new functionality to DTERM, primarily a history command such that if you press the up arrow it will loop through prior commands, similar to how a terminal would work.  That said, I haven't actually updated my version of DTERM in several years so maybe in this latest release there are new functions.  I'm happy to pay to have the features added and still keep the product open source.

I just installed DTERM and it works well on an M2.  Reading through the prior comments, it seems the following would be good to do.
Here is my list of things it seems need to be done.  @muhqu, let me know if you'd be interested or if you are ok with forking if I find somebody to collaborate with.
Create a homebrew formula (Issue #22)
Make historical command text selectable and copyable (Issue #10)
Trusted certificate (Issue #5) - I could probably arrange this on my company account
setup a build server - My company has a TeamCity intance running on AWS if needed
Setup up/down arrows to move through history in DTERM (my request)
We might also want to change the name of the app since DTERM appears to be taken and makes it difficult to find in a search engine

@aburda just made some additional changes to fix layout issues and while doing that also made the last command selectable/copyable: https://github.com/muhqu/dterm/releases/tag/1.7.91-012c4bc
I appreciate that you want to support the project… but I don't have interest. Feel free to create a fork!

@muhqu Many thanks for the updates.  I'll test them shortly, mainly I'm glad that everything works.

I do hope someone takes over the fork. This is still a very good secret gem for macOS


Blog posts not ordered by date

Hi, The blog posts are ordered randomly. It would make sense to order them by date.

@nyejon Thanks for reporting! Fixed


Add more sensor examples

As asked on the openHAB forum by TommySharp.

4 examples are I think enough for now? Feel free to reopen if you don't think so.


Many errors and typos in the docs

Hi
There are many errors and typos in the http://angular.github.io/router docs.
The most critical in my opinion is the fact that the directive names were renamed:

router-view-port ->(should be) ng-viewport
router-view-port -> ng-link

The index.html in the first snippet has broken script includes:

<script src="/dist/router.es5.js"></script> -> <script src="/node_modules/angular-new-router/dist/router.es5.js"></script>
<script src="/app/app.js"></script> -> <script src="/app.js"></script>

also
<body ng-app="myApp" ... should be <body ng-app="app" ... as it is defined in app.js
componentLoader link should point to http://angular.github.io/router/$componentLoaderProvider instead of http://angular.github.io/router/componentLoaderProvider.
Typo in Let's male a home component that our app can route to. (male -> make)
When explaining adding home component, the script tag to include the component is <script src="./components/detail/detail.js"></script>, while it should be <script src="./components/home/home.js"></script>
The sentence _And add the controller's module as a dependency to our main module in app.js:_ is missing the closing tick for app.jsand thus it is not rendered ascode`.
No instruction for including detail component on the index.html (<script src="./components/detail/detail.js"></script>).
And I might have missed some.

Thanks for taking the time to point these out!
Actually, all of these have been fixed in master, I just haven't had a chance to roll out an update to the live site.


TypeError: Cannot read property 'style' of undefined

I get  this error when i try to mock, and my test file looks like this
import React from 'react';
jest.mock('react-native-autocomplete-input', () => 'Autocomplete')
import UserSearch from '../components/UserSearch';
import renderer from 'react-test-renderer';
describe('<UserSearch/>', ()=>{
 it('renders correctly', () => {
 const tree = renderer
 .create(<UserSearch />)
.toJSON();
 expect(tree).toMatchSnapshot();
});
})
The UserSearch compnent using Autocomplete library. And i get the error from where the library getting imported import Autocomplete from 'react-native-autocomplete-input';

Same here.  I ended up editing the react-native-autocomplete-input/index.js file and replacing ListView.propTypes.style with ViewPropsType.style, and it fixed the crash (although I don't know if that is a proper fix, probably not).  The ListView is deprecated anyway, so honestly should be replaced with a FlatList according to react native docs.

After migration to react-native 0.57 I  got issue with this also. Solution - remove this line listStyle: ListView.propTypes.style,

Same as @ViktorAksionov.

Should be fixed by #106


Quoridor Notations

It seems that the notation you use in Quoridor is not one that I have encountered.
The rows and columns are ordered fine (rows 1-9, columns a-i), but the starting player is at the bottom (starting at e9).
Neither in Glendenning's Notation nor in Modern Algebraic Notation this is the case.
I would be happy if you will consider changing the board orientation.
It is just that when looking at games and strategies for quoridor I can't match write it into the board because of this difference.
Thanks!

Tagging original contributor: @tewalds, can you reply?

I don't remember why the current choice was made. I think this matched some existing implementation or thesis, but seem to remember not really finding a standard. It's quite possible that either I missed the standard, implemented it badly or it has become more standardized since. Either way, I'm happy for the code to be updated with whatever the modern standard is. Feel free to send a PR, preferably with a reference to the standard in a comment. @lanctot Assuming this is changed, this should probably be mentioned in release notes in case someone depends on the existing direction with some pre-trained policy.

Works for me! Feel free to submit a PR @ronTohar1, and we'll import + merge it. Do you have a reference for the standard notation? If so, could you include it in the docs? (Point taken @tewalds about breaking backward compatibility, will surely do that for the next release, if this makes it in.)

Btw, if you're up for reviewing the code and know the rules well, I also remember there being uncertainty in the rules around jumping when there are more than 2 players. In particular if multiple players are in a line in a dead end, can a player jump more than one opponent's piece, or should they be forced to pass. I think we ended up deciding they must pass, mainly due to code complexity for this rare situation, but am open to a change if the wider quoridor community has passed a ruling.

Hah, https://github.com/deepmind/open_spiel/commit/c210cf3498f3a5a6ba50173ebb6a09f39ac637b7 looks related to this.

Btw, if you're up for reviewing the code and know the rules well, I also remember there being uncertainty in the rules around jumping when there are more than 2 players. In particular if multiple players are in a line in a dead end, can a player jump more than one opponent's piece, or should they be forced to pass. I think we ended up deciding they must pass, mainly due to code complexity for this rare situation, but am open to a change if the wider quoridor community has passed a ruling.

I agree with this choice. As far as I know, when there are more than 2 players it's not allowed to jump over 2 players so the pawn stuck must pass its turn.
As for the correct notations - Quoridor's notations as for what I have seen follow Glendenning's Notation (Mastering Quoridor (2005)).
There is also a site which contains very nice information about Quoridor such as strategies and "latest" news (stopped updating around 2016), and in this site there are notations similar to Glendenning's except for the walls placement notations.
Glendenning's notation suggest to write the up-left square to represent the wall and the site suggest to write the down-left square.
I would suggest going with Glendenning's approach as it is already implemented this way :).

Yes this is what I meant

Closing due to inactivity. Please re-open if you want to continue the discussion.


Dataset process script for DTU dataset

Hello!
Thanks for providing the script to process custom dataset,
Could you provide the code to generate points.npy and view_id.npy from the dtu dataset

Hello! Thanks for providing the script to process custom dataset, Could you provide the code to generate points.npy and view_id.npy from the dtu dataset

hi！Wuuu3511.I encountered a problem in configuring the environment. Can you share your dependencies and version with me. Thank you very much！


Add: build test function to save pdf locally

I used exactly the same data_example files for consistency @feder-cr


Fixed setting the new title on site copy

Description
Created function to change the name of the siteTitle of the created site to the new name, overwriting the old copied name.
Type of change
bug fix
Tests
In the admin panel of openstad copy a site and give it a new name. The name should be visible in the title when opening the website (both in page and in the tab)

new pr https://github.com/openstad/openstad-management-panel/pull/67 has the same changes but is based on development, disregard this one


Fix #5314: removed last param &NvContext from RtlVirtualUnwind function call

Resolves #5314

What should I pass as 8th arg to RtlVirtualUnwind function in place of &NvContext ?

Looks like #5747 is fixing the same issue?

@dilijev Can you help me with this 1 pending check? What have I done wrong?

@bhavayAnand9 You have done nothing wrong. This is a manual review that a team member needs to sign off before we merge your PR.

I will test this internally and merge once verification completes.

@bhavayAnand9 - Being "out of date" is not really a problem for us. However, hitting the "merge master" button does cause all of the CI checks to start over, so that will slow down your PR.

Hi @bhavayAnand9 - 5 out of 6 commits in this PR are merge commits or fixup commits. Could you please rebase this PR to a single commit on top of master?

@dilijev I tried squashing & rebasing but didn't work out well. I'm still learning Git, so If you don't mind can I close this PR and create a clean new one. Sorry for all the troubles.

@bhavayAnand9 Actually, there's no need to close your PR. This will be a good learning experience with Git and GitHub, and we're happy to help you learn as you contribute to ChakraCore. I'm writing up a quick guide to explain how to do this. I'll reply back with a link shortly.

https://github.com/Microsoft/ChakraCore-wiki/blob/b470bb214c141551a85d9ef30b798d356bbc782a/Rebasing-PRs.md


sync with compiler release

sync core with latest compiler release:

pub trait's semantic will be migrated to a different semantic, fully public traits that can be implemented outside should be marked as pub(open). Currently pub trait will trigger a warning, but its semantic is still fully public
.mbti output for trait impls is improved. impl are now grouped with type/trait definition, and the parameters of impl can now be displayed

Pull Request Test Coverage Report for Build 3831
Details

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

Totals

Change from base Build 3830:
0.0%

Covered Lines:
4342

Relevant Lines:
5414

💛  - Coveralls


metalink error on vagrant+ansible up.sh

The following error, although moves between nodes on subsequent runs, it has shown consistently on at least 1 node for each up.sh initiation.  This time it showed on node0.  wondering if there is something we can do to help this?  going to try to remove epel.repo prior to yum installs or possibly yum clean metadata after repo is installed????
fatal: [node0]: FAILED! => {"changed": true, "cmd": ["yum", "-y", "install", "wget", "screen", "git", "vim", "glusterfs-client", "heketi-client", "iptables", "iptables-utils", "iptables-services", "docker", "kubeadm"], "delta": "0:00:16.419865", "end": "2016-12-08 14:39:52.070970", "failed": true, "rc": 1, "start": "2016-12-08 14:39:35.651105", "stderr": "http://mirror.math.princeton.edu/pub/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel\nTrying other mirror.\nhttps://mirror.chpc.utah.edu/pub/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel\nTrying other mirror.\nhttp://mirror.symnds.com/distributions/fedora-epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel\nTrying other mirror.\nhttp://mirror.us.leaseweb.net/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel\nTrying other mirror.\nhttp://mirror.sfo12.us.leaseweb.net/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel\nTrying other mirror.\nhttp://mirrors.syringanetworks.net/fedora-epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel\nTrying other mirror.\nhttp://mirrors.mit.edu/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel\nTrying other mirror.\nhttp://mirror.cs.pitt.edu/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel\nTrying other mirror.\nhttps://pubmirror1.math.uh.edu/fedora-buffet/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel\nTrying other mirror.\nhttp://fedora-epel.mirror.lstn.net/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel\nTrying other mirror.\nhttp://ftp.osuosl.org/pub/fedora-epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel\nTrying other mirror.\nhttp://mirror.nexcess.net/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel\nTrying other mirror.\nhttp://mirror.sjc02.svwh.net/fedora-epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for epel\nTrying other mirror.\nhttp://mirror.oss.ou.edu/epel/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for

Moving the conversation form #58 here:
@obnoxxx, I think you were running into this issue. Could you weigh in on this? I'm not sure this is a bug in the vagrant setup, I think this is some sort of networking/DNS issue.

The fix in #61 does not fully fix it.  I'm getting repomd.xml does not match metalink for epel errors on at least one random nodes during the vagrant provision.  I can't actually get a successful provision after 4 attempts.

I managed to fix this by adding retry logic to the "install base packages" task.  It isn't pretty but I suspect there are some underlying network issues with the VMs it creates.  I occasionally get the docker pull tasks to fail too.  Or maybe it's just my network.
- name: install base packages
  command: yum -y install {{ install_pkgs }}
  register: task_result
  until: task_result.rc == 0
  retries: 5
  delay: 1

@ravishivt  - yeah, I was testing some retry logic as well on Friday but I couldn't get mine to work for some reason.  Thinks it's a good idea to have some retry logic in some key spots, I will add this in a PR...thanks!

@screeley44 Sounds great.  IMHO, the fixes in #61 should be reverted.  It adds complexity but doesn't improve the outcome.  In my tests, I had the same behavior when using or not using the additional logic in #61.

@ravishivt - agreed, will also revert those #61 changes

Just chiming in to say I like the more elegant retries solution. @screeley44, just a request to make sure the revert is its own commit. :)


Fox-notes finalized

[ ] now neutral, foxes will attack & leap at the player while running at their max speeds if provoked
[ ] new yellow variant for foxes spawning in plains, deserts and other non forest biomes
[ ] orange foxes will now spawn in taiga, savanna forest and other forest types
[ ] white foxes will remain in all snow-type biomes
[ ] foxes do not spawn on beaches/swamps/jungle or mesas

Biomes:
sub-class; arctic
is_cold
sub-class; yellow
is_plains
is_desert
sub-class; orange
is_forest
is_mountains

Are foxes still tamable? And what do you mean with "now neutral"? Will it also attack when trusted? Cause the vanilla code allows the fox to attack it's attackers back

TODO:

[ ] Registering
[ ] Spawning
[ ] Renderer

Wild foxes attack players when attacked
Tamed foxes will not fight back against players just like a tamed wolf
On Tue., Dec. 21, 2021, 11:41 a.m. DerToaster98, @.***>
wrote:

TODO:

Registering
Spawning
Renderer

—
Reply to this email directly, view it on GitHub
https://github.com/DerToaster98/ClassicHostiles/issues/30#issuecomment-998930405,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARFQ7AR6VKV3O5DE2C2K63LUSCU4XANCNFSM5GYKCJDA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

fox
sub-class; arctic
is_cold
sub-class; yellow
is_plains
is_desert
sub-class; orange
is_forest
is_mountains

By default you can't get near cats or foxes. I want it so you can walk toward them and hit them and they'll hit back
But if you sprint at them then they rn away until they're hit
They flee until provoked


Update Support Version

Symfony 5.3
Symfony 5.4
PHP 8.1

Codecov Report

Merging #36 (1412b24) into master (ed6b7f5) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##              master       #36   +/-   ##
===========================================
  Coverage     100.00%   100.00%
  Complexity        16        16
===========================================
  Files              5         5
  Lines             47        47
===========================================
  Hits              47        47

Continue to review full report at Codecov.

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

@khaperets can you please review?


MLS CLI

Summary
Updates the existing CLI example to work with MLS. Supported actions are:

Register
Create Group
List Groups
Send
List Group Messages
Add Group Member
Info
Clear

In order to support the Add Group Member command, I also added the ability to add members by wallet address to the MlsGroup struct.
TODO

I haven't added support for removing group members yet
Add support for listing group members, which could be included in each row of List Groups results

Looks good!
It works, but i'm not able to list-group-messages until after running 'list groups' with the user that was just added to a group:
/xli.sh --local --db user2.db list-group-messages $GROUP_ID
warning: use of deprecated method `tokio_rustls::rustls::RootCertStore::add_server_trust_anchors`: Please use `add_trust_anchors` instead
  --> xmtp_api_grpc/src/grpc_api_helper.rs:32:11
   |
32 |     roots.add_server_trust_anchors(webpki_roots::TLS_SERVER_ROOTS.0.iter().map(|ta| {
   |           ^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: `#[warn(deprecated)]` on by default

warning: `xmtp_api_grpc` (lib) generated 1 warning
    Finished dev [unoptimized + debuginfo] target(s) in 0.27s
     Running `/Users/insipx/Projects/xmtp/workspace-libxmtp/nm/mls-cli/target/debug/cli-client --local --db user2.db list-group-messages d48c0c94a532f1e2f1ccdfc80f7ebefc`
[2023-11-17T16:50:44Z INFO  cli_client] Starting CLI Client....
[2023-11-17T16:50:44Z INFO  cli_client] Recv
[2023-11-17T16:50:44Z INFO  cli_client] Using persistent storage: user2.db
thread 'main' panicked at examples/cli/cli-client.rs:197:18:
failed to find group: Generic("group not found")
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

/xli.sh --local --db user2.db list-groups
warning: use of deprecated method `tokio_rustls::rustls::RootCertStore::add_server_trust_anchors`: Please use `add_trust_anchors` instead
  --> xmtp_api_grpc/src/grpc_api_helper.rs:32:11
   |
32 |     roots.add_server_trust_anchors(webpki_roots::TLS_SERVER_ROOTS.0.iter().map(|ta| {
   |           ^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: `#[warn(deprecated)]` on by default

warning: `xmtp_api_grpc` (lib) generated 1 warning
    Finished dev [unoptimized + debuginfo] target(s) in 0.31s
     Running `/Users/insipx/Projects/xmtp/workspace-libxmtp/nm/mls-cli/target/debug/cli-client --local --db user2.db list-groups`
[2023-11-17T16:50:54Z INFO  cli_client] Starting CLI Client....
[2023-11-17T16:50:54Z INFO  cli_client] List Conversations
[2023-11-17T16:50:54Z INFO  cli_client] Using persistent storage: user2.db
[2023-11-17T16:50:54Z INFO  cli_client] ====== [0] Group d48c0c94a532f1e2f1ccdfc80f7ebefc ======

./xli.sh --local --db user2.db list-group-messages $GROUP_ID
warning: use of deprecated method `tokio_rustls::rustls::RootCertStore::add_server_trust_anchors`: Please use `add_trust_anchors` instead
  --> xmtp_api_grpc/src/grpc_api_helper.rs:32:11
   |
32 |     roots.add_server_trust_anchors(webpki_roots::TLS_SERVER_ROOTS.0.iter().map(|ta| {
   |           ^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: `#[warn(deprecated)]` on by default

warning: `xmtp_api_grpc` (lib) generated 1 warning
    Finished dev [unoptimized + debuginfo] target(s) in 0.30s
     Running `/Users/insipx/Projects/xmtp/workspace-libxmtp/nm/mls-cli/target/debug/cli-

client --local --db user2.db list-group-messages d48c0c94a532f1e2f1ccdfc80f7ebefc`
[2023-11-17T16:51:03Z INFO  cli_client] Starting CLI Client....
[2023-11-17T16:51:03Z INFO  cli_client] Recv
[2023-11-17T16:51:03Z INFO  cli_client] Using persistent storage: user2.db
[2023-11-17T16:51:03Z ERROR openmls::group::public_group::validation] Wrong Epoch: message.epoch() 0 != 1 self.group_context().epoch()
[2023-11-17T16:51:03Z WARN  xmtp_mls::groups] receive error ReceiveError([OpenMlsProcessMessage(ValidationError(WrongEpoch))])
[2023-11-17T16:51:03Z INFO  cli_client] ====== Group d48c0c94a532f1e2f1ccdfc80f7ebefc ======
    [ 17 seconds ago ] 0xa2cf2c5b8ae341012e3426b73576ca6b9732a71e:   helloooooo

@insipx I'm going to merge a few changes from the demo branch into this one (including adding a bunch more syncing before doing operations) to avoid situations like the one you ran into.

@insipx try now. The issue above should be fixed. The logs will be pretty noisy until the topic syncing PR goes in, since it still tries to reprocess all old messages every time.

hello, i'm at commit 6c05ffa9338648c3e36be89bd47f72d349ab265a (HEAD -> main, origin/main, origin/HEAD) and get the same error just running docker build . -t libxmtp:1, which was easily fixed by updating https://github.com/xmtp/libxmtp/blob/6c05ffa9338648c3e36be89bd47f72d349ab265a/xmtp_api_grpc/src/grpc_api_helper.rs#L32
that left me with some lifetime errors for https://github.com/xmtp/libxmtp/blob/6c05ffa9338648c3e36be89bd47f72d349ab265a/xmtp/src/codecs/text.rs#L8, which are easily fixed with &'static ...
finally, i'm down to privacy errors in cli-client.rs, e.g., https://github.com/xmtp/libxmtp/blob/6c05ffa9338648c3e36be89bd47f72d349ab265a/examples/cli/cli-client.rs#L291, stemming from https://github.com/xmtp/libxmtp/blob/6c05ffa9338648c3e36be89bd47f72d349ab265a/xmtp_mls/src/client.rs#L310. the naive fix pub(crate) upgrade to pub of course did the trick.
last trip-up was a clippy error in  https://github.com/xmtp/libxmtp/blob/6c05ffa9338648c3e36be89bd47f72d349ab265a/xmtp_api_grpc/src/grpc_api_helper.rs#L30
i can push a PR if you want.

Thanks for pointing those out @boneyard93501. I have a PR up that restores a missing Github workflow, which should have brought them to our attention sooner. It also should fix the issues listed above.
https://github.com/xmtp/libxmtp/pull/342


Lab / Quiz Page Preview

Add a preview (eye icon) button on the quiz and lab creation pages

This is done in the latest commit


Dynamic transform styling inside transition-group randomly not applied

Vue.js version
2.1.10 2.2.6
Browser version
Safari 10.0.3, also reproduced on a proprietary WebKit-based Samsung TV browser
All latest browsers (tested FF 52, Chrome 57 and Safari 10.0.3)
Reproduction Link
JSFiddle JSFiddle
Steps to reproduce

Create a <transition-group> and apply a dynamic transform style to elements inside it.
Rapidly (before the ongoing transition ends) update values your transform is based on.
Observe some elements not receiving styling.

What is Expected?
All elements should receive consistent transform styling.
What is actually happening?
When updates are fast enough (nothing extreme, simply click on up/down buttons in the example as fast as you can), some elements aren't styled.
The issue doesn't occur:

in other browsers (tried latest Chrome and Firefox);
with other style properties (tried font-size and color);
if updates are slow enough current transitions can end;
if you replace <transition-group> with just a <div> (but that doesn't provide consistent transitions).

Hello, sorry for the delay.
I tried your fiddle but it yields the same result on Chrome and Safari. Can you, please, provide a GIF and double check the Steps to reproduce ?

I checked the reproduction steps and they seem to be correct. Basically all you have to do is open the provided fiddle and click up/down buttons a few times very quickly. Here's how it looks on my side - doing it slowly works well while quick changes break it:

I successfully reproduced it on two different machines in the office (both with latest macOS and Safari) and three different Samsung TVs with a custom WebKit browser, where I initially discovered the issue (we're developing a Vue based smart TV app).

Damn, it just works fine in my Safari. Can you make sure no plugins are installed?

Yup, just checked and I have no extensions installed. I also went under Preferences > Security and unchecked Allow Plug-ins, no difference.
Can you try completely quitting Safari a few times? While testing this it sometimes randomly worked (maybe 1 out of 10 times), but all it took to break it again was a browser restart.

I tried a bunch of times but it just works fine. Are you sure you don't have any extension activated?

Can you share your user agent?
@phanan reproduced it with Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14
Turns out I have a more recent version: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/602.4.8 (KHTML, like Gecko) Version/10.0.3 Safari/602.4.8
You can check that on http://www.whatsmybrowser.org/

I have the same version as you: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/602.4.8 (KHTML, like Gecko) Version/10.0.3 Safari/602.4.8

It may have to do with this.... https://twitter.com/jaffathecake/status/829344704311488514

In case it helps, one of the TV browsers I mentioned where the issue is reproducible has the following: Mozilla/5.0 (SMART-TV; Linux; Tizen 2.4.0) AppleWebKit/538.1 (KHTML, like Gecko) Version/2.4.0 TV Safari/538.1
Though in my experience, these devices sometimes have incorrect user agents hardcoded, so take it with a grain of salt.

@yyx990803 I think it's not related to that regression for two reasons:

Apart from the already mentioned Samsung browser, I have since tried it on a few other devices with older WebKit and managed to reproduce it.
If I replace <transition-group> in the attached JSFiddle with a regular <div>, the bug is no longer reproducible (though this kills transitions in one direction because of elements being moved as you previously explained to me). The behaviour is absolutely consistent, I can open the JSFiddle in Safari and switch tags back and forth with the bug appearing/disappearing accordingly. This leads me to believe it's somehow connected to <transition-group>.

I've made a small breakthrough - I managed to isolate a much better test case that is consistently reproducible in all the browsers I tried (latest Safari, Chrome and FF).
I'm also pretty certain it is related to how <transition-group> works, since everything goes back to normal if I simply use a <div>.
I have updated the initial post accordingly.

But that's not how transition-group should be used: Check out the lazy sudoku example here

OK, hmm, but the logic behind it is practically the same as in the first example.
So if I understand you correctly - I should position my elements with something else then transforms (flex/float/absolute/whatever) and the transition group will automatically animate using transforms?

Yep, pretty much that.

Great, thanks a lot, closing.

@mzgajner I ran into this same problem but in my case I'm using SVG so I don't have much of an option other than using CSS transforms for Vue-animated transitions. How to address this or am I left with no Vue transitions for my case?

never mind. i figured it out. for anyone curious, this is the component i was talking about (link might change). click on the circles to see them moving around as you traverse the graph. this is all vue transition.
if curious about the code, here's the code at this moment


add button negative

hello sir can you add button negative for dismiss the dialog on LovelyChoiceDialog single choice?
like if user not choice now
and then its can setTopColorRes not show like hide the layout
thank you

Same request.  I need a positive and negative button and a "don't show this again" checkbox.  Not found a library that can handle this basic request.

Same request.  I need a positive and negative button and a "don't show this again" checkbox.  Not found a library that can handle this basic request.


Update readme list of contributors

Looking through the list of contributors in the readme there are people who have made non-trivial contributions to the code base who's name does not appear.
It is more difficult to fix this because the use of merge commits can obfuscate who did the work on a pull request.
I think as an open source project it is important we acknowledge our broad range of contributors.

Finding these as I go along.
@awav is missing from the list.
@mrksr is missing from the list.
@dustinvtran is missing from the list.

@john-bradshaw is missing from the list.

Resolved by #1660 .


Could not find the implementation for builder @angular-devkit/build-angular:browser

🐞 Bug report
- [ ] new
- [ x] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Description
I tried to build the project using ng build --prod I got this error.
🔥 Exception or Error

Could not find the implementation for builder @angular-devkit/build-angular:browser
Error: Could not find the implementation for builder @angular-devkit/build-angular:browser
    at WorkspaceNodeModulesArchitectHost.resolveBuilder (/Volumes/Data/Angular/htdocs/thecampus-angular/node_modules/@angular/cli/node_modules/@angular-devkit/architect/node/node-modules-architect-host.js:49:19)
    at BuildCommand.initialize (/Volumes/Data/Angular/htdocs/thecampus-angular/node_modules/@angular/cli/models/architect-command.js:135:55)
    at process._tickCallback (internal/process/next_tick.js:68:7)
    at Function.Module.runMain (internal/modules/cjs/loader.js:757:11)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)

🌍 Your Environment

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.8
@angular-devkit/build-angular     0.6.8
@angular-devkit/build-optimizer   0.6.8
@angular-devkit/core              0.6.8
@angular-devkit/schematics        8.0.0
@angular/cli                      8.0.0
@angular/compiler-cli             8.0.0
@ngtools/webpack                  6.0.8
@schematics/angular               8.0.0
@schematics/update                0.800.0
rxjs                              5.5.12
typescript                        2.5.3
webpack                           4.8.3

It seems that you are using Angular-CLI version 8, which packages that were meant to be used with version 7.
How did you migrate to Angular CLI version 8? Did you use the ng update command?
Thanks

@alan-agius4 I am using angular Angular 5
 "dependencies": {         "@angular/animations": "^5.2.11",         "@angular/common": "^5.2.0",         "@angular/compiler": "^5.2.0",         "@angular/core": "^5.2.0",         "@angular/forms": "^5.2.0",         "@angular/http": "^5.2.0",         "@angular/platform-browser": "^5.2.0",         "@angular/platform-browser-dynamic": "^5.2.0",
Each time I try to use the command npm install I get this warnning
added 1 package from 1 contributor, removed 4 packages, updated 1 package and audited 30564 packages in 8.018s found 6 vulnerabilities (2 low, 4 moderate)   runnpm audit fixto fix them, ornpm auditfor details
so when I ran the npm audit fix cmd it automatically updates CLI version; but with the old version (1.7.4) or with the new one (8.0.0) I get always the errors when I try to build the project.

Hi, @angular/cli version 8 will only work with Angular version 8.
Unfortunately Angular version 5 and CLI version 1, are not longer supported https://angular.io/guide/releases#support-policy-and-schedule
I suggest you update to version 8  by running the update command via ng update @angular/cli @angular/core, This is suggested because when running the update command several migrations will be executed to make your project compatible with the new version which otherwise you'd need to do manually.
If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.

I can't update it
`
Error: Cannot update safely because packages have conflicting dependencies. Package @angular/platform-browser would need to match both versions "7.2.15" and "8.0.0, which are not compatible.
Cannot update safely because packages have conflicting dependencies. Package @angular/platform-browser would need to match both versions "7.2.15" and "8.0.0, which are not compatible.
`

Can you please share your package.json?

{     "name": "thecampus-angular",     "version": "0.0.0",     "license": "MIT",     "scripts": {         "ng": "ng",         "start": "ng serve",         "build": "ng build --prod",         "test": "ng test",         "lint": "ng lint",         "e2e": "ng e2e",         "postinstall": "npm run tsformat",         "tsformat": "tsfmt -r"     },     "private": true,     "dependencies": {         "@angular/animations": "^5.2.11",         "@angular/common": "^5.2.0",         "@angular/compiler": "^5.2.0",         "@angular/core": "^5.2.0",         "@angular/forms": "^5.2.0",         "@angular/http": "^5.2.0",         "@angular/platform-browser": "^5.2.0",         "@angular/platform-browser-dynamic": "^5.2.0",         "@angular/router": "^5.2.0",         "@ng-bootstrap/ng-bootstrap": "^1.0.0-beta.3",         "@types/html2canvas": "0.0.35",         "@types/jquery": "^3.2.6",         "@types/jspdf": "^1.3.0",         "angular-calendar": "^0.24.1",         "angular-calendar-week-hours-view": "^1.0.2",         "angular-draggable-droppable": "^2.0.0",         "angular-notifier": "^4.1.1",         "angular-resizable-element": "^2.0.0",         "bootstrap": "^3.3.6",         "calendar-utils": "^0.1.2",         "classlist.js": "^1.1.20150312",         "core-js": "^2.4.1",         "date-fns": "^1.28.5",         "enhanced-resolve": "^3.3.0",         "html2canvas": "^1.0.0-rc.1",         "jquery": "^3.4.1",         "jspdf": "^1.5.3",         "moment": "^2.24.0",         "ng-pick-datetime": "^5.2.0",         "ng-recaptcha": "^3.0.0",         "ng2-google-charts": "^4.0.0",         "positioning": "^1.3.1",         "primeng": "^4.1.3",         "pusher-js": "^4.4.0",         "rxjs": "^5.5.6",         "survey-angular": "^1.0.87",         "survey-creator": "^1.0.87",         "survey-knockout": "^1.0.87",         "surveyjs-widgets": "^1.0.87",         "tslib": "^1.9.0",         "typescript-formatter": "^5.2.0",         "zone.js": "^0.8.19"     },     "devDependencies": {         "@angular-devkit/core": "^8.0.0",         "@angular/cli": "~1.7.4",         "@angular/compiler-cli": "^5.2.0",         "@angular/language-service": "^5.2.0",         "@types/jasmine": "2.5.38",         "@types/knockout": "^3.4.53",         "@types/node": "^11.13.12",         "codelyzer": "~2.0.0",         "extract-text-webpack-plugin": "^4.0.0-beta.0",         "jasmine-core": "~2.5.2",         "jasmine-spec-reporter": "~3.2.0",         "karma": "^4.1.0",         "karma-chrome-launcher": "~2.0.0",         "karma-cli": "~1.0.1",         "karma-coverage-istanbul-reporter": "^0.2.0",         "karma-jasmine": "^1.1.1",         "karma-jasmine-html-reporter": "^0.2.2",         "node-sass": "^4.11.0",         "protractor": "^6.0.0",         "raw-loader": "^0.5.1",         "style-loader": "^0.16.1",         "ts-node": "~2.0.0",         "tslint": "~4.5.0",         "typescript": "~2.5.3",         "webpack": "^4.32.2"     } }

i faced a same problem, i got error msg:"Could not find the implementation for builder @angular-devkit/build-angular:dev-server" after update @angular/cli version 8.0.0;
what should i do...?

It seems the ng update command does not work when using with v5.2.
For me the error is: Package @angular/platform-browser would need to match both versions "7.2.15" and "8.0.0, which are not compatible.

I also cannot update a version 5 project using ng update.  I tried following the instructions at https://update.angular.io/#5.0:6.0 and got stuck when executing ng update @angular/cli.  It gave me the following error:
Error: Cannot update safely because packages have conflicting dependencies. Package @angular/platform-browser would need to match both versions "7.2.15" and "8.0.0, which are not compatible.
Cannot update safely because packages have conflicting dependencies. Package @angular/platform-browser would need to match both versions "7.2.15" and "8.0.0, which are not compatible.

Here's my package.json
{
  "name": "help-me",
  "version": "0.0.0",
  "license": "MIT",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e",
    "preinstall": "npm install -g node-gyp",
    "heroku-postbuild": "ng build"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "^5.0.2",
    "@angular/cli": "^1.7.4",
    "@angular/common": "^5.0.2",
    "@angular/compiler": "^5.0.2",
    "@angular/compiler-cli": "^5.0.2",
    "@angular/core": "^5.0.2",
    "@angular/forms": "^5.0.2",
    "@angular/http": "^5.0.2",
    "@angular/language-service": "^5.0.2",
    "@angular/platform-browser": "^5.0.2",
    "@angular/platform-browser-dynamic": "^5.0.2",
    "@angular/router": "^5.0.2",
    "@ng-bootstrap/ng-bootstrap": "^1.0.0",
    "@types/jasmine": "~2.5.53",
    "@types/jasminewd2": "~2.0.2",
    "@types/node": "~6.0.60",
    "bootstrap": "4.0.0-beta.2",
    "codelyzer": "~3.2.0",
    "core-js": "^2.4.1",
    "jasmine-core": "~2.6.2",
    "jasmine-spec-reporter": "~4.1.0",
    "karma": "~1.7.0",
    "karma-chrome-launcher": "~2.1.1",
    "karma-cli": "~1.0.1",
    "karma-coverage-istanbul-reporter": "^1.2.1",
    "karma-jasmine": "~1.1.0",
    "karma-jasmine-html-reporter": "^0.2.2",
    "moment": "^2.22.0",
    "node-sass": "^4.12.0",
    "protractor": "~5.1.2",
    "rxjs": "^5.4.2",
    "ts-md5": "^1.2.4",
    "ts-node": "~3.2.0",
    "tslint": "~5.7.0",
    "typescript": "~3.2.2",
    "zone.js": "^0.8.14"
  },
  "devDependencies": {}
}

The only sort of non-standard thing that is here that I'm aware of is that all of the dependencies are listed in the "dependencies" section, even those that are normally in the "devDependencies" section.  This was done in order to satisfy requirements specified in https://www.codewithjason.com/deploy-rails-application-angular-cli-webpack-front-end/  which is used to allow an integrated rails / angular app to be deployed to Heroku.
It would be great to have some suggestions on how to resolve this.

@ryanmcfall see #14581 for a possible solution.

@tuuling i have same issue fatch, let know if you getting any solution ?

I got this error when I to upgrade from angular 7 to 8
Could not find the implementation for builder @angular-builders/dev-server:generic
Error: Could not find the implementation for builder @angular-builders/dev-server:generic

I got this error when I to upgrade from angular 7 to 8
Could not find the implementation for builder @angular-builders/dev-server:generic
Error: Could not find the implementation for builder @angular-builders/dev-server:generic

For my case, I found the reason from here
https://github.com/meltedspark/angular-builders/blob/master/MIGRATION.MD

@tuuling i have same issue fatch, let know if you getting any solution ?

See my previous comment.

I am getting the same error. any possible solutions?

What have worked for me was:
1.) Make sure your angular version starts with 7.2.15 (if not, you should install this version first)
2.) Be sure your Node version is 12.x.x
3.) Typescript version 3.4.5
3.) ng update @angular/cli @angular/core
4.) npm uninstall @angular-devkit/build-angular
5.) npm install @angular-devkit/build-angular
6.) ng update --all
7.) If you have ViewChild on your application, be sure to edit them with:
@ViewChild(<name>, {static: true}) <name>;    // Adding static: true on the 2nd param

got it from this his answer

I have updated Angular 8, when am trying to build the application am getting below error.
Could not find the implementation for builder @angular-devkit/build-ng-packagr:build

@Metourni I am getting error also
Could not find the implementation for builder @angular-devkit/build-angular:dev-server Error: Could not find the implementation for builder @angular-devkit/build-angular:dev-server     at WorkspaceNodeModulesArchitectHost.resolveBuilder (/home/hasmukh/Hasmukh/angular-project/angular7/frontendcertif-id/node_modules/@angular/cli/node_modules/@angular-devkit/architect/node/node-modules-architect-host.js:49:19)     at ServeCommand.initialize (/home/hasmukh/Hasmukh/angular-project/angular7/frontendcertif-id/node_modules/@angular/cli/models/architect-command.js:135:55)     at async ServeCommand.validateAndRun (/home/hasmukh/Hasmukh/angular-project/angular7/frontendcertif-id/node_modules/@angular/cli/models/command.js:127:9)     at async Object.runCommand (/home/hasmukh/Hasmukh/angular-project/angular7/frontendcertif-id/node_modules/@angular/cli/models/command-runner.js:178:24)     at async default_1 (/home/hasmukh/Hasmukh/angular-project/angular7/frontendcertif-id/node_modules/@angular/cli/lib/cli/index.js:32:31)

I have updated Angular 8, when am trying to build the application am getting below error.
Could not find the implementation for builder @angular-devkit/build-ng-packagr:build
How to resolve this?

Is any possible solution?

What have worked for me was:
1.) Make sure your angular version starts with 7.2.15 (if not, you should install this version first)
2.) Be sure your Node version is 12.x.x
3.) Typescript version 3.4.5
3.) ng update @angular/cli @angular/core (for @angular/cli, be sure to install it both local & global)
4.) npm uninstall @angular-devkit/build-angular
5.) npm install @angular-devkit/build-angular
6.) ng update --all
7.) If you have ViewChild on your application, be sure to edit them with: Source
@ViewChild(<name>, {static: true}) <name>; // Adding static: true on the 2nd param

Still getting error.
Could not find the implementation for builder @angular-devkit/build-ng-packagr:build
Error: Could not find the implementation for builder @angular-devkit/build-ng-packagr:build
at WorkspaceNodeModulesArchitectHost.resolveBuilder

I have updated Angular 8, when am trying to build the application am getting below error.
Could not find the implementation for builder @angular-devkit/build-ng-packagr:build
How to resolve this?

I resolved issue, clear cache and npm install --save-dev build-ng-packagr

@angular-devkit/build-angular

npm uninstall @angular-devkit/build-angular
npm install --save-dev @angular-devkit/build-angular

npm audit fix worked for me

ng update  @angular/core in project
worked for me

npm install --save-dev @angular-devkit/build-angular

This one worked for me!  but something strange now in my package.json:
"@angular-devkit/build-angular": "^0.800.3",
Is this normal?

Yes. No issue
On Fri, 21 Jun 2019, 12:43 a.m. RolfDeVries<EMAIL_ADDRESS>wrote:

npm install --save-dev @angular-devkit/build-angular
This one worked for me! but something strange now in my package.json:
"@angular-devkit/build-angular": "^0.800.3",
Is this normal?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/issues/14546?email_source=notifications&email_token=ALSH6GHCKC2QB3VD6MB2XI3P3PJFPA5CNFSM4HQJFYPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYGK52Q#issuecomment-504147690,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALSH6GEHNQDGHTU4LBJBDWTP3PJFPANCNFSM4HQJFYPA
.

What have worked for me was:
1.) Make sure your angular version starts with 7.2.15 (if not, you should install this version first)
2.) Be sure your Node version is 12.x.x
3.) Typescript version 3.4.5
3.) ng update @angular/cli @angular/core (for @angular/cli, be sure to install it both local & global)
4.) npm uninstall @angular-devkit/build-angular
5.) npm install @angular-devkit/build-angular
6.) ng update --all
7.) If you have ViewChild on your application, be sure to edit them with: Source
@ViewChild(<name>, {static: true}) <name>; // Adding static: true on the 2nd param

step 6 fails with:
Using package manager: 'npm'
Collecting installed dependencies...
Found 35 dependencies.
                  Package "@angular-devkit/build-angular" has an incompatible peer dependency to "typescript" (requires ">=3.1 < 3.5", would install "3.5.2")
                  Package "@angular-devkit/build-angular" has an incompatible peer dependency to "typescript" (requires ">=3.1 < 3.5", would install "3.5.2").
Incompatible peer dependencies found.
Peer dependency warnings when installing dependencies means that those dependencies might not work correctly together.
You can use the '--force' option to ignore incompatible peer dependencies and instead address these warnings later.

I did a lot of weird stuff to get it working:
# uninstall build-angular and typescript
npm uninstall @angular-devkit/build-angular
npm uninstall typescript
# update all
ng update --all --allow-dirty
# install the needed typescript and build-angular
npm install @angular-devkit/build-angular
npm install --save<EMAIL_ADDRESS>
Seems to work now. Compiles the bundles and starts de app.

What have worked for me was:
1.) Make sure your angular version starts with 7.2.15 (if not, you should install this version first)
2.) Be sure your Node version is 12.x.x
3.) Typescript version 3.4.5
3.) ng update @angular/cli @angular/core (for @angular/cli, be sure to install it both local & global)
4.) npm uninstall @angular-devkit/build-angular
5.) npm install @angular-devkit/build-angular
6.) ng update --all
7.) If you have ViewChild on your application, be sure to edit them with: Source
@ViewChild(<name>, {static: true}) <name>; // Adding static: true on the 2nd param

Compiled successfully up until step 5th,
Even then I went for the 6th step ng update --all but it threw error
Package "@angular/compiler-cli" has an incompatible peer dependency to "typescript" (requires ">=3.4 <3.5", would install "3.5.2").
Incompatible peer dependencies found.
Peer dependency warnings when installing dependencies means that those dependencies might not work correctly together.
You can use the '--force' option to ignore incompatible peer dependencies and instead address these warnings later.

So used "ng update --all --force" command , it ran without a problem
But typescript was also updated during the update so it threw error on ng serve which was
ERROR in The Angular Compiler requires TypeScript >=3.4.0 and <3.5.0 but 3.5.2 was found instead.
Before ng update the typescript version was 3.4.5 so I downgrade it with  npm install<EMAIL_ADDRESS><3.5"
and it worked.
Thanks Kristy

I get this error even with a brand-new angular project.
ng new <project-name> --style scss --routing
ng serve
And I get the following error:
An unhandled exception occurred: Cannot find module '@angular/compiler-cli/ngcc'
See "C:\Users\patri\AppData\Local\Temp\ng-DAapXj\angular-errors.log" for further details.

I was struggling with this after upgrading to Angular 8.  I had to do a few things including removing all the node_modules and then later:
update @angular/cli @angular/core
npm audit fix

What have worked for me was:
1.) Make sure your angular version starts with 7.2.15 (if not, you should install this version first)
2.) Be sure your Node version is 12.x.x
3.) Typescript version 3.4.5
3.) ng update @angular/cli @angular/core (for @angular/cli, be sure to install it both local & global)
4.) npm uninstall @angular-devkit/build-angular
5.) npm install @angular-devkit/build-angular
6.) ng update --all
7.) If you have ViewChild on your application, be sure to edit them with: Source
@ViewChild(<name>, {static: true}) <name>; // Adding static: true on the 2nd param

One important thing.......be VERY CAREFUL with running the command of "ng update --all"
At this point in time, it upgraded my karma/jasmine to an unstable version and caused me so much pain to figure out the root cause (tests would randomly fail).

I got this error as well. What worked for me was running yarn install again.
Hope this works for you too 😁

What have worked for me was:
1.) Make sure your angular version starts with 7.2.15 (if not, you should install this version first)
2.) Be sure your Node version is 12.x.x
3.) Typescript version 3.4.5
3.) ng update @angular/cli @angular/core (for @angular/cli, be sure to install it both local & global)
4.) npm uninstall @angular-devkit/build-angular
5.) npm install @angular-devkit/build-angular
6.) ng update --all
7.) If you have ViewChild on your application, be sure to edit them with: Source
@ViewChild(<name>, {static: true}) <name>; // Adding static: true on the 2nd param

Thank you!  The thing that worked for me while updating one of my projects was using you're step 4 & 5, that's why the build was getting held up... not sure why it wasn't updated.


Async / Await - Redux Thunk with a returned value

Flow version: ^0.92.0
Expected behavior
No errors.
Actual behavior
Cannot call await with `checkAuthStatus()` bound to `p` because `ThunkAction` [1] is incompatible with `Promise` [2].

I'm trying to Flow type a Redux Thunk action that has a return value.  I think this is related to  #5294  in that I'm getting the same useless error as some of the comments although none of the workarounds posted are working for me.
I'm using the Redux Thunk example from the Flow docs (I've tried adding an explicit return type of Promise to the ThunkAction and async inner function):
type PromiseAction = Promise<Action>;
type ThunkAction = (dispatch: Dispatch, getState: GetState) => any;
type Dispatch = (action: Action | ThunkAction | PromiseAction | Array<Action>) => any;

export const checkAuthStatus = (): ThunkAction => async (dispatch) => {
  const loggedIn: boolean = false;
  const promptSkipped: boolean = true;

  dispatch(setLoggedIn(loggedIn));

  return promptSkipped;
};

This works if I simply call await checkAuthStatus(), but if I try to assign the returned value (const promptSkipped = await checkAuthStatus()), I get the above error.
Try-Flow Example

I'm brand-new to Flow so hopefully there isn't a glaringly obvious problem with the way I'm trying to do this. StackOverflow question here.

You're returning function, not promise

@goodmind I'm returning a function that returns a Promise, yes.

Yes, and you shouldn't be awaiting the function. You should be awaiting the promise returned from the function: https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoVAXAngBwKZgDKGAhhgQLxgDeqYYA1PAObN4AmAkgHYBcYAIzhwYeEtwA0dRjgBOcALY4MhANYBLHPnb8hIsZNQBfdNnxgAggGMM6uNzAVpAHyJ4MAGTisOPa7fsAbnRgYDAAFRJVPAcoeQUwAAsMDBwAZ15Q2EQAOjhZZmAY4HY4KzTgWTEbSo4AVwAPNDMCAHF3YjJKMAAKAEpHAD4iUnJglrAABXj1NLx-OwcqacVZvAAeBftB8dwCcMS67lUtpd72WZwyK0T+ABFL68SJMDYVUbx+dveugYph8RYXbmB5pK4YG6OXokGyLfinMCuA5HE6w+yIqYzOYI1wWWSyEhYTZo7iDP4A7hA1DsPBWGAkKpgABuDLAFzBT3ujwhiWCNLpDIILNkrw6Hy+Yq6wTwDRw+QwYCs9jSCputJOdQwiU6GDqaSh-X4yOOCP+YBIaSw3Cs525N3JNGkSu4KrALDYXD4gmEonEUKgJBgc2C9GdrrkimUak02l0PoMUIwsjqeGC0nZ4JuPTmnm8Hp4PXdvm4fT6afoVV1sgcEaUKg0Wg4wSMabDCvIKoAwol1RZNdrRnqoRarTb+kNHaHlQra1GG9phwgSOpVT2rBqtTq9f0ehmni83jq8GXpNJQhFErMwFetQQYOpuAQtWQwGlEnA6jB2IICHh8fkH2YMAoHyc0UjwOtALADA4HNdhvxIV8kygmDzW9fRxByJ1lX0HIWB6Wd6xjDhGDAAByEC4DIk8W1MPY3FzHxPVNSdoL2fgyMIABRcIAH0PAAeVaVouLuXjOAAOTIqR6CuLB4BIHR0N9QxaNQGU5VkVVp1fdwvCYngDVmfT8y9PQVIdHpqDY-AOO4vjBOE0TxKkl45IUpTjLzYswCME9UCAA

@jcready Thanks, how would this work in a component context where the redux-thunk middleware handles the calling of the inner function? e.g.
async componentDidMount() => {
  const promptSkipped = await this.props.authStatus();
  ...
}

...

const mapDispatchToProps = (dispatch: Dispatch) => {
  authStatus: dispatch(checkAuthStatus()),
};

export default connect(null, mapDispatchToProps)(TheComponent)


Release v4.1.2

Signed-off-by: Spyros Trigazis<EMAIL_ADDRESS>Note: oauth2client is now deprecated. As such, it is unlikely that we will
review or merge to your pull request. We recommend you use
google-auth and oauthlib.

@jonparrott Looks good to you?

@jonparrott The new version goes to pypi automatically? Do we need an extra step?

Travis is supposed to do it automatically, but it looks like travis' deployment plugin is using the deprecated PyPI endpoint and they just started a brownout((log)[https://travis-ci.org/google/oauth2client/jobs/248497987#L909]).
/cc @dstufft

See https://github.com/travis-ci/dpl/issues/655

Thanks, @dstufft, you are incredibly helpful as always. :)

Thanks, @dstufft
@jonparrott It looks like that 4.1.2 will be available tomorrow (at some timezone :-) ).
Is there anything that I can do to help configure the new endpoint?

@strigazi I just need to do a manual release. I'll try to do so today.

@strigazi it's published on PyPI: https://pypi.python.org/pypi/oauth2client


When compiling a PORT, is it possible to specify the version of this PORT?  Or keep multiple versions at the same time?

When compiling a PORT, is it possible to specify the version of this PORT? Or keep multiple versions at the same time?
eg:
Openssl version is 3.0.3 in current vcpkg. but I need openssl 1.1.1.
How do i do it?

In classic mode vcpkg only supports updating to the version owned by GIT_HEAD.
And you can use the manifest pattern to specify the specific version number you want.
See https://github.com/microsoft/vcpkg/blob/master/docs/users/manifests.md

OR user overlay-ports https://github.com/microsoft/vcpkg/blob/master/docs/specifications/ports-overlay.md

We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.

@JackBoosY Thanks you! manifest mode can solved the problem.
How to know which versions of OPENSSL are supported by vcpkg?

@KangLin ./vcpkg x-history openssl.

@Neumann-A I use  overlay-ports, but it is fail.

I copy openssl1.1.n port to my project folder https://github.com/KangLin/RabbitRemoteControl/tree/develop/vcpkg/ports/openssl from old vcpkg.
I run vcpkg install openssl --overlay-ports=D:\source\rabbitremotecontol\vcpkg\ports . it is fail.
I set  environment variable VCPKG_OVERLAY_PORTS. it is fail.

Where am I doing wrong?
Run result:
D:\source\vcpkg>vcpkg install openssl --overlay-ports=D:\source\rabbitremotecont
rol\vcpkg\ports
Computing installation plan...
The following packages will be built and installed:
openssl[core]:x86-windows -> 3.0.5#4

vcpkg-cmake[core]:x64-windows -> 2022-07-18
vcpkg-cmake-config[core]:x64-windows -> 2022-02-06#1
vcpkg-cmake-get-vars[core]:x64-windows -> 2022-05-10#1
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
Detecting compiler hash for triplet x86-windows...
Restored 3 package(s) from C:\Users\Administrator\AppData\Local\vcpkg\archives i
n 68.54 ms. Use --debug to see more details.
Installing 1/4 vcpkg-cmake:x64-windows...
Elapsed time to handle vcpkg-cmake:x64-windows: 16.39 ms
Installing 2/4 vcpkg-cmake-config:x64-windows...
Elapsed time to handle vcpkg-cmake-config:x64-windows: 14.54 ms

@KangLin Can you please provide the full output?

@JackBoosY  @Neumann-A
vcpkg version: f688b2e29676bfa3a02ead4b7096c589f8af8180
openssl 1.1.n:  https://github.com/KangLin/RabbitRemoteControl/tree/develop/vcpkg/ports/openssl
Run result:
D:\source\vcpkg>vcpkg install openssl --overlay-ports=D:\source\rabbitremotecontrol\vcpkg\ports
Computing installation plan...
The following packages will be built and installed:
openssl[core]:x86-windows -> 3.0.5#4

vcpkg-cmake[core]:x64-windows -> 2022-07-18
vcpkg-cmake-config[core]:x64-windows -> 2022-02-06#1
vcpkg-cmake-get-vars[core]:x64-windows -> 2022-05-10#1
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
A suitable version of powershell-core was not found (required v7.2.5). Downloadi
ng portable powershell-core v7.2.5...
Downloading powershell-core...
https://github.com/PowerShell/PowerShell/releases/download/v7.2.5/PowerShell-7
.2.5-win-x86.zip -> D:\source\vcpkg\downloads\PowerShell-7.2.5-win-x86.zip
Extracting powershell-core...
Detecting compiler hash for triplet x86-windows...
A suitable version of 7zip was not found (required v21.7.0). Downloading portabl
e 7zip v21.7.0...
Downloading 7zip...
https://www.7-zip.org/a/7z2107-extra.7z -> D:\source\vcpkg\downloads\7z2107-ex
tra.7z
Extracting 7zip...
Restored 3 package(s) from C:\Users\Administrator\AppData\Local\vcpkg\archives i
n 10.64 s. Use --debug to see more details.
Installing 1/4 vcpkg-cmake:x64-windows...
Elapsed time to handle vcpkg-cmake:x64-windows: 17.82 ms
Installing 2/4 vcpkg-cmake-config:x64-windows...
Elapsed time to handle vcpkg-cmake-config:x64-windows: 17.3 ms
Installing 3/4 vcpkg-cmake-get-vars:x64-windows...
Elapsed time to handle vcpkg-cmake-get-vars:x64-windows: 10.16 ms
Installing 4/4 openssl:x86-windows...
Building openssl[core]:x86-windows...
-- Downloading https://github.com/openssl/openssl/archive/openssl-3.0.5.tar.gz -

openssl-openssl-openssl-3.0.5.tar.gz...
-- Extracting source D:/source/vcpkg/downloads/openssl-openssl-openssl-3.0.5.tar
.gz
-- Applying patch D:/source/vcpkg/ports/openssl/windows/flags.patch
-- Using source at D:/source/vcpkg/buildtrees/openssl/src/nssl-3.0.5-df50913d32.
clean
-- Downloading https://strawberryperl.com/download/<IP_ADDRESS>/strawberry-perl-5.32
.1.1-32bit.zip -> strawberry-perl-<IP_ADDRESS>-32bit.zip...
-- Downloading https://www.nasm.us/pub/nasm/releasebuilds/2.15.05/win32/nasm-2.1
5.05-win32.zip;https://fossies.org/windows/misc/nasm-2.15.05-win32.zip -> nasm-2
.15.05-win32.zip...
-- Downloading https://download.qt.io/official_releases/jom/jom_1_1_3.zip;https:
//mirrors.ocf.berkeley.edu/qt/official_releases/jom/jom_1_1_3.zip -> jom_1_1_3.z
ip...
-- Found external ninja('1.10.2').
-- Getting CMake variables for x86-windows
-- Copying openssl release source files...
-- Copying openssl release source files... done
-- Configure x86-windows-rel
-- Configure x86-windows-rel done
-- Build x86-windows-rel
-- Build x86-windows-rel done
-- Copying openssl debug source files...
-- Copying openssl debug source files... done
-- Configure x86-windows-dbg
-- Configure x86-windows-dbg done
-- Build x86-windows-dbg
-- Build x86-windows-dbg done
CMake Warning at scripts/cmake/vcpkg_copy_pdbs.cmake:44 (message):
Could not find a matching pdb file for:

  D:/source/vcpkg/packages/openssl_x86-windows/bin/legacy.dll
  D:/source/vcpkg/packages/openssl_x86-windows/bin/libcrypto-3.dll
  D:/source/vcpkg/packages/openssl_x86-windows/bin/libssl-3.dll
  D:/source/vcpkg/packages/openssl_x86-windows/debug/bin/legacy.dll
  D:/source/vcpkg/packages/openssl_x86-windows/debug/bin/libcrypto-3.dll
  D:/source/vcpkg/packages/openssl_x86-windows/debug/bin/libssl-3.dll

Call Stack (most recent call first):
ports/openssl/windows/portfile.cmake:218 (vcpkg_copy_pdbs)
ports/openssl/portfile.cmake:36 (include)
scripts/ports.cmake:147 (include)
-- Installing: D:/source/vcpkg/packages/openssl_x86-windows/share/openssl/copyri
ght
-- Fixing pkgconfig file: D:/source/vcpkg/packages/openssl_x86-windows/lib/pkgco
nfig/libcrypto.pc
-- Fixing pkgconfig file: D:/source/vcpkg/packages/openssl_x86-windows/lib/pkgco
nfig/libssl.pc
-- Fixing pkgconfig file: D:/source/vcpkg/packages/openssl_x86-windows/lib/pkgco
nfig/openssl.pc
-- Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-pkg-config-0.29.
2-3-any.pkg.tar.zst;https://www2.futureware.at/~nickoe/msys2-mirror/mingw/i686/m
ingw-w64-i686-pkg-config-0.29.2-3-any.pkg.tar.zst;https://mirror.yandex.ru/mirro
rs/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-3-any.pkg.tar.zst;https://m
irrors.tuna.tsinghua.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-3-
any.pkg.tar.zst;https://mirrors.ustc.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-
config-0.29.2-3-any.pkg.tar.zst;https://mirror.bit.edu.cn/msys2/mingw/i686/mingw
-w64-i686-pkg-config-0.29.2-3-any.pkg.tar.zst;https://mirror.selfnet.de/msys2/mi
ngw/i686/mingw-w64-i686-pkg-config-0.29.2-3-any.pkg.tar.zst;https://mirrors.sjtu
g.sjtu.edu.cn/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-3-any.pkg.tar.zs
t -> msys-mingw-w64-i686-pkg-config-0.29.2-3-any.pkg.tar.zst...
-- Downloading https://repo.msys2.org/mingw/i686/mingw-w64-i686-libwinpthread-gi
t-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst;https://www2.futureware.at/~nickoe/msys
2-mirror/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.
pkg.tar.zst;https://mirror.yandex.ru/mirrors/msys2/mingw/i686/mingw-w64-i686-lib
winpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst;https://mirrors.tuna.tsing
hua.edu.cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd8
3-1-any.pkg.tar.zst;https://mirrors.ustc.edu.cn/msys2/mingw/i686/mingw-w64-i686-
libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst;https://mirror.bit.edu.
cn/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.
pkg.tar.zst;https://mirror.selfnet.de/msys2/mingw/i686/mingw-w64-i686-libwinpthr
ead-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst;https://mirrors.sjtug.sjtu.edu.cn
/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pk
g.tar.zst -> msys-mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pk
g.tar.zst...
-- Using msys root at D:/source/vcpkg/downloads/tools/msys2/9a1ec3f33446b195
-- Fixing pkgconfig file: D:/source/vcpkg/packages/openssl_x86-windows/debug/lib
/pkgconfig/libcrypto.pc
-- Fixing pkgconfig file: D:/source/vcpkg/packages/openssl_x86-windows/debug/lib
/pkgconfig/libssl.pc
-- Fixing pkgconfig file: D:/source/vcpkg/packages/openssl_x86-windows/debug/lib
/pkgconfig/openssl.pc
-- Installing: D:/source/vcpkg/packages/openssl_x86-windows/share/openssl/usage
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: "C:\Users\Administrator\AppData\Local\vcpkg\archives\c2\c21
e89cb18679e5abfe86b49e03719d440d4d103c0d8ce1c88fab5cf090ec326.zip"
Elapsed time to handle openssl:x86-windows: 1.935 h
Total elapsed time: 6.142 h
The package openssl is compatible with built-in CMake targets:
find_package(OpenSSL REQUIRED)
target_link_libraries(main PRIVATE OpenSSL::SSL OpenSSL::Crypto)

vcpkg.json is not exist in your path https://github.com/KangLin/RabbitRemoteControl/tree/develop/vcpkg/ports/openssl.

@JackBoosY Thank you! It is work.
In classic mode, I just need to specify the old version. Using overlays feels a bit complicated. Can there be an easier way? For example: vcpkg install openssl:version

In classic mode, I just need to specify the old version. Using --overlay-ports feels a bit complicated. Can there be an easier way? For example: vcpkg install openssl:version

Corrently no, sorry. I think we will improve this part of usage in the future.

It is recommended to use vcpkg install openssl --overlay-ports=D:\source\rabbitremotecontrol\vcpkg\ports instead of vcpkg upgrade --no-dry-run --overlay-ports=D:\source\rabbitremotecontrol\vcpkg\ports


Feature/ts 195 store collection exercise

What is the context of this PR?
Link to Trello card
https://trello.com/c/GXZ2CWH6
Describe what you have changed and why, link to other PRs or Issues as appropriate.
Added ability to store collection exercise
How to review
Any notes for the reviewer  (include screenshots if appropriate).

Could you add tests around the Draft Post and the Drafts get and the threads get please .


[Question] How to properly integrate with

Hi there,
I'm trying to add this library to a Kotlin Multiplatform project with Compose Multiplatform, targetting Android and iOS.
I'm using also Multiplatform resources, where I store the aboutlibraries.json
I've started by running the gradle command to generate the  aboutlibraries.json
./gradlew :shared:exportLibraryDefinitions -PaboutLibraries.exportPath=src/commonMain/composeResources/files
Then, on Compose side I did this, but looks very 'hacky'
@Composable
fun LibrariesLicensesScreen() {

  val coroutineScope = rememberCoroutineScope()
  var json by remember { mutableStateOf("") }

  coroutineScope.launch {
    json = Res.readBytes("files/aboutlibraries.json").decodeToString()
  }

  LibrariesContainer(
    aboutLibsJson = json,
    modifier = Modifier.fillMaxSize()
  )
}

Ignore the fact that the file is being read in the Composable, it was just for test porposes.
Is there a better way?
Thank you so much

Good day.
So far we have intentionally chosen to offer a very flexible API allowing the integration to choose whichever architecture fits their project best.
Very similar to your approach the wasm example loads it for example this way:
                val libraries = produceState<Libs?>(null) {
                    value = withContext(Dispatchers.Default) {
                        Libs.Builder()
                            .withJson(Res.readBytes("files/aboutlibraries.json").decodeToString())
                            .build()
                    }
                }

Your approach is quite similar and also fine.
The cleanest would certainly be to pull it out of the compose code, and only expose the state to compose world.
That said, I feel like there might be a good argument to build a new rememberLibraries API or similar to abstract this logic away. 🤔


python27Packages.application: 2.7.0 -> 2.8.0 and fix build; python27Packages.python-otr: mark as broken

The build is currently broken due to failure to build darcs to fetch the src
package. The homepage is already their GitHub repo, and it appears to be the
active src of development anyways. See #83718
I came across this while debugging this failure:
https://hydra.nixos.org/build/115510612
Note that the application dependency does succeed on Hydra, because it's
already on local disk in Hydra's store, but I cannot rebuild locally because it
has prefer local builds.
https://hydra.nixos.org/build/115512559
This package is not reproducible on 20.03 or buildable outside of Hydra, so I
intend to backport the fix.
CC @NixOS/nixos-release-managers
ZHF: #80379

Motivation for this change
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

2 package updated:
python2.7-python-application (2.7.0 → 2.8.0) python2.7-python-otr

1 package failed to build:
python27Packages.python-otr

1 package built:
python27Packages.application

Note that python-otr is the package I'm trying to fix for ZHF, but without this PR I can't fetch its dependencies.

Looks like the python-otr package is a known issue with python2 packaging:
https://github.com/NixOS/nixpkgs/issues/74619

1 package updated:
python2.7-python-application (2.7.0 → 2.8.0)

[1 built, 0.0 MiB DL]
1 package built:
python27Packages.application

Looks "better" now.

[detached HEAD e15c9281a52] python27Packages.application: 2.7.0 -> 2.8.0 and fix build
 Author: Benjamin Hipple<EMAIL_ADDRESS> Date: Sun Mar 29 18:18:04 2020 -0400
 1 file changed, 11 insertions(+), 6 deletions(-)
Press Enter to continue
[detached HEAD 81c29c1be0c] python27Packages.python-otr: mark as broken
 Author: Benjamin Hipple<EMAIL_ADDRESS> Date: Sun Mar 29 18:42:39 2020 -0400
 1 file changed, 5 insertions(+), 2 deletions(-)


Navigator swiping back gesture will cause jittering sometimes on Android

I find this weird behavior on all of my android phones, but not on any of my iphones.
I use the debugging to finally track the code cause this in Libraries/CustomComponents/Navigator/Navigator.js.
_handlePanResponderTerminate: function(e, gestureState) {
    if (this.state.activeGesture == null) {
      return;
    }
    var destIndex = this.state.presentedIndex + this._deltaForGestureAction(this.state.activeGesture);
    this._detachGesture();
    var transitionBackToPresentedIndex = this.state.presentedIndex;
    // slight hack: change the presented index for a moment in order to transitionTo correctly
    this.state.presentedIndex = destIndex;  //========>This line will cause the weird bug
    this._transitionTo(
      transitionBackToPresentedIndex,
      null,
      1 - this.spring.getCurrentValue()
    );
  },

Remove the line of 'this.state.presentedIndex = destIndex; ' will fix the bug.
And I tested a lot of times on android and ios and haven't seen anything wrong yet.
But I don't know why. This code exists in _handlePanResponderRelease also. It cannot be removed, delete it will break up the transition.
Anyone knows any ideas?

Is this a new bug or has it always been there?
If this is just a minor visual glitch then I don't think we will be able to fix it, because we are now focusing on new navigation views like NavigationCardStack.
Feel free to send in a fix, if you can figure it out!


Dumb baselines

Currently we don't know how good our baselines are against super dumb baselines:

Task 1: [1/9, 8/9] for everything
Task 2: [1/9, ..., 1/9] for everything
Task 3:

get average 'changed region' length and just pick the section in the middle
predict avg nr of 1s everywhere

Task 4: do nothing

We should probably evaluate these for ourselves at least before releasing our baselines (which will look a bit silly if they don't win!).

Task 3: Predict all 0's would probably be more accurate, similar to task 4 baseline.

I'll keep updating this comment with results.
Task 1:

F-measure = ...
Loss = 8/9 * CrossEnt([1/9, 8/9], 1) + 1/9 * CrossEnt([1/9, 8/9], 0) = 0.4645
Task 2:
Acc = 1/9
Loss = CrossEnt(np.ones(9) / 9, 0) = 2.1972
Task 3 (Predict avg nr of 1s everywhere):
F-measure = ...
Loss = ...
Task 4 (Reproduce input):
Helpfulness = 0.5 * 8/9 + 1 * 1/9 = 0.5556
Loss = ...

The above numbers are in theory. The below are in practice:
Task 1:

Either sort out maths of Task 4 dumb baseline, or rerun empirical on ACME1.0

Switched milestone because I have run on the current acme and that is in the submitted paper, but we should redo the "in practice" numbers with official ACME 1.0, when we have it.

Maybe I'll make the maths work. @apmcleod - rerun baselines on real ACME dataset.

ACME v1.0 numbers:
Task 1-3 number gotten from adding print(counts / np.sum(counts)) to get_inverse_weights and running each task with --weight. Should we make this doable without editing the code? Maybe not important.
Task 1:
[p(0) p(1)] = [0.11100006 0.88899994]
Task 2:
[p(0) p(1) ... p(8)] = [0.11100006 0.11105558 0.11127769 0.11138875 0.11111111 0.11094453
0.10938975 0.11133322 0.11249931]
Task 3:
[p(0) p(1)] = [0.93126526 0.06873474]
Task 4:
TODO

I wrote a script for this. Will push to a "rule" branch. Output:
Task 1 loss = 0.4685294032096863
Task 1 rev F-measure = 0.0
Task 2 loss = 2.1972384452819824
Task 2 acc = 0.11639271434917814
Task 3 loss = 0.4128188192844391
Task 3 F-measure = 0.0
Task 4 loss = 0.6863518953323364
Task 4 Helpfulness = 0.558196357174589


Consolidate csproj settings

use dir props to share common settings
remove default csproj values. IsPackable>false, AssemblyName and PackageId default to the csproj file name,
moved to c# 9. i am assuming u will eventually want to use some of those features

Oh, nice. I knew about that functionality, but I didn't realize how far it went.


[XSLT converter] problems on freme-live

I tried the tei2temp-html converter and it did work on freme-dev and it did not work on freme-live. So I replaced the filter on live with the one from dev and now it works on live.
Then I found out that the "identity-transformation" filter does work on dev and not work on live. This problem could not be solved by copying the filter.
Further the converter xliff20-to-html causes problems both on freme-dev and freme-live, more info here in #87
I could not test xslt-30-test and xslt-with-param because I do not have test input files.

Maybe related to #90 ?

Please create a table

converter
freme-dev
freme-live

xslt20-to.html
works
does not work

...
works
does not work

When something does not work please check if this is due to outdated data or what is the problem.

I added some example requests (including example input data) to the postman collection, but we still need example input for xslt-30-test.

\r should be no problem.
It is odd that the converters work on dev and do not work on live because the xslt converter source code did not change since the last release. But maybe this is some side effect with e-Internationalization or something similar.
Because if html-xliff20 i created #103

The converts still dont work on freme-live

@jnehring the reason is that /toolbox/xslt-converter/.* is not in the freme.einternationalization.endpoint-blacklist of freme-live.

thanks i will try this.

I added the configuration. Now tei2temp-html, identity-transformation, html-xliff-20, xliff20-to-html work. xslt-with-param does not work. I raised #110 for xslt-with-param, this issue is finished


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

Pull request for the wrong repository.


Support for Amazon Bedrock

Is your feature request related to a problem? Please describe.
No current support for Amazon Bedrock
Describe the solution you'd like
Support added for Amazon Bedrock
Due to privacy concerns with OpenAI and it's sub products, I'd love to use this with Amazon Bedrock. Direct integration with the go SDK would be awesome but either way, love to see this added.

Hey @QuinnGT, thanks for the suggestion. We're refactoring how LLM inference works in Zep. We'll consider how Bedrock might be supported.  We already support Anthropic models, albeit directly via the Anthropic API and not necessarily via AWS.

Amazon Bedrock and other inference providers are now supported via a proxy such as LiteLLM.


Added plugin repositories.

@linhpd-axonivy is there any public documentation available how to make the connector compatible with the dev-build? I can't find anything related to this topic in the official wiki
https://github.com/axonivy-market/market/wiki/c3-Market-Integration

@linhpd-axonivy is there any public documentation available how to make the connector compatible with the dev-build? I can't find anything related to this topic in the official wiki https://github.com/axonivy-market/market/wiki/c3-Market-Integration

IMHO making the connector build compatible with the dev-pipeline is a complex task to do. This provokes frustration and forces our users to dive deep into Maven, which is something we want to avoid at any rate due to the steep learning curve that must be mastered. I think it would if Octopus takes that responsibility to setup the pipeline for dev compatibility. :muscle:
We should not bother the original developers with such frustrating work. :shrug:
What do you think @linhpd-axonivy @ivy-sgi

Hi @ivy-rew ,
I checked with our team, and unfortunately, it seems we did not update any documentation for the dev-build. I think we also need to update the product-template.
Since Sabine is on vacation, @nqhoan-axonivy , could you help me take note of this issue?

Hi @ivy-rew , I checked with our team, and unfortunately, it seems we did not update any documentation for the dev-build. I think we also need to update the product-template.
Since Sabine is on vacation, @nqhoan-axonivy , could you help me take note of this issue?

the problem is that the heavy parts of the configuration live in the pom.xml the user is creating during the project setup. So you can't set them up for the user beforehand in the template.
Besides this, it's a highly repetitive task, that you may even automate in a build job. But even if there would be documentation, I think it's overwhelming for normal ivy users and if something fails, requests to our team are being to the rescue.
So I think it would be better if you take this responsibility. Sort of a post-onboarding step that you do after the contribution was added. Maybe even with a simple script that does the job for you :robot:


Feature Set, Vue CLI and some general question

What features do we want to support?
Should we build upon vue-cli and if yes which feature do we select?
Do we want to use typescript or not?
How to start best? Doing a sample jhipster project without client and build vue(cli) based client on that?

What do you think?

I created a sample jhipster project, redoing all components as Angular ones :

I used Axios as recommended by Vue documentation for http request
Vuelidate for form validation
VueI18n for dynamic translation
VueCookie ans VueX to maintain app state
Webpack configurations were inherited from vue-cli but can clearly be enhanced
Finally, I did not used TypeScript but regular JavaScript

I should add my work on a fork to let you review it (of course, it's only a draft at the moment, and should be challenged). I'll do it asap.

Sounds great. We are using a similar stack except VueX as we have quite small micro frontends so not much state management required. I would also go with plain javascript instead of typescript :+1:

Here are my thoughts:

Vue-Cli is good as it can take care of lot of boiler plate setup.
VueX is nice to have but don't really essential.
I would also go with plain javascript instead of typescript (preferred by VueJs community)
Axios is also my fav for http request.

I like @sahbi-ktifa  setup, it does cover most of our wanted features.
Vue-CLI is a good option, but based on our experiences / discussions / opinions with Angular CLI and CRA. Let us not take that.
👍 for JavaScript but Vue 3 will have a complete focus on TypeScript (so we will surely have a discussion that time whether we want to switch to that) - Just a heads up.

I agree with most of it and let's start with what @sahbi-ktifa has. Let's go with what is most used in the Vue community. I think its good to start with VueX as most of the real-world use cases would end up needing some state management. If Vue CLI is useful let's use it but we also need to ensure that the Vue support closely follows Angular/React as well to avoid defragmentation.
Regarding TS vs JS, though I was not a fan of transpiling type systems, after using TS for almost a year I really like it (when used practically and not being a type nazi) its really helpful in code management/refactoring etc and I guess will help our community which is mainly back-end people. SO if possible I would like to stick to TS as we do the same for Angular and React. And as @sendilkumarn pointed out if Vue 3 is gonna focus on TS then as Hipsters we should start that already :wink:

Here is quick read/benefits for using vue-cl version 3.
https://medium.com/the-vue-point/vue-cli-3-0-is-here-c42bebe28fbb

In that case we could use Vue CLI with typescript

I currently work on a Vue.js application integrated with JHipster as well. Here are the technologies we chose:

Vue CLI (really useful and we didn't notice any limitation until now, webpack can still be configured for extra needs), it could be the good project to try to use a CLI and see what solution is best.
Typescript (it does work very well with Vue, expect it sometimes needs a few tweaks, especially for unit tests) & TSLint
Jest for unit tests (coverage is well integrated with Vue CLI, as opposed to mocha + chai solution / however some troubles with cache)
Cypress for e2e tests (no problem using it, it works like a charm)
Axios for HTTP requests

+1 so Vue CLI with typescript, jest and cypress and tslint it is.

For e2e wouldnt it be easier to just use the protractor tests from the react client as I believe it can just work as it is without any major change

I agree with @deepu105, if the couple vue+protractor is working, we should use protractor instead of cypress.

Let's see how it works. I would suggest lets start and maybe give cypress a try as it is the preferred solution in the vue community, so if it works we don't need to maintain special configuration for protractor (writing tests is imho easiert) and we can rely on the power of the vue community and it might attract more vue developers to contribute (maybe).

@deepu105 Yes makes totally sense. Maybe just let's get started and not too much thinking about what we use for e2e testing now and decide when we need to. There is much work we need to do before.

@deepu105 In the Vue.js #q-and-a Discord channel, you can read it:

evan Hier à 18:26
@George Vue core will be refactored to use TypeScript. In that process we also plan to improve general type-friendlyness of the APIs.
^ that's for v3

@Gnuk thanks for the info.
I think we shouldn't overcomplicate stuff. Lets stick to options that are available in JHipster to start with so the stack would be

VueJS written in Typescript
Jsx or html for templates
Vuex
Vue Router
Vue CLI
Axios
Vuei18n
Sass and css options (css can be later and Sass can be default for now)
Jest
Protractor if it works without any additional work else we can switch to Cypress
Tslint , prettier

First lets migrate the default monolith app to Vue so that the default options are supported to begin with. Once thats done we can start implementing additional options. Does everyone agree? If so we can create new tickets and decide who will do what.

Except I don't know how it's difficult to have both Tslint and prettier (cf this issue), i agree with it.

I agree too.
Should I still make my work available as a blueprint even if it's only a start using JavaScript or should we rewrite it from scratch using TypeScript and all the above? If so, I'll wait for tickets 😉

I think your work should be good starting point. We can simply rename file
extensions first and should just work fine
On Sun, 19 Aug 2018, 9:28 am Sahbi KTIFA<EMAIL_ADDRESS>wrote:

I agree too.
Should I still make my work available as a blueprint even if it's only a
start using JavaScript or should we rewrite it from scratch using
TypeScript and all the above? If so, I'll wait for tickets 😉
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jhipster/jhipster-vuejs/issues/1#issuecomment-414109301,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDlF0ps0ttgZ2hO3nE3PWj01zNskGcsks5uSROOgaJpZM4WCDEx
.

@sahbi-ktifa I too agree that we will start with js and then gradually move towards ts
I would say ver.1 can be in js and then change to ts later.

@jdubois thats a good idea. I'll create tickets and assign the label for the important parts at the beginning of September. Is that ok?

Yes please do.

There is a discussion to know how to have official Vue CLI documentation on integration with backend frameworks.
I think we could participate to this discussion to help Vue.js community to help them or propose a standard documentation to have Vue CLI with Spring Boot like we'll do with this feature.
What do you think about it ?

@Gnuk yes, definitely +1
VueJS looks like a much nicer project than Angular (I don't know for React), from what I see they are trying to work with third-party projects, and that's awesome. I'll answer on their thread.

closing as its decided


[Feature] Combiantion Chart need DataZoom

What problem does this feature solve?
Expected: DataZoom

What does the proposed API look like?
none

no need any more