Disable the 8.8 Windows tests, too unreliable

Mmm could we at least compile the project, including test if possile?

Mmm could we at least compile the project, including compile test if possible?

Why? If it compiles with 8.6 Win and 8.10 Linux, doesn't that imply 8.10 Win?

Why? If it compiles with 8.6 Win and 8.10 Linux, doesn't that imply 8.10 Win?

Mmm, i am afraid there is enough cpp conditions over ghc version and windows (in ghcide and upstream packages) to break that  for some (enough?) cases

i've checked that, only if you set explicitly the rerun log with -rerun-log-file , -rerun works locally so maybe we could restore tests for all versions.
Do we have some evidence that -rerun works in linux? i'll take a look

It works fine in Linux

My motivation here is to keep CI reliable and fast. I had the pleasure of merging ~30 PRs with an unreliable CI not so long ago: it was so painful that I invested some time in improving the CI pipelines with your awesome help. That effort involved disabling the Windows jobs which were way too unreliable. When it comes to Windows, I don't even have a Windows machine to reproduce and diagnose issues.
Recently you did a lot of awesome work to reenable the Windows jobs. I just think that they are not ready and a bit more work is needed.
Windows jobs should not make CI materially slower nor unreliable. The current metrics are:

With the goal of preserving the job times under 30m and reliability at 90%, I propose the following:

Let's merge this PR to disable 8.8 and 8.10 Windows jobs
Someone send a PR that reenables the Windows jobs as they see fit.
Run that PR 10 times
When it passes 9 times and runs under 30m, it's ready to merge.

I agree with this.
But sometimes it is good to have Windows jobs to catch obvious errors. Can we run the windows jobs, but don't require them to pass before we can merge?

I agree with this.
But sometimes it is good to have Windows jobs to catch obvious errors. Can we run the windows jobs, but don't require them to pass before we can merge?

That should hopefully fit the requirements of 30m and 90% reliability, so I have nothing against it if you or anyone else wants to submit a follow-up PR.
But to be clear, I do want to run and pass the Windows jobs. What I am asking is that a) someone else takes the burden of maintaining them and b) the unreliable tests are conditionally disabled in Windows. I don't think that running the Windows jobs in ignore mode adds the same value.

I've just checked if rerun is working in linux for ghcide and i am afraid that it is not, see: https://dev.azure.com/jneira/haskell-language-server/_build/results?buildId=865&view=logs&j=4c83789f-ef27-517f-6ab9-6fdd4fc2b12a&t=18529ee9-de7e-5f9c-736e-215e246b6053
I am preparing a pr to make it work for both os's and see if that way is reliable enough

Recently you did a lot of awesome work to reenable the Windows jobs. I just think that they are not ready and a bit more work is needed.

Fair enough, but before that change the project was being compiled, including tests. So i would prefer to let it as it was for 8.8 and 8.10, keeping them as required.

I don't think that running the Windows jobs in ignore mode adds the same value.

Yes, but as someone who has no access to a windows machine, it is useful to be able to take a quick peek at CI to see that nothing is seriously broken, even if some tests are failing due to the usual unreliability.

~I've just checked if rerun is working in linux for ghcide and i am afraid that it is not, see: https://dev.azure.com/jneira/haskell-language-server/_build/results?buildId=865&view=logs&j=4c83789f-ef27-517f-6ab9-6fdd4fc2b12a&t=18529ee9-de7e-5f9c-736e-215e246b6053~
EDITED: i've double checked the linux job and the rerun only is enabled for second and third, so the second pass is always with all tests, if i am understand it correctly
I am preparing a pr to make it work for ~both os's~windows and see if that way it is reliable enough

No, your understanding is not correct. The first pass does not need --rerun

Recently you did a lot of awesome work to reenable the Windows jobs. I just think that they are not ready and a bit more work is needed.

Fair enough, but before that change the project was being compiled, including tests. So i would prefer to let it as it was for 8.8 and 8.10, keeping them as required.

No, I disabled the Windows jobs completely. You reenabled them here: https://github.com/haskell/ghcide/pull/808

I don't think that running the Windows jobs in ignore mode adds the same value.

Yes, but as someone who has no access to a windows machine, it is useful to be able to take a quick peek at CI to see that nothing is seriously broken, even if some tests are failing due to the usual unreliability.

Yes, I understand that. I am in the same position. I'm just saying that that's not the ideal outcome

No, I disabled the Windows jobs completely. You reenabled them here: #808

Ok, but they were enabled before #794 and the reason to disable the compiling at that point (not working azure cache) is fixed, right?
But well, i'll try to reenable them with tests fullfiling those conditions, they are totally reasonable.

No, your understanding is not correct. The first pass does not need --rerun

@pepeiborra i am checking tasty behaviour in windows and if i dont set --rerun tasty does not create .test-rerun-log so the next run can't use it to filter failing tests. Otoh --rerun executes all tests if the previous run is all green by default so it seems it is needed in the first step, i we want make the second run handling only failing ones.
maybe the behaviour is different in linux? or did you want to run the full suite at least two times?

I was wrong them, thanks for checking. No need to run the full suite two times!


Would it be possible to remove prefixes upon configuration bind?

config.AddAzureAppConfiguration(options =>                     {                         options.ConnectWithManagedIdentity(appConfigEndpoint)                         .Use("AppName:Service1:*","Production")                                                 .WatchAndReloadAll("AppName:Service1:Trigger", "Production", watchPolingInterval)                         .RemovePrefix("AppName:Service1");                     });
.RemovePrefix or something similar is what I am suggesting. Basically to bind the retrieved settings without the prefix so that AzureAppConfiguration automatically overrides appsettings.json and appsettings.[Environment].json
Without this 'RemovePrefix' functionality, several changes will need to be done to support both loading from appsettings and Azure App Configuration.
This is a make or break for us.

@TheReaLee, I think this is a good suggestion. Thanks!
I am thinking of an API something like this
UsePrefix(string keyPrefix, string labelFilter)

Unlike keyFilter, anything specified as "prefix" will be stripped out automatically.

After some discussion with @drago-draganov, he convinced me a dedicated API to remove the prefix is actually a better idea (@TheReaLee's original suggestion 👍).

It can be called multiple times in the chain to remove different prefixes
Decoupling the key filtering and the prefix to trim provides better flexibility

Here is the proposed API
public AzureAppConfigurationOptions TrimKeyPrefix(string prefix)

@zhenlan sounds perfect! Thanks for looking into it.
When are you planning to release it?

@TheReaLee, there are a few other changes I'd like to have before we roll out another release, but this shouldn't take too long.

This feature has been added in our most recent release. The AzureAppConfigurationOptions class now exposes TrimKeyPrefix.
Package: https://www.nuget.org/packages/Microsoft.Extensions.Configuration.AzureAppConfiguration/1.0.0-preview-008920001-990
Release Notes: https://github.com/Azure/AppConfiguration/blob/master/releaseNotes/MicrosoftExtensionsConfigurationAzureAppConfiguration.md


git don't work on mounted ntfs wolume on ubuntu 16.04

Version 1.11.1
Commit d9484d12b38879b7f4cdd1150efeb2fd2c1fbf39
Date 2017-04-06T13:55:56.395Z
Shell 1.4.6
Renderer 53.0.2785.143
Node 6.5.0

OS Version:
Mint 18 (core ubuntu 16.04)

I have WIN 10 and MINT 18 installed at the same machine. And have a additional ntfs logical disk to use  at both systems. When I put my project to this additional drive - git don't work in VSCode under Mint 18. And normally work when project placed in ~HOME.

Can you elaborate on that scenario?
What is the host OS? What is the Guest OS? Which virtualisation solution are you using?

Does it work if you run SCM: Disable Preview SCM?

I didn't use virtualisation at all. There are 2 systems at laptop HP - W10 and Mint18.1. First W10.  Hdd have 3 partitions - 1st for W10(NTFS), 2nd for arhiv (NTFS), and 3d (ext4) for Linux. The mistake appear when my files placed at the 1st or 2nd partition.

Got it. Can you still reproduce with the insider release?

I'll try in few days


Could not load required kernel module eq3_char_loop.: After today's update, pivccu3 is no more reachable

Today I did a "sudo apt update && sudo apt dist-upgrade" on my RasPi4. After doing this and a reboot, the piVCCU was not reachable, neither by web-Ui nor by ping.
The base installation consists of an iobroker (IP <IP_ADDRESS>) and a piVCCU (IP <IP_ADDRESS>) installed according to https://github.com/alexreinert/piVCCU/blob/master/docs/setup/raspberrypi.md
Some status info is in the attachment.
Thank you very much for your help.
Best regards,
Ralf
pivccu-status.txt

See #484

Thank you!


In the Azure/communication-ui-library, Can background blur be enabled on mobile devices? If so, when and how?

What feature are you requesting?
What would be the benefit of adding this feature?
What solution would be ideal for you?
What alternatives have you considered?
Is there any additional information for your request?
Attach screenshots or images add detail to your request:

@grathore1999 my apologies if we hadn't responded on the other issue where this was raised.
We are currently revisiting when we can support blur background  for android (chrome ) and iOS (safari). At this time it is currently slated early CY24. If you have any scenarios where having this feature sooner, feel free to share and we can see if we can help prioritize this feature.

Dear  Alkwa,
Thank you for your email update on the status of the blur background feature for Android (Chrome) and iOS (Safari). I appreciate the effort your team is putting into revisiting the timeline for this feature.
While I understand that the feature is currently slated for early CY24, I would like to inquire if there is any possibility of an earlier release. As a [insert your profession or reason for using the feature], I believe that having this feature sooner would significantly improve my productivity and enhance my user experience.
I would greatly appreciate it if you could share any information on the possibility of an earlier release or if there are any scenarios that would help prioritize this feature. Please let me know if you need any further details from my end.
Thank you for your attention to this matter.
Best regards,
Gagan Rathore

From: alkwa-msft @.>
Sent: 08 May 2023 20:17
To: Azure/communication-ui-library @.>
Cc: Gagan Rathore @.>; Mention @.>
Subject: Re: [Azure/communication-ui-library] In the Azure/communication-ui-library, Can background blur be enabled on mobile devices? If so, when and how? (Issue #3033)
@grathore1999https://github.com/grathore1999 my apologies if we hadn't responded on the other issue where this was raised.
We are currently revisiting when we can support blur background for android (chrome ) and iOS (safari). At this time it is currently slated early CY24. If you have any scenarios where having this feature sooner, feel free to share and we can see if we can help prioritize this feature.
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/communication-ui-library/issues/3033#issuecomment-1538484810, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZTNHWTADII5LV3424V6243XFEBRNANCNFSM6AAAAAAXZONPT4.
You are receiving this because you were mentioned.Message ID: @.***>

Sorry just found I didn't respond to this one while going through our Github issue cleanup.
The functionality at this time is based on a dependency team right now that is responsible for the background blur feature.

Closing this issue due to staleness. Please file another issue if this still persists with the appropriate details and version


Update wormhole facet with init and config

@satoshi-lifi
Can you remove the following from the PR?

deploy/012_deploy_wormhole_facet.ts
script/DeployArbitrumBridgeFacet.ts
src/Facets/HopFacet.sol
src/Facets/WithdrawFacet.sol

Also please update this script to handle the setting of chainIds

script/UpdateWormholeFacet.sol


Select from

Bug report
Describe the bug
https://supabase.com/docs/guides/storage/security/access-control
According to the storage guide there is a storage.objects table. I expected to be able to fetch data from it (with appropriate RLS), however I am getting the error:
PostgrestError(details: nil, hint: nil, code: Optional("42P01"), message: "relation \"public.storage.objects\" does not exist")

To Reproduce
I am using the following code:
            let result = try await supabaseClient.database
                .from("storage.objects")
                .select()
                .eq("name", value: "path_that_exists")
                .execute()

Expected behavior
Should we be able to query storage.objects? I took the idea from here: https://github.com/supabase/storage/issues/266

I misunderstood what was suggested in here: https://github.com/supabase/storage/issues/266
I was able to get this working but making a postgres function and calling that via .rpc


Throw error if the array passed to insert is empty

Not sure if it would be better to throw an error, but at least the behavior should be consistent.

@nickrum What happened previously in this case?

how do one create an empty query with knex? missing also tests.

@kibertoad The empty query would be forwarded to the respective database driver. The problem is that each driver handles this differently, e.g. PostgreSQL silently ignores the query, while SQLite throws a SQLITE_MISUSE error.
@elhigu An empty query will be created when insert() is called with an empty array. There might be other cases though, that I am not aware of. Would it be sufficient to add a test for this case, as calling insert() with an empty array is the higher level issue I am trying to fix with this PR?

@nickrum Since this feels like a very undesired situation, my personal preference would be to make it consistent by throwing an error always, especially since doing so later would be a breaking change.

@nickrum I would say that if the use of empty arrays allows to consistently reproduce the issue, that should be perfectly sufficient.

@kibertoad My reasoning for not throwing an error was that MySQL, MSSQL (at least before #2857) and PostgreSQL didn't throw an error (which seem to be the major vendors in use) and users might rely on this behavior. At least Directus does so in one case. But I would be fine either way.

@nickrum Since we are doing a semver major release now, breaking things should be acceptable, question is what we consider to be more helpful to the end user; from my perspective this is wrong input and user should be informed about that.
@elhigu What do you think?

I think it should throw an error. Resolving query without actually sending anything to db would be a pretty strange exception how knex behave.

I changed it to throw an error instead. Maybe it would be better to throw inside insert() directly instead of returning an empty query and throwing later.

@nickrum No other operations can potentially lead to the same outcome?

@kibertoad There are most likely others that lead to the same outcome. I thought it would be better if each operation throws it's own error, but this doesn't seem to be as straight forward as I initially thought.

@nickrum This looks good, let's adjust it later if needed. Can you mention the breaking change in UPGRADING.md?

Thank you!

You can not imagine, how many bugs appeared after this patch in the software-based exclusively on Postgres (where it worked just fine).
I don't insist, but maybe it is possible to make this behavior configurable?

@elhigu What do you think?

@maxkoryukov The way I currently see it, we generally avoid knex-scoped configuration, so even if there was a config option, it would be scoped to a specific insert operation. And if you would be doing it per operation anyway, I suspect that doing the right thing and early return in case of empty array is going to be about as much effort as disabling the empty array check everywhere.

I don't think it should be configurable. Making every piece and bit configurable just to maintain backwards compatibility will accumulate horrible mess to knex.
If you want override the behaviour in your project, you should be able to extend query builder with some method, that does not throw an error. I'm not sure, but maybe it is even possible to override the original insert with patched version.

If extending/overriding query builder methods is not working yet, that would be among other things  a good unopinionated way to provide way to people to add their own backwards compatibility layers.

Would be great if this error some more to help us track down exactly which offending insert calls:

@digitalmaster Would you consider sending PR for this?

Yup... will give it a shot 👍

Apologies for delay but finally got some time on my hands to ramp up and dig into this one 🤗
Would we be open to reconsidering throwing this error in the query builders' insert() function instead?

... Maybe it would be better to throw inside insert() directly instead of returning an empty query and throwing later.

The reason being that that's where we seem to have access to things like this toString() method which returns a query string that includes the table name (ie. 'select * from "account"').
As @nickrum already mentioned, the downside to throwing right at the query builder is that the condition would need to directly check if the insert value is empty (the only case we know of today that results in an empty query). Meaning if there are other types of inputs that also result in empty queries we'd miss those and have to iterate. The check would look something like this:
diff --git a/lib/query/querybuilder.js b/lib/query/querybuilder.js
index 43b56c54..cdcc3d76 100644
--- a/lib/query/querybuilder.js
+++ b/lib/query/querybuilder.js
@@ -1223,6 +1223,11 @@ class Builder extends EventEmitter {

   // Sets the values for an `insert` query.
   insert(values, returning, options) {
+    if (isEmpty(values)) {
+      throw new Error(
+        `Woops! Attempted to insert ${values}. Query: ${this.toString()}`
+      );
+    }
     this._method = 'insert';
     if (!isEmpty(returning)) this.returning(returning, options);
     this._single.insert = values;

I'm a complete n0ob to this project so would love any advice on the following:

Is there a known way to get access to the table name from the vendor clients' _steam / _query functions where we throw now? If so, then we could keep it where it's at for now and just update the error message.
Is there a method to get just the table name without the select * from "account"? Then error could read something like "Attempted to insert an empty array into the foo table"

Lmk if this doesn't make any sense. Appreciate the help.

I was about to ask if there was a way to get a stack trace that showed the exact location of the offending insert command and then realized that when the error is thrown from the query builder it does show the exact location of the insert command:

(My guess is that this is because the async pattern we used to execute queries)
But ya, tracking down the offending insert commands is what makes this debug time-consuming. Otherwise, it's pretty trivial.
LMK if this makes sense and I'll throw up a PR. 🙏🏽


Update _sass-material-colors-function.scss

check if vaiant is number
and add for debug color texts

@minusfive what about that?

@Kikobeats thanks for bringing it back up to my attention, and @esclkm thanks for the PR!
Apologies for not looking at this sooner, 2nd half of last year was insane on my end and this sort-of fell through the cracks. Seems good, but will take a better look at this over the weekend, and likely implement other enhancements I've had in mind for a while.


Light client inconsistently reporting transaction not found for a non-existent transaction.

I set up a local testnet ckb light client and I'm trying to query for the following transaction.
https://explorer.nervos.org/transaction/0x4bb9a6969c516dcf98f5b79271b056294190ddb3c70509f3fb089fe1097efa33
The results I get are inconsistent using fetch_transaction. If I query repeatedly I get "not_found", "fetching", and "added". It should never be present since this hash is a mainnet transaction, not testnet. Are these results expected?
Query
{
  "id": 42,
  "jsonrpc": "2.0",
  "method": "fetch_transaction",
  "params": ["0x4bb9a6969c516dcf98f5b79271b056294190ddb3c70509f3fb089fe1097efa33"]
}

Results
{
	"jsonrpc": "2.0",
	"result": {
		"status": "not_found"
	},
	"id": 42
}

{
	"jsonrpc": "2.0",
	"result": {
		"first_sent": "0x187fef819ab",
		"status": "fetching"
	},
	"id": 42
}

{
	"jsonrpc": "2.0",
	"result": {
		"status": "added",
		"timestamp": "0x187fef9f6e6"
	},
	"id": 42
}

A query using get_transaction always returns unknown.

yes, it's by design.

When is fetch_transaction supposed to be used? I do not understand it's usage based on the RPC description.

When the user sends a transaction through the light client, it will verify the transaction locally before broadcasting to the network, and if the inputs or cell deps are not locally available, for example, if a lock or type script is used that is not in the genesis block, it needs to be pre-fetched with this rpc before it can be verified successfully.


CLOUDP-112093: Validate encrypted audit log records

Proposed changes
Validate encrypted audit log records

Jira ticket: CLOUDP-112093

Closes #[issue number]
Checklist

[x] I have signed the MongoDB CLA
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added any necessary documentation in document requirements section listed in CONTRIBUTING.md (if appropriate)
[x] I have addressed the @mongodb/docs-cloud-team comments (if appropriate)
[x] I have updated e2e/E2E-TESTS.md (if an e2e test has been added)
[x] I have run make fmt and formatted my code

Further comments

Error results will be unformatted example:
{"uuid":{"$binary":{"base64":"+mOPbB12RDGgTsXXjR8R/A==","subType":"04"}},"local":{"isSystemUser":true},"roles":[],"result":0,"ts":{"$date":"2022-02-07T11:07:29.922Z"},"atype":"startup","remote":{"isSystemUser":true},"users":[],"param":{"options":{"auditLog":{"path":"auditLog.json","compressionMode":"zstd","destination":"file","format":"JSON","localAuditKeyFile":"localKey"}}}}
logRecordIdx missmatch, expected: 2, actual: 3
{"atype":"createCollection","users":[],"param":{"ns":"admin.system.version"},"result":0,"ts":{"$date":"2022-02-07T11:07:30.645Z"},"uuid":{"$binary":{"base64":"+mOPbB12RDGgTsXXjR8R/A==","subType":"04"}},"local":{"isSystemUser":true},"remote":{"isSystemUser":true},"roles":[]}
{"roles":[],"atype":"createIndex","uuid":{"$binary":{"base64":"+mOPbB12RDGgTsXXjR8R/A==","subType":"04"}},"users":[],"param":{"indexSpec":{"v":2,"key":{"_id":1},"name":"_id_"},"indexBuildState":"IndexBuildStarted","ns":"admin.system.version","indexName":"_id_"},"result":0,"ts":{"$date":"2022-02-07T11:07:30.651Z"},"local":{"isSystemUser":true},"remote":{"isSystemUser":true}}

the formatting of errors will happen on another PR

linked the wrong ticket, correct one is CLOUDP-114719


Error creating Pull request for Maven

Describe the bug
Error creating pull request for Maven dependencies
Categorization

[x] This is not a permissions issue (Seek help at https://github.com/tinglesoftware/dependabot-azure-devops/discussions/1245)

Repository
private
To Reproduce
Having a Maven dependency to org.junit:junit-bom-xxxx
Enable dependabot task v2
Expected behavior
Having a pull request with the upgrade of org.junit:junit-bom-xxxx
Logs and screenshots
error logs

    at Generator.next (<anonymous>)
    at fulfilled (/home/vsts/work/_tasks/dependabot_d98b873d-cf18-41eb-8ff5-234f14697896/2.35.955/node_modules/typed-rest-client/RestClient.js:7:58)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  statusCode: 400,
  result: {
    '$id': '1',
    innerException: null,
    message: "TF401021: 'refs/heads/dependabot/maven/master/org.junit:junit-bom-5.11.2' is not a valid name for a Git ref. Visit https://go.microsoft.com/fwlink/?LinkId=800646 for more information on Git ref naming.\r\n" +
      'Parameter name: newPush',
    typeName: 'Microsoft.TeamFoundation.SourceControl.WebServer.InvalidArgumentValueException, Microsoft.TeamFoundation.SourceControl.WebServer',
    typeKey: 'InvalidArgumentValueException',
    errorCode: 0,
    eventId: 0
  },

@olamy thanks for the report, this will be fixed in https://github.com/tinglesoftware/dependabot-azure-devops/pull/1392

Thanks


t

Summary of the PR
A short summary of this PR and what it adds/removes/fixes.
Related issues, Discord discussions, or proposals
Links go here.
Further Comments

t

6

a

a

@jit-asm

@jit-asm


Spring cleanup, no functional changes

x!=nil && len(x)>0 => len(x)>0, len works fine on nil
bytes.Equal instead of bytes.Compare
time.Since
regexps are nicer with raw strings

LGTM but we should wait until CI is back online (right?). :thumbsup:

Looks like ci1 is totally down.  I can't access it from home... @cjb if you get a chance to kick it.  Otherwise I'll look at it first thing tomorrow morning.  Likely it ran out of disk space or some such.  It was working Friday afternoon

@maxtaco Was already kicking it. Should be back up now!

Thanks!!!   What was the cause of the stoppage btw?
On Sunday, April 10, 2016, Chris Ball<EMAIL_ADDRESS>wrote:

@maxtaco https://github.com/maxtaco Was already kicking it. Should be
back up now!
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/keybase/client/pull/2573#issuecomment-208050600

You were right, disk full caused a kernel hang.

CI issues still?

i tried to kick the docker

nginx (in front of the docker) wasn't running on ci1, because it wasn't set to run on reboot and we rebooted, so I started it and added it to run at boot.  CI rerunning now.

CI has passed now.


Factories autoload

Automatically load all the module factories
Fix for #353

Agree with @ELtd, this breaks if you don't use factories but just simple a flatfile, better to restore ModuleSeedCommand.php to the previous behaviour.
cc @kaidesu

yes, both are right, I see that @nickurt sent a PR to fix this, thanks
(sorry, the delay)


Addon Folder in Cluster repository

For things like storageClasses it would be a great improvement to define a folder in the source control which automatically will be applied bei either boom or orbiter.
Where should we place such a feature?
Inputs @eliobischof @stebenz

Also @conblem feel free to comment

IMHO it would be best to define a folder in the boom.crd. The content of this folder would then be applied in each iteration.
However there is a limit in this approach... it is not intended to use as a fullblown reconciler
Possible Use Cases:

StorageClasses
Ambassador Module Configs
PersistentVolumes
Argo CRD's for easy registration of applications

that's why I would make the suggestion that we can add it in the boom-crd BUT only as argocd-application, as we already deploy a reconciler

so you mean like a cluster-addon application which contains these resources?

Exactly, as I would not use boom as a full fledged reconciler for yamls where we have no control over the contents, as testing of such functionality would also be too much at the moment.

An additional use case would be the client_id + client_secret for the used IDP(s).
This could be stored in with Gopass and then reconciled with the custom Argocd which includes gopass.

To summarise my point of view. I think we need to have to folders.
An applications folder for e.g argo applications and a addons folder for storageClasses and so on.
The we could separate the like boom applies applications and orbiter applies the addons.

Minor change from latest discussion: boom should apply both folders 💯

will be added in the next release, it is possible to configure the folders which should be applied before and after the reconciling


Fix build

@mattn Could you please resolve the conflicts? Thanks!

Well, I must close this pull-request?

Can one of the admins verify this patch?

Why no one look this?


curl and tar are not in the conda recipe

phrokka version:1.2.1
Python version:3.8
Operating System:docker, biocontainer

Description
I found the probably reason for https://github.com/gbouras13/pharokka/issues/241 and https://github.com/gbouras13/pharokka/issues/236
curl and tar are not in the conda recipe, those commands are used by
install_databases.py, which fails if they are not installed, which is e.g. the case if you use pharokka in
a container (biocontainer) and galaxy
I made a PR to bioconda (https://github.com/bioconda/bioconda-recipes/pull/40481)

Thanks Paul, I imagine they would be at the root of the issue.
The only issue with the conda recipe build I can foresee for the DB integration is that it is for the recent v 1.3.0 not v 1.2.1.
George

This is in the latest conda release now so closing


Enhancement: route level option to use model alias when serialising

Summary
Each route should have an option to specify if alias should be used when serialising (applies to pydantic for sure, perhaps other).  If route level is too troublesome, global would suffice for my needs.
I know I can use:
Starlite(type_encoder={BaseModel: lambda m: json.loads(m.json(alias=True))})

but that is clearly not good for performance and is global.
I cannot use field renaming strategies because, believe it or not, I have to interface with some systems
that use PascalCase, camelCase and snake_case all within a same (nested) model.
I found: starlite.config.OpenAPIConfig which has a by_alias=True by default but that seems to be ignored when returning pydantic models.  (Perhaps this is a bug?)
PS: I worked with "cofin" on Discord regarding this issue. He was super helpful and great to work with. Thanks again cofin for all the energy you put into this!
Basic Example
@get("/api/v1/apartment", by_alias=True)
async def get_room() -> Room:
    return await data_adapter.get_room(1)

Drawbacks and Impact
Likely additional parameters that may not be supported would need to be carried for non pydantic models.
Should be no drawbacks or impacts for the pydantic code path as model.json() is already being called.
Unresolved questions
What is the point of starlite.config.OpenAPIConfig.by_alias in your JSON schema if your returned data never conforms to it?

Funding

If you would like to see an issue prioritized, make a pledge towards it!
We receive the pledge once the issue is completed & verified

# Just tried pydantic v2 and it supports this using:
Starlite(type_encoder={BaseModel: lambda m: m.model_dump(mode="json", by_alias=True)})

Perhaps since most will be moving to pydantic v2 this isn't so important anymore and can / should be closed?

# Just tried pydantic v2 and it supports this using:
Starlite(type_encoder={BaseModel: lambda m: m.model_dump(mode="json", by_alias=True)})

The same thing works for Pydantic 1 as well. No need to do the roundtrip like in your opening post:
Starlite(type_encoder={BaseModel: lambda m: m.dict(by_alias=True)})

and is global

type_encoders are available on every layer of the application.

Incorrect I believe. A datetime for example will not be serialized into a string in v1 when calling dict. This is an important point because the model may contain special serialization for datetime objects. The mode=json feature is lacking in v1 AFAIK.
+Scott
Sent from Proton Mail mobile
-------- Original Message --------
On Sept 17, 2023, 1:51 a.m., Janek Nouvertné wrote:

Just tried pydantic v2 and it supports this using:
Starlite
(
type_encoder
=
{
BaseModel
:
lambda
m
:
m
.
model_dump
(
mode
=
"json"
,
by_alias
=
True
)})

The same thing works for Pydantic 1 as well. No need to do the roundtrip like in your opening post:
Starlite
(
type_encoder
=
{
BaseModel
:
lambda
m
:
m
.
dict
(
by_alias
=
True
)})

and is global

type_encoders are available on every layer of the application.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Incorrect I believe. A datetime for example will not be serialized into a string in v1 when calling dict. This is an important point because the model may contain special serialization for datetime objects.

This is more of a limitation of Pydantic v1 though. These special serialization won't be applied in any case, as there's no way to get to them without using pydantic's JSON serializer or doing the roundtrip thing (which Starlite does not do because it's very expensive).


Both xpip and pip fail to run

>>> cd ~/.xxh
>>> xpip install xonsh-vox-tabcomplete
usage: -c [-h] [-V] [-c COMMAND] [-i] [-l] [--config-path CONFIG_PATH] [--rc RC [RC ...]] [--no-rc] [--no-script-cache] [--cache-everything] [-D ITEM]
          [--shell-type {b,best,d,dumb,ptk,ptk1,ptk2,prompt-toolkit,prompt_toolkit,prompt-toolkit1,prompt-toolkit2,rand,random,rl,readline}] [--timings]
          [script-file] ...
-c: error: unrecognized arguments: -m

>>> pip install xonsh-vox-tabcomplete
Traceback (most recent call last):
  File "/tmp/.mount_xonshS434io/usr/python/lib/python3.8/site-packages/xonsh/main.py", line 399, in main
    args = premain(argv)
  File "/tmp/.mount_xonshS434io/usr/python/lib/python3.8/site-packages/xonsh/main.py", line 352, in premain
    env = start_services(shell_kwargs, args)
  File "/tmp/.mount_xonshS434io/usr/python/lib/python3.8/site-packages/xonsh/main.py", line 283, in start_services
    execer = Execer(
  File "/tmp/.mount_xonshS434io/usr/python/lib/python3.8/site-packages/xonsh/execer.py", line 63, in __init__
    load_builtins(execer=self, ctx=xonsh_ctx)
  File "/tmp/.mount_xonshS434io/usr/python/lib/python3.8/site-packages/xonsh/built_ins.py", line 1288, in load_builtins
    builtins.__xonsh__.load(execer=execer, ctx=ctx)
  File "/tmp/.mount_xonshS434io/usr/python/lib/python3.8/site-packages/xonsh/built_ins.py", line 1360, in load
    self.env = Env(default_env())
  File "/tmp/.mount_xonshS434io/usr/python/lib/python3.8/site-packages/xonsh/environ.py", line 1402, in __init__
    self[key] = val
  File "/tmp/.mount_xonshS434io/usr/python/lib/python3.8/site-packages/xonsh/environ.py", line 1571, in __setitem__
    self.replace_env()
  File "/tmp/.mount_xonshS434io/usr/python/lib/python3.8/site-packages/xonsh/environ.py", line 1439, in replace_env
    os_environ.update(self.detype())
  File "/tmp/.mount_xonshS434io/usr/python/lib/python3.8/site-packages/xonsh/environ.py", line 1424, in detype
    deval = ensurer.detype(val)
  File "/tmp/.mount_xonshS434io/usr/python/lib/python3.8/site-packages/xonsh/tools.py", line 1103, in detype
    return x.detype()
  File "/tmp/.mount_xonshS434io/usr/python/lib/python3.8/site-packages/xonsh/environ.py", line 364, in detype
    style = self.style
  File "/tmp/.mount_xonshS434io/usr/python/lib/python3.8/site-packages/xonsh/environ.py", line 396, in style
    style_name = self.style_name
  File "/tmp/.mount_xonshS434io/usr/python/lib/python3.8/site-packages/xonsh/environ.py", line 386, in style_name
    env = builtins.__xonsh__.env
AttributeError: 'XonshSession' object has no attribute 'env'
Xonsh encountered an issue during launch
Failback to /bin/sh
$

Any idea what I'm doing wrong?

Thank you for the reporting!

You're using legacy call for pip. Just use recommended shortcut:

python3 -m pip install --upgrade pandas

I've fixed xpip and release 0.2.11. Please update your xxh:

python3 -m pip install --upgrade xonssh-xxh

Then update host:
$ xxh yourhost +iv
yourhost$ xpip --version
pip 19.3.1

You can update pip easily: xpip install --upgrade pip

To install xontrib just run:

xpip install --upgrade xonsh-vox-tabcomplete

After that xontrib list could shows that the xontrib is not installed but pip list shows. I have one way to update xontrib list: just disconnect and xxh to server again and the xontrib will be "installed" in xontrib list.
So let's load:
$ xontrib load vox_tabcomplete
<unknown>:1: DeprecationWarning: invalid escape sequence \w
xonsh: For full traceback set: $XONSH_SHOW_TRACEBACK = True
NameError: name '__xonsh_completers__' is not defined

This error for this xontrib I've got also on my local and I suppose you know what to do with xonsh_completers, isn't it? :)

I've fixed pip also in xxh 0.2.12. Please update your xxh:
python3 -m pip install --upgrade xonssh-xxh

Looks like closed.

Thanks for the quick response! Yes, I can now xpip install :-)

AttributeError: 'XonshSession' object has no attribute 'env'
Xonsh encountered an issue during launch
Failback to /bin/sh

@seanfarley I've found the case of this error and it was fixed in xxh 0.3.0

AttributeError: 'XonshSession' object has no attribute 'env'
Xonsh encountered an issue during launch
Failback to /bin/sh

@seanfarley thank you for reporting this! It's related with https://github.com/xonsh/xonsh/issues/3055 and I'm going to fix it in xxh 0.3.1


Start removing Duzzt-generated QueryBuilder

What this PR does:
Removes QueryBuilder and SchemaBuilder in order to remove use of Duzzt; in turn needed to go to JDK 20.
Which issue(s) this PR fixes:
Fixes #
Checklist

[x] Changes manually tested
[ ] Automated Tests added/updated
[ ] Documentation added/updated
[x] CLA Signed: DataStax CLA

First commit is breaking hard; this is planned. Will try to figure out how to rip apart things succesfully; this requires replacing use of QueryBuilder (and possibly SchemaBuilder) with direct CQL use but via DataStore.


Lib.Exponentiation: rlimit bump

Routine rlimit bump, just randomly ran into this due to (I believe) editing Prims in F* for a soon-to-be-merged PR. This should fix it.
Types of changes
What types of changes does your code introduce to HACL*?
Put an x in the boxes that apply

[x] Proof maintenance (non-breaking change which fixes a proof regression)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New algorithm or feature (non-breaking change which adds functionality)
[ ] Improved performance (fix or feature that would improve performance of some algorithm on some platform)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[X] I have read the CODE_OF_CONDUCT.md doc
[X] I have read and agree to submit my changes under the LICENSE
[ ] I have added necessary documentation (if appropriate)
[ ] I have edited CHANGES.md (if appropriate)

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

Thanks Guido!


Add migration to set the GKE integration as deprecated

https://github.com/Shippable/pm/issues/9159

verified on rc


Kusama styling

Collection of previous smaller styling PRs. This is not complete, but would like to merge to keep this PR from growing.

Looks very nice. Just I think we should plan to make both style variants consistent since we want to merge the the codebases eventually after the campaign.

Apologies, I made a git mess, which made this un-reviewable. Started fresh branch from my last clean commit. PR here


Clarification regarding dockremap subuid/subguid addition

File: engine/security/userns-remap.md
Consider this warning:

Warning: Some distributions, such as RHEL and CentOS 7.3, do not automatically add the new group to the /etc/subuid and /etc/subgid files. You are responsible for editing these files and assigning non-overlapping ranges, in this case. This step is covered in Prerequisites.

Since dockremap is a system user (original commit) , it is the behavior of adduser to not add entries to /etc/subuid and /etc/subgid. Hence, the warning regarding the behavior being an issue on CentOS/RHEL seems incorrect? It is really a documented/expected behavior i think?

Issue will be addressed in editing pass. Closing ticket.


definition of origin

I know it was me who proposed to have origin as a field in SAND schema, but having a coordinate may be a self-referencing.
For example, if a space defines the origin to be [75,135,12], assuming um as unit, it is 75um, 135um, 12um from where?
I wonder if the origin should be an enum (PIR origin of volume FILENAME.nii.gz) or an ontology (Weighted center of hippocampus)

The idea is that the image origin is in relation to the right-hand-rule.
A fixed coordinate space where the origin can be described.
On Tue, Oct 8, 2019, 10:48 xgui3783<EMAIL_ADDRESS>wrote:

I know it was me who proposed to have origin as a field in SAND schema,
but having a coordinate may be a self-referencing.
For example, if a space defines the origin to be [75,135,12], assuming um
as unit, it is 75um, 135um, 12um from where?
I wonder if the origin should be an enum (PIR of volume FILENAME.nii.gz)
or an ontology (Weighted center of hippocampus)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/HumanBrainProject/HBP-SAND/issues/8?email_source=notifications&email_token=AADDHHBOGLRM2PXHQ35KXNDQNRCMBA5CNFSM4I6OY3JKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HQJCRLQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADDHHB4KBMQVN4335OXPO3QNRCMBANCNFSM4I6OY3JA
.

This is part of the "axes.schema.json". See #35

This is very outdated and I think fixed, too. I will close this issue.


add a min height to the  div

at the moment it causes resizing jumps while the content is loading

fixed by https://github.com/theDavidBarton/the-harry-potter-database/pull/65


add support of nonces

Replace seed:string to Seed{phrase:string, nonce:number}.

You can create seed with nonce and use it.
import { seedWithNonce, randomSeed, address } from '@waves/waves-crypto'

const nonce = 1
const seedphrase = randomSeed() // uncle push human bus echo drastic garden joke sand warfare sentence fossil title color combine
const seed = seedWithNonce(seedphrase, nonce)

//Now you can use seed as usual
address(seed)


regenerating cast_chann.pb.go

It looks like it was using an older version of protobuf which pointed at code.google.com which was causing errors when trying to go get the project.

My protoc version
$ protoc --version
libprotoc 2.6.1

Looks like this one also addresses the same problem as #3 and #4...


Share and QR as single CTA or on one screen

All these screens should show the QR and link as a secondary option. This applies to

F&F request screen
Receive screen
Keeper request screen
Keeper reshare screen
we would need the QR and link on the first screen as well

Discussed with Sumaiah

Discussed with Sumaiah

More @Arpanjainson note:

When sharing the link, the OS sharing modal should open, and not our modal that we have designed, the benefit is that it is in-app and once you have done that, the user is back in the app. Copying the link to another app leaves the user outside of the app leading to some confusion as there is no message as to what to do.
On sharing the link, currently we show a very good OTP screen (when the skip is done), we need a similar screen telling the requested that the contact has to enter his phone number to confirm the identity and which phone number or email ID it is. The OTP screen does that very well.

More @Arpanjainson note:

When sharing the link, the OS sharing modal should open, and not our modal that we have designed, the benefit is that it is in-app and once you have done that, the user is back in the app. Copying the link to another app leaves the user outside of the app leading to some confusion as there is no message as to what to do.
On sharing the link, currently we show a very good OTP screen (when the skip is done), we need a similar screen telling the requested that the contact has to enter his phone number to confirm the identity and which phone number or email ID it is. The OTP screen does that very well.

Guidance from @Arpanjainson: When sharing, display the OS provided modal for sharing and don't show the current modal that is being displayed.

Proto link - https://xd.adobe.com/view/181f3fd2-7aca-4284-61c7-3417e1fe6d8a-6e2e/screen/cb495627-64b9-46ce-9e33-f73da4b50b14

As per comments on bug #2801Latest screens: https://xd.adobe.com/view/3df97271-f272-4dae-975d-95d4785f1b30-68aa/
Latest screens
https://xd.adobe.com/view/7636e956-af9b-4300-bc63-4c3eab0d4f71-2365/screen/538324fe-2358-4d10-939f-86c872b151a3/
Request Share
Request Share – Share
Request Share – OTP
Request Share – Copied Successfully Toast
Request Share – Message shared with trusted contact – Email
Request Share – Message shared with trusted contact – Phone
Accounts – Receive
Accounts – Receive – Enter Amount

-Verified this issue on Dev app v1.7.0 (286)


Allow merchant to set store currency

Let merchant choose which currency his product prices are denoted in. Refer to the top of this Zeplin screen.

Related: #285

This is merged now


Problem with profile

http://i.imgur.com/vjNnZJ0.png
Why?

Hard to say with the given information. The user in question could still be online on an alt. It also may not have updated at the time. Let me know if this user still appears to be online in profile and i'll see if i can help you out if you need more support.

He was offline.
Why profile's last seen doesn't update?(Sorry for my english)

?

@Latios1 He probably got dced and somehow didn't emit the socket.disconnect event so the seen wasn't able to record or his user object wasn't deleted yet so it show him as online.


Handle @beta in reference items

This adds support for a @beta tag in our jsdocs to label a feature as experimental.
There aren't any of these on main yet, but I'm considering using it for shader hooks in https://github.com/processing/p5.js/pull/7149. Here's how it would look for that:
On the reference listing, beta APIs get a flask icon:

On an individual item's reference, it gets a little explanation on the top:

Thanks @davepagurek. How do you feel about changing the highlighted background color to the reference page theme yellow color #deed33?

Sounds good, updated! Here's what that looks like on an arbitrary reference item as an example:

Looks great, thanks @davepagurek!


Information on Conditional Access for Device State and Filter by Device for Government Clouds

We are on the GCC High cloud, but there is no information on the Device State and Filter By Device preview features that indicate the feature availability, lack thereof or time line for availability in the GCC High or other Government Clouds.   Is this information available somewhere and can it be added to the page?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 625bb1b2-81fd-9804-c0b5-3cd2904decd9
Version Independent ID: e4468b05-200e-24ae-75e9-29fb2b3a6ddc
Content: Conditions in Conditional Access policy - Azure Active Directory
Content Source: articles/active-directory/conditional-access/concept-conditional-access-conditions.md
Service: active-directory
Sub-service: conditional-access
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@jonl-percsolutions-com
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

The feature is in preview so is not currently available in GCC High. #please-close

@MicrosoftGuyJFlo The point of this ticket was the lack of documentation on whether or not it was available.


pr-welcome-msg.yml: add message and ticket template for CI issues

Can one of the admins verify this patch?


dedicated cache database not created with steps from readme

When I follow steps from here  to create dedicated cache database, I run command rails db:create but get only response that my dev database already exists. And cache_development has not been created
# database.yml
default: &default
  adapter: postgresql
  encoding: unicode
  pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>
  url: <%= ENV["DATABASE_URL"] %>

development:
  <<: *default
  database: my_app_development
  cache:
    database: cache_development
    url: <%= ENV["DATABASE_URL"] %>
    migrations_paths: "db/cache/migrate"

what am i missing? I'm using postgresql, does it supported with this syntax?

oh, my bad, that works 🙈
development:
  primary:
    <<: *default
    database: my_app_development
  cache:
    database: cache_development
    url: <%= ENV["DATABASE_URL"] %>
    migrations_paths: "db/cache/migrate"


chore: patch psl to avoid deprecation warning

Summary
See https://github.com/nodejs/citgm/pull/959#issuecomment-1712467647

Test plan
Green CI

Might be better to use a patch that's checked into the repo


Disallow redefine names in the same scope of do/let

for the moment, following code compiles
do {
  a = 3;
  a = 42L;
  print(a); // outputs 42L
}

This behavior is weird for a functional programming lang
(edited) and for let expression
let
  a = 3;
  a = 42L;
in
  print(a); // outputs 42L

This should be allowed neither

There are other possibilities for it to go wrong
let
  a = (2, 3);
  (x, a) = a; // rebind a
in
  print(a); // outputs 3

and
let
  a = {x=3, y=4};
  {x=p, y=a} = a; // rebind a
in
  print(a); // outputs 4

Being a Haskell-alike lang, those behaviors should not be allowed.
But fixing them takes more work

But in the examples I gave, they are in the same let clause let a = 3; a = 4 ... not nested ones like let a = 3 in let a = 4.... The latter is clearly name shadowing (keyword let and different scopes), the former one is rather confusing to say the least

Don't let do notations or let block déclarations fool you, they're eventually rewritten as a series of nested let expressions.
do { a = 1; a = 2; print(a); } is morally equivalent to let a = 1 in let a = 2 in let _ = print(a) in ()
Note, the variable _ can be the subject of multiple let bindings:
do print(2); print (3); becomes let _ = print(2) in let _ = print(3) in (). There's nothing wrong in this

Don't let do notations or let block déclarations fool you
That's my beef with it, it fooled more than me

I was aware of this rewriting to nested let behavior, after going through yacc file. However, we cannot and should not expect other people to understand this by reading parser code
do { a = 3; a = 4; } looks like a reassign or rebind, and it turns out to be neither.
Based on the principle of least astonishment, we have some options,

If this behavior is designed on purpose and well defined, not just a side affect, then at least we should document the design decision well somewhere, and keep fingers crossed that people will find it and read it
Get the compiler panic on this, because it might do what the programmer wants it to do, but the reason could be wrong. Because normally it is a logic error somewhere in his/her code

Hobbes has no notion of rebind, so I'm not sure where you're pulling this from. The doc only mentions local variable introductions, which is what is happening here. My guess is, those getting fooled by this notation are expecting the semantics of the language to be the same as that of C++. This is wrong, and people should read the doc of the language instead of making assumptions on how it's supposed to work.
Does the following also look illegitimate to you? do { a = 1; (do { a = 2; print a;}); print a; }? It's no different that than the notations you're trying to block in the above. It is perfectly legit to have different environments reusing the same name. They are in different environments after all. In imperative languages, they call these blocks, and use { ... } to delimit them. In Hobbes, we'd use ( ... ) as shown above ^. This is done in this way, because there are no statements in hobbes, only expressions that evaluate to values (same as in Haskell, Rust, ...).
Also, note that your current change addresses this issue only from the perspective of the parser. There are more ways (especially using the C++ bindings) one can build let bindings and come with local definitions that'd bind the same name in nested environments as in the above. RPC can also be used to build these very same let bindings. In a sense, this change doesn't work.
One more thing, the title of the ticket implies that there's a notion of "the same scope on do or let" in Hobbes. This is not true and it is misleading as, otherwise, these scopes would be somehow destructive. Each introduction of a new binding creates a totally new scope, different from the previous one. It's described in the doc in the section "local variable definitions". It may be that the doc isn't clear enough, so it should be improved (do notations aren't documented, so they need to be added).
I did mention earlier a more subtle (serious bug) issue in hobbes with the handling of pattern bindings, I actually did open a few tickets, here's one of them:

https://github.com/morganstanley/hobbes/issues/138#issue-333109561

The pattern matching engine is a critical piece Hobbes,  and the above issue is the closest to what you're trying to fix here.

Hobbes has no notion of rebind, so I'm not sure where you're pulling this from.
That's the problem, in C++/Java/Rust/Haskell, a {} defines a scope, { a= x; a = y; } is a rebind/redefine/reassign/re..., doesn't matter language itself allows it or not. I put this in title because it looks like name rebind in the same scope (I was aware of nested scopes get created at the time, but I still chose this very title because that's what it looks like)

But how could a hobbes programmer expect names in a simple {} creates nested blocks? Hobbes has different rules, names in {} creates nested scope, not rebinding/re..., doesn't matter how much it looks like, that's creates surprises, surprises are bad unless for a really really good reason. in C++/C/Java, same name cannot be reused in  {}, but it is ok in { { } }, Haskell is no exception. (Rust allows its, but hobbes is not rust-alike)
If there's a good reason to be so, then it should be better documented. If not, then this behavior should be changed

As for the Local Variable section in doc. It uses an let example, we understand whatever names defines in let are only valid till the end of let .. in expression, because it has the same behavior as Haskell
However, the problem we're talking about is more like this, still in REPL
> a = 3
> a = 4
stdin:1,5-5: Variable already defined: a

I know REPL works differently, but people are expecting "If it looks like a duck, swims like a duck, and quacks like a duck, then it probably a duck"
How do we expect others to spend time on understanding this subtlety for a simple =?

Hobbes has no notion of rebind, so I'm not sure where you're pulling this from.
That's the problem, in C++/Java/Rust/Haskell, a {} defines a scope, { a= x; a = y; } is a rebind/redefine/reassign/re..., doesn't matter language itself allows it or not. I put this in title because it looks like name rebind in the same scope (I was aware of nested scopes get created at the time, but I still chose this very title because that's what it looks like)

But how could a hobbes programmer expect names in a simple {} creates nested blocks? Hobbes has different rules, names in {} creates nested scope, not rebinding/re..., doesn't matter how much it looks like, that's creates surprises, surprises are bad unless for a really really good reason. in C++/C/Java, same name cannot be reused in  {}, but it is ok in { { } }, Haskell is no exception. (Rust allows its, but hobbes is not rust-alike)
If there's a good reason to be so, then it should be better documented. If not, then this behavior should be changed

What you say about Haskell isn't true! {...} in haskell delimits a syntactic block. Curly braces introduce no new variable bindings at all, let alone, they don't even define a scope in Haskell. So I'm unsure what makes you say "Haskell is no exception".
Hobbes is inspired from Haskell, not C, not Java, and not C++. Again, it's important to read documentation, and not make assumption that everything that uses curly braces quacks, then it's [like] C++.

As for the Local Variable section in doc. It uses an let example, we understand whatever names defines in let are only valid till the end of let .. in expression, because it has the same behavior as Haskell

Hopefully you do! And if so, then it should be easy to explain what happens in the REPL. When you let a = 1 in a + 1, you are introducing a new variable a and binding it to the value 1. At the end of the let expression, you can't use a as a replacement for 1 anymore. In a sense, the scope has starting point and an ending point with let expressions.
When in the REPL, what would that scope be? When you first write a = 3 in the repl, you are really saying "From now on, a is 3". In Hobbes REPL, this is true for the rest of your REPL session (that is, until you shut it down). Haskell GHCi allows rebinding a to a different value, but Hobbes doesn't. Two design choices that work, and I can understand both sides.

However, the problem we're talking about is more like this, still in REPL
> a = 3
> a = 4
stdin:1,5-5: Variable already defined: a

I know REPL works differently, but people are expecting "If it looks like a duck, swims like a duck, and quacks like a duck, then it probably a duck"
How do we expect others to spend time on understanding this subtlety for a simple =?

Document it in simpler words that = is not assignment at all. It's equivalent to a proposition. They should read a = 1 as variable a binds to the value 1, or a is 1. Saying a is 1 and a is 2 is absurd, at least in propositional logic.
If you want to assign a new value, then you have the <- operator. The following should then work (if you disable checks for unsafe calls):
a = newPrim() :: int
a <- 2
a <- 3

foo = \_ -> let a = 3
                a = 4
            in a + a

reports
<source>:1:17: error:
    Conflicting definitions for `a'
    Bound at: <source>:1:17
              <source>:2:17
  |
1 | foo = \_ -> let a = 3
  |                 ^^^^^...

in Haskell. Even for people have c++/c/java background expect this behavior
In hobbes,
foo = \_.let a = 3;
             a = 4;
         in a + a

foo() gives 8
I might argue there are some similarities in those code snippets, but surprisingly differently behaviors.
I'm not saying hobbes IS haskell, despite multiple places in documentation mentions haskell. I'm saying hobbes should have the same behavior as haskell
But at least, we should limits language surprises as much as possible. Just like you said

Saying a is 1 and a is 2 is absurd, at least in propositional logic.

Then at least, we should let compiler panic and tell programmer his/her code probably has logic error, error message can be something like
name conflicts, rebinding not allowed in hobbes
1. if you want to reassign, please use <- instead of =
2. otherwise, please use different names to avoid confusion

The following works in Haskell, and that's the simplest behavior for let that Hobbes is also implementing
ghci> foo = \_ -> let a = 1 in let a = 4 in a + a
ghci> foo ()
8

Like I said earlier, Hobbes rewrite all let expressions in the above form, and there's nothing to it. Haskell doesn't always do that, as it supports let constructs for various cases (monadic, comprehensions, let blocks, ... all of them are different things in Haskell).
There are various ways to implement let expressions, and some of them are even used in monadic operations. Hobbes obviously doesn't support all of them (we don't have real monads there); it's a matter of choice:

https://en.wikipedia.org/wiki/Let_expression
https://stackoverflow.com/questions/8274650/in-haskell-when-do-we-use-in-with-let

Then at least, we should let compiler panic and tell programmer his/her code probably has logic error, error message can be something like

I believe you didn't follow my previous explanation; that's exactly what the compiler complained about when you tried it  in the REPL:
> a = 3
> a = 4
stdin:1,5-5: Variable already defined: a

It's a matter of scope definition, that's the point I was making earlier. In a REPL, that scope is the whole session. In a compiled program, that scope is delimited by let expressions, so there's no possible conflict.

I'm not saying hobbes IS haskell, despite multiple places in documentation mentions haskell. I'm saying hobbes should have the same behavior as haskell

Haskell allows the following, which Hobbes doesn't allow. Your whole point is that we shouldn't allow binding variable names in let expression; and Haskell does allow this in certain cases. And you want Hobbes to have the same behavior as Haskell, which is to allow binding variable names to new values as in Haskell.
ghci> let a = 1
ghci> let a = 4
ghci> a + a
8

The above is plain Haskell. I don't follow you anymore.

If you are so concerned about the possibility for Java developers to get confused about the above, then the issue is that they don't understand the rewrite rules around let blocks. Remove that rewrite rule around syntactic sugars such as do and series of let. Then let (pun unintended) these devs write ground expressions with the simpler syntax
let x = value in expr. No more do blocks, no more let blocks in Hobbes. I have to warn you, these syntactic sugars are there for  a reason: that is to increase expressiveness for Hobbes developers.

Let me set the record straight on what I've been talking about

I've never said we should stop rewriting code from let a =3; a =4;... to let a0=3; let a1=4... internally, haven't I?
What I said is, this rewriting has corner cases confused programmers, doesn't matter they got this kind of code by accidently copy-past, forgot what's going on in the beginning of this block, or even genuinely believe this code is legit
The two examples I gave in my previous post, they are not from REPL. Like I mentioned above, I do know hobbes REPL behaves differently , so it should not be used for comparison
Normal programmers do not nor should not care about the complier design internals for a simple =

Everything boils down to, in your words,  a=3; a=4 is "absurd", but compiler silently accept that code, is this a fact?
My whole point from my first post is simply: Should the compiler be more helpful that it should tell programmers that theirs code makes no sense?

Let me set the record straight on what I've been talking about

I've never said we should stop rewriting code from let a =3; a =4;... to let a0=3; let a1=4... internally
What I said is, this rewriting has corner cases confused programmers, doesn't matter they got this kind of code by accidently copy-past, forgot what's going on in the beginning of this block, or even genuinely believe this code is legit
The two examples I gave in my previous post, they are not from REPL. Like I mentioned above, I do know hobbes REPL behaves differently , so it should not be used for comparison

Why not? the principles of let evaluations stay the same if you understand they're always evaluate in a context of variable assignments. These principles are the same whether you're in the REPL or in a compiled program. I strongly recommend you read about propositional logic and their evaluation judgments if you haven't already, because this is no different.

Normal programmers do not nor should not care about the complier design internals for a simple =
This is highly subjective. What's a normal programmer? A Java developer? A C++ dev? or one who reads about the semantics of a symbol such as = before applying it?

Everything boils down to, in your words, a=3; a=4 is "absurd", but compiler silently accept that code, is this a fact?

You are ignoring the context (the scope), so this isn't 100% correct. This is absurd if you consider a single scope (as is done in the REPL), but it is not absurd if each binding introduces different scope (as that's the case in let evaluation for compiled programs).
One can't make a statement, show it's True for a single instance, then consider it a proof of it being universally True like you do here.

My whole point from my first post is simple: Should the compiler be more helpful that it should tell programmers that theirs code makes no sense?

Good point, but remember: the example you are flagging as being universally absurd is no different than
do { a = 3; (do { a = 4; print a;}); print a; }. Would you call this absurd too?
How about the following? Is this absurd to you as well?
  mo.C ✕  +
   1 auto main () -> int {
   1 │ auto a = 3;
   2 │ │    a = 4;
   3 │ return a+a;
   4 }

I'm surprised to see your response to the word "absurd", that makes me realized that I might misunderstand what you've said

It's equivalent to a proposition. They should read a = 1 as variable a binds to the value 1, or a is 1. Saying a is 1 and a is 2 is absurd, at least in propositional logic.

say, in hobbes code, when you see something like
let
  ...
  a = ...
  ...
  a = ...
in ...

Current compiler is happy to compile this code, but are there any better(correct?) ways to do whatever the programmer wants it do?
From your previous post, I thought your answer is Yes, there are better ways to fulfill his/her purpose
Seems I got your answer wrong. So it really depends on your answer to this, then we might have a totally different discussion
My standing on this PR is simple, it is all about ergonomics

Unlike some intermediate to advanced features, we might have to understand how compilers implement them and why they implement it in this or that way. = supports to be simple, IMO, it is unreasonable to expect programmers to read through papers and thesis before pressing the = key
We're human, we make mistakes. If I see code like a=...;a=...; in hobbes, I believe there might be better/clearer ways to do whatever the author of this code wants to do. Being fit in theory is less important. Let the compiler to be programmers' friend is more important

Let's say we have a c++ code like this
struct X {
  T foo() const;
};

Any C++ compilers will be happy to compile this code, because it is legit C++. but clang-tidy still warns me that it might be a good idea to add [[nodiscard]], because it is a pure function, without using its return value, I probably just heat up cpus for no reason, I either forget to remove some dead code, or there are logic errors buried deep in my code. And C++ is infamous for lacking of proper tools as you're well aware
We write bugs with perfect grammar, tools can help
I couldn't figure out what kind of functionalities in reality can only be achieved by a=...;a=..., so I consider programmers are making mistakes when they write code like this

I believe what you want is a way for the compiler to check for potential name shadowing and flag them for you. You don't want to prevent advanced users from writing these expressions. You want a way to lint your programs, so the compiler can warn you on potential name shadowing issues.
Guess what? We do have support for Optional flags and the ability to extend the compiler with new flags. @dawa79 (Dan Wang) can walk you through how he agreed the -o no-Safe option extension to Hobbes, and you could do something similar.
There's a macro expansion stage in the compiler pipeline, where you can run your checks. Even better, you could run your linter at the same place as where Dan wrote the checks for unsafe expressions.
Don't ever change the parser though, for no reasons. You hardly ever need to change the parser, except for compelling cases. See the parser as the contract Hobbes has with its users. You never want to break this contract.

I couldn't figure out what kind of functionalities in reality can only be achieved by a=...;a=..., so I consider programmers are making mistakes when they write code like this

I'm lazy and find it hard to invent new variable names each time I need one. Seriously, I don't think variable names are an infinite resource; it's not. The compiler is the buddy that figures names out for me, so I can focus on engineering solutions for harder problems.
Isn't that the whole point about Lambda calculus? Names don't really matter... But I'm digressing, I'll stop it here now.


Cairo Most Common types and Trait

issue #141
Added a page in appendix where it shows the most common types and trait.

LGTM for now, let me check if we should add more stuff.

Okey i resolved it already. Thank you so much


Fix month length in  provision date

Hi,
In 006,008 conversion, the length of the month is incorrect set to 4 digits. I changed it to position 11-12 instead.
David

Thanks, we'll take a look.


chapter 1 and 2 edits

Purpose/implementation Section
What changes are being implemented in this Pull Request?
What was your approach?
What GitHub issue does your pull request address?
Tell potential reviewers what kind of feedback you are soliciting.
New Content Checklist

[ ] New content/chapter is in an Rmd file with this kind of format and headers.

[ ] New content/chapter contains Learning Objectives and are in the correct format.

[ ] Bookdown successfully re-renders and any new content files have been added to the _bookdown.yml.

[ ] Spell check runs successfully in Github actions style-n-check).

[ ] Any newly necessary packages that are needed have been added to the Dockerfile and image.

[ ] Images are in the correct format for rendering.

[ ] Every new image has alt text and is in a Google Slide.

[ ] Each slide is described in the notes of the slide so learners relying on a screen reader can access the content. See https://lastcallmedia.com/blog/accessible-comics for more guidance on this.

[ ] The color palette choices of the slide are contrasted in a way that is friendly to those with color vision deficiencies.
You can check this using Color Oracle.

Also I think the issue with the style and spell check workflow has to do with github secrets that would need to be set up for your forked repo... I believe they might need to match those for our main repo but not sure. You could try creating similar git secrets as described here: https://github.com/jhudsl/OTTR_Template/wiki/Setting-up-GitHub-secrets. I don't think you would need to do the Docker portion, but we shall see.

also might have some conflicts

All looks good! Could we make line 20 and 24 headers with the hashmarks ### that way they will show up in the TOC to make them more prominent?

This is done!


Wrong variant image color in the cart

I am not sure why this code was added here to override lineitem.ImageUrl, but we have FetchLineItemInformationActivity and it sets correct varaint.ImageUrl, but for some reason this additional activity overrides it and is always set to Base Product.ImageUrl
Without this code we have correct variant images in the Cart:

AB#71514

I am pretty confident that you won't see the Image in MSF if you remove the code in that activity.
If that's the case, I would suggest to revert what you removed and add something like this in the code to get the image from the Variant instead
if (!string.IsNullOrWhiteSpace(lineItem.VariantId))
                {
                    var variant = product.Variants.FirstOrDefault(v => v.Id == lineItem.VariantId);
                    if (variant != null)
                    {
                        imageUrl = variant?.PropertyBag?.GetOrDefault(ImageUrlKey, null);
                    }
                }
It is important we keep that functionality in the activity as we need that to see images in MSF. Any other suggestions that would not break MSF are welcome. Keep in mind, we do that only for BetterRetail for demo purposes.

@joclefrancois I created order on website and in OMS, with variants and without and validated in in MFS, images were present:


Sheet Select dialog override is broken on v9

Need to set DocumentSheetConfig instead of EntitySheetConfig.
This is done, but SHEETS.EntitySheetHint needs to be SHEETS.DocumentSheetHint on v9. Can't easily toggle this so currently it's set correct for v8. When we switch to supporting v9 it can be toggled back and this issue closed.

Switched back to the default sheet select and enabled their sheet name localisation mechansim.


Added my app to the list of apps that use the library

Thanks for the great library!

Current coverage is 100% (diff: 100%)

Merging #5 into master will not change coverage

@@           master    #5   diff @@
===================================
  Files           7     7
  Lines         252   252
  Methods         0     0
  Messages        0     0
  Branches        0     0
===================================
  Hits          252   252
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update 70c6d9b...1494457

Thanks, @aabosh! Cool app btw.


Do no schema verification checks if AutoCreate == None

You do still have the explicit IDocumentSchema.AssertDatabaseMatchesConfiguration(), but otherwise, if AutoCreate == None, don't check the schema at all.
Causing us issues at work. We suspect it's from getting too cute with database GRANT's and ROLE's, but we don't know that for sure.

Any benefit from adding a fifth option between "None" and "CreateOnly" perhaps called "CheckOnly"? Maybe YAGNI but possibly makes the auto create api clearer and more explicit. Just a thought.

Um, yeah, maybe. You do have the Assert() to find any differences. Mind adding that as an enhancement issue?

will do


dynamic_batching_test error

Trying to run: dynamic_batching_test and get the following error:
This error occurs several times I show only the last one.
.
----------------------------------------------------------------------
Ran 18 tests in 8.532s

OK
ERROR:tensorflow:Exception in QueueRunner: GetInputs operation was cancelled
	 [[Node: BatcherGetInputs = BatcherGetInputs[Toutput_list=[DT_INT32, DT_INT32], _device="/job:localhost/replica:0/task:0/device:CPU:0"](Batcher)]]
Exception in thread QueueRunnerThread-batcher-BatcherSetOutputs:
Traceback (most recent call last):
  File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.5/threading.py", line 862, in run
    self._target(*self._args, **self._kwargs)
  File "/home/rjn/.local/lib/python3.5/site-packages/tensorflow/python/training/queue_runner_impl.py", line 252, in _run
    enqueue_callable()
  File "/home/rjn/.local/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1244, in _single_operation_run
    self._call_tf_sessionrun(None, {}, [], target_list, None)
  File "/home/rjn/.local/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1409, in _call_tf_sessionrun
    run_metadata)
tensorflow.python.framework.errors_impl.CancelledError: GetInputs operation was cancelled
	 [[Node: BatcherGetInputs = BatcherGetInputs[Toutput_list=[DT_INT32, DT_INT32], _device="/job:localhost/replica:0/task:0/device:CPU:0"](Batcher)]]

The tests actually run correctly (as you can see with OK). The output is from tests that tests error scenarios. Could probably be removed from the output.


[#179506968] Enable point-in-time restore for MySQL

What
The feature is available and used in production, but doesn't have an
integration test.
How to test
Don't, for now.

This should be working now.
In the end it needed me to implement the ResetState method for the MySQLEngine, which really just involves dropping all the non-superusers.
Then it was just a matter of enabling it and the mysql versions of the relevant tests.
As for testing it - I'm not sure there's a better way than the integration tests which we have running on ci.

I've just realized that the MySQLBroker should have unit tests added for the new ResetState implementation.


Chef encountered an error attempting to create the client WITH [[Scalr]]

Description
Briefly describe the issue
I have configured the Java cookbook with RunList ["recipe[java]"] chef-solo configuration in Scalr UI of Refer Image 1 (Scalr is Cloud Management Platform). I have download cook book from URL and upload in S3 Bucket to use it as HTTP in Scalr ( Refer below image )

When Scalr launch AWS instance (Ubuntu 14 trusty version) successfully
Desire Expected Service from Chef in AWS Instance:
1.Chef should install the Java in my newly created AWS instance (Ubuntu 14 trusty version ) but there no java installed (Refer Image)

Chef client should install in AWS Instance but it throw error (Refer Image3)

Cloud you please help why Java and Chef client not installed....????
Chef Version
Tell us which version of chef-client you are using (see below for Server+ChefDK bugs).
Chef Client, version 11.18.0
Tell us which Operating System distribution and version chef-client is running on.
Ubuntu 14 trusty
Replication Case
Tell us what steps to take to replicate your problem.  See How to create a Minimal, Complete, and Verifiable example
for information on how to create a good replication case.
Client Output
The relevant output of the chef-client run or a link to a gist of the entire run, if there is one.
The debug output (chef-client -l debug) may be useful, but please link to a gist, or truncate it.
Stacktrace
Please include the stacktrace.out output or link to a gist of it, if there is one.
NOTE: CHEF CLIENT BUGS ONLY
This issue tracker is for the code contained within this repo -- chef-client, base knife functionality (not
plugins), chef-apply, chef-solo, chef-client -z, etc.

Server issues
ChefDK issues
Cookbook Issues (see the https://github.com/chef-cookbooks repos or search Supermarket or GitHub/Google)

Thanks for filing a GitHub Issue.
At Chef, we use GitHub Issues to track bugs and feature requests. Questions like "How do I .... with Chef?" are better answered by our awesome community on the Chef mailing lists, or on StackOverflow. (Please pick only one place to ask your question, however, as it's considered impolite to post the same question to multiple forums.)
You can find information about joining and asking questions on our mailing lists here. On StackOverflow, please tag your question with the "chef" label so that it shows up in this list.
We will be closing your issue. Please get in touch with the community via the above mechanisms in order to find a solution to your problem.


thetvdb_favorites.py not working

After this discussion on the Flexget forum ( http://discuss.flexget.com/t/thetvdb-favorites-not-working/2208 ), I decided to open an issue here.
The new TVDB API Auth ( https://api-beta.thetvdb.com/swagger ) requires: {"apikey":"APIKEY","username":"USERNAME","userkey":"USERKEY"}
I took a look at the thetvdb_favorites.py plugin, and it seems like it calls the API in this way:
'username': {'type': 'string'},
'account_id': {'type': 'string'},

Still, it's not clear the difference between these values from TheTVDB (I tried every possible combination):

Account Identifier
Site User ID
Username
Password

and which ones are required by the plugin. The documentation (http://flexget.com/wiki/Plugins/thetvdb_favorites) it's not updated and doesn't help.
I don't know if it's related to an auth error or not, but this is the only error I get from Flexget:
2016-04-18 10:56 INFO configure_series download Did not get any series to generate series configuration

I just updated the doco..
It should just be
thetvdb_favorites:
  username: <username>
  account_id: <account identifier>

Also, make sure you are on the latest version of flexget as there were a few api changes a few days back.

please re-open if u have issues


initial import of rules

these rules are not perfect, they will have to be improved

@alexvonme please review my first version

Hey @Jason3S I would like you to give me an advice about how to merge my changes.
I don't have much experience as you do with license.
Look at the PR description.
Do you think I should split my PR in multiple one to somehow be able to track from where come each word?
It might be a burden for me because this list is the result of more than 2 years of cherry picking to validate my own markdown.
But I could if needed, please let me know.

Copying a word or two from different sources is not generally copyrighted, but taking whole lists of words is.

Thanks you so much @Jason3S for review this alpha project I asked out of the blue  without much context.
My current work is to provide rules for vale, as it's my need.
Then I may go in a larger direction as described in #1

#1

I might write something like glosario or frontend-encyclopedia (links are on the quoted discussion)
I expect to create something that could be used to get definition, maybe project URL.
Available as a yaml, JSON, a readme

To give you a better context of what a vale package look like
You can have a look this rule
https://github.com/errata-ai/packages/blob/master/pkg%2FGoogle%2FGoogle%2FGenderBias.yml
Available in the Google Style rules implemented by Vale
https://vale.sh/hub/google/

@ccoVeille here are my overall thoughts:

Both superlative files depend on copyrighted content and should be removed.
TechnologySpecials,yml depends on a Wikipedia article which utilizes CC BY SA which is not a permissive license and therefore the file should also be removed.
I don't understand the reason you added Suggestions.yml since other organizations already have their (usually larger) versions of that file and wouldn't utilize it.

As such, I'd suggest that you remove all files excluding Technology.yml which we can discuss and expand in this pull request with #6 and #8.

@ccoVeille here are my overall thoughts:
* Both superlative files depend on copyrighted content and should be removed.

I removed, it was something I had locally that I pushed by errors.
There were files

* TechnologySpecials,yml depends on a Wikipedia article which utilizes CC BY SA which is not a permissive license and therefore the file should also be removed.

I removed them, as I found a way to deal with extension

* I don't understand the reason you added Suggestions.yml since it's not an exhaustive list.

This is open for debate, but I can remove them from initial import

As such, I'd suggest that you remove all files excluding Technology.yml which we can discuss and expand in this pull request with #6 and #8.

It's what I just did

hey @Jason3S
my project starts to look like an alpha version of what I imagined, there are still many things to do, but I progressed a lot since I started.
I plan to support export to cspell format #16

#16

For now, I can simply copy the term I collected and a open PR on https://github.com/streetsidesoftware/cspell-dicts/tree/main/dictionaries/software-terms
What do you think ?

hey @Jason3S
my project starts to look like an alpha version of what I imagined, there are still many things to do, but I progressed a lot since I started.
I plan to support export to cspell format #16

consider a master YAML files with all the rules and description #16

For now, I can simply copy the term I collected and a open PR on https://github.com/streetsidesoftware/cspell-dicts/tree/main/dictionaries/software-terms
What do you think ?

Adding to the Software Terms is fine.
I am thinking about improving file based dictionaries to be more complete. We can talk about it on a different thread.

That's the purpose of jargonLint I will be more than happy to discuss about it.
I would prefer the discussion to be on jargonLint repository, but I would understand if you prefer to do it on cspell-dicts repository

@alexvonme pushed back, please review and merge

Reading through it one last time, will merge quickly.

I fixed the one you reported, plus a few one I found by looking at all the file

It might be a good idea to consider removing these 3 commonly used words from the rule:

rest (listed as REST)
react (listed as React)
ok (listed as OK)

That's right.
We will need a exclusion list to avoid adding them back if someone asks for it.
I mean we should document we don't want them and why.
For now, I'll comment them.

Fixed


@motify/skeleton: Fixes backgroundSize prop not being passed down to AnimatedGradient

Skeleton accepts a prop backgroundSize that is supposed to change the resolution of the gradient created by the skeleton. This prop was not being passed down and was statically set to 6 inside the AnimatedGradient component.
This PR moves setting the default value to props and passes the prop down to AnimatedGradient.
Current functionality remains the same.

Side note: while developing, the two AppEntry.js files in /examples/with-*/__generated__/ were changed without my intervention. I did not commit these two files. Was I supposed to?
They following line was automatically changed:
import App from '../App';
to
import App from '..\..\..\node_modules\with-expo/App';

You can ignore the generated files, they shouldn’t be committed


Change default color

We should change the default color from white to black or primary since it is confusing, if the component is used and you don't see anything.
An alternative would be to remove the default color and make the color required.

I'd argue that primary or success would be gould candidates, but they only work together with vuetify. Maybe we could check if they are defined before?


Refresh by replacing document body instead of using header

Co-authored-by: Étienne Barrié<EMAIL_ADDRESS>Closes: https://github.com/Shopify/maintenance_tasks/issues/510, https://github.com/Shopify/maintenance_tasks/issues/569
This is an alternative approach to page refreshing, that should solve some of the complaints folks had with the meta tag usage (losing search abilities, making it difficult to copy/paste text, etc.)
We don't want to jump straight to Turbo for a couple of reasons:

We'd need to make it an explicit dependency / configure it properly for support in pre Rails 7 apps
The gem doesn't use any assets currently / doesn't force embedding apps to use the asset pipeline, so it's tricky make the JS component for Turbo work
Turbo includes a lot of stuff we don't need to achieve the desired behaviour (page refreshing)

@etiennebarrie and I came up with a fairly simple solution to replace using the http-equiv="refresh" attribute for refreshing, but that sticks with plain JS. We essentially just swap out the document body in an inline script that uses window.setInterval() to run repeatedly. The script's SHA is included in the allowlist for the gem's CSP.  This preserves the ability to do things like Cmd+F to search for tasks.

@etiennebarrie I realized that one issue with this approach is that the body will continue to be refreshed after the task finishes because setInterval is never cleared. If the user manually refreshes or navigates away from the page it will stop, but if they stay on the page the function will continue to run. Do you think that's problematic?

Some key points:

losing search abilities

We're still reseting the browser search, but at least we're not scrolling up.

making it difficult to copy/paste text

Your selection is also lost when the refresh occurs. I wonder what people copy though. Even with the current hard reload, if you've right clicked on a link, you can still copy it after the page reloaded.
I think this helps a lot simply by not scrolling around too much, but it's still not ideal. I wonder how hard would it be to only refresh the progress bars, and the description about the status, without touching the rest. I guess we'd also need to move the tasks at their right spot (they might have been completed or started).

I tested on Safari and noticed the style was broken (the stylesheet was never linked). We can't rely on the Sec-Fetch-User header we were using, so I sent the "Rails" one so that we can use Request::xhr?.

the body will continue to be refreshed after the task finishes

I changed the approach a little bit: we're always including the script, but only refreshing if the body doesn't have a data-refresh attribute.

Definitely still not perfect, but I agree that the scrolling was the main issue. The browser search resetting is not too bad if you've already navigated to your task on the index page, and losing your selection also matters less if the page doesn't move because you can just reselect.

I guess we'd also need to move the tasks at their right spot (they might have been completed or started).

I think this is the trickiest part. Even if we were to rely on something like Turbo, if tasks are moving from one section to another (for example new => active => completed), it would refresh the contents of those sections and you'd lose search /  text selection anyways.
Nice fix for the refreshing! 👌


'UserWarning: Optimal rotation is not uniquely or poorly defined for the given sets of vectors'

When building a MOF with edges I often get this warning.
For example, here I make a MOF using the 'tsg' topology. The three node building blocks I have selected are ones that have the correct number of connection points and they have an RMSD of < 0.3 with the relevant local structure.
`import pormake as pm
node_0_name='N10'
node_1_name='N216'
node_2_name='N421'
edge_0_name='E196'
edge_1_name='E51'
database=pm.Database()
node_0=database.get_building_block(node_0_name)
node_1=database.get_building_block(node_1_name)
node_2=database.get_building_block(node_2_name)
edge_0=database.get_building_block(edge_0_name)
edge_1=database.get_building_block(edge_1_name)
nodes=[node_0,node_1,node_2]
edges={(0,1): edge_0, (1,2): edge_1}
database=pm.Database()
tsg=database.get_topology('tsg')
builder=pm.Builder()
mof=builder.build_by_type(topology=tsg,node_bbs=nodes,edge_bbs=edges)
`
I get this output:

== Min RMSD of (node type: 0, node bb: N10): 1.21E-05
Pre-location at node slot 0, (node type: 0, node bb: N10), RMSD: 2.36E-05
RMSD > MIN_RMSD1.01, relocate Node 0 with 216 trial orientations, RMSD: 2.36E-05
RMSD > MIN_RMSD1.01, relocate Node 0 with 216 trial orientations and chiral building block, RMSD: 1.21E-05
== Min RMSD of (node type: 1, node bb: N216): 4.79E-02
Pre-location at node slot 1, (node type: 1, node bb: N216), RMSD: 1.62E-01
RMSD > MIN_RMSD1.01, relocate Node 1 with 216 trial orientations, RMSD: 4.79E-02
Pre-location at node slot 2, (node type: 1, node bb: N216), RMSD: 1.21E-01
RMSD > MIN_RMSD1.01, relocate Node 2 with 216 trial orientations, RMSD: 4.79E-02
Pre-location at node slot 3, (node type: 1, node bb: N216), RMSD: 1.21E-01
RMSD > MIN_RMSD1.01, relocate Node 3 with 216 trial orientations, RMSD: 4.79E-02
== Min RMSD of (node type: 2, node bb: N421): 1.39E-01
Pre-location at node slot 4, (node type: 2, node bb: N421), RMSD: 1.39E-01
Topology optimization starts.
No GPU/TPU found, falling back to CPU. (Set TF_CPP_MIN_LOG_LEVEL=0 and rerun for more info.)
MESSAGE: CONVERGENCE: REL_REDUCTION_OF_F_<=_FACTREPSMCH
SUCCESS: True
ITER: 83
OBJ: 0.019
Location at node slot 0, (node type: 0, node bb: N10), RMSD: 1.47E-03
Location at node slot 1, (node type: 1, node bb: N216), RMSD: 1.68E-01
Location at node slot 2, (node type: 1, node bb: N216), RMSD: 1.62E-01
Location at node slot 3, (node type: 1, node bb: N216), RMSD: 1.74E-01
Location at node slot 4, (node type: 2, node bb: N421), RMSD: 8.29E-02
Start placing edges.
/opt/conda/envs/.../lib/python3.9/site-packages/pormake/locator.py:20: UserWarning: Optimal rotation is not uniquely or poorly defined for the given sets of vectors.
U, rmsd = scipy.spatial.transform.Rotation.align_vectors(p, q)
Start finding bonds in generated framework.
Start finding bonds in building blocks.
Start finding bonds between building blocks.
Start making Framework instance.
Construction of framework done.

Which includes the error I mention:
/opt/conda/envs/.../lib/python3.9/site-packages/pormake/locator.py:20: UserWarning: Optimal rotation is not uniquely or poorly defined for the given sets of vectors.
Does this matter? Are some edge building blocks incompatible with some topologies?
Thanks.

In most cases, locating edge building blocks is not an issue,  it is just an alignment of two lines with unit length. So I would say you can disregard that warning.

OK thanks.


PubVersionFinderResponse in plugin_tools should also handle pre-release versions when sorting

The current approach of PubVersionFinderResponse in plugin_tool does not consider pre-release versions when sorting all the version. So if a pre-release version is introduced, the auto-publish ci will fail.

I believe I fixed this for a package that needed pre-release support.


Add client id for v2 broker support

Add client id for v2 broker support
More context https://github.com/WalletConnect/walletconnect-specs/issues/60

Challenge: https://gist.github.com/pedrouid/a09452a25b0dbf90ee269601874554a7

[ ] - JWT
[ ] - JWT Signer
[ ] - JWT Encoder
[ ] - SocketAuthenticator
[ ] - ED25519DIDKeyFactory
[ ] - ClientIdStorage
[ ] - AuthChallengeProviding
[ ] - Add Bearer to Web socket request


SvgCached not working correctly.

🐛 Bug Report
For some reason, some countries flag (US, Taiwan) are not rendered properly in SvgCachedImage - https://restcountries.eu/data/usa.svg
https://restcountries.eu/data/twn.svg
Expected behavior
It should render properly, I have used the SVG data from the flag on other website and it's working properly.
Reproduction steps
I have attached the sample with the issue.
SvgCachedImageIssue.zip
Configuration
Version:
PackageReference Include="Xamarin.FFImageLoading.Forms" Version="<IP_ADDRESS>2"
PackageReference Include="Xamarin.FFImageLoading.Svg.Forms" Version="<IP_ADDRESS>2"
PackageReference Include="Xamarin.Forms" Version="<IP_ADDRESS>5"
PackageReference Include="Xamarin.Essentials" Version="1.3.1"
Platform:

[ ] :iphone: iOS
[x] :robot: Android
[ ] :checkered_flag: WPF
[ ] :earth_americas: UWP
[ ] :apple: MacOS
[ ] :tv: tvOS
[x] :monkey: Xamarin.Forms

Screenshot from the sample.

I have tried this one as a workaround and it's working well - https://github.com/muak/SvgImageSource


Added format verbs

Related go docs: https://pkg.go.dev/fmt#hdr-Printing
I really wanted this feature and https://github.com/tree-sitter/tree-sitter-go/pull/85 seems to be kind of stale so I did my best attempt here.
_interpreted_string_literal_percent_sign seems like a hack but I haven't figured any other way to tell tree-sitter to treat % just as part of a string literal in one special case (when% is at the end of the string).
The other thing I haven't figured out is highlights.scm. When trying to install local go TS with TSInstall newly added hls do not get applied (and in fact the structure of ~/.local/share/nvim/site/pack/packer/start/nvim-treesitter/queries/go/highlights.scm is quite different. Am I doing it wrong?
I've added related test to literals and removed format verb from statements.
This PR does cover all format verbs cases in an interpreted_string_literal but does not cover different usecases for the literal. (using it as an argument to fmt.Println etc. makes format verbs useless)
Checklist:

[x] All tests pass in CI.
[x] There are sufficient tests for the new fix/feature.
[x] Grammar rules have not been renamed unless absolutely necessary.
[x] The conflicts section hasn't grown too much.
[x] The parser size hasn't grown too much (check the value of STATE_COUNT in src/parser.c).

Great work, hope this feature gets merged soon!

Also very excited for this!

I don't think that Tree-sitter should parse these format verbs. They aren't part of the string literal's syntax; they're just a pattern that the Printf family of functions looks for. For syntax-highlighting these things, I think it would be better to handle it with some kind of separate layer of logic, like language injections.

I think highlighting the printf format is fine. The format verbs are basically different kind of escape sequences and those are already captured. The decision is easier for languages with string interpolation (e.g. javascript with ${}).
Linking this as another place where this was discussed: https://github.com/nvim-treesitter/nvim-treesitter/issues/2917

FWIW this would greatly benefit editors to easily distinguish format verbs and highlight them differently, rather than rely on injections/regex-based matching.
I too would love to see this merged

FYI
https://github.com/nvim-treesitter/nvim-treesitter/issues/2917
https://github.com/nvim-treesitter/nvim-treesitter/commit/f2119df35cdcdb0c6c9bf791a04000d4d131cef7


Can not find semikong models

You guys do great work but I can't find your models in huggingface, have they been taken offline?

I also noticed this, please link to the right models in the README.

I didn't find it either.