Added a metadata table

Base of Issue #13
Added a metadata table
Added active, enabled, lldp, nni and uni items to display.
This pull request depends on changes to k-info-panel/switch_info.kytos. Especifically:
From lines 18 to 19:
         <k-interface :interface_id="interface.id" :name="interface.name" :port_number="interface.port_number" :mac="interface.mac"
                      :speed="interface.speed" :key="interface.name" v-for="interface in this.interfaces">

to Lines 18 to 20:
         <k-interface :interface_id="interface.id" :name="interface.name" :port_number="interface.port_number" :mac="interface.mac"
                      :speed="interface.speed" :key="interface.name" :enabled="interface.enabled" :metadata="interface.metadata"
                      :active="interface.active" :lldp="interface.lldp" :nni="interface.nni" :uni="interface.uni" v-for="interface in this.interfaces">

-The PR on topology have been opened.
-Updated changelog.
-Updated version with suggested string. But my installed npm recognizes that version as an error, let me know if is a problem to change it to another version.

-The PR on topology have been opened. -Updated changelog. -Updated version with suggested string. But my installed npm recognizes that version as an error, let me know if is a problem to change it to another version.

@Alopalao

I've pulled you're PR and successfully built with this version, which error did you end up with npm on your end? Example:

❯ npm run build

><EMAIL_ADDRESS>build
> npm run prod > /dev/null && zip -r latest.zip index.html dist

updating: index.html (deflated 50%)
updating: dist/ (stored 0%)
updating: dist/build.js.LICENSE.txt (deflated 59%)
updating: dist/icon-kytos.svg (deflated 57%)
updating: dist/build.js (deflated 71%)
updating: dist/logo-kytos.svg (deflated 59%)

I forgot to mention that since we'll need to release ui as a beta version, the changelog changes should be under a new subsection, something like this, could you apply this patch?

diff --git a/CHANGELOG.rst b/CHANGELOG.rst
index a4d04ac..2aec413 100644
--- a/CHANGELOG.rst
+++ b/CHANGELOG.rst
@@ -7,8 +7,6 @@ UNRELEASED - Under development
 ******************************
 Added
 =====
--Added active, enabled, lldp, nni and uni items to ``kytos/interfaceInfo`` to be displayed in basic details
--Added a table to ``kytos/interfaceInfo`` to be displayed interface metadata

 Changed
 =======
@@ -28,6 +26,15 @@ Security
 Changed
 =======

+[2022.2.0.b0] - 2022-04-07
+**************************
+
+Added
+=====
+-Added active, enabled, lldp, nni and uni items to ``kytos/interfaceInfo`` to be displayed in basic details
+-Added a table to ``kytos/interfaceInfo`` to be displayed interface metadata
+
+

Updated Changelog d33cb83dbc58182ae1470ac8cedf5159b4d56b11

About the version causing problems, it was because my npm and node were not updated from 6.14.4 and 10.19.0 respectively.


MemoryPack support

          I'd love MemoryPack support to be added to Vogen.

Originally posted by @aradalvand in https://github.com/SteveDunn/Vogen/issues/305#issuecomment-2452321670

@aradalvand - I started working on this, but hit a brick wall: MemoryPack uses source generators, but so does Vogen. There is no way to order which source generator runs first, so MP was emitting errors because value objects were empty (i.e. they hadn't been augmented with fields/constructors etc.)
This won't be a problem if the value objects are in a separate assembly.

@SteveDunn You're right; I realized the same thing quickly after I suggested this :)
However, it would still have been possible for Vogen to support MemoryPack via generating custom formatters, if MemoryPack had support for this kind of thing.

This won't be a problem if the value objects are in a separate assembly.

Then we'd still be back to square one because the value objects would be considered "foreign" types that the user would have to manually write a formatter for — see this other issue I created in MemoryPack's repo.

The MessagePack is good enough for now; thanks for adding it.

👍👍 I'll add the formatters as it'll still be useful for value objects in other assemblies.


Adding Feathr FAQ

Add a collection of questions that we got asked a lot.

close and move to a new PR: https://github.com/linkedin/feathr/pull/610


DOC: fixed misleading docstring om MolType

Thanks to Kalon Peters for pointing this out!

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
178497

Relevant Lines:
194690

💛  - Coveralls


Credential login: How to perform custom error handling?

Ask your question
Im using custom signin page and trying to implement or display error message on the same page.
I've tried the setting
const { data, status, signIn } = useSession({redirect: false})
and also this one,
@click="signIn('credentials', { redirect: false, email: form.email, password: form.password })"
but the return response is always
url: "http://localhost:3000/api/auth/error?error=CredentialsSignin&provider=credentials"
Anyone able to implement custom signin with error message display on the same page? Thanks in advance!
Additional information
No response

I have the same Problem! I didn't figured out how to do this. i tried this:
signIn("credentials", {username: loginData.username, password: loginData.password, redirect: false }).then(
    ({ ok, error }) => {
      if (ok) {
        console.log("ok");
      } else {
        console.log("hallo");
        // console.log(error)
      }
    }
  );

But it only work without Errors.
When i have a Error the Code doesn't return to the "then" Statement.

Heya!
To get a custom error page you can use the pages configuration of the nuxt-auth hanbdler, see https://next-auth.js.org/configuration/pages for all options.
Basically you can tell nuxt-auth to direct to your custom page on error by doing:
pages: {
  error: '/my-cool-error-page'
}

There you can do whatever you want. Does that help? (:

Ah, got it! Sorry that it took some time to get back to you - had a lot pre-christmas / end-of-year stuff going on at our company
So, then you and @noprobz09 should be able to work with the response of:
const result  = await signIn('credentials', { redirect: false, email: form.email, password: form.password })

As @noprobz09 pointed out, the result of this is:
url: "http://localhost:3000/api/auth/error?error=CredentialsSignin&provider=credentials"

You can see the error query parameter here. These are standardized for nuxt auth (: Documentation for them is:

here in code: https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/core/pages/signin.tsx
here in docs (partial): https://next-auth.js.org/errors

For example, in the response shared by @noprobz09 the error is CredentialsSignin, which next auth would translate to the following on its default login page: "Sign in failed. Check the details you provided are correct." (source: https://github.com/nextauthjs/next-auth/blob/aad0b8db0e8a163b3c3ae7dec3e9158e20d368f4/packages/next-auth/src/core/pages/signin.tsx#L69-L70)
That should be what you @Lucas-Gruber and you @noprobz09 are looking for, correct?

I checked this topic out further and identified a bug in the process of doing so 🎊 Thanks to you two for persuing this (:
The fix is in #122. There I've also added documentation + a code playground example. That PR will close this issue and I'll do a release shortly after.
Let me know if you have any other concerns AND also let me know if your issue was actually resolve, that would mean a lot to me ❤
Other than that: Happy Holidays 🎊

Thank you @BracketJohn. Happy Holidays! :)

Thanks 💯

Hi @BracketJohn
I followed the documentation page for custom signin and tried to copy the sample code in it.
`const { signIn } = useSession()
const mySignInHandler = async ({ username, password }: { username: string, password: string }) => {
const { error, url } = await signIn('credentials', { username, password, redirect: false })
console.log(error)
if (error) {
// Do your custom error handling here
alert('You have made a terrible mistake while entering your credentials')
} else {
// No error, continue with the sign in, e.g., by following the returned redirect:
return navigateTo(url, { external: true })
}
}`
and call the mySignInHandler from the button @click="mySignInHandler".
The return error is always null
and this is my sample NuxtAuthHandler
`
import CredentialsProvider from 'next-auth/providers/credentials'
import { NuxtAuthHandler } from '#auth'
export default NuxtAuthHandler({
// A secret string you define, to ensure correct encryption
secret: 'your-secret-here',
providers: [
// @ts-expect-error You need to use .default here for it to work during SSR. May be fixed via Vite at some point
CredentialsProvider.default({
// The name to display on the sign in form (e.g. 'Sign in with...')
name: 'Credentials',
// The credentials is used to generate a suitable form on the sign in page.
// You can specify whatever fields you are expecting to be submitted.
// e.g. domain, username, password, 2FA token, etc.
// You can pass any HTML attribute to the  tag through the object.
  authorize (credentials) {
    // You need to provide your own logic here that takes the credentials
    // submitted and returns either a object representing a user or value
    // that is false/null if the credentials are invalid.
    // NOTE: THE BELOW LOGIC IS NOT SAFE OR PROPER FOR AUTHENTICATION!

    throw new Error('Exception message');   // expecting to throw an error
    // return null;

  }
})

]
})
`

Hey, im pretty late to the party but I want to bump this because I think @noprobz09 has a valid point.
Is there no way for custom errors when using the credentials provider?
For example:
CredentialsProvider.default({
    async authorize(data: {
        username: string;
        password: string;
    }) {
        // Auth Logic

        return new Error("Username or password is incorrect");
        // return new Error("To many login attempts");
        // return new Error("Your account has been disabled");
    },
}),


MetadataServiceTest - Test Methods With No Assert

Running code containing MetadataServiceTest through Checkmarx shows several test methods marked with @IsTest without containing any asserts.
L 78: private static void coverGeneratedCodeCRUDOperations()
L 89: private static void coverGeneratedCodeFileBasedOperations1()
L 109: private static void coverGeneratedCodeFileBasedOperations2()
L 126: private static void coverGeneratedCodeTypes()

For checkmarx, I added system.assertEquals(true, true); to each test methods in MetadataServiceTest.


[Update Request]: Eza v1.12.0 - Incorrect Download Link

What type of update are you requesting?
A change to the package metadata
Current Package Identifier
eza-community.eza
Package Version
1.12.0
Please describe the changes you would like to see
The download link for v1.12.0 is incorrect and results in a 404. It should be updated to {...}/eza.exe_x86_64-pc-windows-gnu.zip. Specifically, the .exe is missing.
> winget install eza-community.eza
Found eza [eza-community.eza] Version 0.12.0
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://github.com/eza-community/eza/releases/download/v0.12.0/eza_x86_64-pc-windows-gnu.zip
An unexpected error occurred while executing the command:
Download request status is not success.
0x80190194 : Not found (404).

If I use https://github.com/eza-community/eza/releases/download/v0.12.0/eza.exe_x86_64-pc-windows-gnu.zip as the download URL and run ./eza --version, I see the version as 0.13.0. Is this expected?

I don't think that's expected. I'll file an issue with eza to check.

[Policy] Reset Labels

[Policy] Help Wanted
[Policy] Package Update


Add support for function pointer types

I would say this is pretty low pri. These are only reachable from IL. We can probably live without this for a year.

typeof(void*) works in C# just fine ... I agree that it is low pri.

@jkotas this bug tracks function pointer types, not reflection with pointer types
Things like
.field method instance void*(int32) [] myVec

Got it...


Juno AI Missing - 2 People stay on ship

After completing the Juno AI mission, I let Juno free and took the 2 Ryujin guys back to Neon, and the mission ended, however the 2 guys stayed on the ship.

Details
After completing the mission and going back to Neon for the 2 Ryujin guys (Operative Collins, and Operative Khambatta) to get off my ship, they ended up staying on board. I have done a number of other missions since completing this, and when I am in the ship you can see dialog happening of the two guys. I flew to a planet just now and they are standing next to me in the cockpit, cant talk to them other than 1 liner NPC chat you get from random NPCs, and so I have no idea what they are sticking around for other than this being a bug.
Game Version
1.7.36
Language
English (EN)
New Game
No
Reproduction Steps
Unsure how to recreate it other than doing the Juno mission again from an old save, but I suspect it will be the same, unless this is a one off glitch?

Did you actually enter the starport at Volii Alpha or did you just fast-travel to Neon City and then fast-travel away? You need to either land at Neon and exit your ship, or fast-travel to Neon City and then take the elevator to the starport.

Yeah I landed on Neon and got out of the ship, the quest completed, and then I went into Neon and did something else, and then left on the ship again. Didnt notice the guys still on the ship till a few missions later, and they are still currently standing on the bridge next to me, just saying random NPC things, you cannot actually talk to them. So weird.

Have been unable to replicate this issue across three characters. Possibly a fluke.


feat: add gnome-software PWA support

Ok so running it locally reveals this error:
error: importing RPMs: creating importer: Processing file-overrides for package gnome-software: Invalid absolute filepath '0001-crash-with-broken-theme.patch'


Data added through the theme is no longer visible

We've been using this theme Mapping VAWC facilities since last week since last week, and yesterday I noticed that it's no longer being shown.
I checked out other themes, and many appears to be working fine, although some of my other theme aren't showing the data, too.
Is there something going on in the back-end?

No nothing... Except maybe an instance restart but it should be related :/
@govvin is it ok on your side too?

Normally, we should be able to view the POIs previously added (star markers) like this, right?

Since Monday, I can only see what's available from the data layer, but not what's been added using the theme.

Ahhh .. now I understand, so a data layer is necessary to visualize what's been added. Thank you. Consider this resolved.

The yellow star markers are only displayed until the real data comes from OSM. It is sort of a placeholder.


docs(module:table): explain the behaviour of  "loading" attribute

update the description to "loading" attribute
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[X] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ X] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[ X] No

Other information

@vthinkxie  thanks for your time to review the PR.  I have read the guidelines and updated the title of this PR, the commit messages as well.

@vthinkxie  can you please let me know what change should be made?

Hi @lovelangy plz rebase your pr onto master, thanks

closed now, you can submit another pr and rebase it onto master


Pipeline composer state-based

Remove/refactor old_* files

Make saved pipeline popup & created pipeline popup


Ml4earth hackathon

Modified part 1 and part 2 in the imaging part, it cannot be merged automatically.

Should stay an own branch


[dev guide] How to see the log print added in python runtime ?

What's this issue about
Asking for some guide for development.
the Problem
I'm trying to add some log print inside tensorrt_llm.runtime.generation, and expects to see them during
decoder = tensorrt_llm.runtime.GenerationSession(...)
decoder.setup()
decoder.decode()

But I can't.
What I did
the sequence of what I did:
vim tensorrt_llm/runtime/generation.py     # add some print(), or logger.error()
python3 ./scripts/build_wheel.py --trt_root /usr/local/TensorRT-<IP_ADDRESS>    # incremental rebuild
pip install ./build/tensorrt_llm*.whl    # reinstall
cd examples/baichuan && python run.py --model_version v2_7b --max_output_len=50 --tokenizer_dir /data/services/inner-tts-chinese/data/Baichuan2-7B-Chat --engine_dir=/data/services/inner-tts-chinese/data/Baichuan2-7B-Chat/tensorrt_llm

The example run succeeded, but without the logs I added in python runtime.
the Question

How to see the logs I added in python runtime ?
Does TensorRT-LLM python backend/runtime support any kinds of pip install -e editable install ?
Does TensorRT-LLM support stream-line return, i.e. per-token decoding and return during LLM infer ?

Do you reinstall the tensorrt llm again after changing the code?

Do you reinstall the tensorrt llm again after changing the code?

I think I did, hopefully. I use these commands:

vim tensorrt_llm/runtime/generation.py     # add some print(), or logger.error()
python3 ./scripts/build_wheel.py --trt_root /usr/local/TensorRT-<IP_ADDRESS>    # incremental rebuild
pip install ./build/tensorrt_llm*.whl    # reinstall
cd examples/baichuan && python run.py --model_version v2_7b --max_output_len=50 --tokenizer_dir /data/services/inner-tts-chinese/data/Baichuan2-7B-Chat --engine_dir=/data/services/inner-tts-chinese/data/Baichuan2-7B-Chat/tensorrt_llm

The example run succeeded, but without the logs I added in python runtime.

The added log snippet:
diff --git a/tensorrt_llm/runtime/generation.py b/tensorrt_llm/runtime/generation.py
index d20832f..7fbae79 100755
--- a/tensorrt_llm/runtime/generation.py
+++ b/tensorrt_llm/runtime/generation.py
@@ -1795,6 +1795,7 @@ class GenerationSession(object):
                return_dict: bool = False,
                encoder_output: torch.Tensor = None,
                encoder_input_lengths: torch.Tensor = None):
+        logger.error('some print')
         scfg = sampling_config
         batch_size = context_lengths.size(0)
         beam_width = scfg.num_beams

Can you try adding some debug code to make sure you really enter the line you change? For example, adding exit directly.

Can you try adding some debug code to make sure you really enter the line you change? For example, adding exit directly.

I've tried assert False, ''. I'll give exit() a try.
Is it correct that after pip install ./build/tensorrt_llm*.whl, it is expected to run the modified code in TensorRT-LLM/ dir ?

Yes. You can also uninstall tensorrt_llm first before installing the new one.

Thanks for your kindly reply. And what about my last question ?

Does TensorRT-LLM support stream-line return, i.e. per-token decoding and return during LLM infer ?

Confirmed workflow:
vim tensorrt_llm/runtime/generation.py     # add some print(), or logger.error()
python3 ./scripts/build_wheel.py --trt_root /usr/local/TensorRT-<IP_ADDRESS>    # incremental rebuild, rebuild logs confirms tensorrt_llm/* are packed in wheel
pip uninstall tensorrt-llm    # otherwise install would be skipped
pip install ./build/tensorrt_llm*.whl    # reinstall. --force-reinstall is much slower and did not work for me
cd examples/baichuan && python run.py ...

Thanks for your kindly reply. And what about my last question ?

Does TensorRT-LLM support stream-line return, i.e. per-token decoding and return during LLM infer ?

I see GenerationSession.decode( streaming= ). Closing issue, thanks.


Disallow intercept Map touch events to parents views

I test it on my own project and it works like a charm.
Regards,


Published Articles are Stale

Today I saw some feedback on twitter where customers were getting upset because they didn't see their contributor avatars on articles that they had contributed to. I looked into it and saw that it was because their contributions had not been published, even after 5 months. The article in question is here:
https://github.com/MicrosoftDocs/windows-uwp/blob/docs/windows-apps-src/porting/desktop-to-uwp-extensions.md
It would be great to look into seeing if you can update the published content.

Thanks EisenburgEffect. I see no pull requests on that topic ( https://github.com/MicrosoftDocs/windows-uwp/pulls ). Can you direct me to the specific requests?

I'm noticing that there are items in the history for this article (not PRs) where the content in master doesn't match what is published on the site. Do you know if the content has been recently published? This could be a bug in the publishing engine as well. Are you all using VSTS paired with GitHub?

Thanks. Can you direct me to a specific item that appears in the master repo that does not appear on the public site?  If there was some contribution in the past that got overwritten somehow, it could very well be some sort of bug in the system. RE: Pairing. Yes with use VSTS paired with Github.

I found the PR actually: https://github.com/MicrosoftDocs/windows-uwp/pull/91
That change doesn't appear to be live on the site.

Clear as day. Thank you. Looks like a member of our team accepted the PR and for some reason that accept doesn't appear live. Definitely a bug somewhere there. I'm reaching out about this right now. Stay tuned. Thanks again

Ok I've asked the contributor to submit their edit again so that I can accept the pull request and get their avatar added to the topic. I have no way to manually add their avatar otherwise I'd do that and just make the edit to the doc myself. I'll give the contributor some time to respond to my comment before I intervene and make the correction myself. The doc will have to be corrected at some point as the typo in it still exists.


useContractRead - TypeError: Cannot read properties of undefined (reading 'map')

I just upgraded from:
    "@web3modal/ethereum": "^2.0.0-alpha.7",
    "@web3modal/react": "^2.0.0-alpha.7",

to:
    "@web3modal/ethereum": "^2.0.0-beta.1",
    "@web3modal/react": "^2.0.0-beta.1",

Both cases using the latest ethers: "ethers": "^5.7.2",
Now nothing changed in the code, I have something like:
const info = useContractRead({
    addressOrName: process.env.NEXT_PUBLIC_CONTRACT_ADDRESS,
    contractInterface: myABI,
    functionName: 'totalUsers',
});

And now the data does not load and in info.error I get:
"Uncaught TypeError: Cannot read properties of undefined (reading 'map')"

Api for this hook was updated to match underlying wagmi changes - https://github.com/WalletConnect/web3modal/blob/V2/docs/react.md#usecontractread-example
In the future we will also support their typescript autocomplete for contracts based on their abi json, stay tuned 😉


Fix omnibox radius, separate omnibox outline flag, and always optimize fully in Release builds.

This PR does three things:

The classic omnibox flag makes the omnibox too square, with no radius at all. M71 and earlier has a 3px radius. In addition, when the omnibox is focused, it causes the stroke outline to not appear correctly without this 3px radius. Updates the flag description too.

The classic omnibox border is incomplete in its current state, separate out the border patch into a new flag underneath the main one, with an appropriate description.

IDK why, but Google seems obsessed with keeping Chrome as small as possible. There are 3 compiler configs that can be applied: "No Optimize", "Optimize", and "Optimize Max". The no optimize section is only for debug builds. The other two are selectively applied depending on the target. Thorium, as one part of it's compiler optimizations, always sets everything to /O2 for Windows and -O3 for Linux, no matter the config, when doing a release build (is_official_build = true). This adds ~30Mb to the overall installed size, but I'm like so what. That's inconsequential and minor, for a good gain in performance. Especially considering people are using this browser on old hardware that sometimes struggles to run such newer Chromium.

I've already done all this in the Thorium repo, and in my Cr-Win7 repo. Just thought I'd share and make a PR. If you don't want to merge 2. and 3., I understand, but 1. should really be merged, since the goal is to have the proper classic appearance.

Please note that I kept the grey colour as it's closer to what older Chromiums used.

@win32ss What do you mean? Why do you mention that you kept it? Also, isn't is black, not grey.
Also, I noticed an error on my part. https://github.com/win32ss/supermium/pull/505/files#diff-7cb2aab2e6e4dcfb07cf81cca5ad8f4490ad85d62d6b437af95dac6dbc4787f5
I accidentally removed the
 &&       base::CommandLine::ForCurrentProcess()->HasSwitch("compact-ui"))
section for the classic omnibox borders. I will restore that and make a new PR.

@win32ss Here you go > https://github.com/win32ss/supermium/pull/509

@win32ss What do you mean? Why do you mention that you kept it? Also, isn't is black, not grey.

While it was originally black in my case, but then upon review of some of the older versions, they were greyer, and especially in 49's case (although that actually uses three different shades to mimick shadows).
There was some delay in uploading my commits so it may seem to have been "always" black though.


setting emit_aggregated_during_backfill does not exist

According to the doc https://docs.timeplus.com/query-syntax#settings , there is a setting emit_aggregated_during_backfill
While , in latest proton 1.5.3, there is no such setting.
In case there is no such setting, how to enable emit during backfill?
here is the error
SELECT
  window_start, count(*) AS count, hash, geohash_decode(hash) AS hash_decode, hash_decode.1 AS long, hash_decode.2 AS lat
FROM
  tumble(v_flows_source_locations, 1s)
WHERE
  _tp_time > (now() - 2m)
GROUP BY
  window_start, hash
settings seek_to = '-2m', emit_aggregated_during_backfill=1

Code: 115. DB::Exception: Unknown setting emit_aggregated_during_backfill. (UNKNOWN_SETTING) (version 1.5.3)

the doc emit_aggregated_during_backfill is outdate, current is emit_during_backfill:
 M(Bool, emit_during_backfill, false, "Enable emit intermediate aggr result during backfill historical data", 0) \
@jovezhong  needs to revisit it

Thanks, I updated the doc via https://github.com/timeplus-io/docs/commit/7b7e85a1e7db67a190af8f74a59adf292e8900b9


OSNexus limited disclosure and product warning

Please don't merge yet.

@Can you merge @Lennaert89 ?


API basePath is coming back with port

I am trying to serve the docs from a relative path for an app using HTTPS.  The Swagger JSON returns something like
{
  "apiVersion":"v1",
  "swaggerVersion":"1.2",
  "resourcePath":"",
  "apis":[{
    "path":"/auth/user.{format}",
    "operations":[{
      "produces":["application/xml","application/json", "application/vnd.api+json","text/plain"],
      "notes":"",
      "summary":"",
      "nickname":"GET-auth-user---format-",
      "httpMethod":"GET",
      "parameters":[]
     }
  ]}],
  "basePath":"https://accounts.kyck.dev:80/api"}

https and port 80 are in direct conflict.  I have tried various options with add_swagger_documentation, including include_base_url: false and root_base_path: false
Not sure what I am doing wrong, but would love some help.

As @dm1try states in a referenced pull request, since https and port 80 are in direct conflict, it seems like a configuration problem, so there is nothing unexpected in the gem's behaviour.

solved in actual versions


fix: cursor is moved when opening file through search interface

Fixes an issue where the cursor would get moved to the start of the document if the user opened the document through something like the search window, which is supposed to move the cursor to the matching position.
#2144

apart from comments above, lgtm

can we add a test for this by manually overriding the position in a test and using https://sinonjs.org/releases/v1.17.7/fake-timers/ ?

That doesn't work unfortunately. If faketimer is set up, VSCode completely freezes. I implemented the tests by wrapping around setTimeout and simulating how the watcher works instead.


Inscription text content often fails to display

eg at http://<IP_ADDRESS>:port_number/shibescription/b28d30d95b967058e04947c6b87764c6ea594c24efb6dc020a2caca0b94570dfi0 it just shows a blank space for the content. You have to click on the 'content' link to see it.

This is probably because some of the previews are empty. eg
https://wonky-ord.dogeord.io/preview/3d06bdeb8981a636d1954dd1c3307e8b99d84c05c8e82e47690ecdbe05875b7fi0
says
<!doctype html>

even though the real content is a drc-20 deploy inscription.

Fixed by https://github.com/verydogelabs/wonky-ord-dogecoin/pull/12


Update straxer

What is the problem / what does the code in this PR do
Straxer is a reprocessing script. Using this script we can e.g. reprocess data. Using this PR, we can easily pass a json configuration file to this script to allow one to change the configurations.
Can you briefly describe how it works?

Read JSON
Convert list -> tuple (we never use lists as options, or at least we shouldn't)
Insert the read JSON file in st.set_config

Also allow straxer to use an extra data-directory.
Can you give a minimal working example (or illustrate with a figure)?
cmd = f'straxer {run_id} --context xenonnt_simulation --target {target}'
cmd += f' --add_folder {data_dir}'
cmd += f' --config_from_json {conf_file}'
!$cmd # Submit using ipython magic

Nobody? I'm merging this than. Looks like I'm the only one using it anyways. Have been using it the past few days. Works like a charm.


code

Excuse me, I got the following error when I ran the third step command, what's going on, and how can I fix it

Hi,
Did you finish running the training code (https://github.com/TaesikGong/NOTE#run)?
The error seems to be caused by not having any results from training.
Hope this helps.


Improve Font Awesome support

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

When we add a chip with MatherialUI icon (e.g. <Phone/> from '@material-ui/icons') all works fine.
But when we'd add a chip with custom icon (e.g. from Font Awesome) inside the Icon component (Icon from '@material-ui/core') we see that the icon looks a bit ugly.
Examples here: https://codesandbox.io/s/material-ui-n4nhw?fontsize=14
Expected Behavior 🤔

I expect that all of a another icons will looks like a MU icons.
Steps to Reproduce 🕹

Steps:

Create
<Chip icon={<Phone />} label="test"/>
and
<Chip icon={<Icon className="fas fa-phone-alt"/>}  label="test"/>
Compare their icons.

Context 🔦

I'm just trying to use chips with FA's icons.
Your Environment 🌎

Tech
Version

Material-UI
v4.5.0

React
16.10.1

Browser
FF 70.0b11, Google Chrome 76.0.3809.100

TypeScript
3.6.3

Fontawesome
5.11.2

@Vestrond Material Design icons and Font Awesome icons use a different strategy to "frame" the vectorial paths.

Font Awesome: variable ratio, 0px padding

Material Design: 1:1 ratio, 3px padding

I'm not sure how we should address the concern. I can advise you to add a padding 3px to the font awesome icons. Could you confirm it looks better with this diff?
diff --git a/docs/src/pages/components/icons/FontAwesome.tsx b/docs/src/pages/components/icons/FontAwesome.tsx
index 94b4f7cfe..7b6738d3e 100644
--- a/docs/src/pages/components/icons/FontAwesome.tsx
+++ b/docs/src/pages/components/icons/FontAwesome.tsx
@@ -3,12 +3,12 @@ import clsx from 'clsx';
 import { loadCSS } from 'fg-loadcss';
 import { makeStyles, createStyles, Theme } from '@material-ui/core/styles';
 import { red } from '@material-ui/core/colors';
-import Icon from '@material-ui/core/Icon';
+import Icon, { IconProps } from '@material-ui/core/Icon';

 const useStyles = makeStyles((theme: Theme) =>
   createStyles({
     root: {
-      '& > .fa': {
+      '& > span': {
         margin: theme.spacing(2),
       },
     },
@@ -21,28 +21,50 @@ const useStyles = makeStyles((theme: Theme) =>
   }),
 );

+const faUseStyles = makeStyles((theme: Theme) =>
+  createStyles({
+    root: {
+      padding: 3,
+      height: 'auto',
+      width: 'auto',
+      fontSize: theme.typography.pxToRem(24 - 3 * 2),
+    },
+    fontSizeSmall: {
+      fontSize: theme.typography.pxToRem(20 - 3 * 2),
+    },
+    fontSizeLarge: {
+      fontSize: theme.typography.pxToRem(36 - 3 * 2),
+    },
+  }),
+);
+
+function FaIcon(props: IconProps) {
+  const classes = faUseStyles();
+  return <Icon classes={classes} {...props} />;
+}
+
 export default function FontAwesome() {
   const classes = useStyles();

   React.useEffect(() => {
     loadCSS(
       'https://use.fontawesome.com/releases/v5.1.0/css/all.css',
-      document.querySelector('#font-awesome-css'),
+      document.querySelector('#font-awesome-css') || document.head.firstChild,
     );
   }, []);

   return (
     <div className={classes.root}>
-      <Icon className="fa fa-plus-circle" />
-      <Icon className="fa fa-plus-circle" color="primary" />
-      <Icon className="fa fa-plus-circle" color="secondary" />
-      <Icon className="fa fa-plus-circle" color="action" />
-      <Icon
+      <FaIcon className="fa fa-plus-circle" />
+      <FaIcon className="fa fa-plus-circle" color="primary" />
+      <FaIcon className="fa fa-plus-circle" color="secondary" />
+      <FaIcon className="fa fa-plus-circle" color="action" />
+      <FaIcon
         className={clsx(classes.iconHover, 'fa fa-plus-circle')}
         color="error"
         style={{ fontSize: 30 }}
       />
-      <Icon className="fa fa-plus-circle" color="disabled" fontSize="large" />
+      <FaIcon className="fa fa-plus-circle" color="disabled" fontSize="large" />
     </div>
   );
 }

Set width: auto and height: auto was fine idea: icons like the fab fa-apple-pay will looks fine.
As I see (may be I do something wrong) padding 3px looks ugly. 1px is Ok. However I'm not sure.

By setting height and width to auto we have a bit pretty picture:

Padding-top: 1px at .MuiIcon-root make more pretty:

Only problems with Bolt (fas fa-bolt) and AD (fab fa-adversal) icons cuz their size's proportion is abnormal. Idk what to do with this.

Maybe we could have something like a fixedRatio prop on the Icon component that forces the icon in a square div with automatic margins on the sides? This would maintain the flexibility if someone is purposefully adding non-square icons while also providing an easier way to use other libraries while maintaining the look and feel of the Material-UI components.

Did you arrive at any "best practice" regarding this? Also - the SVG icon use case (FontAwesome) is highly interesting to us as well:
<Chip
    icon={<FontAwesomeIcon icon={faExclamationCircle} />}
    label="Warning!"
/>

related: https://github.com/FortAwesome/react-fontawesome/issues/239

I've been using a custom replacement component for FontAwesomeIcon from @fortawesome/react-fontawesome that uses the raw SVG path data to populate an SvgIcon component:
import { IconDefinition } from '@fortawesome/fontawesome-svg-core';
import SvgIcon, { SvgIconProps } from '@material-ui/core/SvgIcon';
import makeStyles from '@material-ui/styles/makeStyles';
import React, { forwardRef } from 'react';

type Props = Omit<SvgIconProps, 'viewBox'> & {
  icon: IconDefinition;
};

const useStyles = makeStyles({
  root: {},
  colorSecondary: {},
  colorAction: {},
  colorDisabled: {},
  colorError: {},
  colorPrimary: {},
  fontSizeInherit: {},
  fontSizeSmall: {},
  fontSizeLarge: {},
  pathPrimary: {},
  pathSecondary: {
    opacity: 0.4,
  },
});

export const FontAwesomeSvgIcon = forwardRef<SVGSVGElement, Props>((props, ref) => {
  const {
    icon: {
      icon: [width, height, , , svgPathData],
    },
    classes,
    ...svgIconProps
  } = props;

  const {
    pathPrimary: pathPrimaryClassName,
    pathSecondary: pathSecondaryClassName,
    ...svgIconClasses
  } = useStyles(props);

  return (
    <SvgIcon
      ref={ref}
      {...svgIconProps}
      classes={svgIconClasses}
      viewBox={`0 0 ${width} ${height}`}>
      {typeof svgPathData === 'string' ? (
        <path d={svgPathData} />
      ) : (
        /**
         * For whatever reason the 0th path is considered "secondary"
         */
        svgPathData.map((d, i) => (
          <path className={i === 0 ? pathSecondaryClassName : pathPrimaryClassName} d={d} />
        ))
      )}
    </SvgIcon>
  );
});

It's missing all the fancy transform/stacking features of FontAwesomeIcon but so far it renders correctly everywhere I've tried it.
Colors/sizes:

Bolt in Chip:

Bolt in IconButton (ink is no longer an ellipse instead of a circle):

Not sure how this should/could be applied to either library, though.

@chrislambe Thanks for sharing. While we have been exploring the issue with fonts, its the first time we cover SVG. What do you think about adding a FontAwesome section in https://material-ui.com/components/icons/#svgicon. How about using your gist as a starting point? https://codesandbox.io/s/happy-engelbart-1hke8?file=/src/App.tsx

It's missing all the fancy transform/stacking features

I have been wondering about this for a while. Which feature do you miss?

Nice.
For reference the very simplistic approach we use, using FontAwesomes own icon wrappers can be seen below. Can't promise it's perfect in all cases, but so far it has worked well.  We have not tried any duo-tone things, however duo-tone icons are a separate lib with FA. https://fontawesome.com/how-to-use/on-the-web/styling/duotone-icons
https://codesandbox.io/s/still-architecture-zdr81?file=/src/App.tsx

@SweVictor This approach looks interesting. Did you experience any issue with it?

@oliviertassinari sure! I'll try and write up a Font Awesome section for the docs this week.
@SweVictor I was doing something similar for a while, using fixedWidth to try and account for the difference in dimensions. The fact that the IconButton ink isn't perfectly circular even with fixedWidth is what eventually drove me to write that component.

I see, sounds good @chrislambe.
I haven't seen many issues so far, but we have very few IconButtons so that could be it. I see now (since you pointed it out) that the IconButton is indeed elliptical in my example. We did however notice some issues initially (hence the interest in this thread) with for example the Chip component and some other sub-elements. Each case can be fixed with custom margins/paddings or shrink/grow, but I agree a "real" bridge would be a better solution so I appreciate the effort.
I think it would be good to contrast "normal" FA use (with their wrapper) with the "MUI" bridge to show what you actually gain.
The FA transforms are quite nice to have sometimes, but most can of course fixable with very little CSS as well. https://fontawesome.com/how-to-use/on-the-web/using-with/react#features

The following worked well for me.
I loaded the CSS from Font Awesome in my root component per the MUI Readme:
    useEffect(() => {
      const node = loadCSS(
        'https://use.fontawesome.com/releases/v5.12.0/css/all.css',
        document.querySelector('#font-awesome-css') as HTMLElement,
      );

      return () => {
        node.parentNode?.removeChild(node);
      };
    }, []);

Then I added these overrides in the theme:
createTheme({
  overrides: {
    MuiIcon: {
      root: {
        width: 'auto',
        height: 'auto',
        fontSize: '1.25rem',
      },
      fontSizeSmall: {
        fontSize: '1rem',
      },
      fontSizeLarge: {
        fontSize: '1.75rem',
      },
    },
    MuiButton: {
      iconSizeSmall: {
        '& > span:first-child': {
          fontSize: '1rem',
          marginBottom: '.1rem',
        },
      },
      iconSizeMedium: {
        '& > span:first-child': {
          fontSize: '1.1rem',
          marginBottom: '.1rem',
        },
      },
      iconSizeLarge: {
        '& > span:first-child': {
          fontSize: '1.2rem',
          marginBottom: '.1rem',
        },
      },
    },
  },
});


[3.0.0-beta] Renaming doesn't work

Hi,
I try to rename a node, but it keeps returning false. I think this is probably a bug in the new 3.0.0 beta-version.
I am using the latest built. My (simplified) code:
$('#tree')
                .jstree({
                    'core' : {
                        'data' : {
                            'url': 'some/url/to.json',
                            'data' : function (node) {
                                return { 'id' : node.id };
                            },
                            'type': 'post'
                        }
                    }
                })
                .on("select_node.jstree", function (e, data) {
                    $('#tree')
                            .jstree("rename_node", data.node, 'Foo');
                });

On selecting a node, nothing happens. The select_node.jstree event is being triggered though (tested with alert). I also tested whether the rename_node.jstreeevent is fired, but it is not.
Thanks.

Thanks @vakata !
I was also fasing the same problem. Would be helpfull to write a short note to API documentation of rename_node() - http://www.jstree.com/api/#/?q=rename_&f=rename_node(obj, val) about it if possible.


Fix minor typo in README

By the way, I think the same data structure should be used for every option (either a list or a tuple).

It should, if you have time to update please do!


refresh token optimization

Everytime when user logs in, we will return access and refresh token pair. And we will store refresh token in database.
If user keeps login and logout, we will have too many refresh tokens saved in the database.
Maybe we can reuse these tokens, if they are not too old.
For example, if a token's TTL is 180 days. When user logs in, and we find s/he has a stored refresh token, which still has 150 days (>=80%) left before expiring, in this case we can return this refresh token rather generate a new one.

The refresh creation action is here JWTAuthenticationFilter.java#L61
We can query first, only create new one if required.


feat: move to dotnet 8.0.2

BREAKING CHANGE: move to dotnet 8.0.2

:tada: This PR is included in version 3.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


ACS: Remove the duplicate az acs browse command

Description
There are 2 sets of commands

az acs browse
az acs dcos browse and az acs kubernetes browse

Need to remove 1) because you cant browse for Docker Swarm and swarm mode because both orchestrators have no UI

Environment summary
Install Method: How did you install the CLI? (e.g. pip, interactive script, apt-get, Docker, MSI, nightly)
Answer here: Docker
CLI Version: What version of the CLI and modules are installed? (Use az --version)
Answer here: Latest that comes with the docker image
OS Version: What OS and version are you using?
Answer here: MAC osX
Shell Type: What shell are you using? (e.g. bash, cmd.exe, Bash on Windows)
Answer here: bash

We don't plan to implement this az acs change. @tjprescott this issue can be closed.


[SPARK-29785][SQL] Optimize opening session of Spark Thrift Server

What changes were proposed in this pull request?
Add configuration spark.sql.thriftServer.ignoreDefaultDatabase to control whether it will request a free executor when we opening a new session of Spark Thrift Server.
use:database is supported in SPARK-17819.
If we set spark.sql.thriftServer.ignoreDefaultDatabase=true, we don't need to allocate an executor and opening a session to Spark Thrift Server costs only ~100ms.
Why are the changes needed?
It's not reasonable that a free executor is needed when we open a session. Especially when all  the executors are busy and our cluster is under big pressure.
Does this PR introduce any user-facing change?
If you don't need opening a session to Spark Thrift Server with configurations, it's better to set spark.sql.thriftServer.ignoreDefaultDatabase=true.
The default of spark.sql.thriftServer.ignoreDefaultDatabase is false.
How was this patch tested?
Manual.

Can one of the admins verify this patch?

Can one of the admins verify this patch?


what is the different between the original tensorrt  api and tensorrt llm?

trt-llm is better?

TensorRT-LLM is based on TensorRT and add many features/functions about large language model.
So, if you want to run large langugae model inference, TensorRT-LLM is suggested.


Custom ISerializerExtension is throwing "Recursive dependency detected" exceptions

I'm trying to resolve my own references to get more flexibility on how I resolve them (i.e. some of the references come from other documents).
I'm having a hard time getting a custom ISerializerExtension working.  I was able to get the example case to work but when I tried replacing ISerializer with ISerializer I got a LightInject "Recursive dependency" error.
I thought it might be due to using IContents vs ISerializers (not really sure what the difference is there) but both attempts throw the same error.  I'm showing the test with ISerializers because that's what I'm working with now.  Any ideas?
sealed class Extension : ISerializerExtension
    {
        public static Extension Default { get; } = new Extension();

        Extension() { }

        public IServiceRepository Get(IServiceRepository parameter) =>
                parameter.Decorate<ISerializers, MySerializerDecorator>();

        void ICommand<IServices>.Execute(IServices parameter) { }

        public class MySerializerDecorator : ISerializers
        {
            private ISerializers _serializers;
            private ISerializer<Subject> _myInjectedSerializer;

            public MySerializerDecorator(ISerializers serializers) {
                _serializers = serializers;
                _myInjectedSerializer = new ResolveReferenceSerializer(serializers.Get(typeof(Subject)).For<Subject>());
            }

            public ISerializer Get(TypeInfo parameter)
            {
                return parameter == typeof(Subject) ? _myInjectedSerializer.Adapt() : _serializers.Get(parameter);
            }
        }

        sealed class ResolveReferenceSerializer : ISerializer<Subject>
        {
            readonly ISerializer<Subject> _previous;
            readonly Dictionary<string, Subject> _store = new Dictionary<string, Subject>();

            public ResolveReferenceSerializer(ISerializer<Subject> previous) => _previous = previous;

            public void Write(IFormatWriter writer, Subject instance)
            {
                _previous.Write(writer, instance);
            }

            public Subject Get(IFormatReader parameter)
            {
                var instance = _previous.Get(parameter);
                if (_store.ContainsKey(instance.Id))
                {
                    instance = _store[instance.Id];
                }
                else
                {
                    _store[instance.Id] = instance;
                }

                return instance;
            }
        }

Heres the test:
        [Test]
        public void ExtensionTest()
        {
            IExtendedXmlSerializer serializer = new ConfigurationContainer()
                                                                    .EnableImplicitTyping(typeof(Subject))
                                                                    .Extend(Extension.Default)
                                                                    .Create();
            const string message = "Hello World!";
            var mysubject = new Subject { Message = message };
            string document = serializer.Serialize(
                new List<Subject>() {
                    mysubject,mysubject
                });

            var subject = serializer.Deserialize<List<Subject>>(document);

            Assert.That(subject[0], Is.EqualTo(subject[1]));
        }

And here's the error:
Message: System.InvalidOperationException : Unable to resolve type: ExtendedXmlSerializer.IExtendedXmlSerializer, service name:
  ----> System.InvalidOperationException : Unresolved dependency [Target Type: ExtendedXmlSerializer.ExtensionModel.Xml.ExtendedXmlSerializer], [Parameter: serializer(ExtendedXmlSerializer.ExtensionModel.Xml.ISerializer)], [Requested dependency: ServiceType:ExtendedXmlSerializer.ExtensionModel.Xml.ISerializer, ServiceName:]
  ----> System.InvalidOperationException : Unresolved dependency [Target Type: ExtendedXmlSerializer.ExtensionModel.Xml.Serializer], [Parameter: read(ExtendedXmlSerializer.ExtensionModel.Xml.IRead)], [Requested dependency: ServiceType:ExtendedXmlSerializer.ExtensionModel.Xml.IRead, ServiceName:]
  ----> System.InvalidOperationException : Unresolved dependency [Target Type: ExtendedXmlSerializer.ExtensionModel.Xml.Read], [Parameter: serializers(ExtendedXmlSerializer.ContentModel.Content.ISerializers)], [Requested dependency: ServiceType:ExtendedXmlSerializer.ContentModel.Content.ISerializers, ServiceName:]
  ----> System.InvalidOperationException : Unable to resolve type: ExtendedXmlSerializer.ContentModel.Content.IContents, service name:
  ----> System.InvalidOperationException : Unable to resolve type: ExtendedXmlSerializer.ContentModel.Collections.DefaultCollections, service name:
  ----> System.InvalidOperationException : Unresolved dependency [Target Type: ExtendedXmlSerializer.ContentModel.Collections.DefaultCollections], [Parameter: serializers(ExtendedXmlSerializer.ContentModel.RuntimeSerializers)], [Requested dependency: ServiceType:ExtendedXmlSerializer.ContentModel.RuntimeSerializers, ServiceName:]
  ----> System.InvalidOperationException : Unresolved dependency [Target Type: ExtendedXmlSerializer.ContentModel.RuntimeSerializers], [Parameter: serializers(ExtendedXmlSerializer.ContentModel.Content.ISerializers)], [Requested dependency: ServiceType:ExtendedXmlSerializer.ContentModel.Content.ISerializers, ServiceName:]
  ----> System.InvalidOperationException : Recursive dependency detected: ServiceType:ExtendedXmlSerializer.ContentModel.Content.ISerializers, ServiceName:]

Ah, yes indeed @gmkado the call to ISerializers.Get while in the constructor will result in a recursion.  You want to defer that into the body of the Get as such:
public class MySerializerDecorator : ISerializers
{
	private ISerializers _serializers;

	public MySerializerDecorator(ISerializers serializers) => _serializers = serializers;

	public ISerializer Get(TypeInfo parameter)
	{
		return parameter == typeof(Subject)
			       ? new ResolveReferenceSerializer(_serializers.Get(typeof(Subject)).For<Subject>())
				       .Adapt()
			       : _serializers.Get(parameter);
	}
}

Note that the result of this operation is cached so instantiating a new instance of ResolveReferenceSerializer is a one-time allocation per type which is then stored in a dictionary.
As for ISerializers vs. IContents:
ISerializers is intended for providing serializers that deal with XML document root nodes and list elements, and IContents is used for providing serializers that deal with only the contents of a object.
For some additional context, every object has a "container" context.  This could be the root document or the property/field of a parent serializer.  ISerializers returns the serializer that emits the entire graph (container + content) whereas IContents returns the serializer that only emits the content.
Note that a "container" is the start + end tags.  ISerializers is aware of these whereas IContents is not.
Please let me know if you have any further questions around this and I will do my best to answer them for you. 👍

Thanks for the clarification, that makes sense regarding the dependency injection, I didn't realize it was cached.
Regarding ISerializers vs IContents, can you give an example of when to use one vs the other?  As far as I can tell, I can use DecorateContentsWith + IContents or Decorate + ISerializers and get the same outcome.

Sure @gmkado let me think about this and see if I can get some sample code for you here to delineate the two scenarios.

Alright @gmkado I looked into this some more.  You are correct in that the approaches you mention are similar.  I would say the following about the two:

ISerializers returns the "external" or "container" serializer of a type.
IContents returns the "internal" or "content" serializer of a type.

Worth noting that the serializer returned from ISerializers has a reference to the serializer from IContents.  The serializer processes the "container" (or document/element node) of the object, then passes control to the IContents to do its own processing.
So that stated, the ISerializers serializer knows about the IContents serializer, but the IContents serializer does not know about the ISerializers serializer.
For reference, there are about a dozen implementations of ISerializers and nearly 3x more implementations of IContents in the codebase, making IContents the more utilized/popular of the two.
When I think of ISerializers, I think of the primary entry of an object, before anything has been processed.  As mentioned in the previous post this is typically -- if not exclusively -- for object/document roots and list elements.
As for examples, I think of RootInstanceExtension.Serializers (link) and CachedSerializers (link).  Root instances especially as it is basically capturing a root instance whenever it is passed it for serialization, for use in additional processing down the line.
So to sum up for ISerializers I think it's best to think of "root element" and "list elements".  It handles the external "container" of an object and then passes control to the IContents serializer.  IContents is for the contents of an object/document/element and is primarily where the magic happens.  Most likely, you will want to be working with IContents, but in some cases you will be wanting to work with before that (the "container") so ISerializers is where you would go for that.
Hope that adds some clarification for you.  Please let me know if you have any further questions or points that need additional clarification.  FWIW I am tagging this post now as documentation for others who are searching for the same thing, so continue to ask away if you feel something needs further clarification. :)

Doh, I guess I said I was going to provide some code, but got distracted with traveling through the codebase and looking at existing implementations.  I figured I would use them instead as they do a better job anyways as, you know, working code. 😅  Hopefully those links provided will help assist in providing some further context and meet the intended effect.  Please let me know if that's not the case. 👍

@Mike-E-wins Thanks as always for the quick and detailed response.  I'm new to coding in general so digging through the codebase has been very helpful in learning how to write decoupled code.
That being said, I'm finding it a bit tricky to follow whats going on behind the scenes (I guess those go hand in hand).   So this bit was particularly helpful for me:

The serializer processes the "container" (or document/element node) of the object, then passes control to the IContents to do its own processing.

Is the process of how IContents and ISerializers pass and execute control documented anywhere?  I'm trying to look through the code to see how this works but it would be helpful to have a framework in my mind as I go through it.

Ah so we're actually really in uncharted territory I'm afraid, @gmkado.  Earlier in the year (or late last year) we took a pass at improving the documentation and even though we (I) spent a ton of time addressing conceptual concerns I wasn't able to make it into the customization/extension model.
The thinking -- besides there being limited time to spend on such matters -- is that the extension model is considered "advanced" so if someone has any questions around this they can ask away and I will do my best to assist.  I guess what I should do is have a better strategy/plan around sharing existing code with good examples to get interested developers better on their way.
Along such lines, one thing I did want to mention is that, to add to the above, the "root" ISerializers is a good place to start to see where control is passed off to IContents:
https://github.com/ExtendedXmlSerializer/home/blob/master/src/ExtendedXmlSerializer/ContentModel/Content/Serializers.cs
You can see that on line #19 the IContents.Get is called.  You can also see the Container in action there as well.  I think I should have led with that. 😆  But you can see it's very simple and is the "kernel" implementation that is then subsequently wrapped with further decorations.

Thanks @Mike-E-wins .  I do feel like the true power of this library comes from the extensibility, so it would be nice if that were a little more accessible.  I wonder if you could have a "dumbed down" version of the ISerializerExtension that could decorate a type's serializer without the dependency injection boilerplate.  Ideally I just want to write the ISerializer and register it with its type (similar to IConverter and the v1 IExtendedXmlCustomSerializer).
Also, its not clear to me how to use IFormatReader and IFormatWriter, so a section in the documentation about those would be useful.  As an example, say I have the following class:
       public class CommandList : ICommand
        {
            public List<ICommand> Commands { get; set; } = new List<ICommand>();
        }

These can be nested so my xml ends up looking something like
<?xml version="1.0" encoding="utf-8"?>
<CommandList xmlns:exs="https://extendedxmlserializer.github.io/v2" xmlns:ns1="clr-namespace:System.Collections.ObjectModel;assembly=System" >
  <Commands>
    <CommandList >
      <Commands>
        <CommandA />
        <CommandB />
...
      </Commands>
    </CommandList >
  </Commands>
</CommandList >

Now this is a very simplified model of what I actually have.  I have some command lists that are purely lists and some that have other attributes.  For the commands that are purely lists, I'd like to intercept the serialization and have it serialize something like:
<?xml version="1.0" encoding="utf-8"?>
<CommandList xmlns:exs="https://extendedxmlserializer.github.io/v2" xmlns:ns1="clr-namespace:System.Collections.ObjectModel;assembly=System" >
    <CommandList >
        <CommandA />
        <CommandB />
...
    </CommandList >
</CommandList >

I.e. clean it up by taking out the superfluous Commands tags.  My first pass in a unit test was to do something like this:
sealed class CommandListLifter : ISerializer<CommandList >
            {
                readonly ISerializer<CommandList > _previous;

                public CommandListLifter(ISerializer<CommandList > previous) => _previous = previous;

                public void Write(IFormatWriter writer, CommandList instance)
                {
                    instance.Commands.ForEach(c =>
                    {
                        writer.Start(new MyIdentity()); // <-- how to correctly use IIdentity
                        writer.EndCurrent();
                    });
                }

                public CommandList Get(IFormatReader parameter)
                {
                    var instance = _previous.Get(parameter);           // <-- how to read it back?
                    return instance;
                }
            }

As you can see from my comments, its not clear to me how to correctly use IFormatWriter and IFormatReader to get what I need.  Thanks again for your help!

Oh man, what you are after here @gmkado is default content, which is something of a sore topic with me, mainly because I have not been able to figure out a way to do it myself.  This has been captured in #240.  I have given it a go several times now and it's failed due to the design of the reader.  The reader needs a rewrite, pure and simple.
As for IFormatReader and IFormatWriter, you're right that those need some love.  I'm honestly not very happy with the documentation, it's very v1 -- but at least there's "something" which was pretty much the intention when going through it at the start of v3.  The problem is that it is really like its own project of its own, and takes a lot of time and energy, even when done poorly. 😆
The best I can do in light of #383 is try to help out with some code for you.  I will see if I can put aside some time here in the next day or so to get you something that can provide you some better context/knowledge on how the pieces are put together.

Looking into this now @gmkado ... one thing I did notice that I wanted to share is that there's this notion of composing serializer, which you can use to essentially intercept the serializer creation pipeline and then further use to decorate created serializers.  Here's some code demonstrating that for you:
https://github.com/ExtendedXmlSerializer/home/blob/master/test/ExtendedXmlSerializer.Tests.ReportedIssues/Issue349Tests.cs
I also like this as it makes use of the IIdentityStore so you can see how identities are defined/utilized.

I believe we have addressed this issue as much as possible.  Ideally we should have some advanced documentation but my time is fully spent in fixing bugs with this project.  If, however, you manage to get comfortable around the topic and have something to add, I would be more than happy to accept a pull request. :)
In any case, please do let me know if there is any further assistance you require on this issue (or any other) and I will do my best to assist.
Closing for now.


[ENH]: don't allow a null collection ID on segments

Description of changes
Makes the segments.collection column on single node not null, and updates segment types to make collection ID required everywhere. (The segments.collection_id table on distributed was already not null.)
Also fixes the Makefile for protoc generation for Go, and omits the debug service when generating Python files.
Motivation: segments should always have a collection ID, and segment relationships can be expressed via other fields in the future. Having the collection ID allows us to make more efficient queries, simplifies checks, and makes it easier to do query pushdown in the future. Note that existing segments have always had a collection ID, it's just been boxed in an optional.
This came out of the work in https://github.com/chroma-core/chroma/pull/2613 where the collection ID is required for segment gRPC requests.
Test plan
How are these changes tested?

[x] Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?
n/a

#2613
#2626  👈
main

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

Join @codetheweb and the rest of your teammates on  Graphite

looks good - only question is around the ON DELETE CASCADE in segment_metadata still working after the new table is created

confirmed that this is still present after the migration


Correct return value description

Previously the page said it returned nothing but it returns a string

@dthaler : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@stevewhims the gai_strerrorW page needs the same fix


Problem with Range Callbacks

Hi,
I have set the lower and upper bound respectively to 1 and 100 with a minimum diff of 10, but the callbacks always return me a range between 0 and 1.
here is my code.

Is it possible to also get callbacks that stride by minDifference  (in this case 10) ?
Thanks.

Hi, thank you for posting the issue. I think it's better to inform you that this tool is ill-designed, and it would be troublesome to use it in production environments. I will consider developing a better version after I've got my work in hand done. (The current version is still 0.2.0, which you could regard as a crazy flawful test ground...)
val in the callbacks returns the relative value. You can have your code work fine by accessing the .lowerRange and the .upperRange members.

Does this help?

Thanks, it working now.
It would be great to add an stride parameter in the api.


Template parsing errors can't handle unicode in headers

Many of the errors raised in parsing, including the non-unicode character check, print the column header as part of the error. In qiita pet, some of these errors are explicitly converted to string (see here as an example). This means that if the column headers have unicode characters, the system throws a secondary error trying to print the original error.

We haven't seen this kind of errors in a while, since the changes to the loading and parsing of files. Thus, closing.


Replace usa-input--error-message with usa-error-message (LG-3288, LG-3277)

Why: For improved alignment with USWDS, to reduce the likelihood of inconsistent error styling.
Relevant USWDS documentation: https://designsystem.digital.gov/components/form-controls/#text-input
Toward LG-3288, this backports the following revisions from IDP:
https://github.com/18F/identity-idp/blob/73c3c13/app/assets/stylesheets/components/_typography.scss#L51-L57
Open questions:

USWDS includes more styling for error messages than what had existed previously with usa-input--error-message (padding, display, font weight). Are all of those stylings agreeable, or should we revert back to the original styling? For example, overriding font weight back to normal.
As noted in the associated tickets, USWDS uses the error-dark color token for error messages. Based on how errors are styled throughout the IDP, I've opted to keep this as the existing error color token in the styling overrides.
The Login Design System also includes an error message variant including an icon, styled using the usa-input--error-message-with-icon class. This pull request does not currently propose any changes to this class, though in considering this as a BEM modifier of the error message class, it may be appropriate to update this accordingly to usa-error-message--with-icon.

Screenshots:

Before
After

The Login Design System also includes an error message variant including an icon, styled using the usa-input--error-message-with-icon class. This pull request does not currently propose any changes to this class, though in considering this as a BEM modifier of the error message class, it may be appropriate to update this accordingly to usa-error-message--with-icon.

To expand on this, part of the reason I second-guess making this change in the first place is because the previous usa-input--error-message class was named as though it were a modifier of some usa-input BEM block. With these revisions, usa-error-message becomes its own proper block, leaving open the question of whether the "with icon" continues to be a modifier of usa-input or of usa-error-message.

Talked with @aduth and had a discussion around how this might effect the layout (e.g. cause shifting at various break points) may occur. Approved once that has gotten his 👍

Assessing potential impact:

Vertical space: Because usa-error-message applies a 0.25rem padding, surrounding content may be pushed up or down by this amount. In most cases, this should not have a noticeable impact as long as the flow of content on the page can adapt to occupying more height. Notably, the exception here is if the message would be shown in a container of a fixed height. In practice, it does not appear that usa-input--error-message is used in any product, and as such would not be expected to regress in existing usage.
Block display: Because usa-error-message applies display: block, error messages would not be rendered inline and instead on their own line. This is consistent with USWDS guidance, and in most cases has only a positive result. For example, the "Dates" example of Form validation errors in the live Login Design System website has the error message and hint running together without this styling, and would become clearer after these changes.

Before (usa-input--error-message)
After (usa-error-message)

Again, since usa-input--error-message is not currently used in any product, there would not be any regressions on existing usage.

The Login Design System also includes an error message variant including an icon, styled using the usa-input--error-message-with-icon class. This pull request does not currently propose any changes to this class, though in considering this as a BEM modifier of the error message class, it may be appropriate to update this accordingly to usa-error-message--with-icon.

As proposed, in 5ce4aab I opted to rename usa-input--error-message-with-icon to usa-error-message--with-icon. Since "with icon" is intended to a variant of the error message, BEM conventions would dictate that it be named as such, and not as a modifier of usa-input.
Similar to as noted in my previous comment, there is currently no usage of usa-input--error-message-with-icon in any product, and as such it would not be expected that this change should cause any regressions. That being said, strictly-speaking it is a breaking change, and if we'd document changes in release notes, it should be mentioned.


add autobahn testsuite

Added a note to the readme stating our compliance to the Autobahn testsuite and linked to a document describing how to create a echoserver and run the tests against it.

Codecov Report

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

@@          Coverage Diff           @@
##           master     #40   +/-   ##
======================================
  Coverage    92.4%   92.4%
======================================
  Files           9       9
  Lines         500     500
======================================
  Hits          462     462
  Misses         38      38

Flag
Coverage Δ

#KituraWebSocket
92.4% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


[ci skip] [cf admin skip] NO_CI adding bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I've added bot automerge as instructed in #2.
Merge this PR to enable bot automerging.
Fixes #2

@conda-forge-admin please rerender

Hi! This is the friendly automated conda-forge-linting service.
I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.
Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.


Empty created_at

Laravel Version: 5.6.17
Voyager Version: 1.1.0
PHP Version: 7.2
Database Driver & Version: SQLITE3

Description:
When I create a record with the BREAD, the created_at column is null.
I would like it to have the current time
Steps To Reproduce:
Create a record

This is nothing Voyager controls, but pure Eloquent behaviour.
https://laravel.com/docs/5.6/eloquent#defining-models
You actually have to define that you dont want to use timestamps.
Can you confirm that you dont have public $timestamps = false; in your model?

I don't have public $timestamps = false; in my model

You need to have add unchecked for created_at field in your bread configuration, otherwise you'll need to fill the value manually.
I can't think of anything else.

Can you share your bread settings for that table along with the Model class.

Here is the Model

@lucasdcrk you have already the solution in my previous comment.
This is the default configuration for timestamps when you create BREAD:

It worked! Thanks!
I changed it by mistake


Download links for SSMS 18.10 and 18.9.2 are targeting the same resource

Download links for SSMS 18.10 and 18.9.2 are targeting the same resource (SSMS 18.9.2, build 15.0.18386.0)
Download SSMS 18.10 https://go.microsoft.com/fwlink/?linkid=2168063
Download SSMS 18.9.2 https://go.microsoft.com/fwlink/?linkid=2168063
source uri: Release notes for (SSMS) - SQL Server Management Studio (SSMS) | Microsoft Docs

@hS6ZQZHwgT -- thank you for catching this.  I am updating the article.

Following up; it appears the correct uri for the download should be https://go.microsoft.com/fwlink/?linkid=2174135. I was able to successfully acquire the 18.10 installer with this uri.

Thank you for your feedback.  I have updated the documentation and it should be live by tomorrow.


Comment clarification

Feature Summary and Justification
Clarifying the format of ''parent_id''.

Apparently, that breaks something in Sphinx. I have no experience with Sphinx and thus no idea how to solve the problem or why it is breaking. It has something to do with "target names" according to CI.

docstring of praw.models.Comment:24: WARNING: Unknown target name: "t1".
docstring of praw.models.Comment:24: WARNING: Unknown target name: "t3".

I only added "t1", it should already have been failing on "t3" before my change.

Sphinx thinks that you're trying to link to something else, because RST uses a trailing underscore to mark links. You could try escaping the underscores (r1_ would become r1\_, and you'd need to change line 25 to start with r""" rather than just """), or you could just try removing the underscores.

This is not what I wanted but at least it passes CI now. In my opinion, the "_" was an important piece of information for anyone using the API. It's not that  important since they'd have found out soon enough through experimentation.
Thanks for the help.

Do you think it would be possible to rebase and squash your commits?

@RichardHoekstra if the underscores are important (which I agree they are), try:
``t1_``

This will apply monospaced formatting to the text inside, while allowing you to easily use the underscore. See raw of this file for an example.

@PythonCoderAS rebased and squashed
@jarhill0 thank you, that seems to work and that same format is used elsewhere in the code. I found some other low hanging fruit to add the underscore to and for the sake of consistency changed the quotes in 'redditors.py'  as well.

@RichardHoekstra could you please add yourself to the authors.rst file under documentation contributor?

Thanks again! 🎆

This is an old copy, the mistake has been fixed.

@Pyprohly @PythonCoderAS the mistake is in the merged commit.
https://github.com/praw-dev/praw/blob/2ab8fbaf2dadbd428097e894263fbc23431a50d1/praw/models/reddit/comment.py#L48-L50
It should be (https://www.reddit.com/dev/api/, see: type prefixes)
    ``parent_id``    The ID of the parent comment (prefixed with ``t1_``).                             If it is a top-level comment, this returns the                             submission ID instead (prefixed with ``t3_``).
I didn't catch that when you proposed the change to my prior mistake. How do we deal with this?

It’s a lot of work for a small change, eh? 😂
You’ll have to submit another PR now. Or leave it and someone else will fix it later.

I'll create a new PR in a second. Half hour of work for adding an underscore to a comment. :-)


selecting AOs of specific atoms in AVAS method

Hi PySCF Team,
I was wondering if it's possible to select AOs of specific atoms in the AVAS method? As far as I can tell the implementation allows you to select AO's in the form of for instance ['Fe 3d'] - is it possible to target the AO's of specific atoms and not all atoms of a specific species. E.g. if there is more than one transition metal atom or if you are interested in including AO's of other species around a transition metal atom but not all atoms of that type in the whole structure?
Many thanks,
Georg

Hi @schusteritsch, PySCF allows you to decorate atom symbols and AVAS can see those. Here's a minimal example, where I label one iron atom with !:
from pyscf import gto, scf, mcscf
from pyscf.mcscf import avas

mol = gto.M(atom="!Fe 0 0 0; Fe 0 0 1", basis="def2tzvp", verbose=5)
mf = scf.RHF(mol).run()

ao_labels = ['!Fe 3d']
norb, ne_act, orbs = avas.avas(mf, ao_labels, canonicalize=False)

Here's an excerpt from the output showing that it's only trying to match again a single atoms AOs:
reference AO indices for minao ['!Fe 3d']: [10 11 12 13 14]

Hi @jamesETsmith
Thanks for this - I didn't realize you could decorate atoms this way. This works exactly the way I had hoped!

Happy to help! Closing the issue now, but feel free to reopen if you have more questions about this.

Hi @schusteritsch, PySCF allows you to decorate atom symbols and AVAS can see those. Here's a minimal example, where I label one iron atom with !:
from pyscf import gto, scf, mcscf
from pyscf.mcscf import avas

mol = gto.M(atom="!Fe 0 0 0; Fe 0 0 1", basis="def2tzvp", verbose=5)
mf = scf.RHF(mol).run()

ao_labels = ['!Fe 3d']
norb, ne_act, orbs = avas.avas(mf, ao_labels, canonicalize=False)

Here's an excerpt from the output showing that it's only trying to match again a single atoms AOs:
reference AO indices for minao ['!Fe 3d']: [10 11 12 13 14]

If I have several different atoms like carbon atoms in pyradine, how can I identify them in ao label?


Using performance patches from Thorium project

Description
Using performance patches from Thorium project
Who's implementing?

[ ] I'm willing to implement this feature myself

The problem
Hi guys.
I've used Thorium browser (https://thorium.rocks) for awhile but found it a bit bloated, but it runs pretty fast, you can check the speed on https://browserbench.org/Speedometer3.0
As for Ungoogled-Chromium, in many cases it consumes CPU (even with libva-intel-driver in my case), when watching videos on Youtube.
Possible solutions
Don't you want to implement some of performance paches from Thorium to speed Ungoogled-Chromium up?
Best regards,
Sergey.
Alternatives
No response
Additional context
No response

Duplicate of https://github.com/ungoogled-software/ungoogled-chromium/discussions/2372?

At any rate, we aren't able to address compiler bugs which will definitely arise because of enabling such optimizations and really if Google doesn't have the capacity to deal with such issues and doesn't think it's worthwhile then it's really not worth it.


Local pull request success status testing

Docs Build status updates of commit f041efc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

E2E_DocsBranch_Dynamic/index.md
:white_check_mark:Succeeded
View

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


error with orchardcore-preview build 2561

Hi, I upgraded a test app from Version="2.0.0-preview-2518" to Version="2.0.0-preview-2561"
and the cms does not start. (this also happens from 2555 to 2556, if you downgrade to a version <=2555 it works)
The following error occurs
orchard> fail: Microsoft.AspNetCore.Server.Kestrel[13]
Connection id "0HL5UTANOASC6": An unhandled exception was thrown by the application.
System.InvalidOperationException: Could not resolve feature for type AdminController
at Orchard.Environment.Extensions.TypeFeatureProvider.GetFeatureForDependency(Type dependency)
at Orchard.Mvc.ModularApplicationModelProvider.OnProvidersExecuted(ApplicationModelProviderContext context)
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionDescriptorProvider.BuildModel()
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionDescriptorProvider.GetDescriptors()
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionDescriptorProvider.OnProvidersExecuting(ActionDescriptorProviderContext context)
at Microsoft.AspNetCore.Mvc.Internal.ActionDescriptorCollectionProvider.GetCollection()
at Microsoft.AspNetCore.Mvc.Internal.ActionDescriptorCollectionProvider.get_ActionDescriptors()
at Microsoft.AspNetCore.Mvc.Internal.AttributeRoute.GetTreeRouter()
at Microsoft.AspNetCore.Mvc.Internal.AttributeRoute.RouteAsync(RouteContext context)
at Microsoft.AspNetCore.Routing.RouteCollection.d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Builder.RouterMiddleware.d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Orchard.DeferredTasks.DeferredTaskMiddleware.d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Modules.ModularTenantRouterMiddleware.d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Modules.ModularTenantContainerMiddleware.d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Hosting.Internal.RequestServicesContainerMiddleware.d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Server.Kestrel.Internal.Http.Frame`1.d__2.MoveNext()

Hi, some more info and steps to reproduce.

Create a new Webapplication and add OrchardCore.CMS package.
Make the changes needed to add OrchardCMS and UseModules
Run, the error appears.

If you add Orchard.Queries as a nugget dependency to the WebApplication, the app starts.
This behavior exists after 2518 build

https://github.com/OrchardCMS/Orchard2/commit/f95533724d3ab35d68fc5f770116a6fe4656cd4b

I will take a look when i have time.
That said @MichaelPetrinolis mentioned Orchard.Queries and, in OrchardCore.Cms.csproj, this is the only one for which PrivateAssets="none" is not specified.
Maybe not the root cause regarding the commit dates ...
But this could explain that the bluid counterpart of Orchard.Queries would not be executed when indirectly referenced through the bundle (assets would not be copied, e.g the manifest file), but would be when referenced through the web app directly.
I also saw that in Orchard.Queries.csproj and Orchard.Lucene.csproj there are useless ItemGroup defining individual asset PackagePath which are normally globaly defined in AsModule.props.

I thought I'd take a look since my commit got referenced, although my initial thinking is that it wouldn't be related since the ShellContainerFactory change deals with Startup features and this error is caused by an AdminController feature not being found, which is the responsibility of ExtensionManager to add to TypeFeatureProvider.
Anyway from what I can see if you change Line 21 in TypeFeatureProvider to log the full type name:
throw new InvalidOperationException($"Could not resolve feature for type {dependency.**FullName**}");
It becomes clear that ExtensionManager is having issues loading Orchard.Queries since the exception is now:
System.InvalidOperationException: Could not resolve feature for type Orchard.Queries.Sql.Controllers.AdminController

If you look at the Packages folder in the website root, there is no Orchard.Queries folder and therefore my guess is that ExtensionManager can't find Orchard.Queries' Module.txt to load the features for the module. MVC still loads the referenced assembly however and finds the controller via the automatic ApplicationPartManager which is why the error is originating from ModularApplicationModelProvider due to the mismatch of the controller being present without any feature metadata.
So I would agree with @jtkech that there is something misconfigured in the project/nuget package of Orchard.Queries that is causing Module.txt to not be copied to the Packages folder.
My suggestions:

Change TypeFeatureProvider to log the FullName of the type instead of just Name. This will make the responsible module clearer in the future if any fail to load.

Check the project files of Orchard.Queries (and others) for inconsistencies.

Remove the need for Module.txt files ;)

I didn't take the time to try it because i would need to re-pack all the projects and use a local feed. So, it's better to update the repo through a PR.
But i think we only need to add PrivateAssets="none" for the Orchard.Queries package reference in OrchardCore.Cms.csproj. This as done for other modules references.
I'll do a PR.

Thanks @jtkech , that does seem to be the difference.
If you look at orchardcore.cms.nuspec:
        <dependency id="Orchard.Queries" version="2.0.0-preview-2606" exclude="Build,Analyzers" />
        <dependency id="OrchardCore.AsBundle" version="2.0.0-preview-2606" include="All" />
        <dependency id="Orchard.Admin" version="2.0.0-preview-2606" include="All" />
        ...

The  exclude="Build,Analyzers" would block the 'build/netstandard1.6/Orchard.Queries.props' from being included and therefore not set the PackageAssetFiles variable which holds the files to copy to the Packages folder.
Feels good to find the root cause and not have it be my change!

Exactly, don't worry ;)

updated to v2.0.0-preview-2629, removed orchard.queries nuget package from host and works


options has an unknown property 'plugins'

https://github.com/arackaf/customize-cra/blob/7e97127e530cc6827af66061525e29925e347670/src/customizers/webpack.js#L161

can look at this. https://github.com/arackaf/customize-cra/issues/315#issuecomment-1009628736


Remove School Users

Context
We need to be able to remove users from schools.
Changes proposed in this pull request

Add remove flows for both Users and Support Users.
Updated ApplicationPolicy to create sensible defaults.

The update? method is not used within the UsersController scope and undercover is blocking changes, therefore, we will keep the default update? as false for now.

Guidance to review

Try adding a User and removing them.
You shouldn't be able to remove yourself from a school when signed in as a non-support User.

Screenshots

Change
Screenshot

Added "Remove user" link

Added /schools/:school_id/users/:user_id/remove path

Removal alert

Looks good to me


Rewrite OpenAI feedback provider to use guidance's chat mode

This will enable us to use the (much cheaper) GPT-3.5 Turbo model instead of the current davinci.

As far as I can tell, this is already done


The two input windows pop up multiple times

I'm trying to use the X-Tension with XWF 20.5 SR-1 x64, but I get prompted multiple times to specify the location of the YARA rule file and the MB/size value. Apparently, the number of times is equal to the number of objects/partitions highlighted in the "Case data window" before running the X-Tension.

Hi @forensenellanebbia - I noticed this too a while back. I think it's to do with the code being executed in the XT_Prepare() API call, whereas I should be placing this in the XT_Init() call. Let me see if I can test a fix for you.

@forensenellanebbia - I've pushed version 1.1 which fixes this multiple user input issue. Hopefully that works for you. See https://github.com/CrowdStrike/xwf-yara-scanner/tree/main/Compiled X-Tensions

Fixed in version 1.1

Awesome, thanks! I tried it and worked perfectly.


Add bundler cache to Travis CI

@sorentwo CI fixed, and rebase on latest commit. Could you please have a look?

Thanks for the patch!


Includes to remote Gitlab task files doesn't work

Environment
Device and OS: N/A
App version: uds v0.10.3
Kubernetes distro being used:
Other:
Steps to reproduce

Add anincludes to a remote Gitlab task.yaml:

includes:
  - sshuttle: https://##REMOVED##/##REMOVED##/-/raw/main/uds-tasks/sshuttle.yaml

Run that task

Expected result
You are able to use the remote task file as you would in Github.
Actual Result
It gives the error below
Visual Proof (screenshots, videos, text, etc)

Severity/Priority
low

Thanks for the issue! We'll add it to our backlog

Hi @JaseKoonce , I've been looking at this today and wanted to check and see how much of an issue this is for you and how high of a priority it is.
It's fairly messy to implement the authentication against private GitLab repositories because GitLab requires a custom header for this and doesn't support basic auth. I discussed with @Racer159 and one thing we are wanting to do anyway is add support for publishing tasks as OCI artifacts and allow importing tasks through OCI as well. If you had that you could import them as OCI instead of trying to import directly from the GitLab raw url.
We wanted to make sure this isn't something you need solved immediately and if it could wait and solve through the OCI support. I did see you noted it as 'low' priority/severity but just wanted to touch base. Thanks!

Hi @JaseKoonce , I've been looking at this today and wanted to check and see how much of an issue this is for you and how high of a priority it is.
It's fairly messy to implement the authentication against private GitLab repositories because GitLab requires a custom header for this and doesn't support basic auth. I discussed with @Racer159 and one thing we are wanting to do anyway is add support for publishing tasks as OCI artifacts and allow importing tasks through OCI as well. If you had that you could import them as OCI instead of trying to import directly from the GitLab raw url.
We wanted to make sure this isn't something you need solved immediately and if it could wait and solve through the OCI support. I did see you noted it as 'low' priority/severity but just wanted to touch base. Thanks!

@ericwyles Its not a blocker right now just something that would be nice to have in the future. Currently to get around the issue I am cloning my template task files via a CI job and using them for the length of the job. Being able to publish tasks as OCI artifacts would work for us, but I'm not sure that it would be the preferred method. Happy to chat more about use cases if you think that would be helpful. Thank you for looking into this!


Upgrade to GeoCombine 0.9.1

Problem
GeoBlacklight 4.4.0 requires GeoCombine 0.9 which has changed some of the Indexer interfaces, causing the indexing of documents (and this gem's test suite) to fail.
Solution
Upgrade to official GeoCombine 0.9.1.
Type
Bug fix

Closing this as there is a bug in GeoCombine 0.9.1 that results in documents being skipped during indexing. We need to wait for that bug fix to be merged in and release.


Features : Mapping, Bool, Unicode, Int, Float

This is based on #2 so don't merge before #2.
Add all the basic features found in Eapii. This is close to what I did in Eapii so feel free to comment I don't want to impose my way.

Mapping : support mapping a user value to an instrument value is back
Bool : Mapping(for True, False) + support aliases allowing to pass 'On' instead of True (NB the answer is always True never 'On')
Unicode : simple feature for string like objects, support set of allowed values
Int : support set of allowed values or limits (either fix or by ID, ie a limit is declared by writting a limits* methods full support for this new construct has been added)
Float same as Int and support for unit (this is not mandatory and can work without Pint, we can also add an option so that even if unit supports is available the returned value will be a float). For the time being the value is always returned in the same unit, we could add more options.
I tried to keep each commit quite focused so doing the revision commit by commit should be 'easy'.

Let's try to merge the other PR and this by next week so we can move forward

It is fine with me. I will also prepare a PR with the PyVisa backend if I find some more time.

Look at the Lantz MessageBasedDriver.

I was planning to. I will try to take the best of it and the Eapii MessageBasedDriver.

ping @LabPy/owners

i just read your commit comments,
is the Unicode type a combination of String  and Enum?
is there any type for lists?
i also deal a lot with complex arrays, but i dont think this is a common usage.

It is a subclass of the base enumerable feature indeed. There is no String Feature, but we could have a Byte Feature perhaps. I prefer to enforce the bytes/unicode as it is likely to bite people when going from 2 to 3.
For arrays I don't think we need it as I guess that those arrays are mostly read-only (measure of a PNA or spectrum analyser) or do you have a use case where having a Feature for getting/setting an array make sense ?

so, here is an example for get/set calibration coefficients  for a vna where an array/list might be appropriate.
https://github.com/scikit-rf/scikit-rf/blob/master/skrf/vi/vna.py#L1278-L1327
that example is a actually is a dict of arrays, and you can see i have to translate to and from a comma seperated string. i could see a List type being used for get/set frequency-dependent data (like for importing data ->memory), which you might want on a SpecAnalyzer too
a common data flow for a VNA  would be:
complex array -> real tuple array -> string -> VNA
then backwards.
certain things make sense to form higher objects to, like multiport s-parameters  are effectively sets of complex arrays, to the above data flow would have an additional layer at the front.

Interesting I never used that on my PNA (but we do only very basic measures). The only thing I worry a bit about is the re-usability of the Array/List Feature as the conversion is most likely to be very specific to the instrument. I will have to think more about this one. But anyway we should address this in a subsequent PR I think.

It's also possible to implement something like that with getters and setters.  Not sure what makes the most sense.  I agree that we should open an new issue/PR for it, though.

We can always start from a raw Feature and do what we want so we keep a Feature for consistency.

sounds good

Note : this requires the current development version of Pint

I will merge it this week-end if nobody says no. I will also open an issue for the Array Feature.


[Python] provide a wrapper script to initiate the Python agent without code changes in user app

Please answer these questions before submitting your issue.

Why do you submit this issue?
[x] Question or discussion
[ ] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?
Now java can use non-invasive way to use skywalking, such as :
java -jar $JAVA_AGENT -jar lab-39-demo-2.2.2.RELEASE.jar

But python needs to add code to the original project， such as：
from skywalking import agent, config

config.init(collector_address='<IP_ADDRESS>:11800', service_name='your awesome service')
agent.start()

How does python use skywalking in a non-intrusive way like java？

For now, this is the only way to use Python agent, non-intrusive way needs some wrapper script to wrap the Python interpreter, if you're interested in contributing we can discuss.

Is this possible in theory?

Is this possible in theory?

It's possible

I'm quite interested in this one, could you elaborate a bit more on how this can be achieved? @kezhenxu94

I'm quite interested in this one, could you elaborate a bit more on how this can be achieved? @kezhenxu94

@Superskyyy thanks for your interest, the basic idea is to write a command line tool (in Python language, for example, named sw-python) and start the SkyWalking Python agent first, then start the user-app command, e.g. sw-python app.py, or sw-python gunicorn myproject.wsgi, or sw-python django ......, etc.
I haven't had a chance to look into the details but the following might be a start point:
import os
import sys

from skywalking import config, agent

if __name__ == '__main__':
    args = sys.argv[1:]

    bin_directory = os.path.dirname(sys.argv[0])

    python_exe = os.path.basename(sys.executable)
    python_exe_path = os.path.join(bin_directory, python_exe)
    if (not os.path.exists(python_exe_path) or
            not os.access(python_exe_path, os.X_OK)):
        python_exe_path = sys.executable

    config.service_name = 'provider'
    config.logging_level = 'DEBUG'
    agent.start()

    os.execl(python_exe_path, python_exe_path, *args)

Ha I see how it works. I'll first finish the log reporter related work then start implementing this one.

Shall we introduce some new user friendly config file for the command-line option to use?
It could be used like the following
sw-python --config=sw_agent.yaml run your application

@kezhenxu94  Shall we introduce some new user friendly config file for the command-line option to use?
It could be used like the following
sw-python --config=sw_agent.yaml run your application

We could do that but it's optional because all the configurations can be set via env vars, it's the wrapper script's responsibility to pass the env vars down to the agent.

@kezhenxu94  Shall we introduce some new user friendly config file for the command-line option to use?
It could be used like the following
sw-python --config=sw_agent.yaml run your application

We could do that but it's optional because all the configurations can be set via env vars, it's the wrapper script's responsibility to pass the env vars down to the agent.

Got it, will make it optional.

After some investigation, I believe a sitecustomize script is the right way to go. Using pure exec* overrides the whole process thus using a new interpreter instance, thus won't work.

@Superskyyy site module is another option, if it works, I'm totally OK to use it.