[Fix] display-name: Get rid of false position on component detection

fixes #2751

Please unmark this as a draft when it's updated.

This also fixes #2758

Hey Guys, any news on this one?

Codecov Report

Merging #2759 (9799131) into master (53a0d84) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #2759   +/-   ##
=======================================
  Coverage   97.43%   97.43%
=======================================
  Files         114      114
  Lines        7536     7536
  Branches     2750     2750
=======================================
  Hits         7343     7343
  Misses        193      193

Impacted Files
Coverage Δ

lib/rules/display-name.js
98.11% <100.00%> (ø)

Continue to review full report at Codecov.

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


Issue #169 — Reorganize project as an app bundle

This pull request covers the remainder of issue #169 involving the conversion to Swift 3 and project restructuring. The last 3 commits are regarding the app bundle / project restructure.
NOTE: This is built on top of PR #201 and should be merged after or instead of that request.

Good! Only thing I can note is your changelog entries' format:
* Description of the change.••
  [Author Name](GH profile link)
  [#PRNum](link to PR)

With • to be replaced by a space (ensures that the author and PR links are on a new line).

Time to rework this PR now that #201 has been modified then merged! :tada:
Could you please rebase this on top of master so that it now only include th commits related to the "app bundle migration" change?
Thanks!

Okay! so this should be ready for a look.

Rebased off master
.app is runnable and buildable in xcode

you can pass args by editing the scheme (we may want to leave some in there as they can be toggled)
note I had to disable nsdocumentrevisionsdebugmode (was parsed as command line args)

Rake now builds a more .app like Resources structure

Let me know what you think.

@AliSoftware incorporated your feedback and rebased again 👍

Just a small change requested and I think (at least from what I read from GitHub) that we're good to go.
Maybe if I have more time later I'll pull it and test and run on my Mac in Xcode (or if anyone can do it too to validate that in practice) before we (finally!) merge.

Wait… I think at some point I disabled the EMBEDDED_CONTENT_CONTAINS_SWIFT build settings back in the day when I configured SwiftGen as a command-line target (because Xcode doesn't know how to embed the Swift dylibs if the build product isn't packaged as a bundle). Btw, this caused an execution of pod install or pod update to generate a warning, because the project overwrote this build settings (while we shouldn't, or at least should $(inherit))
I'm surprised not to see that Build Setting being changed in this PR's diff? Shouldn't this (well, more likely the new ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES replacing it) be present again now?
🤔 I definitely will have to pull this on my Mac and inspect/test this. Diff'ing a pbxproj directly on GitHub isn't easy ^^

I can confirm that ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES is set to Yes.
It runs from within Xcode, and also runs when moving the produced app (and deleting the other produced content such as frameworks), so there are definitely no dependencies left.

@AliSoftware Good catch on the root, I've rebased and pushed the fix. Re: the .pbxproj file, for some reason it's been collapsed in this pull request (maybe this is what you're referring to?) there are changes and ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES is flagged set to yes. Let me know if you'd like it to $(inherit) (I believe there is still a warning when you pod update/install).

Indeed, I think we should be sure to get rid of the pod update/install warning.
Probably no need to set the value to $(inherited), just remove the value completely from the Target level so that we just don't override the one set on the Config.File level.

@AliSoftware agree! pushed the fix.

This is the output I'm getting with the latest code:

~/D/L/SwiftGen2 ❯❯❯ pod update                                                       feature/ahtierney/app-bundle
Update all pods
Updating local specs repositories
Analyzing dependencies
Fetching podspec for GenumKit from GenumKit
Downloading dependencies
Using Commander (0.6.0)
Using GenumKit (4.0.0)
Using PathKit (0.7.0)
Using Stencil (0.6.0)
Generating Pods project
Integrating client project
Sending stats
Pod installation complete! There are 4 dependencies from the Podfile and 4 total pods installed.
~/D/L/SwiftGen2 ❯❯❯

I've finally got some time to pull and test in Xcode. Great work!

Just opened a separate issue as testing #204 in Xcode makes me realise that the ANSI color codes are printed in the Xcode console even if Xcode console doesn't support colors (RIP XcodeColors plugin in Xcode 8 😢 ), but that's a separate issue.

I'd suggest to remove the XcodeColors env var (as we now use Xcode 8 so no more XcodeColors) and add some sample launch arguments to make it easy to toggle them and test the various scenarios from Xcode.
I've made the changes locally, here's what the diff looks like. @ahtierney I can't push on your fork (I thought I've read some info on GitHub allowing contributors to push on a foreign fork of a PR? But maybe I'm wrong), so I'll let you apply that patch and push it if you have time. Otherwise that's not a big deal, we could make that change in master once merged.
diff --git a/SwiftGen.xcodeproj/xcshareddata/xcschemes/swiftgen-cli.xcscheme b/SwiftGen.xcodeproj/xcshareddata/xcschemes/swiftgen-cli.xcscheme
index 87f3c10..a350b98 100644
--- a/SwiftGen.xcodeproj/xcshareddata/xcschemes/swiftgen-cli.xcscheme
+++ b/SwiftGen.xcodeproj/xcshareddata/xcschemes/swiftgen-cli.xcscheme
@@ -14,8 +14,8 @@
             buildForAnalyzing = "YES">
             <BuildableReference
                BuildableIdentifier = "primary"
-               BlueprintIdentifier = "09A87B401BCC9B8000D9B9F5"
-               BuildableName = "swiftgen"
+               BlueprintIdentifier = "234F7E6D1DEBD5C5001B3C10"
+               BuildableName = "swiftgen.app"
                BlueprintName = "swiftgen"
                ReferencedContainer = "container:SwiftGen.xcodeproj">
             </BuildableReference>
@@ -85,13 +85,28 @@
             ReferencedContainer = "container:SwiftGen.xcodeproj">
          </BuildableReference>
       </BuildableProductRunnable>
-      <EnvironmentVariables>
-         <EnvironmentVariable
-            key = "XcodeColors"
-            value = "YES"
+      <CommandLineArguments>
+         <CommandLineArgument
+            argument = "colors -t swift3 $(PROJECT_DIR)/UnitTests/fixtures/colors.xml"
             isEnabled = "NO">
-         </EnvironmentVariable>
-      </EnvironmentVariables>
+         </CommandLineArgument>
+         <CommandLineArgument
+            argument = "images -t swift3 $(PROJECT_DIR)/UnitTests/fixtures/Images.xcassets"
+            isEnabled = "YES">
+         </CommandLineArgument>
+         <CommandLineArgument
+            argument = "storyboards -t swift3 $(PROJECT_DIR)/UnitTests/fixtures/Storyboards-iOS"
+            isEnabled = "NO">
+         </CommandLineArgument>
+         <CommandLineArgument
+            argument = "strings -t swift3 $(PROJECT_DIR)/UnitTests/fixtures/Localizable.strings"
+            isEnabled = "NO">
+         </CommandLineArgument>
+         <CommandLineArgument
+            argument = "fonts -t swift3 $(PROJECT_DIR)/UnitTests/fixtures/Fonts"
+            isEnabled = "NO">
+         </CommandLineArgument>
+      </CommandLineArguments>
       <AdditionalOptions>
       </AdditionalOptions>
    </LaunchAction>
@@ -104,9 +119,9 @@
       <MacroExpansion>
          <BuildableReference
             BuildableIdentifier = "primary"
-            BlueprintIdentifier = "09A87B401BCC9B8000D9B9F5"
-            BuildableName = "swiftgen"
-	    BlueprintName = "swiftgen"
+            BlueprintIdentifier = "234F7E6D1DEBD5C5001B3C10"
+            BuildableName = "swiftgen.app"
+            BlueprintName = "swiftgen"
             ReferencedContainer = "container:SwiftGen.xcodeproj">
          </BuildableReference>
       </MacroExpansion>

:tada:


PR commits are cherry-picked instead of the squashed commit

Hey just testing this for our repo and I am seeing that squashed PRs cherrypick using the commits on the PR branch, not the final squash commit. I saw this ticket but it has been closed
https://github.com/korthout/backport-action/issues/46
I've not really dug into it yet but is it possible on a squash commit to grab that commit and cherrypick using that?

I must admit its been a week so I cant fully remember, but I feel like I was having issues with the backport picking up merge commits where main/master had been merged into the PR, but they shouldn't be part of the backport
I'll try and revisit this this week if I can and take another look

Thanks @Lawls91! That's a great point!
There's another feature request that will help resolve that problem, which I plan to implement once I've completed #340:

#341

Still, even with #341 implemented, there would be cases left where cherry-picking the resulting commit(s) (i.e. the squashed commit or the rebased commits) are preferable. So, eventually I hope to support this as well.

I just ran into this as I started using this action. The problem if you squash PRs into main and then backport only the cherry-picked commits to another branch is that the commits will no longer be the same, i.e., the release branch will have different commits from the same changes.
I don't see a great way around this problem though because if you just simply backported the squashed commit, then you run the risk of picking up merge commits from main and end up merging changes you didn't intend to into your release branch...

@jrhemstad Yes, the action only cherry-picks the commits that exist on the merged pull request, at this time.

you run the risk of picking up merge commits from main and end up merging changes you didn't intend to into your release branch

This would not be a risk if this action would support cherry-picking the squashed commit instead of the commits that exist on the merged pull request. However, it does not support this yet.
It seems you have a specific need for cherry-picking only the squashed commit. Can you elaborate on why you need this specifically? It may help me prioritize this over other issues.

Can you elaborate on why you need this specifically?

For example, we recently had a PR where the backport action failed when trying to cherry-pick the individual commits: https://github.com/NVIDIA/cccl/pull/574#issuecomment-1793117712
(fyi, the instructions it prints for manually cherry-picking don't include the logic for skipping merge commits)
Trying to manually cherry-pick all of the PR commits was a bit of a pain. In contrast, when we just manually cherry-picked the squashed commit, it applied cleanly without any conflicts or issues: https://github.com/NVIDIA/cccl/pull/663. It would be nice if the action had a way to automate this for us as we never care about preserving the individual commits in the PR we're backporting.

Ah yes, reduced chance of conflicts is definitely a benefit of cherry-picking a squashed commit. I see this feature (cherry-picking the resulting commits rather than the pull request's commits) as useful, but there are a few issues I'll prioritize over this at this time, like:

#395
#305
#386
#384

@jrhemstad @Lawls91 v2.2.0 is out and adds experimental support to detect_merge_method. I believe it resolves this issue for you. Please give it a try and let me know what you think.


Week of 2022/11/14 - Python buildpack releases

All component buildpacks have been released

We saw an issue with Cpython which meant we need to recompile the dependencies and re-release.

With the release of Python Buildpack v2.5.0 this is complete.


Discrepancies in TopoMLP Implementation and GPU Memory Usage

I have encountered two issues while implementing the TopoMLP codebase, and I am seeking assistance in resolving them.
Question 1: GPU Memory Usage Discrepancy
During model training, I noticed a considerable difference in GPU memory usage between the TopoMLP model and other similar-sized models like Stream Map Net. While the TopoMLP model at batch size 1 consumed approximately 42 GB of GPU memory, Stream Map Net only consumed around 7.5 GB at the same batch size. I'm curious about the reasons behind this disparity in GPU memory usage, particularly whether TopoMLP loads LiDAR data, which might contribute to the increased memory overhead.
Question 2: Convergence Discrepancy
When implementing the TopoMLP code with a modified learning rate (0.1 times the original learning rate), I observed a significant difference in convergence behavior compared to the expected results. Specifically, while the original logs indicated convergence to a loss of approximately 7, my implementation converged to a loss of around 11. Additionally, the lane detection results differed notably. I'm seeking insights into why such discrepancies in convergence occurred.

Our code uses hybrid matching to improve training speed, which requires more GPU memory usage (this is the main memory usage compared to StreamMapNet). You can remove hybrid matching and add flash attention to save memory usage.
The learning rate is well-tuned by ourselves.  Other learning rate settings may be not optimal.

Thanks for the suggestion. Much appreciated.


Update index.md

[ x] I have read freeCodeCamp's contribution guidelines.
[ x] My pull request has a descriptive title (not a vague title like Update index.md)
[ x] My pull request targets the master branch of freeCodeCamp.
[x ] None of my changes are plagiarized from another source without proper attribution.
[ x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it.
Reason: Your addition is almost a word-for-word copy of the content found on https://www.tutorialspoint.com/android/android_fragments.htm.  We do not allow plagiarized content.
Thank you and happy coding.


Fix zero width matches for Regex.split()

Fixes zero width matches for Regex.split() and pulls all the constant flag values to a primitive at the top.

Nice, thanks!


Take more frequent state snapshots

Currently when db-sync is stopped and restarted it rolls back to the start of the epoch. This is done to prevent the loss of volatile data that is in-memory but has not yet been inserted into the database.
Currently (at epoch 292) it takes over 5 hours to sync a single epoch. Ideally, after a rollback, the worst case re-start re-sync would be an hour.
There is a partial solution in #840 .
Possible solutions:

Periodically write this volatile data to disk. This idea's major problem is that it adds complexity and fragility. In the worst, problem A has solution B, which also has problems to which solution C is added ad infinitum.
Implement #850 and add a dynamic block size to aim to get the volatile data inserted as quickly as possible to that the partial fix in #840 is more effective.
Have ledger-specs provide partial stake distribution and epoch rewards so that this data does not need to be stored in queues.

The existing solution may be adequate for this. We insert 1000 rewards per block. So even if there are 1000000 rewards, it will take 1000 blocks to insert them. This is the interval we can't take ledger snapshots, but it is not that big. We already take snapshots every 500 blocks while following, so this makes us lose 2-3 snapshots.

Yes, you may be correct. I will merge #840 and do some more testing.

I still think longer term we should explore the third option, having legder-specs provide partial rewards so that we can drop the queues all together.

We now have incremental rewards, which allow more frequent snapshots.


Claim 1200 VC1S nodes provided by @scaleway

@bchatelard Thank you our super hero from Scaleway !!
This journey cannot be happened without you!!
LGTM


Solr arrays not getting inserted in to solr

Hi I'm running mongo-connector latest build and I'm unable to insert list values into solr multiValued fields.  In my test index, I have the followling solr fields.
<field name="_id" type="string" indexed="true" stored="true" required="true" multiValued="false" />
   <field name="_ts" type="long" indexed="true" stored="true" multiValued="false" />
   <field name="_ns" type="string" indexed="true" stored="true" multiValued="false" />
   <field name="spec_name" type = "string" indexed = "true" stored = "true" multiValued="true"/>
   <field name="spec_value" type = "string" indexed = "true" stored = "true" multiValued="true"/>

Given these two documents from my mongodb
{ "_id" : ObjectId("5320d76ebdca98e379b97b9b"), "jobID" : "2597402", "spec_value" : "20" }
{ "_id" : ObjectId("5320d7ccbdca98e379b97b9c"), "jobID" : "2597402", "spec_name" : [  "one",  "two" ], "spec_value" : [  "20",  "test" ] }

the first document inserts the spec_value field correctly, but the second does not.
Is this possibly a bug?
Also, here is my mongo-connector call for starting it up.
mongo-connector -m localhost:27017 -t http://localhost:8181/solr/content  -d mongo-connector/mongo_connector/doc_managers/solr_doc_manager.py -n test.test -a tomcat -p tomcat -i spec_name,spec_value,jobID

Thanks for any help you may offer,
Tim

Following this issue, I also have a problem inserting into arrays, however my structure is a little different.  I have in mongo:
{
   locations : [
     ..., { name : "chicago, il", contact : {name : "curious george", email : "georgesemail"}},
  ..]
}

And I want to pull out all names.  locations*.contact.name is not allowed unfortunately by dynamicField.
Is there any way to get at this?

I see this post is closed. However, I would like to know if there is any way to handle an array of String within an array of Object.
Ex:
{
"name":  "doc1",
"a" : [
{
"b" : "something.0",
"c" : [
"1001",
"1002"
]
},{
"b" : "something.1",
"c" : [
"1006",
"1007"
]
}
]
},
{
"name":  "doc2",
"a" : [
{
"b" : "something.2",
"c" : [
"1001",
"1002"
]
},{
"b" : "something 3",
"c" : [
"1006",
"1007"
]
}
]
}
This get converted as
{
"name" : "doc1",
a.0.b = "something.0",
a.0.c.0 = "1001",
a.0.c.1 = "1002"
a.1.b="something.1",
a.1.c.0 = "1006",
a.1.c.1 = "1007"
},
{
"name" : "doc2",
a.0.b = "something.2",
a.0.c.0 = "1001",
a.0.c.1 = "1002",
a.1.b="something.3",
a.1.c.0 = "1006",
a.1.c.1 = "1007"
}
Now how can I search in Solr to match all documents that has
a..b="something.0" and a..c contains "1002"
Sorry for the lengthy detail.


java.lang.IllegalArgumentException: No enum constant me.blackvein.quests.particle.PreBuiltParticle.ANGRY_VILLAGER

Quests-3.9.4#117

Error log
https://pastebin.com/H4Erpaci

In your config.yml change "angry_villager" to "villager_angry"

In your config.yml change "angry_villager" to "villager_angry"
Problem still exist

in order to stop this continue to have error message , i disabled the npc-effects
It do stop showing errors.
But the problem still exist right?

@hkkongou Thanks for the followup. Please re-enable npc-effects and try the following build:
https://ci.codemc.io/job/PikaMug/job/Quests/118/
Note that if you're using QuestsGUI, the current version may not be compatible with that build.


Support registry adaptor plugin

Feature Request
Is your feature request related to a problem? Please describe
The client randomly selects eventmesh from the address list to establish a connection. As to the client with same group , they may connect the same eventmesh, or the distribution of clients will be hugely uneven.Therefore, it may lead unbalanced flow on eventmesh.
Describe the solution you'd like

Add eventmesh-registry-plugin module refers to eventmesh-connector-plugin, eventmesh-registry-plugin contains registry api design module and concrete registry plugin implementation module;
I will provide a simple API interface design in eventmesh-registry-api module , support rebalance among clients with same group,  and recommend eventmesh  before connecting in the eventmesh-runtime by calling the API interface.
In order to avoid eventmesh running error , I provide a plugin(eventmesh-registry-rocketmq-namesrv) of the default empty implementation of the eventmesh-registry-api, as to this plugin implemention, you can consider your own requirements.If you are interested in this issue, welcome to participate and suggestions.

Firstly, Every eventmesh will report the distribution data of clients to registry periodly;
Then registry can know the distribution data of clients with same group in different eventmesh.
At last, Eventmesh can do rebalance by the distribution data from registry and recommend eventmesh to client when connect.
API interface design in eventmesh-registry-api
@EventMeshSPI(isSingleton = true)
public interface RegistryService {
    void init() throws RegistryException;

    void start() throws RegistryException;

    void shutdown() throws RegistryException;

    List<EventMeshDataInfo> findEventMeshInfoByCluster(String clusterName) throws RegistryException;

    Map<String/*eventMeshName*/, Map<String/*purpose*/, Integer/*num*/>> findEventMeshClientDistributionData(String clusterName, String group, String purpose) throws RegistryException;

    boolean register(EventMeshRegisterInfo eventMeshRegisterInfo) throws RegistryException;

    boolean unRegister(EventMeshUnRegisterInfo eventMeshUnRegisterInfo) throws RegistryException;
}

I think we may need to add a notify method in RegistryService interface.

Then we needn't query by time polling.

EventmeshRuntime reports the data to every registry of the same cluster. Notification mechanism maybe exist the problem of repeated notification.


Ks/issue/98

Fix problems with brokes links and images after setting repo to Public.
Close #98

Merge without review.


Chart should be updated for version 2019

The chart ends with version 2018.X and should add version 2019.X

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

ID: c84a54e9-baa1-521b-c6de-4edb2024e43e
Version Independent ID: 181e6bb5-86e8-91e6-b3cf-9b554d4a97a0
Content: Upgrade your deployment - Azure DevOps Server & Team Foundation Server
Content Source: https://mseng.visualstudio.com/DefaultCollection/TechnicalContent/_git/tfs-docs-pr?path=%2fdocs%2fupgrade%2fget-started.md&version=GBlive&_a=contents
Product: devops-server
Git Login: aaronhallberg
Microsoft Alias: aaronha

I agree with @filipiwinski. The only place I have seen this mentioned in in the Azure DevOps Server 2019 Release notes: https://docs.microsoft.com/en-us/azure/devops/server/release-notes/azuredevops2019?view=azure-devops. In addition to updating the chart, the following statement needs to be made on THIS page:
"Direct upgrade to Azure DevOps Server is supported from Team Foundation Server 2012 and newer. If your TFS deployment is on TFS 2010 or earlier, you need to perform some interim steps before upgrading to Azure DevOps Server 2019. "

The Previous Versions/Upgrade Path chart was JUST updated to include Version 2019 this week (although the date on this article is still not changed to be current).
Bottom line:  You can upgrade directly to 2019 from several prior versions.

The chart says you can go from 2012 directly to 2019, this appears to not be the case.

Doc updated here: https://docs.microsoft.com/en-us/azure/devops/server/upgrade/get-started?view=azure-devops-2020


Add mergify config and document how it's used

This commit adds a mergify configuration to the repoistory. Mergify will
let us automate PR merging and backporting to stable branches. This
should hopefully simplify the maintainence of the repository as core
reviewers now we only need to tag a PR as "automerge" and the bot will
handle rebasing and merging for us. Additionally, it will automate the
backporting of PRs for us. This will enable us to maintain stable bugfix
releases more easily and hopefully avoid for tension like we had in
0.11.0 between getting a release out for Python 3.10 support and merging
the required features.
To facilitate the use of all these new tools this commit adds detailed
documentation to the contributing guide on code review, the use of
mergify, stable branches, and backporting.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.0004%) to 98.508%

Files with Coverage Reduction
New Missed Lines
%

src/shortest_path/all_pairs_dijkstra.rs
2
98.54%

Totals

Change from base Build<PHONE_NUMBER>:
0.0004%

Covered Lines:
11027

Relevant Lines:
11194

💛  - Coveralls


Support for result builder in concat and merge

Related Issues 💭

Description 📝

Expand the functionality of EffectsBuilder proposed in #68 .
Add unit tests for EffectsBuilder.

Additional Notes 📚
.concat {
    .just(.increment)
    .just(.increment)
    if condition {
        .just(.increment)
    }
}

Checklist ✅

[x] If it's a new feature, have appropriate unit tests been added?
[x] If the changes affect existing functionality, please verify whether the above information has been appropriately described.

Thanks!


Extract mksi into new repo

This PR along with https://github.com/GEOS-ESM/GEOSadas/pull/267 is an attempt to extract the mksi folder in GEOSana_GridComp into its own repo. To do so, the RepoExtractor tool was run as:
./extract_repo.bash -r "GEOSana_GridComp" -d "mksi" --newrepo "GEOS_mksi" --develop --create-repo --push

and a new repo GEOS_mksi was created:
https://github.com/GEOS-ESM/GEOS_mksi
Then GEOS_mksi was added as a new component and placed as @mksi/ under GSI_GridComp/
Tests show it builds which should be proof it is correct, but probably needs testing to be sure.
And of course, before anything is done, tags should be made in GEOS_mksi and GEOSana_GridComp.
Closes https://github.com/GEOS-ESM/swell/issues/289

@mathomp4 Have Matt, can we just get this in?

@mathomp4 Have Matt, can we just get this in?

Oh sure. Let me fix the conflicts and then you can merge.

@rtodling I fixed up the conflicts and it should be good to go. You can re-approve and merge as you wish.


Error: Program type already present: com.google.flatbuffers.Constants

I get this error when i add the gradle dependency and run the project.
although sync works fine.
i have checked the dependency graph to know which lib is using flatbuffers that may getting conflict.
among my dependencies only object box is using flatbuffers.
i have commented out your dependency and checked the app,its working fine
so,somehow this library is causing problem with my dependencies ..
could you please help on this

cool,i fixed the issue.
the problem was because of duplicate dependencies in my gradle
i had object box which internally depended on flatbuffers,when i added this library it used to give me this error
after excluding it from the gradle configuration,i was able to run it


[ASK] How to return exception to function

I check the signature of function always return *v8go.Value and error, is it possible to return exception or how to trigger exception from function?

https://github.com/tommie/v8go/blob/v0.12.0/isolate.go#L154
Could i use this function?

You can use that, yes.
This fork makes it possible to, instead, return an error: https://pkg.go.dev/github.com/tommie/v8go#NewError
Like in this test:
https://github.com/tommie/v8go/blob/99f7408b99acc38b62a0b34ac33de4c53abc0070/function_template_test.go#L156-L158


If a certificate is provisioned with DNS-01 rather than HTTP-01 challenge, nginx still creates the HTTP-01 challenge endpoint

Describe the bug
Even though my certificates are provisioned using DNS-01 challenge, nginx still produces ./well-known/acme_challenge:
	server {
		listen <IP_ADDRESS>:80 ;
		listen [::0]:80 ;
		server_name example.com ;
		# Rule for legitimate ACME Challenge requests (like /.well-known/acme-challenge/xxxxxxxxx)
		# We use ^~ here, so that we don't check any regexes (which could
		# otherwise easily override this intended match accidentally).
		location ^~ /.well-known/acme-challenge/ {
			root /var/lib/acme/acme-challenge;
			auth_basic off;
		}
		location / {
			proxy_pass http://localhost:3255;
		}

(it's added for :443 as well)
https://github.com/NixOS/nixpkgs/blob/5521be288c7729e1653baddce52b8450dca1a4f1/nixos/modules/services/web-servers/nginx/default.nix#L365-L380
It is enabled when (vhost.enableACME || vhost.useACMEHost != null), but this is true for DNS-01 validation as well.
Steps To Reproduce
Steps to reproduce the behavior:

Setup security.acme.certs."example.com" with dnsProvider/credentialsFile as in 51.5. Configuring ACME for DNS Validation.
Create a nginx virtualhost for example.com with useACMEHost = "example.com"
Observe generated output.

Expected behavior
/.well-known/acme-challenge location in nginx is absent if DNS-01 verification is used.
Screenshots
n/a
Additional context
nil
Notify maintainers
@NixOS/acme
Metadata
(probably irrelevant, it's pushed with colmena)
 - system: `"aarch64-linux"`
 - host os: `Linux 6.1.27, NixOS, 23.11 (Tapir), 23.11pre489540.58c85835512`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.3`
 - channels(root): `"nixos-22.11"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Hey there - just to provide an update, this is effectively a clone of #210807 . The solution is to set the acmeRoot for your virtual host(s) to null, which will force disabling of the acme-challenge directory.
We may be able to add conditional logic for this in the future. Haven't quite worked out a non-breaking scenario yet but the conditional you quoted could potentially be extended to add a check for DNS-01.

Hmm, setting acmeRoot = null; only seems to remove the root /var/lib/acme/acme-challenge line from the nginx configuration, not the entire location {} block.
The DNS-01 challenge & provisioning does work -- this was mostly a (minor) bug report as the HTTP-01 path is needlessly generated in the nginx config.
(I am using a wildcard cert, and not using security.acme.defaults.XXX for setting dnsProvider settings.)


Translate docs/concepts/security/overview into Japanese

This is a Feature Request
What would you like to be added
Translate docs/concepts/security/overview into Japanese.
Why is this needed
This page has not been translated.
Comments
/language ja
/assign

/close


Updated broken doc links in readme.md and fixed some typos

[x] I have followed the Your First Code Contribution section of the Contributing guide

Summarize the changes made and the motivation behind them.
Updated broken doc links to working doc links and also fixed a typo.
Reference related issues using # followed by the issue number.
Fixes #1088
If there are breaking API changes - like adding or removing props, or changing the structure of the theme - describe them, and provide steps to update existing code.

Thank you


Add an InputSelector for the valid  attribute

Description
We had no selector for the valid attribute of the input states.
Proposed Changes

Added a InputSelector for the valid attribute that can be called like so:

InputSelectors.getIsValid(state, {id: 'the-input-id'});

Potential Breaking Changes
None
Acceptance Criteria

[x] The proposed changes are covered by unit tests
[x] The potential breaking changes are clearly identified
[x] README.md is adjusted to reflect the proposed changes (if relevant)

Codecov Report

Merging #1143 into master will decrease coverage by 57.33%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master   #1143       +/-   ##
==========================================
- Coverage   99.74%   42.4%   -57.34%
==========================================
  Files         350     350
  Lines        8521    8525        +4
  Branches     2023    2024        +1
==========================================
- Hits         8499    3615     -4884
- Misses         22    4910     +4888

Impacted Files
Coverage Δ

src/components/input/InputSelectors.ts
100% <100%> (ø)
:arrow_up:

src/components/drop/DomPositionCalculator.ts
8.82% <0%> (-91.18%)
:arrow_down:

...ropdownSearch/MultiSelectDropdownSearchReducer.tsx
12.82% <0%> (-87.18%)
:arrow_down:

...mponents/dropdownSearch/DropdownSearchReducers.tsx
15.34% <0%> (-83.6%)
:arrow_down:

...onents/partial-string-match/PartialStringMatch.tsx
17.07% <0%> (-82.93%)
:arrow_down:

src/components/chart/XYAxis.tsx
17.94% <0%> (-82.06%)
:arrow_down:

src/components/tables/TableDataModifier.ts
19.6% <0%> (-80.4%)
:arrow_down:

src/components/calendar/CalendarDay.tsx
22.58% <0%> (-77.42%)
:arrow_down:

...c/components/checkbox/GroupableCheckboxReducers.ts
20.83% <0%> (-77.09%)
:arrow_down:

src/components/datePicker/DatePickerReducers.ts
23.17% <0%> (-76.83%)
:arrow_down:

... and 287 more

Continue to review full report at Codecov.

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


Cluster Statistics Multi cluster problem

I have the following topo and a number of observations of the same

T_obs, clusters, cluster_pv, H0  = mne.stats.permutation_cluster_test(X, threshold=None, n_permutations=1024, tail=0,
                                   connectivity=connectivity, verbose=None, n_jobs=1, seed=None, max_step=1, exclude=None,
                                   step_down_p=0, t_power=1, out_type='mask', check_disjoint=False, buffer_size=1000)

This gives me only one cluster but from the topo we can see that there are two clusters.
What am I doing wrong here?

Is there a way to set max cluster size?

I wonder if the sensors on the right are close enough to be considered "neighbors" by the algorithm...?
No way to set max cluster size, but changing the preliminary threshold to be more restrictive will effectively shrink the cluster sizes because it will reduce the number of clusterable points.

Interesting. Do you know where was the algorithm obtained from?

It's a general algorithm, see e.g.  Maris/Oostenveld (2007), "Nonparametric statistical testing of EEG- and MEG-data" Journal of Neuroscience Methods, Vol. 164, No. 1., pp. 177-190. doi:10.1016/j.jneumeth.2007.03.024. You can set the connectivity however you like, can't remember who did our specific implementation for sensor space. You could try using git blame (or GitHub's equivalent) to figure it out if you're really curious.

I'm going to close this since the method seems to work properly as implemented.


Issue with latest Material Components Web

I've been trying to work my way through issues after upgrading to the latest @material/xxx components that are part of Material Components Web. There's a couple of work arounds they are suggesting to get their code to work which involves using the latest sass library and setting webpackImporter to false as part of the sass options. The problem seems to be this particular code...
@use "@material/button";
@include button.core-styles;

...more specifically the @include button.core-styles part.
I've tried messing around with the options in withStyles, but can't seem to get anything to work so I wanted to see if I'm missing something or if it may be time for some updates in this library. Here's what my current next.config looks like...
module.exports = withStyles({
    sass: true,
    modules: false,
    sassLoaderOptions: {
        sassOptions: {
            implementation: require('sass'), // this is currently v1.26.8
            webpackImporter: false,
            includePaths: [
                path.resolve(__dirname, 'node_modules'),
                path.resolve(__dirname, 'src/styles'),
            ],
        },
    },
    ignoreOrder: true,
    webpack: (config, {dev, isServer}) => {
        if (dev) {
            config.module.rules.push({
                enforce: 'pre',
                test: /\.js$/,
                exclude: /node_modules/,
                loader: 'eslint-loader',
            });
        }

        return config;
    },
});

This is the specific error I get...
./src/components/core/Button.scss
Error: Syntax error: Invalid CSS after "@include button": expected 1 selector or at-rule, was ".core-styles;"

  1 | @import '_mdc-theme';
  2 | @use "@material/button";
> 3 | @include button.core-styles;

Yay... I figured it out. I had some options in the wrong options. FWIW, here's what my next.config.js ended up looking like...
const withStyles = require('@webdeb/next-styles');
const path = require('path');

module.exports = withStyles({
    sass: true, // use .scss files
    modules: false,
    sassLoaderOptions: {
        implementation: require('sass'), // using sass v 1.26.8 for the MDC library
        webpackImporter: false, // needed for MDC library until a fix for Webpack is implemented
        sassOptions: {
            includePaths: [
                path.join(__dirname, 'node_modules'),
                path.join(__dirname, 'src/styles'),
            ],
        },
    },
    // cssLoaderOptions: {},
    // postcssLoaderOptions: {...},
    ignoreOrder: true, // for https://github.com/webpack-contrib/mini-css-extract-plugin/issues/250#issuecomment-544898772
    // miniCssExtractOptions: {
    //     filename: isDevMode() ? '[name].css' : '[name].[hash].css',
    //     chunkFilename: isDevMode() ? '[id].css' : '[id].[hash].css',
    // },

    webpack: (config, {dev, isServer}) => {
        if (dev) {
            config.module.rules.push({
                enforce: 'pre',
                test: /\.js$/,
                exclude: /node_modules/,
                loader: 'eslint-loader',
                options: {
                    // eslint options (if necessary)
                },
            });
        }

        return config;
    },
});


UI?

Planning to use UI based application for end user. So, no need to code and enhance UX. Currently, I plan to use Electron as we can get two benefits

Cross platform
Portable

Can we search by email id of sender ?

And UI will be great help. :1st_place_medal:

@attiq-khan Yes. You can search - https://github.com/munir131/attachment-downloader/blob/b96718a3f86b2067cb936a02df283f4ea7cf7880/index.js#L230
Yes. UI can help but I am not getting enough time to implement it

so index.js --email Id<EMAIL_ADDRESS>will download all attachments ?

@attiq-khan No. Just run node index.js, it will ask you for further option where you can mention email

Sure Thanks for quick reply :) I will check and let you know.
Thanks again for sharing this :)


⚠ AVS (kty) has degraded performance

In a4ef81f, AVS (kty) (https://avus.com.br) experienced degraded performance:

HTTP code: 200
Response time: 8165 ms

Resolved: AVS (kty) performance has improved in d134135.


Fix an 'opts:interface not defined' warning

Fix a remaining lv2 warning. Some change must have been lost in transit during the merging.
The plugin provides the options interface under all conditions; update extension data in order to reflect this.

I think I misread the commit diff before, anyway, thanks.


Support the Nest Detect motion & door sensors

Description
I still have a Nest Secure and some of Nest Detect door sensors which detect motion and door activity.  Do you believe support can be added for these?
I just skimmed the code and was wondering if they would be one of those other bucket types (ie quartz).
Device (optional)
No response
Additional information
No response

@broken did you already figure out how to add these? Are they supported in the Nest integration in core?

I'm in the same boat, it would be amazing to be able to use Nest Detects as presence/motion sensors


in memory limit

Ability to limit the in-memory events held in the 'events array', if the array is at 'capacity' new events will be dropped (not pushed onto the array).
Example Definition
interface Options {
  /**
   * Number of items to be held in memory.
   */
  memoryLimit?: number;
  ...
}

Example
const forEmitOf = require("../dist");
const { EventEmitter } = require("events");

async function main() {
  const emitter = new EventEmitter();

  const iterator = forEmitOf(emitter, {
    memoryLimit: 3,
  });

  emitter.emit("data", 1);
  emitter.emit("data", 2);
  emitter.emit("data", 3);
  emitter.emit("data", 4); // DISCARDED

  const first = await iterator.next();
  const second = await iterator.next();
  const third = await iterator.next();
  const forth = await iterator.next(); // null? 🤔
}

main();

What do you think about instead of memoryLimit the property being called queueLImit?

@Farenheith I like queueLImit makes more sense & thanks for clarifying my '🤔' was not sure the exact behavior.


gpu: Fix stretched mode with global premul alpha

This seems to work, but I can't figure out what the code I removed was supposed to do.

@dbolya If you would look at this that would be very helpful.


Support building NIO with CMake

Adds support for building NIO, packaging or installing its demo programs and running its integration tests with CMake.
Motivation:
Recently @compnerd announced Swift support for CMake. While CMake is a more complex build tool to use than Swift Package Manager, it has a few advantages that make it well-suited as an alternative for NIO. I figure a working PR is as good a place as any to start the conversation about adding another buildsystem to swift-nio. The places it shines are highlighted in this PR:

It supports installation of build products and generation of a number of package formats. This is useful to NIO, for example, you might want to package binaries of NIOPerformanceTester to deploy on a number of servers that you're evaluating.
It supports complex build automation with a number of custom steps. This is useful for NIO's integration tests, which devote a lot of space to building custom variants of NIO libraries with special build settings.
It makes embedding NIO into other CMake projects easier. This could be useful with https://github.com/apple/swift-corelibs-foundation, as that project already uses CMake.

Of course it's also worth pointing out its drawbacks:

Publication of the swift-nio package is much better supported by Swift Package Manager because of its declarative syntax, Semantic Versioning enforcement, and deep integration with tooling like Xcode.
CMake doesn't currently support running the unit tests under Tests due to lack of integration with XCTest.
Since NIO doesn't have a stable ABI, there's no point in using the library packaging support in CMake to package NIO - if you're using it as a library you will still want to depend on it with SwiftPM. The binary packaging support is still useful though, as you can distribute command-line tools like NIOPerformanceTester.
Since the Swift support in CMake is experimental it's subject to frequent breakage for a while.

Modifications:
Created a new CMake buildsystem (CMakeLists.txt). The NIO source code is unmodified with a couple of minor exceptions:

I created explicit module.modulemap files for each C library. Swift Package Manager generates these automatically.
I modified the HTTP1 integration tests to optionally skip building using SwiftPM when invoked by cmake (so that CMake+Ninja can take care of building the NIO binaries themselves).

Result:
You can build NIO with CMake's experimental Swift support.

@Lukasa / @yim-lee did we have a "generate CMake from Package.swift" script somewhere that we could use for NIO?

Crypto has the beginnings of one.

This PR is substantially out of date and there is currently no-one who needs the functionality, so for now we're going to drop this.


Checkpointer usage?

Hi,
Thanks for providing this great project.
I tried to train a model for separation task, but it didn't go well.
I prepared a small customized dataset and train conv-tasnet on it with /tests/integration/neural_networks/separation/example_conv_tasnet.py. (only rewrite "data_folder")
It just like the result shows in tutorials, but it can't save checkpoints and train log.
As I read in checkpointing in sb ckp and log should be saved automatically when output_folder is provided in yaml.
Did I misunderstand the usage of Checkpointer?

Hi
I fixed my problem. If we want to save the model, there are two things must do.

Make sure the hparams "checkpointer" in the .yaml file.
Make sure the functin "checkpointer.save_and_keep_only" used in valid stage. (it was written in train.py)


[SUPPORT] Poor Upsert Performance on COW table due to indexing

Hello, I am having performance issues when attempting to upsert data into a Hudi COW table. With the below specs it is taking longer than 4 hours to finish upserting (if it ever does finish). In the screenshots below, you can see that it is taking a long time doing the index scan. I have tried disabling hoodie.bloom.index.prune.by.ranges because our record key is random. I've also tried upserting using the "Simple" index type and did not see any performance improvements. Is there anything else I can do to improve the performance?

Specs:
Table Size: 13.6TB (compressed in S3)
Number of partitions: 1135 (hoodie.datasource.hive_sync.partition_fields=year,month)
Upsert dataset size:  68 million records, 6GB compressed
Index type: Default (Bloom)
Number of nodes: 30
Node type: r6g.8xlarge
Average record size: ~40 bytes (calculated by File Size/Num Records: 10MB/250000 records)
Environment Description

Hudi version : 0.9.0
Spark version : 2.4.8
EMR version: 5.34.0
Hive version : 2.38.0
Hadoop version : Amazon 2.10.1
Storage (HDFS/S3/GCS..) : S3

It is recommended that you upgrade to the latest version of hudi and use bucket index. Or try to use hbase index and MOR table formats in version 0.9.0

@scxwhite can you point me at some documentation on implementing bucket or hbase indexes?

You can see how to use these indexes in the official documents. If you want to know more about bucket index. Take a look at this document.

You can enable clustering to increase the file sizes. by default file sizes are of 120MB. but you can try to batch small files into larger ones (500Mb) and so during index lookup, the no of files to be looked up could reduce.

Hi
Can try https://hudi.apache.org/blog/2023/11/01/record-level-index/#metadata-table this stores the record_keys in metadata tables. But I am not sure if this indexing can be applied for COW tables.


Using the Same DNS Suffix as the Private DNS zone Leads to Fail Name Resolution.

There is a limitation when using the same private DNS zone as the DNS suffix for Container App in an Internal Container App Environment. The DNS suffix and the private DNS zone are two separate systems, leads to a failed name resolution issue from the Azure Container App.
For example,

A company has two existing private DNS zones contoso.com and contosofake.com

They configure DNS suffix for contoso.com

They can successfully resolve resources in the different private DNS zones within their contosofake.com private DNS zone from their vnet (including private endpoints and its records).
However, the issue arises when they use the same DNS zone as the DNS suffix.
For example:

o	They set contoso.com as the DNS suffix.
o	They create a record for fake.contoso.com that points to the IP address of a container app (e.g., <IP_ADDRESS>).
o	When they look up fake.contoso.com, it returns a different IP address (e.g., <IP_ADDRESS>).

ASK: Update the article to inform clients to either use a different private DNS zone or DNS suffix for the Container App Environment or remove the DNS suffix from the Container App Environment and use only the private DNS zone for the domain name resolution.

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

ID: a5860b4f-4445-bdb3-d15b-2fb80f34f269
Version Independent ID: 20b80909-9c8f-862a-c388-b25a2fda550f
Content: Custom environment DNS suffix in Azure Container Apps
Content Source: articles/container-apps/environment-custom-dns-suffix.md
Service: container-apps
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

@nelroosevelt
Thanks for your feedback! We will investigate and update as appropriate.

Thanks for your feedback and your contribution to Azure docs.
Feedback for this repository is moving away from GitHub to a system specific to the Microsoft Learn platform. Issues for this repository will soon be disabled, and additional comments from GitHub will no longer be possible. However, we are now tracking and triaging this issue in the new feedback system.
To learn more about our feedback systems, please see Provide feedback for Microsoft Learn content.
#please-close


Avalonia on Raspberry pi with Framebuffer - stuck

HI,
I created a very basic sample https://gitlab.com/dn-misc/AvaloniaRaspberryTest
trying to get Avalonia work on Raspberry PI with FrameBuffer.
I am trying to run it on Raspbian Buster
.Net Framework installed is 3.1.2
When running the project with --fbdev flag it is not generating any error but nothing appears or changes on the screen.
When running in GUI, Avalonia app shows up in window.
Any help how to troubleshoot or make it work.
Thanx,
D

Try to run it from a proper virtual console (the ones, accessible via Ctrl+Alt+F(1-12) with XOrg stopped

HI,
tried, but no luck,
tried running as root, but it just get's stuck, it does not try to initiate screen, just gets stuck in console.
Any way to log something to pinpoint issue ?
Thanx,
D

Try to fill framebuffer with garbage using cat /dev/urandom > /dev/fb0. You need to do that with an actual virtual console currently on the screen. Once you succeed with that, you should be able to run Avalonia app on the same terminal.

OK,
I am getting cat: write error: No space left on device
and snowy picture - mainly white background with random color pixels.
I am trying to run avalonia app after this and when run it clears this white showy screen and I get a clear console.
I made a video of test
https://youtu.be/-t_AjlL-Y4E
Regards,
D

Help,
Anyone

@kekekeks, can you plase check video I atrached to previous post, I am not sure what am I doing wrong, but still not able to run in framebuffer

Well, I don't have a raspberry device nearby, so I can only recommend running ControlCatalog with debugger attached and investigating what's going on in this file https://github.com/AvaloniaUI/Avalonia/blob/master/src/Linux/Avalonia.LinuxFramebuffer/Output/FbdevOutput.cs

@kekekeks I am now trying to use DRM as at least I am getting some feedback.
I installed kmscube and it is working ok.
when trying to run with --drm option I am getting following error
pi@minipi:~/avalonia $ dotnet exec AvaloniaTest1.dll --drm
Unhandled exception. System.ComponentModel.Win32Exception (0xFFFFFFFE): drmModeAddFb failed
   at Avalonia.LinuxFramebuffer.Output.DrmOutput.GetFbIdForBo(IntPtr bo)
   at Avalonia.LinuxFramebuffer.Output.DrmOutput.Init(DrmCard card, DrmResources resources, DrmConnector connector, DrmModeInfo modeInfo)
   at Avalonia.LinuxFramebuffer.Output.DrmOutput..ctor(String path)
   at LinuxFramebufferPlatformExtensions.StartLinuxDrm[T](T builder, String[] args, String card, Double scaling)
   at AvaloniaTest1.Program.Main(String[] args) in C:\Users\dino\source\repos\AvaloniaTest1\AvaloniaTest1\Program.cs:line 63
Aborted

this is where it all breaks in the code (from https://gitlab.com/dn-misc/AvaloniaRaspberryTest/-/blob/master/AvaloniaTest1/Program.cs)
            else if (args.Contains("--drm"))
            {
                SilenceConsole();
                return builder.StartLinuxDrm(args, scaling: GetScaling());
            }

There is a somewhat relevant patch for enabling DRM output on ARM devices - https://github.com/AvaloniaUI/Avalonia/pull/4049

@kekekeks I am using Avalonia 0.9.11 nugets, whish are dated from 4 days ago. I can see that "kekekeks merged commit 52701a0 into AvaloniaUI:master  on 31 May" so shoul'd it be already incorporated in these nugets?

@dinonovak that patch was merged to master, not to the 0.9.x maintenance branch

@kekekeks
Ok I now configured VS to use nightly nugets, so with --drm option i now am getting following error
Unhandled exception. System.EntryPointNotFoundException: Unable to find an entry point named 'sk_refcnt_safe_unref' in shared library 'libSkiaSharp'.
   at SkiaSharp.SkiaApi.sk_refcnt_safe_unref(IntPtr refcnt)
   at SkiaSharp.SKObjectExtensions.SafeUnRef(ISKReferenceCounted obj)
   at SkiaSharp.SKObject.DisposeNative()
   at SkiaSharp.SKNativeObject.Dispose(Boolean disposing)
   at SkiaSharp.SKObject.Dispose(Boolean disposing)
   at SkiaSharp.GRGlInterface.Dispose(Boolean disposing)
   at SkiaSharp.SKNativeObject.DisposeInternal()
   at SkiaSharp.SKNativeObject.Dispose()
   at Avalonia.Skia.GlSkiaGpu..ctor(IWindowingPlatformGlFeature gl, Nullable`1 maxResourceBytes)
   at Avalonia.Skia.PlatformRenderInterface..ctor(ISkiaGpu skiaGpu, Nullable`1 maxResourceBytes)
   at Avalonia.Skia.SkiaPlatform.Initialize(SkiaOptions options)
   at Avalonia.SkiaApplicationExtensions.<>c__0`1.<UseSkia>b__0_0()
   at Avalonia.Controls.AppBuilderBase`1.Setup()
   at Avalonia.Controls.AppBuilderBase`1.SetupWithLifetime(IApplicationLifetime lifetime)
   at LinuxFramebufferPlatformExtensions.StartLinuxDirect[T](T builder, String[] args, IOutputBackend backend)
   at LinuxFramebufferPlatformExtensions.StartLinuxDrm[T](T builder, String[] args, String card, Double scaling)
   at AvaloniaTest1.Program.Main(String[] args) in C:\Users\dino\source\repos\AvaloniaTest1\AvaloniaTest1\Program.cs:line 63

These are referenced nugets:

This is Program.cs
using System;
using System.Threading;
using System.Diagnostics;
using System.Globalization;
using System.Linq;
using Avalonia;
using Avalonia.Controls.ApplicationLifetimes;
//using Avalonia.Logging.Serilog;
using Avalonia.ReactiveUI;
using Avalonia.Dialogs;

namespace AvaloniaTest1
{
    class Program
    {
        // Initialization code. Don't use any Avalonia, third-party APIs or any
        // Avalonia configuration, don't remove; also used by visual designer.
        //public static AppBuilder BuildAvaloniaApp()
        //    => AppBuilder.Configure<App>()
        //        .UsePlatformDetect()
        //        .LogToDebug();

        // SynchronizationContext-reliant code before AppMain is called: things aren't initialized
        // yet and stuff might break.
        //public static void Main(string[] args) => BuildAvaloniaApp()
        //    .StartWithClassicDesktopLifetime(args);

        [STAThread]
        static int Main(string[] args)
        {
            if (args.Contains("--wait-for-attach"))
            {
                Console.WriteLine("Attach debugger and use 'Set next statement'");
                while (true)
                {
                    Thread.Sleep(100);
                    if (Debugger.IsAttached)
                        break;
                }
            }

            var builder = BuildAvaloniaApp();

            double GetScaling()
            {
                var idx = Array.IndexOf(args, "--scaling");
                if (idx != 0 && args.Length > idx + 1 &&
                    double.TryParse(args[idx + 1], NumberStyles.Any, CultureInfo.InvariantCulture, out var scaling))
                    return scaling;
                return 1;
            }
            if (args.Contains("--fbdev"))
            {
                Console.WriteLine(">> Run in Mode: Framebuffer");
                //SilenceConsole();
                return builder.StartLinuxFbDev(args, scaling: GetScaling());
            }
            else if (args.Contains("--drm"))
            {
                SilenceConsole();
                return builder.StartLinuxDrm(args, scaling: GetScaling());
            }
            else
                return builder.StartWithClassicDesktopLifetime(args);
                //return builder.StartLinuxFbDev(args, scaling: GetScaling());
        }

        /// <summary>
        /// This method is needed for IDE previewer infrastructure
        /// </summary>
        public static AppBuilder BuildAvaloniaApp()
            => AppBuilder.Configure<App>()
                .UsePlatformDetect()
                .LogToDebug()
                .With(new X11PlatformOptions
                {
                    EnableMultiTouch = true,
                    UseDBusMenu = true
                })
                .With(new Win32PlatformOptions
                {
                    EnableMultitouch = true,
                    AllowEglInitialization = true
                })
                .UseSkia()
                .UseReactiveUI()
                .UseManagedSystemDialogs();

        static void SilenceConsole()
        {
            new Thread(() =>
            {
                Console.CursorVisible = false;
                while (true)
                    Console.ReadKey(true);
            })
            { IsBackground = true }.Start();
        }
    }
}

SkiaSharp managed/native version mismatch. I think there is currently some work being done on providing an ARM build out of the box for SkiaSharp 2.80.
I think @ahopper has a pre-built Skia binary that works with the current master

This has all the info https://github.com/mono/SkiaSharp/pull/1382

@Gillibald do the builds here mono/SkiaSharp#1382 need https://github.com/AvaloniaUI/Avalonia/pull/4222 ? I convinced myself they did.  My builds for the current master can be extracted from the arm release here http://www.ihopper.org/radio/previews.htm you need libHarfBuzzSharp.so and libSkiaSharp.so . Hopefully that will be the last release with custom builds.

Hi all,
ok, now I am not getting any error at startup.
But still I am just getting blank screen. Is there anything that would need to be done to MainWindow.xaml to make it work under --drm option. With X Windows started app starts and window is displayed.
raspberry pi config.txt has following for framebuffer:
# uncomment to force a console size. By default it will be display's size minus
# overscan.
framebuffer_width=1280
framebuffer_height=720

[all]
dtoverlay=vc4-fkms-v3d

Here is MainWindow.xaml definition:
<Window xmlns="https://github.com/avaloniaui"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
        xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
        xmlns:local="clr-namespace:AvaloniaTest1"
        mc:Ignorable="d" d:DesignWidth="800" d:DesignHeight="600"
        x:Class="AvaloniaTest1.MainWindow"
        Title="AvaloniaTest1">
  <Panel>
    <local:MainView />
  </Panel>
</Window>

Try enabling "Full KMS" mode in raspberry pi options.

No luck, still blank screen with Full KMS enabled.

Having exactly the same behavior on Raspberry Pi 3 B+, Debian Stretch 9.8, .NET Core 3.1

simple NET Core 3.1 console app with this code works no matter whether I run it directly on Pi or over SSH console
so its not some kind of NET stuff.
using System;
using System.IO;

namespace ConsoleApp33
{
    class Program
    {
        static void Main(string[] args)
        {
            Console.CursorVisible = false;

            var ScreenWidth = 640;
            var ScreenHeight = 480;
            var BytesPerPixel = 2;

            var random = new Random();
            var buffer = new Byte[ScreenWidth * ScreenHeight * BytesPerPixel];

            using (var fb = new FileStream("/dev/fb0", FileMode.Open, FileAccess.ReadWrite, FileShare.ReadWrite))
            {
                random.NextBytes(buffer);
                fb.Write(buffer, 0, buffer.Length);
                fb.Close();
            }

            Console.WriteLine("Hello World!");
        }
    }
}

Hello, @dinonovak I had similar problem like the one you had at the beginning of this topic (running with --fbdev option)
I think I could share my solution here.
I had very similar issue - when running the app with StartLinuxFbDev I did not see anything except my console.
It looks like when running with StartLinuxFbDev we don't have IClassicDesktopStyleApplicationLifetime, but  ISingleViewApplicationLifetime
And in your code you're checking for IClassicDesktopStyleApplicationLifetime, you should check for  ISingleViewApplicationLifetime and assign your view to its MainView property:
https://gitlab.com/dn-misc/AvaloniaRaspberryTest/-/blob/c0918cc7a712ed2c45ff69225c3c888bbdf36b91/AvaloniaTest1/App.xaml.cs#L16

We should probably add some default content like "MainView is not set" message or something. It's confusing otherwise

For anyone struggling with framebuffers. MainView can not be inialized with Window it will result with Could not CreateWindow(): IWindowingPlatform is not registered Window has to be replaced with UserControl
Not obvious at all
if (ApplicationLifetime is ISingleViewApplicationLifetime single)
{
    single.MainView = new Window1(); // Could not CreateWindow(): IWindowingPlatform is not registered
}

if (ApplicationLifetime is ISingleViewApplicationLifetime single)
{
    single.MainView = new UserControl1(); // OK
}

I have the same issue as @dinonovak though my Win32Exception message says
drmModeSetCrtc failed
when running with --drm.
Running with --fbdev never displays a GUI. Running with neither shows it, but there's a flicker whenever anything is redrawn, e.g. on mouse-over buttons in the sidebar, etc. I also tried with AvaloniaEdit.Demo with similar results. So I think it's not the fault of ControlCatalog.NetCore.
Just for a proof of concept, I'm running ControlCatalog.NetCore built from master, on a DragonBoard 410c running the Linaro image provided for it on 96boards.org, linaro-sid-alip-dragonboard-410c-933 w/ .NET Core SDK 3.1.405

I have the same issue as @dinonovak though my Win32Exception message says
drmModeSetCrtc failed
when running with --drm.
Running with --fbdev never displays a GUI. Running with neither shows it, but there's a flicker whenever anything is redrawn, e.g. on mouse-over buttons in the sidebar, etc. I also tried with AvaloniaEdit.Demo with similar results. So I think it's not the fault of ControlCatalog.NetCore.
Just for a proof of concept, I'm running ControlCatalog.NetCore built from master, on a DragonBoard 410c running the Linaro image provided for it on 96boards.org, linaro-sid-alip-dragonboard-410c-933 w/ .NET Core SDK 3.1.405


Add option to use locked clocks instead of application clocks

Calling nvmlDeviceSetApplicationsClocks doesn't seem to affect the memory clock frequency that is used at runtime. An addition call to nvmlDeviceSetMemoryLockedClocks fixes this. A small typo in a comment has been fixed as well.
This was tested on a RTX A4000 GPU  with CUDA 11.5.1, driver version 495.29.05, and pynvml version 11.4.1.

Some more changes have been made to simplify the code. It has been tested both with application clocks (the default) and the newly added mode that uses locked clocks. The same platform as mentioned above is used, more testing is needed, since depending on the GPU model and/or driver version, some NVML features may (not) be available. This also fixes https://github.com/benvanwerkhoven/kernel_tuner/issues/153.
The current change-set has gone a bit beyond the scope of this PR, as the power limit code has for instance also been changed along with the code that controls GPU clocks.

Looks great @csbnw ! Thanks a lot!


fix Conv2d not registered in pytorch 1.0.1

Modify for the issue:
https://github.com/Lyken17/pytorch-OpCounter/commit/fdeec3ee4994b8ea419a103d6371ee6327b7824e#r33009849
This works in my enviroment ( pytorch 1.0.1.post2)

Thanks for the fix!


Add stored procedures and triggers

[To be written]

Pull Request Test Coverage Report for Build 325

-51 of 193 (73.58%)  changed or added relevant lines in 8 files are covered.
7 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-2.5%) to 82.994%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/khepri_app.erl
1
3
33.33%

src/khepri_tx.erl
19
21
90.48%

src/khepri_utils.erl
14
16
87.5%

src/khepri_event_handler.erl
14
20
70.0%

src/khepri_sproc.erl
9
15
60.0%

src/khepri.erl
4
12
33.33%

src/khepri_machine.erl
76
101
75.25%

Files with Coverage Reduction
New Missed Lines
%

src/khepri_machine.erl
7
86.07%

Totals

Change from base Build 309:
-2.5%

Covered Lines:
1386

Relevant Lines:
1670

💛  - Coveralls


rc and pod packed in deployments and added rbac

I have added a Deployment around the ReplicationController and the single pod. Also I added the RBAC rules to work correctly.

Signed the CLA
/assign @idvoretskyi


architecture doesn't have reference to the BinaryView

This will make certain arches possible - like dex smali.
I need to be able to access bv.session_data.string_table from the Architecture class.

I suspect there's another way around this -- we make Thumb2/Arm work without it, can you clarify a bit more about why you need session data from architecture?

In smali the instructions reference strings and methods using an table index
My current idea: save the table in SessionData, and access it that way.

I would also like to see this addressed; the primary motivation is so that Python-based plugins could use settings defined for a Resource to change their disassembly format.

I also have a use case for this, smali is a powerful IL that's used for jvm bytecode transformations and I've been working on jvm bytecode support for some time (on and off, work is crazy). It's quite simple to convert Dalvik and "Java bytecode" to smali and with this change (and a preprocessing step to perform the initial conversion), I believe both Dalvik classes and "Java" classes would be able to leverage the benefits of the different ILs offered (and it would be much more reasonable to do now that projects support has been added)

Hopefully this issue can be improved, as it greatly limits the flexibility of developing decompilation plugins for unknown instruction sets.

For a C166 architecture, this will allow proper decoding of sring references which are addressed in a specific bank context.

@xusheng6 suggested I weigh in here: I'd like to perform some limited instruction decoding (basically a limited linear sweep with no further analysis) to extract data from executable code in a flat binary file that references data needed to inform subsequent loading of the file.


[forwardport] Editing an existing vSphere node template does not populate correct values after upgrading to v2.3.3

Forwardport of rancher/rancher#23920

Available in latest2.

Tested in rancher\rancher:master-head version 781cd0fdc.
UI: latest2

Created vSphere node template in v2.3.3-rc4 w/ RancherOS
Created cluster
Upgraded Rancher to master-head
Edit previously created node template and all values load correctly
For values that do not map correctly, a warning is displayed and does not impact other fields


Docs within C extensions need to be updated

The docs within the extensions contain relevant info for the old API. All the extension functions need to be updated with the docs from the corresponding python wrapper.
The difference between the wrapper and the extension is that the extensions only accept string for a binfile (and not arrays, unlike the python wrappers). The return value always is a tuple with the results and time (unlike the python wrapper, which only returns a tuple if c_api_timer is set.

Fixed via d17a2c766fda93a6398a1f9be6e9a9f3757a3ab2


merge MONDO_0022263 'congenital hepatic fibrosis' with MONDO:0018840 'isolated congenital hepatic fibrosis'

From GARD:
Congenital Hepatic Fibrosis:  Orphanet has the term “isolated congenital hepatic fibrosis” while most sources (GR, GHR, Medscape, UpToDate, most relevant Pubmed articles) have congenital hepatic fibrosis.  I think we can change it to isolated congenital hepatic fibrosis because congenital hepatic fibrosis may occur alone (in which case it is called isolated congenital hepatic fibrosis). As per GHR: More frequently, it occurs as a feature of genetic syndromes that also affect the kidneys, such as polycystic kidney disease (PKD).

I am not sure if this exists.


Does not detect Oracle JDK 1.8.0_91

What happened:
Does not discover some Oracle Java installations. The path is not even mentioned in the generated syft-json output.
What you expected to happen:
Detect Oracle Java (for licence compliance survey)
Steps to reproduce the issue:
Java is installed on a server as part of an Oracle product (12cR2). I don't know how to reproduce that.
# ./syft --output syft-json --file myserver.sbom.syft.json \
> --exclude ./proc --exclude ./sys --exclude ./dev --exclude ./run \
> dir:/

jq '.artifacts[] | select(.name == "java") | {"name": .name, "cpes": .cpes, "paths": .locations | map(.path)}' myserver.sbom.syft.json

This shows a number of results for Java, but nothing inside /opt/oracle/product/12.2.0/
Grepping the SBoM for /opt/oracle/product/12.2.0/ shows plenty of results, but nothing with bin/java
Anything else we need to know?:
The Java 'release' file looks like the following:
# cat /opt/oracle/product/12.2.0/client_64/jdk/release
JAVA_VERSION="1.8.0_91"
OS_NAME="Linux"
OS_VERSION="2.6"
OS_ARCH="amd64"
SOURCE=" .:574417338118 corba:f8d0cfaa9900 deploy:533e20357a00 hotspot:fa8991ccf6e5 hotspot/make/closed:c0ee4cb5e8ee hotspot/src/closed:886b814d251d hotspot/test/closed:af7b7237cce4 install:d028e4e7f041 jaxp:f6bda5729ff8 jaxws:e71f424e2c96 jdk:f8725698a870 jdk/make/closed:68f13d0ff50a jdk/src/closed:2cb0fde09d2c jdk/test/closed:fa8356bd840f langtools:8921667c26ba nashorn:6296644a2c9c pubs:1cb5455f7c71 sponsors:c6134a642c3e"
BUILD_TYPE="commercial"

There is also a 32-bit version installed that wasn't detected.
# cat /opt/oracle/product/12.2.0/client_32/jdk/release
JAVA_VERSION="1.8.0_91"
OS_NAME="Linux"
OS_VERSION="2.6"
OS_ARCH="i586"
SOURCE=" .:574417338118 corba:f8d0cfaa9900 deploy:533e20357a00 hotspot:fa8991ccf6e5 hotspot/make/closed:c0ee4cb5e8ee hotspot/src/closed:886b814d251d hotspot/test/closed:af7b7237cce4 install:d028e4e7f041 jaxp:f6bda5729ff8 jaxws:e71f424e2c96 jdk:f8725698a870 jdk/make/closed:68f13d0ff50a jdk/src/closed:2cb0fde09d2c jdk/test/closed:fa8356bd840f langtools:8921667c26ba nashorn:6296644a2c9c pubs:1cb5455f7c71 sponsors:c6134a642c3e"
BUILD_TYPE="commercial"

Environment:

Output of syft version: syft 0.82.0
OS (e.g: cat /etc/os-release or similar): RHEL7.9

Hi @pythiankerr, can you attach the resulting SBOM and we can take a look to see what is has detected? The relevant binary detection mechanism is here:
https://github.com/anchore/syft/blob/1bd9de9047dcf83f83697be1e64848f26094fd6c/syft/pkg/cataloger/binary/default_classifiers.go#L90
We are looking for binaries called "java" and a particular version string within that binary, and for some reason it may not be matching the release you have deployed with Oracle. Having a look at the SBOM might help us figure out what, if anything, it is matching. Thanks!

Hi there, since we haven't heard back we'll go ahead and close this issue, but please feel free to re-open it with additional information if you are still having a problem. Thank you!


Add an example of a UICollectionView using PinLayout

Codecov Report

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

@@           Coverage Diff           @@
##           master      #94   +/-   ##
=======================================
  Coverage   89.51%   89.51%
=======================================
  Files          31       31
  Lines        5810     5810
=======================================
  Hits         5201     5201
  Misses        609      609

Continue to review full report at Codecov.

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


jedis.close() is not closing connection

Expected behavior
Write here what you're expecting ...
After using jedis.close() I was expecting jedis connection object to be null.
Write here what happens instead ...
It was available and i was able to connect to redis-server again with same connection object.
Steps to reproduce:
Below code can be used to reproduce steps :-
Jedis jedis = new Jedis("localhost");
   System.out.println("Connection to server sucessfully");

    jedis.lpush("tutorial-list", "Redis");
    jedis.lpush("tutorial-list", "Mongodb");
    jedis.lpush("tutorial-list", "Mysql");

    List<String> list = jedis.lrange("tutorial-list", 0, 5);

    for (int i = 0; i < list.size(); i++) {

        System.out.println("Stored string in redis:: " + list.get(i));
    }

// i closed connection here
jedis.close();
// trying to get list again
List list1 = jedis.lrange("tutorial-list", 0, 5);
    for (int i = 0; i < list1.size(); i++) {
    // this is printing valid values
        System.out.println("Stored string in redis1:: " + list1.get(i));
    }

Redis / Jedis Configuration
Jedis version:2.8.1
Redis version:redis_version:3.0.7
Java version: Java 8.

close closes the connection when using jedis in single instance mode. The thing is that if object is re-used, it will establish a new connection redis. This is how it works, you can use the isConnected method to check if a specified Jedis instance is connected to the server.


How to get IP address of current visitor in Helper

I tried using this approach but I get undefined as the value for the variable named clientIpAddress.
Meteor.methods({
    getClientIpAddress: function () {
        return this.connection.clientAddress;
    }
});

Template.home.helpers({
    starsAlreadyReceivedFromIpAddress: function () {
        var clientIpAddress;
        Meteor.call("getClientIpAddress", function(err, ipAddress) {
            clientIpAddress = ipAddress;
        });
        console.log(clientIpAddress);
        ....
    }
});

So I wanted to ask that if using this package I could get the current visitors IP address in the helper method.

Got it with Meteor.user().status.lastLogin.ipAddr

Using Meteor.user().status.lastLogin.ipAddr only works when the user is logged in. I am also using accounts-password package. So when the user is logged in I get their ip address using the code below, but not for users who are not logged. I would like to get the ip address of the visitor who are not logged in (like in the demo) the helper method
Meteor.user().status.lastLogin.ipAddr;

Using Meteor.user().status.lastLogin.ipAddr only works when the user is logged in. I am also using accounts-password package. So when the user is logged in I get their ip address using the code below, but not for users who are not logged. I would like to get the ip address of the visitor who are not logged in (like in the demo) the helper method
Meteor.user().status.lastLogin.ipAddr;

You will need to publish the current user's session information to the client. The demo publishes everyone, but you will want to publish by session ID.

@mizzao Thanks for the reply back, it worked out great. Have a nice day :+1:


Component hangs at startup if monitor server down

If a backend component (e.g. broker) has a monitor server in its configuration that is down (e.g. NOC), the component will be stuck in a loop retrying to connect to the monitor during startup. Since the initial connection to the monitors is made synchronously and before the gRPC server is started, the backend component will remain unavailable the entire time.
As far as I understand, monitors are not part of the primary process of the backend. It seems therefore that components should be able to start independently of whether the configured monitor servers are up or down.
Not really a big issue, but it does introduce some (unnecessary?) brittleness. Any thoughts on this @johanstokking @htdvisser ?

Yes, components should start in any case, even if monitors are down on start.


Add support for waiting-children

BullMQ flows have a waiting-children type of job.
This is a first step into having better support for flows, as discussed in: https://github.com/felixmosh/bull-board/issues/277
This PR adds a new tab for the waiting-children jobs, as well as the button to delete them, individually:

I have tested it manually and everything works. But I'm lost as to where/how I should add tests for the changes in this PR. Please let me know how that should be done...

I am currently looking for a way to visualize the parent/child relationship so its pretty cool to see this.
A view of the aggregated child jobs of a flow would be ideal for my use case.

Feel free to reopen if still relevant

Better to show waiting-children jobs without dependencies, than not showing job with children until it finishes.
If one of children job stuck or fail, parent job won't be visible at all.
As partial fix we could show them in waiting tab, maybe with asterisk or some symbol.
According to the docs, deleting parent job will automatically delete its children.


We should download only tested 'latest-release' of rules

Description
Currently, we build the container with the rules from master branch. We should download only tested latest-release ref.
Fixes # (issue)
Type of change

Refactor (refactoring code, removing useless files)

Testing steps
Tested locally with:
buildah bud --build-arg GITHUB_API_TOKEN=token -f Dockerfile -t ics .

Codecov Report

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

@@           Coverage Diff           @@
##           master      #98   +/-   ##
=======================================
  Coverage   73.00%   73.00%
=======================================
  Files           9        9
  Lines         363      363
=======================================
  Hits          265      265
  Misses         79       79
  Partials       19       19

Continue to review full report at Codecov.

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


[Zephyr 1.14] drivers: flash: spi_nor: Problematic write with page boundaries

Describe the bug
The driver is known to have an issue when the size of the chunk to be written is bigger than the page boundaries. It is fixed for the later versions of Zephyr through https://github.com/zephyrproject-rtos/zephyr/pull/17691 and https://github.com/zephyrproject-rtos/zephyr/pull/17994, but not for Zephyr v1.14.
In my opinion https://github.com/zephyrproject-rtos/zephyr/pull/17994 should be backported as a whole.
This issue has been created to backport the needed fixes in v1.14.
The needed commits are:

fde373313a24eaae25562c816babc6d0e2e0c23a
ef62bf3c47ed285de60f50f2ab9da9a53072d1b0
7501968027501df489146443e98be4f7c86a411b

To Reproduce
Write an application that writes at unaligned page addresses.
Expected behavior
The driver should handle correctly writes across page boundaries.
Impact
Showstopper
Screenshots or console output
Environment (please complete the following information):

OS: GNU/Linux
Toolchain: Zephyr SDK
v1.14-branch

@pabigot Here you are.

Fixed in 1.14.1


Cache assets locally to enable working offline

@mk I think this PR is ready for another review. A brief explanation:

There is a function clojure -X nextjournal.clerk/cache-assets! you can call if you're on the wifi of the airport.
After that, all development can happen without an internet connection
All assets are served through the /assets endpoint. If they weren't previously cached via clojure -X nextjournal.clerk/cache-assets! they will still be cached locally, so in case you forgot to run that function, but already developed, then you will have those files locally anyway.
When adding assets, these need to be added in the bb script and the bb task hash-assets needs to be ran to update resources/asset_manifest.edn.

@borkdude one thing I forgot to mention on our call is if we can incorporate our learnings from https://github.com/nextjournal/dejavu/issues/4 here.

@mk Isn't that automatically solved when using the new dejavu?

@mk I think all things have been addressed that we discussed yesterday. I will ask in #30 if people want to test this PR.

It does work well for me once I requested a notebook when online. When only calling nextjournal.clerk/cache-assets! without ever serving a notebook, we seem to be missing a bunch of files however:
$ ls .clerk/.cache/*/*
.clerk/.cache/assets/36q3Vv52BMdq6KArT8NxBBcm5xXwGTQ4tXkFwjKDkSZx8TJL47KhhHDadZkLVLZSqXGuSLeoL9Mm1Em87cusoqVN?name=tailwind.css
.clerk/.cache/assets/3uEQGQ9cBUjLVQBay2VqQsMkT8RmYjctuV356d82PSAH8qX7eQsXXC4FXzSz3K3YSWFs9ZVw2fBdBZD3r8oeCYBj?name=Fira+Code.css
.clerk/.cache/lookup/3fXMVxKEk34PRw2hKjU7NRy9o5vJ

After showing a notebook on the first request, they're there:
ls .clerk/.cache/*/*
.clerk/.cache/assets/2wrujFq9FbBNiC7dyA6ESW9vvp5Nx3EstRjvfZwpy1Ra1PHW1hdVc5sXwhp4rJF9Xksu1R3BaPgQEevvx8acCKZu
.clerk/.cache/assets/36q3Vv52BMdq6KArT8NxBBcm5xXwGTQ4tXkFwjKDkSZx8TJL47KhhHDadZkLVLZSqXGuSLeoL9Mm1Em87cusoqVN
.clerk/.cache/assets/36q3Vv52BMdq6KArT8NxBBcm5xXwGTQ4tXkFwjKDkSZx8TJL47KhhHDadZkLVLZSqXGuSLeoL9Mm1Em87cusoqVN?name=tailwind.css
.clerk/.cache/assets/3UUKLrYWC5yYHepSePNSjneRgKkeupqXVR9Qu5sMRh31S6nJDmAusn1AP9r9hzoX4zPQNzDF59iPnNykSiNjt9fA
.clerk/.cache/assets/3uEQGQ9cBUjLVQBay2VqQsMkT8RmYjctuV356d82PSAH8qX7eQsXXC4FXzSz3K3YSWFs9ZVw2fBdBZD3r8oeCYBj
.clerk/.cache/assets/3uEQGQ9cBUjLVQBay2VqQsMkT8RmYjctuV356d82PSAH8qX7eQsXXC4FXzSz3K3YSWFs9ZVw2fBdBZD3r8oeCYBj?name=Fira+Code.css
.clerk/.cache/assets/4R867PoGjDfokDKtsdXkQymyqPFFjMecXgkaoGGbKssw9CScH28Ro8soEXyEJVF9YPh4p1oB6EGXcEbvu5QrxRTb
.clerk/.cache/assets/4dy4nMTjQ9by3rB5rb8jroM3FvUqLm2Dboqent2P43MAyntTD1wkUCBAjNzHMCpybgyMrMhN1sjXkGsdkao3uTKF
.clerk/.cache/lookup/3fXMVxKEk34PRw2hKjU7NRy9o5vJ

Another thing I'm noticing is that the css files exist with and without the ?name param:
36q3Vv52BMdq6KArT8NxBBcm5xXwGTQ4tXkFwjKDkSZx8TJL47KhhHDadZkLVLZSqXGuSLeoL9Mm1Em87cusoqVN
36q3Vv52BMdq6KArT8NxBBcm5xXwGTQ4tXkFwjKDkSZx8TJL47KhhHDadZkLVLZSqXGuSLeoL9Mm1Em87cusoqVN?name=tailwind.css
3uEQGQ9cBUjLVQBay2VqQsMkT8RmYjctuV356d82PSAH8qX7eQsXXC4FXzSz3K3YSWFs9ZVw2fBdBZD3r8oeCYBj
3uEQGQ9cBUjLVQBay2VqQsMkT8RmYjctuV356d82PSAH8qX7eQsXXC4FXzSz3K3YSWFs9ZVw2fBdBZD3r8oeCYBj?name=Fira+Code.css

Also noticing now that we're serving assets with a content-type of application/octet-stream:
$ curl -I "https://storage.googleapis.com/nextjournal-cas-eu/data/3uEQGQ9cBUjLVQBay2VqQsMkT8RmYjctuV356d82PSAH8qX7eQsXXC4FXzSz3K3YSWFs9ZVw2fBdBZD3r8oeCYBj?name=Fira+Code.css"
HTTP/2 200
x-guploader-uploadid: ADPycdvvRcwz-TQ0DS1GieFWn7QRMCnyNXk1_XDBjWRX_iINMr0AOhkQ4A0_eMKyjhxuzrh5W5GWhVf-2i8ZNQ0Dqu0Xw0uq6g
x-goog-generation:<PHONE_NUMBER>505151
x-goog-metageneration: 1
x-goog-stored-content-encoding: identity
x-goog-stored-content-length: 3792
content-language: en
x-goog-hash: crc32c=DvM9AQ==
x-goog-hash: md5=gImMytMCOi6K6vf3N9ScIA==
x-goog-storage-class: STANDARD
accept-ranges: bytes
content-length: 3792
server: UploadServer
date: Wed, 30 Mar 2022 06:24:12 GMT
expires: Wed, 30 Mar 2022 07:24:12 GMT
cache-control: public, max-age=3600
last-modified: Wed, 23 Mar 2022 11:04:31 GMT
etag: "80898ccad3023a2e8aeaf7f737d49c20"
content-type: application/octet-stream
age: 2134
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"

TODO:

[x] store cached files in a different directory, so they don't get wiped
[ ] solve merge conflicts
[ ] only two files get cached when you run cache-assets!

@mk See above TODOs, most should be solved. About vega/plotly, I see this is coming from viewers:
borkdude@MBP2019 ~/dev/viewers (main) $ rg "vega-embed"
resources/css/viewer.css
349:.vega-embed .chart-wrapper { @apply h-auto !important; }

modules/ui/src/nextjournal/ui/components/d3_require.cljs
22: [with {:package<EMAIL_ADDRESS>
modules/viewer/src/nextjournal/viewer/vega_lite.cljs
8:    [d3-require/with {:package<EMAIL_ADDRESS>
Is it realistic/expected that caching should take into account dynamically loaded assets? Any ideas how to approach that?

@borkdude Just tried this out locally and the fonts were missing (i.e. the CSS referred to fonts that were not served via /assets).  Were they missing as in a cache miss or did they not load at all?

@borkdude I tried the latest commit in this branch. The fonts did not load at all.

Thanks for testing. I'll take a look after my vacation (the week after next week).

@joe-loco Can you please specify which notebook you were viewing?

I think it was the Rule 30 one but I also believe I looked at multiple and the issues were everywhere (I might be wrong about that last part though).

@joe-loco I stared at this for too long. I even preserved the names of the fonts in the CSS in this commit and don't see anything loading from external sources, except the katex.min.css which we decided to leave external for now. Yet the font doesn't render as it normally does.

The CSS is loaded from here:
http://localhost:7777/assets/36rHBCKZuQoGayvSbwoGsc4RKUf3zSe58S6etnk6EgCBLfEsBsNpRXnPMiUjP3EekgSDY4kxaaxqzu7P9jiXL8k4?name=Fira+Code.css
and looks like this:
@font-face {
  font-family: 'Fira Code';
  font-style: normal;
  font-weight: 400;
  font-display: swap;
  src: url(/assets/uU9eCBsR6Z2vfE9aq3bL0fxyUs4tcw4W_D1sFVc.ttf) format('truetype');
}
@font-face {
  font-family: 'Fira Code';
  font-style: normal;
  font-weight: 700;
  font-display: swap;
  src: url(/assets/uU9eCBsR6Z2vfE9aq3bL0fxyUs4tcw4W_NprFVc.ttf) format('truetype');
}
@font-face {
  font-family: 'Fira Mono';
  font-style: normal;
  font-weight: 400;
  font-display: swap;
  src: url(/assets/N0bX2SlFPv1weGeLZDtQIQ.ttf) format('truetype');
}
@font-face {
  font-family: 'Fira Mono';
  font-style: normal;
  font-weight: 700;
  font-display: swap;
  src: url(/assets/N0bS2SlFPv1weGeLZDtondv3mQ.ttf) format('truetype');
}
@font-face {
  font-family: 'Fira Sans';
  font-style: italic;
  font-weight: 400;
  font-display: swap;
  src: url(/assets/va9C4kDNxMZdWfMOD5VvkojO.ttf) format('truetype');
}
@font-face {
  font-family: 'Fira Sans';
  font-style: italic;
  font-weight: 500;
  font-display: swap;
  src: url(/assets/va9f4kDNxMZdWfMOD5VvkrA6Qhf_.ttf) format('truetype');
}
@font-face {
  font-family: 'Fira Sans';
  font-style: italic;
  font-weight: 700;
  font-display: swap;
  src: url(/assets/va9f4kDNxMZdWfMOD5VvkrByRBf_.ttf) format('truetype');
}
@font-face {
  font-family: 'Fira Sans';
  font-style: normal;
  font-weight: 400;
  font-display: swap;
  src: url(/assets/va9E4kDNxMZdWfMOD5VfkA.ttf) format('truetype');
}
@font-face {
  font-family: 'Fira Sans';
  font-style: normal;
  font-weight: 500;
  font-display: swap;
  src: url(/assets/va9B4kDNxMZdWfMOD5VnZKvuQQ.ttf) format('truetype');
}
@font-face {
  font-family: 'Fira Sans';
  font-style: normal;
  font-weight: 700;
  font-display: swap;
  src: url(/assets/va9B4kDNxMZdWfMOD5VnLK3uQQ.ttf) format('truetype');
}
@font-face {
  font-family: 'Fira Sans Condensed';
  font-style: italic;
  font-weight: 700;
  font-display: swap;
  src: url(/assets/wEOuEADFm8hSaQTFG18FErVhsC9x-tarUfPVFMZ0dw.ttf) format('truetype');
}
@font-face {
  font-family: 'Fira Sans Condensed';
  font-style: normal;
  font-weight: 700;
  font-display: swap;
  src: url(/assets/wEOsEADFm8hSaQTFG18FErVhsC9x-tarWU3IiMM.ttf) format('truetype');
}
@font-face {
  font-family: 'PT Serif';
  font-style: italic;
  font-weight: 400;
  font-display: swap;
  src: url(/assets/EJRTQgYoZZY2vCFuvAFTzro.ttf) format('truetype');
}
@font-face {
  font-family: 'PT Serif';
  font-style: italic;
  font-weight: 700;
  font-display: swap;
  src: url(/assets/EJRQQgYoZZY2vCFuvAFT9gaQVy4.ttf) format('truetype');
}
@font-face {
  font-family: 'PT Serif';
  font-style: normal;
  font-weight: 400;
  font-display: swap;
  src: url(/assets/EJRVQgYoZZY2vCFuvDFR.ttf) format('truetype');
}
@font-face {
  font-family: 'PT Serif';
  font-style: normal;
  font-weight: 700;
  font-display: swap;
  src: url(/assets/EJRSQgYoZZY2vCFuvAnt65qV.ttf) format('truetype');
}

It seems even when adding an incorrect URL in the CSS, I don't see a 404 anywhere (xassets instead of assets) in my browser.

Also the server isn't really hit with these urls it seems, else exception would be logged.

When I save the CSS locally as foo.css and make an index.html like:

    <link rel="stylesheet" href="foo.css">

Hello

then I'm able to see an error. Why am I not seeing a single error in the clerk context?

When correcting xassets back to assets the 404s are gone. So it seems the fonts are being loaded. Then why am I not seeing those fonts being rendered?

@joe-loco @mk I finally (sorry it took me so long) found the remaining issue with those fonts: binary files were downloaded and stored as text, which explains the difference in byte size. Can you give this another go?
In the branch:

rm -rf .clerk/assets (to ensure you're starting from scratch)
clojure -X nextjournal.clerk/cache-assets! to pre-download all necessary assets (before hopping on airplane)
Then develop as usual, you should be able to do this without an internet connection

I tried this out (018bdd534cf820fe529ba65cfec912a062684ab1), and it's not working for me on Linux (Pop! OS 22.04, based on Ubuntu 22.04) with either Clojure 1.10.3 or Clojure 1.11.1:

Online, it gives me the error: "unusable viewer: :clerk/notebook".
Offline, the page is empty and I get a console error nextjournal is not defined.

Whether offline or online, Firefox is also complaining that downloadable fonts being rejected by the sanitizer. Chromium gives a similar issue, but says that "Size of decompressed WOFF 2.0 is less than compressed size"

@alysbrooks Can you specify all steps you did to try this out? Did you run clojure -X nextjournal.clerk/cache-assets!? Which notebook were you viewing? Etc.
Thanks for trying this out!

 Here's what I tried:

Set my clerk dependency to 018bdd534cf820fe529ba65cfec912a062684ab1
Ran rm -rf .clerk/assets
Ran clojure -X nextjournal.clerk/cache-assets!

It doesn't seem to depend on the notebook. The error happens when I just call clerk/serve!, it happens on my own notebooks, and it happens on a variety of the official demo notebooks, including readme.clj and markdown.clj.
The error seems to be occurring between evaluation and the browser rendering it. I get the "clerk rendered" message in my out when I evaluate clerk/show!. Also, when I tried to open one of the official demo notebooks that I don't have the correct dependencies for, it shows a stacktrace with FileNotFoundException
I can provide my whole deps.edn if that would help?

@alysbrooks If your code happens to be open source, you could maybe push a branch I could check out locally? That would be super helpful.

@borkdude It's not open source because I haven't bothered to make it into a proper repository yet.
Actually, while I was trying to make a minimal reproduction, it stopped happening. A lot of the files I excluded aren't necessary for me and were leftovers from cloning the clerk repository, so it might not be an issue for my actual use.

Here's the repository that reproduces the issue: https://github.com/alysbrooks/Clerk-Issue-Reproduction. It seems to be the resources/ directory, which I took from the clerk main repository.

Thanks. I'll take a look next Monday probably.

Thanks! With the resources/ directory moved elsewhere, it works just fine both offline and online, except for the font error.

@alysbrooks Sorry, didn't get to it this week. @mk and I are still figuring out the best solution by either using this PR, using a ServiceWorker or both.

Since we learned that in corporate environments PCs are often locked-down so the JVM isn't even allowed to access the internet, we'll probably revisit offline work using a service worker or bundling the assets inside the jar. The upside of a service worker would be that it is a general solution for the jar and when consumed as a git-dep but it's more complex to implement.


Convert unsupported key type exception to a log line

Greetings! Coming at you from #153!
In KeyDB.php, there's a @todo in addKey() https://github.com/php-tuf/php-tuf/blob/main/src/KeyDB.php#L137 that says:
        if (! in_array($keyMeta['keytype'], self::getSupportedKeyTypes(), true)) {
            // @todo Convert this to a log line as per Python.
            throw new \Exception("Root metadata file contains an unsupported key type: \"${keyMeta['keytype']}\"");
        }

So... we should do that. :)

So we never did finalize how we wanted to do error handling. The pro of using exceptions is that there is an explicit failure; the con is that we have to then also catch the exceptions in calling code or it introduces its own sort of attack (trigger an exception, halt the update). But I think we would want to change that everywhere, not just this one method?
If we do use an exception, it should also have a more specific type as per #61 .


Minor Road labels Question

Where can I go to get some help with the YAML style? I have a cinnabar YAML that I've modified but I can't seem to get the minor roads to show up with a zoom level less than 14 (i.e. 13, 12). Sorry for making a new issue....I'm new here and not sure where to ask for help. Is there a slack channel or something else for this kind of thing? Below is what I've set for minor road labels but I'm not able to get labels to show at zoom 13.
labels-minor_road:                 filter: { $zoom: [13,14,15,16,17] }                 draw:                     text-blend-order:                         priority: 59                         visible: global.text_visible_minor_road_e                         #text_source: name                         font:                             fill: global.text_fill_road_e                             size: 10px                             stroke: { color: global.text_stroke_road4, width: 2 }                 labels-minor_road-z13:                     filter: { $zoom: [13] }                     draw:                         text-blend-order:                             font:                                 size: 10px                                 stroke: { color: global.text_stroke_road4, width: 2 }                 labels-minor_road-z14:                     filter: { $zoom: [14] }                     draw:                         text-blend-order:                             font:                                 size: 12px                                 stroke: { color: global.text_stroke_road4, width: 3 }

I can't seem to get the minor roads to show up with a zoom level less than 14 (i.e. 13, 12)

Does the vector source you're using have the roads at those zooms?

Well I guess I'm not sure. I'm using tangram and mapzen's service (just like the cinnabar repo).

Hi Ken,
While minor road geometries are shown earlier, their names aren’t included
in Mapzen Vector Tiles until zoom 14:

https://mapzen.com/documentation/vector-tiles/layers/#roads-transportation

This is done to decrease file size and improve performance.
But there is a delicate balance between minor roads in cities which aren’t
significant, and minor roads in rural areas that actually are significant
(and should be labeled). If you have some specific examples you can note,
please file an issue in this repo:

https://github.com/tilezen/vector-datasource/issues/new

Cheers,
_Nathaniel
On Fri, Apr 14, 2017 at 2:48 PM, Ken Frey<EMAIL_ADDRESS>wrote:

Well I guess I'm not sure. I'm using tangram and mapzen's service (just
like the cinnabar repo).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tangrams/tangram/issues/546#issuecomment-294243227,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0EO2ys3j0XjkPMmBUOtLwcICOVOpdoks5rv-m-gaJpZM4M-G21
.

I think this question is answered, so closing the issue, feel free to reopen or open a new one with additional question details.


Send build output to stdout and retain formatting

This patch fixes it so that any elm compilation errors are formatted correctly (using correct colours, etc) instead of logging the entire message as an error (all formatted with red text).

I don't know how long this is expected to take but I wonder if it would be better to merge this for now rather than postponing it in favour of a better solution that may or may not actually happen?

@TechnoTone I just talked with Feldman, and he said he'd be open for a PR for this issue to node-elm-compiler.

Ok, I'll take a look at node-elm-compiler to see what I can do. I had previously raised a PR in that project (99) for this but my change was crude and broke existing behaviour so I closed it and came up with this instead.


Multiple screens - Kap doesn't record from the chosen screen

This is a bit of an edge-case.  ;-)
// OSX 10.12
// 1 x GeForce dual-head PCI card
// 1 x internal graphics
I have three screens connected, I launch Kap from my main screen, move the recording-marquee to screen 2 where I want to record content and begin recording in Kap.
The recording actually captures content from screen 1 and not where my selection marquee is (on screen 2)

#33 😄

Aha!  :-)  Thanks Matheus.

On 19 Oct 2016, at 10:22, Matheus Fernandes<EMAIL_ADDRESS>wrote:
#33 https://github.com/wulkano/kap/issues/33 😄
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/wulkano/kap/issues/57#issuecomment-254760448, or mute the thread https://github.com/notifications/unsubscribe-auth/AL-eadLdmyzaor8GHl9J8gCt8yspxE7bks5q1eFqgaJpZM4Kavhu.


Update switching-endpoints.md

Fixed some Python errors and formats.

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

#sign-off


Build visualize  not working as mentioned in Doc

Describe the problem that you experienced
Angular Build Stats Json
Enter the URL of the topic with the problem
https://angular.io/cli/build
Describe what you were looking for in the documentation

Describe the actions that led you to experience the problem
Stats genentration had a issue since build analyzer consider as invalid format
Describe what you want to experience that would fix the problem
No response
Add a screenshot if that helps illustrate the problem
After uploading stats.json file

If this problem caused an exception or error, please paste it here
No response
If the problem is browser-specific, please specify the device, OS, browser, and version
No response
Provide any additional information here in as much as detail as you can
No response

I'm transfering this as this content is generated from the CLI repo.

@JeanMeche, the generated documents are accurate, however we must establish a clearer method for documenting Angular CLI commands, particularly as ng build may differ depending on whether webpack, esbuild, or ng-packagr builders are utilized. Therefore, I propose that the most suitable location for this clarification is within the framework repository. This will ensure that the docs team can prioritize this task appropriately.