Feature/weekend days

-disabled weekend days

update gradle

This looks like a good feature to have.
I will try to do a detailed review later this week.

Thanks , I wait for review my commit
On Tue, Apr 9, 2019, 6:33 PM wdullaer<EMAIL_ADDRESS>wrote:

This looks like a good feature to have.
I will try to do a detailed review later this week.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wdullaer/MaterialDateTimePicker/pull/576#issuecomment-481326494,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Au4hey1_PLtdYMjDkIt9Ud8q-wKetiBYks5vfMDXgaJpZM4cWEWn
.


Alpha 7 an alpha 8 are not fully released

https://docs.rs/crate/pallet-staking/2.0.0-alpha.8
Last successful build is alpha 6.
Please add a step to release pipeline to make sure the released version is actually compilable.

I am getting the same error as docs.rs and I can't identify what causes the error by looking at the code. There isn't any _phragmen::sp_runtime.
But I suspect this issue have something todo with the build pipeline modify Cargo.toml file during release. Pulling crates from tags in Github works perfectly fine.

@xlc the sp-phragmen-compact problem will be fixed by yanking the 2.0.0-dev.1 version. This will be done shortly by us.

The crate is yanked, please make sure that the specific version is removed from your Cargo.lock.

@bkchr cargo update seems fixes the build issue we have.
I will leave this open as I think there needs to be some process to ensure docs.rs builds successfully on publish.

Docs.rs could not build because of the same error. So, I going to close this. In the end it was an error that happened quite some time ago.


HCP: remove IngressController OwnerRef

Fixes the guest cluster ingress proxy.  The HCP does not exist in the same namespace as the IngressController and, if the Owner does not exist in the same namespace as the resource, garbage collection immediately removes the resource.

/lgtm


Import from attention.py error

I can't seem to import from attention.py
pip install git+https://github.com/mlfoundations/open_lm.git
Stuff like these work without any issues:
from open_lm.data import get_data
from open_lm.main import main
It fails when I try to import from open_lm.attention
from open_lm.attention import ATTN_ACTIVATIONS, ATTN_SEQ_SCALARS
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: cannot import name 'ATTN_ACTIVATIONS' from 'open_lm.attention' (unknown location)

hi @sedrick-keh-tri  what version of open_lm are you on? can you try pip install -U git+https://github.com/mlfoundations/open_lm.git in your environment?

Hmm, I'm tried that and I'm on 0.0.27 but it still doesn't seem to be working.
Anyways, I tried it on a ray environment and it worked there, so the issue is likely with my environment. Closing this issue.


Fixed webhook uri name as it cause an error.

@insearching Can you please update the main.yaml with the latest actions/checkout@v2 so that the internal build gets passed?

@insearching I fixed the main.yaml. Never mind.


 - Can change incremental step as double value? Like '0.1'

Hello, Hope you are doing well.
I am using  component of MUI.

import TextField from "@mui/material/TextField";

<TextField type="number"/>

Now, the default incremental value of  is 1.
I want to change it 0.1.
So my question:

Can I change the incremental value?
Or How can I receive the events when the spin (increase/decrease) buttons are clicked?

Kind Regards.

Currently, <TextField type="number"/> it use a native html number input. What you want is not supported at this moment.
Please follow this issue about NumberInput instead. I am closing this one.

hello i whant to eliminate increment and decrement for number type
const getFieldProps = (fieldName: string) => {
const inputProps: any = {
name: fieldName,
value: formik.values[fieldName],
onChange: formik.handleChange,
onBlur: formik.handleBlur,
error: formik.touched[fieldName] && Boolean(formik.errors[fieldName]),
type: columns[fieldName].type === "number" ? "number" : "text",
style:
columns[fieldName].type === "number"
? {
// Stili per Webkit browsers come Chrome e Safari
WebkitAppearance: "none",
// Stili per Mozilla Firefox
MozAppearance: "textfield",
}
      : {},
};


Installing package from npm.pkg.github.com requires auth token

Installation from //npm.pkg.github.com/ should be public and not require an auth token.

For now only workaround is to configure ~/.npmrc with:
//npm.pkg.github.com/:_authToken=...


Consolidate troubleshooting docs between azure-apps and iis

Right now, the troubleshooting docs between azure apps and iis have a lot of duplication between them. We should consider cross-referencing shared components to minimize duplication.
There are also many issues filed in ASP.NET Core that effectively say "500.30 ANCM Startup failure". I think it would be nice to have an equivalent doc that SignalR has for diagnostics: https://docs.microsoft.com/en-us/aspnet/core/signalr/diagnostics?view=aspnetcore-3.0. This can also use cross-referencing to share details with troubleshooting.
cc @guardrex @shirhatti @anurse thoughts?

I think this is a great idea. That SignalR doc has been a fantastic resource for improving the quality of user bug reports. Even if they don't find it immediately, we can respond to bug reports with "Check out this doc and use it to collect some logs pls?" and they either find the issue and realize it's their code, or give us much more detailed information that makes reproduction and investigation easier.

This might be tricky to pull off. The instructions for working in the two scenarios aren't the same in several respects.
Azure ...

Relies on Kudu for some approaches.
Has different paths that it must call out.
Uses monitoring blades for some scenarios.
Has cross-references to specific content in Azure docs that only apply to Azure scenarios.

It might work out ok ... it's just a point of concern that I have. I see the duplication. However if the process of dealing with those duplicated aspects (the same error or logging) results in just cutting-and-pasting full sections from each doc into one, I wonder if it really accomplishes anything. If I were an Azure reader or an IIS reader, I'd only want to see what applies to my scenario and not have to skip/read past a lot of non-applicable guidance.
Seems like a draft of the combined doc would help understand how this might work. Do you want me to give it a go and see how it turns out?

Regarding Azure:

Relies on Kudu for some approaches.

I reallllly wish we didn't need to rely on Kudu. But I agree that is a difference.

just cutting-and-pasting full sections from each doc into one, I wonder if it really accomplishes anything.

For example, this PR I just made has two entirely duplicated sections https://github.com/aspnet/AspNetCore.Docs/pull/12605

Do you want me to give it a go and see how it turns out? If so, I need more detail on "cross-referencing" ... what exactly do u want to do? Combine topic content into one doc that resides in the Test, debug, troubleshoot area of the TOC, then cross-link that from the Host and deploy node topics (and elsewhere)?

Let's start with just cross referencing between IIS and azure apps with a shared source. I'll take care of the creating a doc for diagnostics/test/debug/troubleshoot. after we flesh out some of the structure.

I'm still working toward #12605 ...... buried in a Blazor tutorial at the moment but hope to be free soon.

I reallllly wish we didn't need to rely on Kudu. But I agree that is a difference.

Kudu is often the best tool to debug on Azure.
@guardrex  how clumsy would it be to put the shared content in includes? If it's alot of includes and only used in two places, you're usually better off copy/paste with internal <!-- Comment, this is copied from -->.

Significantly shared content ... almost duplicated exactly ... is the bit at the tops of these docs that describe the way errors manifest themselves (mostly HTTP status+messages in the browser IIRC).
I'll take a 🔪 stab at getting one topic in the Test, debug, troubleshoot area. If these two topics combine well into one topic, then there won't be a need for INCLUDES. Hopefully, they will compose well into one topic. 🤞

NOTE: This issue remains open because more work is planned. On #12954, the process was started ... combination and relocation of troubleshooting topics. More content work is on the way tho in a future PR. The details are TBD at this time (6/28). I'll move this out to the July sprint for now.


[BEAM-3645] add thread lock for ParallelBundleManager

This PR adds thread lock when appending data to buffers, otherwise, we may miss some data.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @lukecwik
Is it possible to do a quick review for this PR? Thank you.


Define EE responsibility for hart forward progress

This adds a generic forward progress definition into the normative text of Section 1.2.
One question came up.  That section appears to freely alternate between the terms "execution environment" and "execution environment interface", without establishing anywhere that they are equivalent or otherwise what distinguishes them.  Are they in fact, equivalent terms?

EEI and EE aren't equivalent terms---to make an analogy, EEI is to ABI as EE is to OS kernel---but I think the terminology is abused in some cases.

I've committed this with some stylistic adjustments; LMK if there are any more quibbles. 9a39b75241914a210d1f4f7a342d62743cd1dcb7


[API RFC] Support IColumn.if_else for Boolean Column

cond.if_else(a, b) -> IColumn, the output is defined as:

out_i = a_i if cond_i is True
out_i = b_i otherwise

API Demo
>>> import torcharrow as ta
>>> cond = ta.Column([True, False, True, True])
>>> a = ta.Column([1, 2, 3, 4])
>>> b = ta.Column([10, 20, 30, 40])
>>> cond.if_else(a, b)
0   1
1  20
2   3
3   4
dtype: int64, length: 4, null_count: 0

Current API
It's currently called ite in Boolean Column: https://github.com/facebookresearch/torcharrow/blob/0dbe14d399b766a2dfd596e35cb7843e7514ad59/torcharrow/icolumn.py#L848-L853
API in other frameworks
PyArrow
pyarrow.compute has if_else. Note instead of being a member function to BooleanArray, it's a standalone function in pyarrow.compute package that takes 3 arguments (cond, left, right)
Pandas
Doesn't seem to have same method?
NumPy/PyTorch/TensorFlow
NumPy provides np.where: https://numpy.org/doc/stable/reference/generated/numpy.where.html
PyTorch provides torch.where: https://pytorch.org/docs/stable/generated/torch.where.html
TensorFlow provides tf.where: https://www.tensorflow.org/api_docs/python/tf/where
R
ifelse as a standalone function: https://www.rdocumentation.org/packages/base/versions/3.6.2/topics/ifelse
But in general, R seems to prefer standalone functions instead of fluent-style API.
Discussions
Shall we make ta.if_else as standalone function that takes 3 arguments in torcharrow package (rather than a member methods in BooleanColumn`)? -- This is similar to Arrow Compute, PyTorch and TensorFlow.

Standalone function (if_else(cond, x, y) ):

ta.if_else(a < 1, a, 1)

ta.if_else(
    tf.contains([1, 2, 3], a),
    a, b
)

cond.if_else(x, y)

(a < 1).if_else(a, 1)

tf.contains([1, 2, 3], a).if_else(a, b)

Resolved by  https://github.com/facebookresearch/torcharrow/pull/56


[TEST] Testing PR #1704

Testing PR #1704
Delete

Confirmed the new Github Action works successfully, closing


Bluetooth: Mesh: Fix mesh shell compilation without provisionee support

cmd_pb_adv and cmd_pb_gatt are only used when provisionee role is
supported. They should not be compiled if provisionee role is disabled.
Signed-off-by: Pavel Vasilyev<EMAIL_ADDRESS>

@PavelVPV does this fix a GitHub issue?

@PavelVPV does this fix a GitHub issue?

Which one?

@PavelVPV does this fix a GitHub issue?

Which one?

No no, this was a question from my side. I assume the answer is "no" :)


Certificate Depth not saved in new OpenVPN interface

Important notices

[X] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[X] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
When setting Certificate Depth in the new OpenVPN interface the setting is not saved
To Reproduce
Steps to reproduce the behavior:

Open settings for OpenVPN instance in 23.7 interface
Set a value for Certificate Depth and save the settings
Open the settings again
Setting is not saved

Expected behavior
Setting should be saved
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 23.7(amd64, OpenSSL).

This was https://github.com/opnsense/core/issues/6692


C-SCALE computing resources: take them or lose them!

Hi!
This use case currently has the following resources allocated:

Compute: 48 vCPUs at CreoDIAS, 20 vCPUs at GRNET Cloud plus the capacity at GRNET HPC
Storage: 2 TB at CreoDIAS, 1 TB at GRNET Cloud plus 13 TB at GRNET HPC

Do you think that's enough for the next 9 months? C-SCALE currently has spare capacity that can be allocated now, so if you need to scale up, please let us know asap!
If we don't hear from you by Friday 30th Sept we will assume that you don't need more capacity and we will then reuse the spare capacity in C-SCALE for other use cases.
On the other hand, if you no longer need C-SCALE computing resources, please let us know as well as they will be reused properly.
Best regards,
C-SCALE

cc: @backeb @lorincmeszaros

Hi @sebastian-luna-valero
For the HiSea use case our next steps are:

wrap the docker containers in a workflow engine such as snakemake
figure out how to do a hybrid deployment to run parts of the workflow on the GRNET HPC, and other parts on the GRNET cloud.

We also want to do performance tests with the current cloud workflow, including:

comparing performance on CPU-intensive VMs vs RAM-intensive VMs

We would run the workflow for longer periods, e.g. simulating one or multiple years instead of the 5 day simulations we've been testing on.
We would still like to use CREODIAS and GRNET for these tests, but I'm not sure if we will consume all allocated resources.

Hi @backeb
Thanks for this input.
Some initial comments:
You have 1M CPU hours at the HPC, if we count from here to the end of the project (9 months, 730 hours in average per month), that's 152 cores running all time, which is not small amount.
Snakemake supports sending parts of the workflow to kubernetes and to a batch system, so I assume you could use the same tool for interacting both with cloud and HPC. Is that your plan? If so, could we get started by deploying kubernetes on the cloud allocation for GRNET?

Woah! Yeah that's a lot of HPC.
I've posted messages internally at Deltares to ask if anyone is interested in using HPC for their simulations.
I doubt we will consume all of that.
cc @lorincmeszaros


[hbase] Add kerberos authentication for HBaseClient.java

For running YCSB on secure Hadoop.

this will be a great addition. thanks for working on it!

Hi @busbey ,
Thanks for your comments. The modification has been committed.

looks good to me. I'll grab a secure hbase cluster to test it tonight. If someone else beats me to hit, feel free to hit the merge PR button.

Sorry that the final smoke test slipped my schedule. I'll get to this today.

just noticed this is targeting the 0.2.0 RC branch. I've cherry picked it over to master. I'll test it there and then push.

Testing against a kerberos-enabled cluster, it looks like the client works without this patch if I kinit ahead of time. Can we pare this down to the support for logging in via a provided keytab and the additional instructions?
Logging in via passed keytab isn't working for me, and there's nothing obvious in the logs. Could we add some logging, both to indicate that we're going to authenticate via kerberos (like what principal and the path to the keytab) and if we think it succeeded?
I can confirm that the keytab I'm using works, because I can kinit with it ahead of time and then rely on the extant kerberos support.

Figured out why the keytab logins aren't working. Please make sure you also update the hbase-10 client. I'll need to find an hbase 0.94 cluster to test the older client.

Hi @busbey,
I execute YCSB on HBase 0.98 with kerberos, which provided by HDP 2.2 distribution. Even I kinit ahead of time, YCSB is still failed on kerberos authentication, so that I patch the hbase client to make it works.
This patch is not added to hbase-10 client because I have such cluster for verification, and I am glad if someone could do the verificatino.

A 0.98 cluster to test the hbase client is much easier for me to find, thanks for the heads up.
If you include the changes for the hbase-10 client I can test them on the cluster I'm already testing against.

Okay, so against a 0.98 cluster I can use both the hbase and hbase-10 clients when the cluster is insecure.
Once the 0.98 cluster has kerberos, I can't run the client either before or after your changes. It appears to hang and then after a substantial amount of time shows a bunch of errors. Can you add some more logging so it's easier to figure out what's gone wrong?

Today I install the latest HDP 2.2.6 distribution, running HBase <IP_ADDRESS>.2 with kerberos-enabled.
In this environment, YCSB execute successfully if kinit ahead of time, or with kerberos parameter of my patch. If any one of these methods not applied, YCSB will fail.

This got auto-closed because the 0.2.0-staging branch was deleted with the release. Sorry about that. Could you reopen with your changes rebased onto master?


Sl/update docs

Prep the other files in Documents for new term.
Updated links.
Recompiled all tex files to get updated header.
Should be merged after #9
cc @cc7768 to merge when ready

merging now, Will fix one more thing off new master


Suggestion: Always put @id field on top in introspection result

Right now, introspection orders all fields of a model alphabetically. Due to the special status of @id fields primary key, I suggest to have an extra rule for those and always put them into the model as the first first. For example:
before
model Profile {
  bio  String?
  id   Int     @id
  user User
}

after
model Profile {
  id   Int     @id
  bio  String?
  user User
}

DECISION: we will not look into this before the initial release of Prisma Query.

As I'm working on https://github.com/prisma/upgrade I'm feeling the pain of this schema field shuffling.
For example, given a datamodel.graphql:
type User {
  id: ID! @id # ID field
  createdAt: DateTime! @createdAt # DateTime created at
  updatedAt: DateTime! @updatedAt # DateTime updated at
  email: String! @unique # Required unique scalar
  age: Int! # Required non-unique scalar
  type: UserType! # Singular enum
  tagline: Tagline @relation(link: INLINE) # Singular inline relation, this is not possible in DM 1.0
  work: Work @relation(link: TABLE) # Singular relation table relation, TODO: Relation table with custom name
  thoughts: [Thought!] # To many relation with implicit back relation
  home: Home @relation(link: INLINE) # Optional 1-m relation with explicit many back relation
  isActive: Boolean! @default(value: false) # Default
  temperature: Float # Float field
  meta: Json # Json field
  identificationDocument: IdentificationDocument!
    @relation(name: "UserIdentificationDocument", link: INLINE) # Required 1-1 relation
  taxDocument: TaxDocument @relation(name: "UserTaxDocument", link: INLINE) # Optional 1-1 relation
  bestFriend: User @relation(name: "UserBestFriend") # Optional self 1-1 relation
  godFather: User! @relation(name: "UserGodFather") # Required self 1-1 relation
  friends: [User!] @relation(name: "UserFriends", onDelete: CASCADE) # Self 1-m relation, cascade
  nickName: String @db(name: "friendlyName")
}

The introspected result is:
model User {
  age                              Int
  bestFriend                       String?
  createdAt                        DateTime                @default(now())
  email                            String                  @unique
  friendlyName                     String?
  godFather                        String?
  home                             Int?
  id                               String                  @id
  identificationDocument           String?
  isActive                         Boolean                 @default(false)
  meta                             Json?
  tagline                          String?
  taxDocument                      String?
  temperature                      Float?
  type                             UserType
  updatedAt                        DateTime                @updatedAt
  User_UserToUser_godFather        User?                   @relation("UserToUser_godFather", fields: [godFather], references: [id])
  Home                             Home?                   @relation(fields: [home], references: [id])
  IdentificationDocument           IdentificationDocument? @relation(fields: [identificationDocument], references: [id])
  Tagline                          Tagline?                @relation(fields: [tagline], references: [id])
  TaxDocument                      TaxDocument?            @relation(fields: [taxDocument], references: [id])
  User_UserToUser_bestFriend       User?                   @relation("UserToUser_bestFriend", fields: [bestFriend], references: [id])
  other_User_UserToUser_bestFriend User?                   @relation("UserToUser_bestFriend")
  other_User_UserToUser_godFather  User                    @relation("UserToUser_godFather")
  Thought                          Thought[]               @relation(references: [id])
  User_A                           User[]                  @relation("UserFriends", references: [id])
  User_B                           User[]                  @relation("UserFriends", references: [id])
  Work                             Work[]                  @relation(references: [id])

  @@index([bestFriend], name: "bestFriend")
  @@index([godFather], name: "godFather")
  @@index([home], name: "home")
  @@index([identificationDocument], name: "identificationDocument")
  @@index([tagline], name: "tagline")
  @@index([taxDocument], name: "taxDocument")
}

On top of the all the additional fields, the order has been shifted which makes it extra jarring.
Possible Solution
@mavilein mentioned that the columns were returned in a different order from time to time as the reason for sorting alphanumerically.
I'm not sure which databases were affected, but for Postgres, I've solved this in a past project by doing the following:
SELECT
	a.attnum as field_ordinal,
	a.attname as name,
	format_type(a.atttypid, a.atttypmod) as data_type,
	a.attnotnull as not_null,
	d.description as comment,
	pg_get_expr(ad.adbin, ad.adrelid) as default_value,
	COALESCE(ct.contype = 'p', false) as is_primary_key
FROM pg_attribute a
JOIN ONLY pg_class c ON c.oid = a.attrelid
JOIN ONLY pg_namespace n ON n.oid = c.relnamespace
LEFT JOIN pg_constraint ct ON ct.conrelid = c.oid AND a.attnum = ANY(ct.conkey) AND ct.contype IN('p', 'u')
LEFT JOIN pg_attrdef ad ON ad.adrelid = c.oid AND ad.adnum = a.attnum
LEFT JOIN pg_description d ON d.objoid = a.attrelid AND d.objsubid = a.attnum
WHERE a.attisdropped = false AND n.nspname = $1 AND c.relname = $2 AND a.attnum > 0
ORDER BY a.attnum

The ORDER BY a.attnum is the important bit.

Tracking via https://github.com/prisma/prisma/issues/2434


Auto setup

Coverage increased (+0.8%) to 97.6% when pulling ac42d6cb6ec448cd322343e93f07053504e0fd6d on feature/auto_setup into a811ef9a0e351b0bb48800f6a82129ce7017733e on feature/appcnfig.


Usability of optimize.shgo

I've been trying to familiarise myself with the operation of optimize.shgo, and have run into several usability issues which limit the ability of a general user to apply it to their problems. A lot of these could be improved by a documentation route.

[ ] it's not clear how n and iters need to be adjusted to solve a particular problem, or how they should be varied if the dimensionality changes.

[ ] it's not clear how many function evaluations, nfev, that the user will be exposed to when they change the different solver options. How does nfev scale with iters, n and sampling_method? By experimenting it looks like there are a total of n * iters function evaluations (plus any local minimizer evaluations) if the sampling method is sobol (this isn't documented), i.e. nfev - nlfev = n * iters.
When the sampling method is changed to simplicial the total number of function evaluations appears to be much larger, and have no clear dependence on n or iters.

[ ] When sampling_method = 'sobol', and iters = 1 it still looks like there are two iterations done. This might be a bug:

nfev: 1067   # output when iters=1, n=100, sampling_method='sobol'
nit: 2
nlfev: 867

[ ] Setting maxev does not have any bearing on the total number of function evaluations actually used. For one example I tried to set options={'maxfev': 100, 'maxev': 100}, but there were 750 function evaluations used overall. How does one limit the number of nfev?
[ ] When is the callback actually called? I counted the number of times the callback function was called, and it's not equal to iters. My expectation is that it would be called iter times.
[ ] The callback function is not called with the best value of x found so far, it varies quite a bit.  From my point of view this renders the callback of little use; is there a good reason for this?
[ ] When a callback is provided a message Callback for minimizer starting at *x* is printed. There's no way of removing that message, I tried setting options['disp']=False, but to little effect.
[ ] It's not clear from the OptimizeResult why/how the sampling terminates. There is a minhgrd and f_tol, but the reason for termination is not generally given.
[ ] If f_tol an absolute tolerance or a relative tolerance? Should the minimiser have both?
[ ] The default value for f_tol is not explained.
[ ] How many local minimisations are done at each iteration of the sampling? When are the local minimizations done? From the docstring minimize_every_iter defaults to False, and the default value of local_iter is not mentioned in the docstring. I would naively expect a total of 1 local minimization if iters=5 and the default options apply (minimize_every_iter should be False)

@Stefan-Endres

The points about sobol are solved in #13469 which is ready to merge on my side (there is indeed a bug). This PR is currently blocking @Stefan-Endres as he wanted to ship enhancement after this PR.

A lot of these could be improved by a documentation route.

I definitely agree. I am working on the documentation before pulling the code into scipy. Currently what is eating most of time is that I wrote a new caching for the sampling step which fixed all of the bugs mentioned here and I'm trying to clean and document the code before opening a PR to scipy. In addition I need to update the parallelisation to be consistent with the other routines in scipy and avoid any extra dependency and the finally the issues mentioned in #13469.

When the sampling method is changed to simplicial the total number of function evaluations appears to be much larger, and have no clear dependence on n or iters.

This is a bug that was fixed in the upstream repository.

When sampling_method = 'sobol', and iters = 1 it still looks like there are two iterations done. This might be a bug:

There is a known bug where optimize.shgo always does one extra iteration. This has been fixed in the upstream repository.

Setting maxev does not have any bearing on the total number of function evaluations actually used.

maxev is the maximum number of evaluations, including constraint evaluations at a sampling point that is infeasible (in this case the objective function is not evaluated).
maxfev is the maximum number of function evaluations when the contraints at the are feasible.

Perhaps a small tutorial problem would be worth writing to demonstrate the difference.

When is the callback actually called? I counted the number of times the callback function was called, and it's not equal to iters. My expectation is that it would be called iter times.
The callback function is not called with the best value of x found so far, it varies quite a bit. From my point of view this renders the callback of little use; is there a good reason for this?

It is called in the local minimization routine. The current callback is used only in the scipy.optimize.minimize step. It might be more appropriate to have a separate callback function for the global and local routine to return the current best global?

When a callback is provided a message Callback for minimizer starting at x is printed. There's no way of removing that message, I tried setting options['disp']=False, but to little effect.

I see, thank you, this is a bug that still needs to be fixed.

It's not clear from the OptimizeResult why/how the sampling terminates. There is a minhgrd and f_tol, but the reason for termination is not generally given.

If f_tol an absolute tolerance or a relative tolerance? Should the minimiser have both?

Relative tolerance, I will update this. I don't know about having both, I would assume that only relative tolerance is needed unless there are applications where absolute tolerance is required (currently if the solution vector is at 0.0 then absolute tolerance is used, everywhere else relative tolerance is used).

How many local minimisations are done at each iteration of the sampling?
From the docstring minimize_every_iter defaults to False, and the default value of local_iter is not mentioned in the docstring. I would naively expect a total of 1 local minimization if iters=5 and the default options apply (minimize_every_iter should be False)

This depends on how many proven basins of attraction was found in a given sampling step or over several iterations without minimization.

When are the local minimizations done?

For each attractive basin a local minimization should only be done once. There is a bug in the current scipy version where the same basin of attraction could be run in the following iterations. This bug has been fixed with the new caching (this was the main reason for writing the new file which is unfortunately very large right now).
In general, there are a large number of options and the docstring is already quite large. But a lot of the confusion pointed out here is due to bugs. I think mainly the usability of shgo could be improved with more tutorial examples in addition to fixing the problems pointed out in this issue.

Often people often like to know how far through the minimisation procedure they are, perhaps using a progress bar like tqdm.
If you know the total length of computation (e.g. with differential_evolution there may be a maxiter), then you can express this as a percentage, and update a progress bar as the iterations finish and the callback is called.
If you don't know the total length of computation you can e.g. update a progress bar with minimum cost function found so far. If you get the best x so far in the callback this is relatively easy. If you're not, then you have to cache the best cost function (a few more lines of code) for comparison. Either way, you need to know what x value is being given to the callback.

Often people often like to know how far through the minimisation procedure they are, perhaps using a progress bar like tqdm.
If you know the total length of computation (e.g. with differential_evolution there may be a maxiter), then you can express this as a percentage, and update a progress bar as the iterations finish and the callback is called.

This is actually interesting and could be shown in the doc. We could even think about having an optional dependency to tqdm for that. Would be cool and be like PyMC3.

I am currently attempting to solve an optimization problem using shgo. During the process, I found that the parameter n can control the number of sampling points generated. However, only a portion of the sampling points undergo local optimization in the final output. After inspecting the source code, I discovered that the issue occurs at line 1133 in ‘scipy\optimize_shgo.py’. The code checks whether each sampling point is the lowest among its neighboring points. In my view, this behavior is intended to optimize only those points that could potentially be local minima, thereby reducing calculation time. However, for my optimization problem, this operation may not be quite suitable. Whether it would be possible to add a parameter option to shgo to control this filtering behavior?


Unofficial Q&A Discord Server

Forgive me for the inproper use of issues for this repo, this is soley to inform users and contributers of this repo to where they are able to get more active support
No Support From This Repo ???
Join The Unofficial Discord Server
A discord server has been set up specifically for help with this library and other instagram api related bits. Please join the link below to actually get your questions and issues answered.
https://discord.gg/6RtGQ5J8Wz

Cheers @Nerixyz 😘


Merge strategies: How to squash'n'merge by default but also allow rebase

Thx for offering this service and github app!
Although I scanned the Readme multiple times it is not clear to me how to support the following use case:
We switched off merging PRs but we let developer pick to squash'n'merge or rebase. The common default is squash'n'merge, but adding the autorebase label always rebases.
How to let the app know that for this specific PR I want it to be squash'n'merged?
Could that be done with another label autosquash?
Or can something be configured or are there more comment options?
I hope I was able to phrase my question n an understandable manner.
Best Christian

Thanks for reporting this but I don't maintain this project anymore.


Fix for single-word field names in quotation

This fixes a runtime issue with reports where BC is expecting request page field names like ChosenOutputMethod to be without quotation marks.

Very straight forward - thanks so much ;-)


Feedback from Mandy

Hi @hanwenzhang0317,
The feedback to your research proposal comes to be the below 3 parts.
First part - strongest point
This research proposal proposes applying one advanced methodology, that is, Bayesian Structural Vector Autoregression (SVAR) model, to study and investigate how the fiscal policy impact and how the tax shocks affect the Australian economy and financial market. It fills in the gaps that less studies are conducted on the Australian economy and therefore gives an opportunity to understand it econometrically. In addition, it draws attention to a very specific topic on how stock prices react on the tax shocks, which contributes to clearing some ambiguousness on the existing literatures. Overall, this research proposal introduces the cutting-edge macroeconometric method, SVAR , to study and shed light on the macroeconomy in Australia.
Second part - points could be better
Under motivation,

Several topics, such as, effects on fiscal policy, tax cuts on economy and stocks, dynamic economics, and stimulus policy-making process, are brought up initially; whereas the quotations are mainly focused on tax shocks on output and fiscal policy shocks on output and stock price. This might make the readers, like me, a bit unclear what the research questions are.

[Suggestions]: 1) make it explicitly in the first paragraph e.g., how many questions are going to be answer, what the questions are; 2) restate the relevant research questions after the quotation paragraph so it’s clear how research questions are related to the quotations.

More explanations may need to add in quotations to make more sense, for example,

“using sign restrictions”: I’m not too sure what it means.

“exogeneous tax changes could end with large difference”: large difference on what?

“However, Charziantoniou et al. (2013) argued there was no monetary policy indicators in Afonso and Sousa (2011)”: I’m not too sure what the monetary policy indicators are and why without them is a problem in the report of Afonso and Sousa.

[Suggestion]: putting a bit more elaboration on the quotations and how each of them relates would be better.
Under data & preliminary, all data are wrangled and presented well. Small suggestions are:

Put preliminary and data together, that’s they are all before methodology and model, the idea is that the data are cleaned and the data properties are well studied and ready to implement into the model.

Given all table title “Table x: xxx” are on the middle top of each table, it would be more consistent if we can put the figure title “Figure x: xxx” on the middle top of each graph.

Third part - index.qmd file
Please kindly refer to the qmd file directly.
Best,
Xiaoman Guo

Hi @mandyxmg,
Thanks for your time reading and giving feedback on my proposal.
In the next draft, I would definitely consider  elaborating more on the research questions and introduce the topic into more details!
Bests,
Hanwen


Update azure-storage-account-limits-standard.md

Added limit on allowed number of directories and subdirectories for an ADLS Gen2 account as this is a question from customers and it's not documented already in our scalability limits documents
Reference of modificaiton:
Maximum number of blob containers, blobs, directories and subdirectories(If Hierarchical Namespace is enabled), file shares, tables, queues, entities, or messages per storage account. | No limit |

@tamram
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@tamram
Can you review this old PR and determine whether it needs to be closed or merged?

I sent an email to the content owner 10/26.

Thanks, @khdownie! I committed your suggestion. When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

#sign-off

Merging now.


release: v0.1.0

:tractor: New release prepared
0.1.0 (2024-03-13)
Features

Initial version (bceb097)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/flovogt/test-lib-rp-sp/releases/tag/sam-lib-v0.1.0 :sunflower:


Polish windows installer metadata

Application name is just shown as spring while it should be Spring Cli. Logo is plain java dude while we could just take spring-shell logo.

Used this command in linux to create ico file:
convert -background transparent -define 'icon:auto-resize=16,24,32,64,128' spring-cli.svg spring-cli.ico


Cloudwatch image in_tail_container_logs is duplicated Error (v1.13)

Hello,
I was running the latest version of the images available and noticed that the containers failed to start.
The id "in_tail_container_logs" is duplicated in conf/kubernetes.conf and conf/kubernetes/containers.conf
I can fix this. I think the original config from conf/kubernetes.conf should be removed ?
Or we could get rid of the @id field from the config present at conf/kubernetes.conf

Fixed by #585


Go Green!

Let's go the open source way for a greener earth. Go green!!

@parikchit10 when do you want the merging of this PR? Before 1 October or later?


Run on pull_request_target to pick up environment variables and secrets on forks

Checklist

[x] You followed contributing section
[x] You kept your Pull Request small and focused on a single feature or bug fix.
[x] You added unit testing when necessary
[x] You added functional testing when necessary

The checks aren't running because this branch does not have a trigger (this branch says to look at main) and main does not have a trigger (main says to look at the incoming branch). Once this is merged, the next PR should trigger the same checks since then main will get triggered on a PR.

@mikealfare good catch here, we faced this issue back then on PR coming from a fork, should resolve the issue on #746


Introduce named constants for highlighting tag names.

Refers to #2563 .
This is just a refactor of all the tag strings to named constants as suggested by @matklad.
An enum could probably prevent some future inconsistencies (since strings are still accepted), but I think the constants here are just fine - since the frontend only cares about strings anyways.
The frontend doesn't know about about those constants, so we'll still need to be mindful for them there.
Note: I didn't touch the STYLE const (big css blob), we could probably make it a format! string using something like once_cell::Lazy, let me know if this is something that needs fixing (since it doesn't seem like a useful API outside of tests).
Also - I left those consts private, I assume if they were some kind of API we would have made it into an enum?

I assume if they were some kind of API we would have made it into an enum?

I don't think an enum makes sense (as it's open-ended), but something like struct Tag(&'static str) might!
bors r+


Can the program train its own models

Can the program train its own models? I found that I couldn't finish it.

Hi @dreamitpossible1!
The repository provides model definitions and basic training script so you can train mobilenetv3. What exact problem did you have?
Cheers,
Martin


Offline PWA version?

This would be amazing to play on a long flight!
Would it be possible to add a minimal PWA manifest and service worker so that it can be reliably used offline?

I was thinking the exact same thing except building it locally and running from index.html, but I would have to roll back to a version of node with known security vulnerabilities... The error I get is:
Error: error:0308010C:digital envelope routines::unsupported


README unclear where to clone example project to

It’s unclear in the documentation that django_deployment_example_project.git needs to be cloned into a separate directory from the definitive_guide_to_django_deployment.

It shouldn't actually matter where you clone the project. You actually don't need to clone it at all if you use the rogueleaderr github username and the default project name.


⚠ Jenkins Plugins Artifactory has degraded performance

In 6018a01, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1073 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 9885898 after 53 minutes.


[e2e]: container tag main gcp-workload-identity slsa3

Repo: https://github.com/slsa-framework/example-package/tree/v32.0.588
Run: https://github.com/slsa-framework/example-package/actions/runs/10626082150
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.container.tag.main.gcp-workload-identity.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.container.tag.main.gcp-workload-identity.slsa3.yml
Trigger: push
Branch: v32.0.588
Date: Fri Aug 30 03:04:58 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v32.0.589
Run: https://github.com/slsa-framework/example-package/actions/runs/10641887911
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.container.tag.main.gcp-workload-identity.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.container.tag.main.gcp-workload-identity.slsa3.yml
Trigger: push
Branch: v32.0.589
Date: Sat Aug 31 03:06:27 UTC 2024
Tests are passing now. Closing this issue.


Fix code tab link when viewing tags

"Code" tab button in the repo view assumes that the current BranchName is always a branch. This fix replaces the hardcoded "branch/{{.BranchName}}" path with the proper "{{.BranchNameSubURL}}".

Codecov Report

Merging #3908 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3908   +/-   ##
=======================================
  Coverage   20.16%   20.16%
=======================================
  Files         145      145
  Lines       29171    29171
=======================================
  Hits         5881     5881
  Misses      22395    22395
  Partials      895      895

Continue to review full report at Codecov.

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


[1.10.2] [Bug/Enhancement] Owl Death Noise

Hello,
It appears in the latest release of Ender Zoo on CurseForge, the mod does not have a sound file for when the owl dies. It just plays the normal sound or no sound at all.

Looks like it has only three sounds registered, two ambient and one hurt sound
https://github.com/SleepyTrousers/EnderZoo/blob/b58afe17d75cbc656090e5ce2f8fd7780f0e5be6/src/main/java/crazypants/enderzoo/entity/EntityOwl.java#L50
but the death sound should bejust the hurt sound https://github.com/SleepyTrousers/EnderZoo/blob/b58afe17d75cbc656090e5ce2f8fd7780f0e5be6/src/main/java/crazypants/enderzoo/entity/EntityOwl.java#L366


Feature requests: Statistics summary and next planned backup

Hello,
thanks for a great add-on.
It will be helpfull to see more statistics about backups (as was in Google backup Addon).
For example - summary page:
Local backups (7,8 GBs )
Onedrive backups (3,5 GBs)
Last Backup Date:
Next Backup Data:
Thanks

Yes seems reasonable. Last Backup Date already exists in the overview now :)

Available now in 2.3


Implement strings in adapter modules

This commit is a hefty addition to Wasmtime's support for the component
model. This implements the final remaining type (in the current type
hierarchy) unimplemented in adapter module trampolines: strings. Strings
are the most complicated type to implement in adapter trampolines
because they are highly structured chunks of data in memory (according
to specific encodings). Additionally each lift/lower operation can
choose its own encoding for strings meaning that Wasmtime, the host, may
have to convert between any pairwise ordering of string encodings.
The CanonicalABI.md in the component-model repo in general specifies
all the fiddly bits of string encoding so there's not a ton of wiggle
room for Wasmtime to get creative. This PR largely "just" implements
that. The high-level architecture of this implementation is:

Fused adapters are first identified to determine src/dst string
encodings. This statically fixes what transcoding operation is being
performed.

The generated adapter will be responsible for managing calls to
realloc and performing bounds checks. The adapter itself does not
perform memory copies or validation of string contents, however.
Instead each transcoding operation is modeled as an imported function
into the adapter module.  This means that the adapter module
dynamically, during compile time, determines what string transcoders
are needed. Note that an imported transcoder is not only parameterized
over the transcoding operation but additionally which memory is the
source and which is the destination.

The imported core wasm functions are modeled as a new
CoreDef::Transcoder structure. These transcoders end up being small
Cranelift-compiled trampolines. The Cranelift-compiled trampoline will
load the actual base pointer of memory and add it to the relative
pointers passed as function arguments. This trampoline then calls a
transcoder "libcall" which enters Rust-defined functions for actual
transcoding operations.

Each possible transcoding operation is implemented in Rust with a
unique name and a unique signature depending on the needs of the
transcoder. I've tried to document inline what each transcoder does.

This means that the Module::translate_string in adapter modules is by
far the largest translation method. The main reason for this is due to
the management around calling the imported transcoder functions in the
face of validating string pointer/lengths and performing the dance of
realloc-vs-transcode at the right time. I've tried to ensure that each
individual case in transcoding is documented well enough to understand
what's going on as well.
Additionally in this PR is a full implementation in the host for the
latin1+utf16 encoding which means that both lifting and lowering host
strings now works with this encoding.
Currently the implementation of each transcoder function is likely far
from optimal. Where possible I've leaned on the standard library itself
and for latin1-related things I'm leaning on the encoding_rs crate. I
initially tried to implement everything with encoding_rs but was
unable to uniformly do so easily. For now I settled on trying to get a
known-correct (even in the face of endianness) implementation for all of
these transcoders. If an when performance becomes an issue it should be
possible to implement more optimized versions of each of these
transcoding operations.
Testing this commit has been somewhat difficult and my general plan,
like with the (list T) type, is to rely heavily on fuzzing to cover
the various cases here. In this PR though I've added a simple test that
pushes some statically known strings through all the pairs of encodings
between source and destination. I've attempted to pick "interesting"
strings that one way or another stress the various paths in each
transcoding operation to ideally get full branch coverage there.
Additionally a suite of "negative" tests have also been added to ensure
that validity of encoding is actually checked.

Closes #4309

I also realize that this is an extremely large PR unfortunately. I've tried to be thorough with tests but I have almost certainly forgot something here and there. My next plan is to enhance the existing component model fuzzer to have an adapter module generated as well which should exercise more successful cases, but I don't know how to more systematically test the "negative" cases.


npm error - Raspberry pi

When I want to install npm using the command
sudo apt-get install npm
Show me this error and doesn't install npm.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
npm : Depends: nodejs but it is not going to be installed
Depends: node-abbrev (>= 1.0.4) but it is not going to be installed
Depends: node-ansi (>= 0.3.0-2) but it is not going to be installed
Depends: node-ansi-color-table but it is not going to be installed
Depends: node-archy but it is not going to be installed
Depends: node-block-stream but it is not going to be installed
Depends: node-fstream (>= 0.1.22) but it is not going to be installed
Depends: node-fstream-ignore but it is not going to be installed
Depends: node-github-url-from-git but it is not going to be installed
Depends: node-glob (>= 3.1.21) but it is not going to be installed
Depends: node-graceful-fs (>= 2.0.0) but it is not going to be installed
Depends: node-inherits but it is not going to be installed
Depends: node-ini (>= 1.1.0) but it is not going to be installed
Depends: node-lockfile but it is not going to be installed
Depends: node-lru-cache (>= 2.3.0) but it is not going to be installed
Depends: node-minimatch (>= 0.2.11) but it is not going to be installed
Depends: node-mkdirp (>= 0.3.3) but it is not going to be installed
Depends: node-gyp (>= 0.10.9) but it is not going to be installed
Depends: node-nopt (>= 3.0.1) but it is not going to be installed
Depends: node-npmlog but it is not going to be installed
Depends: node-once but it is not going to be installed
Depends: node-osenv but it is not going to be installed
Depends: node-read but it is not going to be installed
Depends: node-read-package-json (>= 1.1.0) but it is not going to be installed
Depends: node-request (>= 2.25.0) but it is not going to be installed
Depends: node-retry but it is not going to be installed
Depends: node-rimraf (>= 2.2.2) but it is not going to be installed
Depends: node-semver (>= 2.1.0) but it is not going to be installed
Depends: node-sha but it is not going to be installed
Depends: node-slide but it is not going to be installed
Depends: node-tar (>= 0.1.18) but it is not going to be installed
Depends: node-underscore but it is not going to be installed
Depends: node-which but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

This is not a node-red issue, so please use the mailing list, slack team or you could ask a question on Stack Overflow and tag it node-red. That way the whole Node-RED user community can help, rather than rely on the core development team.
In this instance, also please read the RaspberryPi docs:https://nodered.org/docs/hardware/raspberrypi
If you've used our update script you should already have npm installed. If you haven't used our update script you'll need to provide more information about your setup.
Thanks!


Added leading zeros to RU numbers in rack elevations

Closes #5274
What's Changed

- Rack elevations will now display 01,02,03.. instead of 1,2,3.. for RU numbers.
- UI/UX change only.

Screenshots

After
Before

TODO

[x] Explanation of Change(s)
[x] Added change log fragment(s) (for more information see the documentation)
[x] Attached Screenshots, Payload Example
[x] Unit, Integration Tests
[x] Documentation Updates (when adding/changing features)
[x] Example App Updates (when adding/changing features)
[x] Outline Remaining Work, Constraints from Design

For what it's worth, I have a rack here in my office that does not have leading zeros, so this change would actually make Nautobot less representative of my rack labeling. I'm wondering if this should be configurable?

For what it's worth, I have a rack here in my office that does not have leading zeros, so this change would actually make Nautobot less representative of my rack labeling. I'm wondering if this should be configurable?

@abates I thought I had seen it both ways as well.  There is a boolean field for descending units on a per rack basis, so maybe this should be a boolean as well. 🤔

Agreed, this needs to be configurable. IMHO making it a global configuration setting may be sufficient and simpler than adding it as a per-rack toggle?

@glennmatthews I think that would suffice unless a user has both rack types in their environment.  They might want to distinguish between them like they can do with the descending units attribute?

my 2 cents :)
I don't disagree that they could have both, but imho there will not be confusion if your work order said "RU 1" and it read "RU 01" as an example. Given the effort, a global setting seems to be more that enough options.

I would agree given the effort.  Are we thinking something like the following?
unit_display = f"{unit:02d}" if settings.UI_RACK_UNIT_TWO_DIGIT_FORMAT else str(unit)
drawing.add(drawing.text(unit_display, position_coordinates, class_="unit"))

Yes, though I'd suggest something along the lines of RACK_ELEVATION_UNITS_TWO_DIGIT_FORMAT just to more closely match the existing RACK_ELEVATION_DEFAULT_UNIT_HEIGHT and RACK_ELEVATION_DEFAULT_UNIT_WIDTH setting.

@glennmatthews Following the same way those settings are implemented, it's now a configuration parameter in constance or a settings override.


Editing recipe Help

Hello everyone ,
I'm trying to remove some alloy smelter but it doesn't works and i don't understand why could you help me please ?
http://pastebin.com/iABaw1pD
Forgot to say i'm using EnderIO-1.10.2-3.1.164

Are you sure you're looking at the right recipe ingame? There are multiple variants for the glasses...

Edited and relaunch with all recipe removed and it still works. I don't understand what i'm doing wrong
http://pastebin.com/dretyC5g
Screen of alloy smelting:
http://imgur.com/a/dvqXn

What does the logfile say?

log file here
http://pastebin.com/nK5nBzsq

[17:25:55] [Client thread/DEBUG] [EnderIO/EnderIO]: Removed recipe Enlightened Fused Quartz from Block 4 due to user config.

Looks good to me.
You might want to avoid having multiple blocks with the same ID in the file. The last one wins.

I don't understand , how to do xD
I have to disable all recipe for this item so i have to tell him wich recipe disable  not wich item .
Could you give me an example to illustrate what you wanna mean ?
PS: Enlightened Fused Quartz from Block 4 still craftable ...

<AlloySmelterRecipes>

  <recipeGroup name="EnderIO">
    <recipe name="Enlightened Fused Quartz"/>
    <recipe name="Enlightened Fused Quartz 2"/>
    <recipe name="Enlightened Fused Glass"/>
    <recipe name="Enlightened Fused Glass 2"/>
    <recipe name="Enlightened Fused Quartz from Block"/>
    <recipe name="Enlightened Fused Quartz from Block 2"/>
    <recipe name="Enlightened Fused Quartz from Block 3"/>
    <recipe name="Enlightened Fused Quartz from Block 4"/>
  </recipeGroup>

</AlloySmelterRecipes>

Awesome it works thanks for help ,p


ios version and bitcode

Hi
When building for iOS, the minimum version is 8.2, is this on purpose? Would like to see a 7.0 as minimum (same as React)
Also, bitcode is not enabled in the RCTGoogleAnalyticsBridge.xcodeproj, would love to see it being compiled with bitcode enabled.

Hi!
The iOS version has been mentioned in another issue (#3). No reason other than not noticing the warning myself. I'll consider making 7.0 the default target.
Bitcode enabled is a good suggestion, but I am unsure of the potential side effects. I will have to look into it.

Didn't see that closed issue. And thanks for looking into bitcode.

Cool! If you have any experience with migrating from non-bitcode to bitcode I'd love to hear it.
It seems like it shouldn't be an issue, but at the same time some people are mentioning esoteric problems enabling bitcode. I wouldn't want to break the library for people currently implementing it. It would have to be a breaking changes release in that case.

Tagging @9mm to say I am going to look into making 7.0 the default target soon :)

:) :+1:


Fix async export serialization

@akatsoulas r?

Tests need some fine tuning.

r+wc 🍺

Coverage increased (+0.004%) to 93.047% when pulling<PHONE_NUMBER>a4cabe484aabe26e6d8ae146cc42f6 on johngian:fix-async-export-serialization into a445d6c8ff3684ee46bc3ebe530704467afb335e on mozilla:master.

Coverage increased (+0.006%) to 93.049% when pulling 034bea20aa34b36b68d07ae2de7a40e9b49c8d44 on johngian:fix-async-export-serialization into a445d6c8ff3684ee46bc3ebe530704467afb335e on mozilla:master.


Design labels error messages

New UI with cards design
Fixes #5 (improve labels) also with better rounding of numbers
Fixes #4 (error messages)
Cards with best/worst configurations for time and cost and best balanced configuration

Deployed to -> master.d19f2a8daatc3f.amplifyapp.com


Introduce a TimestampedPath class to simplify user data loading

We used to have quite some duplicate code for checking the timestamps of the user data files. TimestampedPath is introduced to remove the duplication.
Also all std::filesystem uses are now the noexcept version that takes an extra error code as the out parameter. We don't need to be surprised by exceptions.

LGTM. Thaks!


Possibility to customize Clock

Describe the problem you'd like to have solved
Customize Clock for Testing
Describe the ideal solution
When building the Verifier, add the possibility of customizing the Clock as it's already present in build(Clock clock) method.
Ideally it would be necessary to implement something like JvmClock as it's used in other libraries.
e.g.:
  @RequiredArgsConstructor(staticName = "of")
  public static class JvmClock implements com.auth0.jwt.interfaces.Clock {
    private final Clock clock;

    @Override
    public Date getToday() {
      return Date.from(Instant.now(clock));
    }
  }

Alternatives and current work-arounds
Current workaround:
    if (builder instanceof JWTVerifier.BaseVerification) {
      return ((JWTVerifier.BaseVerification) builder).build(JvmClock.of(clock));
    }

Additional information, if any
N/A

@driverpt that's the API we've decided for that. The clock is a value that we really don't want to expose as it could completely change the result of time-related claims verification. But we have documented that if you need to change it for unit tests purposes, you can do it casting the builder instance. See https://github.com/auth0/java-jwt#time-validation.

Closing due to inactivity.


Add a tiny feature: when adding a blog note, grep for TODO and add them to ~/TODO.md ?

[x] Or to ~/motd which on my laptop gets displayed on new bash terminals.

[x] It can be very easily done, I'll just have to think about the best use for it.

[ ] I could also play with Google Notes cli or API and add these .*TODO.* lines to a special list of TODO on Google Notes?

I could also play with Google Notes cli or API and add these .TODO. lines to a special list of TODO on Google Notes?
I don't even want to try, I know I could do it, but it's not so useful


Recommendation Engine for Travel Buddy

ongoing work on the recommendation system.

I and varsha started working on recommendation engine.

Both of us are still working on the recommendation engine. (Update as per yesterday's scrum).

Recommendation engine is all set and yet to be integrated with the UI.

Working on "Ensuring  the recommendation engine that  provides recommendations in a timely manner".

Completed the task. Marking the status as closed.


Fixes OLED wake from motion detect

There was an intermittent problem when the OLED off/on is called from the timer thread where the OLED on would not always work causing the screens to stay off.
This PR changes that behaviour by just setting a flag in the timer thread, and the detect_motion call is now done from the main thread which perform the OLED changes if there was motion or not.
Prior to this fix I could easily get the OLED wake to fail within a couple of tries, but after this I have performed the sleep/wake well over 10 times without a problem.

lovely, i could not provoke a fault once in about 10 attempts. prior i would hit it ~3 attempts in.

I've cherry-picked the cleanup code from your repository @bkleiner and retested again 10 times without issue.


Add an Emacs command to toggles Emacs Anywhere on/off

The command istoggle-ea. When the toggle is off, Emacs Anywhere will do nothing when the frame is deleted.


fix: matomo events

:tada: This PR is included in version 0.22.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


fix:  fix the wrong show of kubernetes

Fix #748

Description

When we can connect to Kubernetes cluster, we will show Kubernetes section.

Screenshot

@simoneggler  HI, Can you try this PR ?

Yes. When they cant connect the cluster，they     don’t want the section to
be shown
Maxim Baz<EMAIL_ADDRESS>周六23:22写道：

@maximbaz commented on this pull request.
In sections/kubecontext.zsh
https://github.com/denysdovhan/spaceship-prompt/pull/759#discussion_r355127207
:

@@ -29,6 +29,10 @@ spaceship_kubecontext() {

spaceship::exists kubectl || return

if kubectl can't connect kubernetes cluster, kubecontext section will be not shown

local kubectl_version=$(kubectl version --short 2>/dev/null | grep "Server Version" | awk '{ match($0, /^Server Version: (.+)$/, version); print version[1] }')
[[ -z $kubectl_version ]] && return

I've seen the issue but I don't understand root cause, all those guys have
kubernetes cluster configured but they currently have no internet and
therefore cannot connect to it, and they ask why kubernetes segment is
still visible?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/denysdovhan/spaceship-prompt/pull/759?email_source=notifications&email_token=AAIHF65R3NLIFZ7HU2VG3U3QXO5TVA5CNFSM4JWQPNNKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCOKXFQY#discussion_r355127207,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIHF66MRASSSUQGGD65G53QXO5TVANCNFSM4JWQPNNA
.

I rather understood that those people don't want to use kubecontext section entirely, maybe this section should not be shown by default simply? I don't think it's correct to slow down kubecontext section for those who use it, for the sake of people who just want this section to be disabled :)

@maximbaz  So, will we change the default show to false?

I know @salmanulfarzy would be interested to chip in (also related to #341), but if we have this section that confuses many people, personally I'd rather disable it by default, yes.

Refactoring finished. Review again, please @maximbaz

Finished.

Disable kubectl by default
Keep comments. https://github.com/denysdovhan/spaceship-prompt/pull/759/files#diff-3d0e72496aee0181266b4d16a394f5bfR13-R14

@denysdovhan  @salmanulfarzy  Hi buddies, review this PR please.


suggest new_adding

It is recommended to add calling AI detection algorithms such as the yolov5 algorithms demo.

您的邮件已收到！


JSON Should minimize formatting

The JSON dumped by foundation includes indents and newlines. We should remove this, and have the consumer of the json decide how to display json on their own.

What is the advantage of not spitting it out human-readable (other than x%
file size)?
On Wed, Feb 17, 2021 at 10:54 AM Aaron Vontell<EMAIL_ADDRESS>wrote:

The JSON dumped by foundation includes indents and newlines. We should
remove this, and have the consumer of the json decide how to display json
on their own.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/instabase/foundation/issues/31, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOORA24HMQBREUSF7EOSLI3S7PRBXANCNFSM4XYTAVEA
.

Solely file size


Update README: Cloudflare has deprecated Auto Minify

Not a minify-html bug

[X] I am not reporting an issue with minification.

Python Version
No response
Django Version
No response
Package Version
No response
Description
Cloudflare has deprecated Auto Minify and should no longer be referenced in the README.

Sure, I guess. I won't get round to this for a while though.


Does distiller need the PyTorch CNN to be defined in some fixed ways?

Hello.
First of all, thank you for this awesome library.
I have one question.
This question might sound simple and "noob". However, I really need to ask this still I am still quite a beginner in this domain (especially in trying to shrink the CNN size) and need some guidance.
I will build a custom CNN architecture with PyTorch. Because I have only worked with Keras in the past, I am still vague with the PyTorch framework in defining a CNN model. That being said, I am learning PyTorch and am trying to build my own custom CNN right now.
The thing is, I need to make sure that my custom CNN can be shrunk/compress with the distiller library. Is it safe for me to assume that distiller can work with any arbitrary CNN model defined in PyTorch? Or does distiller needs the CNN model to be defined in some fixed way?
Actually, I already checked and executed the compress_classifier.py file but I still can't really tell on how the distiller actually interacts with the CNN model and this leads me on asking this question.
Thank you.

Hi @hilman-dayo,
That mostly depends on how you want to compress your model.
If you want to prune weights, as long as the weights are seen by model.parameters() - you're good to go. In PyTorch, the model weights (and in general any trainable tensors) are best defined as nn.Parameter objects, which is a subclass of torch.Tensor which knows that inside a module - it usually serves as a weight tensor. More info in pytorch nn.Parameter docs.
If you want to quantize the model, you should add every operation in the .forward function as a layer in the model, and then call this layer!
E.g. if the regular forward is done with residuals like
def forward(self, x):
    x_res = x
    x = self.conv1(x)
    x = self.bn1(x)
    x = x + x_res
    return x

Instead - in the module constructor you should add a layer for element wise addition, so this element wise addition may be quantized by our quantizers, like this
def __init__(self, ...):
    ... # previous/regular init
    self.eltwiseadd_residual = distiller.modules.EltwiseAdd()

def forward(self, x):
    x_res = x
    x = self.conv1(x)
    x = self.bn1(x)
    x = self.eltwiseadd_residual(x, x_res)
    return x

This way, you can assure the quantizer will find all of the modules inside the model graph and be able to quantize properly every operation :)
Let us know if you have more questions.
Lev

Thank you for the answer.
It really helped.
One other question.
As I said previously, I want to build my own custom Object Detection framework and make it smaller with distiller.
In the future, I want to convert it into an ONNX model.
Will the fact that my custom Object Detection framework being pruned etc. with distiller make it is impossible for it to be exported to ONNX model?
Is there anything that I need to keep in mind whenever I am designing and pruning my model so that it is possible to be converted to ONNX model in the future?

Hi @hilman-dayo
No, you don't have to worry about exporting to onnx compressed models.
You can export pruned models already right now - since the weights are the only thing that are changed in the model, and not the structure itself. Not quite sure about thinned models, I assume it would work as well.
Quantized models are a bit harder - we simulate the quantization, and when exporting to onnx you would actually see the simulation instead of actual quantization ops. We are thinking of implementing a way to export a quantized model, but we're still not quite there in terms of work schedule.
In short - no, you don't have to worry about export to onnx, eventually we'll support everything.
Thanks,
Lev

Thank you for the answer. I may close this thread right now.


Request to Host Package - hashroute

This issue was originally filed by<EMAIL_ADDRESS>
I don't know if the instructions Seth sent me prior to pub launch are something I can share yet or not, so I am submitting the request for this package myself, even though I do not control the repo. Andreas Krennmair does.
The library is hashroute and the repo is here:
https://github.com/akrennmair/hashroute.dart
I've successfully tested it and it works great. I put it into the pub format, added the pubspec, and sent a pull request, which Andreas accepted, so the code in the repo is good to go.

This issue has been moved to dart-lang/pub#240.


Broken Image in the IO Module Docs

Need to fix the broken image in [1].
Now, docs are displayed through the \Central. In the ballerina-distribution repo, the BALAs are used to generate API docs and they are sent to the Central. Currently, resources like images are not being packed into the BALA.
[1] https://docs.central.ballerina.io/ballerina/io/0.6.0-alpha5

Even in the Ballerina central, this architecture diagram is not visible.
https://swanlake.central.ballerina.io/ballerina/io
@shehan360 please note.


[P0] Rename train/evaluate methods so train/eval can set model state

Description
Currently IntervenableModel.train() and IntervenableModel.evaluate() are helper methods for training and evaluating interventions in a simple interface. I am renaming these to train_alignment() and eval_alignment() so that train() and eval() can set the model state (so that HF trainer can be compatible with this interface).
I think we have not actually been using these in pyvene-based projects because they don't allow much customisation so this doesn't break much; just had to change one notebook.
Testing Done
Tested in current project and worked. Let's see if tests pass!
Checklist:

[x] My PR title strictly follows the format: [Your Priority] Your Title
[x] I have attached the testing log above
[x] I provide enough comments to my code
[x] I have changed documentations
[x] I have added tests for my changes

For #121.


FF 343

Coverage remained the same at 49.857% when pulling 8e62a57bdf1f4c013d03a5dcd465ece1d73333f5 on FF-343 into 859c3c19bff55e6f2f68d1edde8a65e84656ae14 on master.

Coverage increased (+0.008%) to 49.865% when pulling a10a6565f121bc59d76f103fdb2e5d3475bcf41d on FF-343 into 859c3c19bff55e6f2f68d1edde8a65e84656ae14 on master.


Add configurable settings that allow CSRF fields to be renamed

Allow for user defined overrides for:

form field csrf-token
query parameter csrf-token
header X-CSRF-Token

I've decided against implementing this.


Quick start problem

Hi, I tried the following quick start tutorial in the README.md. After creating the app.json and _init_.py with its content, I don't know where to go from there.

Now, enter the About app and long press the "Start State Shell" button to launch the Debug App Bind feature. Open your app's folder, then press the green dot button to select it and associate the app with the system.

I don't know how to go to the 'Start State Shell' and even install 'pyos' properly on my system. Mine is not raspberry. I'm running Ubuntu 16.04. (32 bit)
I tried running pyos.py in the root of directory, and run fine, but it's just print on the window screen, and nothing else. This is what I see -

How to actually use this program? Going to wiki only shows you the API documentation.
Thanks for your advance.

You are doing everything properly, the bug was caused by PyOS thinking it was running on a Pi. I pushed a new version that should fix this bug.

Alright. Let me test the new version and will report if anything else happened.

Erm. Hey, is there a way to enable cursor just for debugging/dev/testing? I'm not on touchscreen pc, so it's a bit problem to see where I click, although stuff is functioning. Now, I'm gonna try to click the 'Start Shell'

I can open the following state shell smoothly, however a bit hard for a non touchscreen pc.
The problem is I don't really know where my cursor pointing at, and I fail at clicking the 'dot green button' because I just don't see my cursor.

I'm sorry for the problems. I did not try the code on a Linux PC other than the Pi, so I did not realize this would happen. The reason your previous issue and this one occurred is because PyOS thinks it is running on the Pi. When I get to my computer I will change the code to enable the cursor on Linux.

The previous issue is fixed. Well done. just this new issue (I think just for me at least, because my PC is old and non touchscreen), make things a little steep, but maybe blind clicking will make things smooth. I currently stuck at dot green button clicking part (can't see :stuck_out_tongue_closed_eyes: ), but others are fine and functional, well I did not hit the part after clicking the green button yet.
Thanks. I think I'll close this issue for now, and maybe you'll re-open this whenever cursor is added?

The newest version should add the cursor on Linux.

Hi, the new push is a great feature for me! Now can I navigate easily. Now I encounter a new problem -
After creating the helloworld stuff based on tutorial, and navigated to helloworld dir and clicked green dot button, it spits out this error -

This is error_text in my temp/ -
last_error.txt

:smile:
Things working, and the program (helloworld) appeared in the HOME screen! Nice!
here's my screen shot -

:+1:
Now I can officially close this issue. Thanks for helping out.

You are very welcome. Thank you for helping me iron out problems in the tutorial.

You are welcome, too!


Invoke-RestMethod cmdlet error if the response is neither JSON nor XML

This change fixes the Invoke-RestMethod cmdlet behavior if the response is neither XML nor JSON, e.g. just a plain text from a webservice.
Before the change:
PS> Invoke-RestMethod http://httpbin.org/encoding/utf8
Invoke-RestMethod : Unexpected character encountered while parsing value: <. Path '', line 0, position 0.
At line:1 char:1
+ Invoke-RestMethod http://httpbin.org/encoding/utf8
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  + CategoryInfo : NotSpecified: (:) [Invoke-RestMethod], JsonReaderException
  + FullyQualifiedErrorId : Newtonsoft.Json.JsonReaderException,Microsoft.PowerShell.Commands.InvokeRestMethodComman
  d

After the change:
PS> Invoke-RestMethod http://httpbin.org/encoding/utf8

Unicode Demo

...

todo: I am going to refactor ConvertFromJsonCommand a little bit in order to remove the duplication and eliminate some ifdef sections

Hi @2xmax, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

Hi @2xmax, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

Eliminated the duplication caused by platform-specific libs exceptions. Also, locally I've written some C# unit tests for the JsonObject class https://gist.github.com/2xmax/ced86b7f7d9bbcdf0d004fa507b9a314, but found only a few C# unit tests in the project for some reason. If it makes sense, I can push the C# unit tests as well.

@daxian-dbw , @iSazonov, it is ready for your review. Would you mind looking this over?

@daxian-dbw I see in JsonObject.cs multiple double castings. Can we ask @2xmax to fix this or better make new PR?
Also in JsonObject.cs  a null checks is absent
for theValue in line 142:
JValue theValue = entry.Value as JValue;
result.Properties.Add(new PSNoteProperty(entry.Key, theValue.Value));

in line 184
result.Add(((JValue)element).Value);

@2xmax Before contribution you must sign CLA (a contribution license agreement) https://cla.microsoft.com

Thanks @2xmax for the contribution and @iSazonov for the code review!
I was distracted by other things. I will go through the changes this morning 😄

@2xmax we don't support NUnit, but the support to xUnit is on the way, see #2574.
The JsonObject unit tests you wrote are great. Since we don't have good support to xUnit yet, is it possible that you can convert them into Pester tests?

I see in JsonObject.cs multiple double castings. Can we ask @2xmax to fix this or better make new PR?

@iSazonov I think general code refactoring can go to a separate PR. Yes, those double casting should be avoid, but like @2xmax mentioned it will increase nesting, which is also annoying. Declaration Expressions would really help in such cases, if it can make into C# 7.0.

Also in JsonObject.cs a null checks is absent. full comment

Good catch. I'm not sure if it's really a potential bug, or it's OK because the value can only be one of JArray, JObject and JValue. @2xmax can you comment? If it's a potential bug, then we can open an issue to track it.

have ported the unit tests to Pester, signed the CLA

Good catch. I'm not sure if it's really a potential bug, or it's OK because the value can only be one of JArray, JObject and JValue. @2xmax can you comment? If it's a potential bug, then we can open an issue to track it.

According to this doc, there be no other value except JArray, JObject and JValue but maybe it is still worth to look into the Json.NET unit test suite in details; I haven't found any contradiction, yet I feel like maybe we could beware of a breaking change by writing some tests here.

For these untyped properties, the Json.NET serializer will read the JSON into LINQ to JSON objects and set them to the property. JObject will be created for JSON objects; JArray will be created for JSON arrays, and JValue will be created for primitive JSON values

According to this doc, there be no other value except JArray, JObject, and JValue

Yes, my question just is can we hope that this will be not changed in the future? May be protect it and forget? :-) Or at least add a relevant comment.

Yes, my question just is can we hope that this will be not changed in the future (newtonsoft is not under our control)? May be protect it and forget? :-) Or at least add a relevant comment.

I already responded you in the same sentence you quoted "...we could beware of a breaking change (e.g. caused by the nuget package update) by writing some tests here," perhaps it was too long and convoluted.  To put it simply, we can write some tests (a safety net) to prevent this.
Yet I still consider this discussion is out of the scope of this PR and it is better to converse about this in a separate issue or a Slack channel.

@2xmax Thanks for your contribution.
There is some problem with CLA. Maybe you used different email addresses here and when signing CLA.
@daxian-dbw Thanks for your great comments!

Thank you both for the comments too!
tried to sign one more time with no luck. Seems I'm not the only person who is having problems with the cla bot https://github.com/Microsoft/HoloToolkit-Unity/issues/370

@2xmax I changed the label to cla-signed based on your comment. Thanks again for your contribution!


ZEPPELIN-345 Duplicate "Ctri + n" in the keyboard list

I deleted just several lines of code in modal-shortcut.html .

looks good! thanks for fixing this

LGTM

Thanks for the contribution!
LGTM


Fix create not running on Windows

There are several reports of create not working on Windows for v2. This PR fixes it.
Fix #159
How to test (must run on Windows)
npx extension@latest my-new-extension --template=new-react

I suspect there's incompatible Windows code within go-git-it, as I encountered a similar error when running npx go-git-it https://github.com/extension-js/extension.js/tree/main/examples/new-react .

No success yet.
pnpm dlx extension@latest create . --template=react-typescript
🐣 - Starting a new browser extension named browser-extension-template...
🤝 - Ensuring browser-extension-template folder exists...
🤞 - Checking if destination path is writeable...
🔎 - Scanning for potential conflicting files...
🧰 - Installing browser-extension-template from template react-typescript...
Removing existing .go-git-it-temp-folder...
[======                                            ] 11% 16.7sError pulling git repository: Error: Command failed: mv examples/react-typescript /Users/henry/code/react-typescript
mv: rename examples/react-typescript to /Users/henry/code/react-typescript: No such file or directory

    at genericNodeError (node:internal/errors:984:15)
    at wrappedFn (node:internal/errors:538:14)
    at ChildProcess.exithandler (node:child_process:422:12)
    at ChildProcess.emit (node:events:519:28)
    at maybeClose (node:internal/child_process:1105:16)
    at Socket.<anonymous> (node:internal/child_process:457:11)
    at Socket.emit (node:events:519:28)
    at Pipe.<anonymous> (node:net:339:12) {
  code: 1,
  killed: false,
  signal: null,
  cmd: 'mv examples/react-typescript /Users/henry/code/react-typescript',
  stdout: '',
  stderr: 'mv: rename examples/react-typescript to /Users/henry/code/react-typescript: No such file or directory\n'
}

@OSpoon @zh30 please review it again extension@latest my-new-extension --template=new-react.
v2.0.0-alpha.7 "works on my machine"

I'll merge this one as completed, please re-open if I'm mistaken. Windows is tough love

v2.0.0-alpha.8 works~ Thanks a lot.


Skip Xcode automation handling with Xcode 16 and new deployment process

Type of Request
infra task
Infrastructure Environment
Recipes
What is happening?
Assuming we fix https://github.com/flutter/flutter/issues/133465 with a solution like https://github.com/flutter/flutter/pull/150113, we can stop handling Xcode automation in CI: https://flutter.googlesource.com/recipes/+/refs/heads/flutter-3.22-candidate.0/recipe_modules/os_utils/api.py#408
Steps to reproduce
No response
Expected results
No response

So excited to see this happening! :)


Connection handle close

Pull Request Test Coverage Report for Build 495939579

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

Totals

Change from base Build 493688986:
0.0%

Covered Lines:
1153

Relevant Lines:
4089

💛  - Coveralls

Pull Request Test Coverage Report for Build 495939579

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

Totals

Change from base Build 493688986:
0.0%

Covered Lines:
1153

Relevant Lines:
4089

💛  - Coveralls


blame parent links should link to specific line

Fixes #208
This PR traverses over the DOM in the git blame table in the UI in order to find all lines affected by a change and adds them as hash URLs. Old #L123 will be removed

@sindresorhus is there anything that needs to be done for this?

@sindresorhus ok, I've resolved the conflicts introduced in #251 and fixed everything up into a single commit.

Nice work @Ma27 :)

It looks like after this PR, the blame parent links are no longer blame parent links but just "blame at this revision" links.  Specifically, the old link was constructed with
`$1${commitSha}${encodeURI('^')}`

but the encodeURI('^') was lost in this commit. Was that intentional?

@glasser Probably not. Open a new issue ;)


router & interface service build completed

Coverage decreased (-11.5%) to 21.612% when pulling d70f07eb15614589318a1c6f2cb919a618cb32bd on dashng:master into e70a00809ebd7d4475bc32a5d0d944c9b0a5eb41 on ciscochina:master.


Update README.md with Arch Linux supported

Simple add of Arch Linux to requirements/platforms; order platforms alphabetic.

We have a conflict now since I updated this first.  I'm going to close this one out now.


QA kcrypt on kairos 1.5 and 1.6

There was a report (on Slack) that kcrypt doesn't work.
Original report:
I’m currently having issues with Encryption on both v1.5 and v1.6. We have tried v1.5 with Ubuntu and v1.6 with Open-suse and the same issue occurs. I will add the Cloud-Config to the thread.
#cloud-config

# Additional system users
users:
- name: "kairos"
  passwd: "kairos"
  lock_passwd: true
  groups: "admin"

# Enable K3s on the node.
k3s:
  enabled: true

# The install block is to drive automatic installations without user interaction.
install:
  # Device for automated installs
  # device: "/dev/nvme0n1"
  # Reboot after installation
  reboot: false
  # Power off after installation
  poweroff: true
  # Set to true when installing without Pairing
  auto: true
  # Label of partitions to encrypt
  # COS_PERSISTENT is the OS partition
  # dedicated to user-persistent data
  encrypted_partitions:
  - COS_PERSISTENT
  grub_options:
    extra_cmdline: "rd.neednet=1"

# Kcrypt configuration block
kcrypt:
  challenger:
    challenger_server: "http://<IP_ADDRESS>:30000/"
    nv_index: ""
    c_index: ""
    tpm_device: ""

stages:
  initramfs:
    - users:
        kairos:
          groups:
            - sudo
          passwd: kairos

We are using kairos-challenger v0.2.3 and CRDs v0.0.13
Kcrypt logs show invalid Hash which doesnt make much sense, since the Hash is the exact same as the one configured
The TPM hash was obtained by running this
kairos@localhost:~> ID=$(sudo /system/discovery/kcrypt-discovery-challenger)
kairos@localhost:~> echo $ID

the SealedVolume:
apiVersion: keyserver.kairos.io/v1alpha1
kind: SealedVolume
metadata:
    name: encryption
    namespace: kairos
spec:
  TPMHash: "redacted"
  partitions:
    - label: COS_PERSISTENT
  quarantined: false

let's try to reproduce on 1.5 and 1.6 . There is a chance that the kcrypt binaries being used are old ones because we failed to tag the packages.

The challenger version used (0.2.3) has the sealed volume fix described in the commit message here: https://github.com/kairos-io/kcrypt/commit/018322ff009f36829083a1a8e8adc7e2b2219ecb
The kcrypt side of that fix was introduced in kcrypt tag 0.5.0 which is available since kairos v1.5.0 afaict.
So this should not be the reason for this issue here.

We can conclude that 1.5 and 1.6 had bugs around it? can we pinpoint to specific chart version that works? I guess this won't be relevant anymore with the 2.0 release, but we should be clear and close the card with what's the best course of action

Let's close this and track any other issue after 2.0 is released

@mudler @jimmykarily can we re-open this ticket? Still having issues encrypting the COS_PERSISTENT partition with kairos v2.0.3, using this ISO: kairos-ubuntu-20-lts-v2.0.3-k3sv1.24.13+k3s1.iso
We are seeing an error during install saying that the COS_PERSISTENT partition does not exist? No encryption takes place and after the machine powers off, it boots just fine without any encryption.

The cloud-init YAML is below:
#cloud-config

# Additional system users
users:
- name: "kairos"
  passwd: "kairos"
  lock_passwd: true

# Enable K3s on the node.
k3s:
  enabled: true

# The install block is to drive automatic installations without user interaction.
install:
  # Device for automated installs
  device: "/dev/nvme0n1"
  # Reboot after installation
  reboot: false
  # Power off after installation
  poweroff: true
  # Label of partitions to encrypt
  # COS_PERSISTENT is the OS partition
  # dedicated to user-persistent data
  encrypted_partitions:
  - COS_PERSISTENT
  grub_options:
    extra_cmdline: "rd.neednet=1"

# Kcrypt configuration block
kcrypt:
  challenger:
    challenger_server: "http://<IP_ADDRESS>:30000/"
    nv_index: ""
    c_index: ""
    tpm_device: ""

stages:
  initramfs:
    - users:
        kairos:
          groups:
            - sudo
          passwd: kairos

There's connectivity between the node and challenger server:
root@localhost:/# curl -v http://<IP_ADDRESS>:30000/
*   Trying <IP_ADDRESS>:30000...
* TCP_NODELAY set
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 30000 (#0)
> GET / HTTP/1.1
> Host: <IP_ADDRESS>:30000
> User-Agent: curl/7.68.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 404 Not Found
< Content-Type: text/plain; charset=utf-8
< X-Content-Type-Options: nosniff
< Date: Fri, 05 May 2023 10:20:18 GMT
< Content-Length: 19
<
404 page not found
* Connection #0 to host <IP_ADDRESS> left intact

2.0.3 migth have an issue identifying the proper partition due to a library update.
See, on https://github.com/jaypipes/ghw which we use to get info about partitions, there was a switch between partition.Label and partition.FilesystemLabel -> https://github.com/jaypipes/ghw/pull/316
The label entry in the Partition struct should correspond to the
partition label, but we were getting the FS label instead.

This patch fixes that by getting the actual partition label for the
label value and adding an extra field on the Partition struct to add the
fs label, so they are separated and clear on which is which.

So clearly the kcrypt binary is using partition.Label which used to return the proper partition COS_PERSISTENT but now reports a different one persistent
kcrypt was updated to ghw 0.10.0 during a normal bump of deps and that issue went undetected. The patch is present on v0.5.2.
So in this line: https://github.com/kairos-io/kcrypt/blob/v0.5.2/main.go#LL166C11-L166C11 we are checking persistent against COS_PERSISTENT so it will never find the persistent partition and will never encrypt.
@JPedro2 As a workaround, you migth be able to set the persistent value in your config and see if that matches correctly and encrypts the persistent partition:
install:
  encrypted_partitions:
  - persistent

Good news is that this should be fixed on kcrypt 0.6.0-rc2 and everything up to date with the new label/filesystemlabel :D

@JPedro2 In any case, we DONT recommend you encrypt your partitions now, unless its for testing only.
Once 2.1.0 is released with this fixed, your partitions will have a passphrase that was generated with a wrong label and that wont work once we fix the label issue. So on upgrade, unlocking your partitions will fail and you would need to reinstall the whole thing.

@JPedro2 Seeing that this is a big issue as basically encryption is broken AND anything installed on 2.0.X would need an upgrade path to the fixed packages, I would say that the release will be closer than expected, even maybe with a backport and a minor patch release to 2.0.4 to fix this.
I will bring this on the meeting on monday to discuss with the team and update you when we know. Unfortunately kcrypt 0.6.0 brings too many changes to make it a patch release so probably a backport to fix that will be in the works and that should release pretty soon-ish :D

@Itxaka thank you! Appreciate it, please let me know and we can go from there :)
I will keep you posted on the workaround - most probably on Monday too

@Itxaka We've applied the workaround as recommended and tried the install again and we are now seeing another error:

This is weird because when running the command below on the node, we get the TPM hash without any issues:
ID=$(sudo /system/discovery/kcrypt-discovery-challenger)

Any recommendations?

@Itxaka another question, since kcrypt is reporting the persistent label instead of COS_PERSISTENT, I'm assuming that the SealedVolume on the KMS needs to change to the below?
apiVersion: keyserver.kairos.io/v1alpha1
kind: SealedVolume
metadata:
    name: test2
    namespace: default
spec:
  TPMHash: <redacted>
  partitions:
    - label: persistent
  quarantined: false
EOF

This is weird because when running the command below on the node, we get the TPM hash without any issues:
ID=$(sudo /system/discovery/kcrypt-discovery-challenger)

Any recommendations?

Getting the TPM hash doesn't involve talking to the challenger server in any way. I would start with a curl -v on the challenger server address to see where this 301 is redirecting. My guess is that it redirects from http to https but maybe there is something else. Then try to change the challenger server address to the final one to avoid the redirection.
The bad handshake error sound like a TLS certificate error. curl -v may show you more information.

I think this has been now confirmed by @JPedro2 and our end2end tests to work as expected, closing!


Add auto-reconnect option

Hi,
Please find my first pull request to this project. It aims to enable the option to automatically try to reconnect to the LDAP server if the connection is closed. As I already mentionned in an issue, I am quite new to Elixir, so feel free to adapt this PR to what suits best.
In particular, if the new configuration retry_on_connection_closed is set to true, then each call to GenServer.call is observed by do_call_or_retry/2. If it returns a {:error, :ldap_closed} or a {:error, {:gen_tcp_error, term}} , then it calls Paddle.reconnect and resends the request.
I have not been able to find an equivent of :gen_tcp_error for the :ssl-module, but I think, based on eldap.erl's do_send/3, that both (maybe erroneously) return :gen_tcp_error.
I sadly wasn't able to reproduce the configuration for the tests, but I don't expect any to fail. But that would be something to check for in the QA.
It is tricky to write tests for this PR, and I wasn't really able to do so. My approach to ensure a correct behaviour:

for :ldap_closed errors, that is, when :eldap is able to close the connection properly, I just killed the socket using ss. It would be quite easy to implement, but I wasn't comfortable with adding this as a dependency, as it would be quite hard to setup for the users anyway.
for :gen_tcp_error, it's quite tricky, and I just played with my LDAP server a little bit. What should really be done in order to properly insure that it behaves as expected would be using a tool that allows for connections drop, as for instance toxiproxy does. But that's a lot of work, that I'm not willing to put in right now, and again, there is the extra dependency issue.

With my best regards !

Actually, I should probably update the specs of each function that calls do_call_and_retry too. I'll fix that in the next few days.


Add tooltip support

Can use https://github.com/ReactTooltip/react-tooltip or a similar project.

This should be addressed on a per-need basis, no need to have it pre-packaged by default.


Potential PPA Optimization: I$ can have 32b banks

Area
I$
Current behavior
I$ has 64b banks, which are read and then muxed down to 32b.
Desired behavior
deeper, thinner rams are generally more area-efficient. They can always be folded if this is untrue for a particular node
Analysis
SRAM generation tables should be analysed for the design space
Verification
Standard regression should be fine. Large programs that fill the I$ will verify.

Presumably this is driven by the desire to write 64b at a time to match
d-cache?
On Sun, Dec 11, 2022 at 3:16 PM Dan Petrisko @.***>
wrote:

Area
I$
Current behavior
I$ has 64b banks, which are read and then muxed down to 32b.
Desired behavior
deeper, thinner rams are generally more area-efficient. They can always be
folded if this is untrue for a particular node
Analysis
SRAM generation tables should be analysed for the design space
Verification
Standard regression should be fine. Large programs that fill the I$ will
verify.
—
Reply to this email directly, view it on GitHub
https://github.com/black-parrot/black-parrot/issues/1147, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEFG5AADJ7GCEOWMN5GK5KTWMZOD7ANCNFSM6AAAAAAS3I3JVI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

64b was driven by the D$, but just by shared code history and reusing hardened rams.
We support multi-bank fill e.g. 128b fill on 2x64b banks, so for I$ this would just turn to e.g. 4x32b banks per fill. Writes shouldn't see a difference in energy. Reads however should see energy/timing improvements


"touchenter" listener is probably a no-op

This code listens for touchenter events, but AFAIK no browser implements such events.  I'm just curious if this is needed, or could be removed from the code.  I've noticed this listener on a bunch of sites when debugging chromium performance issues.

Thanks for pointing this out. Looks like it should be removed, I wasn't aware that it's a NOOP.