Update scalafmt-core to 3.5.8

Updates org.scalameta:scalafmt-core from 3.5.0 to 3.5.8.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scalameta", artifactId = "scalafmt-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:n:3

Codecov Report

Merging #307 (f22248c) into master (405ea71) will decrease coverage by 0.95%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #307      +/-   ##
==========================================
- Coverage   96.19%   95.23%   -0.96%
==========================================
  Files           4        4
  Lines         105      105
  Branches        4        6       +2
==========================================
- Hits          101      100       -1
- Misses          4        5       +1

Impacted Files
Coverage Δ

src/main/scala/io/circe/yaml/Printer.scala
98.03% <0.00%> (-1.97%)
:arrow_down:

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 405ea71...f22248c. Read the comment docs.

Superseded by #314.


smtweb cannot show project page when the project name contains spaces

This is how to reproduce:
{{{
smt init "Project with spaces"
smtweb
}}}
http://<IP_ADDRESS>:8000/ shows:
{{{
List of projects
No projects found
}}}
http://<IP_ADDRESS>:8000/Project with spaces/ raises Page not found (404) error.
Imported from Bitbucket issue 77,  created by tkf on 06-17-2011 at 08:42, last modified: 06-22-2011 at 15:03

Projects are not saved to the record store until they contain at least one record. In other words, smtweb does not show empty projects.
If you do an smt run, then http://<IP_ADDRESS>:8000/ will show "Project with spaces".
The second part of this ticket (404 error for "Project with spaces" is indeed a bug.
Trac comment by apdavison on 06-22-2011 at 13:50

fixed in r246
Trac comment by apdavison on 06-22-2011 at 15:03


version update slf4j

update version of slf4j in Titan to match TP3.1 version
built.  ran test cases.

Merged into titan11, thanks.


Machin specification for evaluation of BOP benchmark

Hello, thank you for the great work. I am trying to compare the methods on the BOP benchmark from the time perspective. It would be very beneficial if you could shape the machine specification you have used to evaluate the BOP benchmark's datasets. Thank you very much

The experiments are conducted on an RTX A5000 GPU (24GB CUDA Memory).

Thank you very much @YoungSean.

Done


⚠ ClamAV has degraded performance

In 4f1e87b, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 104 ms

Resolved: ClamAV performance has improved in fea5ed7.


signalr javascript snippet reverted

@Rick-Anderson  edit: Internal review url
@Rick-Anderson @BrennanConroy snippet reverted. But the information in this section is wrong. Please apply a fix for it. Thanks 🙌

I thought the aspnetcore/signalr/javascript-client.md was fixed. The problem with the last PR was you had a stale branch to work with.

Actually, the problem was that the snippet in the sample was updated to,
connection.onclose(function (error) {
        if (error) {
            console.log(`Connection closed with error: ${error}`);
        } else {
            console.log("Connection closed.");
        }
    });

But the doc was not updated for some reason. This section needs to be changed as the information doesn't match with the snippet,

The following code demonstrates a typical manual reconnection approach:

A function (in this case, the start function) is created to start the connection.
Call the start function in the connection's onclose event handler.

async function start() {
    try {
        await connection.start();
        console.log("SignalR Connected.");
    } catch (err) {
        console.log(err);
        setTimeout(start, 5000);
    }
};

connection.onclose(function (error) {
        if (error) {
            console.log(`Connection closed with error: ${error}`);
        } else {
            console.log("Connection closed.");
        }
    });

But the information in this section is wrong.

Oh I think I see what happened. The PR that changed the sample, just changed the sample code without regard for the doc page that was using it for the manual reconnect section.
So I think you fixed it in https://github.com/dotnet/AspNetCore.Docs/pull/22826. We should probably keep it as is in main currently. Sorry for the extra work 😄

No problem. The doc has a mixture of hard-coded snippets and reference snippets from the sample, hence the confusion. 😸


Update community icons index.md

KubeSphere and Kubernetes are the opposite positions, correct them.

Thanks, the zh version has the same issue, could you handle it?

Can they in the same PR?

Sure, all right.

done


HEADER_SEARCH_PATHS concatenation issue

New Version
0.72.6
Old Version
0.70.5
Build Target(s)
iOS simulator
Output of react-native info
System:
OS: macOS 14.1.1
CPU: (10) arm64 Apple M1 Pro
Memory: 812.52 MB / 32.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 16.14.0
path: ~/.nvm/versions/node/v16.14.0/bin/node
Yarn:
version: 1.22.21
path: ../node_modules/.bin/yarn
npm:
version: 8.3.1
path: ~/.nvm/versions/node/v16.14.0/bin/npm
Watchman: Not Found
Managers:
CocoaPods:
version: 1.14.3
path: /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 23.0
- iOS 17.0
- macOS 14.0
- tvOS 17.0
- watchOS 10.0
Android SDK:
API Levels:
- "26"
- "28"
- "29"
- "30"
- "31"
- "32"
- "33"
- "34"
- "34"
Build Tools:
- 28.0.3
- 29.0.2
- 30.0.2
- 30.0.3
- 31.0.0
- 32.0.0
- 32.1.0
- 33.0.0
- 34.0.0
System Images:
- android-30 | Intel x86_64 Atom
- android-30 | Google APIs Intel x86 Atom
- android-32 | Google APIs ARM 64 v8a
- android-32 | Google Play ARM 64 v8a
- android-33 | Google APIs ARM 64 v8a
- android-33 | Google Play ARM 64 v8a
- android-34 | Google Play ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: 2022.3 AI-223.8836.35.2231.11090377
Xcode:
version: 15.0.1/15A507
path: /usr/bin/xcodebuild
Languages:
Java:
version: 11.0.21
path: ../.jenv/shims/javac
Ruby:
version: 2.6.10
path: /usr/bin/ruby
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.72.6
wanted: 0.72.6
react-native-macos: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: true
newArchEnabled: false
Issue and Reproduction Steps
After upgrading to the new version, we also upgraded our RNFirebase module which requires Cocoapods to use framework.
As a result of these changes, whenever I run pod install, I see new changes in my Xcode HEADER_SEARCH_PATHS.
It seems that you are concatenating the search paths with the previous ones. Probably in this script.

Hi @hamidhadi, thanks for the report.
I'll look into it.
What is the pod that is getting multiple HEADER_SEARCH_PATHS?
The link you added refers to a function called get_react_codegen_spec that we use internally to create the React-Codegen podspec on the flight.
So it is regenerated at every pod install, and therefore the search_path should not concatenate. I suspect for the issue to happen in some other podspec.

PSA: I'll be on PTO from tomorrow until the 12th of December.

I'm experiencing the same issue (most probably after updating to React Native 0.73.0, but we've also bumped other dependencies).
				HEADER_SEARCH_PATHS = (
					"$(inherited)",
					"${PODS_CONFIGURATION_BUILD_DIR}/ReactCommon-Samples/ReactCommon_Samples.framework/Headers",
					"${PODS_CONFIGURATION_BUILD_DIR}/ReactCommon/ReactCommon.framework/Headers/react/nativemodule/core",
					"${PODS_CONFIGURATION_BUILD_DIR}/ReactCommon-Samples/ReactCommon_Samples.framework/Headers/platform/ios",
					"${PODS_CONFIGURATION_BUILD_DIR}/React-NativeModulesApple/React_NativeModulesApple.framework/Headers",
					"${PODS_CONFIGURATION_BUILD_DIR}/React-graphics/React_graphics.framework/Headers/react/renderer/graphics/platform/ios",
					" ${PODS_CONFIGURATION_BUILD_DIR}/ReactCommon/ReactCommon.framework/Headers",
					" ${PODS_CONFIGURATION_BUILD_DIR}/React-Fabric/React_Fabric.framework/Headers/react/renderer/components/view/platform/cxx",
					" ${PODS_CONFIGURATION_BUILD_DIR}/React-graphics/React_graphics.framework/Headers",
					" ${PODS_CONFIGURATION_BUILD_DIR}/ReactCommon/ReactCommon.framework/Headers",
					" ${PODS_CONFIGURATION_BUILD_DIR}/React-Fabric/React_Fabric.framework/Headers/react/renderer/components/view/platform/cxx",
					" ${PODS_CONFIGURATION_BUILD_DIR}/React-graphics/React_graphics.framework/Headers",
					" ${PODS_CONFIGURATION_BUILD_DIR}/ReactCommon/ReactCommon.framework/Headers",
					" ${PODS_CONFIGURATION_BUILD_DIR}/React-Fabric/React_Fabric.framework/Headers/react/renderer/components/view/platform/cxx",
					" ${PODS_CONFIGURATION_BUILD_DIR}/React-graphics/React_graphics.framework/Headers",
+					" ${PODS_CONFIGURATION_BUILD_DIR}/ReactCommon/ReactCommon.framework/Headers",
+					" ${PODS_CONFIGURATION_BUILD_DIR}/React-Fabric/React_Fabric.framework/Headers/react/renderer/components/view/platform/cxx",
+					" ${PODS_CONFIGURATION_BUILD_DIR}/React-graphics/React_graphics.framework/Headers",
				);

This concatenation happens in every configuration (Debug, Release) after running pod install.

@annuh Could you share on which target it is happening? Could any of you prepare a repro using https://github.com/react-native-community/reproducer-react-native? Otherwise it is really hard for me to help you out, because I am not able to reproduce this behavior locally.

@cipolleschi I've created a reproducer here: https://github.com/annuh/reproducer-react-native.
I believe it's related to an old/correct installation of RN Firebase, since I fixed the issue by reinstalling the Firebase library.
The HEADER_SEARCH_PATHS in my original ./ios/AwesomeProject.xcodeproj/project.pbxproj contained this:
HEADER_SEARCH_PATHS = (
   "$(inherited)",
   "${PODS_CONFIGURATION_BUILD_DIR}/ReactCommon-Samples/ReactCommon_Samples.framework/Headers",
   "${PODS_CONFIGURATION_BUILD_DIR}/ReactCommon/ReactCommon.framework/Headers/react/nativemodule/core",
   "${PODS_CONFIGURATION_BUILD_DIR}/ReactCommon-Samples/ReactCommon_Samples.framework/Headers/platform/ios",
   "${PODS_CONFIGURATION_BUILD_DIR}/React-NativeModulesApple/React_NativeModulesApple.framework/Headers",
   "${PODS_CONFIGURATION_BUILD_DIR}/React-graphics/React_graphics.framework/Headers/react/renderer/graphics/platform/ios",
);

This happened after a pod install:
HEADER_SEARCH_PATHS = (
   "$(inherited)",
   "${PODS_CONFIGURATION_BUILD_DIR}/ReactCommon-Samples/ReactCommon_Samples.framework/Headers",
   "${PODS_CONFIGURATION_BUILD_DIR}/ReactCommon/ReactCommon.framework/Headers/react/nativemodule/core",
   "${PODS_CONFIGURATION_BUILD_DIR}/ReactCommon-Samples/ReactCommon_Samples.framework/Headers/platform/ios",
   "${PODS_CONFIGURATION_BUILD_DIR}/React-NativeModulesApple/React_NativeModulesApple.framework/Headers",
   "${PODS_CONFIGURATION_BUILD_DIR}/React-graphics/React_graphics.framework/Headers/react/renderer/graphics/platform/ios",
+   " ${PODS_CONFIGURATION_BUILD_DIR}/ReactCommon/ReactCommon.framework/Headers",
+   " ${PODS_CONFIGURATION_BUILD_DIR}/React-Fabric/React_Fabric.framework/Headers/react/renderer/components/view/platform/cxx",
+   " ${PODS_CONFIGURATION_BUILD_DIR}/React-graphics/React_graphics.framework/Headers",
);

However, when I reinstalled RN Firebase completely in a new project, the HEADER_SEARCH_PATHS contained this:
HEADER_SEARCH_PATHS = (
   "$(inherited)",
   "${PODS_CONFIGURATION_BUILD_DIR}/ReactCommon/ReactCommon.framework/Headers", #
   "${PODS_CONFIGURATION_BUILD_DIR}/ReactCommon/ReactCommon.framework/Headers/react/nativemodule/core",
   "${PODS_CONFIGURATION_BUILD_DIR}/ReactCommon-Samples/ReactCommon_Samples.framework/Headers",
   "${PODS_CONFIGURATION_BUILD_DIR}/ReactCommon-Samples/ReactCommon_Samples.framework/Headers/platform/ios",
   "${PODS_CONFIGURATION_BUILD_DIR}/React-Fabric/React_Fabric.framework/Headers/react/renderer/components/view/platform/cxx", #
   "${PODS_CONFIGURATION_BUILD_DIR}/React-NativeModulesApple/React_NativeModulesApple.framework/Headers",
   "${PODS_CONFIGURATION_BUILD_DIR}/React-graphics/React_graphics.framework/Headers", #
   "${PODS_CONFIGURATION_BUILD_DIR}/React-graphics/React_graphics.framework/Headers/react/renderer/graphics/platform/ios",

So a pod install added all the 'missing'(?) folders, which is probably correct 🙂
The problem is that it adds these lines with a trailing   (whitespace), so these folders are added after every pod install.

I experience the concatenation since upgrading to react-native 0.73.2.
After every pod install the following lines are added to my project:
" ${PODS_CONFIGURATION_BUILD_DIR}/ReactCommon/ReactCommon.framework/Headers",
" ${PODS_CONFIGURATION_BUILD_DIR}/React-Fabric/React_Fabric.framework/Headers/react/renderer/components/view/platform/cxx",
" ${PODS_CONFIGURATION_BUILD_DIR}/React-graphics/React_graphics.framework/Headers",

Are these repeated multiple times? Because it is expected for you to have these 3 new lines.
If they are repeated, try to run:
bundle exec pod deintegrate to cleanup the Pod structure and then rerun:
bundle eexec pod install to reinstall it.

Yes there are repeated.
It seems that pod deintegrate fixed it! Thanks!

Had the same issue after updating react-native from v0.72.6 to v.073.2. The only thing that prevented subsequent install pods steps from adding the same 3 lines again was to manually edit the project.pbxproj file and remove the empty spaces added at the beginning of each of the 3 lines.

Despite upgrading react-native-firebase as per @annuh’s suggestion, I still encountered the issue of duplicated concatenation and white space prefix at HEADER_SEARCH_PATHS.

Despite upgrading react-native-firebase as per @annuh’s suggestion, I still encountered the issue of duplicated concatenation and white space prefix at HEADER_SEARCH_PATHS.
My current workaround:

[ ] Run pod deintegrate to resolve duplicated concatenation issue.
[ ] Then remove white space prefix at HEADER_SEARCH_PATHS

I noticed that these lines start with spaces. I removed spaces and it helped. 🎉

Removing the spaces is definitely going to fix it, it is better though to replace the HEADER_SEARCH_PATHS with
HEADER_SEARCH_PATHS = (
	"$(inherited)",
);

then run pod install in the ios directory, this will generate the correct paths again, for some reason pod deintegrate doesn't do this

I'm guessing that maybe this commits to make this behaviour happens: https://github.com/facebook/react-native/commit/fa6f170658723acffcac0102386c8efcd37f121e#diff-2bd8393b331d124e068c72072334b0d49cc9aea43828f768b36c5dc25576b4c7
I'm using use_frameworks! :linkage => :static for my build target in my Podfile, and I checked the added lines in my pbxproj file after run pod install and find out this is the most possible commit to make the HEADER_SEARCH_PATHS concatenated.
In line 281, the script will generate the header search paths then use self.add_search_path_if_not_included to concat our HEADER_SEARCH_PATHS, and in the definition of self.add_search_path_if_not_included in utils.rb, I see it will add a whitespace prefix if the search path not included.

As the function to check the search path without the whitespace prefix, so the checking will be always true in this case, this will let the script will add the 'not exists' search path into our pbxproj file each pod install run time.

Removing the spaces is definitely going to fix it, it is better though to replace the HEADER_SEARCH_PATHS with
HEADER_SEARCH_PATHS = (
"$(inherited)",
);

then run pod install in the ios directory, this will generate the correct paths again, for some reason pod deintegrate doesn't do this

This doesn't change a thing here. pod install will re-add the paths.

@pke, yes but this time it would not contain duplicates or white-spaces, that's just a solution for not editing the pbxproj file manually

I created a PR to fix this issue, before I saw this issue. It's indeed caused by an extra space when the scripts adds entries to HEADER_SEARCH_PATHS, see https://github.com/facebook/react-native/pull/46262

Fixed in the release candidate v0.76

It seems fixed for me after completely deleting HEADER_SEARCH_PATHS and running pod install. The new HEADER_SEARCH_PATHS are regenerated from scratch, and there are no duplicates anymore after the second pod install


data: project addition by akshaykamath45

Related Issue
Add your projects to ProjectsHut  #141
Description
This is a Google Clone application built with React JS. It replicates the functionality of the Google search engine, providing a home page, search component, and search results page.
Features

Home Page: The application displays a home page similar to the Google search page, with a search bar and buttons.
Search Component: Users can enter search queries in the search bar and click the search button to initiate a search.
Search Page: The application displays search results instantly without refreshing the page, providing a list of search results with page titles, snippets, and links.

Screenshots

Home Page

Search Page

add your issue number, not mines after that we can merge this PR

this branch has a conflicts error. Please resolve it


Update the SSMSKeymap extension to 1.0.0

This updates the SSMSKeymap extension to 1.0.0. This has updated README contents to reference Azure Data Studio and adds 1 additional keybinding for Refresh Intellisense Cache

@kburtram - I will leave this to you for merging since you control the extension gallery releases. If this looks good please merge when suitable. Thanks!

@kevcunnane I'll push extension updates this afternoon.


Add webjars support

would be nice to have either direct slupport for webjars or a rife2 plugin for it

Any war deployed in a servlet container that support servlet spec 3 or later will implicitly support webjars. We just added support for webjars to the embedded jetty server and are looking at doing the same with tomcat.


Clarify if Android installation required in 0.65 now that it's released.

From INSTALL.md:
// TODO: Remove all of this when MMKV and Reanimated can be autoinstalled (maybe RN 0.65)

Unfortunately RN 0.65 doesn't fix this yet.


Add support for 'Implicit Grant Flow'

This pull request add support for the 'Implicit Grant Flow' to support users that want to build fully client-side apps.
It implements the protocol as defined by spotify

Coverage remained the same at 89.091% when pulling 7433993be55e58d67ad37a1236f3a05ad6734db2 on noahp78:master into 37a78656198185776ca825b37e2de4a31c2ae5de on thelinmichael:master.

Any update here? Can this be merged? Thanks

Thanks @noahp78! Better late than never? I changed the PR somewhat to accept a response_type argument instead, similar to the API.


Add new script to retrieve chains info from Viem

Closes #1268

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 93.545%

Totals

Change from base Build<PHONE_NUMBER>2:
0.01%

Covered Lines:
8782

Relevant Lines:
9388

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 93.545%

Totals

Change from base Build<PHONE_NUMBER>2:
0.01%

Covered Lines:
8782

Relevant Lines:
9388

💛  - Coveralls


[firefox] Add 112

https://www.mozilla.org/en-US/firefox/112.0/releasenotes/

What do you think of my comment #2705 (comment)

Now with #2594 in place we can think about also listing the older unmaintained versions, e.g. 110, 109, etc.

I agree with you. It seems there is usually 13 releases between two ESR releases, so the release list on endoflife.date would be at most 16-17 releases (let's say 20), which looks OK to me.

In this case I would keep the 111 cycle and mark it as eol on the release date of 112 cycle. In new issue/pr we can add the older cycles back again.

I suggest we merge this PR as it is and create a new issue to handle the work of adding all releases. Would it be OK if we handle things like that ?

I suggest we merge this PR as it is and create a new issue to handle the work of adding all releases. Would it be OK if we handle things like that ?

Yes that is okay for me. I'll merge this one.


Update readme, add usage for namespaced model [ci skip]

@anilmaurya hey, thank you for the pull request but that's how rails's form_for works for not sure we need to duplicate it in the README: http://guides.rubyonrails.org/form_helpers.html#dealing-with-namespaces


Folding akd_mysql, integration_tests, and akd_test_tools into examples

This moves all of the code from akd_mysql, integration_tests, and akd_test_tools into the examples directory.
Now, we have three utilities in the examples/ directory: whatsapp_kt_auditor, mysql_demo, and fixture_generator

Codecov Report
Patch coverage: 87.96% and project coverage change: -10.68 :warning:

Comparison is base (f2d8a96) 79.49% compared to head (d97156e) 68.81%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff             @@
##             main     #386       +/-   ##
===========================================
- Coverage   79.49%   68.81%   -10.68%
===========================================
  Files          45       58       +13
  Lines        9649    11834     +2185
===========================================
+ Hits         7670     8143      +473
- Misses       1979     3691     +1712

Impacted Files
Coverage Δ

akd/src/storage/transaction.rs
60.24% <ø> (+2.18%)
:arrow_up:

...es/src/fixture_generator/examples/example_tests.rs
91.42% <ø> (ø)

examples/src/fixture_generator/generator.rs
80.00% <0.00%> (ø)

examples/src/fixture_generator/parser.rs
6.66% <ø> (ø)

examples/src/fixture_generator/reader/mod.rs
14.28% <ø> (ø)

examples/src/fixture_generator/reader/tests.rs
100.00% <ø> (ø)

examples/src/fixture_generator/reader/yaml.rs
92.53% <ø> (ø)

examples/src/fixture_generator/writer/yaml.rs
100.00% <ø> (ø)

examples/src/mysql_demo/mod.rs
0.00% <ø> (ø)

examples/src/mysql_demo/mysql.rs
4.71% <ø> (ø)

... and 7 more

... and 4 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


server chassis issues in containers - regression for 2.2 & master

Configuring cocoMDS1...
   ... configuring the platform the server will run on...
   ...... (POST https://lab-dev:9443/open-metadata/admin-services/users/garygeeke/servers/cocoMDS1/server-url-root?url=https://lab-datalake:9443 )
---------------------------------------------------------------------------
JSONDecodeError                           Traceback (most recent call last)
<ipython-input-11-3a3bd59f8553> in <module>
      7 print("Configuring " + mdrServerName + "...")
      8
----> 9 configurePlatformURL(adminPlatformURL, adminUserId, mdrServerName, mdrServerPlatform)
     10 configureMaxPageSize(adminPlatformURL, adminUserId, mdrServerName, maxPageSize)
     11 clearServerType(adminPlatformURL, adminUserId, mdrServerName)

<ipython-input-3-82e673aa31dc> in configurePlatformURL(adminPlatformURL, adminUserId, serverName, serverPlatform)
    156     print("   ... configuring the platform the server will run on...")
    157     url = adminCommandURLRoot + serverName + '/server-url-root?url=' + serverPlatform
--> 158     postAndPrintResult(url)
    159
    160 def configureMaxPageSize(adminPlatformURL, adminUserId, serverName, maxPageSize):

<ipython-input-3-82e673aa31dc> in postAndPrintResult(url, json, headers)
    150     print("   ...... (POST", url, ")")
    151     response = requests.post(url, json=json, headers=headers)
--> 152     print("   ...... Response: ", response.json())
    153
    154 def configurePlatformURL(adminPlatformURL, adminUserId, serverName, serverPlatform):

/opt/conda/lib/python3.8/site-packages/requests/models.py in json(self, **kwargs)
    896                     # used.
    897                     pass
--> 898         return complexjson.loads(self.text, **kwargs)
    899
    900     @property

/opt/conda/lib/python3.8/json/__init__.py in loads(s, cls, object_hook, parse_float, parse_int, parse_constant, object_pairs_hook, **kw)
    355             parse_int is None and parse_float is None and
    356             parse_constant is None and object_pairs_hook is None and not kw):
--> 357         return _default_decoder.decode(s)
    358     if cls is None:
    359         cls = JSONDecoder

/opt/conda/lib/python3.8/json/decoder.py in decode(self, s, _w)
    335
    336         """
--> 337         obj, end = self.raw_decode(s, idx=_w(s, 0).end())
    338         end = _w(s, end).end()
    339         if end != len(s):

/opt/conda/lib/python3.8/json/decoder.py in raw_decode(self, s, idx)
    353             obj, end = self.scan_once(s, idx)
    354         except StopIteration as err:
--> 355             raise JSONDecodeError("Expecting value", s, err.value) from None
    356         return obj, end

JSONDecodeError: Expecting value: line 1 column 1 (char 0)

This is in the containers
... investigating

This fails in a container, but works ok locally.
Suspect there is an issue with the docker image.

jonesn:egeria/ (egeria-release-2.2) $ http --verify=no POST https://<IP_ADDRESS>:30082/open-metadata/admin-services/users/garygeeke/servers/cocoMDS1/server-url-root\?url\=https://lab-datalake:9443
HTTP/1.1 401
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Connection: keep-alive
Content-Length: 0
Date: Fri, 28 Aug 2020 09:54:34 GMT
Expires: 0
Keep-Alive: timeout=60
Pragma: no-cache
Set-Cookie: JSESSIONID=D90FA88B1E4E2F58B9F44E312264D985; Path=/; Secure; HttpOnly
Strict-Transport-Security: max-age=31536000 ; includeSubDomains
WWW-Authenticate: Basic realm="Realm"
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-XSS-Protection: 1; mode=block

jonesn:egeria/ (egeria-release-2.2) $ http --verify=no POST https://localhost:9445/open-metadata/admin-services/users/garygeeke/servers/cocoMDS1/server-url-root\?url\=https://lab-datalake:9443
HTTP/1.1 200
Connection: keep-alive
Content-Type: application/json
Date: Fri, 28 Aug 2020 09:54:46 GMT
Keep-Alive: timeout=60
Transfer-Encoding: chunked

{
    "class": "VoidResponse",
    "relatedHTTPCode": 200
}

Interestingly on the same platform, an attempt to get to the REST api docs (swagger) at https://<IP_ADDRESS>:30080/swagger-ui.html results in:

Meanwhile swagger locally is also failing - not found? (odd):

Somehow the image running in k8s appears to have security enabled. This looks like the default spring security challenge.

Problem located.....
Egeria fails once LOADER_PATH is set to include the 'lib' directory of dependencies.
As noted when we did the assembly, we pull in ALL dependencies for all modules in the assembly due to deficiencies in the plugin. Clearly one of more of these dependencies is being pulled into the classpath and affecting the chassis configuration severely
The challenge now is how to address.
Reverting the assembly change to use uber jars is possible, but brings it's own challenges
Switching to gradle may offer more flexibility, but there's a lot to do first
Revisiting our strategy for dynamic loading may be needed
Ad-hoc stripting to manipulate the assembly pos-creation may be possible, but very tricky tro do without being platform specific. Maybe the groovy plugin could help.
Will consider best short term and long term fix
cc: @mandy-chessell

Interestingly on the same platform, an attempt to get to the REST api docs (swagger) at https://<IP_ADDRESS>:30080/swagger-ui.html results in:

Swagger UI work only with this url https://localhost:9444/swagger-ui/index.html?configUrl=/v3/api-docs/swagger-config#/
I dont know why this is such. Such work after 1.8.

Yes I was aware of that - mentioned swagger above. Unfortunately :-(
I plan to look at this tomorrow (it's a public holiday today in uk)  - the cause was a change to packaging which is bringing in some additional things in the classpath which are changing the behaviour of spring security amongst other things.

Made a change to drop the additional dependencies - as this is a one line change
The impact of this is

discovery notebook will fail
Dynamically loadable additional connectors will fail

However it would get people working again with containers.
If this helps, I will look at pushing a PR .... and then looking at better fixes.

The graph repo tests completed successfully.


Support yaml format for configuration files

This has been brought up several times by members in the community and is simple enough to support

Support for yaml configuration was released in v0.4.0


Unable to restore saves after 11.1 downgrade system transfer

Hi,
I was setting up a friends New 3ds and used the downgrade method to transfer my CFW old3ds onto his new 3ds. I followed through with the rest of the steps and it worked successfully, but I noticed his old save files wouldn't load. I have looked on various websites and it seems like his save files are encrypted in the /Nintendo 3DS/ sub folders underneath the 00040000 folder in a .sav file. Is there anyway to restore them or am I truly out of luck since I didn't use a save manger to decrypt and backup his save file? I only have a backup of his SD card before the hack and post system transfer.
Thank you!

If there isn't a NAND backup to go with those encrypted files, you're truly out of luck, sorry.


(Suggestion) a button that makes the chat box disappear

good idea, will add

What's the benefit of hiding the chat? I don't understand

@Agent-11 it would be nice to record stuff without it.

@Agent-11 it would be nice to record stuff without it.

I see

yeah and it kinda gets annoying to see people arguing/fighting in chat, whereas the point of sm64js is to just play online and not twitter so enabling/disabling chat would be cool


Reported ionosctl version

Description
When using a beta version, the reported version doesn't include the beta suffix.
Expected behavior
ionosctl --version should print the whole version. Otherwise people may think they are using 6.0.0.
How to Reproduce
[fischerman@falcon ~ ]$ curl -sL https://github.com/ionos-cloud/ionosctl/releases/download/v6.0.0-beta.3/ionosctl-6.0.0-beta.3-linux-amd64.tar.gz | tar -xzv
ionosctl
[fischerman@falcon ~ ]$ ./ionosctl --version
ionosctl version 6.0.0

Cheers!


check ca errors only for cloud provider errors

Related issue: https://github.com/giantswarm/giantswarm/issues/25286
Proposal to make this alert less noisy:
We only include Cloud Provider Errors (my most favourite ones), which only checks for things like:

Failing to get node group info
Failing to set node group size
...

And we exclude errors

Internal errors
API call errors (K8s API Server)

Those should be covered by other alerts.

Related issue: giantswarm/roadmap#1855
Proposal to make this alert less noisy:
We only include Cloud Provider Errors (my most favourite ones), which only checks for things like:

Failing to get node group info
Failing to set node group size
...

And we exclude errors

Internal errors
API call errors (K8s API Server)

Those should be covered by other alerts.

not sure. I still think we should alert on the outcome, not the process. I'm ok with any number of errors connecting to the cloud provider's API as long as the cluster is not needing any more/less node. See what I mean?

As discussed I added 2 more alerts
cluster_autoscaler_unneeded_nodes_count - checks if cluster is able to scale in, if not there's something fishy and we need to check
cluster_autoscaler_unschedulable_pods_count - checks if pods can be scheduled or stuck in "Pending"
We need to check if this get's too noisy and if the checks are helpful.


OSX/Darwin build

hey, I would love to use these neat Grafana dashboards, but being an osx person I would prefer I could do some of the development on my Mac. I understand that mdf-iter is binary only, but any chances you can share darwin M1 builds?

I'm afraid we're only supporting Windows/Linux - but you can deploy the writer on e.g. AWS Lambda in which case it does not have to run on your Mac


Docs

Im interested in this, is this a completed version or is it still under development?

https://localstellars.algobasket.com/


UPLC panic on sort_by

What Git revision are you using?
831a37d0947944e22e1c3565a8d92dadf0e10812
What operating system are you using, and which version?

[x] Linux / Ubuntu

Describe what the problem is?
The following code ends up with UPLC panic: (https://github.com/aiken-lang/stdlib/pull/4/files)
pub fn sort_by(xs: List<a>, f: fn(a, a) -> Int) -> List<a> {
  do_merge_all(do_sequences(xs, f), f)
}

test sort_by_1() {
  let xs = [4, 3, 2, 1]
  sort_by(xs, fn(a, b) { a - b }) == [1, 2, 3, 4]
}

fn do_sequences(xs: List<a>, f: fn(a, a) -> Int) -> List<List<a>> {
  when xs is {
    [x, y, ..rest] ->
      if f(x, y) > 0 {
        do_descending(y, [x], rest, f)
      } else {
        do_ascending(y, [x], rest, f)
      }
    xs -> [xs]
  }
}

fn do_descending(
  x: a,
  xs: List<a>,
  rest: List<a>,
  f: fn(a, a) -> Int,
) -> List<List<a>> {
  let [y, ..ys] = rest
  if f(x, y) > 0 {
    do_descending(y, [x, ..xs], ys, f)
  } else {
    [[x, ..xs], ..do_sequences(rest, f)]
  }
}

fn do_ascending(
  x: a,
  xs: List<a>,
  rest: List<a>,
  f: fn(a, a) -> Int,
) -> List<List<a>> {
  let [y, ..ys] = rest
  if f(x, y) <= 0 {
    do_ascending(y, concat(xs, [x]), ys, f)
  } else {
    [concat(xs, [x]), ..do_sequences(rest, f)]
  }
}

fn do_merge(xs: List<a>, ys: List<a>, f: fn(a, a) -> Int) -> List<a> {
  when [xs, ys] is {
    [[], ys] -> ys
    [xs, []] -> xs
    [[x, ..xs2], [y, ..ys2]] ->
      if f(x, y) > 0 {
        [y, ..do_merge(xs, ys2, f)]
      } else {
        [x, ..do_merge(xs2, ys, f)]
      }
  }
}

fn do_merge_pairs(xs: List<List<a>>, f: fn(a, a) -> Int) -> List<List<a>> {
  when xs is {
    [x, y, ..rest] -> [do_merge(x, y, f), ..do_merge_pairs(rest, f)]
    xs -> xs
  }
}

fn do_merge_all(xs: List<List<a>>, f: fn(a, a) -> Int) -> List<a> {
  when xs is {
    [x] -> x
    xs -> do_merge_all(do_merge_pairs(xs, f), f)
  }
}

Compilation ends with the following error:
Error:
  × Main thread panicked.
  ├─▶ at crates/aiken-lang/src/uplc.rs:754:29
  ╰─▶ internal error: entered unreachable code
  help: set the `RUST_BACKTRACE=1` environment variable to display a backtrace.

What should be the expected behavior?
It should not panic.

I wouldn't bother with any sorting stuff until we have traits or some way to have polymorphic ordering operators.

I am aware, this was not to endorse sorting but rather to flag there maybe a new unknown error in Aiken compiler which could happen under different circumstances.

A sort was recently added to stdlib


Update dash_acl.p4 Change Optional to Ternary

Change 'optional' to 'ternary' according to last Behavioral Model meeting.
Issue 575 Change dash_acl

This work is going to take some time and it also changes the attributes of the ACL table too (ternary match will add a priority attribute, which is not in design), so it will require a larger change to get it addressed.

See comments above


Colored notification-active

Add new icon(s) to the library

Please fill out the table below with the desired information per icon

name
category
description

notification-active
interface
this icon is a colored version of the current notification-active icon to be used for the new search experience alert

Icon art

The icon(s) per this request, has the new art been completed?

[X] Yes
[ ] No

If YES, does the new icon art follow all the recommendations from the Auro Icon Design Guidelines?

[X] Yes
[ ] No

If YES, the icon(s) in the request, have they been added to the UiKit Abstract repo?

[x] Yes
[ ] No

Attach exported SVG files to this issue
notification-active.zip

Does this icon need to be moved into the fullColor/ namespace in the iconography library? It has a monocolor counterpart of the same design already in ADS.

I am assuming that this request is to replace the current mono-color version.

I am assuming that this request is to replace the current mono-color version.

Yes, if that is alright to do.


Overlay rotation

Hi, I am using the Overlay component and I want to rotate this. I see that bearing prop is not there anymore. And I tried adding the style and change the props to transform: [{rotate: '50deg'}]. It doesn't work either. Any suggestion?

@KaviduAloka bearing property does work for Overlay component (tested on Android physical device), but you must manually clone library and select master branch, and then put that cloned folder (react-native-maps) inside your node_modules folder (you can rename your current react-native-maps to keep it as a backup). But this is not appropriate way, i'm curious why updates on library are not included when simply installing it (e.g. npm install react-native-maps --save)

@nkulic thank you very much. It was in the documentation too. But it didn't make any sense. I will have a look and let you know..


Docs relating to streams

The documentation relating to involving writable streams is poor. There are no examples of how to set this up, and it appears that each 'chunk' is not the complete JSON despite what some of the documentation says.

Creating and using streams is not relevant to this project and its official documentation can be found within node's actual documentation here though you will likely not need to access the stream directly. I'm not sure what's unclear about what is pushed to them. It says "Each player is individually written to the stream" and that's exactly what happens. Every player object in the group regardless of page will be sent. There are examples of using it with a writable stream in savePlayers and other files.


Not possible to deploy the devfile registry via CR on OpenShift 4.12

Which area this feature is related to?
/kind bug
Which area this bug is related to?

/area registry

What versions of software are you using?
latest from main
Go project
Operating System and version:
OpenShift 4.12
Go Pkg Version:
Node.js project
Operating System and version:
Node.js version:
Yarn version:
Project.json:
Web browser

Operating System and version:
Browser name and version:
Bug Summary
Describe the bug:

To Reproduce:
Install registry operator on 4.12
create devfile-registry namespace and create CR in it
based on quay.io/devfile/devfile-index:next
ERROR: pod can not be started:
Error creating: pods "devfile-registry-cd79f67d9-" is forbidden: unable to validate against any security context constraint: [provider "anyuid": Forbidden: not usable by user or serviceaccount, provider restricted-v2: .spec.securityContext.fsGroup: Invalid value: []int64{3001}: 3001 is not an allowed group, spec.containers[0].securityContext.runAsUser: Invalid value: 1001: must be in the ranges: [1000600000,<PHONE_NUMBER>], spec.containers[1].securityContext.runAsUser: Invalid value: 1001: must be in the ranges: [1000600000,<PHONE_NUMBER>], spec.containers[2].securityContext.runAsUser: Invalid value: 1001: must be in the ranges: [1000600000,<PHONE_NUMBER>], provider "restricted": Forbidden: not usable by user or serviceaccount, provider "nonroot-v2": Forbidden: not usable by user or serviceaccount, provider "nonroot": Forbidden: not usable by user or serviceaccount, provider "hostmount-anyuid": Forbidden: not usable by user or serviceaccount, provider "hostnetwork-v2": Forbidden: not usable by user or serviceaccount, provider "hostnetwork": Forbidden: not usable by user or serviceaccount, provider "hostaccess": Forbidden: not usable by user or serviceaccount, provider "node-exporter": Forbidden: not usable by user or serviceaccount, provider "privileged": Forbidden: not usable by user or serviceaccount]

Expected behavior

Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable
Additional context

Any workaround?
N / A
Suggestion on how to fix the bug
related docs - https://devfile.io/docs/2.2.0/deploying-a-devfile-registry#deploying-a-devfile-registry-with-operator-lifecycle-manager
Target Date: 04-18-2023

After further investigating we have found a few items to address:

Under no circumstances is the default namespace to used for the deployment target. This namespace does not respect any security contexts set and is not recommend for use with OpenShift deployments. To properly address this:

We will provide this requirement in our README instructions and/or our documentation
Add validation in the webhooks to not allow the default namespace to be used for deployment

Our security contexts for the registry operator needs some adjusting to match the setups for our other templates, such as the helm chart. This is due to needing specific user/group definitions to allow a storage enabled volume for OCI registry to work, which is enabled by default for the registry operator. This feature is no longer needed for the devfile registry service so we will be disabling it by default to address this fix then further addressing the retirement of it across all deployment mechanisms in https://github.com/devfile/api/issues/1093.

@ibuziuk In this thread, could you provide the linked issue(s) which are being blocked by this issue.

Storage enabled volume now defaults to false fixing the security context issues: https://github.com/devfile/registry-operator/pull/40
Additional PRs coming in the next sprint for updating the documentation and providing webhook validation.

just for the record, the issue happen in any namespace, not just default e.g.

@ibuziuk

just for the record, the issue happen in any namespace, not just default e.g.

could you provide the linked issue(s) which are being blocked by this issue.

Thanks for catching and addressing this. We also caught this too during our deployment testing and disabling the storage enabled volume https://github.com/devfile/api/issues/1092#issuecomment-1495075473 seems to have fixed this during additional tests with OCP 4.12 environments.

well, I put the blocker label since it was not possible to use the operator for deploying registries via CR on 4.11 and 4.12

This is understandable that any issue needing to use the registry operator will be blocked by this issue. With the blocker label, it is good to have what issue(s) are being blocked which triggered the creation of the issue in addition to any additional issues that others can report on in the thread, helps us keep track of what is going on.
Side note: Officially, we are only supporting OCP 4.12 at this point. This will added to our requirements in documentation as one of the TODOs for this issue.

thanks, I added some details in the spike we had on the Eclipse Che end - https://github.com/eclipse/che/issues/22075#issuecomment-1496281368

Work in progress has webhook validation which prints the following error message when trying to deploy a devfile registry to a default namespace:
Error from server (devfile registry deployment namespace should never be 'default'.): error when creating "registry.yaml": admission webhook "vdevfileregistry.kb.io" denied the request: devfile registry deployment namespace should never be 'default'.

Work in progress has webhook validation which prints the following error message when trying to deploy a devfile registry to a default namespace:
Error from server (devfile registry deployment namespace should never be 'default'.): error when creating "registry.yaml": admission webhook "vdevfileregistry.kb.io" denied the request: devfile registry deployment namespace should never be 'default'.

@michael-valdron that looks good but can we avoid the duplicate error message devfile registry deployment namespace should never be 'default' (caused by error wrapping I think)

Should we say something along the lines of 'default' namespace is forbidden for devfile registry deployment.  Retry the deployment with a non-default namespace That way, users are guided on the corrective action to take.

Updating to webhook validation test cases to take these changes into account.

Webhook changes to validate the namespace is not default is now ready for review: https://github.com/devfile/registry-operator/pull/41
Additional PR is being worked on for documentation changes.

Deployment requirements outline in README.md is now ready for review: devfile/registry-operator#42

Latest changes to the registry operator seems to have fixed the errors shown in this issue while using OCP 4.12 and Kubernetes 1.23.
@ibuziuk Can you confirm if this is fixed on your end?

Additional time is needed for the review on this, target date has been updated. Confirmation of PR fixes and PR revisions to provide correct Kubernetes version requirements are still needed to close this issue.

tested on 4.12 nightly and it seems to work :+1:

Now using issue #662 to track documentation additions related to the requirements these changes support.
Since it is confirmed that the changes completed in https://github.com/devfile/registry-operator/pull/40 and https://github.com/devfile/registry-operator/pull/41 have resolved this issue I will be closing it now.


Code restrictions for merit function not documented

[Side note: You might want to consider a documentation problem category for issues.]
The following code fails:
using NonlinearSolve, LinearSolve, LinearAlgebra, Random, ForwardDiff, PyFormattedStrings

function fff(var, p)
  v_true = [1.0, 0.1, 2.0, 0.5]
  xx = [1.0, 2.0, 3.0, 4.0]
  println(f"{typeof(xx)}  {typeof(var)}  {typeof(v_true)}")
  xx[1] = var[1] - v_true[1]
  return var - v_true
end

v_true = [1.0, 0.1, 2.0, 0.5]
v_init = v_true .+ randn!(similar(v_true)) * 0.1

prob_oop = NonlinearLeastSquaresProblem{false}(fff, v_init)
sol = solve(prob_oop, LevenbergMarquardt(); maxiters = 10000, abstol = 1e-8)

The error generated is:
julia> include("z.jl")
Vector{Float64}  Vector{Float64}  Vector{Float64}
Vector{Float64}  Vector{Float64}  Vector{Float64}
Vector{Float64}  Vector{ForwardDiff.Dual{ForwardDiff.Tag{NonlinearSolve.NonlinearSolveTag, Float64}, Float64, 4}}  Vector{Float64}
ERROR: LoadError: MethodError: no method matching Float64(::ForwardDiff.Dual{ForwardDiff.Tag{NonlinearSolve.NonlinearSolveTag, Float64}, Float64, 4})

Closest candidates are:
  (::Type{T})(::Real, ::RoundingMode) where T<:AbstractFloat
   @ Base rounding.jl:207
  (::Type{T})(::T) where T<:Number
   @ Core boot.jl:792
  (::Type{T})(::VectorizationBase.Double{T}) where T<:Union{Float16, Float32, Float64, VectorizationBase.Vec{<:Any, <:Union{Float16, Float32, Float64}}, VectorizationBase.VecUnroll{var"#s45", var"#s44", var"#s43", V} where {var"#s45", var"#s44", var"#s43"<:Union{Float16, Float32, Float64}, V<:Union{Bool, Float16, Float32, Float64, Int16, Int32, Int64, Int8, UInt16, UInt32, UInt64, UInt8, SIMDTypes.Bit, VectorizationBase.AbstractSIMD{var"#s44", var"#s43"}}}}
   @ VectorizationBase ~/.julia/packages/VectorizationBase/0dXyA/src/special/double.jl:111
  ...

The error is generated in the line xx[1] = var[1] - v_true[1] in the function fff. I believe I understand this to be due to a call to fff inside solve with the argument var not being a vector but instead a construct using ForwardDiff. This is not covered in the documentation and I'm not sure how to get around this. [It is true that this line is completely irrelevant to the test case but in my real code I need to understand exactly what is happening.]

You will need https://github.com/SciML/PreallocationTools.jl

@avik-pal Looking at the documentation for PreallocationTools it is not clear to me how to use this. Can you show me how to use this for implementing fff in the above example? That is, how to write xx[1] = var[1] - v_true[1] in a form that will not cause an error.

@ChrisRackauckas Yes this works. Much Thanks!


Design Module Crystal Oscillator Block

Our module board design(s) may require an external crystal oscillator for a stable frequency source to the RP2040. While the RP2040 has an internal oscillator, they recommend feeding the clock from an external oscillator. So, step 1 is determining if we can use the internal crystal with the high frequencies we will likely need for SPI (>= 10 Mbps), step 2 is picking a crystal oscillator that fits those constraints, and step 3 is designing around the selected part.

We will use an external crystal. The Hardware Design doc uses  ABLS-12.000MHZ-B4-T in their minimal design example (12 MHz). Likely too slow, so we should look for a similar one with a higher frequency.


Improve logging so it's much less verbose

#39  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @vegarsti and the rest of your teammates on  Graphite


Build fails, Invalid lock "content-hash" on cloned project

Lock file is already created in repo, user clones down repo with lock file.
User tries ssb-project build in folder.
Errors out, logfile:

CompletedProcess(args=['poetry', 'install'], returncode=1, stdout=b'Creating virtualenv utd-nudb in /home/jovyan/utd_nudb/.venv\nInstalling dependencies from lock file\n', stderr=b'\nUnable to read the lock file (Invalid TOML file /home/jovyan/utd_nudb/poetry.lock: Key "content-hash" already exists.).\n')

Error can be resolved by running poetry lock --no-update before running ssb-project build again.
Should this robustness be built into build?

This sounds like a problem with the specific lock file in this project, there shouldn't be repeated keys in a TOML file. ssb-project shouldn't handle problems like this, that's up to the user.


[Cards] Section title

Not sure if this is possible?
When you ask for more info on an artist, you get a row of artworks, but they appear very similar to the row of artists (from 'trending artists'). It's easy to get confused about what you're looking at.
Can we add something like:

I don't think we can, but I can take a look, I've added all the words that can trigger the FB example data in the README: https://github.com/orta/Mitosis#want-to-test-it
If it isn't on one of them, it can't be done

Doesn't look like it, https://developers.facebook.com/docs/messenger-platform/send-api-reference/generic-template
Maybe have to have a feedback-like message above a carousel

Showing page 2 of Artworks from Juan Car


Validate v1.0.5

[x] Win7
[x] Win10

Upgrade went fine but i am investigating why a fresh reseed and without a dcrd previously synced is showing errors.
Don't know if these issues are new or not yet.

Win 10 64-bit upgrade went OK.
Clean install is syncing fine so far.

win7 seemed fine in both cases for me.  It is on a slow VM so I can't test much as usual, but no obvious regressions from last time.

No issues noted during upgrade on win10.
Did some additional testing this round when reseeding and without a previously synced chain, and i was noticing errors there (the error message said "credit value missing", and looking through the dcrwallet code i wasn't entirely sure what could have been causing this), but in any case i don't believe these are new regressions.  If others can't reproduce let's roll with this release and I will debug this in my environment later.

Closing this, reopen if more issues are discovered or anyone else can hit the missing credit error on seed restore without doing a full IBD.


Data-toggle AND data-filter, depending on click or double click

I am trying to make it so that when a user single clicks a filter, it becomes the only filter. If they double click a filter, the filter is added as an OR to the current filter(s).
Is that possible?
I am really new to JavaScript and libraries so please forgive my code, but this is what I tried:
var containerGrid = document.querySelector('.grid'),
    clickMix = mixitup(containerGrid),
    buttons = Array.from(document.querySelectorAll('.btn'));

const doubleClick = (e) => {
    e.preventDefault();
    if (e.currentTarget.hasAttribute('data-filter')) {
        var filter = e.currentTarget.getAttribute('data-filter');
        console.log(filter);
        e.currentTarget.removeAttribute('data-filter');
        e.currentTarget.setAttribute('data-toggle', filter);
  }
}

That successfully replaces the data-filter attribute with the data-toggle attribute when I double click a button. However, the button still seems to act as though it has the data-filter attribute still. I tried adding
clickMix.toggleOn(filter) but that didn't make a difference (I'm probably using it wrong).
Can you point me in the right direction? I've been trying things from the API method documentation but can't seem to figure it out.
--Edit--
I temporarily replaced the code triggered by double click with mixer.hide(). It first filters according to whatever button I clicked, THEN it filters everything out. So I guess that is a clue that the default behavior was occurring before my code ran. I'll have to try messing around with the mixClick event.

Hi there,
That's an interesting problem. I can't say I've come across it before, but it may be possible. Have you tried setting the controls.live configuration to true?
By default, MixItUp will crawl the DOM for your controls once and attach specific click functionality to them by type, on init. By setting live: true, we are telling MixItUp that the controls can change (e.g. added/removed/edited) during the a session, and that the functionality of a control must be determined when it clicked only, and not before. This incurs a very minor performance overhead which is why it is disabled by default.
An example integration looks like this:
var mixer = mixitup(containerEl, {
    controls: {
        live: true
    }
});

Hi there,
That's an interesting problem. I can't say I've come across it before, but it may be possible. Have you tried setting the controls.live configuration to true?
By default, MixItUp will crawl the DOM for your controls once and attach specific click functionality to them by type, on init. By setting live: true, we are telling MixItUp that the controls can change (e.g. added/removed/edited) during the a session, and that the functionality of a control must be determined when it clicked only, and not before. This incurs a very minor performance overhead which is why it is disabled by default.
An example integration looks like this:
var mixer = mixitup(containerEl, {
controls: {
live: true
}
});


ONNX conversion is too memory expensive

When I try to use "convert_hf_to_onnx.py" it is extremely expensive in terms of DRAM (or VRAM if I try to load the model and input to CUDA device). I am not able to convert to ONNX even with pretty good system resources. Is there any solution to this? Anybody successful convert to ONNX?

@makermotion were you able to find the solution , i am facing the same issue?
Thanks

@bhupendrasalesken hey, the solution for me was more memory :) I think this is the nature of ONNX conversion for huge models.

@makermotion you closed this? I am on a machine with 720GB of RAM and still hitting OOM trying to convert storywriter with 16k sequence length and batch size of 1.

@zacharyblank I can understand that it might be a problem with longer context lengths but I think no minor changes will solve this.


Jupyter notebook not able to run on Conda environments

Issue Type: Bug
I installed Ipykernel and jupyter packages in a Conda environment. I then selected that environment as Kernel. I tried to run a simple code in a cell
x = 5
y = 4
x+y

The kernel does load and I get this error:

Kernel died with exit code 1. C:\Users\spannala\AppData\Roaming\Python\Python39\site-packages\traitlets\traitlets.py:2196: FutureWarning: Supporting extra quotes around Unicode is deprecated in traitlets 5.0. Use 'hmac-sha256' instead of '"hmac-sha256"' – or use CUnicode.
warn(
C:\Users\spannala\AppData\Roaming\Python\Python39\site-packages\traitlets\traitlets.py:2151: FutureWarning: Supporting extra quotes around Bytes is deprecated in traitlets 5.0. Use 'f87c5fd3-18f2-4a8c-bac4-41774c9a79b3' instead of 'b"f87c5fd3-18f2-4a8c-bac4-41774c9a79b3"'.
warn(
Traceback (most recent call last):
File "C:\Users\spannala\Miniconda3\envs\NDS\lib\runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "C:\Users\spannala\Miniconda3\envs\NDS\lib\runpy.py", line 87, in _run_code
exec(code, run_globals)
File "C:\Users\spannala\AppData\Roaming\Python\Python39\site-packages\ipykernel_launcher.py", line 16, in
app.launch_new_instance()
File "C:\Users\spannala\AppData\Roaming\Python\Python39\site-packages\traitlets\config\application.py", line 844, in launch_instance
app.initialize(argv)
File "C:\Users\spannala\AppData\Roaming\Python\Python39\site-packages\traitlets\config\application.py", line 87, in inner
return method(app, *args, **kwargs)
File "C:\Users\spannala\AppData\Roaming\Python\Python39\site-packages\ipykernel\kernelapp.py", line 577, in initialize
self.write_connection_file()
File "C:\Users\spannala\AppData\Roaming\Python\Python39\site-packages\ipykernel\kernelapp.py", line 230, in write_connection_file
write_connection_file(cf, ip=self.ip, key=self.session.key, transport=self.transport,
File "C:\Users\spannala\AppData\Roaming\Python\Python39\site-packages\jupyter_client\connect.py", line 136, in write_connection_file
with secure_write(fname) as f:
File "C:\Users\spannala\Miniconda3\envs\NDS\lib\contextlib.py", line 117, in enter
return next(self.gen)
File "C:\Users\spannala\AppData\Roaming\Python\Python39\site-packages\jupyter_core\paths.py", line 461, in secure_write
win32_restrict_file_to_user(fname)
File "C:\Users\spannala\AppData\Roaming\Python\Python39\site-packages\jupyter_core\paths.py", line 387, in win32_restrict_file_to_user
import win32api
ImportError: DLL load failed while importing win32api: The specified procedure could not be found.

VS Code version: Code - Insiders 1.58.0-insider (49e1f9919880c1c96004f9b6ad91bcee7a94a1bd, 2021-06-25T05:14:20.119Z)
OS version: Windows_NT x64 10.0.17134
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Xeon(R) CPU E3-1245 v3 @ 3.40GHz (8 x 3392)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.94GB (7.28GB free)

Process Argv
--crash-reporter-id 6fbbf8cb-b568-4b3b-9ae7-493a124a6e21

Screen Reader
no

VM
0%

Extensions (14)

Extension
Author (truncated)
Version

gitlens
eam
11.5.1

vsc-material-theme
Equ
33.2.2

vsc-material-theme-icons
equ
2.0.10

vscode-pull-request-github
Git
0.27.1

git-graph
mhu
1.30.0

gather
ms-
2021.6.0

python
ms-
2021.7.969414671-dev

vscode-pylance
ms-
2021.6.4-pre.1

jupyter
ms-
2021.7.970869158

vscode-github-issue-notebooks
ms-
0.0.102

best-dark-themes-pack
the
1.0.2

vscodeintellicode
Vis
1.2.14

vscode-icons
vsc
11.5.0

material-theme
zhu
3.10.14

(11 theme extensions excluded)

A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383:30185418
pythonvspyt602:30291494
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30291487
pythontb:30258533
pythonvspyt551:30291412
vspre833:30321513
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscus158:30321503
pythonvsuse255:30319630
vscorehov:30301224
vscod805cf:30301675
pythonvspyt200:30323110
vscextlangct:30310089
vsccppwt:30312692

The same error is occurring with poetry virtual environments. Only pipenv virtual environments seem to work.


flac: 1.3.4 -> 1.4.0

Description of changes
Upstream tag/release notes: https://github.com/xiph/flac/releases/tag/1.4.0
Note, there will be a 1.4.1 soon, if this causes a lot of rebuilds, it may be better to wait for 1.4.1 before merging.
Also adopt the package as a maintainer, since it did not have any yet. I am subscribed to the flac-dev mailing list and I maintain an alternative flac decoder so I keep an eye out on developments upstream.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Because of so many rebuilds, please use branch staging.
The tricky part is how to switch the branch without triggering the maintainer notifications. And I have no answer for that.
I would try to cherry pick your commit to staging, do a force push on your branch und immediately update the "into branch" of this PR. But I am not sure if the force push directly triggers the "package changed analysis and notify maintainer".
Another way could be to close this PR and reopen it after you did the changes.

If there's a mistake in the 1.4.0 release, I suppose it will be better to wait a while for 1.4.1.

Thanks for having a look @ck3d and @vcunat.
Would force-pushing b52db2e48020e7a7499aa66e51288530413214fc (a rebased version of this pr) at this point trigger unwanted notifications, now that @vcunat changed the base branch to staging? I’m a little scared to do that now, so I created a new pull request instead, see #191362.
I marked it as draft pending the 1.4.1 release.

I think you only trigger problems if you get - at some point - many commits between your target branch (as selected on GitHub) and your head branch for the PR.  Normally that only happens when changing bases (and not always).


Add preferred max heap size setting to settings, and autodetect a good value by default

The JVM's default max heap varies by OpenJDK version, but is typically rather small compared to the size of memory on a computer. For example, I ran out of memory trying to perform a filter.gauss op on a 1G dataset. After increasing my max heap to 16G by adding -Xmx16g to the additional JVM args area, I was able to perform the operation.
But users will not know to do this, especially Python users who don't know Java. Fiji tries to be kind and autoset the max heap to 3/4 of your physical RAM by default, and I think napari-imagej should do the same. I also think the settings dialog should expose an option directly to control max memory, rather than instructing users in the documentation (which many people don't read, of course) to add the arcane -Xmx... flag to extra JVM args.
Detecting physical memory size in Python is simple with psutil:
import psutil
memory_mb = psutil.virtual_memory().total / 1024**2

As an aside: it's unfortunate that the backing ImgLib2 implementation for filter.gauss seems to scale badly in RAM with the size of the image. In my story above, I was performing the computation on an image wrapped from Python, to an image wrapped from Python. The way it ran out of memory was actually due to the creation of too many and/or large intermediate data objects during the computation, which for something like gauss is surprising given that the amount of intermediate RAM needed should be bounded by something like threads x neighborhood_pixel_count x bytes_per_pixel. My sigmas were (5, 5, 0, 0) so the neighborhood_pixel_count is only 11 x 11, and I have 24 cores according to Java, so that's a measly 12KB of intermediate storage needed for a naive gauss implementation.


Filtering by log type and then changing log causes fatal error

Hello - this package looks lovely, and I'm excited to use it in my app!
I've found a bug which I seem to be able to reproduce reliably.

Select a log file from the left hand side
Filter out 'Notice' (or any other log type) at the top

Change log file to a different one

This then causes a fatal error, as demonstrated below.
Let me know if you require any more info. Cheers!

The line this fails at means it's not finding the timestamp for this particular log entry. This tells me there might be something in the second log file (the one you're switching to later) that's not properly understood by the log viewer.
Could you please share the full log file (as an attachment, not a quote here) that you're switching to in your example?
Thanks! 🙌

Hey @dkmonaghan , thanks for reporting this!
The line this fails at means it's not finding the timestamp for this particular log entry. This tells me there might be something in the second log file (the one you're switching to later) that's not properly understood by the log viewer.
Could you please share the full log file (as an attachment, not a quote here) that you're switching to in your example?
Thanks! 🙌

Hi @arukompas  - thanks for the quick reply!
I've just spent some time removing lines from my test log file to see where it fails, and it seems like there's no line specifically that's causing it to fail. I'm actually even more baffled than I was before, and I think the de-selecting of "NOTICE" was actually a red herring. The behaviour happens regardless of whether or not I have any filtering of event types enabled.
I've created a log file called test.log containing only the below, and this fails consistently:
[2022-08-30 15:42:54] production.NOTICE: Test

I'm pretty stumped by this. I have log files that are multiple megabytes large that render fine, yet the above fails to render. The request that actually returns the HTTP 500 is a call to livewire/message/log-viewer::log-list, if that helps. Let me know what more information I can provide - if a video would be helpful, I'm happy to provide that.
Additionally, while experimenting, I discovered that the viewer fails with a fatal error if no logs at all are found in the directory, rather than failing gracefully. It'd be nice if it didn't do this!

hey @dkmonaghan , ok, so there's 2 bugs now! :D
1. The exception when viewing test.log
I'm still finding it difficult to replicate 😅 Maybe the issue is with a different PHP version or a different OS, which behaves slightly differently or has a different REGEX behaviour...
Here's the latest (v1.2.1) log viewer that handles this test.log file with just a single line, just fine:

I've made a small bugfix to validate the last log entry. Could you please upgrade to the latest (v1.2.2) version of the Log Viewer first?
If it still fails, could you please let me know:

the Log Viewer version you're using (bottom right corner)
the PHP version
Laravel version
the OS you're using

This might help me debug the issue if I can mimick the exact environment.
2. Failure when no log files are found
I was testing this and found that the exception only occurs when the file from the query param (e.g. localhost/log-viewer?file=test.log) is not found. I've added a check for that in the newest v1.2.2 release - https://github.com/opcodesio/log-viewer/releases/tag/v1.2.2

Hi @arukompas

v1.2.3 still fails to render test.log for me, I'm afraid.

Log Viewer Version = 1.2.3
PHP Version = 8.1.6
Laravel Version = 9.27.0
OS = Debian 11.4

Yes, this seems to be fixed now! :)

Hey @dkmonaghan , please try the latest version as there have been some changes to the regular expressions used to match the logs. Thanks!


xsltproc from libxslt produces broken man pages from docbook files

Describe the bug
When generating man pages from docbook files the tool introduces spaces before tags which breaks the man page. This affects some packages which rely on it for manpage generation, e.g., xmlto and xdg-utils. This behavior does not occur on other distributions (I've checked Debian and Alpine).
Steps To Reproduce
Steps to reproduce the behavior:

nix-shell -p xmlto
man xmlto
See the broken man page

Expected behavior
The xsltproc produces correct man pages.
Notify maintainers
@jtojnar

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.10.7, NixOS, 24.11 (Vicuna), 24.11.20240831.12228ff`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.5`
 - nixpkgs: `/nix/store/bd4fmzws6n5542khxbifbkr6nrygi232-source`

Add a :+1: reaction to issues you find important.

same issue as https://github.com/NixOS/nixpkgs/issues/299081#issuecomment-2019352869?

If  the problem is with the stylesheet, same as the other issue, then the package to fix would docbook-xsl (currently maintainerless).


binary_directory in getBinaryDirectoryHostEncoded() lacks an implementation for OpenBSD

Hi, I'm working on an OpenBSD package for Nuitka. It builds fine but the standalone binaries generated abort in getBinaryDirectoryWideChars. Looks like  binary_directory in getBinaryDirectoryHostEncoded() (build/static_src/CompiledCodeHelpers.c) lacks an implementation for OpenBSD.
$ python3.7 -m nuitka --version
0.6.7
Python: 3.7.7 (default, Mar 30 2020, 15:25:59)
Executable: /usr/local/bin/python3.7
OS: OpenBSD
Arch: amd64

Hello,
can you check if the factory branch works better for you. I do not have access to an openBSD machine, but this should be better and I willing to work on it.
https://nuitka.net/doc/factory.html
Yours,
Kay

Thanks for the quick reply. I checked your recent changes in CompiledCodeHelpers.c, unfortunately that's not going to work on OpenBSD. It doesn't have KERN_PROC_PATHNAME.

I asked in our internal chat and Robert Nagy gave me this code. http://ix.io/2gZF

Excuse me for arguing with the demo program.
I am not convinced that argv[0] is the path to the binary in all cases, it depends on how it's forked and could be an arbitrary value. Therefore the Chromium patch is very much based on that kind of luck to work. My guess that KERN_PROC_PATHNAME` is apparently untrue.
Also tokens need not be an array, only a char * is return by strtok and only element 0 is used. The split to : is confusing to me, maybe uses an implementation detail. Makes me wonder of course, what happens with paths that contain that character.
Also the scan for open files, seems to only do that the split to : value is returned only if a main program file is found. I guess, it's missing a match there. It would make sense to check if it's the same file I guess, but that part is not done. A program not having the program text open is probably unlikely, so this doesn't contribute to reliability, does it, and requiring it is not a help I think, if it's not used to check. So I would leave that out, or see it enhanced to make a check that compares the name or content derived from argv[0] and that file, and error out if they mismatch.
I don't think there is a way to get the filename names from a file handle, is there?
Also I guess, I need to setup a VM. Due to my switch to WSL I don't have the KVM to run OpenBSD easily now. But I got a machine with Hyper-V where I can do it maybe, but that will take time.
I will try and incorporate the code given without checks, it's probably the best thing possible, but allow some time for that. I still want to see if there is an easy way to test for me.

Unfortunately, I can't help you with the C code. That's why I asked for alternatives to FreeBSD KERN_PROC_PATHNAME, so you can adapt the code to your needs. From time to time appears a package which requires something equivalent but OpenBSD doesn't implement KERN_PROC_PATHNAME because it makes assumptions which are not always true (not my words).
If you need machines with different OS and architectures, ask for an account in the GCC Compile Farm. They accept users from non GNU projects.

The code that was on factory, turned out to be useless. I will attempt a solution, once I got VMs back under control. Compile farm is all nice, but I prefer more control.

I do have the VM setup now, and I am going to install OpenBSD just to do a quick check, but it's not going to be fast. The code may still not work, let me know if you have any new knowledge here.

I am installing a VM with OpenBSD just now, lets see how it goes.

My VM installation is not forthcoming, if nobody is going to step up, I am going to close the issue at 2.3 release time, this should be tested by somebody with OpenBSD.

I'm still getting an error regarding KERN_PROC_PATHNAME:
(cool-venv2) nickfaro$ python -m nuitka --follow-imports pygmentize_launcher.py
Nuitka-Options: Used command line options: --follow-imports pygmentize_launcher.py
Nuitka-Options: Detected static libpython to exist, consider '--static-libpython=yes' for better performance,
Nuitka-Options: but errors may happen.
Nuitka: Starting Python compilation with Nuitka '2.2.3' on Python '3.10' commercial grade 'not installed'.
Nuitka: Completed Python level compilation and optimization.
Nuitka: Generating source code for C backend compiler.
Nuitka: Running data composer tool for optimal constant value handling.
Nuitka: Running C compilation via Scons.
Nuitka-Scons: Backend C compiler: clang (clang 16.0.6).
In file included from static_src/CompiledFunctionType.c:3108:
In file included from /home/npfaro/pygment-stuff/cool-venv2/lib/python3.10/site-packages/nuitka/build/static_src/CompiledCodeHelpers.c:56:
/home/npfaro/pygment-stuff/cool-venv2/lib/python3.10/site-packages/nuitka/build/static_src/HelpersFilesystemPaths.c:59:14: error: use of undeclared identifier 'KERN_PROC_PATHNAME'
    mib[2] = KERN_PROC_PATHNAME;
             ^
/home/npfaro/pygment-stuff/cool-venv2/lib/python3.10/site-packages/nuitka/build/static_src/HelpersFilesystemPaths.c:197:10: fatal error: 'sys/sendfile.h' file not found
#include <sys/sendfile.h>
         ^~~~~~~~~~~~~~~~
2 errors generated.
Nuitka-Scons: Backend linking program with 7 files (no progress information available for this stage).
scons: *** [static_src/CompiledFunctionType.o] Error 1
FATAL: Failed unexpectedly in Scons C backend compilation.
Nuitka:WARNING:     Complex topic! More information can be found at
Nuitka:WARNING: https://nuitka.net/info/scons-backend-failure.html
Nuitka-Reports: Compilation crash report written to file 'nuitka-crash-report.xml'.

Looks to me like OpenBSD doesn't have KERN_PROC_PATHNAME, but here the directive incorrectly says to use it:
https://github.com/Nuitka/Nuitka/blob/e6ea71eac84d0a866fad3aa3c26c03577f927018/nuitka/build/static_src/HelpersFilesystemPaths.c#L52

I at least got things to compile with this patch, but the resulting binary just core dumps.
diff --git a/nuitka/build/static_src/HelpersFilesystemPaths.c b/nuitka/build/static_src/HelpersFilesystemPaths.c
index e69cbd749..89cd78ef8 100644
--- a/nuitka/build/static_src/HelpersFilesystemPaths.c
+++ b/nuitka/build/static_src/HelpersFilesystemPaths.c
@@ -49,7 +49,7 @@ filename_char_t *getBinaryPath(void) {
     if (res != 0) {
         abort();
     }
-#elif defined(__FreeBSD__) || defined(__OpenBSD__)
+#elif defined(__FreeBSD__)
     /* Not all of FreeBSD has /proc file system, so use the appropriate
      * "sysctl" instead.
      */
@@ -167,7 +167,7 @@ int64_t getFileSize(FILE_HANDLE file_handle) {
 #if defined(__APPLE__)
 #include <copyfile.h>
 #else
-#if defined(__MSYS__) || defined(__HAIKU__)
+#if defined(__MSYS__) || defined(__HAIKU__) || defined(__OpenBSD__)
 static bool sendfile(int output_file, int input_file, off_t *bytesCopied, size_t count) {
     char buffer[32768];

@@ -618,7 +618,7 @@ char const *getBinaryFilenameHostEncoded(bool resolve_symlinks) {
     // Resolve any symlinks we were invoked via
     resolveFileSymbolicLink(binary_filename_target, binary_filename_target, buffer_size, resolve_symlinks);

-#elif defined(__FreeBSD__) || defined(__OpenBSD__)
+#elif defined(__FreeBSD__)
     /* Not all of FreeBSD has /proc file system, so use the appropriate
      * "sysctl" instead.
      */

I got things working using this patch, I grabbed some code off StackOverflow to implement the binary path thing but I don't really know if it's totally right.
diff --git a/nuitka/build/static_src/HelpersFilesystemPaths.c b/nuitka/build/static_src/HelpersFilesystemPaths.c
index e69cbd749..f0b258b14 100644
--- a/nuitka/build/static_src/HelpersFilesystemPaths.c
+++ b/nuitka/build/static_src/HelpersFilesystemPaths.c
@@ -34,6 +34,62 @@
 #include "nuitka/filesystem_paths.h"
 #include "nuitka/safe_string_ops.h"

+const char *getExecutablePathOBSD(char *epath) {
+  int mib[4];
+  char **argv;
+  size_t len;
+  const char *comm;
+  int ok = 0;
+
+  mib[0] = CTL_KERN;
+  mib[1] = KERN_PROC_ARGS;
+  mib[2] = getpid();
+  mib[3] = KERN_PROC_ARGV;
+
+  if (sysctl(mib, 4, NULL, &len, NULL, 0) < 0)
+    abort();
+
+  if (!(argv = malloc(len)))
+    abort();
+
+  if (sysctl(mib, 4, argv, &len, NULL, 0) < 0)
+    abort();
+
+  comm = argv[0];
+
+  if (*comm == '/' || *comm == '.') {
+    if (realpath(comm, epath))
+      ok = 1;
+  } else {
+    char *sp;
+    char *xpath = strdup(getenv("PATH"));
+    char *path = strtok_r(xpath, ":", &sp);
+    struct stat st;
+
+    if (!xpath)
+      abort();
+
+    while (path) {
+      snprintf(epath, PATH_MAX, "%s/%s", path, comm);
+
+      if (!stat(epath, &st) && (st.st_mode & S_IXUSR)) {
+        ok = 1;
+        break;
+      }
+
+      path = strtok_r(NULL, ":", &sp);
+    }
+
+    free(xpath);
+  }
+
+  if (ok)
+    *strrchr(epath, '/') = '\0';
+
+  free(argv);
+  return ok ? epath : NULL;
+}
+
 filename_char_t *getBinaryPath(void) {
     static filename_char_t binary_filename[MAXPATHLEN];

@@ -49,7 +105,9 @@ filename_char_t *getBinaryPath(void) {
     if (res != 0) {
         abort();
     }
-#elif defined(__FreeBSD__) || defined(__OpenBSD__)
+#elif defined(__OpenBSD__)
+    getExecutablePathOBSD(binary_filename);
+#elif defined(__FreeBSD__)
     /* Not all of FreeBSD has /proc file system, so use the appropriate
      * "sysctl" instead.
      */
@@ -167,7 +225,7 @@ int64_t getFileSize(FILE_HANDLE file_handle) {
 #if defined(__APPLE__)
 #include <copyfile.h>
 #else
-#if defined(__MSYS__) || defined(__HAIKU__)
+#if defined(__MSYS__) || defined(__HAIKU__) || defined(__OpenBSD__)
 static bool sendfile(int output_file, int input_file, off_t *bytesCopied, size_t count) {
     char buffer[32768];

@@ -617,8 +675,10 @@ char const *getBinaryFilenameHostEncoded(bool resolve_symlinks) {

     // Resolve any symlinks we were invoked via
     resolveFileSymbolicLink(binary_filename_target, binary_filename_target, buffer_size, resolve_symlinks);
-
-#elif defined(__FreeBSD__) || defined(__OpenBSD__)
+#elif defined(__OpenBSD__)
+    getExecutablePathOBSD(binary_filename_target);
+    resolveFileSymbolicLink(binary_filename_target, binary_filename_target, buffer_size, resolve_symlinks);
+#elif defined(__FreeBSD__)
     /* Not all of FreeBSD has /proc file system, so use the appropriate
      * "sysctl" instead.
      */

The bit where it does
+  if (ok)
+    *strrchr(epath, '/') = '\0';

That seems to be there it strips the binary name away, which is not what is wanted. And in case of not OK, it should abort since it must be expected to be possible to resolve this. Can you make a PR @SuperDisk so I can integrate it, seems like a good idea.

@kayhayen I created the PR, although I must say that I didn't really test it at all, I just quickly put it together to make something work. Please let me know if there's anything else I can do to help out, I can test on an OpenBSD machine once there's a proper fix so you don't have to set up a VM.

Correct, this is released now, very many thanks for the help!


Enable contam overlap with MIRI

Update:

There was some contamination "pile up" for MIRI LRS

I fixed it by making the contamination calculator ignore the rows that had just pure background:

Next issue is verifying that all the contamination is there because it looks like MIRI has way less contamination compared to its NIRCam equivalent for this target:

@hover2pi


documentation question about nested block

I tried the doc about nested block
file "base":
===
{% block a %}{% endblock %}
===

file "child"
{% if not Standalone %} {% extends "base" %}{% endif %}
{% for item in ("a","b","c") %}
  {% set int = loop.index %}
  {% block a scoped %}
  {{ int }} : {{ item }}
  {% endblock %}
{% endfor %}

{% block another %}
   another  block only in child
{% endblock %}

{% for item in (1,) %}
   {% block other %}
      other block only in child
   {% endblock %}
{% endfor %}
{% for item in (1,) %}
   something in child out of block
{% endfor %}

out put:

  1 : a

  2 : b

  3 : c

      other block only in child
   ===

   :

===

Maybe this is a bad practice.
Is this output normal ?I am confused about this behavior  :

{% block another %} and {% block other %} are both only in child but not defined in parent .But only one nested in for loop was rendered to finally output .
{% block a %} was in a for loop .But where did the ":" in the last 3 line  come from ?
So How would jinja deal block and text defined only in child but not in parent while template inheritances used.
when re-defined same named block in neither child nor base. It will throw error exception while rendering. So what's the difference when put it in a for loop.It appeared 4 times?
by the way. with scoped enabled. block  can access  outer var now.but loop.index seemed not accessible directly

There's just a bunch of weird template nesting here along with a lot of questions. And it's not super clear to me what's going on or what's being asked. This does not seem like a standard use of templates. Closing due to age. If someone runs across this and thinks they have a better example of the specific behavior, please open a new issue.


Specify locale for case conversions

case conversion without specifying locale can vary based on the locale of the machine executing the code.  Conversion functions should specify the proper locale such that behavior is consistent regardless of locale.
See https://github.com/Kotlin/KEEP/blob/master/proposals/stdlib/locale-agnostic-string-conversions.md
A quick check to Smithy's source code yields that locale is always specified, so the scope of this is specific to SDKs that call case conversions explicitly, not those that call Smithy-based methods.
internal id: 176991541

Moved to 2170


get rows occupied in each col?

hi,
is there an easy way to get an object width the occupied number of rows in each column.
been searching through the source but haven't found any.

@dustmoo Can you give an example how to use for_each_widget_below() function. Because it is not working for me. Plz


kubeadm: promote the "kubeadm certs" command to GA

The command resided under "kubeadm alpha certs".
It will be promoted to GA in 1.20 as "kubeadm certs".
The existing command "kubeadm alpha certs" will
remain present for one more release, but it will be hidden
from documentation as it is deprecated.
xref https://github.com/kubernetes/kubeadm/issues/2291

/sig cluster-lifecycle
/cc @yagonobre

note: the generated/* file changes are needed so that this PR can pass CI, but otherwise the docs release process should generate them.

/milestone 1.20

added missing section for certs generate-csr.

rebased on top of https://github.com/kubernetes/website/pull/24557

/cc @tengqm
hi, this PR renames the generated files for "kubeadm_alpha_certs_" -> "kubeadm_certs_", with the assumption that since the "kubeadm alpha certs" command will be deprecated in 1.20 it will be hidden from the generator. LMK if this is PR is valid, as is.

I'd like to suggest we put this on hold until we are near the release week. There could be further changes to kubeadm tool. Such changes will lead to the changes in the generated docs as well.

SGTM @tengqm . we have no more planned changes for commands, but merging this late seems fine as long as the docs approvers agree.

/hold

hey @neolit123 wondering if this is part of an enhancement? could you link the enhancement link here?

hi, @annajung no it does not have a tracking issue in k/enhancements. historically this has not been done for kubeadm command promotions.

I see, thanks for the clarification! :D

/assign

@kubernetes/sig-cluster-lifecycle can someone else from sig cluster lifecycle provide a tech review / lgtm?

@annajung This one doesn't need a tech lgtm. The author is from that sig.

/label tide/merge-method-squash


Feature request: "Clear" icon button in date input.

Is your feature request related to a problem? Please describe.
It's quite common when we need to clear selected date in datepicker. Currently this feature is not implemented for inline datepicker. So we need to add external controls and logic to handle it.
Describe the solution you'd like
It'd be very handy to have optional "X" icon button in date input itself (like in react-datepicker) that allows us to clear selected date when clicking on it.

Would you like to open a PR?

I have never used TypeScript, but I can try.

@stsiarzhanau nice way to start with ts. Its pretty awesome


Zoho chat does not open on Flutter app Android.

Hi everyone,
I have a problem with the sd zoho on android flutter for a while now in effect the chat button appears correctly but when you click on it nothing happens. I obviously have the latest version of the sdk installed.
implementation 'com.zoho.salesiq:mobilisten:6.0.2'
The version of the package I use:
salesiq_mobilisten: ^4.0.0
Thank you in advance for any help.

Hi @joresv ,
We apologize for any inconvenience caused. This issue seems to be an unusual case. Please write us at<EMAIL_ADDRESS>with your Mobilisten configuration details (code snippets), portal details, and the app key. We will check it from our side and get back to you.
Best regards,
Bhahirathan M,
Zoho SalesIQ

Hi @bhahirathan-mb-11956  I get this error when I want to leave you an email

Hi @joresv
Apologies. Here is the correct email address to reach out to us -<EMAIL_ADDRESS>Please mail us the mentioned details and we will get back to you.


Question about detection in Nuscenes

Hello, sir!
I'm learning your code, in the detection part, you wrote in data_preprocess.md that the command is like this:
cd preprocessing/nuscenes_data
python detection.py --raw_data_folder ${raw_data_dir} --data_folder ${data_dir_2hz} --det_name ${name} --file_path ${file_path} --mode 2hz --velo
i have downloaded the nuscences data you published by dropbox, and move it to SimpleTrack directory. So I entered following command:  python detection.py --raw_data_folder /mnt/yrfs/nuscenes/src_data/nuscenes/ --data_folder data_dir_2hz --det_name lyx_track --file_path ../../nuscenes/validation_2hz/center_point_detection.json --mode 2hz --velo
It returns to me an error that "ValueError: setting an array element with a sequence. The requested array has an inhomogeneous shape after 1 dimensions. The detected shape was (40,) + inhomogeneous part."
Could you pls tell me what's the problem it is?

@lyx-louis Sure, let me check this. Could you please re-do the whole procedure (from the step of git clone) and provide me a full log of the error? It is a bit difficult for me to check the error with limited information.

ok i will re-do it. pls wait a moment

Ok sir, i re-did it and found that it works and in the directory below the detection, it generate a lot of scene-xxx.npz fichiers, is that the correcte result?
In fact i found that it maybe because the conda enviorment, in the previous enviorment, python version is 3.6, it report the error like this:
python detection.py --raw_data_folder /mnt/yrfs/nuscenes/src_data/nusce                                                                                nes/ --data_folder data_dir_2hz --det_name lyxsimple --file_path ../../nuscenes/                                                                                validation_2hz/center_point_detection.json --mode 2hz --velo
LOADING RAW FILE
PROCESSING...
100%|████████████████████████████████████| 6019/6019 [00:00<00:00, 11627.23it/s]
SAVING...
0%|                                                   | 0/150 [00:00<?, ?it/s]                                                                                Traceback (most recent call last):
File "detection.py", line 104, in
main(args.det_name, args.file_path, detection_folder, args.data_folder, args                                                                                .mode)
File "detection.py", line 90, in main
np.savez_compressed(os.path.join(output_folder, '{:}.npz'.format(scene_name)                                                                                ),
File "<array_function internals>", line 200, in savez_compressed
File "/home/win/Softwares/anaconda/envs/simpletrack/lib/python3.8/site-package                                                                                s/numpy/lib/npyio.py", line 686, in savez_compressed
_savez(file, args, kwds, True)
File "/home/win/Softwares/anaconda/envs/simpletrack/lib/python3.8/site-package                                                                                s/numpy/lib/npyio.py", line 716, in _savez
val = np.asanyarray(val)
ValueError: setting an array element with a sequence. The requested array has an                                                                                inhomogeneous shape after 1 dimensions. The detected shape was (40,) + inhomoge                                                                                neous part.
0%|                                                   | 0/150 [00:00<?, ?it/s]
and when i change another enviorment, it report that:
python detection.py --raw_data_folder /mnt/yrfs/nuscenes/src_data/nuscenes/ --                                                                                data_folder data_dir_2hz --det_name lyxsimple --file_path ../../nuscenes/validat                                                                                ion_2hz/center_point_detection.json --mode 2hz --velo
LOADING RAW FILE
PROCESSING...
100%|████████████████████████████████████| 6019/6019 [00:00<00:00, 12032.48it/s]
SAVING...
0%|                                                   | 0/150 [00:00<?, ?it/s]                                                                                /home/win/Softwares/anaconda/lib/python3.9/site-packages/numpy/lib/npyio.py:719:                                                                                VisibleDeprecationWarning: Creating an ndarray from ragged nested sequences (wh                                                                                ich is a list-or-tuple of lists-or-tuples-or ndarrays with different lengths or                                                                                shapes) is deprecated. If you meant to do this, you must specify 'dtype=object'                                                                                when creating the ndarray.
val = np.asanyarray(val)
100%|█████████████████████████████████████████| 150/150 [00:04<00:00, 35.03it/s]
Could you pls confirm the result? thx alot
I compare the version between this 2 conda enviorment
The first one (which report error ). numpy version is 1.24.3,filterpy = 1.4.5, shapely =1.8.5,  numba = 0.57.0 pyquaternion=0.9.9 and nuscenes-devkit=1.1.10, python = 3.8.16
And for the second one,  numpy version is 1.21.6,filterpy = 1.4.5, shapely =1.8.5,  numba = 0.55.1 pyquaternion=0.9.9 and nuscenes-devkit=1.1.10,python=3.9.12

@lyx-louis Yes, this result looks good to me.


Exhaustiveness check should be able to prefer API instead of non-API witnesses

See https://dart-review.googlesource.com/c/sdk/+/308520 for the initial question.
With this CL, if we write switch like this:
void f(TypedLiteral node) {
  switch (node) {
  }
}

...and use "Add missing case" twice, it does end up with using implementation classes.
void f(TypedLiteral node) {
  switch (node) {
    case ListLiteralImpl():
      // TODO: Handle this case.
    case SetOrMapLiteralImpl():
      // TODO: Handle this case.
  }
}

It does not have to, and this API version works as well.
void f(TypedLiteral node) {
  switch (node) {
    case ListLiteral():
      // TODO: Handle this case.
    case SetOrMapLiteral():
      // TODO: Handle this case.
  }
}

So, here we might have a tooling issue. Either CFE should be enhanced to prefer reporting witnesses that are available in the target code, maybe some filtering, etc. Or the quick fix should climb up. Ideologically, I think it should be CFE. Or the analyzer in a way how it feeds data into CFE, e.g. never return non-API classes that the target package should not use. Not different than how code completion will not suggest non-API classes from other packages.

It appears that we do a better job than I expected. I don't have your CL patched in, but when I mark TypedLiteral as sealed and change the example slightly to force the switch to be exhaustive:
void f(TypedLiteral node) {
  var x = switch (node) {
    ListLiteral() => 2,
    SetOrMapLiteral() => 1,
  };
  print(x);
}

It realizes that those two types are supertypes of all of the subtypes of TypedLiteral and doesn't complain (which I thought it would).
I agree, though, that the tools need to do a better job with package-private types.


Navigating spesific screen in nested navigators

I didn't find to navigate spesific screen. Here is my case:
I have a TabNavigator with 2 tabs which are Tab1 and Tab2 inside DrawerNavigator. Also, I have a StackNavigator which has 6 different stacks, and one of them is DrawerNavigator. Now I wanna solve this problem: When I am on one of Stacks, I want to navigate Tab1 inside Drawer after clicking a button in the Stack. How can I do that? I found that some issues which are about changing initialRouteName, but I couldn't fit my case. Any idea ?

Did you see this: https://reactnavigation.org/docs/navigators/navigation-actions
So it seems you need to use the action param to navigate to a route in the child navigator. Something like this:
navigate('Drawer', {}, NavigationsActions.navigate({ routeName: 'Tab1'}))

Closing in favor of #1715


Plans for a new release?

Hi all - curious if there is another release planned soon? Looking at the PyPI package it's been a few months since the last release, and I see from the GitHub Release there's been about 92 commits since then.
Apologies if I missed any communications about this elsewhere - appreciate any info you can provide!

Hi! We'll be putting out a new release very soon! We were waiting on #1873 to merge and settle a little bit before doing so.

Great news - thank you @haileyschoelkopf!

Please add in the new release also these fixes and improvements:
#1956
#1930
#1919
#1872
#1868
#1800
#1796
#1731
#1571

Some have been merged. But there's no need to rush them as we will be releasing with a shorter and more predictable period moving forward.

v0.4.3 is live!