Extension Not Activating When Using .NET 6

Describe the bug
When I try to use the .NET 6 SDK, the Ionide extension does not activate.
Once I switch to .NET 7 or 8, it activates.
Steps to reproduce
Use https://devenv.sh/ to manage environment.
# devenv.nix

{ pkgs, ... }:

{
  languages.dotnet = {
    enable = true;
    package = pkgs.dotnetCorePackages.sdk_6_0;
  };
}

Can also manually create a Nix environment with pkgs.dotnetCorePackages.sdk_6_0 being used.
Link to sample reproduction
TODO
Expected behaviour
I expected the extension to activate when using .NET 6.
Screenshots

Ionide Output

As you can see, things seem to look good, but unlike with .NET 7 & 8,
I do not get a [16:00:32 DEBUG] [Main] Activating features message logged after this.
Machine info

OS: Mac
.NET SDK version: 6.0.417
Ionide version: 7.16.1

Additional context
TODO

Just wanted to add that I was also experiencing the same issue, only on Linux instead of macOS. Swapping out .NET 6 for .NET 7, and then uninstalling/reinstalling the extension resolved the issue for me.
That happens to work in my situation so that's good. But is .NET 6 not supported anymore?

Quoting @baronfel https://github.com/ionide/ionide-vscode-fsharp/issues/1961#issuecomment-1893616101

Not supporting 6 is a bug, we'll take a look.

This is also happening for me (VSCode 1.85.2, .net 6.0.126, ionide 7.17.0, linux), the extension never initiates. Previously the extension was taking some time (upwards of a minute) to open in large projects but now doesn't start at all. The F# explorer doesn't show either.
I can recreate on a separate machine (VSCode 1.85.2, .net 6.0.126, ionide 7.17, windows 10) with a fresh install of everything. Upgrading to .net 6.0.418 doesn't affect the issue.
It's also blocking any other commands from running so until the extension is disabled it's not possible to launch the debugger etc. The only workaround I have (changing from .net 6 is not an option) is to disable the extension.

changing from .net 6 is not an option

You mean because your project needs to use .NET 6? If yes, then you can install another version of .NET side by side with the one you have. Ionide should pick up the latest version and your project could be told to use .NET by using a global.json file.
If you can't install another version of .NET for another reason then, you probably need to wait for a bug fix to contributed.

Installing .NET 8 does fix the issue, at least I think so there's other issues with the FS Explorer opening projects that are on a network share.
Is there a feature request for using the .net install tool extension to avoid these issues in the future?

There is in my head, but we're not going to use it for a least a few months. It currently installs an extension-local version of the runtime or SDK, and we want to use a global SDK install - I. E. What the user uses on the command line.
I'm on the team that develops that runtime extension so I'm keenly aware of the use case. We're currently working with the Dev Lot extension to manage global SDK installs, and once that's solid I'll look at integrating it here.

I think we might be hitting https://github.com/dotnet/fsharp/issues/14313


Properly detecting IRCv3.2 capabilities with arguments

For some reason it was stripping the first character of capabilities with arguments, sasl=plain,authcookie,external,ecdsa-nist256p-challenge became asl, plain,authcookie,external,ecdsa-nist256p-challenge.
This breaks SASL on ircv3.2-capable servers

Thanks, I'm not sure how I ever wrote that! Merged.


Python in the read me file

The read me file, as far as I can see, focuses on the command line. I have a dozen WACZ files created to archive Facebook posts of political leaders during COVID, and I'm trying to understand how people could use them in the future beyond uploading them into the browser plugin (which doesn't seem to handle big files very well). Can we use py-wacz to interact with and explore the contents of a WACZ file? Is there any documentation on using archives?

pywacz doesn't offer any tools for exploring archived content.  ReplayWebpage is the primary tool that we make for exploring web archives.
You may be interested in Internet Archive's warc Python library, WACZ files are basically extra data wrapped around WARC files as a ZIP.  If you want a more data-driven approach you might start there.  Additionally, the pages.jsonl file inside the pages directory of the WACZ contains extracted text metadata you may find useful.
Hopefully this answers your question? :)

Thanks. I'll see what I can do with Warcio. For what is worth, we tried uploading the WACZ files into an Archive-It repository so we could use Archives Unleashed tools, but never managed to get it working. Webrecorder is an essential tool to try and capture content on sites that blocks the Internet Archive, but we need to start developing documentation on what to do with the data once it is created. I'm working on a paper that will try to make a start and if there is anyone from your project interested in collaborating, I'd be happy for the help.


Ezcad3 Driver

Initial tests of establishing an ezcad3 dlc-controller driver.
The goal here is to implement the major features that are more or less parallel to those in the ezcad2 lmc-controller. A lot of the controller is weirdly overbuilt and the function set is apparently bordering on being Turing complete.

This PR is more a feasibility study than an honest attempt.
We have nobody with the given hardware controller to test against.

This would absolutely require hardware to complete.


#2512 Multiple lists with same name.

Description

Updated database schema version to add Unique on listName
Add check on listName before adding to resolve backward compatibility

To do in the future : update MaterialDialog deps.
Not done here, because too much work. OFF has been used 24 times.
Need a dedicated Issue and a full test of the app.
Related issues and discussion
#fixes {2512}

Thanks @StephaneC
I just relaunched the 2/4 travis builds.
@brandenfung can you have a look. There's a DB schema change.

@StephaneC it works well for me. The app is blocked on first use, but I don't think it's related (see my latest bug)

Tests are ok.
Something I don't understand but it works :)

I have 2 lists with the same name
I use this fix
I suppose that some issues should appear with DB as the name is not unique
But it works...

So ok for me


Fixing the invoke save option of redis backups.

The invoke save option for Redis backups is not working. Currently it is using the run command and assuming that this function returns the STDOUT of the shell command.
This is not the case so have replaced the call to run with a standard ruby backtick command.

Good catch! Must've been when we switched to POpen4 that I forgot about the response check, seeing as STDOUT/STDERR only show up during exceptions.
Thanks!


can't build console project in visual studio 2019

i almost done but always got this error: "cannot convert from 'boost::asio::io_service' to 'asio::io_service &'"

Hi, we remove the need for Boost libraries. Can you check if the issue is still there?


AR transactions are not being rolled back when a timeout error is raised

Hey, we are having an issue where large requests timeout, the database changes are handed inside of an ActiveRecord::Base.transaction, however the commits are still happening. There is no rollback. Which is causing issues because it seems like the request just hits a dead wall and commits then throws the timeout error. I have seen this in my development logs.
I have tried the following, rescue app wide rake timeous in the application controller. However this does not work. One odd thing is when this rescue code was not present and timeout time was set the timeout error did trigger a rollback for development, Normally this would be great but after testing on staging commits were still made, regardless. See Log 1 below.
#application controller
rescue_from Rack::Timeout::RequestTimeoutException do |timeout|
    if ActiveRecord::Base.connection.open_transactions > 0
      raise ActiveRecord::Rollback
    end
  end

Any error in raise should also cause a rollback. So why is a rollback not happening.
Is there a way to rollback the db in a transaction when a time error is raised?
Scenarios
I made a simple js endpoint for testing, which just updates a string attribute on a simple model we have.
  def update
    ActiveRecord::Base.transaction do
      @note = Note.find(note_id)
      @note.update(content: permitted_params[:content])

      sleep(permitted_params[:sleep].to_i)
    end

    render json: Note.find(note_id).attributes, status: 200
  end

Log 1 Development logs went like this, when the rescue in application controller was present.
This is currently how our staging and production behave regardless.
 Processing by LargeRequestTimeoutsController#update as */*
   Parameters: {"content"=>"using application transaction", "sleep"=>"35", "id"=>"133117"}
    (1.0ms)  BEGIN
source=rack-timeout id=c98a271671c194dfcd6dae6d453cab4a timeout=10000ms service=1002ms state=active
   Note Load (1.5ms)  SELECT  "notes".* FROM "notes" WHERE "notes"."id" = $1 LIMIT $2  [["id", 133117], ["LIMIT", 1]]
    (0.3ms)  BEGIN
   SQL (0.8ms)  UPDATE "notes" SET "content" = $1, "updated_at" = $2 WHERE "notes"."id" = $3  [["content", "using application transaction"], ["updated_at", "2018-08-22 21:00:29.923092"], ["id", 1111]]
    (3.2ms)  COMMIT
 timeout=10000ms service=2005ms state=active
 timeout=10000ms service=3004ms state=active
 timeout=10000ms service=4001ms state=active
 timeout=10000ms service=5001ms state=active
 timeout=10000ms service=6005ms state=active
 timeout=10000ms service=7001ms state=active
 timeout=10000ms service=8003ms state=active
 timeout=10000ms service=9006ms state=active
 timeout=10000ms service=10005ms state=active
 timeout=10000ms service=10006ms state=timed_out
    (0.7ms)  ROLLBACK
 Completed 500 Internal Server Error in 9065ms (ActiveRecord: 72.3ms)
Rack::Timeout::RequestTimeoutException (Request ran for longer than 10000ms):

Log 2 When the rescue in application controller was NOT

 Processing by LargeRequestTimeoutsController#update as */*
   Parameters: {"content"=>"using application transaction", "sleep"=>"35", "id"=>"133117"}
    (1.0ms)  BEGIN
source=rack-timeout id=c98a271671c194dfcd6dae6d453cab4a timeout=10000ms service=1002ms state=active
   Note Load (1.5ms)  SELECT  "notes".* FROM "notes" WHERE "notes"."id" = $1 LIMIT $2  [["id", 133117], ["LIMIT", 1]]
    (0.3ms)  BEGIN
   SQL (0.8ms)  UPDATE "notes" SET "content" = $1, "updated_at" = $2 WHERE "notes"."id" = $3  [["content", "using application transaction"], ["updated_at", "2018-08-22 21:00:29.923092"], ["id", 1111]]
 timeout=10000ms service=2005ms state=active
 timeout=10000ms service=3004ms state=active
 timeout=10000ms service=4001ms state=active
 timeout=10000ms service=5001ms state=active
 timeout=10000ms service=6005ms state=active
 timeout=10000ms service=7001ms state=active
 timeout=10000ms service=8003ms state=active
 timeout=10000ms service=9006ms state=active
 timeout=10000ms service=10005ms state=active
 timeout=10000ms service=10006ms state=timed_out
    (0.7ms)  ROLLBACK
 Completed 500 Internal Server Error in 9065ms (ActiveRecord: 72.3ms)
Rack::Timeout::RequestTimeoutException (Request ran for longer than 10000ms):

My understanding so far is that ideally large requests should use polling/ background jobs etc., however sometimes things happen.  So Rake-timeout should be a chance to handle a timeout error before Heroku's router 30 sec hard stop. Being set to timeout at ~28 sec.

The shortcomings of rack-timeout are well documented. Please see:
https://github.com/heroku/rack-timeout#further-documentation
Keep in mind it's possible to hit a timeout after the commit has finished. There's also the possibility of other weird threading behavior, roughly a race condition.
You should not need a rescue_from to rollback. This behavior happens automatically in Rails when an exception is raised during a transaction.
There is no way for rack-timeout to detect your app is in the middle of a transaction, and even if there was, I can't see any way to change or improve the behavior, since the goal of rack-timeout is to abort the transaction (both the web and database transaction) if the request is taking a long time.

@wuputah thanks for the quick response, so on our production server, we have the timeout set at 25 seconds.

You should not need a rescue_from to rollback. This behavior happens automatically in Rails when an exception is raised during a transaction.

This is what I thought to, but we are not seeing this. What we are seeing is all db changes up to the point when a  Rack::Timeout::RequestTimeoutException is raised, are committed but no rollback is happening.

Yea, taking a deeper dive it is an issue with our App, our ActiveRecord is wrapping updates in their own transaction so we have an issue with nested transactions, either through a gem or some obscure setting. This is not an issue with rake-timeout, thanks though.

Ah! That's good information for others, thanks for sharing!


Change the key name for page numbers to number

According to the specification (https://jsonapi.org/format/#fetching-pagination) the page number should appear as page[number], not page[page]. This PR fixes it.

This might be a breaking change.

Definitely. I'll think we'll have to support both with a deprecation pathway.

Yet, it is. As @jherdman mentions perhaps include both fields and issue warning somewhere?

@strzibny That's just an example, no actual restriction is put on the contents of the page query param. I'd go with a more radical approach. Completely avoid parsing paging parameters into a struct.

no actual restriction is put on the contents of the page query param

yet the struct won't have this key, no?

Completely avoid parsing paging parameters into a struct.

I like the fact it's parsed, there are not that many variants out there, right?

@strzibny yes, but if the struct stays you should you should be able to configure which query parameters are mapped to which page struct fields. Also, this is tricky because the format of the parameters is also not mandated, so you can't assume they are integers or any other type.
This is why I did #192 but in retrospect I think the best way to address this would be to completely remove the JSONAPI.Page struct and directly use query params to handle this.

Hey friends. After having read over the spec I feel that we can close this issue. As @lucacorti pointed out, the confusion comes from this param being part of an example. The following are the only keys in the pagination family that are prescribed:

first: the first page of data
last: the last page of data
prev: the previous page of data
next: the next page of data

Beyond that there are no prescriptions to the other parameters used.
Therefore I think we should close this ticket. I don't know if I'm ready to toss the Page struct yet, but clearly something needs to be done here.

@jherdman just to confirm, your recommendation is therefore be using page[page] for page number?

The JSON:API spec's section on pagination makes no recommendation for key used for the current page number. The choice is yours!

My point is about the automatic assign:
conn.assigns.jsonapi_query.page.page

I won't have there "number". So if I want it I have to bypass jsonapi_query and do it on my own. Is that what you mean?

That's a great question and I honestly don't have a good answer for you at this time. If you find a work around please post it here. I'll try to free up some time to get the recent flurry of pagination work merged in and released.

@strzibny  I'm working on fixing this in #189, but the current implementation forces you to use that specific query parameter name.


feat: Docz

Switches the markdown renderer from mkdocs to https://docz.site. This new thing is React and Gatsbyjs based, giving us much more possibilities about the rendering. Especially it now uses the vscode highlight engine, so Jsonnet highlighting works.
Furthermore I have written an entire tutorial to get new users started much easier.
PS: Don't worry, the +16k is related to yarn.lock (wtf)

There we go @malcolmholmes, applied your review feedback.
Unfortunately, gatsby and docz seem to crash in Netlify, though I am not sure why, as it works locally. Don't have enough JavaScript knowledge to properly debug :(

Things to be done:

[ ] libraries/import-paths
[ ] libraries/installing-and-publishing

Here's some review thoughts:

On the homepage, we say "used at Grafana for our". I would suggest we say "used at Grafana for their". The reason for "their" is it allows a potential contributor to identify with the project more easily.
We really need 'next/previous' links in the tutorial. It is confusing otherwise working out what page to read next.
The "Import Paths" and "Installing and Publishing" links don't point to pages.


feat: improve function return types

What is the current behaviour?
There are some type errors, and functions return everything with | null, making it difficult for end-users to work with.
What is the new behaviour?
Functions now return type unions, which are more correct and easier to work with.
Additional context
I've labelled this as feat instead of chore as it should be treated as a breaking change because it may show new type errors to existing users.

  ): Promise<
    | {
        data: { message: string }
        error: null
      }
    | {
        data: null
        error: Error // in future we might add Error || OurOwnError
      }
> {
     const data = something
     return { data, error: null }
    } catch (error) {
        if(basicErrorTypeguard(error)) return { data: null, error }
        // In case we would need to add new Error type in future.
        //if(ourOwnErrorTypeguard(error)) return { data: null, error }
        throw error
    }
  }

Reasoning:

If there will be any other error that is not handled by us, we shouldn't return it without a type.
User won't be able to handle it, returning an unknown type as error isn't an option as well as that makes developer experience completely worthless. We might as well return a flag 'isError'

Why this solution:
Typeguard will ensure that we only ever return our 'Error' and users can handle it.
They will get an error in development that will give them information.
Bonus:
Backward compatibility.
With this code it's possible to add new ErrorTypes in future without breaking anything. Its maintanable
Another possible solution (not recommended):
catch (error) {
    const castedError = error as Error
      return { data: null, error }
    }

This will also work, but it will tell the developer that the error is of type 'Error'.
If any other error is thrown, the developer won't get information about it. This is bug prone.
For example:

Developer shows information from the error to user (user of website).
Any other error is thrown that doesn't match 'Error'.
Javascript might crash because of accessing a property that doesn't exist.

Thanks, @Jaaneek!
I agree with your first option more than the second.
The only thing I don't feel great about is returning an error in the object, but having the function also be able to throw... If a user sees that error in the object, my intuition is that all errors would come through that error and not through a try/catch.
I'm keen to hear your thoughts!

@alaister
My proposal:
Create custom error that will format any unknown error
Something like
try {
  throw new Error('Some supabase error')
} catch (error) {
  if (error instanceof Error) return error
// if(error instaceof SomeOtherError) return error
// if(error instaceof AnotherError) return error

return toStorageError(error,Reason.Unknown)
}

const toStorageError = (error:unknown,reason:Reason) => {
if(isErrorWithMessage) return new StorageError(error.message,reason,error)

// We might aswell do:
// return new StorageError('',reason,error)
try {
    return new StorageError(JSON.stringify(maybeError),reason,error)
  } catch {
    // fallback in case there's an error stringifying the maybeError
    // like with circular references for example.
    return new StorageError(String(maybeError),reason,error)
  }
}

export class StorageError extends Error {
  reason: Reason
  originalError:unknown
  constructor(message: string, reason: Reason,originalError:unknown) {
    super(message)
    this.name = 'StorageError'
    this.Reason= status
    this.,originalError: originalError
  }

  }
}

enum Reason {
  Unknown,
  OtherEasons...
}

function isErrorWithMessage(error: unknown): error is ErrorWithMessage {
  return (
    typeof error === 'object' &&
    error !== null &&
    'message' in error &&
    typeof (error as Record<string, unknown>).message === 'string'
  )
}

Why?
It'simportant to let the developer handle the final error.
With introducing 'StorageError' we will let developers always:

See a message
We will let him know the reason behind the error (if we know of that)
Let him handle the final error which will be always unknown.

Suggestions
Name it better, 'StorageError ' might be understood as something that we throw, which is not. We are just wrapping it for developers.
More to read about this pattern
https://kentcdodds.com/blog/get-a-catch-block-error-message-with-typescript
I don't have currently much time to analyze that too much so treat everything above as pseudocode.

I think that PRs #62 and #63 could also be closed and added  here, as they also address the return types for some functions.

@mirceanton, I'll review your PRs now and try and get them in before this goes out. Thank you!

:tada: This PR is included in version 1.8.0-next.1 :tada:
The release is available on:

GitHub release
npm package (@next dist-tag)

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0-rc.1 :tada:
The release is available on:

GitHub release
npm package (@rc dist-tag)

Your semantic-release bot :package::rocket:


Redesign clGetKernelArgInfo (#522)

This PR implements changes to the Harness to make it easier and clearer to determine whether a device supports the half and double data types. This is the same changes as in https://github.com/KhronosGroup/OpenCL-CTS/pull/1055.
The remainder of the PR is a complete redesign of clGetKernelArgInfo. It is split into 2 different commits. The first commit removes the previous tests and the second commit implements the redesign.

Not a thorough review, but please note that 64-bit integer types (long/ulong) are optional for embedded profile, so these should not be tested unconditionally. They should be guarded with checks similar to double and half, e.g. if the device is embedded profile only run them if cles_khr_int64 is supported.

GitHub's review system has apparently made a mess of my review.  If you go to the "Files changed" page rather than viewing the review comments in "Conversation", it should hopefully make more sense.

Hi all,
Are there any further issues with this PR? I'd be happy to make some changes so that this can be merged.
Thanks

Hi all,
Are there any further issues with this PR? I'd be happy to make some changes so that this can be merged.
Thanks

This is a really nice improvement! Just a few nits. I'm not sure how the coverage compares to the original, but it looks pretty complete. Is the run time similar?

Yes, from what I can tell there is very little difference between the runtimes of this and the original version

@bashbaug. I pushed a some changes to address the following:

Sets the alignment/space requirement for Vector3's to take up the same space as Vector4's
Ensures that image args don't have an explicit address qualifier specified.

Please could you verify that it works?
Regarding 3) the test has been tested on a platform which supports pipes but I believe there are a number of issues with different implementations regarding this. I believe @StuartDBrady knows a bit more on the issue

Please could you verify that it works?

Thanks for continuing to look at this, but I'm still seeing a case that is generating too many parameters.  I actually wonder if this has to do with pipes also.  Does the test currently assume that sizeof(pipe char) == sizeof(char)?  If so, I don't think we ever explicitly say this in the spec (and we should!), but it looks like Clang and our implementation treats the size of a pipe as the size of a pointer, so up to 8 bytes: https://godbolt.org/z/8xdbWz
Do we need to open a spec bug to clarify the size of a pipe?
We're currently failing a few other cases too, but at first glance those failures appear to be related to https://github.com/KhronosGroup/OpenCL-Docs/pull/558.

You're right it does assume that sizeof(pipe char) == sizeof(char).
This is addressed in the next patch.
Yes I think it would be worth explicitly stating what the size of a pipe is.

Looks like the remaining failures on our implementation fall into three different categories:

char vs. signed char.  See: https://github.com/KhronosGroup/OpenCL-Docs/pull/558

Arg Type: Expected: char*	 Actual: signed char*
Argument in Kernel Source Reported as:
global   signed char*  argument14

Pipes with scalar types and signed or unsigned type modifiers.

Arg Type: Expected: uchar	 Actual: unsigned char
Argument in Kernel Source Reported as:
private read_only pipe  uchar  argument92

Pipes with vector types.

Arg Type: Expected: char2	 Actual: char __attribute__((ext_vector_type(2)))
Argument in Kernel Source Reported as:
private read_only pipe  char2  argument9

(3) and probably also (2) appear to be due to Clang's handling of pipes.  See: https://godbolt.org/z/cMPP96
!5 = !{!"char __attribute__((ext_vector_type(2)))", !"uint*"}

I'd be curious to know if any implementations that support pipes and use a largely unmodified Clang are able to pass this test.

@bashbaug thank you for your comments, regarding:

Given the confusion and lack of clarity in the OpenCL spec for signed char vs char, and that OpenCL C specifies that a Char is a Signed Char by default, is it acceptable to ignore the "signed char" arguments for the conformance test?

2 & 3) I believe both of these issues are related to Clangs handling of Pipes and a solution is being/has been developed https://reviews.llvm.org/D96151

is it acceptable to ignore the "signed char" arguments for the conformance test?

Yes, I think so, but please monitor the resolution of https://github.com/KhronosGroup/OpenCL-Docs/pull/558.

2 & 3) I believe both of these issues are related to Clangs handling of Pipes and a solution is being/has been developed

Does it make sense to disable the pipe parts of this test by default until this issue is fixed?  We won't be able to pass this test as-is until the Clang solution is complete (and we've had time to integrate it).
I have a few additional pipe-specific comments I'll leave inline in the code as well.

Small update, since it's been a few months:
We're still failing the pipes part of this test due to the Clang issues mentioned above, but we're passing the test otherwise.
Have you given any thought to merging these changes with the pipes part disabled or optional? I don't think anyone that supports pipes and uses Clang will be able to pass this test otherwise. If this test gets merged as-is we'd probably just stop supporting pipes (which, honestly, we've been considering anyhow).

@bashbaug I've disabled the tests in the latest patch. Please let me know if you are still having problems.


Update LlamaCPP?

Describe the bug
When I unpack the old Phi3 ModelKit from GHCR and run kit dev start . everything works.
When I unpack the newer Phi3 ModelKit from Jozu Hub the Dev command fails.
Version
kit version: 0.3.0-1653de5

This wasn't the source of the issue we were seeing with some of the Jozu-built ModelKits. Closing this as not an issue.


Slate Forms Styles

Summary of changes
Add Slate Forms styles for select, input and button (using the UG version of Bootstrap styles as a base)
Frontend

Added Slate Forms styles for select, input and button
Felt slightly ashamed for copying them over in the quickest manner possible (without cleaning them properly)
Promised myself I would clean them up some day

Backend

None

Test Plan
View https://mmtest.gatsbyjs.io/lindas-test-page

Holding off on this until we can stabilize the loading.


Feature Request: Make blur optional

Dear maintainers,
The blur event on textMask directive (link below) causes a warning when used with Ionic, since ionic recommends (ionBlur) event over native (blur) event.

(blur) is deprecated in ion-input, use (ionBlur) instead
Is it possible to make this event configurable (like guide flag)? There can be scenarios where this behaviour is not wanted for other reasons (such as styling).
Do you see a benefit in implementing this option? Would you like me to create a PR?
Thanks!
https://github.com/text-mask/text-mask/blob/0b0b57740c5881ab3cc58fc7135028d644853c66/angular2/src/angular2TextMask.ts#L14

Ionic in general and ion-input in particular are not supported by text-mask. Using blur is part of a standard control value accessor. As ion-input rejects any foreign ControlValueAccessor, which hinders textMask from working correctly, there are no plans to implement any changes to conform to their own API.


[bug] load extension on duckdb 1.1.0 cause error

I'm use duckdb with my python application, after auto package without specify the version of duckdb, so we got duckdb from version 1.0.0 to 1.1.0.
And this sql may cause error:
>>> import duckdb
>>> mem_duck = duckdb.connect()
>>> mem_duck.sql("LOAD '/opt/data/duckdb/extensions/vss.duckdb_extension'")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
duckdb.duckdb.NotImplementedException: Not implemented Error: Enum value: '' not implemented
>>> mem_duck.sql("select version()")
┌─────────────┐
│ "version"() │
│   varchar   │
├─────────────┤
│ v1.1.0      │
└─────────────┘

Hey @Mrzyxing, thanks for raising this!
I think what's happening here is that you are using an extension mean for DuckDB v1.0.0 while you are running DuckDB v1.1.0.
That, combined with a weird bug, lead to this not helpful error message.
The bug is solved, to a degree, by this PR: https://github.com/duckdb/duckdb/pull/13884.
Workaround in your case is either let DuckDB install new extensions (say INSTALL vss; LOAD vss;) or downloading them yourself a new, from URL such as https://extensions.duckdb.org/v1.1.0/YOUR_PLATFORM/vss.duckdb_extension.gz, then performing gzip -d, then doing duckdb -c "LOAD 'vss.duckdb_extension';".
This should offer a workaround, to you or others that have bumped against some similar behaviour.

This has been fixed by https://github.com/duckdb/duckdb/pull/13894 and to some degree by https://github.com/duckdb/duckdb/pull/13885.
Note that the original problem was that you were using incompatible versions of DuckDB library and extension, but this unclear error masked the proper one.


Updated version of dependency builtins to 1.0.1 ( inclusion of console to the built in module list )

Was facing an error while using nexe because console was not added to the list of modules returned by builtins, prior to 1.0.1. This PR updates the builtins dependency to 1.0.1.
Fixes #112

Thanks!


Javascript (Turbo) based navigation breaks OAuth redirects for native apps when the user is not already signed in

I'm working on a desktop app that will auth against my BulletTrain app. Everything works well if the user is already signed in to the BT app, but it doesn't work so well if the user is not signed in.
In the desktop app I click the "sign in" button, and that opens a native browser window to my BulletTrain app at:
/oauth/authorize?
  client_id=xxx&
  redirect_uri=syncbot://auth-return&
  response_type=code

Doorkeeper sees that I'm not signed in and redirects me to /users/sign_in.
I enter my credentials and hit the "Sign in" button.
Javascript on the page makes a POST request to sign me in. The server accepts the credentials and issues a 302 redirect to the original URL:
/oauth/authorize?
  client_id=xxx&
  redirect_uri=syncbot://auth-return&
  response_type=code

The Javascript follows that redirect, and makes a GET request to the /oauth/authorize endpoint.  The authorization on the server side is successful and the server issues a 302 redirect to the redirect_uri specified in the original request, which is syncbot://auth-return. (syncbot:// is a custom protocol that is points back to the desktop app.)
At this point the Javascript attempts to follow the redirect, but is blocked by a CORS issue. This error shows up in the developer console:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at syncbot://auth-return?code=yyy. (Reason: CORS request not http).

Along with with one:

TypeError: NetworkError when attempting to fetch resource.

The app just remains on the login page, making it look like nothing happened. If I click the "sign in" button again (or if I just reload the sign in page) I'm redirected into the BT app with the "you are already signed in" messaging.
At this point I can go back to the native app and click the "sign in" button again, and this time everything works as expected because I'm already signed in and there are no Turbo based navigation steps in that part of the OAuth dance.
I'm not sure if we'd need to completely disable Turbo on the sign in page, or if maybe there's a way to only disable it if we can detect that the destination after sign in is an /oauth related route.

I ejected the devise/sessions/new.html.erb partial and added data: {turbo: false} to the form tag and that gets things working better. Now when I sign in to BT I do get redirected back to the desktop app and authentication is successful.
But the browser window just stays on the sign in page since the ultimate redirect location is outside the browser. I probably need to look at having an intermediate page in the redirect chain that displays a message saying "you signed in and we're redirecting you back to the desktop app, you can close this window".

I got something working that only disables Turbo on the login form for oauth based redirects.
In ApplicationController I did this:
  def user_return_to_is_oauth
    session["user_return_to"].match(/^\/oauth/)
  end
  helper_method :user_return_to_is_oauth

And then in devise/sessions/new.html.erb I added this to the form tag:
data: {turbo: !user_return_to_is_oauth}

Would this be something that you'd be interested in pulling into BT proper? If so, would bullet_train-base be the appropriate repo for a PR?

@jagthedrummer That would be amazing! 🙏

Yes, submit it to bullet_train-base. I can’t remember where devise/sessions/new.html.erb comes from off the top of my head, but you can PR that repo as well and we’ll handle getting the tests passing.

This has been implemented in the sessions controller, which currently fails within the _box layout view in the current version (unable to find method), unless you move this helper block into the application controller.


Impossible move the snake

My snake is stuck at launch, how correct her? thank you

It's not actually done.

This is okay so. The movement is currently under development.

Oh, okay thanks for your response

@ritney78 i made a new check in. this is my latest work on the movement but still not finished. maybe you and others can help to make it work

ty, i'm trying it now

what is this error?
https://gyazo.com/2bbd4a6163ee5f8fe9fa3db2ecb0c491
thanks


Orientations should return Trajectories instead of np.ndarrays

The Orientation class currently returns trajectories of unit vectors as np.ndarrays.
Investigate if it is possible to instead return Trajectory objects

I'm not sure if this is still relevant after #293

This has been solved by #293


Email headers being cached

In my Rails application, I developed a mailing application in which I allow administrator to choose the from in email header.
I opened this issue because I think delayed_job keep some cache because the new email value is not taken in consideration. However I haven't found any information about resetting cache.
I also wrote a post in stack overflow: http://stackoverflow.com/questions/34355318/rails-4-delayed-job-keep-cache-for-email-from-header-value
Thanks !

ActionMailer::Base.default is set once when the application starts up as it is a class level thing. You can't use it to do what you want to do with or without DJ. Move the from assignment into the individual mailer methods and pass in the appropriate setting object or preferably id.

How can I forgot to try this, it was an easy fix !
Thanks for helping me to understand better how it worked.


It doesn't start after the last update

Restarting doesn't help.

Without any more detailed instructions, screenshots, logs, etc., I am unable to solve your problem.

Without any more detailed instructions, screenshots, logs, etc., I am unable to solve your problem.
I was getting an error starting the extension after the upgrade, but I found the reason. I deleted the "hystory" files and now it runs fine.

This issue has been fixed before, and it shouldn't occur again in future updates.


How do I attach persistent storage?

I have followed the dev-spaces quick start tutotirals, and spun up a simple "dev" space that has two services, one that makes a http request to the other.
However I now need them both to have access to some persistent file storage (shared between them).
How would I go about achieving that? Is this something I add to the azds.yaml file?

Dev spaces currently helps you with your code but not so much with external dependencies. To do that, you will need to modify the Helm chart that was produced by dev spaces to include the necessary objects and/or configuration to reference external storage. For example, you might create an Azure file share and mount that into both of your containers. See here for one example of how to do that.

@stepro I followed that documentation already. However after creating the storage account and file share, the next step was to manually create a pod using kubectl specifying storage options in a local .yaml file. I rely on dev spaces controller to deploy the pod so I cant use that approach to attach storage because I'm not the one spinning up the pod. So.. what would you recommend?

This is where you want to modify the pod spec in the deployment template yaml in the Helm chart. You can start out by creating the secret separately and then referring to it using the spec in the Helm chart. Later, you might want to have the Helm chart create the secret using values that you pass in.

Hmm slowly getting there..
I added the following to the bottom of the deployment template:
          volumeMounts:
            - name: azure
              mountPath: /mnt/azure
      volumes:
      - name: azure
        azureFile:
          secretName: azure-secret
          shareName: devbranch
          readOnly: false

However when I build I get this error:

pods/hubplatformserver-6fd94d7bc7-xfbsr: FailedMount: MountVolume.SetUp failed for volume "azure" : Invalid default/azure-secret, couldn't extract azurestorageaccountname or azurestorageaccountkey

When I followed the docs linked earlier, I used kubectl to set this secret in my local environment, I am assuming that it won't exist however where the helm build actually takes place. Looking around I found that the template populates secrets from the values.yaml file secrets section. However these comments are in that section:
secrets: {}
  # Optionally specify a set of secret objects whose values
  # will be injected as environment variables by default.
  # You should add this section to a file like secrets.yaml
  # that is explicitly NOT committed to source code control
  # and then include it as part of your helm install step.
  # ref: https://kubernetes.io/docs/concepts/configuration/secret/
  #
  # This creates a secret "mysecret" and injects "mypassword"
  # as the environment variable mysecret_mypassword=password.
  # mysecret:
  #   mypassword: password

Note: This values.yaml file contains all sorts of other things and it seems I would want to check it in to source control. How do I move the secrets out to another file that I wouldn't check in? And shoudn't your template be set up to do that by default?

Looks like you are close. When you ran kubectl create secret, it created the secret from the literal values you provided and stored it in the cluster, so it's not on your local machine. It seems there is something wrong about how the secret was created. Check kubectl get secret azure-secret -o yaml to make sure that the two data properties you specify exist. It will show the values as base64 encoded so don't worry if they look wrong.
Don't worry (yet) about the secrets section in the values.yaml file. I can tell you more about that after we get the basic scenario working with a pre-created secret.

Thank you. Yup, deleting the secret with kubectl delete secret azure-secret and recreating it has solved that issue! It looks like the basic scenario is now working! :-)

Glad that's working now. If you want to explore having the Helm chart itself deploy the secret, and how dev spaces helps you with that, take a look at this article.

Excellent, thanks I will.


HIVE-26100: Preparing for 4.0.0-alpha-2 development

What changes were proposed in this pull request?
New pom.xml versions, and new db files
Why are the changes needed?
So the next release development could be started
Does this PR introduce any user-facing change?
New db version
How was this patch tested?
Unit tests

@zabetak: Fixed them. Thanks for the review!


examples/output/test001.isdoc.pdf is invalid PDF/A

Hi,
I'd like to report that test001.isdoc.pdf of examples here declares itself as a PDF/A-1B, which is invalid for the obvious reason of having an attachment. Pls upgrade this example to PDF/A-3B.
PS: I'm working on bash "isdoc-pdf" for Unix environment (Linux & Mac), utilising Ghostscript to attach invoice.isdoc to a pdf and convert it to PDF/A-3B. Will share later :-)

Thanks for report, yes examples were using wrong PDF profile. Examples and code are fixed now.
However please note that ISDOC.PDF should be PDF/A-3a not PDF/A-3b file, see https://isdoc.cz/6.0.2/doc/isdoc.html#reprezentace-isdoc.pdf


Syntastic can't find pylint, pyflakes (after :SyntasticCheck pylint) even though in $PATH (as seen by syntastic#util#shell)

Here's the output with g:syntastic_debug=3 after using :SyntasticCheck pylint.
syntastic: 954.489072: g:syntastic_version = '3.8.0-24 (Vim 800, Darwin)'
syntastic: 954.489246: &shell = '/bin/bash', &shellcmdflag = '-ic' (!), &shellpipe = '2>&1| tee', &shellquote = '', &shellredir = '>%s 2>&1', &shelltemp = 1, &shellxquote = '', &autochdir = 0, &shell
xescape = ''
syntastic: 954.489685: UpdateErrors: pylint
syntastic: 954.489971: CacheErrors: pylint
syntastic: 954.490617: g:syntastic_aggregate_errors = 0
syntastic: 954.490842: getcwd() = '/Users/ldavis'
syntastic: warning: checker pylint is not available

and here's the output of echo syntastic#util#system('echo "$PATH"'):
/Users/ldavis:/Users/ldavis/anaconda3/bin:/usr/local/bin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/Library/TeX/texbin:/Users/ldavis:/Users/ldavis/anaco
nda3/bin:/opt/local/bin:/opt/local/sbin:/Users/ldavis/bin

with which pylint indicating a pylint executable in the /Users/ldavis/anaconda3/bin directory. Any idea what could be going on?.

syntastic: 954.489246: &shell = '/bin/bash', &shellcmdflag = '-ic' (!),

You changed options affecting system().  This is not supported.

Any idea what could be going on?

Please quit Vim, start it again, open a Python file, and post the output of:
:SyntasticInfo
:echo executable('pylint')
:echo syntastic#util#system('pylint --version')

Ah, well if that's the problem... how can I get syntastic to point to the pylint in an anaconda distribution? I have in my .vimrc the line set shellcmdflag=-ic, which loads my .bashrc and sets up my $PATH to point to the anaconda bin.
Now when I run :SyntasticInfo I get nothing; with the ic flag, I was getting executable('pylint')=1 (anaconda was in the path), but now it returns 0 (no longer in path).

Please consider answering the question I asked.  Post a new issue if you still have problems after resolving this one.

I did answer your question: the second paragraph. But here is the verbatim output.
Syntastic version: 3.8.0-24 (Vim 800, Darwin)
Info for filetype: vim
Global mode: active
Filetype vim is active
The current file will be checked automatically
Available checkers: -
Currently enabled checkers: -
```:echo executable('pylint')
0```
```:echo syntastic#util#system('pylint --version')
/bin/bash: pylint: command not found````

Does the problem "getting syntastic to view a 'checker' *outside* of the default `$PATH`, and without modifying `shellcmdflag` (because that breaks it)" warrant a new thread?

Does the problem "getting syntastic to view a 'checker' outside of the default $PATH, and without modifying shellcmdflag (because that breaks it)" warrant a new thread?

This is described in the manual, at :h syntastic-config-exec: point g:syntastic_python_pylint_exec to the executable.  This might not be your only problem though. shrug


🔧 Restore MkDocs Material pin after the fix

🔧 Restore MkDocs Material pin after the fix

📝 Docs preview for commit 54fb771b42168ceace3506540207392f3315d0fb at: https://99f71c31.fastapitiangolo.pages.dev


Ian Campbell: Watch coresumo.com

Ian Campbell requests the watch of the watch_keyword coresumo\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

coresumo\.com has been seen in 2 true positives, 0 false positives, and 1 NAA.

Approved by cigien in Charcoal HQ


fixes

i haven't tested it much

What exactly does this fix?

non-fissary polytopes with fissary elements are counted as fissary and truncating a polytope where rank != dimension

What does the fn update_system in the first commit do?
I think polytopes with fissary elements are usually considered fissary.
The "exclude hemis" feature is not redundant, as the inradius bounds are inclusive.

fn update_system is for getting the right number of checkboxes for truncation


TME-2291: Update stackset expel principal arn

Updates the principal account arn to point directly to the Expel AWS account when establishing the trust relationship instead of going through the created IAM role as is currently being done.
This PR has been tested to validate that no regressions were introduced.

Is the scan-tf check fail related to this change?

Is the scan-tf check fail related to this change?

nope, I'm adding an ignore block to the relevant section so it doesn't break future PRs.


ADBDEV-5473 Truncate temporary relation files before unlink

Truncate temporary relation files before unlink
Problem description:
After the drop of a temporary heap relation, disk space was not released to the
OS for several minutes. The expected behavior is immediate disk space release.
Root cause:
Background writer process kept file descriptors of the relation open until the
next checkpoint. The next checkpoint occurred after a timeout, which could be up
to CheckPointTimeout seconds (300 by default). Only temporary relations suffered
from it, because in mdunlinkfork segment files were truncated for all
non-temporary relations.
Fix:
The mdunlinkfork function was changed to call do_truncate on all segment files
for all relations, including temporary.


LayoutRenderer cannot be found

Type: Question
NLog version:
<PackageReference Include="NLog" Version="5.0.0-beta09" />
<PackageReference Include="NLog.Extensions.Logging" Version="1.0.0-rtm-beta5" />
<PackageReference Include="NLog.Web.AspNetCore" Version="4.4.1" />

Platform: ASP.NET Core 1.1
Current NLog config (database target is very similar to the example from https://github.com/nlog/NLog/wiki/Database-target)
<?xml version="1.0" encoding="utf-8" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      autoReload="true"
      internalLogLevel="Warn"
      internalLogFile="c:\temp\internal.txt">

  <!-- define various log targets -->
  <targets>
    <!-- write logs to file -->
    <target xsi:type="File" name="allfile" fileName="c:\temp\nlog-all-${shortdate}.log"
                 layout="${longdate}|${logger}|${uppercase:${level}}|${message} ${exception}" />

    <target xsi:type="File" name="ownFile" fileName="c:\temp\nlog-own-${shortdate}.log"
              layout="${longdate}|${logger}|${uppercase:${level}}|${message} ${exception}" />

    <target xsi:type="Null" name="blackhole" />

    <target xsi:type="Database" name="database" >

      <dbHost>(localdb)\MSSQLLocalDB</dbHost>
      <dbDatabase>BvsDbContext</dbDatabase>

      <commandText>
        insert into dbo.Log (
        Application, Logged, Level, Message,
        Username,
        ServerName, Port, Url, Https,
        ServerAddress, RemoteAddress,
        Logger, CallSite, Exception
        ) values (
        @Application, @Logged, @Level, @Message,
        @Username,
        @ServerName, @Port, @Url, @Https,
        @ServerAddress, @RemoteAddress,
        @Logger, @Callsite, @Exception
        );
      </commandText>

      <parameter name="@application" layout="${appsetting:name=AppName:default=Unknown}" />
      <parameter name="@logged" layout="${date}" />
      <parameter name="@level" layout="${level}" />
      <parameter name="@message" layout="${message}" />

      <parameter name="@username" layout="${identity}" />

      <parameter name="@serverName" layout="${aspnet-Request:serverVariable=SERVER_NAME}" />
      <parameter name="@port" layout="${aspnet-Request:serverVariable=SERVER_PORT}" />
      <parameter name="@url" layout="${aspnet-Request:serverVariable=HTTP_URL}" />
      <parameter name="@https" layout="${when:inner=1:when='${aspnet-request:serverVariable=HTTPS}' == 'on'}${when:inner=0:when='${aspnet-request:serverVariable=HTTPS}' != 'on'}" />

      <parameter name="@serverAddress" layout="${aspnet-Request:serverVariable=LOCAL_ADDR}" />
      <parameter name="@remoteAddress" layout="${aspnet-Request:serverVariable=REMOTE_ADDR}:${aspnet-request:serverVariable=REMOTE_PORT}" />

      <parameter name="@logger" layout="${logger}" />
      <parameter name="@callSite" layout="${callsite}" />
      <parameter name="@exception" layout="${exception:tostring}" />
    </target>
  </targets>

  <rules>
    <!--All logs, including from Microsoft-->
    <logger name="*" minlevel="Trace" writeTo="allfile" />
    <logger name="*" minlevel="Trace" writeTo="database" />

    <!--Skip Microsoft logs and so log only own logs-->
    <logger name="Microsoft.*" minlevel="Trace" writeTo="blackhole" final="true" />
    <logger name="*" minlevel="Trace" writeTo="ownFile" />
  </rules>
</nlog>

I'm trying to log to table in a SQL Server database, but some layout renderers cannot be found:
2017-08-03 14:21:25.4611 Error Error parsing layout appsetting will be ignored. Exception: System.ArgumentException: LayoutRenderer cannot be found: 'appsetting'
   at NLog.Config.Factory`2.CreateInstance(String name)
   at NLog.Layouts.LayoutParser.ParseLayoutRenderer(ConfigurationItemFactory configurationItemFactory, SimpleStringReader sr)
2017-08-03 14:21:25.5153 Error Error parsing layout identity will be ignored. Exception: System.ArgumentException: LayoutRenderer cannot be found: 'identity'
   at NLog.Config.Factory`2.CreateInstance(String name)
   at NLog.Layouts.LayoutParser.ParseLayoutRenderer(ConfigurationItemFactory configurationItemFactory, SimpleStringReader sr)
2017-08-03 14:21:25.5223 Error Error parsing layout aspnet-Request will be ignored. Exception: System.ArgumentException: LayoutRenderer cannot be found: 'aspnet-Request'. Is NLog.Web not included?
   at NLog.Config.Factory`2.CreateInstance(String name)
   at NLog.Layouts.LayoutParser.ParseLayoutRenderer(ConfigurationItemFactory configurationItemFactory, SimpleStringReader sr)
2017-08-03 14:21:25.5223 Error Error parsing layout aspnet-Request will be ignored. Exception: System.ArgumentException: LayoutRenderer cannot be found: 'aspnet-Request'. Is NLog.Web not included?
   at NLog.Config.Factory`2.CreateInstance(String name)
   at NLog.Layouts.LayoutParser.ParseLayoutRenderer(ConfigurationItemFactory configurationItemFactory, SimpleStringReader sr)
2017-08-03 14:21:25.5223 Error Error parsing layout aspnet-Request will be ignored. Exception: System.ArgumentException: LayoutRenderer cannot be found: 'aspnet-Request'. Is NLog.Web not included?
   at NLog.Config.Factory`2.CreateInstance(String name)
   at NLog.Layouts.LayoutParser.ParseLayoutRenderer(ConfigurationItemFactory configurationItemFactory, SimpleStringReader sr)
2017-08-03 14:21:25.5223 Error Error parsing layout aspnet-request will be ignored. Exception: System.ArgumentException: LayoutRenderer cannot be found: 'aspnet-request'. Is NLog.Web not included?
   at NLog.Config.Factory`2.CreateInstance(String name)
   at NLog.Layouts.LayoutParser.ParseLayoutRenderer(ConfigurationItemFactory configurationItemFactory, SimpleStringReader sr)
2017-08-03 14:21:25.5373 Error Error parsing layout aspnet-request will be ignored. Exception: System.ArgumentException: LayoutRenderer cannot be found: 'aspnet-request'. Is NLog.Web not included?
   at NLog.Config.Factory`2.CreateInstance(String name)
   at NLog.Layouts.LayoutParser.ParseLayoutRenderer(ConfigurationItemFactory configurationItemFactory, SimpleStringReader sr)
2017-08-03 14:21:25.5373 Error Error parsing layout aspnet-Request will be ignored. Exception: System.ArgumentException: LayoutRenderer cannot be found: 'aspnet-Request'. Is NLog.Web not included?
   at NLog.Config.Factory`2.CreateInstance(String name)
   at NLog.Layouts.LayoutParser.ParseLayoutRenderer(ConfigurationItemFactory configurationItemFactory, SimpleStringReader sr)
2017-08-03 14:21:25.5373 Error Error parsing layout aspnet-Request will be ignored. Exception: System.ArgumentException: LayoutRenderer cannot be found: 'aspnet-Request'. Is NLog.Web not included?
   at NLog.Config.Factory`2.CreateInstance(String name)
   at NLog.Layouts.LayoutParser.ParseLayoutRenderer(ConfigurationItemFactory configurationItemFactory, SimpleStringReader sr)
2017-08-03 14:21:25.5373 Error Error parsing layout aspnet-request will be ignored. Exception: System.ArgumentException: LayoutRenderer cannot be found: 'aspnet-request'. Is NLog.Web not included?
   at NLog.Config.Factory`2.CreateInstance(String name)
   at NLog.Layouts.LayoutParser.ParseLayoutRenderer(ConfigurationItemFactory configurationItemFactory, SimpleStringReader sr)

@ndreisg When you look at the error message LayoutRenderer cannot be found, then it also asks you Is NLog.Web not included?
Have you tried to add <extentions> to your nlog.config:
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      autoReload="true"
      internalLogLevel="Warn"
      internalLogFile="c:\temp\internal.txt">

   <extensions>
     <add assembly="NLog.Web.AspNetCore"/>
   </extensions>
   .....
</nlog>

https://github.com/NLog/NLog.Web/wiki/Getting-started-with-ASP.NET-Core-(csproj---vs2017)

I have tried this and most exceptions now disappeared (only the "identity" renderer still can't be found).
However, the fields in my table are still not filled :/

However, the fields in my table are still not filled :/

That's probably some missing code in the startup.cs, please check
https://github.com/NLog/NLog.Web/wiki/Getting-started-with-ASP.NET-Core-(csproj---vs2017)

@ndreisg ${identity} is not supported by NetCore as shown by the platform support:
https://github.com/NLog/NLog/wiki/platform-support
Maybe ${aspnet-user-identity} can help you out, or maybe create your own custom layout-renderer with some help from stackoverflow:
https://stackoverflow.com/questions/30701006/how-to-get-the-current-logged-in-user-id-asp-net-core
To diagnose the problems with writing to database, then activate and check the NLog-InternalLogger.

I assume your question has been answered, if not, let us know!


enable support for chocolately delivered shims

enable support for chocolately delivered shims (https://chocolatey.org/docs/features-shim)
path set as:
$env:Path = "C:\Program Files\PowerShell\6.0.0-alpha.18;C:\Program Files\OpenSSH-Win64"
allows new-pssession to successfully call ssh.exe (directly)
path set as:
$env:Path = "C:\Program Files\PowerShell\6.0.0-alpha.18;C:\ProgramData\chocolatey\bin;C:\Program Files\OpenSSH-Win64"
prevents new-pssession from calling ssh.exe (via chocolately-delivered shim), with error:
The background process reported an error with the following message: The SSH client session has ended with error message: The input line is too long..
$psversiontable
Name                           Value

BuildVersion                   <IP_ADDRESS>
CLRVersion
GitCommitId                    v6.0.0-alpha.18-39-gc0aafdb3d034ccc5d2e1d0744...
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSEdition                      Core
PSRemotingProtocolVersion      2.3
PSVersion                      6.0.0-alpha
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0
(Get-Command ssh).Path
C:\ProgramData\chocolatey\bin\ssh.exe
ssh -V
OpenSSH_7.5p1, OpenSSL 1.0.2d 9 Jul 2015

@DarwinJS   Could you please comment the Issue?

@surlypants this is happening because you also have the "OpenSSH (mls-software)" chocolatey package installed which puts those shims in place. (https://chocolatey.org/packages/mls-software-openssh).
Please uninstall openssh (mls-software) with choco install mls-software-openssh and then ensure $env:chocolateyinstall\bin does NOT have any shims for any file like "ssh*.exe"
The OpenSSH package from the PowerShell open source project does not create shims (https://chocolatey.org/packages/openssh)
@iSazonov - this could be an ongoing issue for people who have installed more than one SSH client.  Maybe new-pssession should check and report on which ssh.exe it finds.  If PS remoting is only supported with Microsoft's client - you could give an error.

it would appear to me that https://chocolatey.org/packages/openssh does in fact deliver shimmed EXEs. hence this report.
$ choco search ssh |grep mls
mls-software-openssh <IP_ADDRESS> [Approved] Downloads cached for licensed users
$ choco list -lo |grep ssh
openssh <IP_ADDRESS>

In your original post ssh -V delivered OpenSSH_7.5p1 so I assumed it was that package - good work finding the original culprit.
For anyone else following or finding this thread - the openssh chocolatey package does not generate shims.
Apologies @bagajjal - I have to loop in our conversation here https://github.com/DarwinJS/ChocoPackages/issues/28 to add a case in point of why I am not a fan of using the path for critical software dependencies.

@DarwinJS Thanks for comments!
@surlypants Nothing can be done in the repo. We close the Issue as External.


powershell

how do i fix it

Did the logging screen ever show up?

Did the logging screen ever show up?

yes

Could you please provide the log as well?

Could you please provide the log as well?

Does the integration work / has it been added? (To check start Roblox / Open Bloxstrap Menu)

Does the integration work / has it been added? (To check start Roblox / Open Bloxstrap Menu)

You could try replacing the username with the actual username used on your User (e.g. "Тимофіи") to check if that works.

You could try replacing the username with the actual username used on your User (e.g. "Тимофіи") to check if that works.

tysm

Ofcourse! For any other questions don't hesitate to open another ticket.


Home Assistant Core Log Warning

I'm using HCW7819EHMP side-by-side refrigerator and logger is throwing that warning every boot.
But it happens to other customs integrations like "https://github.com/jason0x43/hacs-hubitat" with climate components.
"Logger: homeassistant.components.climate
Source: components/climate/init.py:354
Integration: Climatización (documentation, issues)
First occurred: 11:28:33 (10 occurrences)
Last logged: 11:30:20
Entity None (<class 'custom_components.hon.climate.HonClimateEntity'>) implements HVACMode(s): cool, off and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please create a bug report at https://github.com/Andre0512/hon/issues"

Same problem here
2024-03-15 21:57:25.678 WARNING (MainThread) [homeassistant.components.climate] Entity None (<class 'custom_components.hon.climate.HonACClimateEntity'>) implements HVACMode(s): off, auto, cool, dry, heat, fan_only and therefore implicitly supports the turn_on/turn_off methods without setting the proper ClimateEntityFeature. Please create a bug report at https://github.com/Andre0512/hon/issues

Duplicate of #165

Fixed, thanks for reporting! :slightly_smiling_face:


command-line-service footprint too big

initial bringup indicates that command-line service is too big.  Need to investigate what is causing this

@tseelbach The container that the CLI microservice uses needs to be trimmed.  Probably should use a different Liberty image that only contains the features that are required for the microservice.  @davco01a builds the container... I think that is a manual process at this point.

I only have app security and microprofile in the feature list in server.xml
How do I get a trimmed down Liberty image?


PolyUtils - distanceToLine and IslocationOnPath alternative in Google Maps iOS

How to find if the car location is in the given polyline or not in swift. If it's not in the given polyline then I want to find distance.
In Android, Google maps is giving class PolyUtils which has distanceToLine and IslocationOnPath method.
How to implement the same feature in iOS using google maps SDK?

Duplicate of https://github.com/googlemaps/google-maps-ios-utils/issues/407


how to only compute the perplexity of each paragraph using your language model with local data?

how to only compute the perplexity of each paragraph using your language model with local data?  i don't want to use -d to dump data?  I have downloaded the Chinese model use  make lang=zh dl_lm

Hi, did you finish it？I also want to do something like this, maybe we can discuss this and exchange ideas :)


jQuery is undefined, but $ is working well.

jQuery is undefined error after loaded fully.
But $ is works well.
some plugins using window.jQuery are causing issues.
Is there any way to register jQuery like $ when loading shopify ?

What release of Slate are you kiddos using? I've found that when they upgrade to jQuery 3 they didn't refactor some things and its causing breakages like you guys are seeing. If you simple include jquery2.2.3.min.js everything works great again. If you wanna be a hero you can refactor the code for them and submit a pull request. I haven't checked to see whether its fixed in RC1 or master yet as I am on slate 0.14.0. I have to say the documentation could not be farther from the actual implementation.

This is a theme development problem, not a Slate problem. How jQuery is exposed is dependent on how it is imported and used in the theme. If there is a problem with Starter Theme, please open an issue there.


monkey_patch did not read current settings

Hi, can you help me with the following:

lets say I run migrate
django_cachalot monkey_patch will run, to invalidate cache
however i received redis.exceptions.ConnectionError: Error 111 connecting to None:6379. Connection refused --> it happened because django-cachalot still looking for redis at :6379, while my application used redis through different endpoint, lets say SOME_OTHER_REDIS_URL (stated in my app settings.py)

Have been running over the place, but can't find out why the application setting did not apply (it used default settings). This behavior does not exist in normal caching operation, only when I run from management console, eg. manage.py migrate or manage.py invalidate_cachalot

Mmm… I’m not sure I understand. What is SOME_OTHER_REDIS_URL? Could you send a minimal example for me to reproduce the settings issue?

Closing this issue until more info is provided.


examples: use optee-utee-build to build TA

Change examples, use optee-utee-build for building TA.

Looks like a good cleanup, thanks. FWIW:
Reviewed-by: Sumit Garg<EMAIL_ADDRESS>

Looks like a good cleanup, thanks. FWIW:
Reviewed-by: Sumit Garg<EMAIL_ADDRESS>
Done👀


[ Application/bugfix ] Remove unnecessary link @open sesame 08/19 4:43

Previous commit left this unnecessary link and this makes newly-implemented features to fail CI test. Remove accordingly.

Self evaluation:

Build test:     [X]Passed [ ]Failed [ ]Skipped
Run test:     [X]Passed [ ]Failed [ ]Skipped

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #2712. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

INFO: You can read if there are misspelled characters at our misspelling check report. Please read http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2712-202408191639450.61936092376709-bbab1bf0d640e3a4060f1f4f2258c5b90624a295/report/.

INFO: You can read if there are misspelled characters at our misspelling check report. Please read http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2712-202408191643450.40864300727844-bbab1bf0d640e3a4060f1f4f2258c5b90624a295/report/.

LGTM!

Thanks for fast review! 👍

:octocat: cibot: @skykongkong8, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2712-202408191643450.40864300727844-bbab1bf0d640e3a4060f1f4f2258c5b90624a295/.

:octocat: cibot: @skykongkong8, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2712-202408191936150.46614289283752-ee3fbb48650f80f83ec1c9ae030bfb49e7367e11/.

This PR was pointing different issue from the original purpose. Close.


claim.Spec.Selector is not supported for dynamic provisioning on AWS

The following
https://github.com/Alluxio/alluxio/blob/e6b7900126ebb8d236410f35ad69b6ffdb258470/integration/kubernetes/helm-chart/alluxio/templates/worker/domain-socket-pvc.yaml#L33-L38
results in
K8s dynamic volume provisioning: claim.Spec.Selector is not supported for dynamic provisioning on AWS
when you go with gp2 storage class

@jiacheliu3 @cheyang  do you have a good understanding of this issue?

@apc999 When the user is using dynamic PV provisioning (instead of manually creating PVs), the dynamic PV provisioners in K8s do NOT support specifying the selectors yet so the provision will fail. The solution will be to change the default selector to empty, same to https://github.com/Alluxio/alluxio/pull/13379 is doing for the logserver PVC.


Feat: implementation of websocket with updated examples

This PR implements a cli and browser communication between a client and a server on irmin-server via websocket.
This solution impose a stream-like structure layered on top of the message-oriented websocket connection.
More details on the issue #46

Thanks, this is great :smile:
I will need a little more time to do a full review, but based on CI it looks like the .opam files need to be updated to match the changes to the dune files. I think you will need to add pin-depends for irmin and graphql since this depends on unreleased changes.

Nice, CI is passing :partying_face: I will look everything over once more before I merge.
@dinakajoy: Would you please remove the duplicate CI commits?

This is great! I have a few suggestions, please feel free to ignore them. Great work :)

Thank you for taking time to go through it. I will effect the suggested changes, thank you.
Regarding the ws and wss question, it's just like http and https but for websocket

What's the purpose of base64 encoding the messages? Is that for the browser?

The Base64 encoding is needed because OCaml strings are just bytes whereas Websockets use UTF-8 [1] to send and receive messages. With the unix clients we don't hit any problems because ocaml-websocket doesn't do any checks or conversions. In the browser, however, this is not the case and things fail if the message is not UTF-8. Base64 is valid UTF-8 so this seemed the simplest workaround.
Websockets do support binary mode but even when I tried this I couldn't get it to work, the encoding of strings in js_of_ocaml/brr is a little confusing to me. See [1] for that also.
[1] https://datatracker.ietf.org/doc/html/rfc6455#section-5.6


Logo Changes to PulumiUP Featured Partners

This PR adds new sponsor and speaker logos for PulumiUP, including logos for Docker, Honeycomb, Imagine Learning, Mysten Labs, Oso, and Wiz. The updated images are added to the appropriate directories for both sponsors and speakers.
Equinix, CicleCI and nignx were removed.

Wiz and docker are a bit... gigantic, but they are there...


Add uv.lock as being identified automatically as TOML with VS Code's most common TOML extension

Upstream issue: https://github.com/tamasfe/taplo/issues/667
I already pushed a commit I added this issue here in this repository as well for future reference.

Thank you!

https://github.com/tamasfe/taplo/pull/668 has been merged, so this is closed.


2D Array is missing

Description: In a given array section, it is briefly explained about one-dimensional arrays, but we did not talk about two-dimensional arrays, which I believe is significant and should be included, and the sorting part should be included in another section called sorting techniques.
Use Case: 1. Structure of 2D array

Indexing
Initialization
4.Accessing
Problem for practise

Similar Features: (Optional) We would be different because here I'm going to all the problems from basic to advanced with the corporate tags.

You can try it, and I'll be here to assist you along the way.

ok sir

hi @Ajay-Dhangar i'd love to work on this!

Okay, @iamanolive

@Ajay-Dhangar submitted PR/


Add serialization to withConverter

We currently are able to specify withConverter when retrieving data from the database, but we're unable to to use convert the data back to your model.
https://github.com/supabase-community/postgrest-dart/pull/48
Basically like this PR but add toSupabase

like a toJson? I believe it'd be a lot better to do this on your model.
Model
class User {
  final String id;

  const User(this.id);

  Map<String, dynamic> toJson() {
    return {
      'id': id,
    };
  }
}

Postgrest call
final newUser = User('new-user-id');
postgrest.from('users').insert(
  newUser.toJson(),
);

Is this what you're talking about?

@DanMossa Yeah, Firestore has something like this right? I never quite understood the benefit of it, and I always do it like @bdlukaa as well. What is the benefit of having such method?

Yeah! It was mostly for feature parity. It just seemed a little weird to have it on the response but not the request. Nothing urgent but would be nice to have.

@DanMossa how's it like on firestore?

Coming back to this in a super long time.
I actually like the current implementation of withConverter, and don't find the withConverter implementation on Firestore that useful.
The toSupabase parameter suggested here is to convert the objects to Map<String, dynamic> when writing to the database, but you can actually pass custom class directly to insert or upsert as long as the class has toJson implemented.
class Foo {
  Foo(this.bar);
  final int bar;

  Map<String, dynamic> toJson() {
    return {'bar': bar};
  }
}
...
await supabase.from('foo').insert(Foo(1));
await supabase.from('foo').insert([Foo(2)]);


Removal of PIMT tool + performance improvements

What?
This PR adds performance improvements to the plugin calculation process.

create a minimal and full list of plugins for informational purposes
improvement - no longer need to download plugins for custom URLs
remove dependency on the pimt tool
performance increase through using associative arrays
add complex test, add minimal flag tests
better candidate for removal check
removed unused REFRESH option
update README.md

The script doesn’t work in bash 3.2.57 (mac, declare -g is not available), it should test the bash version and error out in a controlled way if it's not sufficient. Probably doesn't make sense to support old bash versions.


etcd doesn't run on arm64

Just updated to v2.3.1 and got this: unsupported architecture; unreliable, unstable.  This makes CoreOS unusable for arm64 users.  Please think about the ramifications next time you make this kind of change.

https://github.com/coreos/etcd/issues/5027#issuecomment-212481532

I believe @glevand wants etcd to start on arm64 by default. https://github.com/coreos/etcd/pull/5028 wont solve it. We are working on CI for arm64.

Yes, both I and @glevand wants to start etcd on arm64 without blockers.
But with v2.3.1, it's impossible without hacking the code.
I obviously know that #5028 doesn't solve it, but at least it's possible without code changes,
If you want help with CI for arm, arm64 and ppc64le, just ping me

So what do we need to do to make checkSupportArch() return success for arm64?

@glevand

Setup CI to build/test etcd for every pull request.

Continuously running etcd functional testing on arm64.

Step1 should be enough to say we support arm64 in a limited way.

@xiang90 OK, @lupan2005 has some patches to add arm64 build support to the travis.ci gimme script which he is preparing to submit: https://github.com/lupan2005/travis-ci-gimme.  This will only support building though.   We will see how those work with etcd PR's.  He is also working to bring up a Jenkins installation for arm64 testing.

@glevand Awesome! Thanks for the help on arm64.

to be officially supported on CoreOS, which means that every system application needs to catch up. Besides the missing CI integration, what is the official state of the build scripts and code WRT arm64 support?

@steveeJ arm64 builds (but not tests) already go through CI, but there hasn't been much testing. @mischief did some initial testing with CoreOS+arm64 using #5088

@lupan2005 has been working on our local Jenkins setup.  Currently, some of the fmt_tests and dep_tests fail on arm64, but all the unit_tests pass.  He plans to go through the tests and get them working.  It seems to be more of a tools problem than the etcd code.

@glevand sounds like a tooling problem to me too since the most important part passes, which is good to hear. Are there also any integration/functional tests in place to test the binary execution?

@steveeJ well, we have arm64 clusters here running fleet and flannel.  That's what we've been using as a test...  It would be nice if we did something more to stress it.

@glevand We listed a few things that need to be done to make arm64 officially supported here: https://github.com/coreos/etcd/blob/master/Documentation/op-guide/supported-platform.md
For arm64, we need a maintainer and set up integration test CI. Do you want to help on that?

also @luxas

@xiang90 Sure, I can act as arm64 maintainer.  We have our local Jenkins system doing the etcd tests, which are generally working OK, but those results are not available publicly.  In the next week or so I will do some rework of the tests and work toward having public test results.

@glevand Is it possible to hook the testing infra with github? So we can run the tests for each pull request?

@xiang90 The problem is that we need to run on an arm64 system.  We may be able to use qemu on x86 machines to emulate arm64, but qemu may not run fast enough for the tests to succeed without timeouts.  The other option is to run the tests on real arm64 hardware, but it needs to be looked into how to this with github.

@glevand qemu is definitely too slow for the tests-- @mischief tested arm64 etcd on qemu a few months ago and got a bunch of timeouts.

I wouldn't either go the qemu route. Qemu has quite poor Go runtime support.
Here's an article about Github and Jenkins, might be interesting: https://www.terlici.com/2015/09/29/automated-testing-with-node-express-github-and-jenkins.html

@glevand Any progress on CI testing on arm64?

@xiang90 still working on the arm64 CI, but nothing to report yet.

@glevand Is it possible to finish this up before Oct? Or I have to move this to 3.2 milestone.

@xiang90 Our goal is to have it for v3.1.0.  I'll bump the priority.

@glevand Thanks!

@glevand Kindly remind you that 3.1 rc will be out in mid of Sept.

@glevand any update on this one? what is your next step?

@xiang90 All tests now run successfully on arm64.
I'm now trying to figure out if we can somehow run arm64 hosted tests from github PRs.

@glevand OK. That would be great. It is also the last missing part to say we officially support arm64 I guess.

@glevand Any progress update on this one?

@glevand I am going to move this out of 3.1 milestone. We are working on an etcd Jenkins. If the happens, we can simply add a arm64 slave to finish the remaining part.

@xiang90 we can add ppc64le slave as well to the same jenkins server

What's the distance right now between "unsupported" and "supported" arm64 etcd?
I don't see any evidence of unusual behavior on that platform reported recently.

@vielmetti The Container Linux kola test suite does etcd tests, and those have been passing, so I think etcd itself is working OK on arm64.
There have been some improves made to the project's CI/testing recently, and that needs to be updated to work on arm64.  My feeling is that in the least the arm64 equivalents of the linux-amd64-* targets of the project's travis file should be working.  That would need:

Get the build script and test script to run on arm64.
Get the etcd-test docker image to build on/for arm64.
Get the same test script PASSES that the travis file runs for amd64 to work on arm64.

We also need to setup an arm64 jenkins project that has an etcd github hook to run the tests.  See: https://jenkins-etcd-public.prod.coreos.systems/job/etcd-ci-ppc64/.


Fix build -- Don't force install of next version of electron builder

We'll just use the version specified in packages.json

This issue with Travis has resolved itself without this PR.


Transfers from a vesting account should

Transfers from a vesting account to general account of the same key should

incur no transfer fee
not be subject to minimum transfer amount if the full amount is transferred

@davidsiska-vega do we need the restriction that the above only applies when transferring to the general of the same key?
Not sure I can see any issues with allowing transfers to any valid key/account combo and it's a bit simpler.


wait for unfinished jobs and close all accepts

In current implementation, there is a wait group counting the listners. but the problem is, by sending kill signals, the process is kiled by os.Exit and wait group is only used for unhandled panic inside the listner functions.
Adding a channel to inform the listner to exit (and also Close all Accept() locks) is a good idea to handle this problem.
ps - I want to implement a hack to reload config with SIGUSR1 , just closing all connections, fork new instanse and then exit. this PR is required for that reload functionality. if you have another way to handle it, I'll happy to help.

@fzerorubigd Thank you. I thought about implementing config reload before, but found it not so easy to do.


Extend Swagger coverage

Hi,
I'm sharing here information I shared on discord , but it would be of value to extend the API Specification / Swagger to additional use cases which I haven't seen (Apologise if I am wrong) :

[ ] - Swagger don't seems to support a "workspace" end-point to list productions & download productions individually
[ ] - Swagger don't seems to support a "workspace" end-point to list productions as a whole (or sub whole)
[ ] - Swagger don’t seems to have user management which would be beneficial for people working portable UI
[ ] - Swagger don’t seems to support more that 1 agent
[ ] - Swagger don't seems to offer solution to list agent
[ ] - Swagger don't seems to offer solution allowing X step (equivalent of AutoGPT ‘-y N’ argument)
[ ] - Swagger don't seems to offer budget/consumption follow-up
[ ] - Swagger don't seems to offer LLM back-end list
[ ] - Swagger don't seems to offer LLM back-end selection
[ ] - Swagger don't seems to offer Agent type list
[ ] - Swagger don't seems to offer Agent type selection
[ ] - Swagger don't seems to offer BDD back-end definition (Which would be beneficial for companies willing to host their Data)

My 2 cents,

Hi @ph-ausseil, I'm reading through the Discord and I plan to talk about the protocol there too.
We are trying to balance being general and simple enough with the needs of individual agents, but we'll definitely be iterating on the AutoGPT feedback 👍

Hi @ph-ausseil, I'm reading through the Discord and I plan to talk about the protocol there too.
We are trying to balance being general and simple enough with the needs of individual agents, but we'll definitely be iterating on the spec with the AutoGPT feedback 👍

I see two added  value, the service provided by the SDK & the Swagger to provide a standard. Just for my two cents, as a developer I don't necessarly that some element of the standard are not support by the SDK. None the less I think it is appreciated that there is a standard so everyone working on GUI or Agent goes in the same direction.

@ph-ausseil, would love to see more context here if you have a link to the conversation?

There is one here : https://discord.com/channels/1092243196446249134/1106856186273341471/1131833763719020614
Which I also empted to bring to somewhere it is more adapted : https://discord.com/channels/1092243196446249134/1129949435082842262/1132385779717509231


Update header from marketing to include Connect banner

Turned the z-index values into variables.
The values were suggested by marketing team while we troubleshooted some overlapping issues with these changes.


Broken link in examples readme

Steps to Reproduce
Go to: https://github.com/flutter/flutter/tree/master/examples
Try the last link to the widget apps example, it's a broken link. Not completely sure, but maybe widgets have been renamed to material_gallery?

Addressing https://github.com/flutter/flutter/issues/2131 might catch errors like this :)
Also, thanks for the report!


Removed stray characters from CLI sample output

The sample CLI output in the readme was presumably copied from the source in cli.js, but a single quote and comma seems to have been left behind.

Good catch :)


Need to save token generated as part of service end point connection

Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Environment

Server - Azure Pipelines or TFS on-premises?
Azure Pipelines

If using TFS on-premises, provide the version:

If using Azure Pipelines, provide the account name, team project name, build definition name/build number:
vinitasanghi

Agent - Hosted or Private:
Hosted

If using Hosted agent, provide agent queue name:

If using private agent, provide the OS of the machine running the agent and the agent version:

Issue Description
[Include task name(s), screenshots and any other relevant details]
As mentioned in https://github.com/Microsoft/vsts-tasks/issues/7263, "I had been able to implement getTokenUsingBasicAuth and use the generated token in subsequent REST API calls. However,  would be interested in this option "Another option is to create a service endpoint UI contribution, generate the token within that UI and save it with endpoint.". I want to save the token to be used/passed in node js or powershell scripts for final task execution. Please confirm as to how can we achieve the same."
Task logs
[Enable debug logging and please provide the zip file containing all the logs for a speedy resolution]
Error logs
[Insert error from the logs here for a quick overview]

It's not clear which specific task you're having an issue with (in /Tasks)

I have a written a custom service endpoint for VSTS  in which I connect to a REST API to authenticate to our server.  Post authentication, a token is generated which needs to be stored and reused in my custom build tasks for any further REST API calls

service connections question

This issue is stale because it has been open for a year with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days


Remove remains of deprecated Site.GoogleAnalytics

Purpose
Some occurrences of the Site.GoogleAnalytics variable that is deprecated since Hugo 0.133 have not been removed in #3137, as mentioned by @rodrigoalcarazdelaosa in that same PR.

This seems to cause an error (rather than a deprecation warning) with Hugo 0.140.1. Will a full release bear this change soon?


sdk/core/azure-core/src/http/curl/curl.cpp compile error

Query/Question
Tried to build with latest SDK (head https://github.com/Azure/azure-sdk-for-cpp/commit/2cce17d6910a9f34376fcaa88d78710566d91eae) but compilation failed:
/opt/project/sdk/core/azure-core/src/http/curl/curl.cpp: In constructor 'Azure::Core::Http::CurlConnection::CurlConnection(Azure::Core::Http::Request&, const Azure::Core::Http::CurlTransportOptions&, const string&, const string&)':
/opt/project/sdk/core/azure-core/src/http/curl/curl.cpp:2312:5: error: 'curl_blob' was not declared in this scope
 2312 |     curl_blob rootCertBlob
      |     ^~~~~~~~~
/opt/project/sdk/core/azure-core/src/http/curl/curl.cpp:2317:37: error: 'CURLOPT_CAINFO_BLOB' was not declared in this scope; did you mean 'CURLOPT_CAINFO'?
 2317 |     if (!SetLibcurlOption(m_handle, CURLOPT_CAINFO_BLOB, &rootCertBlob, &result))
      |                                     ^~~~~~~~~~~~~~~~~~~
      |                                     CURLOPT_CAINFO
/opt/project/sdk/core/azure-core/src/http/curl/curl.cpp:2317:59: error: 'rootCertBlob' was not declared in this scope
 2317 |     if (!SetLibcurlOption(m_handle, CURLOPT_CAINFO_BLOB, &rootCertBlob, &result))
      |                                                           ^~~~~~~~~~~~
make[2]: *** [sdk/core/azure-core/CMakeFiles/azure-core.dir/build.make:63: sdk/core/azure-core/CMakeFiles/azure-core.dir/src/http/curl/curl.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:298: sdk/core/azure-core/CMakeFiles/azure-core.dir/all] Error 2

Why is this not a Bug or a feature Request?
First want to check if I missed some build env changes.
Setup (please complete the following information if applicable):

OS: ubuntu:focal-20230412
IDE : Linux cmake
Version of the Library used: libcurl is libcurl4-openssl-dev:amd64 7.68.0-1ubuntu2.18

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Query Added
[x] Setup information Added

The Azure SDK for C++ has an undeclared dependency on CURL 7.77, which was released in May 2021 (our vcpkg baseline is from 2022 so we didn't notice that we had taken a dependency on version 7.77).
Do you have the ability to move to a more recent version of CURL? The version you're targeting is from Jan 2020 and there are several security vulnerabilities that have been fixed since then (including at least one marked High).

Thanks for the info. So there is no way to use latest SDK with 7.68?  We are using Ubuntu 20.04 and latest libcurl distribution for that is 7.68.
If no solution on your side, then we will seek other solutions like compile from more recent libcurl source.

@bzhou-sw how do you acquire the azure-sdk-for-cpp libraries? Do you use vcpkg to install this SDK as part of your application? Or do you use some other approach?

We don't use vcpkg. We clone the git repo and only build modules we need as .so inside container.
We will move our dev env from Ubuntu 20.04 to 22.04, and libcurl issue should be solved since 22.04 has libcurl 7.81, that will work for the SDK, right?

Build SDK with ubuntu 22.04 successfully.

We are tracking the 7.77 dependency work in #4792


Add support for TTL at collection level with CosmosDB

Enables specifying Time to live at collection (or container level).
Description
For collection like Activations its desirable to expire the activations after some time. For CouchDB this is done by running a cleaner script. For CosmosDB we can make use of the TTL support which allows auto removal of entries after the TTL time has passed after their last modified time.
So to specify TTL for activations
whisk {
    cosmosdb {
        collections {
            WhiskActivation {
                time-to-live = 30 days
            }
        }
    }
}

This PR also now sets the default TTL to -1 which allow us to later specify TTL at individual item level if required.
Related issue and scope

[ ] I opened an issue to propose and discuss this change (#????)

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[ ] Bug fix (generally a non-breaking change which closes an issue).
[ ] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[ ] I signed an Apache CLA.
[ ] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[ ] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

Updated indentation


How we dump data and load data in django cms version 3.2.3

hi,
i setup django-cms in my local system with following version
django == 1.8.10
dajngo-cms == 3.2.3
after i setup all pages in local system
now i want to deploy my site on webfactiona server
for that i setup everything and use dumpdata in json format and load them in web faction server
i dump all data using following command

python manage.py dumpdata > db.json

after transfer that json file in webfaction server give following command

python manage.py loaddata db.json

so it give error like
"raise Value error("No Json object could be decoded") django.core.serializes.base.Depersonalization: Problem installing fixture :no Json Object could be decoded"
after i validate json file in online json validator and check but not an issue in json file
after that i create another file and try to load data but it gives same errros
and then i try dumpdata with individual app and load them in database
for that i give following command
./manage.py dumpdata cms djangocms_column djangocms_file djangocms_flash djangocms_googlemap djangocms_inherit djangocms_link djangocms_picture djangocms_style djangocms_teaser djangocms_text_ckeditor djangocms_video > db.json
but it return error like "djangocms_column is invalid app"
so i try to dump only cms app
./manage.py cms > db.json
and load them in webfactional server but still it return same error like
"raise Value error("No Json object could be decoded") django.core.serializes.base.Depersonalization: Problem installing fixture :no Json Object could be decoded"
please guide for dump data from local system and load them in webfactional server

Hi, I don't think is really a django CMS issue, but a more general Django issue.
I made a couple of suggestions at https://groups.google.com/forum/#!msg/django-cms/CEvi5izGOBg/v_uTuC8RBgAJ.
I'm closing this here as out-of-scope, but if you find some reason to think this is specific to django CMS< please feel free to re-open.


Strings being seen as Protobuf

OS
OSX 10.15.7
VERSION
Version 1.5.600 (1.5.600) (Mac App Store)
ISSUE DESCRIPTION
After seeing some keys defaulting to protobuf I was able to reproduce by creating a test DB with data created from a python script creating random 4 character strings with a space between 2 of them.
As you can see in the screenshots some of them are showing as protobuf but changing the type dropdown to string shows the correct string that was stored.

these are just a few examples that I have found in my testing. If you would like the python script I used to create them I can provide that so you can easily create test data.

fixed, Thx!

Hey , it looks like it fixed most of the problems but I still get it sometimes.
Ive managed to recreate it using a script again to create some random data.

Seems to be when there is a space in the value usually


(Only) show filtered category items on scatterplot axes

Steps to reproduce:
Create a scatterplot, make sure at least one of the axes is category (String) type.
Filtered on this category
Desired behavior:
User have the choice to only see the filtered category items: Scatterplot Axes automatically adjust and scale to filtered category items. Categories that were filtered out in the filter panel are not displayed on axes.
Option: distinguish filtered/filtered out category items on this axes.
Actual behavior:
User still see all the category items on this axes including filtered out items

The goal is to reflect state of filters for categorical columns both on axes and on legends.

Estimated fix time: 29.04

@skalkin  - please procced with that


Sqlite clean fix

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: axelfontaine:white_check_mark: tinybarks:x: Marco PerazzoMarco Perazzo seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


fix(atomic): guarantee alignment in struct

It affected us on ARM architecture where it panicked with panic: unaligned 64-bit atomic operation.
See: http://golang.org/pkg/sync/atomic/#pkg-note-BUG
Also see: https://github.com/zishang520/socket.io/pull/10

thx.


[Feature] Add flutter bindings

Can you explain more please? I'm not familiar with flutter at all.

Flutter is a multiplatform framework for development for Mobile (android, iOS, fuchsia in the future) and Desktop (Linux, Windows, macOS). He is very much gaining popularity. It is mainly used for Android and iOS development. Now it has poorly developed neural networks. Since you already have integration with Java, Objective C, it would be possible to make a library on pub.dev, which will make a good contribution to the development of the framework (as well as give you a great popularity of your library. Integration of flutter and the native part occurs by PlatformChannel
Now there are poorly developed libraries:

https://pub.dev/packages/tflite
https://pub.dev/packages/google_ml_vision

Moreover, all libraries are about third-party developers

@FedyuninV What think about it?

@ltropin as an idea it looks interesting, but AFAIK none of my colleagues is familiar with Flutter and Dart (myself included). And right now we have our hands full with some other tasks (optimizations + moving towards distributed training). That's why I can't guarantee that we're going to implement this, but I'll discuss it with others after the holidays.
I'm leaving this issue open as a remainder.


Use search prompt as placeholder for inputs

Allow an option to have the search prompt show as input text then when the input has text in it the search prompt should hide

Yeah, placeholder text should be fairly straightforward to do.


Update CCSWeaponInfo for the new panorama update?

I would really like to see the new updated class with the CHudTexture included...

I didnt found public source, may be I will reverse this(and FileWeaponInfo_t) later. If someone will get it before me, please, provide pull request.


Index type for Eigen ctors, fixes #1909

Submisison Checklist

[x] Run unit tests: ./runTests.py src/test/unit
[ ] Run cpplint: make cpplint
[x] Declare copyright holder and open-source license: see below

I couldn't run cpplint because insalling Anaconda and Python 3.x broke my build.
Summary
Generate explicit static cast to VectorXd::Index type for constructors of Eigen types to deal with ambiguity of VectorXd(0) call.
Intended Effect
Allow zero sizes for row vectors, vectors, and matrices in Stan.
How to Verify
New model test compiles.
Side Effects
No.
Documentation
Behavior now matches doc.
Reviewer Suggestions
Anyone.
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company):  Columbia University
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

I checked that the test make sense with regards to the issue, shows up in CI output, and that the new generate_eigen_indexed_expression does something that should resolve the previous ambiguity.  I only understand the code generator at a high level so... code review with a grain of salt?

Thanks.

Bob

On Jun 13, 2016, at 1:41 PM, Krzysztof Sakrejda<EMAIL_ADDRESS>wrote:
I checked that the test make sense with regards to the issue, shows up in CI output, and that the new generate_eigen_indexed_expression does something that should resolve the previous ambiguity. I only understand the code generator at a high level so... code review with a grain of salt?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


[Doc] Fix the order of comments in sample Job YAML file

Why are these changes needed?
The docstring of runtimeEnv didn't appear right above the runtimeEnv field.  This PR fixes the issue.

Related issue number

Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[ ] Manual tests
[ ] This PR is not tested :(

Compatibility test failure unrelated, merging.