Compiling source code locally

Does anyone know what command I can use to compile the LaTeX source? I get an error stating that I have to use XeLaTeX or LuaTex :(

Ahh, sorry I definitely need to document this somewhere...
Most of the templates just use the normal latex command while a few use xelatex or lualatex. Right now, you can just look at this file and look at the cmd property for each template to see which command you should run. If the template doesn't have a cmd property, that means it is just the normal latex command.


Bug: NPCRetaliationsystem crashes localhost server when killing a goat on the dev map

Description
At first i thought I did something wrong while trying to work on the woolysystem.
But it also happens on the dev map with a freshly downloaded and compiled game as well, but not the regular maps.
Pretty sure last week I did the same thing and this didnt happen.
Reproduction

kill a goat on the dev map, when launching from the bin folder.
Screenshots

Additional context

should have used the search function, someone is already on it and fixing it
https://github.com/space-wizards/space-station-14/pull/21785


[Tests] Enhance KaTeX tests

Enhance test page with support table
Update KaTeX 0.11.1 -> 0.13.3
Custom katex.min.css, add font-display: swap for better performance
Change math option in config.toml to true

Check this page for details.
Notice that although DoIt theme supports all functions provided by KaTeX, some equations need to be typed in an alternative way. Most of the issues are about escape characters.
For example:
\begin{matrix}
   a & b \\
   c & d
\end{matrix}

need to be typed in as
\begin{matrix}
   a & b \\\\
   c & d
\end{matrix}

Also be careful with things like \_, '\t'. To fix these issues need to modify the Markdown parser and is not an easy job, so there is no plan for this currently.


Fixes #931 :fixed what we do text which was blending with background

fixed  what we do text which was blending with background
before

after

Fixes #931
Pls accept this under Hacktoberfest2024.

@Pranavdixit24
Your pull request has been successfully merged! Don't stop here—continue contributing by addressing more issues and aiming to become a top contributor. You can also contribute in my another Repository BuddyTrail which is also under Hacktoberfest
Great contribution to HACKTOBERFEST'24! 🎉


Add Support for Submenus with Dropdowns

It would be nice if there was a feature to toggle submenus with something like:
{{#bs-dropdown as |dd|}}
   {{#dd.button}}Dropdown {{/dd.button}}
   {{#dd.menu as |ddm|}}
     {{#ddm.item}}{{#link-to "index"}}Something{{/link-to}}{{/ddm.item}}
     {{#ddm.submenu as |sub|}}
       {{#sub.toggle}}Special Submenu {{/sub.toggle}}
       {{#sub.menu as |subm|}}
         {{#subm.item}}{{#link-to "index"}}Something else{{/link-to}}{{/subm.item}}
         {{#subm.item}}{{#link-to "index"}}Another thing{{/link-to}}{{/subm.item}}
       {{/sub.menu}}
     {{/ddm.submenu}}
   {{/dd.menu}}
{{/bs-dropdown}}

@directrix1 I'll try to take a look at this over the weekend.
Which e-b and Bootstrap versions are you using? If you're using a recent version of e-b 1.0 alpha, you can run ember bootstrap:info and paste the results here.

Submenus were deliberately removed from Bootstrap in BS3 and were not re-added in BS4. See twbs/bootstrap#6342.
I'm inclined not to support submenus as a result, but would like @simonihmig's opinion on this.

I agree with @srvance on this., let's stick to what Bootstrap itself supports. You would still maybe be able to extend the existing components to make this work within your app, but we won't support this by default.


Switch over to shared Interop.Globalization.cs on Windows

Match CoreCLR refactoring done for invariant culture
Use actual unsafe types in the interop signatures instead of opaque IntPtr
Use Unsafe.As to get a pointer to stack allocated structure instead of allocating GCHandles
Remove use of NativeCallable for enumeration to make the same code work on both CoreRT and CoreCLR. (I have kelp the NativeCallable annotations commented out so that we can switch back to them once C# gets the intrinsics to make it possible.)

LGTM


RoutingError raised in ContentController# not rescued in Rails 4 (not propagated)

I recently upgraded a legacy app from Rails 3 to 4 and CMS 1.8 to 1.12. I've noticed that the code in the app's ApplicationController used to rescue from errors is NOT executed:
rescue_from ActionController::RoutingError, ActiveRecord::RecordNotFound do |exception|
  render template: '/errors/page_not_found', status: 404
end

Instead, I get an error page in Dev env and blank page in Prod.
Here's the code in CMS that raises RoutingError
def page_not_found
  @cms_page = @cms_site.pages.published.find_by_full_path!('/404')

   respond_to do |format|
     format.html { render_page(404) }
   end
rescue ActiveRecord::RecordNotFound
  raise ActionController::RoutingError.new("Page Not Found at: \"#{params[:cms_path]}\"")
end

Does it seem like an issue with CMS or it's an application concern? Hmm, docs for rescue_from say that since Rails version 4.0
Exceptions raised inside exception handlers are not propagated up.

If so, then should we modify page_not_found method to call somehow the global rescue_from (if possible at all)? Or maybe we should remove rescue_from from ContentController ? Or make rescue_from configurable in CMS ?

I ran into this issue as well.  Let me know what you ended up doing.

Here's one proposition wrapped in PR: https://github.com/comfy/comfortable-mexican-sofa/pull/661
Make rescue_from conditional, configurable in initializer.
Alternatively I was thinking about putting the logic to handle "rescue" in a module and include that module in ContentController with the initialiser if possible.

Another solution is to unset the exception handler for ContentController with
Comfy::Cms::ContentController.rescue_handlers.delete(["ActiveRecord::RecordNotFound", :page_not_found])

in your application code (perhaps an initialiser)

Closing as we don't rescue from exceptions in content serving controller.

We ended up using ... ContentController.rescue_handlers.delete ... 2 years ago.
It's great that this CMS project is still under active development, thanks!


Matlab version?

Hi, may I know which version of matlab you are using to run the code?

We have developed and tested the toolkit with MATLAB version 2022a.

I highly recommend using MATLAB version 2022a, as it has been specifically tested and developed with the toolkit in mind. This will ensure that the code runs smoothly and that you can achieve the best possible results.


trivy scan results

Hi, just wanted to drop some feedback (great tool by the way). I've managed to take a look at the Trivy scanning results you provide, as per this image (for an Ubuntu container):

Have you elected to not show the "low" vulnerabilities summary at the top of the screen on purpose? Otherwise, I think it would be useful to a) show it; or b) provide an option to the user to allow them to select which levels of vulnerability to view.
Back to my main point, I've performed the same Ubuntu scan from the command line and I get the format:

which helpfully shows me which package/library, the installed version and if applicable, the version the vulnerability is fixed in. For me, these are particularly helpful columns to have access to (along with CVE number). Is there anyway these could be surfaced to the podman desktop companion UI? It could also be useful to permit the user to select which columns they wish to view?
Thanks!

Hopefully solved in 5.2.0-rc.3, re-open if needed.


Allowing nested output fields

Something like this would be very useful:
class A(dspy.Signature):
    field_1 = dspy.OutputField()
    field_2 = dspy.OutputField()

class B(dspy.Signature):

    input_data = dspy.InputField()
    As = dspy.OutputField(base_signature=A, format="list")

Just use pydantic: https://github.com/stanfordnlp/dspy?tab=readme-ov-file#5-pydantic-types


Support OpenID Connect standard

Would be a great addition to this lib to support OpenID Connect Oauth standard, to configure and provide custom auth providers.

Yes, this would be awesome!

I am using https://authjs.dev/  with my SvelteKit app.
OIDC support really helps adopting nhost managed services

Could this be re-opened? This would be a prerequisite for us to use Nhost :)

@jonlambert let us know if you are interested in contributing this feature

Please keep it open.


Create 1:1 conversation api-- can a conversation be initialized without messaging?

If I create a 1:1 conversation with a user (using here ) and I want to reference that conversation whenever I need to get a user's info using endpoint: {{serviceUrl}/v3/conversations/{conversationID}/members}.
Do I first have to have the bot say something into the conversation. Or just creating it with the api call enough? I just want to make sure because without the bot saying anything I can't see the conversation popup in the conversation list in msteams, and I am unsure if I can use: {{serviceUrl}/v3/conversations/{conversationID}/members}.
(Also I cannot test it because I already created a conversation with my testing users and I can't delete 1:1 conversations.)
Any help would be appreciated. Best

By using this you will get the informatiom to create a conversation. You can create conversation using CreateConversationAsync method. Could you please check this sample? by using this method you will get conversation id in the activity.

@Nikitha-MSFT Thankyou for getting back to me. I just want to clarify one thing. Does this method alone suffice for creating a conversation? I won't need to first message in the conversation with my bot correct? (AKA, can a 1:1 conversation exist even if messages are not sent.)

Yes when you use this method it will create a new empty chat with specified data if you don't send any message using bot. You can store conversation id for further references.

Okay, thanks for the help @Nikitha-MSFT


Use info icon in duplicated cluster names and sids

Edit: Please, validate if the solution is the desired one. I have implemented this based on the issue 479
It basically changes the duplicated name warning icon by a info icon to be less invasive and have less option to confuse the user with the checks or cluster result.
Fix for: https://github.com/trento-project/trento/issues/479

@arbulu89 Thanks much better like this !
I think tho that the teal color is a bit weird for an info tooltip, I would rather use a grey color after the name, wdyt?

rebased and merged manually in 5bfa2ec99cb4399f4a5f9aba5f3d19b8f9d29951


Check the sensor set-up in the robots available and add any sensor needed before data recording (e.g. IMU, VLP-16, etc.)

We can use robot 8 which currently has:

RTK-GPS
2x 2D lasers
3d Lidar (Ouster)
ZED2 : Stereo camera providing depth
IMU

To Do:

Check if the IMU coordinate system is following the ROS convention
Add Intel Real sense

The ZED2 camera needs of an external PC with an nvidia with cuda cores. We should think of providing a more powerful pc to throvald 008 where also bacchus team can work on with the different packages


made .triggerSubmit be agnostic of the actual event argument

This allows a manual function call to triggerSubmit

Looks like this was resolved in #81.


Point integration page URL to production.

Description

Point integration page URL to production.
Motivation and Context

The current URL points to the staging instance.
Creating accounts for all our customers on the staging instance is impractical.

Maintaining passwords for multiple accounts would be confusing.

Instead, I propose we update the URL to point to the production instance.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[X] Documentation fix (typos, incorrect content, missing content, etc.)

Checklist

[X] I have read the contributing document.
[X] My change requires a change to the documentation.
[X] I have updated the documentation accordingly.
[X] I have added tests to cover my changes.
[X] All new and existing tests passed.

@sweeneyskirt-sl, could you please review!
Also, could we bump this page up in the search results? The Visual page is ranked higher, and it's not apparent which webhooks integration page you're on.
Even when you show all results, there's no indication of which product each result is mapped to.
Placing all product integrations on a single landing page before branching off would be helpful!

@kmissoumi , thank you for your submission and great catch! I've just approved and followed up with you via Slack.

moved to new PR: https://github.com/saucelabs/sauce-docs/pull/1137


Remote play latency/bitrate Issues

Just installed latest beta on my steamdeck and getting extreme lag and latency issues. The xbox is wired into a gigabit switch connected to a gigabit router. The steamdeck is accessing 5 feet away from a wifi 6 4 gigabit wireless ap. Searched everywhere and cannot see a solution.

Does the problem go away when you downgrade the version? Also, on which version does it still work without the added latency?

So beta 1 I get the Java error, beta 2 and beta 3 I get this issue. Not sure how I can troubleshoot to show network stat's but feels like the latency is only an issue when the xbox is pushing decent bitrates. Fight night champion is mostly fine, but battlefront tl2 gets huge artifacts and latency spikes. Have the app set to unlimited bitrate but doesn't seem to change much. Any suggestions I'd be happy to try

Very similar setup to the OP. Latency is too high to play fast paced games like halo or sonic, and bit rate drops randomly creating some fun artifacts. Chiaki (ps remote play), oculus link and steam link under the same conditions work perfectly with no noticeable video latency and very minimal compression artifacts.

On Mac, the latest version has noticeable latency/lag however Onecast doesn’t have the same issue with the same setup

On Mac, the latest version has noticeable latency/lag however Onecast doesn’t have the same issue with the same setup

I get the same issue. But on onecast I get stutter/smearing


Add Tsc lint

Abstract
Add typescript linting. It takes type information from jsdoc comments, or is able to deduce it itself
For instance:
function test(hi) {
	return Number.parseInt(hi);
}

Will automatically mark the function as test(hi: any): number.
Added @typescript-eslint/no-floating-promises, the lint will now catch non awaited promises. If the behavior is intentional, .then(()=>{}) can be used.

I encountered that bug in #121 but forgot about it. If we look at the code (in master) we are importing the wallet first and loading the network after that, it only worked because the wallet code was async and the settings code wasn't (and we weren't awaiting), since the scheduler waits for the tick to finish it would execute after the network and work. This is the reason I added no-floating-promises, so we can't have these confusing things that break when you make the function async

Closing as stale


Is it possible to add something to the tune of a condvar to this crate?

With the underlying event_listener mechanism, would it be possible to add a structure like std::sync::Condvar to this crate? I would be willing to implement it if it is.

I would like to see that, yes. @taiki-e what do you think?

I would like to see that, yes. @taiki-e what do you think?

I realized this niche is basically fulfilled by event_listener::Event, so I'm closing this issue.

I realized this niche is basically fulfilled by event_listener::Event, so I'm closing this issue.


Bug - Investigate why 986 Data Elements are orphaned on Prod (and pronbably Stage)

We believe there are 986 homeless Data Elements in Prodcution - and probably Staging (see separate ticket)
We need to work out how this happened - was it a result of:

Manual error (deleting concepts?)
Database or code error
Something else

Homeless elements can be seen in Prod Admin if you go to Concepts page and search 'No Concepts'.
We have a date of 'Mon 5th Aug 2019 15:16:21' when we think they were made homeless
Two examples if needed are: NFTYPE and ToE_CODE, both for year 7.

This has been fixed and released.


Untyped package not moved from vendor directory to custom path

My Github package is a directory of files of no pre-designated type. i.e. it is not a  "type:drupal-theme" or anything. This package's composer.json says:
  {
    "name": "iainhouston/pellucid_configuration",
    "description": "Drupal 8 configuration directory for pellucid_build",
    "extra": {
          "installer-name": "sync"
      },
    "license": "GPL-2.0+",
    "keywords": ["pellucid", "php"],
    "homepage": "https://iainhouston.com",
    "minimum-stability": "dev",
    "authors": [
      {
        "name": "Iain Houston",
        "email"<EMAIL_ADDRESS>      }
    ],
    "require": { }
   }

and the project's composer.json says:
"require": {
    "composer/installers": "^1.0.20",
...
},
...
"extra": {
    "installer-paths": {
     ...
      "web/sites/default/files/config/{$name}/": [  "iainhouston/pellucid_configuration"  ]
    }

}
After I do composer require iainhouston/pellucid_configuration
the package is downloaded but remains in vendor and is not moved to web/sites/default/files/config/sync/
web/sites/default/files/config/ exists and is writable by the user of composer.
BTW Other packages that I keep in GitHub are moved to to the correct "installer-paths" but these do have pre-designated types: "type:drupal-module" and "type:drupal-theme" and "type:drupal-library"
What am I doing wrong?

This project only supports package types named in the readme.  Dynamic types/paths are not supported. https://github.com/composer/installers#should-we-allow-dynamic-package-types-or-paths-no

@sbuzonas, the readme also shows an example as below:
{
    "extra": {
        "installer-paths": {
            "your/custom/path/{$name}/": ["shama/ftp", "vendor/package"]
        }
    }
}

I am reading this as being able to use your own repo that isn't one of the supported package types.

The text above those examples states:

If you are consuming a package that uses the composer/installers you can override the install path with the following extra in your composer.json

Meaning, you have a dependency on a project that requires composer/installers and has a supported package type. This project only acts on a package that it supports. If you control the dependency, there isn't anything preventing you from declaring the wrong type to trick the installer, but that sounds wrong to me. YMMV


Mocking Prisma client for unit testing (typescript client)

Is your feature request related to a problem? Please describe.
Is there a simple way to mock Prisma for unit testing? What are the best practices?
Describe the solution you'd like
For instance it would be neat to be able to create an instance of prisma client with dummy data in memory. Something like that:
import { Prisma } from '@generated/prisma-client';
const db = new Prisma({
  mockData: {users: [{name: "myUser", password: "myUserPassword"}] }
  debug: config.isDev!,
});

export default db;

And we could inject that mocked Prisma instance in the context for unit test purspose and use it like a real Prisma.
Describe alternatives you've considered
At the moment we have to mock every prisma functions like this:
const db = {
  users: args => ({name: "myUser", password: "myUserPassword"}),
  createUser: args => ({...args})
  $exists: {
      users: (args) => true
  }
 ...
}

This would be important for the Go client as well.

+1

Hi @pantharshit00  I am getting circular dependency error while mocking the prisma client, do you happen to know the solution?


Disable Screen Saver / Display Sleep

From e-mail:

Fermata should have the ability to prevent screen saver or display sleep.

This showed up at a concert yesterday - the screensaver activated on the laptop being used for visuals.

Fixed in 1.2


[BUG] Searchable Snapshot not working with an NPE error

Describe the bug
I create a snapshot based on HDFS. When the snapshot is not searchable, it works fine. When I set the snapshot to searchable, it reports error. The opensearch version is 2.9
To Reproduce
Create the repository:
{
  "type": "hdfs",
  "settings": {
    "uri": "hdfs://es1:9000",
    "path": "/searchable_snapshots",
    "conf.dfs.client.read.shortcircuit": "false"
  }
}

create index:
{
  "settings": {
    "number_of_shards": 1,
    "number_of_replicas": 0
  },
  "mappings": {
    "properties": {
      "name": {
        "type": "text"
      },
      "age": {
        "type": "integer"
      }
    }
  }
}

create snapshot:
{
  "indices": "my_index",
  "ignore_unavailable": true,
  "include_global_state": false,
  "partial": false
}

create restore index:
{
  "indices": "my_index",
  "storage_type": "remote_snapshot",
  "rename_pattern": "(.+)",
  "rename_replacement": "restored_my_index"
}

search. The error reports:
{
  "error" : {
    "root_cause" : [ ],
    "type" : "search_phase_execution_exception",
    "reason" : "all shards failed",
    "phase" : "query",
    "grouped" : true,
    "failed_shards" : [ ]
  },
  "status" : 503
}

Error in log:
[2023-08-14T14:36:06,713][WARN ][o.o.c.r.a.AllocationService] [es2] failing shard [failed shard, shard [restored_my_index][0], node[jMJDygdtQC6QqlAi043HUg], [P], recovery_source[snapshot recovery [YpS3Jwc8RROsfw7z1Wn7uQ] from searchable_hdfs_repository:searchable_snapshot/sEJNO-07T2Sc_9sO9b0UYA], s[INITIALIZING], a[id=t7IsZGhZQUKEOn1c4L5GnA], unassigned_info[[reason=ALLOCATION_FAILED], at[2023-08-14T06:36:06.588Z], failed_attempts[4], failed_nodes[[jMJDygdtQC6QqlAi043HUg]], delayed=false, details[failed shard on node [jMJDygdtQC6QqlAi043HUg]: failed recovery, failure RecoveryFailedException[[restored_my_index][0]: Recovery failed on {es2}{jMJDygdtQC6QqlAi043HUg}{leroNMlxRsOMDwkuxlyRcg}{<IP_ADDRESS>}{<IP_ADDRESS>:9300}{dms}{shard_indexing_pressure_enabled=true}]; nested: IndexShardRecoveryException[failed recovery]; nested: NullPointerException[Cannot invoke "org.opensearch.common.unit.ByteSizeValue.getBytes()" because the return value of "org.opensearch.index.snapshots.blobstore.BlobStoreIndexShardSnapshot$FileInfo.partSize()" is null]; ], allocation_status[fetching_shard_data]], message [failed recovery], failure [RecoveryFailedException[[restored_my_index][0]: Recovery failed on {es2}{jMJDygdtQC6QqlAi043HUg}{leroNMlxRsOMDwkuxlyRcg}{<IP_ADDRESS>}{<IP_ADDRESS>:9300}{dms}{shard_indexing_pressure_enabled=true}]; nested: IndexShardRecoveryException[failed recovery]; nested: NullPointerException[Cannot invoke "org.opensearch.common.unit.ByteSizeValue.getBytes()" because the return value of "org.opensearch.index.snapshots.blobstore.BlobStoreIndexShardSnapshot$FileInfo.partSize()" is null]; ], markAsStale [true]]
org.opensearch.indices.recovery.RecoveryFailedException: [restored_my_index][0]: Recovery failed on {es2}{jMJDygdtQC6QqlAi043HUg}{leroNMlxRsOMDwkuxlyRcg}{<IP_ADDRESS>}{<IP_ADDRESS>:9300}{dms}{shard_indexing_pressure_enabled=true}
        at org.opensearch.index.shard.IndexShard.lambda$executeRecovery$30(IndexShard.java:3554) ~[opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.action.ActionListener$1.onFailure(ActionListener.java:88) ~[opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.index.shard.StoreRecovery.lambda$recoveryListener$8(StoreRecovery.java:510) ~[opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.action.ActionListener$1.onFailure(ActionListener.java:88) ~[opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.action.ActionListener.completeWith(ActionListener.java:345) ~[opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.index.shard.StoreRecovery.recoverFromStore(StoreRecovery.java:113) ~[opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.index.shard.IndexShard.recoverFromStore(IndexShard.java:2620) ~[opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.action.ActionRunnable$2.doRun(ActionRunnable.java:88) ~[opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:908) ~[opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52) ~[opensearch-2.9.0.jar:2.9.0]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
        at java.lang.Thread.run(Thread.java:833) [?:?]
Caused by: org.opensearch.index.shard.IndexShardRecoveryException: failed recovery
        ... 11 more
Caused by: java.lang.NullPointerException: Cannot invoke "org.opensearch.common.unit.ByteSizeValue.getBytes()" because the return value of "org.opensearch.index.snapshots.blobstore.BlobStoreIndexShardSnapshot$FileInfo.partSize()" is null
        at org.opensearch.index.store.remote.file.OnDemandBlockSnapshotIndexInput.<init>(OnDemandBlockSnapshotIndexInput.java:107) ~[opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.index.store.remote.file.OnDemandBlockSnapshotIndexInput.<init>(OnDemandBlockSnapshotIndexInput.java:90) ~[opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.index.store.remote.file.OnDemandBlockSnapshotIndexInput.<init>(OnDemandBlockSnapshotIndexInput.java:61) ~[opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.index.store.remote.directory.RemoteSnapshotDirectory.openInput(RemoteSnapshotDirectory.java:77) ~[opensearch-2.9.0.jar:2.9.0]
        at org.apache.lucene.store.FilterDirectory.openInput(FilterDirectory.java:101) ~[lucene-core-9.7.0.jar:9.7.0 ccf4b198ec328095d45d2746189dc8ca633e8bcf - 2023-06-21 11:48:16]
        at org.apache.lucene.store.FilterDirectory.openInput(FilterDirectory.java:101) ~[lucene-core-9.7.0.jar:9.7.0 ccf4b198ec328095d45d2746189dc8ca633e8bcf - 2023-06-21 11:48:16]
        at org.apache.lucene.store.Directory.openChecksumInput(Directory.java:156) ~[lucene-core-9.7.0.jar:9.7.0 ccf4b198ec328095d45d2746189dc8ca633e8bcf - 2023-06-21 11:48:16]
        at org.apache.lucene.codecs.lucene90.Lucene90CompoundReader.readEntries(Lucene90CompoundReader.java:110) ~[lucene-core-9.7.0.jar:9.7.0 ccf4b198ec328095d45d2746189dc8ca633e8bcf - 2023-06-21 11:48:16]
        at org.apache.lucene.codecs.lucene90.Lucene90CompoundReader.<init>(Lucene90CompoundReader.java:67) ~[lucene-core-9.7.0.jar:9.7.0 ccf4b198ec328095d45d2746189dc8ca633e8bcf - 2023-06-21 11:48:16]
        at org.apache.lucene.codecs.lucene90.Lucene90CompoundFormat.getCompoundReader(Lucene90CompoundFormat.java:86) ~[lucene-core-9.7.0.jar:9.7.0 ccf4b198ec328095d45d2746189dc8ca633e8bcf - 2023-06-21 11:48:16]

Host/Environment (please complete the following information):

OS: Centos7

Additional context
Add any other context about the problem here.

If I remove "storage_type": "remote_snapshot" from creating restored index. The restored index can be created correctly. So I am pretty sure it's an error against searchable snapshot feature.

The config file is like:
cluster.name: my-cluster
discovery.type: single-node
node.roles: [ master, data, search ]
node.search.cache.size: 10mb

Thanks @ryanqin01. This looks like a bug with the HDFS integration with the searchable snapshot feature.

Thanks @ryanqin01. This looks like a bug with the HDFS integration with the searchable snapshot feature.

Thanks for reply. I guess is that because "partSize" is a parameter of Amazon S3, but the HDFS integration involves it wrongly?

@ryanqin01 That seems to be the issue. "partSize" isn't specifically a parameter of S3, but for whatever reason it appears not to be set by the HDFS repository. I'm honestly not yet sure whether the HDFS repository is wrong or if it is wrong to assume that field will never be null. This still needs some more investigation.

I believe I have traced the bug to the fact that the searchable snapshot code is not correctly allowing for "partSize" to be null. null is a valid value, as this part size ultimately comes from this chuckSize() property on a repository, which per the contract can be null when no chunking is needed. In practice, it appears the other repository implementations use a very large value as a default, whereas HDFSRepository uses null as the default. The fix should be simple here.
@ryanqin01 Is there any chance you can validate this by supplying the following setting when creating your HDFS repository?
"chunk_size": "5tb"

Any implausibly large value is fine as it will have the effect of "no chunking". This should be useful as a work-around until the fix is made available in a subsequent release.

I believe I have traced the bug to the fact that the searchable snapshot code is not correctly allowing for "partSize" to be null. null is a valid value, as this part size ultimately comes from this chuckSize() property on a repository, which per the contract can be null when no chunking is needed. In practice, it appears the other repository implementations use a very large value as a default, whereas HDFSRepository uses null as the default. The fix should be simple here.
@ryanqin01 Is there any chance you can validate this by supplying the following setting when creating your HDFS repository?
"chunk_size": "5tb"

Any implausibly large value is fine as it will have the effect of "no chunking". This should be useful as a work-around until the fix is made available in a subsequent release.

Hi Andrew，
It's frustrating that some new errors occured:
[2023-08-22T14:57:59,049][WARN ][r.suppressed             ] [es2] path: /restored_my_index/_search, params: {pretty=, index=restored_my_index}
org.opensearch.action.search.SearchPhaseExecutionException: all shards failed
at org.opensearch.action.search.AbstractSearchAsyncAction.onPhaseFailure(AbstractSearchAsyncAction.java:665) [opensearch-2.9.0.jar:2.9.0]
at org.opensearch.action.search.AbstractSearchAsyncAction.executeNextPhase(AbstractSearchAsyncAction.java:373) [opensearch-2.9.0.jar:2.9.0]
at org.opensearch.action.search.AbstractSearchAsyncAction.onPhaseDone(AbstractSearchAsyncAction.java:704) [opensearch-2.9.0.jar:2.9.0]
at org.opensearch.action.search.AbstractSearchAsyncAction.onShardFailure(AbstractSearchAsyncAction.java:473) [opensearch-2.9.0.jar:2.9.0]
at org.opensearch.action.search.AbstractSearchAsyncAction.lambda$performPhaseOnShard$0(AbstractSearchAsyncAction.java:274) [opensearch-2.9.0.jar:2.9.0]
at org.opensearch.action.search.AbstractSearchAsyncAction$2.doRun(AbstractSearchAsyncAction.java:351) [opensearch-2.9.0.jar:2.9.0]
at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52) [opensearch-2.9.0.jar:2.9.0]
at org.opensearch.threadpool.TaskAwareRunnable.doRun(TaskAwareRunnable.java:78) [opensearch-2.9.0.jar:2.9.0]
at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52) [opensearch-2.9.0.jar:2.9.0]
at org.opensearch.common.util.concurrent.TimedRunnable.doRun(TimedRunnable.java:59) [opensearch-2.9.0.jar:2.9.0]
at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:908) [opensearch-2.9.0.jar:2.9.0]
at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52) [opensearch-2.9.0.jar:2.9.0]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
at java.lang.Thread.run(Thread.java:833) [?:?]
The output is like:
{
"error" : {
"root_cause" : [ ],
"type" : "search_phase_execution_exception",
"reason" : "all shards failed",
"phase" : "query",
"grouped" : true,
"failed_shards" : [ ]
},
"status" : 503
}

The repository setting is like:
{
"type": "hdfs",
"settings": {
"uri": "hdfs://es1:9000",
"path": "/searchable_snapshots",
"conf.dfs.client.read.shortcircuit": "false",
"chunk_size": "5tb"
}
}'
The HDFS cluster is a single node cluster on my vm:
[root@es1 bin]# ./hdfs dfs -ls /searchable_snapshots
Found 5 items
-rw-r--r--   1 wing supergroup        424 2023-08-22 14:55 /searchable_snapshots/index-2
-rw-r--r--   1 wing supergroup          8 2023-08-22 14:55 /searchable_snapshots/index.latest
drwxr-xr-x   - wing supergroup          0 2023-08-22 14:55 /searchable_snapshots/indices
-rw-r--r--   1 wing supergroup        234 2023-08-22 14:55 /searchable_snapshots/meta-WnboontfQeOXbJKZMNSUmQ.dat
-rw-r--r--   1 wing supergroup        313 2023-08-22 14:55 /searchable_snapshots/snap-WnboontfQeOXbJKZMNSUmQ.dat

@ryanqin01 It turns out the key interface method that the searchable snapshot feature uses to fetch partial files in not implemented by the HDFS repository. Unfortunately that means HDFS doesn't support searchable snapshots currently. I'm going to look into what it would take to add support and in the meantime update our documentation appropriately.

Closed inadvertently, reopening.


" brew install gnutls openconnect openssl" did not work after installing Homebrew-4.2.0.pkg

brew doctor output
/Users/tzhang> brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: gettext files detected at a system prefix.
These files can cause compilation and link failures, especially if they
are compiled with improper architectures. Consider removing these files:
  /usr/local/homebrew/lib/libgettextlib.dylib
  /usr/local/homebrew/lib/libintl.dylib
  /usr/local/homebrew/include/libintl.h

Warning: Unbrewed dylibs were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected dylibs:
  /usr/local/lib/libgcc_ext.10.4.dylib
  /usr/local/lib/libgcc_ext.10.5.dylib
  /usr/local/lib/libgcc_s.1.dylib
  /usr/local/lib/libgfortran.4.dylib
  /usr/local/lib/libgomp.1.dylib
  /usr/local/lib/libhdf5.8.dylib
  /usr/local/lib/libhdf5_hl.8.dylib
  /usr/local/lib/libnetcdf.18.dylib
  /usr/local/lib/libnetcdff.7.dylib
  /usr/local/lib/libquadmath.0.dylib
  /usr/local/lib/librtmp.dylib
  /usr/local/lib/libstdc++.6.dylib
  /usr/local/lib/libsz.2.0.0.dylib
  /usr/local/lib/libtcl8.6.dylib
  /usr/local/lib/libtk8.6.dylib
  /usr/local/lib/libz.1.2.8.dylib

Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected header files:
  /usr/local/include/H5ACpublic.h
  /usr/local/include/H5Apublic.h
  /usr/local/include/H5Cpublic.h
  /usr/local/include/H5DOpublic.h
  /usr/local/include/H5DSpublic.h
  /usr/local/include/H5Dpublic.h
  /usr/local/include/H5Epubgen.h
  /usr/local/include/H5Epublic.h
  /usr/local/include/H5FDcore.h
  /usr/local/include/H5FDdirect.h
  /usr/local/include/H5FDfamily.h
  /usr/local/include/H5FDlog.h
  /usr/local/include/H5FDmpi.h
  /usr/local/include/H5FDmpio.h
  /usr/local/include/H5FDmulti.h
  /usr/local/include/H5FDpublic.h
  /usr/local/include/H5FDsec2.h
  /usr/local/include/H5FDstdio.h
  /usr/local/include/H5Fpublic.h
  /usr/local/include/H5Gpublic.h
  /usr/local/include/H5IMpublic.h
  /usr/local/include/H5Ipublic.h
  /usr/local/include/H5LTpublic.h
  /usr/local/include/H5Lpublic.h
  /usr/local/include/H5MMpublic.h
  /usr/local/include/H5Opublic.h
  /usr/local/include/H5PLextern.h
  /usr/local/include/H5PTpublic.h
  /usr/local/include/H5Ppublic.h
  /usr/local/include/H5Rpublic.h
  /usr/local/include/H5Spublic.h
  /usr/local/include/H5TBpublic.h
  /usr/local/include/H5Tpublic.h
  /usr/local/include/H5Zpublic.h
  /usr/local/include/H5api_adpt.h
  /usr/local/include/H5overflow.h
  /usr/local/include/H5pubconf.h
  /usr/local/include/H5public.h
  /usr/local/include/H5version.h
  /usr/local/include/fakemysql.h
  /usr/local/include/fakepq.h
  /usr/local/include/fakesql.h
  /usr/local/include/hdf5.h
  /usr/local/include/hdf5_hl.h
  /usr/local/include/itcl.h
  /usr/local/include/itcl2TclOO.h
  /usr/local/include/itclDecls.h
  /usr/local/include/itclInt.h
  /usr/local/include/itclIntDecls.h
  /usr/local/include/itclMigrate2TclCore.h
  /usr/local/include/itclTclIntStubsFcn.h
  /usr/local/include/mysqlStubs.h
  /usr/local/include/netcdf.h
  /usr/local/include/netcdf_aux.h
  /usr/local/include/netcdf_dispatch.h
  /usr/local/include/netcdf_filter.h
  /usr/local/include/netcdf_mem.h
  /usr/local/include/netcdf_meta.h
  /usr/local/include/odbcStubs.h
  /usr/local/include/pqStubs.h
  /usr/local/include/ricehdf.h
  /usr/local/include/szip_adpt.h
  /usr/local/include/szlib.h
  /usr/local/include/tcl.h
  /usr/local/include/tclDecls.h
  /usr/local/include/tclOO.h
  /usr/local/include/tclOODecls.h
  /usr/local/include/tclPlatDecls.h
  /usr/local/include/tclThread.h
  /usr/local/include/tclTomMath.h
  /usr/local/include/tclTomMathDecls.h
  /usr/local/include/tdbc.h
  /usr/local/include/tdbcDecls.h
  /usr/local/include/tdbcInt.h
  /usr/local/include/tk.h
  /usr/local/include/tkDecls.h
  /usr/local/include/tkPlatDecls.h
  /usr/local/include/zconf.h
  /usr/local/include/zlib.h

Warning: Unbrewed '.la' files were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected '.la' files:
  /usr/local/lib/libh5bzip2.la
  /usr/local/lib/libhdf5.la
  /usr/local/lib/libhdf5_hl.la
  /usr/local/lib/libnetcdf.la
  /usr/local/lib/libnetcdff.la
  /usr/local/lib/libsz.la

Warning: Unbrewed '.pc' files were found in /usr/local/lib/pkgconfig.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected '.pc' files:
  /usr/local/lib/pkgconfig/netcdf-fortran.pc
  /usr/local/lib/pkgconfig/netcdf.pc
  /usr/local/lib/pkgconfig/tcl.pc
  /usr/local/lib/pkgconfig/tk.pc
  /usr/local/lib/pkgconfig/zlib.pc

Warning: Unbrewed static libraries were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected static libraries:
  /usr/local/lib/libhdf5.a
  /usr/local/lib/libhdf5_hl.a
  /usr/local/lib/libnetcdf.a
  /usr/local/lib/libnetcdff.a
  /usr/local/lib/libsz.a
  /usr/local/lib/libtclstub8.6.a
  /usr/local/lib/libtkstub8.6.a
  /usr/local/lib/libz.a

Warning: Your Homebrew's prefix is not /usr/local.

Many of Homebrew's bottles (binary packages) can only be used with the default prefix.
Consider uninstalling Homebrew and reinstalling into the default prefix.
It is expected behaviour that some formulae will fail to build in this unsupported configuration.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.

Verification

[X] My "brew doctor output" above says Your system is ready to brew. and am still able to reproduce my issue.
[X] I ran brew update twice and am still able to reproduce my issue.
[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

brew config output
/Users/tzhang> brew config
HOMEBREW_VERSION: 4.2.0
ORIGIN: https://github.com/Homebrew/brew
HEAD: ff899e5b3ff6731208564ef502db237e2627e8ba
Last commit: 6 days ago
Core tap JSON: 24 Dec 17:23 UTC
HOMEBREW_PREFIX: /usr/local/homebrew
HOMEBREW_REPOSITORY: /usr/local/homebrew
HOMEBREW_CELLAR: /usr/local/homebrew/Cellar
HOMEBREW_CASK_OPTS: []
HOMEBREW_DISPLAY: :0.0
HOMEBREW_MAKE_JOBS: 12
Homebrew Ruby: 3.1.4 => /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/3.1.4/bin/ruby
CPU: dodeca-core 64-bit kabylake
Clang: 15.0.0 build 1500
Git: 2.39.3 => /Applications/Xcode.app/Contents/Developer/usr/bin/git
Curl: 8.4.0 => /usr/bin/curl
macOS: 14.2.1-x86_64
CLT: <IP_ADDRESS>.1.1700200546
Xcode: 15.1

What were you trying to do (and why)?
Configure OpenConnect on Linux/macOS for NCEP CAC VPN
What happened (include all command output)?
I have installed latest Homebrew-4.2.0.pkg
but it fails when I want to install some packages, see below.

In file included from verify-high2.c:37:
./../pkcs11_int.h:27:10: fatal error: 'p11-kit/pkcs11.h' file not found
#include <p11-kit/pkcs11.h>
^~~~~~~~~~~~~~~~~~
1 error generated.
make[4]: *** [verify-high2.lo] Error 1
make[3]: *** [install] Error 2
make[2]: *** [install-recursive] Error 1
make[1]: *** [install] Error 2
make: *** [install-recursive] Error 1
What did you expect to happen?
" brew install gnutls openconnect openssl" can succeed.
Step-by-step reproduction instructions (by running brew commands)
/Users/tzhang>  brew install gnutls openconnect openssl
Running `brew update --auto-update`...
==> Auto-updated Homebrew!
Updated 1 tap (homebrew/cask).
==> New Casks
creality-print

Warning: openssl@3 3.2.0_1 is already installed and up-to-date.
To reinstall 3.2.0_1, run:
  brew reinstall openssl@3
==> Fetching gnutls
Warning: Building gnutls from source as the bottle needs:
- HOMEBREW_CELLAR: /usr/local/Cellar (yours is /usr/local/homebrew/Cellar)
- HOMEBREW_PREFIX: /usr/local (yours is /usr/local/homebrew)
==> Downloading https://raw.githubusercontent.com/Homebrew/homebrew-core/3cc33fc9f06a4f83a37a88075a2269ce98840018/Formula/g/gnutl
########################################################################################################################## 100.0%
==> Downloading https://www.gnupg.org/ftp/gcrypt/gnutls/v3.8/gnutls-3.8.2.tar.xz
Already downloaded: /Users/tzhang/Library/Caches/Homebrew/downloads/71b8292530a732bba1ea94a35f8c3977c5cb1b780e81b6e1786152a2eb372033--gnutls-3.8.2.tar.xz
==> Fetching dependencies for openconnect: gnutls and stoken
==> Fetching stoken
==> Downloading https://ghcr.io/v2/homebrew/core/stoken/manifests/0.93
Already downloaded: /Users/tzhang/Library/Caches/Homebrew/downloads/7ef6178c25578d41919bd9775a1ea0c77333661c7194aa0f574525ace45a278d--stoken-0.93.bottle_manifest.json
==> Downloading https://ghcr.io/v2/homebrew/core/stoken/blobs/sha256:8b6a3bb0bc8d471162e70570a9effdc056f007d43eeb6974b452518fe6c4
Already downloaded: /Users/tzhang/Library/Caches/Homebrew/downloads/d7c4ad1161b42bd87553e5085d353a2aaf13622c321ddceeae7198d55f22a86f--stoken--0.93.sonoma.bottle.tar.gz
==> Fetching openconnect
Warning: Building openconnect from source as the bottle needs:
- HOMEBREW_CELLAR: /usr/local/Cellar (yours is /usr/local/homebrew/Cellar)
- HOMEBREW_PREFIX: /usr/local (yours is /usr/local/homebrew)
==> Downloading https://raw.githubusercontent.com/Homebrew/homebrew-core/3cc33fc9f06a4f83a37a88075a2269ce98840018/Formula/o/openc
########################################################################################################################## 100.0%
==> Downloading https://gitlab.com/openconnect/openconnect/-/commit/7512698217c4104aade7a2df669a20de68f3bb8c.diff
##O#-  #
==> Downloading https://gitlab.com/openconnect/vpnc-scripts/-/raw/473d3e810b8fe8223058ab580fac20c53204e677/vpnc-script
Already downloaded: /Users/tzhang/Library/Caches/Homebrew/downloads/1b7f88a9790d37a4934e0a751544ee70c40e345c1b32d97c23da07c45f3a8162--vpnc-script
==> Downloading https://www.infradead.org/openconnect/download/openconnect-9.12.tar.gz
Already downloaded: /Users/tzhang/Library/Caches/Homebrew/downloads/cb27d1442fcaee671e3cbf37db09ef51faac0653757a21fa9df88854fc7f3471--openconnect-9.12.tar.gz
==> ./configure --disable-silent-rules --disable-static --sysconfdir=/usr/local/homebrew/etc --with-default-trust-store-file=/usr
==> make install
Last 15 lines from /Users/tzhang/Library/Logs/Homebrew/gnutls/02.make:
libtool: compile:  clang -DHAVE_CONFIG_H -I. -I../.. -I./../../gl -I./../../gl -I./../includes -I./../includes -I./.. -Wtype-limits -fno-common -Wall -Wbad-function-cast -Wdate-time -Wdisabled-optimization -Wdouble-promotion -Wextra -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-include-dirs -Wmissing-prototypes -Wnested-externs -Wnull-dereference -Wold-style-definition -Wpacked -Wpointer-arith -Wshadow -Wstrict-prototypes -Wuninitialized -Wunknown-pragmas -Wvariadic-macros -Wwrite-strings -Wformat=2 -Wno-missing-field-initializers -Wno-unused-parameter -fdiagnostics-show-option -fno-builtin-strcmp -I/usr/local/homebrew/Cellar/nettle/3.9.1/include -I/usr/local/homebrew/Cellar/libtasn1/4.19.0/include -I/usr/local/homebrew/Cellar/libidn2/2.3.4_1/include -I/usr/local/homebrew/Cellar/p11-kit/0.25.3/include/p11-kit-1 -g -O2 -c verify-high2.c  -fno-common -DPIC -o .libs/verify-high2.o
make[4]: *** [x509.lo] Error 1
libtool: compile:  clang -DHAVE_CONFIG_H -I. -I../.. -I./../../gl -I./../../gl -I./../includes -I./../includes -I./.. -Wtype-limits -fno-common -Wall -Wbad-function-cast -Wdate-time -Wdisabled-optimization -Wdouble-promotion -Wextra -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-include-dirs -Wmissing-prototypes -Wnested-externs -Wnull-dereference -Wold-style-definition -Wpacked -Wpointer-arith -Wshadow -Wstrict-prototypes -Wuninitialized -Wunknown-pragmas -Wvariadic-macros -Wwrite-strings -Wformat=2 -Wno-missing-field-initializers -Wno-unused-parameter -fdiagnostics-show-option -fno-builtin-strcmp -I/usr/local/homebrew/Cellar/nettle/3.9.1/include -I/usr/local/homebrew/Cellar/libtasn1/4.19.0/include -I/usr/local/homebrew/Cellar/libidn2/2.3.4_1/include -I/usr/local/homebrew/Cellar/p11-kit/0.25.3/include/p11-kit-1 -g -O2 -c x509_ext.c  -fno-common -DPIC -o .libs/x509_ext.o
libtool: compile:  clang -DHAVE_CONFIG_H -I. -I../.. -I./../../gl -I./../../gl -I./../includes -I./../includes -I./.. -Wtype-limits -fno-common -Wall -Wbad-function-cast -Wdate-time -Wdisabled-optimization -Wdouble-promotion -Wextra -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-include-dirs -Wmissing-prototypes -Wnested-externs -Wnull-dereference -Wold-style-definition -Wpacked -Wpointer-arith -Wshadow -Wstrict-prototypes -Wuninitialized -Wunknown-pragmas -Wvariadic-macros -Wwrite-strings -Wformat=2 -Wno-missing-field-initializers -Wno-unused-parameter -fdiagnostics-show-option -fno-builtin-strcmp -I/usr/local/homebrew/Cellar/nettle/3.9.1/include -I/usr/local/homebrew/Cellar/libtasn1/4.19.0/include -I/usr/local/homebrew/Cellar/libidn2/2.3.4_1/include -I/usr/local/homebrew/Cellar/p11-kit/0.25.3/include/p11-kit-1 -g -O2 -c email-verify.c  -fno-common -DPIC -o .libs/email-verify.o
libtool: compile:  clang -DHAVE_CONFIG_H -I. -I../.. -I./../../gl -I./../../gl -I./../includes -I./../includes -I./.. -Wtype-limits -fno-common -Wall -Wbad-function-cast -Wdate-time -Wdisabled-optimization -Wdouble-promotion -Wextra -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-include-dirs -Wmissing-prototypes -Wnested-externs -Wnull-dereference -Wold-style-definition -Wpacked -Wpointer-arith -Wshadow -Wstrict-prototypes -Wuninitialized -Wunknown-pragmas -Wvariadic-macros -Wwrite-strings -Wformat=2 -Wno-missing-field-initializers -Wno-unused-parameter -fdiagnostics-show-option -fno-builtin-strcmp -I/usr/local/homebrew/Cellar/nettle/3.9.1/include -I/usr/local/homebrew/Cellar/libtasn1/4.19.0/include -I/usr/local/homebrew/Cellar/libidn2/2.3.4_1/include -I/usr/local/homebrew/Cellar/p11-kit/0.25.3/include/p11-kit-1 -g -O2 -c pkcs7-output.c  -fno-common -DPIC -o .libs/pkcs7-output.o
In file included from verify-high2.c:37:
./../pkcs11_int.h:27:10: fatal error: 'p11-kit/pkcs11.h' file not found
#include <p11-kit/pkcs11.h>
         ^~~~~~~~~~~~~~~~~~
1 error generated.
make[4]: *** [verify-high2.lo] Error 1
make[3]: *** [install] Error 2
make[2]: *** [install-recursive] Error 1
make[1]: *** [install] Error 2
make: *** [install-recursive] Error 1

Warning: Building gnutls from source as the bottle needs:

HOMEBREW_CELLAR: /usr/local/Cellar (yours is /usr/local/homebrew/Cellar)
HOMEBREW_PREFIX: /usr/local (yours is /usr/local/homebrew)

Looks like it installed in the wrong place - will take a look.

This is the first time that I install homebrew by installing ".pkg" file. So I think "Homebrew-4.2.0.pkg" may have issues?

I checked our tests and they seemed to pass. It should have installed to /usr/local/Homebrew rather than /usr/local/homebrew (note the different casing of H), and the CI run on Homebrew-4.2.0.pkg seemed to do so correctly.

/usr/local/Homebrew> ls
CHANGELOG.md		Library/		lib/
CONTRIBUTING.md README.md		manpages/
Caskroom/		bin/			opt/
Cellar/			completions/		package/
Dockerfile		docs/			sbin/
Frameworks/		etc/			share/
LICENSE.txt		include/		var/

Yes,it is installed to /usr/local/Homebrew

Maybe a PATH thing? What does your $PATH look like? Did you use brew shellenv and if so show how you used it.
Also check if -ls -l /usr/local/bin/brew points to the correct casing.

/usr/local/Homebrew> ls -l /usr/local/bin/brew
lrwxr-xr-x  1 tzhang  admin  20 Dec 23 12:08 /usr/local/bin/brew@ -> ../Homebrew/bin/brew

setenv PATH /usr/local/homebrew/bin:$PATH
setenv PATH /usr/local/homebrew/sbin:$PATH

It should work if you do
setenv PATH /usr/local/bin:$PATH
setenv PATH /usr/local/sbin:$PATH

instead

That's my setting in .cshrc file. I do not use "brew shellenv"

setenv PATH /usr/local/bin:/opt/local/bin:/opt/local/sbin:$PATH
I already have the above, should I also add "setenv PATH /usr/local/sbin:$PATH"?

After I have added "setenv PATH /usr/local/sbin:$PATH", and rerun the installation, it causes new errors

MacBook-Pro-2018:~ 97;brew install gnutls openconnect openssl
Warning: your HOMEBREW_PREFIX is set to /usr/local but HOMEBREW_CELLAR is set
to /usr/local/Homebrew/Cellar. Your current HOMEBREW_CELLAR location will stop
you being able to use all the binary packages (bottles) Homebrew provides. We
recommend you move your HOMEBREW_CELLAR to /usr/local/Cellar which will get you
access to all bottles."
Warning: openssl@3 3.2.0_1 is already installed and up-to-date.
To reinstall 3.2.0_1, run:
brew reinstall openssl@3
==> Fetching gnutls
Warning: Building gnutls from source as the bottle needs:

HOMEBREW_CELLAR: /usr/local/Cellar (yours is /usr/local/Homebrew/Cellar)
HOMEBREW_PREFIX: /usr/local (yours is /usr/local)
==> Downloading https://raw.githubusercontent.com/Homebrew/homebrew-core/3cc33fc9f06a4f83a37a88075a2269ce98840018/Formula/g/gnutls.rb
Already downloaded: /Users/tzhang/Library/Caches/Homebrew/downloads/d25e859364926eac20277f254f2b67bbbef4fd2bc28c747f5664771fb66f6fdf--gnutls.rb
==> Downloading https://www.gnupg.org/ftp/gcrypt/gnutls/v3.8/gnutls-3.8.2.tar.xz
Already downloaded: /Users/tzhang/Library/Caches/Homebrew/downloads/71b8292530a732bba1ea94a35f8c3977c5cb1b780e81b6e1786152a2eb372033--gnutls-3.8.2.tar.xz
==> Fetching dependencies for openconnect: gnutls and stoken
==> Fetching stoken
==> Downloading https://ghcr.io/v2/homebrew/core/stoken/manifests/0.93
Already downloaded: /Users/tzhang/Library/Caches/Homebrew/downloads/7ef6178c25578d41919bd9775a1ea0c77333661c7194aa0f574525ace45a278d--stoken-0.93.bottle_manifest.json
==> Downloading https://ghcr.io/v2/homebrew/core/stoken/blobs/sha256:8b6a3bb0bc8d471162e70570a9effdc056f007d43eeb6974b452518fe6c4162f
Already downloaded: /Users/tzhang/Library/Caches/Homebrew/downloads/d7c4ad1161b42bd87553e5085d353a2aaf13622c321ddceeae7198d55f22a86f--stoken--0.93.sonoma.bottle.tar.gz
==> Fetching openconnect
Warning: Building openconnect from source as the bottle needs:
HOMEBREW_CELLAR: /usr/local/Cellar (yours is /usr/local/Homebrew/Cellar)
HOMEBREW_PREFIX: /usr/local (yours is /usr/local)
==> Downloading https://raw.githubusercontent.com/Homebrew/homebrew-core/3cc33fc9f06a4f83a37a88075a2269ce98840018/Formula/o/openconnect.rb
Already downloaded: /Users/tzhang/Library/Caches/Homebrew/downloads/90a66b0c8509a005d3a72b074a40ff76738ba48b2f8849e1a6547c95169d2d8d--openconnect.rb
==> Downloading https://gitlab.com/openconnect/openconnect/-/commit/7512698217c4104aade7a2df669a20de68f3bb8c.diff
##O=#   #
==> Downloading https://gitlab.com/openconnect/vpnc-scripts/-/raw/473d3e810b8fe8223058ab580fac20c53204e677/vpnc-script
Already downloaded: /Users/tzhang/Library/Caches/Homebrew/downloads/1b7f88a9790d37a4934e0a751544ee70c40e345c1b32d97c23da07c45f3a8162--vpnc-script
==> Downloading https://www.infradead.org/openconnect/download/openconnect-9.12.tar.gz
Already downloaded: /Users/tzhang/Library/Caches/Homebrew/downloads/cb27d1442fcaee671e3cbf37db09ef51faac0653757a21fa9df88854fc7f3471--openconnect-9.12.tar.gz
Error: An exception occurred within a child process:
RuntimeError: /usr/local/opt/pkg-config not present or broken
Please reinstall pkg-config. Sorry :(

rm -r /usr/local/Homebrew/Cellar /usr/local/Homebrew/opt will probably fix it. Will uninstall the formulae that you've already installed but that's ok.

Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
Hide these hints with HOMEBREW_NO_ENV_HINTS (see man brew).
==> Installing dependencies for openconnect: stoken
==> Installing openconnect dependency: stoken
==> Downloading https://ghcr.io/v2/homebrew/core/stoken/manifests/0.93
Already downloaded: /Users/tzhang/Library/Caches/Homebrew/downloads/7ef6178c25578d41919bd9775a1ea0c77333661c7194aa0f574525ace45a278d--stoken-0.93.bottle_manifest.json
==> Pouring stoken--0.93.sonoma.bottle.tar.gz
🍺  /usr/local/Cellar/stoken/0.93: 16 files, 270.2KB
==> Installing openconnect
==> Pouring openconnect--9.12.sonoma.bottle.1.tar.gz
==> Caveats
A vpnc-script has been installed at /usr/local/etc/vpnc/vpnc-script.
==> Summary
🍺  /usr/local/Cellar/openconnect/9.12: 57 files, 3.4MB
==> Running brew cleanup openconnect...
Removing: /Users/tzhang/Library/Caches/Homebrew/openconnect--patch--8a26be2116b88bf9ad491b56138498a2a18bd80bb081e90a386ee8817a1314c3.diff... (688B)
==> Running brew cleanup<EMAIL_ADDRESS>Removing<EMAIL_ADDRESS>(1.4KB)
==> Caveats
==> gnutls
Guile bindings are now in the guile-gnutls formula.
==> openconnect
A vpnc-script has been installed at /usr/local/etc/vpnc/vpnc-script.

Bo98,
I have done the following:

add in .cshrc
setenv PATH /usr/local/bin:/usr/local/sbin:/opt/local/bin:/opt/local/sbin:$PATH
rm -r /usr/local/Homebrew/Cellar /usr/local/Homebrew/opt
a) Is the above information correct for installation?
b) what causes my problem? Thanks a lot

By the way, why I can list "Downloads" directory now after I install homebrew, see below.
Thanks
/Users/tzhang/Downloads> ls -la
total 0
ls: .: Operation not permitted
/Users/tzhang/Downloads>

Sorry, I can not list "Downloads" folder now.

That all looks correct - everything should be working fine now.

Is the above information correct for installation?

Yes. The rm -r was only because of the previous broken state - it was just to reset Homebrew.

what causes my problem? Thanks a lot

The incorrect /usr/local/homebrew/bin PATH you had before seems to confuse the install prefix detection - there's maybe something we can do on our side to prevent that from happening, not sure.

I do not know what happened, I just add "/usr/local/sbin" to $PATH
Below is my .cshrc settings for re-running the installation package,
Thanks for your help. Happy Holiday!
setenv PATH /usr/local/bin:/usr/local/sbin:/opt/local/bin:/opt/local/sbin:$PATH
setenv PATH /usr/local/Homebrew/bin:$PATH
setenv PATH /usr/local/Homebrew/sbin:$PATH

Hi Bo98,
My issue is almost done, I open a new ticket to discuss certificate issue using "openssl" of Homebrew. see
https://github.com/orgs/Homebrew/discussions/5009
Do you know what's problem?
Thanks


Bitso Websocket Implementation

Has anybody implemented websocket functionality for Bitso, or is anybody working on it right now? I might take a crack at it, if not.

I haven't heard of anyone working on it.

Streaming now dropped in this lib: https://github.com/timmolter/XChange/issues/1235


LOGOUT_URL doesnot work if its not HTTPS & SLO (Single log out) messages not being sent.

Hi, I got Single Sign-On working with different python apps in different virtual environments. Its combination of django-mama-cas as a server, and django-cas-ng on the clients. SSO is piece of cake. 9I referred the documentation and this article  as well.
But, I have noticed that on Logout from one app, I am still Signed into the other apps. On the terminal (after running manage.py runserver), I see that the SLO (Single log out) messages are not sent to any other app if the LOGOUT_URL is not HTTPS.
But, when I set LOGOUT_URL = 'https://', it tries to send the Logout message. But, since I am running in development environment, so I get the following error:

requests.exceptions.ProxyError: HTTPSConnectionPool(host='<IP_ADDRESS>', port=9898): Max retries exceeded with url: /admin/callback (Caused by ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 403 Forbidden',)))

That most likely due to the self-signed SSL certificates.
Can you please tell me if this is the desired behavior to have LOGOUT_URL as HTTPS? And, any specific procedure to look at the logs of django-mama-cas only which will help to troubleshoot this?

FYI I am using:

django-mama-cas==2.3.0 (as server)
django-cas-ng==3.5.8 (on the client side)

Hi @amanjots,
Of course you want HTTPS every time sensitive information like tokens or cookies travel across the network.
I'd say it is trying to use a proxy and it is not configured correctly, or you are not listening on the 443 port, I mean, it doesn't look like a CAS problem, but a network configuration problem.

@manelclos I agree that sensitive information should be HTTPS. But my question is that in a development environment, where it may or may not be possible to have HTTPS all the time, does django-mama-cas still needs HTTPS in LOGOUT_URL?

I tried to trace all the django requests being sent or received. with django-request. And, I found that when a user clicks on Logout, he is logged out of the app, but there is no POST request sent for SLO messages to the other apps. So, user remains signed in the other apps.

I don't think so. I'll try to do some testing using the repository from https://github.com/jbittel/django-mama-cas/issues/59 to check for both issues.

Ops, previous response if for previous comment. About your new comment, I think there is some bad configuration on your side.

Can you check that in the client you are using
CAS_LOGOUT_COMPLETELY = True
CAS_VERSION = '3'

and that you have this in your urls.py?
from django_cas_ng import views as cas_views

urlpatterns = [
    ...
    url(r'^accounts/login/$', cas_views.login, name='login'),
    url(r'^accounts/logout/$', cas_views.logout, name='logout'),
    url(r'^admin/logout/$', cas_views.logout),
    ....

@manelclos  yes the client has settings (CAS_LOGOUT_COMPLETELY = True & CAS_VERSION = '3'). In the URLs of the first django virtual environment, the Wagtail's admin authentication is to be handled by the django-ng-cas client, so the urls are:
    url(r'^admin/login/$', cas_views.login, name='cas_ng_login'),
    url(r'^admin/logout/$', cas_views.logout, name='cas_ng_logout'),
    url(r'^accounts/callback$', cas_views.callback, name='cas_ng_proxy_callback'),

And, the third virtual environment is having django-helpdesk, and to use CAS for its authentication I have changed the url's to following:
    url(r'^login/$', cas_views.login, name='cas_ng_login'),
    url(r'^logout/$', cas_views.logout, name='cas_ng_logout'),
    url(r'^accounts/callback$', cas_views.callback, name='cas_ng_proxy_callback'),

As per this tutorial   , the callback "url processes logout request that comes from the CAS server." That's why I have used it in this way, and have also tried 'admin/callback' or 'accounts/callback' or even commenting it out as well.
In the above config, single sign-on works perfectly fine. But, single log out doesn't work at all.

I've never used the callback setting in urls.py.

@manelclos: I have tried without callback setitngs also, and SLO still doesn't work.
Can you please share the settings (from settings.py) and URLs of django-mama-cas and django-cas-ng that works for you?

Hi @amanjots, I got some time today for testing this. Maybe you are missing this on the settings.py of the server (mama_cas):
MAMA_CAS_ENABLE_SINGLE_SIGN_OUT = True

I've fixed the SSO and SLO configurations so they are working in this example: https://github.com/manelclos/django-cas-test
See that when you log out from "cas_client" (app1) the cookie for the cas_server is deleted and also the one for "cas_client" (app1). "second_client" (app2) cookie is not deleted until you access "second_client" again.
Let me know if you get it working with the example repository.

@manelclos Thanks a lot for your reply and providing the example. Have you tested django-mama-cas server with 'MAMA_CAS_SERVICES'
because the way you have configured CAS server it is operating in "open mode".
So can you once check if you configure 'MAMA_CAS_SERVICES' in settings.py of cas server, does it work properly? If you can update the config after testing this, that will really help to resolve the issue. Thanks again. :)

Yes, it was working also with MAMA_CAS_SERVICES, I removed it before
commiting to make it even simpler.

@manelclos Thanks again. Can you please add 'MAMA_CAS_SERVICES' configuration that you tested to be working to https://github.com/manelclos/django-cas-test ?

Sure thing, see here: https://github.com/manelclos/django-cas-test/commit/f1b1dd9509986bb6bbe62f601952fafb97ca723f
On the server you can check:
$ python manage.py checkservice http://<IP_ADDRESS>
Invalid service: http://<IP_ADDRESS>

$ python manage.py checkservice http://<IP_ADDRESS>:8001
Valid service: http://<IP_ADDRESS>:8001
  Proxy allowed: True
  Logout allowed: True
  Logout URL: None
  Callbacks:

@amanjots is this issue fixed?

@manelclos I will have to do the testing again soon. Actually, the project structure that I was working on is changed completely. So, I will have to setup my separate project to test this issue. Kindly allow me few days to ensure this issue is resolved. Thanks.

Thanks for the description - from this thread I figured out how to make this mama-client thing going. For me also does not work the single log out in local development mode if I use http protocol. I'll check on staging, if it works with https.
Manel, ( @manelclos ) I have a multi-language multi-domain site. I have - as you suggested:
settings.py:
MAMA_CAS_ENABLE_SINGLE_SIGN_OUT = True
CAS_LOGOUT_COMPLETELY = True
CAS_VERSION = '3'

urls.py:
    path('accounts/', include('django.contrib.auth.urls')),
    url(r'^cas/', include('mama_cas.urls')),
    path('accounts/login', django_cas_ng.views.LoginView.as_view(), name='cas_ng_login'),
    path('accounts/logout', django_cas_ng.views.LogoutView.as_view(), name='cas_ng_logout'),
    url(r'^admin/logout/$', django_cas_ng.views.LogoutView.as_view()),

first I log in on Site1
then I go to Site2 and get automatically logged in
now I log out on Site2
expect to get logged out on Site1 but I stay logged in.

What am I missing?

Ok, now I've figured out.
For that MAMA CAS has to be said where to say good bye (it is done using the MAMA_CAS_SERVICES config variable) and the client has to provide a place for calling back (in case of DJANGO_CAS_NG it is CallbackView - they recommend setting "/acconts/callback" as AP).

@BarnabasSzabolcs  do you mean 'LOGOUT_URL': 'http://<IP_ADDRESS>:80/accounts/callback' in the MAMA_CAS_SERVICES?
thanks，I have the same problem.

yes. My solution was to put my server behind nginx, locally.

The fact that request.user is AnonymousUser in the LogoutView function means that the logout_user(request) function will not be executed, resulting in a single logout failure, but I can't find a solution.

@BarnabasSzabolcs
thanks，I will configure nginx and try again, only change 'LOGOUT_URL' doesn't work.

Ah, one more thing: with nginx I use mkcert https://github.com/FiloSottile/mkcert to generate local ssh certificates.
ssl_certificate /full/path/to/mypage.test-fullchain.pem;
ssl_certificate_key /full/path/to/mypage.test-key.pem;

@BarnabasSzabolcs  Oh, I know my problem. I guess I forget to add 'django.middleware.clickjacking.XFrameOptionsMiddleware' in client app's setting.MIDDLEWARE. After that I can single-logout.
I haven't install nginx
this is my logout url:
Request URL: http://<IP_ADDRESS>:8000/logout?service=http%3A%2F%2F<IP_ADDRESS>%3A8000%2F
Request Method: GET
Status Code: 302 Found
Remote Address: <IP_ADDRESS>:8000
#setting.py        server
MAMA_CAS_SERVICES = [
{
'SERVICE': 'http://<IP_ADDRESS>:8000',
'CALLBACKS': [
'mama_cas.callbacks.user_model_attributes',
],
'LOGOUT_ALLOW': True,
'LOGOUT_URL': 'http://<IP_ADDRESS>:8000/accounts/callback',
'PROXY_ALLOW': True,
# 'PROXY_PATTERN': '^https://proxy.example.com',
},
{
'SERVICE': 'http://<IP_ADDRESS>:8000',
'CALLBACKS': [
'mama_cas.callbacks.user_model_attributes',
],
'LOGOUT_ALLOW': True,
'LOGOUT_URL': 'http://<IP_ADDRESS>:8000/accounts/callback',
'PROXY_ALLOW': True,
# 'PROXY_PATTERN': '^https://proxy.example.com',
}
]
#setting.py         client
ALLOWED_HOSTS = ['<IP_ADDRESS>']
CAS_SERVER_URL = 'http://<IP_ADDRESS>:8000'
CAS_VERSION = '3'
CAS_APPLY_ATTRIBUTES_TO_USER = True
CAS_LOGOUT_COMPLETELY = True
AUTHENTICATION_BACKENDS = (
'django.contrib.auth.backends.ModelBackend',
'django_cas_ng.backends.CASBackend',
)

Hello, I have a problem in making a logout system using mama cas, I can't get service at the login URL after logging out.
How to get service in URL when logout using mama cas?


Remove version: Strem.App version 0.9.32

This version is older than what has been set in max-versions-to-keep by the publisher.
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/strem-app/strem/releases/download/0.9.x014/Strem-0.9.32.zip
OK
(Automated message - build 924)

#204285


UofT DSI | Visualization - Assignment 2

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Assignment 2 submission.
What did you learn from the changes you have made?
I learnt to critically assess visualization, based on the materials covered in class, and think of ways to improve them.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
N/A
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
N/A
How were these changes tested?
N/A
A reference to a related issue in your repository (if applicable)
N/A
Checklist

[X] I can confirm that my changes are working as intended

A2 pass

Thank you Amanda, I'll close the Pull Request now.


 elements have type="button" missing, causing autosubmitting forms

Hey, thanks for the library!
I have just run into an edge case. My <Importer> is inside a <form>, so since the default type for buttons is "submit" and there is no type defined for the button IconButton, it tries to submit my form whenever I change the page while mapping fields.
I can work on a PR to define type="button" to stop auto-submitting forms if you would like. I currently am catching the faulty submits in my onSubmit function using a flag.

Oh that's a mistake on my part for sure! Thanks for reporting it, I should be able to make a PR by Monday ish.

Np, thanks for the fix!

Released in v0.8.0.


Change update orchestration to use systemctl

We were using rebootmgr, but with that service disabled
we now need to use systemctl.
Salt has a bug where it will mark any call to system.reboot as
failed when a system actually reboots, so we cannot use the
built-in salt methods.
See saltstack/salt#24297 and saltstack/salt#31557

So does systemctl reboot exactly the same as rebootmgrctl reboot now?

@inercia yes - it triggers a reboot straight away - but the minion has enough time to return the status code.

@kiall / @flavio - can we merge this with out e2e tests? It will not get used by e2e tests. We are just replacing the call to a salt module with a call to the raw command.

Going to see how concourse reacts to a close + reopen.


[yarn] Install fails for yarn versions > 1.x

Apparently yarn can no longer be installed via the yarn npm package (only version 1.x). The
install script for yarn and yarn slim fails if one tries to install it for e.g. version 3.2.2.
https://yarnpkg.com/getting-started/install
We noticed that issue when using renovate with binarysource = install, hence I'm not sure
if the issue fits here.

yarn V2+ can't installed via npm. you need to install yarn v1 or use corepack.
i suggest to use corepack and yarn V3+.
please open a discussion in main renovate repo for more questions.


Use tag as name if not provided

:white_check_mark: Build vswhere 2.2.9+g274ba321e0 completed (commit https://github.com/Microsoft/vswhere/commit/274ba321e0 by @heaths)


Bug: In the latest image I am unable to cache the images in the local disk

I am using the
docker run -v /tmp/ttt:/tmp/imageproxy  -p 8080:8080 willnorris/imageproxy -addr <IP_ADDRESS>:8080 -cache /tmp/imageproxy this command and executing the images on port :8080 but I am unable to find any cached results in the directory path /tmp/ttt. Can I know how to fix it? I am able to cache the results with docker image with tag v0.8.0.

chmoding inside the image doesn't make a difference (which makes sense).  The most straightforward way seems to be to create the cache directory ahead of time, and make sure the container is running as a user which has write access to that directory.
So for example, to create the directory and run the container as your current user:
# make cache direct, and ensure it is owned by current user in case it already existed
mkdir /tmp/ttt && chown $(whoami) /tmp/ttt
docker run -u $(id -u) -v /tmp/ttt:/tmp/imageproxy -p 8080:8080 willnorris/imageproxy:v0.9.0 -addr <IP_ADDRESS>:8080 -cache /tmp/imageproxy -verbose

So this all seems to be working as intended (from a docker permission perspective), it's just a little surprising since we changed how the container runs.  I'll see about updating the docs to make this clearer.

Hi,
I've configured imageproxy with docker-compose but I am not able to see any images being served from cache.
My Config:
  imageproxy:
    image: ghcr.io/willnorris/imageproxy
    restart: "unless-stopped"
    container_name: "imageproxy"
    user: "1000"
    volumes:
      - "./data/imageproxy/cache:/tmp/imageproxy"
    env_file:
      - "./config"

My config file:
# Image Proxy

IMAGEPROXY_ADDR=<IP_ADDRESS>:8080
IMAGEPROXY_CACHE=/tmp/imageproxy

I've created the cache folder as user 1000, but its still not writeable. How can I verify that the configuration is correct? With -verbose enabled I dont see any file writing issues/exceptions.


Fix external cross reference

@yannanwang1,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/azure-docs-sdk-python, working directory: W:\yxaz-s, target branch: opendev, target branch commit: c2a7b5fd82b7e3f007c5bf65613b70c3dfc008e6, source branch: yannan/dev, source branch commit: .

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


[Feature req][3.5] Add anchor/link attribute for all columns

I've been creating a lot of custom columns that are identical to the standard ones provided with Backpack except that I'm making the contents links elsewhere in the project.
Was thinking it would be a nice addition to have an optional 'href' => '/some/link' and 'href_text' => 'Text for link' parameters on all columns with a corresponding @if() in the blade file to easily add links to any column (or at least the ones that make sense, probably wouldn't with a column that outputs an array/list)
Definitely would add it too:

date/datetime (may want to link to the date on a calendar)
image (could link to a zoomed in version, or anywhere else)
model_function/model_function_attribute
number
radio
text
select
video

There may be some others that make sense too that I missed

Hmm…. I believe image and email already have anchors.
But I think it’s a great idea for ALL columns to have the posibility to have anchors, yes. Some would have a sensible default link, because it makes sense, some will not. And that should keep the backwards-compatibility.
I think that’s a great idea. My thoughts on it:

I like href, but it might also be useful to specify the target; you might want some links to open in the same page, others in another tab; so it would be useful to also be able to specify that; I don’t know what else it would make sense to specify on this anchor element, but since we already have two attributes, it would probably make sense to just allow the developer to specify any attribute his heart desires; so maybe an anchor attribute, which is an array of href, target and whatever else the developer wants would allow the most customization; this would also open up the possibility of styling the contents of a cell depending on its content - if you can specify a class or style attribute on the anchor; so you can maybe have green labels for good stuff using class=‘label label-success’, red labels for bad stuff, things like that;
For the href at least, the value will most likely need to be a closure, so that the developer specifies how to construct the URL (since it should be different for each entry); so for each anchor attribute, we should probably allow two types of content: text (will just output it) and closure (will run it, then show the output);

So I think this feature could look something like this:
// custom anchor around an image
$this->crud->addColumn([
    'name' => ‘image',
    'label' => ‘Image',
    'type' => ‘image’,
    'anchor' => [
        'href' => function($entry, $column, $crud) {
             return asset('user/images/'.$entry->hash.'png');
         },
        'target' => '_blank',
        'class' => 'img img-rounded',
    ],
]);

// custom anchor around a text, that turns it into a label
$this->crud->addColumn([
    'name' => ’status',
    'label' => ’Status',
    'type' => ’text’,
    'anchor' => [
        'href' => '',
        ‘class' => function($entry, $column, $crud) {
             if ($entry->status == ‘good’) { return ‘label label-success’; }
             if ($entry->status == ‘bad’) { return ‘label label-danger’; }
             return ‘label label-default’;
         },
    ],
]);

// custom anchor around a relationship, that links to that entry
$this->crud->addColumn([
   // 1-n relationship
   'label' => "Parent", // Table column heading
   'type' => "select",
   'name' => 'parent_id', // the column that contains the ID of that connected entity;
   'entity' => 'parent', // the method that defines the relationship in your Model
   'attribute' => "name", // foreign key attribute that is shown to user
    'anchor' => [
        'href' => function($entry, $column, $crud) {
             if (!entry) { return ‘'; }
             return backpack_url(‘users/'.$entry->id);
         },
    ],
]);

I don't think href_text would be useful in any way… In my opinion, the href text should be the actual column content, shouldn’t it? And specifying it from the controller would just make it the same text for all columns, which would defeat the purpose of the column. Please correct me if I’m wrong.

What do you think @redf150flames ? Anybody else? Let’s see if we can make this as good as possible before implementation.

@Laravel-Backpack/veterans - thoughts?

@tabacitu glad to hear you agree with the idea! Sorry it took a while to get back, been a busy week.

I agree with specifying target and class, I left it off in my original trying to keep things as simple as possible, so maybe it could be optional as well?
I used href_text for my custom column when I initially made this feature request. but ended up removing it, so yes, that is unnecessary.

I think this is a must have feature. I find myself creating columns from model functions to return anchors to the linked entitites. Thanks.

Did you add this feature or not yet? I searched the docs but couldn't find anything related.
I want to link to another model or discussion->user(), and there are many other use cases I will need this feature for.
Should I do it manually?

@MostafaAttia - no, it's not implemented yet. Best to go ahead and create a custom column type for your use case.

Working example of a column showing "x entries" with link here.
        $this->crud->addColumn([
            'type' => 'relationship_count',
            'name' => 'snippets',
            'label' => 'Snippets',
            'suffix' => ' snippets',
            'link' => function($entry) {
                return backpack_url('creator/'.$entry->id.'/snippet');
            }
        ]);

Maybe someone will find it useful until we push anchors/links to all columns.

Going to close this, please keep the discussion on PR #2448
Thanks @redf150flames for bring this to our attention.
Best,
Pedro


Disable Tests causing exit issues during the builds

AK Builds are exiting while running the tests. After going through various builds here is what I found -

Clients which ever aren't closed while running the tests are trying to connect to the broker even when broker got shutdown. And when a gradle worker starts running on the same port which is a system assigned port as gradle by default bind a worker to port:0 and if broker was running previously it starts accepting the connection from the hanging clients and result in MessageIOException and eventually gradle worker starts shutting down with a ConnectException. All the tests expect MetadataQuorumCommandTest may be the reason for this.

Whenever the build initiates the shutdown process it starts removing the shutdown hooks and these shutdown hooks can only be removed when all the executing threads were able to gracefully shutdown. But few tests in MetadataQuorumCommandTest aren't able to catch the InterruptSignal and resulting in failure of removing shutdown hooks.

These two issues are mainly contributing for the build failures.

cc @kirktrue since you are interested in getting the CI stable.

@PrasanthV454 thank you for digging into this. Some of these are tests are important enough that we cannot release without them. But they are also making CI fail and hence making it difficult to review code.
May I suggest the following path forward:

Create a ticket for each test that we are disabling here and mark it as "blocker" for 3.6 release
Disable the tests
Fix the tests one by one by resolving the root cause

@PrasanthV454 thank you for digging into this. Some of these are tests are important enough that we cannot release without them. But they are also making CI fail and hence making it difficult to review code.
May I suggest the following path forward:

Create a ticket for each test that we are disabling here and mark it as "blocker" for 3.6 release
Disable the tests
Fix the tests one by one by resolving the root cause

makes sense. I don't have access to create tickets yet(requested for it). @lbradstreet is helping me with this.

@PrasanthV454 what's your JIRA username? I can add permissions now.

@divijvaidya "prasanth" it is.

Added you as a contributor. You should be able to create JIRA now.

@divijvaidya "prasanth" it is.

Ah seems like your JIRA account is not created at all. https://issues.apache.org/jira/secure/ViewProfile.jspa?name=prasanth says "The specified user could not be found."
Did you follow the steps at https://kafka.apache.org/contributing.html, specifically, "Please request a JIRA account using ASF's Self-serve portal. After that you can assign yourself to the JIRA ticket you have started working on so others will notice."

@divijvaidya I did follow the above steps. can you try Prasanth?

A few extra thoughts:

We may be unearthing fundamental limitations with the static Exit API if we can't cleanly/easily force testing-only clusters to not invoke System::exit (or similar methods). It may be more appropriate to develop a non-static API similar to the Time interface so that we can have complete control over our testing clusters
Since https://github.com/apache/kafka/pull/14156 was merged, there have been no test failures on trunk for the testOffsetTranslationBehindReplicationFlow case. We can look into the other failing tests, but this one was the highest-priority because we had reason to believe that it was indicative of legitimate issues with MM2 (and these suspicions proved correct)


projects:ad579x_iio: Add support for AD579x

Release AD579x IIO FW
Checkout no-os, precision-converter-library libraries to latest commit ids, update lib files

Change log:
Add project in the build-projects.yaml part of the Github workflow


Property does not exist on type 'FirebasePlugin'

Bug report
I cannot use many of firebase auth properties for example using signInUserWithEmailAndPassword  return Property 'signInUserWithEmailAndPassword' does not exist on type 'FirebasePlugin';
I am using Ionic V5
Environment information

Cordova CLI version

9.0.0<EMAIL_ADDRESS>

Cordova platform version

Installed platforms: android 8.1.0 browser 6.0.0

Plugins & versions installed in project (including this plugin)

cordova-plugin-androidx 1.0.2 "cordova-plugin-androidx" cordova-plugin-androidx-adapter 1.1.0 "cordova-plugin-androidx-adapter" cordova-plugin-device 2.0.2 "Device" cordova-plugin-firebasex 8.0.0 "Google Firebase Plugin" cordova-plugin-ionic-keyboard 2.2.0 "cordova-plugin-ionic-keyboard" cordova-plugin-ionic-webview 4.1.3 "cordova-plugin-ionic-webview" cordova-plugin-splashscreen 5.0.2 "Splashscreen" cordova-plugin-statusbar 2.4.2 "StatusBar" cordova-plugin-whitelist 1.3.3 "Whitelist"

Related code:
signIn() {
<EMAIL_ADDRESS>'123456',
success => {
console.log( success);
}, error => { console.log(error);}
}

signInUserWithEmailAndPassword() does exist along with the other v8 auth functions - please see the example project for usage examples.
Note that the FirebaseX Ionic Typescript wrapper has not yet been updated to add Typescript mappings for these new functions - please feel free to open an issue against Ionic Native to request that they be added.


[Form Refactor] Request a call page

Coming from the New Expensify Forms design doc, we should refactor RequestCallPage to use the new form component, follow the guidelines below:
Here's an example of a Form refactor: https://github.com/Expensify/App/pull/9056
Guidelines

Replace the form component with Form.js.
Create a unique Onyx key in ONYXKEYS.FORM and pass it as the formID prop to Form.
Pass a validate callback prop.
Pass an onSubmit callback prop that calls the API via an action.
Update all inputs wrapped by Form, following the guidelines in Refactor inputs.
Remove any unused code.

Testing
Verify that:

[ ] UI looks as it did before the refactor
[ ] Values can be added and edited
[ ] Errors are highlighted correctly (input border)
[ ] Error messages show up correctly
[ ] Draft values are saved properly
[ ] Form alerts are displayed correctly
[ ] Clicking the fix the errors link focuses the first input with error
[ ] No duplicate submission of the form occurs (when it's already submitting)

Holding on push to page discussion as per this comment

On hold

On hold

No longer on hold!

Oh sorry, I think the bot's comment shouldn't be here (maybe it's my fault), I just wanted to cite this issue.

@ntdiary no worries! these comments have been all over the place.


Add Picom toggle to Polybar

This toggle allows users with limited system resources to disable/enable Picom on the fly.

Thank you very much, it works like a charm!


Check for basic functionality of a gitlab server

Check for basic functionality of a gitlab server instance. It check for readiness, functionality and health.
Returns 0 or OK in Icinga2 if all services are Ok, else it returns a status code of 2 or CRITICAL in Icinga2.

Thanks for contributing! Just to let you know: We do not support Bash scripts for checks within this project (have a look at CONTRIBUTING for details), but I will take your script and migrate it to our standards for the next milestone.

Can be done via HTTP check:

zones.d/director-global/servicesets.conf
/**
 * Service Set: 116 GitLab
 *
 * assign where "gitlab" in host.vars.custom_tags
 */

apply Service "HTTP - GitLab Liveness" {
    import "116 HTTP"
    import "116-tpl-service-teams-bot"

    notes = "Checks whether the application server is running. This probe is used to know if Rails Controllers are not deadlocked due to a multi-threading."
    assign where "gitlab" in host.vars.custom_tags
    vars.enable_teams_notifications = true
    vars.http_link = true
    vars.http_ssl = true
    vars.http_string = "{\"status\":\"ok\""
    vars.http_uri = "/-/liveness?token=TOKEN"
    vars.http_vhost = "gitlab.example.com"
    vars.notify_teams_bots = [ "Teams Bot GitLab" ]

    import DirectorOverrideTemplate
}

apply Service "HTTP - GitLab Readiness" {
    import "116 HTTP"
    import "116-tpl-service-teams-bot"

    notes = "The readiness probe checks whether the GitLab instance is ready to accept traffic via Rails Controllers. The check by default does validate only instance-checks. If the all=1 parameter is specified, the check also validates the dependent services (Database, Redis, Gitaly etc.) and gives a status for each."
    assign where "gitlab" in host.vars.custom_tags
    vars.enable_teams_notifications = true
    vars.http_link = true
    vars.http_ssl = true
    vars.http_string = "{\"status\":\"ok\""
    vars.http_uri = "/-/readiness?token=TOKEN"
    vars.http_vhost = "gitlab.example.com"
    vars.notify_teams_bots = [ "Teams Bot GitLab" ]

    import DirectorOverrideTemplate
}

apply Service "HTTP - GitLab Readiness DB" {
    import "116 HTTP"
    import "116-tpl-service-teams-bot"

    notes = "The readiness probe checks whether the GitLab instance is ready to accept traffic via Rails Controllers. The check by default does validate only instance-checks. If the all=1 parameter is specified, the check also validates the dependent services (Database, Redis, Gitaly etc.) and gives a status for each."
    assign where "gitlab" in host.vars.custom_tags
    vars.enable_teams_notifications = true
    vars.http_link = true
    vars.http_ssl = true
    vars.http_string = "\"db_check\":[{\"status\":\"ok\"}]"
    vars.http_uri = "/-/readiness?all=1&token=TOKEN"
    vars.http_vhost = "gitlab.example.com"
    vars.notify_teams_bots = [ "Teams Bot GitLab" ]

    import DirectorOverrideTemplate
}

apply Service "HTTP - GitLab Readiness Redis" {
    import "116 HTTP"
    import "116-tpl-service-teams-bot"

    notes = "The readiness probe checks whether the GitLab instance is ready to accept traffic via Rails Controllers. The check by default does validate only instance-checks. If the all=1 parameter is specified, the check also validates the dependent services (Database, Redis, Gitaly etc.) and gives a status for each."
    assign where "gitlab" in host.vars.custom_tags
    vars.enable_teams_notifications = true
    vars.http_link = true
    vars.http_ssl = true
    vars.http_string = "\"redis_check\":[{\"status\":\"ok\""
    vars.http_uri = "/-/readiness?all=1&token=TOKEN"
    vars.http_vhost = "gitlab.example.com"
    vars.notify_teams_bots = [ "Teams Bot GitLab" ]

    import DirectorOverrideTemplate
}

apply Service "HTTP - GitLab Readiness Cache" {
    import "116 HTTP"
    import "116-tpl-service-teams-bot"

    notes = "The readiness probe checks whether the GitLab instance is ready to accept traffic via Rails Controllers. The check by default does validate only instance-checks. If the all=1 parameter is specified, the check also validates the dependent services (Database, Redis, Gitaly etc.) and gives a status for each."
    assign where "gitlab" in host.vars.custom_tags
    vars.enable_teams_notifications = true
    vars.http_link = true
    vars.http_ssl = true
    vars.http_string = "\"cache_check\":[{\"status\":\"ok\""
    vars.http_uri = "/-/readiness?all=1&token=TOKEN"
    vars.http_vhost = "gitlab.example.com"
    vars.notify_teams_bots = [ "Teams Bot GitLab" ]

    import DirectorOverrideTemplate
}

apply Service "HTTP - GitLab Readiness Queues" {
    import "116 HTTP"
    import "116-tpl-service-teams-bot"

    notes = "The readiness probe checks whether the GitLab instance is ready to accept traffic via Rails Controllers. The check by default does validate only instance-checks. If the all=1 parameter is specified, the check also validates the dependent services (Database, Redis, Gitaly etc.) and gives a status for each."
    assign where "gitlab" in host.vars.custom_tags
    vars.enable_teams_notifications = true
    vars.http_link = true
    vars.http_ssl = true
    vars.http_string = "\"queues_check\":[{\"status\":\"ok\""
    vars.http_uri = "/-/readiness?all=1&token=TOKEN"
    vars.http_vhost = "gitlab.example.com"
    vars.notify_teams_bots = [ "Teams Bot GitLab" ]

    import DirectorOverrideTemplate
}

apply Service "HTTP - GitLab Readiness Shared State" {
    import "116 HTTP"
    import "116-tpl-service-teams-bot"

    notes = "The readiness probe checks whether the GitLab instance is ready to accept traffic via Rails Controllers. The check by default does validate only instance-checks. If the all=1 parameter is specified, the check also validates the dependent services (Database, Redis, Gitaly etc.) and gives a status for each."
    assign where "gitlab" in host.vars.custom_tags
    vars.enable_teams_notifications = true
    vars.http_link = true
    vars.http_ssl = true
    vars.http_string = "\"shared_state_check\":[{\"status\":\"ok\""
    vars.http_uri = "/-/readiness?all=1&token=TOKEN"
    vars.http_vhost = "gitlab.example.com"
    vars.notify_teams_bots = [ "Teams Bot GitLab" ]

    import DirectorOverrideTemplate
}

apply Service "HTTP - GitLab Readiness Trace Chunks" {
    import "116 HTTP"
    import "116-tpl-service-teams-bot"

    notes = "The readiness probe checks whether the GitLab instance is ready to accept traffic via Rails Controllers. The check by default does validate only instance-checks. If the all=1 parameter is specified, the check also validates the dependent services (Database, Redis, Gitaly etc.) and gives a status for each."
    assign where "gitlab" in host.vars.custom_tags
    vars.enable_teams_notifications = true
    vars.http_link = true
    vars.http_ssl = true
    vars.http_string = "trace_chunks_check\":[{\"status\":\"ok\""
    vars.http_uri = "/-/readiness?all=1&token=TOKEN"
    vars.http_vhost = "gitlab.example.com"
    vars.notify_teams_bots = [ "Teams Bot GitLab" ]

    import DirectorOverrideTemplate
}

apply Service "HTTP - GitLab Readiness Rate Limiting" {
    import "116 HTTP"
    import "116-tpl-service-teams-bot"

    notes = "The readiness probe checks whether the GitLab instance is ready to accept traffic via Rails Controllers. The check by default does validate only instance-checks. If the all=1 parameter is specified, the check also validates the dependent services (Database, Redis, Gitaly etc.) and gives a status for each."
    assign where "gitlab" in host.vars.custom_tags
    vars.enable_teams_notifications = true
    vars.http_link = true
    vars.http_ssl = true
    vars.http_string = "\"rate_limiting_check\":[{\"status\":\"ok\""
    vars.http_uri = "/-/readiness?all=1&token=TOKEN"
    vars.http_vhost = "gitlab.example.com"
    vars.notify_teams_bots = [ "Teams Bot GitLab" ]

    import DirectorOverrideTemplate
}

apply Service "HTTP - GitLab Readiness Sessions" {
    import "116 HTTP"
    import "116-tpl-service-teams-bot"

    notes = "The readiness probe checks whether the GitLab instance is ready to accept traffic via Rails Controllers. The check by default does validate only instance-checks. If the all=1 parameter is specified, the check also validates the dependent services (Database, Redis, Gitaly etc.) and gives a status for each."
    assign where "gitlab" in host.vars.custom_tags
    vars.enable_teams_notifications = true
    vars.http_link = true
    vars.http_ssl = true
    vars.http_string = "\"sessions_check\":[{\"status\":\"ok\""
    vars.http_uri = "/-/readiness?all=1&token=TOKEN"
    vars.http_vhost = "gitlab.example.com"
    vars.notify_teams_bots = [ "Teams Bot GitLab" ]

    import DirectorOverrideTemplate
}

apply Service "HTTP - GitLab Readiness Gitaly" {
    import "116 HTTP"
    import "116-tpl-service-teams-bot"

    notes = "The readiness probe checks whether the GitLab instance is ready to accept traffic via Rails Controllers. The check by default does validate only instance-checks. If the all=1 parameter is specified, the check also validates the dependent services (Database, Redis, Gitaly etc.) and gives a status for each."
    assign where "gitlab" in host.vars.custom_tags
    vars.enable_teams_notifications = true
    vars.http_link = true
    vars.http_ssl = true
    vars.http_string = "\"gitaly_check\":[{\"status\":\"ok\""
    vars.http_uri = "/-/readiness?all=1&token=TOKEN"
    vars.http_vhost = "gitlab.example.com"
    vars.notify_teams_bots = [ "Teams Bot GitLab" ]

    import DirectorOverrideTemplate
}

apply Service "HTTP - GitLab Readiness Labels" {
    import "116 HTTP"
    import "116-tpl-service-teams-bot"

    notes = "The readiness probe checks whether the GitLab instance is ready to accept traffic via Rails Controllers. The check by default does validate only instance-checks. If the all=1 parameter is specified, the check also validates the dependent services (Database, Redis, Gitaly etc.) and gives a status for each."
    assign where "gitlab" in host.vars.custom_tags
    vars.enable_teams_notifications = true
    vars.http_link = true
    vars.http_ssl = true
    vars.http_string = "\"labels\":{\"shard\":\"default\""
    vars.http_uri = "/-/readiness?all=1&token=TOKEN"
    vars.http_vhost = "gitlab.example.com"
    vars.notify_teams_bots = [ "Teams Bot GitLab" ]

    import DirectorOverrideTemplate
}

apply Service "Systemd Unit - gitlab-runsvdir.service " {
    import "tpl-service-systemd-unit"
    import "116-tpl-service-teams-bot"

    assign where "gitlab" in host.vars.custom_tags
    vars.enable_teams_notifications = true
    vars.notify_teams_bots = [ "Teams Bot GitLab" ]
    vars.systemd_unit_unit = "gitlab-runsvdir.service"

    import DirectorOverrideTemplate
}

apply Service "HTTP - GitLab Certificate" {
    import "116 HTTP"
    import "116-tpl-service-teams-bot"

    assign where "gitlab" in host.vars.custom_tags
    vars.enable_teams_notifications = true
    vars.http_certificate = "25,20"
    vars.http_vhost = "gitlab.example.com"
    vars.notify_teams_bots = [ "Teams Bot GitLab" ]

    import DirectorOverrideTemplate
}

gitlab-liveness and gitlab-readiness are yet to come.


Add GAM regressor and classifier

This could be a good place to start

@ParthivNaresh what's the status of this?

@dsherry I'm having a number of issues with this because of the constant errors that pop up. We can't run GAM against the basic datasets because of its parameters have to be fine tuned for each set otherwise we get errors related to the num_knots. And because of the Java backend I can't dig deeper into the cause and can't check for it.
I have a PR for this #1674 but until I can complete comprehensive enough tests for it, we can add this to the backlog.

Removing myself from this until we can have a broader discussion around GAM and how it should be implemented considering the above mentioned blockers.

I'd be happy to pitch in on this when it rises in the priority queue. :-)
Other H2O-3 stuff it'd be good to have are their GBM, which has some nice features for categorical and NA handling as well as monotonicity constraints, and isolation forests for anomaly detection. There is also a new feature for extracting feature interactions from their GBM and XGBoost extension, which would be great for our AutoML.
When we circle back to this we ought to decide overall what if anything we want to do with H2O-3 integration and make an epic for it.

@dsherry Let's chat about this