Unable to use docker secrets to push image to dockerhub

Expected Behavior
When using docker secrets to build and push image, I should be able to reference the secret, build and push my build image by following https://github.com/tektoncd/pipeline/blob/master/docs/auth.md.
Actual Behavior
Unable to push image.
Steps to Reproduce the Problem

Create a clusterTask:

apiVersion: tekton.dev/v1alpha1
    kind: ClusterTask
    metadata:
      name: buildkit
    spec:
      inputs:
        resources:
        - name: source
          type: git
        params:
        - name: image
          description: Where to publish the resulting image
        - name: dockerfile
          description: The name of the Dockerfile
        - name: docker-context
          description: The context of the build
        - name: push
          description: Whether push or not
          default: "true"
        - name: workingdir
          description: The directory containing the app
          default: "/workspace"
        - name: buildkit-client-image
          description: The name of the BuildKit client (buildctl) image
          default: "moby/buildkit:master"
        - name: buildkit-server-address
          description: The address of the BuildKit daemon (buildkitd) service
        - name: insecure-registry
          description: Whether to use insecure registry
      outputs:
        resources:
        - name: output-image
          type: image
      volumes:
      - name: buildkit-cache
        hostPath:
          path: /var/lib/buildkit/runc-overlayfs/content
          type: DirectoryOrCreate
      steps:
      - name: build-and-push
        image: $${inputs.params.buildkit-client-image}
        command: ["buildctl-daemonless.sh"]
        workingDir: /workspace/source
        securityContext:
          privileged: true
        volumeMounts:
        - mountPath: /var/lib/buildkit/runc-overlayfs/content
          name: buildkit-cache
        args: ["build",
                  "--progress=plain",
                  "--frontend=dockerfile.v0",
                  "--frontend-opt", "filename=$${inputs.params.dockerfile}",
                  "--local", "context=$${inputs.params.docker-context}", "--local", "dockerfile=.",
                  "--output", "type=image,name=$${inputs.params.image},push=true,registry.insecure=$${inputs.params.insecure-registry}"]

Create a secret, service account, using service in taskRun

apiVersion: tekton.dev/v1alpha1
kind: TaskRun
metadata:
  labels:
    service-name: optimistic-wright2
    service-namespace: default
    tekton.dev/task: buildkit
  name: optimistic-wright2-7b5a5-e6af3
  namespace: default
spec:
  inputs:
    params:
    - name: image
      value: index.docker.io/strongmonkey1992/default-optimistic-wright2:2cc4018aa26188f2f29c3adb32154d3fcdd3be5e
    - name: buildkit-server-address
      value: tcp://buildkit.rio-system:9001
    - name: insecure-registry
      value: "false"
    - name: dockerfile
      value: Dockerfile
    - name: docker-context
      value: .
    resources:
    - name: source
      resourceRef: {}
      resourceSpec:
        params:
        - name: url
          value: https://github.com/StrongMonkey/priv-repo
        - name: revision
          value: 2cc4018aa26188f2f29c3adb32154d3fcdd3be5e
        type: git
  outputs:
    resources:
    - name: output-image
      resourceRef: {}
      resourceSpec:
        params:
        - name: url
          value: index.docker.io/strongmonkey1992/default-optimistic-wright2:2cc4018aa26188f2f29c3adb32154d3fcdd3be5e
        type: image
  serviceAccount: optimistic-wright2-7b5a5-2cc4018aa26188f2f29c3adb32154d3f-4e8ca
  taskRef:
    kind: ClusterTask
    name: buildkit

Image was built successfully within buildkit, but failed to push with the following error:

error: failed to solve: rpc error: code = Unknown desc = server message: insufficient_scope: authorization failed

Additional Info
Found that in cred-init, there is no user-agent header when mounting docker secrets into file. I noticed this difference https://github.com/tektoncd/pipeline/blob/master/pkg/credentials/dockercreds/creds.go#L90 when comparing with my own config file generated from docker login:
docker login generated:
{
    "auths": {
        "https://index.docker.io/v1/": {
            "auth": "redacted"
        }
    },
    "HttpHeaders": {
        "User-Agent": "Docker-Client/18.09.5-ce (linux)"
    }
}

cred-init generated:
{
	"auths": {
		"https://index.docker.io/v1": {
			"password": "redacted",
			"username": "redacted",
			"auth": "redacted",
			"email"<EMAIL_ADDRESS>		}
	}
}

When add HttpHeaders, buildkit was able to push the image successfully.

@StrongMonkey thanks for the issue. Can you share how the secret is defined ? (redacted of course, I am mainly interested in the annotation)

@vdemeester The secret is defined as the following
apiVersion: v1
data:
  password: redacted
  username: redacted
kind: Secret
metadata:
  annotations:
    tekton.dev/docker-0: https://index.docker.io/v1/
  creationTimestamp: "2019-06-19T23:52:39Z"
  name: dockerconfig
  namespace: default
  resourceVersion: "271289"
  selfLink: /api/v1/namespaces/default/secrets/dockerconfig
  uid: 51f3ec4f-92ed-11e9-af8e-0242ac1d0002
type: kubernetes.io/basic-auth

@StrongMonkey the docker-0 annotation should be in the form of tekton.dev/docker-0: https://index.docker.io (no need for the v1, it might even mess the thing). The only thing that matters is the auth part in the gerenated .docker/config.json file.
Note that you can also use kubernetes.io/dockerconfigjson secrets, Tekton supports thoses.
kubectl create secret generic regcred \
    --from-file=.dockerconfigjson=<path/to/.docker/config.json> \
    --type=kubernetes.io/dockerconfigjson

Thanks for the response. I have solved my issue.


Help with website

Prerequisites

[X] I have written a descriptive issue title
[X] I have searched existing issues to ensure the issue has not already been raised

Issue
Hi, @mcollina it seems like you are going to rewrite the website. If so I can help you with do that. Let me know the tech stack you'd like me to use and the setup.

Please go through https://github.com/fastify/website/issues/291 (and all the comments)

cc @lachlancollins and @Xhale1

Ideally we can first discuss the project strategy prior to starting. I think using Eleventy will make migration easier, but I would like to hear everyone's opinion first.

@mcollina  I'm waiting for the conclusion!

Hi @veritem, I believe the current plan is for either myself or @Xhale1 to create a demo of Docusaurus, before getting the thumbs up to continue with the migration. I'm going to have some time to work on it later today, but will definitely be welcoming contributions once we have a core codebase to work on :)

I've been invited to the repo too. I can give you guys a hand specially with the scripts part as I have it quite fresh from fastify/website#269


Delay Push Replication by n milliseconds or schedule

Hi @hideki
Could we implement a delay in the  PushReplication for N seconds or schedule a push replication with a backoff functionality ?
Something like:
Replication push = db.createPushReplication(url);
push.setDelay(nTime);
push.start();

nTime => Time in milliseconds or a scheduler Class ....
I would a assume that implementing that would mean pinning the future timestamp to the doc somehow so a scheduler thread in the back can query the docs which are about to get pushed to the SyncGateway.
regards,
Patrick

hi @pbertsch,
Are you looking for the method fo Replicator.getPendingDocumentIDs() which returns list of docIDs that are not pushed yet.

Hi @hideki ,
no, I thought it might be helpful to delay the initial push/pull by N seconds once a change was registered.
Something like adding time until the push actually happens. I assume it does something like that under the hud but I thought it might be interesting giving the power to the developer.

@pbertsch,
Push replicator obtains a list of documents which should be pushed by changesSince() method and Database.ChangeListener. So, you could modify following code to implement the delay feature.
https://github.com/couchbase/couchbase-lite-java-core/blob/master/src/main/java/com/couchbase/lite/replicator/PusherInternal.java#L266
https://github.com/couchbase/couchbase-lite-java-core/blob/master/src/main/java/com/couchbase/lite/replicator/PusherInternal.java#L296


Synchronize Freemarker setup to avoid concurrency issues

This should fix the the following error, sometimes seen in the build:
External error in org.kie.workbench.common.stunner.core.processors.MainProcessorjava.lang.ExceptionInInitializerError
at freemarker.template.ObjectWrapper.(ObjectWrapper.java:69)
at freemarker.core.Configurable.(Configurable.java:139)
at freemarker.template.Configuration.(Configuration.java:142)
at freemarker.template.Configuration.(Configuration.java:127)
at org.uberfire.annotations.processors.AbstractGenerator.(AbstractGenerator.java:44)
at org.kie.workbench.common.stunner.core.processors.rule.ContainmentRuleGenerator.(ContainmentRuleGenerator.java:43)
at org.kie.workbench.common.stunner.core.processors.MainProcessor.(MainProcessor.java:194)
The same change was done in UF few months back as well: https://github.com/uberfire/uberfire/blob/master/uberfire-workbench/uberfire-workbench-processors/src/main/java/org/uberfire/annotations/processors/AbstractGenerator.java

So this did not really worked as expected :( I am still seeing the same exceptions occasionally.


remove duplicated Usage header in core README.md

I'm so embarassed that i merged this with the duplicate header. Good catch!


Can not create schema and cred def with multitenancy

I am trying to create schema and cred def with multitenancy but I receive only Unauthorized.
I also tried to create default sub wallet to get the token so that I can submit schema and create cred def for the next purpose but I received the following:
    Created new profile
    Profile backend: indy
    Profile name: mysubwallet
    No public DID

Error: cannot submit schema without public did.
Any help is appreciated!

@phearaeun You have to first create a public DID for the sub wallet. The way to do that is:
POST /wallet/did/create which creates a local DID. Then you have to register this DID to the ledger. If you are using http://dev.greenlight.bcovrin.vonx.io/ then just go on 'Register from DID' and add the DID and the Verkey. Once this is done you just:
POST /wallet/did/public and add the DID as a parameter. After this you should be able to create a schema and cred def.


Bundle build failed

log :

Learnt compile failed ***

 at /Users/admin/Library/Application Support/Developer/Shared/Xcode/Plug-ins/InjectionPlugin.xcplugin/Contents/Resources/common.pm line 57.
	main::error('Learnt compile failed') called at /Users/admin/Library/Application Support/Developer/Shared/Xcode/Plug-ins/InjectionPlugin.xcplugin/Contents/Resources/injectSource.pl line 350

and xcode logs:
:0: error: cannot open file '/var/folders/gy/dms6sh0x52721rsvwn4g44qm0000gn/T/sources-e0f20c' (No such file or directory)
:0: error: this mode requires at least one input file

Could be because your project has > 128 swift source files?


Updating HoloLens RS4 article with dev tips for updating apps

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/hololens-rs4-preview.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Feature #36 new function to get bolt11 from lnurlp

Added a new function to get a bolt11 invoice from lnurlp and extracted code which now used in two different cases to separat function.

Thanks @FelixFrei! I will take a look at the PR later this week when doing the build for next release.


Xpander AppImAGE not working

Labas @OzymandiasTheGreat ,
First of all thank you for your hard work on your various projects!
I tried to use Xpander Appimage but it seems something is wrong.
Screenshot below:

For info I am using Linux Mint 19.3 X64.
Any help would be appreciated!
Ačiū

First thing, sorry, been out with particularly bad flu for over a month and I'm still not fully back.
Anyway, I'd need to see the full error. Try control-c when the error dialog is focused, should copy the full text.
This is probably a runpy bug I filed upstream, it's fixed by now, but it'll be some time before I make a new release with the fix.

Hi @OzymandiasTheGreat Hope you will feel better soon!
The system does unfortunately not let me copy and paste from that error.
Tried to look for the log file but hard to find the path.
I was using Textexpander with the company I am working with but when I decided to completely move from Mac to Linux, They said they don't have a Linux version.
I have tons of snippets there in CSV, does your app have an import possibility ? (They all have smileys btw), does your app support them?
I am ready to donate to you if it is fixed and it has the features mentioned above, as I do not plan to get back to Mac or Windows anymore, as I found all alternative stuff with Linux and at a much better speed and stability.
Let me know if you need further info..
Thx!
Riadh

Ok, you can mostly disregard my previous comment because apparently I was still feverish.
That control-c suggestion? That's a Windows thing, I got confused.
Anyway, after rereading the error message, it seems this is caused by a missing optional dependency on older versions of python. I can't be 100% sure without seeing the full error message, but we can check rather easily.
In the terminal enter this command sudo pip3 install importlib-resources and when it completes try starting xpander again. It should work now.
As for the import from textexpander functionality, I'd be very interested in adding this, but I'd need a sample textexpander csv for analysis and testing so if you can provide that I'll do it.
P.S. Re:smileys if you mean emoji, then yes, emoji is fully supported.

Thank you very much @OzymandiasTheGreat
It was indeed the missing dependency that caused the issue 👍
It starts normally now ;)
Just for information, I had my old sentences from TEXTEXPANDER and I tried to copy them to XPANDER, but only the text copies (Emojies don't unfortunately). Maybe there is a special format?
I can send you an example of TE that I use:

Hello 🙋
I'm Riadh from XXXX and it will be my pleasure to help you today!
Glad to talk to talk to you by the way 🤝

Attached is an export example from the current app that I am using on Windows.
Thank you in advance!
My-Snippets Example.zip

Hmm, what do you mean emojis don't copy? Copy/pasting and typing emojis into xpander editor works on my end. What happens when you try to paste emoji into xpander editor? Note, since you're on Linux Mint emojis will probably display as black and white on your machine. They will look just fine on other devices.
Re:textexpander csv. First column seems like the shortcut, second column is the expanded text, what's the 3rd column? Once I know how to treat this, I can implement import :)

Thx @OzymandiasTheGreat No rush!
For the Emojies,
When I type the abbreviation, the text shows normally on the field I need, however the Emojies do not show, while they show normally on the Xpander windows.
Does that make sense?
I am attaching a screen record, thx!

There's your problem. You set phrase expansion method as type. That method, while the most reliable and fastest, only supports inserting characters defined in your current keyboard layout. That means only plain text and no emoji.
Set it to paste and it should work as intended (altho there might be a slight delay in expansion).

All good now, I forgot that I've set it to type instead of paste.
Thank you very much!

So once again, I prove that developers can't estimate time.
Importing csv is done, you can download new version on releases page.
Then click new button and choose import csv, that's it.
If you wish to support my work, you can do so here: https://www.patreon.com/ozymandias
Also, if you read any tech or productivity blogs, please send them a tip about xpander. This project desperately needs more love!
If everything is working for you, please close this issue.

Thanks again Tomas!
The imported snippets do not seem to trigger strangely. But no big deal, You've already made a great job!
I would like to support with a one time donation. Send me your Revolut or Paypal please ;)
Will definitely talk about your project in the Internet, as your app can even replace the TEXT EXPANDER that is used for companies. I'm sure you can much better job than they did.
Let's stay in touch (You already have my Whatsapp).
I will close this issue, ✔


SqliteContainsOptimizedTranslator doesn't work when using wildcards

Steps to reproduce
run a query using string.Contains where the search pattern contains '%' or '_'
The issue
it seems that since SqliteContainsOptimizedTranslator doesn't use LikeExpression and instead uses "instr" wildcards are not supported (at least not in sqlite...)
This wouldn't be a problem for me right now if #2850 were resolved since then I could explicitly use the like operator (in fact I'd prefer that), but I would think that .Contains should still handle wildcards
Further technical details
EF Core version: 1.1.0
Operating system: Windows 10
Visual Studio version: VS 2015
Other details about my project setup:
Sqlite

Also of note: instr appears to be case-sensitive while like is not

We made the change to Contains becasue the scenarios where one wanted to search for strings containing a wildcard (e.g. "75%") were giving unexpected results. Current translation better resembles CLR Contains method, which was our goal. I do agree that we need the ability to use Like and other SQL functions now more than before

Using SQL functions is probably already covered by https://github.com/aspnet/EntityFramework/issues/2850

That actually makes good sense to me that it should behave more like the CLR Contains methods, so I take back my comment that it should handle wildcards :)
However, as you mention this does make the case for resolving #2850 much stronger...

in fact, why don't I just close this one...


fix grid bug

fixes #15

The plots are very similar, the tests pass, so I think it's ready for review @DanaJomar


[Migration][Analytic Privileges] Disable during migration

Background
In the old HANA, user management was part of HANA itself and analytic privileges were used to restrict access based on the current session user. In HANA Cloud, access is primarily done via a technical user which makes logic that made use of the session user useless.
Target
Calculation view processing
As an intermediate step an in order to enable initial migration effort we'll ignore the analytic privileges.
Modify the Calculation:scenario from the following
<Calculation:scenario ... applyPrivilegeType="SQL_ANALYTIC_PRIVILEGE" checkAnalyticPrivileges="true" ...>
...
</Calculation:scenario>

to
<Calculation:scenario ... applyPrivilegeType="NONE" checkAnalyticPrivileges="false" ...>
...
</Calculation:scenario>

where the modifications are as follows

If there's an applyPrivilegeType attribute set its value to NONE
If there's an checkAnalyticPrivileges attribute set its value to false

Analytic Privilege processing
As analytic privilege checks need to be define in both the .analyticprivilege file and in the .calculationview file, even if the checks from the calcview are removed, having the .analyticprivilege in the project published will cause errors because this'll be an inconsistency.
The only way we can bypass this for now is to either not move the .analyticprivilege file or not publish it in HANA Cloud.
TBD: skip analyticprivilege files or when published don't send them to HANA Cloud in the backed

fixed with https://github.com/dirigiblelabs/xsk-ide-migration/pull/21


Having trouble testing out KServe Locally

Attempting the get started but doesn't seem to work locally
https://kserve.github.io/website/master/get_started/#install-the-kserve-quickstart-environment
Raising this issue for me to work on when I get back to it.

Resolved this. Apparently if you're using Orbstack to build the kind cluster container, the Kserve would not work as intended. Its likely a configuration issue that has to be made. I recommend to use Docker itself or Docker Desktop to run the quickstart.


jsx-closing-bracket-location props-aligned/after-props documentation wrong

Not sure if this is a bug or documentation issue. Either way something needs to be switched.
Here's the rule I'm using:
"react/jsx-closing-bracket-location": [2, "after-props"]

to make this valid:
<Hello
  firstName="John"
  lastName="Smith" />;

Documentation states the opposite.
// 'jsx-closing-bracket-location': [1, 'after-props']
<Hello
  firstName="John"
  lastName="Smith"
  />;

// 'jsx-closing-bracket-location': [1, 'props-aligned']
<Hello
  firstName="John"
  lastName="Smith" />;

The docs were fixed in #1005.


Update well-architected-framework-azure-firewall.md

correcting bug per PG request

@rohilla-shweta
Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@Jak-MS Shweta doesn't own this area anymore as I own Networking now.  How can we update? :)

@Jak-MS thank you!


Add dev config for nested column support

What is the context for this pull request?

Tracking Issue:  n/a
Parent Issue: #347
Dependencies: n/a

What changes were proposed in this pull request?

Disable index creation with nested columns until it's fully supported.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Unit test

@andrei-ionescu I created a temp config for disabling nested column support (for v0.5 release).
We could remove the config when it's fully supported. Could you have a look at this?

@sezruby Please provide a clear explanation of the reason to add this flag. Is there a technical reason to add it and have this "nested column based index creation feature" disabled by default?
In the project are other features that are partially supported and I don't understand why this is different and needs to have this new flag.
By the way, adding this flag cannot stop one to set it and have the nested column based index creation enabled.
One more thing, if such a nested column based index is created, when they'll try to use it, it will not be applied. The results will be correct and impact is only that performance wise Hyperspace does not provide enough performance in this case. The user may just open some tickets in regards to it.
On the other hand, I offered my time to work on adding the full nested field support into Hyperspace for v0.5 but due to different priorities and lack of time from your team, the nested field support had to be postponed and I agreed with it, but with this PR I'm under the impression that this feature is in your way and needs to be removed (more work from my side to put it back). Maybe I'm getting it wrong and please correct me if so.
@rapoth,

Do you have some more info on this decision?
When should we resume the nested field support in Hyperspace? Do you have a time frame?

@andrei-ionescu Sorry for the lack of explanation. We need to release v0.5 this month to deliver some bug fixes.
Without the config, customers may create indexes with nested columns and ask why it's not applied.
To avoid unnecessary time consuming analysis, (it's just for quick failure), I introduced this config to deliver 0.5 without those kind of issues.
It's ok to deliver incomplete PRs without the temp config while developing, but for release, we need to disable (or exclude) incomplete features.
It's a temporal / hidden config, so I don't expect anyone will use the config.

@sezruby The feature of creating an index over a nested field is also hidden, the users may not use it at all. And this is the way Hyperspace did work before I added it.
Before adding this functionality I remember that there hasn't been any error specific to the fact that nested fields are not supported - it just did not work.
From my perspective with or without it Hyperspace works the same as before.
So, let me see if I got right what you're saying:
There is no technical issue forcing you do this.
You're afraid that on your products the customers will possibly use this feature and wonder why does not work when querying.
My questions are:

How was it in version 0.4 and why keeping the feature as it is in 0.5 is worse?
Why do you want the customers to be locked in the fact that Hyperspace does not support indexes on nested fields? Is this nested field support totally removed from Hyperspace roadmap?

@rapoth, @imback82: I may need you input here are there are some product related questions that I would like to get some answers. Thank you.

1=>
In version 0.4
scala> hs.createIndex(dff, IndexConfig("nestedIndex", Seq("nestedC"), Seq("hsh")))
// succeeded

scala> hs.createIndex(dff, IndexConfig("nestedIndex", Seq("nestedC.id"), Seq("hsh")))
com.microsoft.hyperspace.HyperspaceException: Index config is not applicable to dataframe schema.
  at com.microsoft.hyperspace.actions.CreateAction.validate(CreateAction.scala:53)
  at com.microsoft.hyperspace.actions.Action$class.run(Action.scala:88)
  at com.microsoft.hyperspace.actions.CreateAction.run(CreateAction.scala:30)
  at com.microsoft.hyperspace.index.IndexCollectionManager.create(IndexCollectionManager.scala:43)
  at com.microsoft.hyperspace.index.CachingIndexCollectionManager.create(CachingIndexCollectionManager.scala:77)
  at com.microsoft.hyperspace.Hyperspace.createIndex(Hyperspace.scala:42)
  ... 54 elided

// the index with "nestedC" can be applied
scala> val filter = dff.filter($"nestedC".isNotNull).select("hsh", "nestedC")
filter: org.apache.spark.sql.DataFrame = [hsh: string, nestedC: struct<id: string, leaf: struct<id: string, cnt: int>>]

scala> filter.queryExecution.optimizedPlan
res4: org.apache.spark.sql.catalyst.plans.logical.LogicalPlan =
Project [hsh#13, nestedC#17]
+- Filter isnotnull(nestedC#17)
   +- Relation[hsh#13,nestedC#17] Hyperspace(Type: CI, Name: nestedIndex, LogVersion: 1)

in current master:
scala> hs.createIndex(dff, IndexConfig("nestedIndex2", Seq("nestedC"), Seq("hsh")))
scala.MatchError: List() (of class scala.collection.immutable.Nil$)
  at com.microsoft.hyperspace.util.ResolverUtils$.com$microsoft$hyperspace$util$ResolverUtils$$getColumnNameFromSchema(ResolverUtils.scala:215)
  at com.microsoft.hyperspace.util.ResolverUtils$.com$microsoft$hyperspace$util$ResolverUtils$$getColumnNameFromSchema(ResolverUtils.scala:220)
  at com.microsoft.hyperspace.util.ResolverUtils$$anonfun$1$$anonfun$apply$2.apply(ResolverUtils.scala:174)
  at com.microsoft.hyperspace.util.ResolverUtils$$anonfun$1$$anonfun$apply$2.apply(ResolverUtils.scala:171)
  at scala.Option.map(Option.scala:146)
  at com.microsoft.hyperspace.util.ResolverUtils$$anonfun$1.apply(ResolverUtils.scala:171)
  at com.microsoft.hyperspace.util.ResolverUtils$$anonfun$1.apply(ResolverUtils.scala:168)
  at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)
  at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)
  at scala.collection.immutable.List.foreach(List.scala:392)
  at scala.collection.TraversableLike$class.map(TraversableLike.scala:234)
  at scala.collection.immutable.List.map(List.scala:296)
  at com.microsoft.hyperspace.util.ResolverUtils$.resolve(ResolverUtils.scala:168)
  at com.microsoft.hyperspace.actions.CreateAction.isValidIndexSchema(CreateAction.scala:77)
  at com.microsoft.hyperspace.actions.CreateAction.validate(CreateAction.scala:60)
  at com.microsoft.hyperspace.actions.Action$class.run(Action.scala:89)
  at com.microsoft.hyperspace.actions.CreateAction.run(CreateAction.scala:29)
  at com.microsoft.hyperspace.index.IndexCollectionManager.create(IndexCollectionManager.scala:47)
  at com.microsoft.hyperspace.index.CachingIndexCollectionManager.create(CachingIndexCollectionManager.scala:78)
  at com.microsoft.hyperspace.Hyperspace$$anonfun$createIndex$1.apply$mcV$sp(Hyperspace.scala:45)
  at com.microsoft.hyperspace.Hyperspace.withHyperspaceRuleDisabled(Hyperspace.scala:188)
  at com.microsoft.hyperspace.Hyperspace.createIndex(Hyperspace.scala:44)
  ... 54 elided

scala> hs.createIndex(dff, IndexConfig("nestedIndex2", Seq("nestedC.id"), Seq("hsh")))
=> succeeded

with this fix:
cala> hs.createIndex(dff, IndexConfig("nested3", Seq("nestedC"), Seq("hsh")))
scala.MatchError: List() (of class scala.collection.immutable.Nil$)
  at com.microsoft.hyperspace.util.ResolverUtils$.com$microsoft$hyperspace$util$ResolverUtils$$getColumnNameFromSchema(ResolverUtils.scala:215)
  at com.microsoft.hyperspace.util.ResolverUtils$.com$microsoft$hyperspace$util$ResolverUtils$$getColumnNameFromSchema(ResolverUtils.scala:220)
  at com.microsoft.hyperspace.util.ResolverUtils$$anonfun$1$$anonfun$apply$2.apply(ResolverUtils.scala:174)
  at com.microsoft.hyperspace.util.ResolverUtils$$anonfun$1$$anonfun$apply$2.apply(ResolverUtils.scala:171)
  at scala.Option.map(Option.scala:146)
  at com.microsoft.hyperspace.util.ResolverUtils$$anonfun$1.apply(ResolverUtils.scala:171)
  at com.microsoft.hyperspace.util.ResolverUtils$$anonfun$1.apply(ResolverUtils.scala:168)
  at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)
  at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)
  at scala.collection.immutable.List.foreach(List.scala:392)
  at scala.collection.TraversableLike$class.map(TraversableLike.scala:234)
  at scala.collection.immutable.List.map(List.scala:296)
  at com.microsoft.hyperspace.util.ResolverUtils$.resolve(ResolverUtils.scala:168)
  at com.microsoft.hyperspace.actions.CreateAction.validate(CreateAction.scala:63)
  at com.microsoft.hyperspace.actions.Action$class.run(Action.scala:89)
  at com.microsoft.hyperspace.actions.CreateAction.run(CreateAction.scala:29)
  at com.microsoft.hyperspace.index.IndexCollectionManager.create(IndexCollectionManager.scala:47)
  at com.microsoft.hyperspace.index.CachingIndexCollectionManager.create(CachingIndexCollectionManager.scala:81)
  at com.microsoft.hyperspace.Hyperspace$$anonfun$createIndex$1.apply$mcV$sp(Hyperspace.scala:45)
  at com.microsoft.hyperspace.Hyperspace.withHyperspaceRuleDisabled(Hyperspace.scala:177)
  at com.microsoft.hyperspace.Hyperspace.createIndex(Hyperspace.scala:44)
  ... 55 elided

scala> hs.createIndex(dff, IndexConfig("nested3", Seq("nestedC.id"), Seq("hsh")))
com.microsoft.hyperspace.HyperspaceException: Hyperspace does not support nested columns.
  at com.microsoft.hyperspace.actions.CreateAction.validate(CreateAction.scala:71)
  at com.microsoft.hyperspace.actions.Action$class.run(Action.scala:89)
  at com.microsoft.hyperspace.actions.CreateAction.run(CreateAction.scala:29)
  at com.microsoft.hyperspace.index.IndexCollectionManager.create(IndexCollectionManager.scala:47)
  at com.microsoft.hyperspace.index.CachingIndexCollectionManager.create(CachingIndexCollectionManager.scala:81)
  at com.microsoft.hyperspace.Hyperspace$$anonfun$createIndex$1.apply$mcV$sp(Hyperspace.scala:45)
  at com.microsoft.hyperspace.Hyperspace.withHyperspaceRuleDisabled(Hyperspace.scala:177)
  at com.microsoft.hyperspace.Hyperspace.createIndex(Hyperspace.scala:44)
  ... 54 elided

From this result, I'll

create a fix for the ResolverUtil
nested column check only for the indexed columns
change the msg to "Hyperspace does not support nested columns yet"

IMO quick failure and a temp config for incomplete / unstable features are a kind of best practice for development.
There's no reason we should keep the bad practice.
2=>
I would have liked to put this PR, because

successfully created (but useless) indexes might take much amount of data in the storage.
successfully created indexes may give the impression that Hyperspace can support it.

This PR doesn't mean that Hyperspace won't support nested field at all in the future, and there's no such decision between our team. This is a quick fix for release, just because I strongly thought that we should disable incomplete features before release to avoid any confusion.
It was my mistake that I didn't inform you first before this PR and give much information about it.
This is the first time I work with outside of company and also open source community, there's still a bit of trial and error.
3=>
Though our refactoring is almost done, still there're some remaining works. (@clee704 please correct me if I'm wrong)
As we should release the version by this month, I'm not sure we could make it. v0.6 would be safe.
4=>
There's no specific time frame but Data Skipping index + another type of index will be the included.
It would be the end of July or August, from my expectation.
@rapoth and @imback82 are OOO until next week / next month, so there will be some delay on response.

Having a feature toggle for a non-trivial under-tested new feature is a good thing. Maybe I should make one for DataSkippingIndex, too 😄
The PR message can be reworded like "Add a feature toggle for nested columns". I think we can drop "temp" in the config key, and make the feature fully pluggable at will. Or maybe "dev" instead of "temp".

@sezruby I need a clear time frame when to get back working on the nested field feature. I need to plan my time as I also have other things on my plate and I would like as much as possible to stick to that time frame.

As @clee704 noted, the same approach should be to any big feature regardless if is developed by your internal team or by someone from the open source community.

I'm not sure what do you mean by this. There is no half-implemented feature on the master branch except this. I'm going to add a feature toggle for DataSkippingIndex which is not merged yet, but you are against using a feature toggle. Can you explain why?

@clee704

There is no half-implemented feature on the master branch except this

You guys have been merging different PRs with refactor in master that address a part of a future feature. For me that is a partial implemented feature. I don't want to go into this discussion.

I'm not sure what do you mean by this.

I'm glad that you come with this idea of having a unified approach when developing big features.

but you are against using a feature toggle. Can you explain why?

It is not that I'm against a flag. It is just the fact that there is a simpler approach to disable it.
For the "nested feature" the simplest thing to do is to directly throw if a nested field is detected and disable the tests. When I'll resume developing the feature I'll remove the throw lines and enable the tests. Doing it with a flag all require do some more extra cleanup.

You guys have been merging different PRs with refactor in master that address a part of a future feature. For me that is a partial implemented feature. I don't want to go into this discussion.

Refactoring is not a feature. A feature provides new functionality to users. Refactoring does not.

Currently we're not doing it but disabling the tests can drop the code coverage and it would be an issue if we are going to add coverage check to CI. Having a non-tested, unused code sitting around in the codebase doesn't feel right.
But if you insist then I'm fine and I'll leave it up to @sezruby.

@clee704
I already said that I prefer not to get into this discussion but now that you mentioned it I'll give some feedback.
You know the phrase: "don't fix it if it works!"
In the majority of the cases refactoring happens due to new features that needs to be added. So, with this being said, any refactor is a partial feature, at least from my perspective.

I'd like to keep the dev config approach as I don't want to break the tests without knowing it.
@clee704 Could you approve the change again? it's dismissed due to the merge conflict.
@andrei-ionescu please note that @clee704 and I are NOT the kind of person who doesn't fix the code just because it's working. @imback82 has even higher standards.
BTW WHY ARE YOU ARGUING WITH US? I don't understand what you're doing here.

If you think this's the first time using disabled config in this project, I insist that I've done the rule refactoring with a temporal "disabled" package & tests for it, and enabled after it's fully delivered.
Anyway this is not a helpful discussion at all.

I forgot to add: the nested column support is only relevant to CoveringIndex. Other index types might support it without any change to the framework. For example, DataSkippingIndex can support nested columns out of the box because it doesn't directly store the column values in the index. Therefore, a more correct fix would be blocking nested columns in CoveringIndex. But this is a minor issue as currently we only have CoveringIndex now. This is just something to remember when we continue to work on the nested column support later.

@sezruby I'm not arguing with you. I just propose different solutions than what you already did choose to do and I try to compare the differences between your proposal and mine and build a case for my proposal. The fact that it is in contradiction with what you are planning is in fact part of the development itself.

@andrei-ionescu please note that @clee704 and I are NOT the kind of person who doesn't fix the code just because it's working. @imback82 has even higher standards.

I never did think of you guys having low standards. On the contrary, my impression is that you have pretty high standards. I'm used to work in all kinds of projects (start-up, research, PoCs, production level, etc) and I'm comfortable in any of them. From my experience there should be a balance in regards the standards too, as these may slow the development in the early stages.
There are things that I see that you can improve in regards to doing open development. The biggest thing that in my opinion is hindering the open development is that there is a "double standard development" -- what's on your direct interests is treated differently than other things. This is understandable up to a point but after that it drives developers off the project. You need to find the balance.
There are other things as well in regards to open development but I'll stop here. If you want to discuss about these open dev things we can have a separate context.

@sezruby I need a clear time frame when to get back working on the nested field feature. I need to plan my time as I also have other things on my plate and I would like as much as possible to stick to that time frame.

I'm getting back to my ask which didn't get an answer yet. Can you provide a time frame for me so that I can plan my time accordingly?

I'm getting back to my ask which didn't get an answer yet. Can you provide a time frame for me so that I can plan my time accordingly?

I'm not sure but you can resume after merging #461 - early or mid July.
As it also has some refactoring change and another refactoring change might be required for different index type support.


Migrate Terraform Forseti Install to Forseti-Security github org

Migrate the Terraform Forseti Install from: https://github.com/terraform-google-modules/terraform-google-forseti to new repo in Forseti-Security org.

@morgante Added this issue based on our discussions related to moving forseti terraform repo.

This issue has been resolved by moving the terraform-google-forseti repo into the Forseti Security organization: https://github.com/forseti-security/terraform-google-forseti


Update the Header Small Dark Part

As a user, I would like to have the option of a dark theme on a small screen for the header.
AC

User can switch to a dark theme and the dark header renders for small screens.

no longer needed


cross compile to 2.12.0-RC2

+modules/test and +modules/publishLocal` works fine
there are two failing test in HorizontalTests

the ci fails because you need to publishLocal derive & other libs

This should probably be updated to 2.12 proper.

@lespea 2.12.0 is not released yet. I know it's on maven central, but it was not announced.

Good point

SHouldn't be hard to get this out for 2.12.0-final, but uPickle uses a bunch of random stuff in it's test suite to make sure the derivation doesn't blow up so we'll need to wait till all that stuff is published

@lihaoyi I just disable it:
https://github.com/lihaoyi/upickle-pprint/pull/179/files#diff-fdc3abdfd754eeb24090dbd90aeec2ceR220

Only missing dependency i bumped into for 2.12-final is @non's
[ ] org.spire-math:jawn-parser_2.12:0.10.2

This makes this pass on 2.12.0
LIs-MacBook-Pro:upickle-pprint lihaoyi$ git diff
diff --git a/build.sbt b/build.sbt
index 273c6ab..1e784e4 100644
--- a/build.sbt
+++ b/build.sbt
@@ -4,7 +4,7 @@ val settings = Seq(
   version := upicklePPrint.Constants.version,

   scalaVersion := "2.11.8",
-  crossScalaVersions := Seq("2.10.6", "2.11.8", "2.12.0-RC2"),
+  crossScalaVersions := Seq("2.10.6", "2.11.8", "2.12.0"),

   scalacOptions := Seq("-unchecked",
     "-deprecation",
@@ -30,7 +30,7 @@ val settings = Seq(
   libraryDependencies ++= Seq(
     "com.lihaoyi" %% "acyclic" % "0.1.5" % "provided",
     "com.lihaoyi" %%% "utest" % "0.4.4" % "test",
-    "com.lihaoyi" %%% "sourcecode" % "0.2.0",
+    "com.lihaoyi" %%% "sourcecode" % "0.1.3",
     "org.scala-lang" % "scala-reflect" % scalaVersion.value % "provided",
     "org.scala-lang" % "scala-compiler" % scalaVersion.value % "provided"
   ) ++ (
@@ -51,7 +51,7 @@ settings

 val compatible211and212 =
   unmanagedSourceDirectories in Compile ++= {
-    if (Set("2.11", "2.12.0-RC2").contains(scalaBinaryVersion.value))
+    if (Set("2.11", "2.12").contains(scalaBinaryVersion.value))
       Seq(baseDirectory.value / ".." / "shared" / "src" / "main" / "scala-2.11_2.12")
     else
       Seq()

Just chiming in to mention that scala 2.12.0 final has been released :smile:. Keep up the good work!

@lihaoyi should be ready now. I ran the test locally, it works fine ;-). Travis is a bit stuck on memory.

Thanks for doing this!
Any idea when the first publish for 2.12.0 will go out?

@stuhood It's out already under 0.4.4


Maybe replace atomic's fetch_update with fetch_max

fetch_max is not enough as we want the max between some min value and the current value + 1:
https://github.com/vitorenesduarte/fantoch/blob/4c14e7f4ec7a6375b73422ddf54eed719535aa09/fantoch_ps/src/protocol/common/table/clocks/keys/atomic.rs#L113-L116


Player state is going to STATE_NONE and notification is disappearing while network interruption.

Notification is disappearing when there is a network interruption, how to make the notification widget stay at interruptions?
react-native-track-player: 1.1.8 v
react-native: 0.60.4
occurrence: When track is played for 10 min, notification widget disappears and players stops playing.
platform: iOS and android.

@Guichaguri Any thoughts on the first issue? The state seems super unreliable lately. We're using this in production, and we've had many reports of users complaining that the audio keeps randomly stopping, pausing, or restarting.
We think this could potentially be tied into losing and reconnecting network state.

Any updates on this?

Ok, maybe lets try to get a bit more detail into reproduction steps.
Are you guys using several instances of the player? (Like a mini player/ full player or just a player that mounts and unmounts often)
Displaying a progress bar?
Using hooks or class components?

@stokesbga Thanks for getting back to us!
We initialize the player when we initialize our app, and then we don't initialize it again. We have a mini player / full screen player, and we display a progress bar. We're trying to use the hooks useTrackPlayerEvents and useProgress. We wrapped the state functionality in our own hook where we store the state, as we found the state updates in general very unreliable.
If you'd like some more information, please don't hesitate to get in touch.
currently on version 1.2.2

Any luck with this? App stops immediately initialised in production


Make prometheus_multiproc_dir uppercase to support running under Docker

Currently it's not possible to define the prometheus_multiproc_dir when the application is running inside a Docker container because you can't define lowercase environment variables for a container.
This fix makes the environment variable uppercase while still supporting the old lowercase prometheus_multiproc_dir environment variable.

Nope. I was wrong.


SchemaShape2D does not need constructor check!

I do not think you to force that check!

Got it. Addressed! Fixed!


TEDAPI Vitals: Not Connected

Problem Description
Cannot get string data with the latest PyPowerwall setup.  Although TEDAPI is available, it is not connected.
Running python3 -m pypowerwall.tedapi seems to give all the data needed, including string data from my 2 powerwalls, but Powerwall-Dashboard does not get the data.
http://localhost:8675/tedapi/status returns 404 page not found
System Details
Describe the host system you are trying to use for the Dashboard:
Debian Linux setup running Powerwall-Dashboard through docker setup.
I have 2 Powerwall+ Units with Tesla Solar Panels
Verify Tool Output
If possible, please run the verify.sh found in the Powerwall-Dashboard main folder. It will attempt to verify all the services needed to run Powerwall-Dashboard and identify errors. Please paste the output or screenshot here:
./verify.sh

Checking pypowerwall

Config File pypowerwall.env: GOOD
Container (pypowerwall): GOOD
Service (port 8675): GOOD
Version: 0.11.1 Proxy t56
Powerwall State: CONNECTED - Firmware: 24.28.1
Site Name: Tesla Powerwall
Gateway TEDAPI: Available (<IP_ADDRESS>)
TEDAPI Vitals: Not Connected
Cloud Mode: NO

Checking telegraf

Config File telegraf.conf: GOOD
Local Config File telegraf.local: GOOD
Container (telegraf): GOOD
Version: Telegraf 1.28.2 (git: HEAD@8d9cf395)

Checking influxdb

Config File influxdb.conf: GOOD
Environment File influxdb.env: GOOD
Container (influxdb): GOOD
Service (port 8086): GOOD
Filesystem (./influxdb): GOOD
Version: InfluxDB shell version: 1.8.10

Checking grafana

Config File grafana.env: GOOD
Container (grafana): GOOD
Service (port 9000): GOOD
Filesystem (./grafana): GOOD
Version: Grafana CLI version 9.1.2

Checking weather411

Container (weather411): GOOD
Service (port 8676): GOOD
Weather: {"temperature": 53.76}
Version: 0.2.3

Hi @saultenuts - Make sure your pypowerwall.env is set up to correctly activate to TEDAPI. Key variables are PW_GW_PWD and PW_HOST. Note, PW_GW_PWD is the WiFi password listed on the QR code. It is all caps. PW_HOST must be <IP_ADDRESS>.
<EMAIL_ADDRESS>PW_PASSWORD=tesla_Password
PW_HOST=<IP_ADDRESS>
PW_TIMEZONE=America/Los_Angeles
TZ=America/Los_Angeles
PW_DEBUG=no
PW_STYLE=grafana-dark
PW_GW_PWD=ABCDEFGHIJK

Note: You can edit this file manually and just restart with ./compose-dash.sh up -d or you can re-run setup.sh.

Hi @jasonacox, my pypowerall.env is setup exactly like this.  I use the PW_GW_PWD from my gateway which works with python3 -m pypowerwall.tedapi, but I still cannot get verify.sh to show  "- TEDAPI Vitals: Connected"
Why would pypowerwall.tedapi work, but verify.sh would show not conencted, alogn with Powerwall-Dashboard?

The verify.sh script look at the pypowerwall container to see if it is using tedapi. This means that the container version is not yet using the PW_GW_PWD.  Try to rebuild pypowerwall:
docker stop pypowerwall
docker rm pypowerwall
./compose-dash.sh up -d

Surf over to http://localhost:8675/help (replace localhost with the address of the host running the dashboard), and it should show the tedapi mode.

After re-installing pypowerwall, I get this form /help
 Stat	Value pypowerwall	0.11.1 Proxy t64 mode	Local gets	17 posts	0 errors	0 timeout	0 ts<PHONE_NUMBER> start<PHONE_NUMBER> clear<PHONE_NUMBER> uptime	0:00:24 mem	34800 site_name	Tesla Powerwall cloudmode	False fleetapi	False tedapi	False pw3	False tedapi_mode	off siteid	None counter	0 authmode	cookie URI: /stats	7 URI: /version	2 URI: /help	4

There has to be something wrong with the pypowerwall.env file. A few recommendations:

Restart pypowerwall and look at logs to see if it is trying but not successful

docker restart pypowerwall
docker logs pypowerwall -f

Re-run ./setup.sh again and enter the gateway password to ensure there aren't any errors in the password.

Strange, I couldn't get it to work, logs didn't show anything.  I ended up re-installing all the docker containers and re-installed PyPowerwall and now everything works.  TEDAPI is connected and strings are being reported.

That's great news! It would be great to know what happend, but I'm glad you have it working again.


Intermediate prompt auto-submission doesn't behave as expected

I'm thinking the way to fix this is to allow prompts to have a resolve step.
While prompt will set data which is essentially a configuration step, the resolve step operates on the input data, conditions on the configuration


[Designer] json created by designer sets value of Input.Number to wrong type

Platform

Designer

Issue
This is the json created by the designer when you put a default value in a Input.Number
{
    "type": "AdaptiveCard",
    "body": [
        {
            "type": "Input.Number",
            "title": "New Input.Toggle",
            "placeholder": "Placeholder text",
            "id": "Inputer4",
            "value": "5"
        }
    ],
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "version": "1.0"
}

According to the schema value is supposed to be a number not a string, so this seems to be a designer bug for setting value as a string in the produced json.
This is most likely the root cause of this issue

We'll track this as part of #3171


Fix small syntax error in gcp_pudl_etl.sh

PR Overview

PR Checklist

[ ] Merge the most recent version of the branch you are merging into (probably dev).
[ ] All CI checks are passing. Run tests locally to debug failures
[ ] Make sure you've included good docstrings.
[ ] For major data coverage & analysis changes, run data validation tests
[ ] Include unit tests for new functions and classes.
[ ] Defensive data quality/sanity checks in analyses & data processing functions.
[ ] Update the release notes and reference reference the PR and related issues.
[ ] Do your own explanatory review of the PR to help the reviewer understand what's going on and identify issues preemptively.

@bendnorman I added this one-character fix into #3086 so there's no longer a difference between this branch and dev (other than updated lockfiles)


Broken ordering

Since time_added is never added as part of loading the patterns it always sets the order_obj to None here, preventing proper ordering.

Should be fixed with #37 and #38. Update to 0.2.7


Add CircleCI Continuous Integration (Build library & unit tests with pytest)

Fixes #9 .

Thanks a bunch!


GSNGM-821: Add a link-view to a project

@fredj or @gberaudo there is a bug, when creating a project, selecting a view, deselect/do some other stuff, select project view again, the view title does not display in the popup.

@fredj or @gberaudo there is a bug, when creating a project, selecting a view, deselect/do some other stuff, select project view again, the view title does not display in the popup.

fixed


Received corrupted packet data from client

When I try to reach server, docker server logs "Received corrupted packet data from client from client <IP_ADDRESS>"
and client alerts
[UNetConnection] RemoteAddr: <IP_ADDRESS>:52869, Name: IpConnection_2147474731, Driver: GameNetDriver EOSNetDriver_2147482513, IsServer: YES, PC: NULL, Owner: NULL, UniqueId: INVALID, Channels: 2,
I fully followed your instructions, Is there anything else I need to check?

log.txt
Here is my full-log, I just replace my steam-id as {steam-username}.
When I try to reach server via "open <IP_ADDRESS>" or  "open my.own.public.IP"
It starts to load server immeately.
After loading, client redirects to main screen(where we can start new game, load game) with error.
[UNetConnection] RemoteAddr: <IP_ADDRESS>:52869, Name: IpConnection_2147474731, Driver: GameNetDriver EOSNetDriver_2147482513, IsServer: YES, PC: NULL, Owner: NULL, UniqueId: INVALID, Channels: 2,
I don't think the local firewall is relevant, is there anything I can check?

Thanks for the information! After reviewing your log file, I'm going to guess that you're not binding the /config directory to your host, which also means that you're not providing your locally generated world to the server. The log very clearly shows that the container restarts after failing to find the game world, and then successfully loads the world after generating it in the first run. I've made these assumptions for two reasons:

The game updates in your log, which is unlikely if you've just restarted the container as updates are infrequent
The log shows Save file cannot be found. You need to generate a new world on your client, and then put it into /config/savefiles/savefile.sav

Please pull the latest version of the Docket image (docker pull wolveix/satisfactory-server:latest) and make sure to bind a local directory on your host to the container. Please show how you're running the Docker image (are you using docker run? Or docker-compose?), and I'll be able to help you further.


Please add me

Though I will have to step out for a while at about 10:30 for another meeting unfortunately.

added, please check your mail for the invite and accept it. Thanks!


How am I supposed to debug an error with this complexity? - Shapes mismatch YoloV4 - tensorflow 2.2

I recently added a new feature to my yolo implementation in tensorflow 2.2 is models are currently loaded directly from DarkNet cfg files for convenience, I tested the code with yolov3 configuration as well as yolov4 configuration they both work just fine except for v4 training. Shortly after I start training I get a shapes mismatch error and I'll be very grateful if someone can help me get rid of the error and get to finally complete my project. Please let me know in the comments and I will provide you with any resources you need to help me with fixing the problem and thank you in advance...
This is what I run in order to reproduce:
if __name__ == '__main__':
    tr = Trainer((608, 608, 3),
                 '../Config/yolo4.cfg',
                 '../Config/beverly_hills.txt',
                 1344, 756, score_threshold=0.1,
                 train_tf_record='../Data/TFRecords/beverly_hills_train.tfrecord',
                 valid_tf_record='../Data/TFRecords/beverly_hills_test.tfrecord')

    tr.train(
        100,
        8,
        1e-3,
        dataset_name='beverly_hills',
        merge_evaluation=False,
        n_epoch_eval=10,
        clear_outputs=True
    )

links to files you need:
bh_labels.csv
beverly_hills.txt
beverly_hills_train.tfrecord
beverly_hills_test.tfrecord
The error:
Traceback (most recent call last):
  File "trainer.py", line 629, in <module>
    clear_outputs=True
  File "../Helpers/utils.py", line 62, in wrapper
    result = func(*args, **kwargs)
  File "trainer.py", line 490, in train
    validation_data=valid_dataset,
  File "/root/.local/lib/python3.6/site-packages/tensorflow/python/keras/engine/training.py", line 108, in _method_wrapper
    return method(self, *args, **kwargs)
  File "/root/.local/lib/python3.6/site-packages/tensorflow/python/keras/engine/training.py", line 1090, in fit
    tmp_logs = train_function(iterator)
  File "/root/.local/lib/python3.6/site-packages/tensorflow/python/eager/def_function.py", line 766, in __call__
    result = self._call(*args, **kwds)
  File "/root/.local/lib/python3.6/site-packages/tensorflow/python/eager/def_function.py", line 826, in _call
    return self._stateless_fn(*args, **kwds)
  File "/root/.local/lib/python3.6/site-packages/tensorflow/python/eager/function.py", line 2811, in __call__
    return graph_function._filtered_call(args, kwargs)  # pylint: disable=protected-access
  File "/root/.local/lib/python3.6/site-packages/tensorflow/python/eager/function.py", line 1838, in _filtered_call
    cancellation_manager=cancellation_manager)
  File "/root/.local/lib/python3.6/site-packages/tensorflow/python/eager/function.py", line 1914, in _call_flat
    ctx, args, cancellation_manager=cancellation_manager))
  File "/root/.local/lib/python3.6/site-packages/tensorflow/python/eager/function.py", line 549, in call
    ctx=ctx)
  File "/root/.local/lib/python3.6/site-packages/tensorflow/python/eager/execute.py", line 60, in quick_execute
    inputs, attrs, num_outputs)
tensorflow.python.framework.errors_impl.InvalidArgumentError:  Incompatible shapes: [4,76,76,3,1] vs. [4,19,19,3,1]
     [[node yolo_loss/logistic_loss/mul (defined at ../Helpers/utils.py:260) ]] [Op:__inference_train_function_38735]

Errors may have originated from an input operation.
Input Source operations connected to node yolo_loss/logistic_loss/mul:
 yolo_loss/split_1 (defined at ../Helpers/utils.py:222)
 yolo_loss/split (defined at ../Helpers/utils.py:196)

Function call stack:
train_function

Your class number is different from yolov4 weight.

@fsx950223 The problem has nothing to do with weights, i dont even load the weights to produce the error just run the code using the code snippet and the data i provided, you'll get the same error and try again using yolo3.cfg it will run perfectly fine and since there is no clear indication of which tensors that are incompatible, i can't trace the source of the error

@fsx950223 The problem has nothing to do with weights, i dont even load the weights to produce the error just run the code using the code snippet and the data i provided, you'll get the same error and try again using yolo3.cfg it will run perfectly fine and since there is no clear indication of which tensors that are incompatible, i can't trace the source of the error

The log shows node yolo_loss/logistic_loss/mul (defined at ../Helpers/utils.py:260)

I ran the program in pycharm debugger, the inputs of the loss function are the same for yolo3 and yolo4 configuration or maybe i overlooked something however, the error happens in some tensorflow module that is named execute.py or a similar name

@emadboctorx,
In order to expedite the trouble-shooting process, could you please provide a minimal code sample to reproduce the issue reported here. Thanks!

@amahendrakar the minimum code sample is indicated above, clone my repo and run the code snippet above in trainer.py


dart2js: recognize harmless noSuchMethod implementations

An implementation of noSuchMethod that uses a (chain of) super calls to hit Object.noSuchMethod is operationally indistinguishable from not implementing noSuchMethod, but is useful as a means to suppress warnings about incompletely implemented interfaces.
We should ensure dart2js code quality is not affected by these 'suppression' implementations.
If all implementations of noSuchMethod forward to Object.noSuchMethod we can omit the forwarding hooks on Object (~1% of a large program).
If all implementations of noSuchMethod always throw an exception we can improve type inference (~1.5% of a large program).
After resolution but before type inference:
  Categorize noSuchMethod implementations into
  [A]: those that look like
      noSuchMethod(Invocation invocation) => super.soSuchMethod(invocation);
  where the super.noSuchMethod hits Object.noSuchMethod, Interceptor.noSuchMethod or another member of [A].
  [B]: those that syntactically directly throw an exception
  [C]: Everything else
  During type inference members of sets [A] and [B] should be ignored in determining a return type (or strengthening an argument, Issue #17084).
After type inference:
  Partition [C] into [C1] those that never return (empty returned type) and [C2] those that return.
  Ensure (and test) the forwarding hooks are generated only if union([B], [C]) is non-empty.
At end of compilation:
  Generate a diagnostic if there are implementations in [B] or [C]:
  If all definitions are in set [B], list the locations and say that the generated code will be smaller if they are rewritten to the recognized form.
  If all definitions are in [B] or [C1], list the locations and say that the generated code will be smaller and permit more optimizations if they are rewritten to the recognized form.
  Otherwise
  (1) List locations of [C2], with a message saying these 'useful' implementations of noSuchMethod, if removed, will allow the generated code to be smaller and permit more optimizations.
  (2) List locations of [B] and [C1], with a message saying rewriting them in the recognized form is also neccessary to get teh better code.

This was implemented in c90a6adc6525f1d97a7f1047102e7980437b620d


[AVM Question/Feedback]: Release tag creation failed for VNET-GW module

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Description
We have to find out why the tag creation for the VNET-GW module was rejected. The provided error doesn't make much sense and the same issue was not observed for other modules

! [remote rejected]   avm/res/network/virtual-network-gateway/0.1.2 -> avm/res/network/virtual-network-gateway/0.1.2 (refusing to allow a GitHub App to create or update workflow .github/workflows/publish-module-index.yml without workflows permission)

Without a fix, the module's updates won't lead to a new version and without a new version, the original issue isn't really resolved.
https://github.com/Azure/bicep-registry-modules/actions/runs/8567043080/job/23504037256

Note, I created the tag now manually and used the 'publish from tag' pipeline to publish the module. However, this is not a fix for the underlying issue

Closing until issue re-appears

Hey @AlexanderSehr as it looks like we don't have the issue anymore (v0.5.0 got published via pipeline today) should we close this?

Hey @eriqua, we can if we want to. The only reason I did not until today is because it happened a handful of times for different modules to this day. And we still don't know why 😄 Your call. We can of course always re-open the issue too.

If we want to keep it open I'd suggest to generalize the issue title and add info about all other modules for which the same happened. I only knew about vnet gw for which I remember this happened consistently for a few times.
Also we should agree on when it would be OK to close this then (acceptance criteria). Just to avoid this being open indefinitely.


Add PR merge policy for RC.

Update PR docs to describe more strict merge policy during RC.

lgtm


Unresolved reference setUrl in build.gradle.kts

Intellij indicates the setUrl function in the maven { } block as a unresolved reference. It happens with the latest distribution (https://repo.gradle.org/gradle/dist-snapshots/gradle-script-kotlin-3.5-20170120180718+0000-all.zip) but not with the 0.7 release distribution (https://repo.gradle.org/gradle/dist-snapshots/gradle-script-kotlin-3.4-20170117200919+0000-all.zip).
Building the project works without any problems so it seems like it's an error by Intellij but since it doesn't happen with the 0.7 wrapper I thought I'd post the issue here first.
Platform: Windows 10
Kotlin plugin version; 1.1.0-beta-17
Intellij version: 2016.3.3
Gradle wrapper: https://repo.gradle.org/gradle/dist-snapshots/gradle-script-kotlin-3.5-20170120180718+0000-all.zip

Blocked by #157.

Resolved in a7308886672047171bcddcb9979c0a22295f925f with latest IntelliJ Kotlin plugin from the 1.1 EAP channel.


UI stuck in 'Saving" state when launching Grafana app

Version: v2.3-head
Single node setup
Steps:

As an admin, launch "Grafana" app on a DO cluster.
Once launch is clicked, the UI is stuck is "Saving" state as below

The console has the below error :

Available in latest-2.3.

Tested with v2.3-head with latest UI index latest-2.3
Steps:
As an admin, launch "Grafana" app on a DO cluster.
Launching the app was successful. There were no errors in the console


how to get date in datetimepicker???

I have read the documentation and yet I have no idea how to get or set date for the component. Few examples would be appreciated.
I have tried following ways but non works.
$('#datetime').date(); //get date
$('#datetime').currentDate(adate_variable); //set default date

Try
$('#datetimepicker1').data('DateTimePicker').date()

thanxs, it works. It would be useful if included in the documentation. I had to dig down the source codes in the demo to figure out.


Documentation Improvement: README.md typos and library ysage

This pull request aims to enhance the documentation by addressing minor typographical errors in the README.md file and instructions on utilizing the fkafka library.

Thanks u so much!


Bank account - Company website field appears empty on company info confirmation page

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: v9.0.43-1
Reproducible in staging?: Y
Reproducible in production?: Unable to validate in Prod because of Bank Setup
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5032805
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause Internal Team
Action Performed:
Pre-requisite: with Expensifail account, user must have created a workspace and have enabled Workflows.

Go to Settings > Workspaces > Workspace > Workflows.
Click on "Connect bank account".
Select "Connect online with Plaid", use Regions bank and testing credentials.
Go trough the add bank account flow until you reach the Company info section.
Keep going trough the flow, when you reach the company website page, leave it as it is and click "Next".
Reach the confirmation page.

Expected Result:
Company website filed should be filled with default value on the confirmation page.
Actual Result:
Company website filed appears empty on the confirmation page.
Workaround:
Unknown
Platforms:

[ ] Android: Native
[ ] Android: mWeb Chrome
[x] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/dc351cdd-4fe0-44b1-a4ac-be14224b69a9

View all open jobs on GitHub

Thanks @gijoe0295, gonna get a revert up for that PR since it sounds like the proposal on that one is flawed.

I am reverting already 😄

PR is on staging, asking for retest here

Thanks, closing.
Posted on the other review and linked to this issue.

Thanks @allgandalf , closing, for real....


Reorder stackNavigator indices and navigationActions

What I believe is the default behavior of the Stack Navigator is creating a UX issue for my app. Here's the use case:
current behavior:
A user navigates from  screen1 to  screen2 and then to screen1 again. This creates two separate instances of the components that comprise screen1.
A user navigates from screen1 to screen2 and then presses the Android back button. This does not create two instances of screen 1, but rather, re-renders the original instance.
Problem:
screen1 makes an api call when the component mounts and I noticed that when a user navigates to screen1 the content of the call is rendered after the 1-2 seconds it takes to get a promise, convert it to json, and set the state of the component, as one would expect. Then if a user navigates to screen2, and then to screen1, there is another 1-2 second delay, indicating that a new component is being added to the stack, and that component is going through the componentDidMount() process. However, if a user were to use the back button instead, there is no delay, indicating that the navigation component is storing that old component and that it's stateful data remains intact even if the user navigates away from it. This unnecessarily slows down the user experience, and could generate dozens of unnecessary instances of commonly used screens.
Solution:
I would like the set up my app so that no more than one instance of a screen exists. if a user navigates from screen1 to screen2 and then to screen1, I simply want to reorder those instances on the stack, instead of creating a new instance of screen1. I'm not sure how I can do that.
I can achieve a similar effect by keeping track of stateful data in redux (which will require a refactor) and also keeping track of the of the Navigation states in redux. Then when a user wants to go from screen1 to screen2 and then back to screen1, I can use NavigationActions.reset() to simply rearrange the screens instead of adding a new one, but is there another way to do this?

I think this is a relatively unusual case. If someone is going from screen 1 to screen 2 and then to screen 1, why not just have them go back to screen 1?


Workaround for ZK 3.4->3.5 upgrade

Motivation
In current master code we have upgrade ZK version to 3.5, same version already used by BK to avoid all shading in internal components.
A problem has been identified in upgrading from ZK 3.4.x to 3.5.x in that if a snapshot was not already created, a validation check in ZK 3.5 would prevent the ZK server to start.
A fix is being discussed in https://issues.apache.org/jira/browse/ZOOKEEPER-3056. In the meantime, we need to apply a workaround.
Modifications

Use AspectJ interceptor to modify ZK server constructor parameters and wrap FileTxnSnapLog class to catch and handle the precise IOException thrown by ZK 3.5

Result

We can update from ZK 3.4 to 3.5 without any manual fix required.

awesome job!


Nth minute Price and Volume breakout not working (Bug)

15 min Price and volume breakout not working for any cater gory once kindly check the logic  whenever the 15 min time frame the next candle volume is above the previous candle volume around 2 or 3 percent the and price is moved higher than the previous close we can generate alert (combining with technical will work good)

Thanks @raviyellani for reporting this. It has been fixed in the recent release build #463 and above.


Turing NLG

Are there any plans to release the Turing NLG pre-trained model?

Hi, we are currently only releasing a controlled demonstration of the model as we continue to test it. This decision is in line with Microsoft’s AI ethical principles and our goal is to not just build technology but to also ensure it is distributed and used in a responsible way.  See More: https://www.microsoft.com/en-us/AI/our-approach-to-ai

+1 to release the LM!
In the meantime, the second best LM model freely available (NVIDIA Megatron 11 billions parameters) can be downloaded from Facebook Research fair (11b, 19GB model!)
https://github.com/pytorch/fairseq/blob/master/examples/megatron_11b/README.md

Hi, we are currently only releasing a controlled demonstration of the model as we continue to test it. This decision is in line with Microsoft’s AI ethical principles and our goal is to not just build technology but to also ensure it is distributed and used in a responsible way.  See More: https://www.microsoft.com/en-us/AI/our-approach-to-ai

After the giant GPT-3 has been released I assume Turing-NLG can be proposed as a reasonable alternative to academic research.


Test result not found on VS Code Ext

Describe the bug
Right clicking the test on Vscode returns “Test result not found”
Reproduction
Right clicking the test on Vscode
System Info
System:
    OS: Windows 10 10.0.19042
    CPU: (12) x64 Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
    Memory: 16.94 GB / 31.78 GB
  Binaries:
    Node: 16.14.2 - C:\Program Files\nodejs\node.EXE
    npm: 8.5.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (101.0.1210.53)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    @vitejs/plugin-react: ^1.3.2 => 1.3.2
    vite: ^2.9.9 => 2.9.9
    vitest: ^0.12.9 => 0.12.10

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I have the same problem in VSCode with a simple test that just checks for toBeDefined. In the terminal it works fine including watch mode, in VSCode, it throws the following error:

Multiple issues were fixed by @zxch3n in the vscode repository (thanks!). If @acostaf doesn't have any additional problems, I think we can close this issue.

Fixed, thanks everyone.

@acostaf not working with multiple workspaces in last version. After opening folder in new vscode window, everthing is ok. Maybe reproducing on macos?

I'm encountering the same bug..
tried the command line option cd to the root where my package lies in my workspace along with  && rushx test but getting this error.

  "@vitejs/plugin-react": "^1.3.1",
"vite": "^2.9.9",
"vitest": "^0.20.3"

Please, if you have an issue with vscode extension, open an issue in its repository.


⚠ Bofrost.ch has degraded performance

In 6d11908, Bofrost.ch (https://www.bofrost.ch) experienced degraded performance:

HTTP code: 200
Response time: 1958 ms

Resolved: Bofrost.ch performance has improved in c0ec3c9 after 7 minutes.


Configurable moderator roles

RoyalGuard's old permission system had a static permission to check if the user is/isn't a moderator. This depended on the command where ban/kick required the user to have the Ban Members permission and warns/mutes require the Manage Messages permission.
Rather than making everything confusing as to what permissions to set. The guild administrator can set a role as the moderator role. However, this role has to have the proper permissions for all commands.
If the role isn't set, RoyalGuard will check for the Ban Members permission by default.

Resolved in commit 06ce42afa431b2ea97ce3849b1d91be577d48478


Update 3.20.3

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Just a test to see how it goes. I am not expecting this to work because of the QT 5.15 dependency

@conda-forge-admin, please rerender


Electron based app build failing to install latest version of sharp correctly

This is the error that shows up in my app Nostlan that uses Electron v11.2.3. It's not including libvips in the build. Why not?
Uncaught (in promise) Error:
Something went wrong installing the "sharp" module

dlopen(/var/folders/vd/w9__42kd42b9q2x6pcy9qdmm0000gn/T/.com.qashto.nostlan.KDHkI1, 1): Library not loaded: /usr/local/opt/vips/lib/libvips-cpp.42.dylib
  Referenced from: /var/folders/vd/w9__42kd42b9q2x6pcy9qdmm0000gn/T/.com.qashto.nostlan.KDHkI1
  Reason: image not found

- Remove the "node_modules/sharp" directory then run
  "npm install --ignore-scripts=false --verbose" and look for errors
- Consult the installation documentation at https://sharp.pixelplumbing.com/install
- Search for this error at https://github.com/lovell/sharp/issues

    at Object.<anonymous> (/Applications/nostla…b/constructor.js:34)
    at Object.<anonymous> (/Applications/nostla…/constructor.js:387)
    at Module._compile (internal/modules/cjs/loader.js:1152)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1173)
    at Module.load (internal/modules/cjs/loader.js:992)
    at Module._load (internal/modules/cjs/loader.js:885)
    at Function.f._load (electron/js2c/asar_bundle.js:5)
    at Module.require (internal/modules/cjs/loader.js:1032)
    at require (internal/modules/cjs/helpers.js:72)
    at Object.<anonymous> (/Applications/nostla…harp/lib/index.js:3)
    ```

Hi, there's not a lot to go on here but it looks like you're relying a globally-installed libvips at install time, which will then be required at the same location at runtime.
If you're able to provide a standalone repo with the minimal configuration and dependencies that allows someone else to reproduce this, that would be very useful.

How do I not use a globally installed libvips? I want it to be included in the app?

https://sharp.pixelplumbing.com/install#building-from-source
SHARP_IGNORE_GLOBAL_LIBVIPS=true npm install sharp

I hope this information helped. Please feel free to re-open with more details if further assistance is required.

That didn't work. I had to revert to using v0.26.2 which works. Something about the newer versions causes the build to fail.

If you're able to provide a standalone repo with the minimal configuration and dependencies that allows someone else to reproduce this, that would be very useful.

npm ERR! code 1
npm ERR! path /home/qashto/dev/apps/nostlan/node_modules/sharp
npm ERR! command failed
npm ERR! command sh -c (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
npm ERR! sharp: Using existing vendored libvips v8.10.6
npm ERR! make: Entering directory '/home/qashto/dev/apps/nostlan/node_modules/sharp/build'
npm ERR!   CC(target) Release/obj.target/nothing/../node-addon-api/nothing.o
npm ERR!   AR(target) Release/obj.target/../node-addon-api/nothing.a
npm ERR!   COPY Release/nothing.a
npm ERR!   TOUCH Release/obj.target/libvips-cpp.stamp
npm ERR!    In file included from ../src/common.cc:24:
npm ERR! /usr/include/vips/vips8:35:10: fatal error: glib-object.h: No such file or directory
npm ERR!    35 | #include <glib-object.h>
npm ERR!       |          ^~~~~~~~~~~~~~~
npm ERR! compilation terminated.
npm ERR! make: *** [sharp.target.mk:141: Release/obj.target/sharp/src/common.o] Error 1
npm ERR! gyp ERR! build error
npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2
npm ERR! gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/node-gyp/lib/build.js:194:23)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:369:20)
npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)
npm ERR! gyp ERR! System Linux 5.10.30-1-MANJARO
npm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
npm ERR! gyp ERR! cwd /home/qashto/dev/apps/nostlan/node_modules/sharp
npm ERR! gyp ERR! node -v v15.14.0
npm ERR! gyp ERR! node-gyp -v v7.1.2
npm ERR! gyp ERR! not ok

Same problem on Linux too. v0.28.1 doesn't work. Just try installing it into an empty repo and run this command npm rebuild --build-from-source --runtime=electron --target=11.2.3 --disturl=https://atom.io/download/atom-shell

okay I tried v0.27.1 on linux which I used for the previous release of my app and it worked

You'll either need to npm install --build-from-source in the first place or remove node_modules/sharp/vendor after running npm install if you're later planning to use npm rebuild --build-from-source

oooooh thank you!


Update cache action to v2

Related to https://github.com/opencollective/opencollective/issues/4322

Seems duplicate with https://github.com/opencollective/opencollective-api/pull/6315


Font seems to load, but is not adding any boldness in browser, terminal, but does on abiword

Hi.
I wonder what my problem is. I installed all the 3 fonts to my Arch Linux through ~/.local/share/fonts/ dir and they show up in fc-list. I can also load them in qutebrowser or firefox, and I can see a difference to the font I have before loading them at least on qb. However, they just change the outlook, but do not add boldness to the characters at the begin of words. Same goes for kitty terminal when I try run kitty with kitty --override font_family='Fast_Sans' I don't see any boldness. In fact, on kitty the font may not change at all. Tried with the dotted font and no dots are added. I am succesfully loading my custom conhanzi font on qutebrowser and it also has a lot of ligature substitutions going on, so there should be ligature support there. Also kitty supports ligatures and I can load conhanzi with the override flag succesfully there.
Then running abiword and picking the Fast_Sans from the font menu I can see it working properly bolding first chars on each words so the font files themselves should be alright I guess
edit: I might have figured this out. In firefox if I pick one of the fonts as the "monospace" font, then it works there properly. Maybe it has to do with needing a monospace variation and I just need to find out how I can force one of these to be forced as monospace on terminal and qutebrowser. However it doesn't explain why on qb I can see the font appearance changing when I switch :thinking:
edit2: Kitty doesn't support non-monospaced fonts, so I guess I would need to create a monospaced variation of the font using your python script or something else I guess

Hey would it be possible for you or someone on windows computer to create a fast font from some Monospace font to add compatibility? For example DejaVu Sano Mono? https://dejavu-fonts.github.io/
I'm on linux and Fontlab is only available onWindows and Mac. I have FontForge installed and I'm already struggling at the first step adding a suffix to each character in a font.
That python script that is mentioned on the "apply to other fonts" part though.. For example, using the addfeatures.py script.  https://github.com/simoncozens/test-fonts/blob/master/addfeatures.py That looks like a simple script and Chatgpt had a plan how to use it once I first got the bold glyphs copied to the regular font file.
I then tried to keep on getting the glyphs copied. Chatgpt gave me instructions on copying them with fontforge, but the options were not there or they were grayed out. Then Chatgpt tried instructing me to do it with a python script using fonttools, but after 30+ minutes with trial and error, we couldn't get them copied. I also tried asking Gemini. So apparently this is a too difficult thing for a LLM chatbot for now at least

Just an update where I have got so far.
Using Fontforge I got so far (hopefully right way) that I added new encoding slots to regular font file, then pasted these bold glyphs from bold font file to the new empty slots in regular font file. Then manually.. sigh.. renamed all of them to a.bold A.bold b.bold B.bold etc. At this point I guess I have the font file with regular and both in one.
Now after this I should paste the contents of the .fea file to a proper place and I'm struggling.
I tried going to Element>font info> Lookups> Add Lookup. Choosing in new box "contextual substitition > dropdown "Calt" contextual substition. Clicking the box opens a window that has DFLT{dflt} latn{dflt,CAT, ESP ,GAL ...} ends in math{dflt}.
I tried then pasting the contents of the .fea (or rather the simplified A-Z code snippet) from the fontlab tutorial to it overwriting those or also just below them, but I'm getting "script tag on line 1 (calt) is too long. It may be at most 4 letters"
I might try consulting fontforge people or read more how to do the calt stuff there but now I have run out of time for today probably.


Bump version in debian changelog

@flexiondotorg Can you please bump the version in debian/changelog file to facilitate building on Launchpad?

@flexiondotorg A gentle reminder.

@philclifford Any idea on this request?

I suggest you fork the Debian packaging for building in LP. The automation that publishes new releases to the GitHub page automatically bumps the version.


net: lwm2m: Update connectivity monitor object

Update the connectivity monitor object to version 1.2.
Added also a Kconfig option to switch between object versions 1.0 and 1.2.
The OMA specification for LwM2M version 1.1 uses the object version 1.2 of the connectivity monitor object.
Signed-off-by: Jarno Lamsa<EMAIL_ADDRESS>

@VeijoPesonen @jheiskan81 @SeppoTakalo please review.

Thank you for your review comments @rlubos I think I have addressed those, could you please re-review.


carrierwave-aws doesn't append bucket name to the host URL

fog gem config:
config.fog_credentials = {
  :host => 's3-eu-west-1.amazonaws.com'
}
config.fog_directory  = 'mybucket'

carrierwave-aws config:
config.aws_bucket = 'mybucket'
config.asset_host = 'https://s3-eu-west-1.amazonaws.com/mybucket'

Shouldn't this be kept a bit more consistent?

Perhaps the means for configuring fog has changed. Very little was changed intentionally, as noted in the README:

The only notable difference is the use of aws_bucket instead of fog_directory, and aws_acl instead of fog_public.

I'd rather not change the existing config on carrierwave-aws just to match fog though, if that has indeed changed. Thank you for the consideration.


Filter and sort broken in <IP_ADDRESS>9

Filter and Sort is broken in <IP_ADDRESS>9 version. I rolled back to the 4.11.2 version and there it works fine

Could you be a little more specific please.

The following setup code in my collection that works perfectly with 4.11.2 and when I updated to 4.11.3 it stopped working. The connection doesn't seem to watch / observe the filter and sorter anymore.
public ObservableCollection(IConnectableCache<T, string> source, Func<T, TResult> transform, IScheduler scheduler, IApplicationConfiguration config)
{
    _pageData = new PageParameterData(1, config.PageSize);

    var pager = Pager.WhenValueChanged(x => x.CurrentPage)
        .Select(page => new PageRequest(page, config.PageSize))
        .StartWith(new PageRequest(1, config.PageSize))
        .DistinctUntilChanged();

    var filter = this.WhenPropertyChanged(x => x.Filter)
        .Throttle(TimeSpan.FromMilliseconds(250))
        .Select(x => x.Value ?? NoFilter);

    var sorter = this.WhenValueChanged(x => x.Sort)
        .Where(x => x?.Item1 != null)
        .Select(x => x.Item2
            ? SortExpressionComparer<TResult>.Ascending(x.Item1)
            : SortExpressionComparer<TResult>.Descending(x.Item1));

    var connection = source.Connect()
        .Transform(transform)
        .Filter(filter)
        .Sort(sorter)
        .Page(pager)
        .Do(x => _pageData.Update(x.Response))
        .ObserveOnSafe(scheduler)
        .Bind(_collection)
        .DisposeMany()
        .Subscribe();

    var changes = Observable
        .FromEventPattern<NotifyCollectionChangedEventHandler, NotifyCollectionChangedEventArgs>(
            x => _collection.CollectionChanged += x,
            x => _collection.CollectionChanged -= x)
        .ObserveOnSafe(scheduler)
        .Select(x => x.EventArgs)
        .Subscribe(x => CollectionChanged?.Invoke(this, x));

    _cleanup = new CompositeDisposable(connection, changes);
}

I cannot see anything obvious. Have you checked for exceptions using the error channel?

I have a near identical example to your code on dynamic trader. I will try it with 4.11.3 tonight.

That example was the main source for my code.
Sorry I also didn't have time anymore yesterday evening to look further into it. Maybe tonight or tomorrow I find the time. For now the 4.11.2 is a good workaround.

I upgraded dynamic trader to v<IP_ADDRESS>9 and the paged example still works

Im a bit busy atm. I will attach the 4.11.3 to my own code this sunday or after the weekend and let you know what I find. Which branch\tag is the 4.11.3 release?

Grab the code in this branch Version 4. Although I did not create a tag, the code is unchanged since.
Btw for future releases I will make sure I create tags.

I did some quick debugging and I get an SortException in the FilteredIndexCalculator on line 90. The merged changeset from master is that big that I cannot quickly see which change caused this to happen.

That's odd that you are getting this exception now, as that code has not substantially changed for years so I am baffled why you are getting it now. The only difference is the following line (I checked the object history):
if (insertIndex < 0)
             throw new SortException("Cannot determine current index");

Beforehand it threw an index out of range exception when that condition was hit which was not a very helpful exception which is why I added the code.  I have seen this error condition hit on objects which are mutable and have a variable hash code (i.e. the default one which is based on all values). If the object is mutable, try and implement a hash code based solely on the key value which is important for ```IndexOf()`` operations.
Failing that, I am left scratching my head.

I just realised why the condition has been hit.  The change is ChangeReason.Move which can only possibly be hit after the sort comparer has changed.  Check out this commit to see what is different with sorting.
The change was necessary so a consumer can apply animations on the UI when the comparer changed - previously the comparer change would always reset the entire list even for a small number of changes.
But even then the condition can only be hit when Sort(myComparer, resetThresohold: 100) overload is used. Have you set the threshold? If so, try removing the threshold to see if the problem goes away.
So where does this leave us? Possibly one of the following

Mutable object which has changed - if so implement a non-changing has code (as per previous comment)
Using reset threshold - try removing it to see what happens
Failing the above, the only way I am going to to get to the root of the matter is to be able to replicate the issue in test code

I've found the problem and I am working on a fix

@njannink this should be fixed now. Update to the latest Nuget version and let me know how you get on

Thanks I will test it tonight and let you know

Tested 4.12.0 and it works. Thanks again for the quick fix


[Components] Check hover/pressed implementation

Check if we have aligned implementations on all platforms (Android, Figma, iOS, Web). If the states are different compared to the spec, please create implementation tickets.
More information can be found here: https://adevinta.slack.com/archives/C04LNCEMMUN/p1695809868250139?thread_ts=1695734572.383399&cid=C04LNCEMMUN
### Tasks
- [ ] Checkbox
- [ ] Radio button
- [ ] Swtch
- [x] Slider

As discussed, the Slider component implementation of hover/pressed states has been treated in implementation ticket: https://github.com/adevinta/spark/issues/961


[RFC] Deprecate gradient clipping flags on the trainer

Proposed refactoring or deprecation
Deprecate these flags:
https://github.com/PyTorchLightning/pytorch-lightning/blob/7a9a08c5d3ca4699fb439f691c40e1320b37507a/pytorch_lightning/trainer/trainer.py#L122-L123
since users can already configure gradient clipping on the LM:
https://github.com/PyTorchLightning/pytorch-lightning/blob/7a9a08c5d3ca4699fb439f691c40e1320b37507a/pytorch_lightning/core/lightning.py#L1482-L1515
Motivation

There shouldn't be two ways for users to do something
Reduces # of args on trainer constructor
Fixes situations like this
https://github.com/PyTorchLightning/pytorch-lightning/blob/c33df2639f19d49c5e7520294e3221efe402d684/pytorch_lightning/plugins/training_type/deepspeed.py#L432-L433
where we have to reach through LM and trainer to get gradient_clip_algorithm property

Pitch

Deprecate gradient_clip_val and gradient_clip_algorithm from trainer constructor and as trainer properties
Make gradient_clip_val and gradient_clip_algorithm properties of LM instead

Hey @daniellepintz,
Personally, I am not in favour of this depreciation. This would be an important API breaking change and it would make discoverability of this feature harder for new users.