Some of the log calls can crash the fez review call

https://github.com/tony-o/raku-fez/blob/1163df343b9808e9110c8430d4456868217a14f8/lib/Fez/CLI.rakumod#L334C1-L345C4
This segment contains a couple of calls that take a formatter parameter but there is no placeholder variable in the message. Two layers down, at a sprintf call, this will crash if the program executes any of the log calls.

@2colours tyvm, this will get released in the next ver

released -


Documentation is not clear regarding "Allow interaction with custom apps" org-wide setting

Hello,
"Allow interaction with custom apps" description in the Teams admin center and in the docs.microsoft.com page is not clear, based on what we saw by testing the 2 values for this setting (or we do not have the same definition of "Custom App").
Our use case was to forbid users from chatting with externals bots by deeplink (bot apps not uploaded to our tenant by a Teams admin, i.e. this feature: https://learn.microsoft.com/en-us/microsoftteams/platform/bots/how-to/debug/locally-with-an-ide#talk-to-your-bot-directly-by-id ; deeplink is like "https://teams.microsoft.com/l/chat/0/0?users=28:< GUID >"), but to allow them to use apps uploaded by a Teams admin in the "Manage apps" page of the Teams admin center (upload of a zip file).
And this can be done only by setting "Allow interaction with custom apps" to "Off", which is counter-intuitive and does not correspond to what is in the documentation, according to me.
You say:
"The Allow interaction with custom apps org-wide custom app setting on the Manage apps page applies to everyone in your organization and governs whether they can upload or interact with custom apps. This setting acts as a master on/off switch for the user and team custom app policy settings. It's intended to serve as a master on/off switch during security events."
I think you should say:
"The Allow interaction with custom apps org-wide custom app setting on the Manage apps page applies to everyone in your organization and governs whether they can upload or interact with custom apps (it does not govern interaction with custom apps uploaded by a Teams Service Admin or a Global admin). This setting acts as a master on/off switch for the user and team custom app policy settings. It's intended to serve as a master on/off switch during security events."
You say:
"Interaction with all custom apps is blocked for your organization"
I think you should say:
"Interaction with all custom apps is blocked for your organization. Interaction with custom apps uploaded by a Teams Service Admin or a Global admin is still allowed, if the custom app has the 'Allowed' status."

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

ID: d51bb7b1-801e-6801-dcaf-afa3e38e6941
Version Independent ID: d8e726a1-cbf2-53c7-da4d-cc155b48612b
Content: Manage custom app policies and settings - Microsoft Teams
Content Source: Teams/teams-custom-app-policies-and-settings.md
Service: msteams
GitHub Login: @ashishguptaiitb
Microsoft Alias: guptaashish

Hi @orandev, thank you for your feedback.
I think it's currently there:
"Interaction with all custom apps is blocked for your organization. Custom apps can't be uploaded by anyone except a Teams Service Admin or a Global admin."

Hello @dariomws
It's not the same thing. There is "Interaction" on one side and "Upload" on the other side.
It says "Interaction is blocked for everyone" and "Custom apps can be uploaded by a Teams admin". For me, the second part does not imply that "interaction is allowed for custom apps uploaded by admins".

Hi @orandev,
Why will an admin upload the app if users cannot interact with it? :)
Anyway, please check the update I have proposed 33 minutes ago.

In your PR, I would say "If this setting is set to Off, only a Teams Service Admin or a Global admin can upload custom apps and users will be able to interact with them." instead of "Only a Teams Service Admin or a Global admin can upload custom apps and users will be able to interact with them.".


Release roles bug

The release_roles() function did not handle additional selection options correctly - changing dsl_spec.rb:18 highlighted the problem with the existing code. I reworked the Property filtering code to make it cleaner and more capable (added shortcut for property equality tests).
Improved documentation and added new tests

Will resubmit this after sync'ing up with latest master....

Thanks Nick
Sent from my Nexus 5.
On 27 Jan 2015 23:27, "Nick Townsend"<EMAIL_ADDRESS>wrote:

Will resubmit this after sync'ing up with latest master....
—
Reply to this email directly or view it on GitHub
https://github.com/capistrano/capistrano/pull/1351#issuecomment-71741502
.


Not able to use User ID and Password when using connection string of Azure analysis server

When trying to use this library in Python application, the library is ignoring the credentials passed in the connection string. It again prompts with SSO screen for consent.
connection_string = "Provider=MSOLAP;Data Source=asazure://someas_url/someserver;Catalog=gfhfghtr;User ID=####;Password=####"
with Pyadomd(connection_string) as conn:
with conn.cursor().execute(generated_dax_query) as result:
df = pd.DataFrame.from_records(result.fetchone())
df.columns = [i.name for i in result.description]
tableresponse = st.table(df)
When using above connection string the system still prompts me to login, the library is not using the user id and password supplied to it.

Please help to get it resolved, or to identify any additional steps missing
Thanks for your help

Have you tried using a service principal user instead? The query string needs to be User ID=app:{APP_ID}@{TENANT_ID};Password={APP_SECRET} I have gotten this working fine but I haven't tried a normal user, I suspect it might be something to do with MFA being on for that user meaning you can't use it in this manner.

Have you tried using a service principal user instead? The query string needs to be User ID=app:{APP_ID}@{TENANT_ID};Password={APP_SECRET} I have gotten this working fine but I haven't tried a normal user, I suspect it might be something to do with MFA being on for that user meaning you can't use it in this manner.
Sorry just to add my example is connecting to the powerbi api: powerbi://api.powerbi.com/v1.0/myorg/ and I think I do have this working for a user with MFA turned on so maybe it's an analysis server difference?

Can you showme and example plss ?


Create release-notes-may-2020.md

Initial commit for new release notes for desktop VR headsets

Docs Build status updates of commit 1f0745c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/release-notes-may-2020.md
:warning:Warning
View
Details

mixed-reality-docs/release-notes-may-2020.md

Line 21: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 24: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/windows/mixed-reality/new-microsoft-edge' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 36637be:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/release-notes-may-2020.md
:warning:Warning
View
Details

mixed-reality-docs/release-notes-may-2020.md

Line 21: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 24: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/windows/mixed-reality/new-microsoft-edge' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 345eeb0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/release-notes-may-2020.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Login with email or phone number

Preflight Checklist

[X] I could not find a solution in the existing issues, docs, nor discussions
[X] I have joined the ZITADEL chat

Describe your problem
Some services, especially mobile-first, want users to login with their phone number. As alternative they let users register with email (or use email as recovery).
Examples are Facebook, Uber, Google etc.
Describe your ideal solution
As an end-user, I can enter my email or phone number or username on the login page, and continue to login with my user
Version
No response
Environment
ZITADEL Cloud
Additional Context
It is currently possible to login with email xor phone number by changing the username format. This feature should allow users to be able to use either their phone number or email on the login screen, when this feature is enabled.
Seems like this feature is more useful in B2C cases than B2B cases.

It is currently possible to login with email xor phone number by changing the username format. This feature should allow users to be able to use either their phone number or email on the login screen, when this feature is enabled.

That's what I mentioned in the Additional Context, yes. Can a user enter either their email address or their phone number (not limited to one or the other) in the username field, like in the services mentioned above?

It is currently possible to login with email xor phone number by changing the username format. This feature should allow users to be able to use either their phone number or email on the login screen, when this feature is enabled.

That's what I mentioned in the Additional Context, yes. Can a user enter either their email address or their phone number (not limited to one or the other) in the username field, like in the services mentioned above?

yes they can use what they like to login.

Replaced by https://github.com/zitadel/zitadel/issues/7411


Word replacement  with synonym after translation

Hi, I have found this tool very much helpful and excellent effort and help.
I want to know that after translation, is there any way that if I want to replace the word by its synonym, can I call any function?
Please if you can guide.

There is no such function implemented

If any chance to get any ability of synonym replacement would be a great addition.


Access log file per frontend

I haven't found anything in docs - but this is one thing I'm really missing from Caddy. Is it possible to specify a log file per frontend?

I'll close the issue due to inactivity but feel free to re-open if needed.

Is there any way to implement this? Are there any plans to include it?

An alternative might be to use something like logstash or fluentd and filter by frontends (or any other key) in a post-processing step.

+1


PATH environment variable doesn't work within a plugin

I have to install latest version of plugin on latest version of Atom. Now when I run it I cannot get access for a PATH variable (it says that command is not recognized as exe, batch file and so on).
It's probably because when console shows, it writes that "PSReadline module load failed. Console is running without PSReadLine". Message is localized so It could vary, but the meaning is the same.
When I run Powershell from Start menu everything works fine.

Confirmed, using the set command also produces no results, as well as setting variables within the shell, ex. `set VAR="example".

I am getting the same error...

I also have "PSReadline module load failed. Console is running without PSReadLine".
Atom 1.7.4
Terminal-plus 0.14.5
Windows 10


Batch Size in Alignment Pretraining

Based on the scripts you provided, the batch size per GPU is set to 2, which totals 16 across 8 GPUs, and this configuration is working fine. However, in the paper, the total batch size is mentioned as 128, with 16 per GPU. When I attempt to train the model with this batch size, I encounter a "out of memory" error.

Thanks for your attention. Since we use gradient_accumulation_steps=8, the effective batch size of the script is actually 16*8 = 128.


Minor typo within welcome E-mail template

Recently I signed up on open collective for one of our projects - Mevn-CLI

mevn.madhacks.co

I just noticed a minor typo on the welcome E-mail that came out thereafter.

Towards the end of the Get & manage funds section the word approved is misspelled as evident from above.

Thank you for reporting. Are you fancy creating a PR for it?
https://github.com/opencollective/opencollective-api/blob/f807ce3757e8e5adde8c7579499589728a8a906a/templates/emails/github.signup.hbs

Sure :+1:

@znarf Check out #2273

@znarf Would love to know your thoughts on Mevn-CLI

@jamesgeorge007 I'm not practicing Mongo or Vue, so I don't have a lot of thoughts on it. Unfortunately!

@znarf Well, you could show off your support and love by leaving a :star: :smile:

@znarf Well, you could show off your support and love by leaving a :star: :smile:


Abort item gathering when quit UI

Use events instead of checking flags in a loop, because we can't cancel until the next chunk arrives.
For example, if you run ddu-soure-rg in the root directory... the ripgrep process will continue to run even if you quit the UI.

Thank you.


t_obs must be 4?

I followed the quickstart and using source class on https://legwork.readthedocs.io/en/latest/notebooks/Source.html, and I get the following error for calculating SNR whenever I use anything other than t_obs = 4.0 * u.yr:
>>> snr_10 = sources.get_snr(t_obs=4.000000000000001 * u.yr, verbose=True)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/kayhan/miniconda3/envs/legwork/lib/python3.9/site-packages/legwork/source.py", line 477, in get_snr
    "{} but this function".format(self._sc_params["t_obs"]),
KeyError: 't_obs'

If I do not set t_obs or set it to 4 yr it works (albeit with many warnings from the ode solver).

Good catch @kayhangultekin, thank you! I tried adding a warning message in a recent PR and it seems I actually made things worse haha 🙃
Also yeah the warnings from the ode solver are annoying, we are working on that.

Thanks again for pointing this out Kayhan (and sorry it took me a week to reply! I don't seem to get notifications for issues). I've now changed the default functionality so that the sensitivity curve with automatically get re-interpolated if you change the mission length in the get_snr() function. Hope this makes for an improved user experience.
Glad that you're taking a look at LEGWORK, we're very open to feedback if you have more thoughts! 😄


Add "is null" and "is not null" relations

Relates to https://github.com/byjg/php-anydataset-db/pull/26


Scala Native crash for Aspect

Scala Native is crashing after https://github.com/getkyo/kyo/pull/839. I had the same issue in https://github.com/getkyo/kyo/pull/843 after adding an aspect to Parse.
[error] /home/runner/work/kyo/kyo/kyo-prelude/native/target/scala-3.5.2/native-test/generated/1a0c1.ll:585314:52: error<EMAIL_ADDRESS>defined with type 'i8* (i8*, i8*)*' but expected 'i8* (i8*)*'
[error]   %_4000001 = call dereferenceable_or_null(16) i8* @"_SM11kyo.Aspect$D15init$$anonfun$1L16java.lang.ObjectL15scala.Function1L16java.lang.ObjectEpT11kyo.Aspect$"(i8* dereferenceable_or_null(16) %_2)
[error]                                                    ^
[error] 1 error generated.
[info] Compiling to native code (5815 ms)
[info] Total (17149 ms)
[error] Failed to compile /home/runner/work/kyo/kyo/kyo-prelude/native/target/scala-3.5.2/native-test/generated/1a0c1.ll
[error] (kyo-preludeNative / Test / nativeLink) Failed to compile /home/runner/work/kyo/kyo/kyo-prelude/native/target/scala-3.5.2/native-test/generated/1a0c1.ll

It seems an issue with the new Cut encoded as a generic function:
type Cut[I[_], O[_], S] = [C] => (I[C], I[C] => O[C] < S) => O[C] < S

To reproduce:
mv kyo-prelude/jvm/src/test/scala/kyo/AspectTest.scala kyo-prelude/shared/src/test/scala/kyo/AspectTest.scala
mv kyo-prelude/jvm/src/test/scala/kyo/ParseTest.scala kyo-prelude/shared/src/test/scala/kyo/ParseTest.scala

Issue is fixed in Scala Native (https://github.com/scala-native/scala-native/issues/4082) but I'll keep this ticket open so we can move the files back once there's a release with the fix.


dont force ampm

undo force am/pm format with certain intents when requesting a location
(instead depend on the global setting for 24/12 system)

description
copilot:summary
Explanation of changes
copilot:walkthrough
copilot:poem

thanks, but a big overhaul is incoming, handling this in its wake.


Fdg 5973Update Homepage Topics Section Copy and Tiles to Include Spending Explainer

https://federal-spending-transparency.atlassian.net/browse/FDG-5973
Carri said to use the image in the code instead of the ones on mac
The Topics section is updated to ensure the new subtext verbiage below the 'Your Guide to America’s Finances' heading reads as follows: “Fiscal Data presents the third of four concepts from Your Guide to America’s Finances, which will be added in the coming months.”. Note - This copy is not included in the Homepage MAC as this text will soon be removed for the Revenue/AFG Overview release.
The 'Your Guide to America’s Finances' section is updated to have three tiles included. The new Spending explainer tile is added in the primary tile location and the Deficit tile is moved to the secondary location in top position. Note - the design mock will not have Spending reflected in the correct location.
All copy related to the tiles matches the copy in the Homepage MAC.
The Spending explainer tile in the 'Your Guide to America’s Finances' section displays as expected on desktop and mobile.
CC: 89.47%

Update to move spending to primary.


chore: Configure testing environment using ts-jest and adjust project settings

This PR configures the testing environment with ts-jest to support TypeScript testing and improves various project configurations. Key changes include:

Testing Configuration:

Removed the old jest.config.json and replaced it with a TypeScript-based configuration file (jest.config.ts).
Set up Jest to use ts-jest for TypeScript transpilation and configured the test environment to node.
Added a .env.test file for environment variable management specific to the testing environment.
Configured Jest to load the environment variables from .env.test during testing via the jest.setup.ts file.

Project Setup Adjustments:

Updated package.json with dependencies for ts-jest, ts-node, and dotenv for managing environment variables.
Refined ESLint configurations to handle TypeScript test files and resolve missing imports.
Adjusted the tsconfig.json paths and root directory to work seamlessly with TypeScript and Jest.
Added a basic test file (test/telegram.test.ts) to validate Telegram class functionality.
Removed the outdated sample.test.ts file.

Miscellaneous:

Updated .gitignore to include .env.test for test environment isolation.
Ensured all necessary files and configurations are set up for a consistent and efficient testing environment.

This setup ensures a clean, reliable environment for running tests with TypeScript support, improving code quality and maintainability.

everything's cool we only need a way to initialize 2 instances in which we can track which one received another one's messages

I get your concern, but there’s no need to worry, we can rely on Telegram’s server responses for this.


Fix unaligned dereferencing (preparation for Rust upgrade)

Analysis:

Unaligned pointer dereferencing has undefined behavior in Rust: https://doc.rust-lang.org/reference/behavior-considered-undefined.html
Using 64-bit fields in a struct implies that the struct is also 64-bit-aligned. This is however not guaranteed in our heap as objects are only 32-bit aligned.
The recent Rust version occasionally checks misaligned pointer dereferencing. This currently fails in Stream.rs and in BitmapIterator.rs for the Compacting GC. However, it is correctly aligned in the incremental GC.
Simplification: The implicit padding for 64-bit field alignment depending on the header size and the GC (incremental or not) is now removed.

Intended as a fix for the build errors in https://github.com/dfinity/motoko/pull/3947.

Comparing from 66c55a1 to f2aaa0b: In terms of gas, 2 tests regressed, 2 tests improved and the mean change is +0.0%. In terms of size, 4 tests improved and the mean change is -12.4%.

The performance of this PR without Rust upgrade will be remeasured in https://github.com/dfinity/motoko/pull/3999.

I like how you divide the 64-bit members into two consecutive 32-bit ones, and how that avoids padding. Thanks for doing this!

Thank you also very much for reviewing!

LGTM
We'll need to be careful that @matthewhammer's regions PR doesn't introduce more 64-bit object fields.

Thank you very much for the review. Yes, we need to be careful about future inserts of 64-bit fields. Once we have moved to new Rust version, the error would probably be reported at runtime.


AttributeError: 'VAE' object has no attribute 'clone' in forge_layerdiffusion.py

When I enable layer diffusion in sd-forge, it has no effect. The resulting image is not transparent and is identical to the one generated with layer diffusion disabled. The error occurs within the process_before_every_sampling() function in the forge_layerdiffusion.py script. Here's the relevant information:
[Layer Diffusion] LayerMethod.FG_ONLY_ATTN
*** Error running process_before_every_sampling: E:\stable-diffusion-webui-forge\extensions\sd-forge-layerdiffusion\scripts\forge_layerdiffusion.py
    Traceback (most recent call last):
      File "E:\stable-diffusion-webui-forge\modules\scripts.py", line 835, in process_before_every_sampling
        script.process_before_every_sampling(p, *script_args, **kwargs)
      File "E:\stable-diffusion-webui-forge\extensions\sd-forge-layerdiffusion\scripts\forge_layerdiffusion.py", line 130, in process_before_every_sampling
        vae = p.sd_model.forge_objects.vae.clone()
    AttributeError: 'VAE' object has no attribute 'clone'

Operating system: Windows 11

you need to update forge

Yes, just noticed. Thx! 😊👍


Ordering of fonts in pubspec.yaml affects rendering on CanvasKit

Steps to Reproduce
See https://github.com/rydmike/mr_font_test
When fonts are ordered:
flutter:
  fonts:
    - family: Roboto
      fonts:
        - asset: assets/fonts/Roboto/Roboto-Thin.ttf
          weight: 100
        - asset: assets/fonts/Roboto/Roboto-Light.ttf
          weight: 300
        - asset: assets/fonts/Roboto/Roboto-Regular.ttf
          weight: 400

all Text widgets that don't have an explicit weight set are rendered with weight 100.
Reordering them so that the 400-weight font appears at the top of the list causes a line like:
const Text(
   'This page uses no specified font theme it should show up '
   'using the default font for each used platform.'),

to appear correctly.
This is a regression in CanvasKit compared to DomCanvas, where the font renders (as with mobile and desktop) with weight 400 in the above snippet regardless of the font ordering in pubspec.yaml.
(This bug is a tighter expression of #56319, now that we have pinpointed the issue.)
/cc @hterkelsen

I can only see thin text. I tried re-ordering the fonts, I tried setting fontWeight to normal. They all show thin text for me in CanvasKit.
Text(
  'This page uses no specified font theme it should show up '
  'using the default font for each used platform.',
  style: TextStyle(fontFamily: 'Roboto', fontWeight: FontWeight.normal),
)

I can confirm on the DOM backend, the text renders as expected.

@mdebbar That sounds interesting. When I tried the re-ordering it worked fine for my case with the CanvasKit and CanvasKit+CanvasText font issues in https://github.com/flutter/flutter/issues/56319
Do you have a simple example shows it not working?
For me it worked fine when I in my pubspec.yaml file reordered my font assets, like so:
flutter:
  fonts:
    - family: Roboto
      fonts:
        - asset: assets/fonts/Roboto/Roboto-Regular.ttf
          weight: 400
        - asset: assets/fonts/Roboto/Roboto-Thin.ttf
          weight: 100
        - asset: assets/fonts/Roboto/Roboto-Light.ttf
          weight: 300

For the actual case it was not just the Roboto font, a few other ones too and different styles of Roboto as well, like putting Roboto Italic Regular before the other italic weights.
Similar to what Tim did here for the issue demo code: https://github.com/rydmike/mr_font_test/pull/1/files but for my actual app. The last screenshot in issue https://github.com/flutter/flutter/issues/56319#issuecomment-666553493 also shows that it worked for the more complex app case and not just the issue demo.

/cc mdebbar: prior issue around font weight : https://github.com/flutter/flutter/issues/56319

@rydmike I'm testing on a brand new sample app:
import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  MyApp();

  @override
  Widget build(BuildContext context) {
    return Directionality(
      textDirection: TextDirection.ltr,
      child: Center(
        child: Text(
          'hello world',
          style: TextStyle(fontFamily: 'Roboto', fontSize: 24.0),
        ),
      ),
    );
  }
}

I always see this, even if I re-order the fonts:

I'll try this repo https://github.com/rydmike/mr_font_test.git to check if I see the same behavior.

I think that's because you're using the system fonts? I can repro this with the same Dart code if I add the following to my pubspec.yaml:
    - family: Roboto
      fonts:
        - asset: assets/fonts/Roboto/Roboto-Black.ttf
          weight: 900
        - asset: assets/fonts/Roboto/Roboto-Regular.ttf
          weight: 400
        - asset: assets/fonts/Roboto/Roboto-Light.ttf
          weight: 300
        - asset: assets/fonts/Roboto/Roboto-Thin.ttf
          weight: 100
        - asset: assets/fonts/Roboto/Roboto-Medium.ttf
          weight: 500
        - asset: assets/fonts/Roboto/Roboto-Bold.ttf
          weight: 700
        - asset: assets/fonts/Roboto/Roboto-ThinItalic.ttf
          weight: 100
          style: italic
        - asset: assets/fonts/Roboto/Roboto-RegularItalic.ttf
          weight: 400
          style: italic
        - asset: assets/fonts/Roboto/Roboto-LightItalic.ttf
          weight: 300
          style: italic
        - asset: assets/fonts/Roboto/Roboto-MediumItalic.ttf
          weight: 500
          style: italic
        - asset: assets/fonts/Roboto/Roboto-BoldItalic.ttf
          weight: 700
          style: italic
        - asset: assets/fonts/Roboto/Roboto-BlackItalic.ttf
          weight: 900
          style: italic

Here, the text is rendered differently depending on which weight is at the top of the list. For example:

I'm using Roboto too. Here's my pubspec.yaml:
flutter:
  fonts:
    - family: Roboto
      fonts:
        - asset: assets/fonts/Roboto/Roboto-Thin.ttf
          weight: 100
        - asset: assets/fonts/Roboto/Roboto-Light.ttf
          weight: 300
        - asset: assets/fonts/Roboto/Roboto-Regular.ttf
          weight: 400

  uses-material-design: true

Maybe because uses-material-design: true? I'll try removing it.

Weird -- I also have that line, just didn't include it.
Here's my repo: https://github.com/timsneath/fonttest
as it stands, it shows Roboto Regular when I run with flutter run -d chrome --release --dart-define=FLUTTER_WEB_USE_SKIA=true on ToT master.

I was able to repro this in release mode. For some reason in debug mode it always renders thin text even when I re-order the fonts.
Anyway, I believe the problem is happening here and here. Flutter refers to all of the Roboto-* fonts with the name Roboto. But our CanvasKit backend cares about the actual font names (e.g. Robot-Thin, Roboto-Light, etc). So we have a mapping from the flutter font name to the actual font name (Roboto -> Roboto-Thin). Since in this case Roboto refers to multiple actual fonts, we only pick the first one.
I tried to change the mapping so that a single font family maps to a list of actual font families (see code here). With that code, we are passing the entire list of font names to CanvasKit. But that didn't help. It seems like CanvasKit just picks the first font and doesn't care about the specified font weight. @hterkelsen any idea how this is supposed to work?


Simplify mechanism of providing params and retrieving result

Maybe create some sort of Resource (of python-simple-rest-client) that will handle passing arguments and fetching data.
Current usage:
 servers = await self.nova.api.servers.list(params={'name': '^my'})
 for server in servers.body["servers"]:
     print(server)

Expected usage:
 servers = await self.nova.api.servers.list(name='^my')
 for server in servers:
     print(server)

This issue shall be resolved by this PR: #20

By virtue of #20  I'm closing this issue as resolved :)


Error in running a launch file

-OS Platform and Distribution (e.g., Linux Ubuntu 14.04): 16.04
-Apollo installed from (source or binary): Source
-Apollo version (1.0, 1.5, 2.0, 2.5, 3.0)**: 5.0
I run the simulator and launch v2x by "v2x.launch". However, I received the following error. Can anyone help me?
[/apollo/bazel-bin/modules/v2x/v2x --flagfile=/apollo/modules/v2x/conf/v2x.conf] /apollo/bazel-bin/modules/v2x/v2x: error while loading shared libraries: libfastcdr.so.1: cannot open shared object file: No such file or directory

@Martin20  In most cases, This is about environmental variables. Usually libfastcdr.so.1 is located in /usr/local/fast-rtps/lib/, check the LD_LIBRARY_PATH  environment variable to see if /usr/local/fast-rtps/lib is in it, perhaps you may forget to execute source cyber/setup.bash.

Do you run the simulator and launch v2x in the docker environment?

Yes, I run it inside the docket.

@Eclipsehelio
I execute source "cyber/setup"

can you find libfastcdr.so.1 in your environment?

Closed due to inactivity. If the problem persists, pls feel free to reopen it or create a new one and refer to it.


Added IPv6 table to network page

Added IPv6 table to network page

Added stateless ipv6 config toggle
Edit ability is not working fine for now
The three toggles use DNS servers, use Domain names, use NTP servers are specific to interfaces now and not specific to ipv6 or ipv4

https://github.com/ibm-openbmc/webui-vue/pull/85  is the actual Pr for IPv6, hence closing this one.


Loader data for wildcard routes is somehow being cached

Describe the bug
I previously reported a bug where the loader would only run the first time for wildcard paths. It seems that this problem is fixed.
But now it happens that, although the loader runs, the value of the * parameter does not change after the first run.
You can clearly see the problem in the codesandbox example.
This does not work correctly:
const catchAllRoute = new Route({
  getParentRoute: () => rootRoute,
  path: "*",
  component: CatchAll,
  loader: ({ params }) => {
    console.log(`Loader for ${params["*"]}`);
    // LOADER PARAMS DO NOT CHANGE ON SUBSEQUENT RUNS
    return { data: `Loaded data for ${JSON.stringify(params)}` };
  }
});

However, this works without problems (with the problem that it does not match nested routes):
const catchAllRoute = new Route({
  getParentRoute: () => rootRoute,
  path: "$*",
  component: CatchAll,
  loader: ({ params }) => {
    console.log(`Loader for ${params["*"]}`);
    return { data: `Loaded data for ${JSON.stringify(params)}` };
  }
});

Your Example Website or App
https://codesandbox.io/s/gifted-herschel-4xthvm?file=/src/App.js
Steps to Reproduce the Bug or Issue
Click on page 1 and see the loader params. Then click on page 2. Loader params did not change.
Expected behavior
Loader params should change for each Link.
Platform
Ubuntu Linux
Node 18
React 18
Edit: I traced the issue to here in route.ts:
      // Waste not, want not. If we already have a match for this route,
      // reuse it. This is important for layout routes, which might stick
      // around between navigation actions that only change leaf routes.
      return (existingMatches.find((d) => d.id === matchId) ||
        new RouteMatch(this, route, {
          id: matchId,
          params: allParams,
          pathname: joinPaths([this.basepath, interpolatedPath]),
        })) as RouteMatch

Edit 2: dirty patched interpolatePath to account for wildcards. Now it works, but I'm not sure there is no collateral damage.
export function interpolatePath(
  path: string | undefined,
  params: any,
  leaveWildcard?: boolean,
) {
  const interpolatedPathSegments = parsePathname(path)

  console.log(interpolatedPathSegments, params)

  return joinPaths(
    interpolatedPathSegments.map((segment) => {
      if (['$', '*'].includes(segment.value) && !leaveWildcard) {
        return ''
      }

      // Added this

      if (leaveWildcard && segment.type === 'wildcard') {
        return params![segment.value] ?? ''
      }

      if (segment.type === 'param') {
        return params![segment.value.substring(1)] ?? ''
      }

      return segment.value
    }),
  )
}

This was the change I made as well, but there were some other repercussions that I needed to iron out. It should be fixed in the release that's going out right now.


feat(client): Add exclude option to the queries

Counterpart to prisma/prisma-engines#4807
Can be used standalone or combined with include, allows to exclude
the fields that normally would be included by default. Available in all
methods that return actual database records.
It is not useable together with select and attempt to do so would
cause type check and validation error.
When using together with result extensions, excluded dependency of a
computed field will be queried from a DB, but will not be returned to
the end user, unless computed field is exlucded as well (see "exclude
with extensions" tests in this PR). This behaviour is equivalent to what
we do if depenency of a computed field is not mentioned in explicit
select.
TODO:

[x] preview feature
[x] validation of non-existing fields in exclude

Close prisma/team-orm#1080
Close #5042

Note: tests are failing because https://github.com/prisma/prisma/pull/23776 needs integration first, it should not block the review though.


Dynamic destinations Branch

This PR is only for Easier readability and PR Tagging.
This the Branch that we are using to generate dataflow templates to pipe from a single PUBSUB topic to mulitple bigQuery Tables.
We are using PubsubToBigQueryDynamicDestinations.java which has been added into this project from github repo https://github.com/ryanmcdowell/dataflow-bigquery-dynamic-destinations
and modified to fit us.

@logason is missing the commit you did to fix the schema stuff?

@logason is missing the commit you did to fix the schema stuff?

The schema fix is on the branch in the monorepo


Update CHANGELOGs post-release

Update CHANGELOGs where relevant and also fix some inaccuracies in RELEASING.md.

Perfect! You got the git tags for the released packages too. Very nice job!

Cheers! I've just realised that I also have to update the flake.lock file to make sure that CHaP is up-to-date, right?

I also have to update the flake.lock file to make sure that CHaP is up-to-date, right?

Nope, not in cardano-base, because regardless what is on CHaPs, this repo will use cardano-slotting and strict-containers from this repo.
It is the index-state and flake.nix need to be updated in ledger repo.

I also have to update the flake.lock file to make sure that CHaP is up-to-date, right?

Nope, not in cardano-base, because regardless what is on CHaPs, this repo will use cardano-slotting and strict-containers from this repo.
It is the index-state and flake.nix need to be updated in ledger repo.

Ah okay, makes sense. Thanks for clarifying!


PR link to GitHub api url

I'm comfortable with it!
I found a problem that when you click on a PR number, you are redirected to the URL of the API, so I checked the repository, and it seems that the following PRs are used
https://github.com/Gamesight/slack-workflow-status/commit/9cc863f8369fe43931daff811fb17c55b5a5c4eb
I'd like to use it, so I'd like you to type a version of tag with the above fix applied

The master branch should have those fixes, I've created a new release tag which contains all the latest security patches and PR link fix here v1.0.1


Mock importing undefined not mocked value

Describe the bug
I want to test a function and mock a custom module with vi.mock and vi.mocked(...).mockReturnValue(...) but the mock always returns undefined in the tested file (but not in the .test.ts file).
I already tried to add the workaround from !1918
Reproduction
https://stackblitz.com/edit/vitest-dev-vitest-gdhswk?file=vite.config.ts
System Info
System:
    OS: Windows 10 10.0.19043
    CPU: (8) x64 Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz
    Memory: 3.00 GB / 15.81 GB
  Binaries:
    Node: 18.8.0 - C:\Program Files\nodejs\node.EXE
    npm: 8.18.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (105.0.1343.42)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    @vitejs/plugin-vue: ^3.1.0 => 3.1.0
    vite: ^3.1.3 => 3.1.3
    vitest: ^0.23.4 => 0.23.4

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Well, you mock the call after the module is already evaluated. You need to use await import('../src/withI18nMessage'), or mock a call inside vi.mock.

Ups, thanks for your help! 👍


issue with Mail.app .emlx files

I have a bunch of old Mail.app message files (.emlx) that contain resource forks.
I tried using resource_dasm on one of them, and it produced a .emlx_cmpf_1.bin file.
Is this a compressed resource of some kind?
Any suggestions on what to do with it?

There are no other resources.
This may be an example described in:
https://wiki.sleuthkit.org/index.php?title=HFS￼
Is there a command line way of doing a zlib decoding?

On Feb 26, 2023, at 5:16 PM, Martin Michelsen @.***> wrote:
I'm not familiar with that resource type. This article (https://blog.fosketts.net/2009/09/11/bizarre-hfs-tricks-in-mac-os-x-10-6-snow-leopard/) seems to imply that it could be a trick Apple used to implement per-file compression in HFS+. Are there any other resources in the .emlx files?
—
Reply to this email directly, view it on GitHub https://github.com/fuzziqersoftware/resource_dasm/issues/69#issuecomment-1445534371, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSSJGOXJBXWC3RIQ6HFUH3WZP56DANCNFSM6AAAAAAVIZITHA.
You are receiving this because you authored the thread.

I should add that the one file I have examined also has a data fork that looks reasonable, so perhaps the resource fork is redundant and was somehow left behind after Apple stopped using this compression hack?

On Feb 26, 2023, at 5:16 PM, Martin Michelsen @.***> wrote:
I'm not familiar with that resource type. This article (https://blog.fosketts.net/2009/09/11/bizarre-hfs-tricks-in-mac-os-x-10-6-snow-leopard/) seems to imply that it could be a trick Apple used to implement per-file compression in HFS+. Are there any other resources in the .emlx files?
—
Reply to this email directly, view it on GitHub https://github.com/fuzziqersoftware/resource_dasm/issues/69#issuecomment-1445534371, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSSJGOXJBXWC3RIQ6HFUH3WZP56DANCNFSM6AAAAAAVIZITHA.
You are receiving this because you authored the thread.

Github's search found this code: https://github.com/adrianstephens/orbiscrude/blob/fc4e57b2e7a021858eb100491ebaee63fb01e65e/shared/filetypes/container/apple_apfs.cpp#L936
And according to https://wiki.sleuthkit.org/index.php?title=HFS#HFS.2B_File_Compression the icat tool, which is part of sleuthkit, compresses these files:

icat will automatically decompress the file data by default.

Thanks to both of you for the helpful information.
This file is indeed an “HFS” compressed file (on APFS) as revealed by ls -alhO
I found a program afsctool (can be installed using brew) that shows information about compressed files.
File is HFS+/APFS compressed.
Compression type: ZLIB in resource fork (4)
File content type: com.apple.mail.emlx
File size (uncompressed; reported size by Mac OS 10.6+ Finder): 16956 bytes / 17 KB (kilobytes, base-10)
File size (compressed): 12288 bytes / 12 KiB
Compression savings: 27.5%
Number of extended attributes: 2
Total size of extended attribute data: 85 bytes
Uncompressed file size reported in compressed header: 16956 bytes
(The reported extended attributes are presumably ones that I installed, unrelated to compression.)
I now understand that the data fork is not a separate copy of the data, it is the virtual result of uncompressing the data in the resource fork.
Getting a uncompressed version of the file is trivial, just use cp.
Uncompressing the ZLIB data directly might be tricky as the resource fork has a non-standard header.


service_id required

From November 2016 service_id is mandatory. The code would need to be reviewed to support the use of service_id (it should be optional to avoid breaking change).

Why was this issue closed ?

I opened the issue by mistake. Readme and the code are already OK, no changes required.


Sometimes it dispatches twice

The first time I click on the button in this component...
@react.component
let make = () => {
  let (_state, send) = ReactUpdate.useReducer((state: int, _action: unit) => {
    Js.log("Handled Action")
    ReactUpdate.Update(state + 1)
  }, 0)

  <button
    onClick={_event => {
      Js.log("Sent Action")
      send()
    }}>
    {React.string("Send Action")}
  </button>
}

It logs:
Sent Action
Handled Action
Handled Action

But subsequent clicks log this instead:
Sent Action
Handled Action

However, in a more complex app, the doubled output shows up quite often, not just the first time.
Why is this?  Can you fix it?  Unfortunately my app doesn't handle double-dispatched actions well.
This problem manifests in both version 3 and version 4.

Hi! This is normal behavior due to the fact we use React's useReducer under the hood (https://github.com/facebook/react/issues/16295)
That shouldn't affect the behavior in your app if your reducer itself is pure.


Terraform 11 VPC module throwing errors

s3 endpoint on line 193 is causing issues, it is commented out in tag 0.15.2, but we will likely need to fix this until we upgrade cjm, sol, and cct to tf12

this issue is occurring across all version of terraform, not just version 11.

Change did not fix the issue, just removed some necessary code from the module. We are looking into how to fix long term.

Data Provides Multiple Results
We currently receive this error when trying to run terraform plans:

The reason for this is because there are multiple matches for VPC endpoint services that contain S3. Code below.
https://github.com/thinkstack-co/terraform-modules/blob/b3098f0fb10146d86596a17ae224439c4bf0fa8d/modules/aws/vpc/main.tf#L197-L199
To fix this issue what is needed is to narrow down the search to 1 VPC endpoint service. However, the issue with this is that there are 2 VPC endpoints for S3 that have the same endpoint name.
To see there are two services with the same name
Command:
aws ec2 describe-vpc-endpoint-services --filters Name=service-name,Values=com.amazonaws.us-east-1.s3
Results:

Problems
There is now way to differentiate between these two services. If we look at trying to filter the AWS documentation shows us that we have no filter that would differentiate the two. Source.
Example from source:

It would seem to be impossible to narrow it down to just one result. That would be a problem if the data were doing anything, but when we run a command with the same filters present in the code in the AWS cli we return no results.
Command:
aws ec2 describe-vpc-endpoints --filters Name=service-name,Values=s3
Results:

Since the CLI command shows no results, it makes me think that there are actually no results for this data block and it is effectively just providing an empty string. The data is pushed through to this block:
https://github.com/thinkstack-co/terraform-modules/blob/b3098f0fb10146d86596a17ae224439c4bf0fa8d/modules/aws/vpc/main.tf#L201-L205
Solution
At this point we know that the error was a result of the data filter not narrowing down the services to just one result, but we also know that the data cannot narrow the result down enough to be useful, therefore I would suggest we remove these lines from the module.
https://github.com/thinkstack-co/terraform-modules/blob/b3098f0fb10146d86596a17ae224439c4bf0fa8d/modules/aws/vpc/main.tf#L197-L199
We still need to fix the endpoint that is referencing that data though. To do that I would propose that we change line 204 from this location
https://github.com/thinkstack-co/terraform-modules/blob/b3098f0fb10146d86596a17ae224439c4bf0fa8d/modules/aws/vpc/main.tf#L201-L205
Which would be changed to this:
service_name = element("com.amazonaws.${var.vpc_region}.s3", count.index)
Then add a variable to the variables file.
variable "vpc_region" {   description = "The region for the VPC" }
Last, update the requirements for the module to require vpc_region to be used in the VPC's. This would allow us to have a region specified so that the S3 endpoint would be valid no matter the region.
Confirmation
Confirmed successful cases:

ventura_prod_infrastructure

From main.tf:

Last Run:

To confirm the run had this new code you can view commit 0c9066d here. You will see source set to the branch.

[ ] Code for TF 12 has this fix. Review and discuss with @zachreborn, see branch dev_actually_fix_s3_endpoints
[ ] Figure out how to implement the same fix in TF 11, syntax is difficult. Work in progress on branch dev_vpc_fix_tf_11
[ ] Discuss endpoints with @zachreborn and determine if they are doing anything yet. From what I can tell no clients have VPC endpoints.

Per zach edit this block and remove count, it should not be necessary.
https://github.com/thinkstack-co/terraform-modules/blob/8422c8c47c3820043322d1ee0bc72f3e9d54e8f5/modules/aws/vpc/main.tf#L207-L214


[7.0] Searching with Nested Relationships

Summary of problem or feature request
Hello,
I'm trying to build table with posts and users, each user have moderator. So table contains $post->id, $post->title, $post->user->email and $post->user->moderator->email. There is no problem with displaying content. But I can't understand how to use search with such type of relationships ($post->user->moderator->email).
This is part of my js:
columns: [
                    { data: 'id', name: 'id' },
                    { data: 'title', name: 'title' },
                    { data: 'user', name: 'user.email' },
                    { data: 'moderator', name: 'moderator' },
                ]

But now, if I try to search, I'm getting error that "Column not found".
I also tried to do something like this:
columns: [
                    { data: 'id', name: 'id' },
                    { data: 'title', name: 'title' },
                    { data: 'user', name: 'user.email' },
                    { data: 'moderator', name: 'user.moderator.email' },
                ]

But it doesn't work.
I'm using last version of yajra/laravel-datatables and laravel 5.3

@stsepelin sorry but only first level of relationship is currently tested to work with the package. Will try to implement this when I had the chance. Thanks!

Should be fixed on v6.22.0. Thanks!


Investigate and maybe switch to Netty 5

We're currently using Netty 4. Netty 4 is effectively EoL and Netty development is now focused on version 5. As an early stage project there is no particular benefit (e.g. in terms of compatibility/risk) in sticking with version 4. Switching to version 5 would bring these benefits to the project

Allow us to benefit from improvements in Netty 5 which won't be back-ported to 4.
Allow us to switch to JDK 17 for all the code without taking a performance hit

We should start investigating this, and make the switch if no major problems are found.
See also #71.

triaged, netty 5 still in the works and doesn't look to be coming soon

The last alpha for Netty 5 was https://netty.io/news/2022/09/28/5-0-0-Alpha5.html

Looks like Netty 5 is no longer the direction being pursued by the Netty community, who are now focussing on 4.2. Closing this.


[CUR-935] Add multiple curriculum partners in docx

Description
Music year: 1988

Added compatibility for multiple curriculum partners in the explainer section of the docx

How to test

Go to https://deploy-preview-2885--oak-web-application.netlify.thenational.academy
Download any curriculum document with two curriculum partners
You should see them both in the docx
You should see no change in docx with a single curriculum partner

Screenshots
How it used to look (delete if n/a):

How it should now look:

Checklist

[ ] Added or updated tests where appropriate
[ ] Manually tested across browsers / devices
[ ] Considered impact on accessibility
[ ] Design sign-off
[ ] Approved by product owner
[ ] Does this PR update a package with a breaking change

@sonalisin I think we need a isCycleTwoEnabled check in this PR, else we'll be going live with the multiple partners prior to cycle 2 launch.

@orangemug I don't think it matters that this isn't behind the cycle 2 flag, as there are no cycle 1 lots with multiple partners.


Glitch when opening Sidenav

[x] bug
[ ] feature request
[ ] enhancement

Expected behavior
No glitch when opening the menu
Actual behavior

Reproduction of behavior
https://stackblitz.com/edit/clarity-light-theme-v11-otmuux
Environment details

Angular version: 6.0.9

Clarity version: 0.12.4

OS and version: Windows 10

Browser: Chrome 67

Can you please provide a stackblitz or example for us to reproduce?

I'm also experiencing this bug.

Sure! https://stackblitz.com/edit/clarity-light-theme-v11-otmuux

Thanks, can confirm this on Chrome (but not Safari or Firefox) and also see it on our docs. We haven't made changes to this recently, so I'm wondering if it is something to do with the animations library, a recent Chrome change.
https://vmware.github.io/clarity/documentation/v0.12/vertical-nav/nav-groups/fire/charizard

I tested it on Firefox too but it's only chrome that seems to be having this issue.

I've also experienced this when there's an item that has a longer text.


kanban board setup

I @mercymugambi and @anbehindY have been paired to work on this space travel application.
Below is the link to the kanban board with tasks assigned to each one of us.
space-travel-project

Hi @mercymugambi & @anbehindY 🙋♂
Good job working on your Kanban board.👏
You still need to implement a few on the project but you are almost there!!! 🚶 :
TO HIGHLIGHT:
Assigning the group assignments to both students. ✔
STATUS: Required Changes :recycle:

Required Changes :recycle:

[ ] Please ensure that the required category cards are evenly assigned. At this stage, I have noticed that you are missing the conditional components category for @mercymugambi 😞. Kindly assign her to balance the tasks ☺.

Optional suggestions
N/A
Cheers, and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread or slack channel if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.
HAPPY CODING AND GOOD LUCK :crossed_fingers: :four_leaf_clover:

Hi @mercymugambi and @anbehindY,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
Highlights

Equally assign the work ✔

Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Version Flag

Hi @StevenBlack
Adding a version flag -v per issue #16

Thanks Esad @esadkrs this is really good!
Two small things, and I'll merge this.
First, we're currently at [Release v0.2.2](https://github.com/StevenBlack/ghosts/releases], so this version could be v0.2.3.Beta — I'm looking at semver.org.
Secondly, by convention, constant names are usually written in uppercase letters.  Since Golang is case sensitive, that variable name could be VERSION.
Otherwise this is good to merge!  Thanks!

Got it! I'll get on it right away!


Replace the sumstat for GCP000043 (PMID: 33204752)

The user has requested to replace the sumstat for submission id: 5f529a8ef10d27000109a3bc.
The updated file is placed in https://www.dropbox.com/home/Butler-Laporte G_ GCP000043
The submission has HLA allele in the rsid column and it needs to be manually pushed through

these are the list of GCST ids:
GCST90006884
GCST90006885
GCST90006886
GCST90006887
GCST90006888
GCST90006889
GCST90006890
GCST90006891
GCST90006892
GCST90006893
GCST90006894
GCST90006895
GCST90006896
GCST90006897
GCST90006898
GCST90006899
GCST90006900
GCST90006901
GCST90006902
GCST90006903
GCST90006904
GCST90006905
GCST90006906
GCST90006907
GCST90006908
GCST90006909
GCST90006910
GCST90006911
GCST90006912
GCST90006913
GCST90006914
GCST90006915
GCST90006916
GCST90006917
GCST90006918
GCST90006919
GCST90006920
GCST90006921
GCST90006922
GCST90006923
GCST90006924
GCST90006925
GCST90006926
GCST90006927
GCST90006928
GCST90006929

GCST ids.xlsx
The spreadsheet has the list of new sumstats file names from the dropbox folder and the corresponding GCST ids

ok so these need to be released but not added to the harmonisation pipeline?

This is done. There were harmonised files for all the studies so I removed them from the FTP. I have queued these new files up for harmonisation - I don't think hla alleles will be harmonised, but the rest of the file should.


Fix search CLI crash under Python 3.11+

Some of the configuration options in the search CLI used mutable dataclasses as defaults; for some reason, this is only detected by Python 3.11 onwards, therefore our CI running under 3.7 - 3.9 did not detect it, but under Python 3.11 the search CLI would crash with an error. What's worse, one of our environment files (environment.yml) did not pin the version of Python, leading to 3.13 being selected, under which the error would be present.
This PR makes the following changes:

Use the field constructor instead of mutable defaults to restore proper behaviour under all Python versions.
Run the CI under all Python versions ranging from 3.8 to 3.13 (the last stable version). In theory, it would likely be enough to test under 3.8 (oldest supported), 3.9 (used by single-step models) and 3.13 (newest supported). On the other hand, the core tests are fast and run in parallel, so testing under all versions shouldn't significantly increase time taken to merge PRs. Having a more extensive CI slightly increases the risk we run out of the 2000 free monthly CI minutes provided by GitHub, but a back-of-the-envelope calculation suggests that even doubling historical PR frequency would still not get us to run out, so we should be fine for now; we can always reconsider this if we ever happen to hit the limit. Finally, having more CI variants also increases the chance that we hit some test flakiness and need to rerun a subset of the CIs, but if anything this will motivate us to fix the flaky tests.

Actually, regarding the GitHub Actions limits: given that this repo is under a corporate microsoft account, and not a private one, I'm not sure what limit (if any?) applies here. Running CI in syntheseus does not seem to consume the free GitHub Actions minutes tied to my personal account.


clamp kernel blacklist for system-probe

What does this PR do?
For some kernel versions, using eBPF on it could cause kernel panic. After some testings seems like only the main stream kernel versions between 4.4.114 ~ 4.4.127 have this problem. Earlier version would most likely not have this bug introduced, and it is fixed in later versions.
Also fixed a bug in function kernelCodeToString.
Also add some packages needed for dev environment.
cc: @DataDog/burrito
Motivation
Clamp the range so we don't over block versions.
Additional Notes
Anything else we should know when reviewing?

Out of curiosity have you tested this internally on any of our trusty nodes to see if the agent successfully starts?

@sunhay Do you mean xenial? Trusty is in 3.13 and won't work anyway.

Whoops - yes I meant to say our Xenial version :)

It was tested manually and seem to work(it starts and not crashing the server). I guess we need to deploy it in devops during the freeze to test on everything.

Nice - it would be great to add some details in the description on how this range was calculated, as well as what tests were done to confirm it looked good :)


[Bugfix] ignore partition and columns name case when create mv.#9386

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
#9386
Problem Summary(Required) ：

CREATE TABLE t1 (
                  col1 int,
                  col2 double,
                  col3 varchar(20)
                ) ENGINE=OLAP
                DUPLICATE KEY(col1)
                COMMENT "OLAP"
                PARTITION BY RANGE(`col1`)
                (
                    PARTITION p1 VALUES LESS THAN ("100")
                )
                DISTRIBUTED BY HASH(col1) BUCKETS 3
                PROPERTIES (
                "replication_num" = "3"
                );

CREATE MATERIALIZED VIEW mv1
PARTITION BY COL1
DISTRIBUTED BY HASH(col1) BUCKETS 10
REFRESH ASYNC
AS SELECT col1, col2
FROM t1;

CREATE MATERIALIZED VIEW mv2
PARTITION BY COL1
DISTRIBUTED BY HASH(col1) BUCKETS 10
REFRESH ASYNC
AS SELECT COL1, col2
FROM t1;

If there are two identical fields ignore case in select , it will report error "Duplicate column name ".For example:
CREATE MATERIALIZED VIEW mv5
PARTITION BY COL1
DISTRIBUTED BY HASH(col1) BUCKETS 10
REFRESH ASYNC
AS SELECT COL1, col2 ,Col1
FROM t1;

ERROR 1064 (HY000): Duplicate column name 'col1'

[FE PR Coverage Check]
:heart_eyes: pass : 7 / 8 (87.50%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/analyzer/MaterializedViewAnalyzer.java
7
8
87.50%
[363]

@Astralidea PTAL

[FE PR Coverage Check]
:heart_eyes: pass : 7 / 8 (87.50%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/analyzer/MaterializedViewAnalyzer.java
7
8
87.50%
[363]

Add related UTs please.

ok, I have done it.

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test


Support more XDG directories

Please also support those directories:

USER_DIRECTORY_DESKTOP
USER_DIRECTORY_DOCUMENTS
USER_DIRECTORY_DOWNLOAD
USER_DIRECTORY_MUSIC
USER_DIRECTORY_PICTURES
USER_DIRECTORY_PUBLIC_SHARE
USER_DIRECTORY_TEMPLATES
USER_DIRECTORY_VIDEOS
USER_N_DIRECTORIES

I didn't see these in XDG standard? Where do you see them? I know Desktop isn't a thing for servers that don't have a window manager.

https://cgit.freedesktop.org/xdg/xdg-user-dirs/tree/user-dirs.defaults

It has been implemented here: https://github.com/adrg/xdg/blob/master/user_dirs.go


Hero: add style options to hero on homepage

The hero component should allow for different style options (see component library in Figma):

Text position: left, centre, right
Text background colour: dark blue, white or no colour
Text colour: dark blue or white
Background colour opacity: 100%, 60% or 0%

@justintemps I checked on some online tools and it seems that if the opacity is not lower than 60%, the colour contrast ratio passes AA. Can you please check?

If there's no background on the title, then always apply a drop shadow

Hey @inesdgomes, all of these things are already possible, you just have to fiddle with the settings in Storybook.
Example: with these settings...

You get this preview...

If you toggle hasbackground then you get this:

Ok. This one was also flagged by @PauZoocha, so just making sure it's all clear for you @PauZoocha ?
@justintemps could you please confirm that the background colour opacity only has 3 possible values (100%, 60% and 0%) and that they all pass AA for colour contrast ratio?


Insert metadata in (dataset) pages, and add sitemap, for (google)datasetsearch

Is your feature request related to a problem? Please describe.
I would like to find clowder datasets in https://datasetsearch.research.google.com/ and via other aggregators
Describe the solution you'd like
Insert json-ld into at least the dataset pages, and then an associated entry in the sitemap, so it can be crawled
Describe alternatives you've considered
Given the possibly very large numbers, we need to give just enough metadata to get in the right area, and then be able to follow the Linked-Data follow your nose pattern. This might mean allowing for (api) calls to get the file/etc metadata as needed.
Additional context
This will be done in stages, starting with the mapping of the dataset and file classes, which is in a draft-PR

sitemap will come later, as well as some of the other possible metadata
Right now just starting w/two classes: File and Dataset, to product jsonld describing their attributes mapped to schema.org vocabulary terms   In the end the two *.scala.html outputs can be taken from the output html and pasted into: https://validator.schema.org to that once the sitemap is there, all of those elements from the linked Datasets could end up in https://datasetsearch.research.google.com/

Dataset Files and the classes they hold instances of, all have to_jsonld methods, that get kicked off in the view; only other change was to signature of Utils.baseURL

After this is accepted, the next step is issue #351 to get the sitemap so the datasets can get crawled

pr comments have been closed for awhile, also not much sitemap feedback, so will look at other issues too


Fix Dockerfile

This PR fixes csproj file names in the Dockerfile.

Thank you very much for your contribution. 🎉


"Go to Definition" Should Navigate to an Existing Tab in Another "Editor Group" by Default

I have the definition of a symbol (a C struct in a header file) open in one "Editor Group" on the left. When I do a "Go to Definition" (F12 or Ctrl+Click) on that symbol in the other Editor Group I have on the right, I'd like it to navigate to that definition over in the Editor Group on the left where that header file is already open, instead of opening that header file again in the group on the right. I believe this to be the most intuitive default behavior.
After fishing through the settings for a while, I found that changing workbench.editor.revealIfOpen (which defaults to false) to true did the trick. I propose either renaming this setting to something more intuitive, or having an alias for it called something like workbench.editor.goToDefinitionAllowedToCrossEditorGroups.

or having an alias for it called something like workbench.editor.goToDefinitionAllowedToCrossEditorGroups.

I don't think that's a good name and I also dislike the idea of config aliases.

Passing to @bpasero to tweak the description of the setting to be more generic or include more words about when this the setting is picked up

I propose either renaming this setting to something more intuitive

Sorry, but how is workbench.editor.goToDefinitionAllowedToCrossEditorGroups more intuitive than what we have today? This setting applies to everything, not just "Goto definition"?

What about workbench.editor.revealIfOpenInAnyGroup?

@MBetters but the setting description should be more than enough to understand it no?

I think it would be a little clearer if the title of the setting mentioned Editor Groups, but it's not a big deal. It just took me a while to spot since I didn't know what I was looking for. I figured it might take other people a little while as well.


Home Assistant not working after upgrade to 0.83.3 (probably Openzwave related)

Home Assistant release with the issue:

0.83

Last working Home Assistant release (if known):
0.82.1
Operating environment (Hass.io/Docker/Windows/etc.):
Debian linux
Component/platform:
Probably related to open z-wave
Description of problem:
I just migrated my home assistant configuration from a raspberry pi to a NUC. Everything seemed to work fine, but since I was already a few versions behind (I think I was on 0.81.x) I decided to upgrade to the latest version, 0.83.3.
After that, I'm unable to use home assistant. When I start home assistant, I see these errors in the log:
Dec 07 11:02:05 nuc hass[440]: TypeError: expected bytes, NoneType found
Dec 07 11:02:05 nuc hass[440]: Exception ignored in: 'libopenzwave.str_to_cppstr'
Dec 07 11:02:05 nuc hass[440]: TypeError: expected bytes, NoneType found

and in the OZW_log is only see:
2018-12-07 11:02:05.561 Always, OpenZwave Version 1.4.3254 Starting Up

I'm unable to reach the UI of home assistant, even though parts of home assistent seem to be running, because when I enable logging for MQTT, I see messages coming in.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
zwave:
  usb_path: /dev/ttyACM0

Traceback (if applicable):

Additional information:
OS: Debian GNU/Linux 9
system: Intel NUC D34010WYK
z-wave: Aeotec USB Z-Stick
I have home assistant running in a virtual env
I did some more testing: When I downgrade to 0.82.1, everything works fine. When I upgrade to 0.83, the problem is present again.

same error here.
[code]
TypeError: expected bytes, NoneType found,
Exception ignored in: 'libopenzwave.str_to_cppstr',
TypeError: expected bytes, NoneType found,
[/code]

I have got the error in the log but all functioneren well. No issues so far.
Also running with docker

Seems like python-openzwave was upgraded to 0.4.11 with the 0.83.0 release via #18160. Maybe that's related?

Issue for me ended up being owntracks: #18809

@sidoh that issue and culprit looks promising. I do have owntracks rattling around. I will test in the coming day or two and report back.

I’m not using owntracks, so at the very least there could be multiple reasons (though an upgrade of openzwave sounds the most likely culprit)

My startup issue ended up being owntracks as well. Shout-out to @sidoh for pointing me in that direction.
My z-wave network seems healthy even though I still see the TypeError and the exception in the logs upon startup.

I just upgraded to 0.84.2, still the same problem.
I did actually have owntracks enabled in my configuration, but I was not using it. After removing it, home assistant was functional again, even though the errors (TypeError etc ) persist.

I might have the same issue, I cannot access the Frontend every morning, components like Hue_bridge, and alexa intent scripts all cannot run.
Then I see the OWZ_log.txt had the last save at 2:00 o'clock. Three continuous days, exactly same situation. So I guess the death of homeassistant was caused by Zwave.

Same here, but this started to pop-up without any upgrades (did an upgrade 2 weeks ago) and was keenly looking at the logs.
Dec 26 11:00:39 raspberrypi hass[21179]: TypeError: expected bytes, NoneType found
Dec 26 11:00:39 raspberrypi hass[21179]: Exception ignored in: 'libopenzwave.str_to_cppstr'
Dec 26 11:00:39 raspberrypi hass[21179]: TypeError: expected bytes, NoneType found

Curiously, zwave switches actually work, but my xiaomi_aqara component stopped working at the same time I saw the above. Could be a coincidence since I've looked at the logs because it stopped working.

Update: I tried to downgrade the homeassistant to 0.82.1 but next morning the issue still exists.
I used command: sudo systemctl Status home-assistant, and it said Status [dead] and the same description as above. NoneType found, libopenzwave.str_to_cppstr.

Dec 29 19:48:47 raspberrypi hass[5048]: TypeError: expected bytes, NoneType found
Dec 29 19:48:47 raspberrypi hass[5048]: Exception ignored in: 'libopenzwave.str_to_cppstr'
Dec 29 19:48:47 raspberrypi hass[5048]: TypeError: expected bytes, NoneType found
Dec 29 19:48:47 raspberrypi hass[5048]: Config directory: /home/homeassistant/.homeassistant
Dec 29 19:48:48 raspberrypi systemd[1]: Stopped Home Assistant.
There is error message:
Dec 29 19:48:47 raspberrypi hass[5048]: TypeError: expected bytes, NoneType found
Dec 29 19:48:47 raspberrypi hass[5048]: Exception ignored in: 'libopenzwave.str_to_cppstr'
Dec 29 19:48:47 raspberrypi hass[5048]: TypeError: expected bytes, NoneType found
But if I use command "sudo systemctl stop home-assistant" (without .service), it showed:
:~ $ sudo systemctl status home-assistant.service
● home-assistant.service - Home Assistant
Loaded: loaded (/etc/systemd/system/home-assistant.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Sat 2018-12-29 19:50:12 CET; 4s ago
Process: 11142 ExecStart=/srv/homeassistant/homeassistant_venv/bin/hass -c /home/homeassistant/.homeassistant (code=killed, signal=TERM)
Main PID: 11142 (code=killed, signal=TERM)
Dec 29 19:50:09 raspberrypi hass[11142]: 2018-12-29 19:50:09 INFO (MainThread) [homeassistant.loader] Loaded system_log from homeassistant.components.system_log
Dec 29 19:50:09 raspberrypi hass[11142]: 2018-12-29 19:50:09 INFO (MainThread) [homeassistant.loader] Loaded auth from homeassistant.components.auth
Dec 29 19:50:09 raspberrypi hass[11142]: 2018-12-29 19:50:09 INFO (MainThread) [homeassistant.loader] Loaded onboarding from homeassistant.components.onboarding
Dec 29 19:50:09 raspberrypi hass[11142]: 2018-12-29 19:50:09 INFO (MainThread) [homeassistant.loader] Loaded lovelace from homeassistant.components.lovelace
Dec 29 19:50:09 raspberrypi hass[11142]: 2018-12-29 19:50:09 INFO (MainThread) [homeassistant.loader] Loaded history from homeassistant.components.history
Dec 29 19:50:09 raspberrypi hass[11142]: 2018-12-29 19:50:09 INFO (MainThread) [homeassistant.loader] Loaded recorder from homeassistant.components.recorder
Dec 29 19:50:09 raspberrypi hass[11142]: 2018-12-29 19:50:09 INFO (MainThread) [homeassistant.loader] Loaded logger from homeassistant.components.logger
Dec 29 19:50:09 raspberrypi hass[11142]: 2018-12-29 19:50:09 INFO (MainThread) [homeassistant.setup] Setting up logger
Dec 29 19:50:12 raspberrypi systemd[1]: Stopping Home Assistant...
Dec 29 19:50:12 raspberrypi systemd[1]: Stopped Home Assistant.
There is then so such error message. The other difference is previous one is code=exited, second is code=killed. I don't know the reason, just post what I see.


Cannot parse two ifs

Fuzzing found a few more missing cases, having two if's does not seem to work yet.
Set<int> globx = {};

@NeverInline
int bar() {
  globx = { if (true) 3,           4 };  // OK
  globx = {           3, if (true) 4 };  // OK
  globx = { if (true) 3, if (true) 4 };  // NOT OK
}

hello.dart:40:13: Error: Expected ':' after this.
  globx = { if (true) 3, if (true) 4 };  // NOT OK
            ^
hello.dart:40:26: Error: Expected ':' after this.
  globx = { if (true) 3, if (true) 4 };  // NOT OK
                         ^

@a-siva

For what it is worth, fuzzing also found this issue for for-loops.
Also, putting a value in between resolves the issue.
  globx = { for (int i = 0; i < 10; i++) i,  100 };  // OK
  globx = { 0, for (int i = 0; i < 10; i++) 100 + i };  // OK
  globx = { for (int i = 0; i < 10; i++) i,  for (int i = 0; i < 10; i++) 100 + i };  // NOT OK
  globx = { for (int i = 0; i < 10; i++) i,  50, for (int i = 0; i < 10; i++) 100 + i };  // OK AGAIN

hello.dart:42:13: Error: Expected ':' after this.
  globx = { for (int i = 0; i < 10; i++) i,  for (int i = 0; i < 10; i++) 100 + i };  // NOT OK
            ^
hello.dart:42:46: Error: Expected ':' after this.
  globx = { for (int i = 0; i < 10; i++) i,  for (int i = 0; i < 10; i++) 100 + i };  // NOT OK
                                             ^

Also, not really a bug, but the new syntax gives us a nice classic dangling else problem :-)
globx = [ if (b1) if (b2) 1 else 2 ];

false false : []
false true  : []
true  false : [2]
true  true  : [1]

This looks like a bug in the inference of whether the literal is a map or a set, as if only top-level elements are counted when trying to see if it's a map or set. The "expected ':' here" message suggests that it is being treated as a set literal.
Since the if branches contain a single value element expression, they should count as a vote for being a set, and the literal should become a set literal.

Thanks for spotting this!  Proposed fix: https://dart-review.googlesource.com/c/sdk/+/98341.


fix race in datachannel handleOpen

Description
The two variables used here are protected by the mutex mu they should only be accessed when the lock is held.
Reference issue
https://github.com/pion/webrtc/issues/2586

Thank you @sukunrt !

@sukunrt I tagged v3.2.21 for this

Oh wow, this is awesome! Thanks for the release @Sean-Der


Add golintui

It would be useful information for those who want to operate golangci-lint from the terminal.

thank you!


Add API Documentation for Resources and Sessions endpoints

Feature
Why is this feature being added?

Our contributors need to be able to research, confirm and build against the API endpoints that the backend offers.
What should your feature do?
Document the following backend API endpoints in our online API documentation.  When doing so, please follow the steps described in our README for how to document our API.
The endpoints to be documented are:

[ ] api/v1/resources_controller#destroy
[ ] api/v1/sessions_controller#create
[ ] api/v1/sessions_controller#sso

@christopher-wolff23 - As there has not been a pull request, or any recent activity on this issue, we are assuming it has become abandoned. We are marking it available for other members to contribute.
Here are our contributing guidelines which discuss the process and timelines for working an issue. You are more than welcome to re-reserve the issue, if it remains marked as "Status: Available"!

@hpjaj Sorry! I had some initial trouble wrapping my head around Rails, and then school started back again. Hopefully I'll find some time to look at it, again. But it's fine that you made it available.

@christopher-wolff23 - No worries!

K... I will check this out on thursday to see if I have any shot of handling this. @hpjaj Let's see how it goes.   Let me know if you run into any issues.

@nagano564 - Heads up, updated this story's acceptance criteria.


Unable to set up sentry sdk debug logger option in Laravel 7

How do you use Sentry?
Sentry SaaS (sentry.io)
SDK version
3.8.0
Steps to reproduce
My enviroment: Laravel 7, PHP 7.4
I am trying to set up the Sentry SDK logger to debug an issue: the performance monitoring is not properly displaying all the API routes on my transactions page.
I am using the Laravel SDK, but the transactions are only showing 4 routes. In my project, there are about 100 routes. I'm not sure where the misconfiguration might have occurred.
My project provides RESTful APIs, so I am only using routes/api.php.
To set up the logger options in Laravel, I followed the Sentry documentation for an option in config/sentry.php named "logger" (https://docs.sentry.io/platforms/php/guides/laravel/configuration/options/?original_referrer=https%3A%2F%2Fdocs.sentry.io%2Fplatforms%2Fphp%2Fconfiguration%2Foptions%2F%3Foriginal_referrer%3Dhttps%3A%2F%2Fgithub.com%2F#logger). However, this resulted in an error with the older version (3.8.x), indicating that the DebugLogger Classes provided by Sentry did not exist.
Before SDK version 4.0.0, this option only accepted strings. After 4.0.0, the logger option now accepts a Psr\Log\LoggerInterface instance (https://github.com/getsentry/sentry-php/blob/master/CHANGELOG.md#features-2).
After attempting to upgrade the SDK to ^4.1.x, I encountered another error, as shown
I then realized it was a PHP version issue, so I created a new class extending LoggerInterface. This led to another error related to serialization, as shown

After having a discussion with sentry support in the discord thread https://discord.com/channels/621778831602221064/1186889992526626866
I tried the approach that official doc provided
https://docs.sentry.io/platforms/php/guides/laravel/configuration/laravel-options/#closures-and-config-caching
and it showed type error.

Expected result
The sentry performance monitoring page should show all the api routes in my project.
Actual result
The sentry performance monitoring page shows only 4 routes.

The logger option is not meant to be used in production and doesn't have any special handling to resolve it from the container or allow it to accept a callable. Maybe it's an idea to when you have the debug logger active not have config caching on? This way you can (temporarily) add the debug logger to your application and see what is going on?
However you have 2 issues here, the first is with the debug logger (which can be solved by using your own implementation of the logger interface for now, we will fix that to work in all PHP versions we support) but the other one is much more interesting.
You mention you are only showing 4 out of about 100 routes, does php artisan route:list also show that many routes (I am not a 100% certain Laravel 7 has that command but it's worth a try)?
In addition, how did you configure the sample rate for transactions? Is tracing_sample_rate set to 1.0? Can you maybe share a but more about how you configured those routes that are not showing up?
Did you end up using version 4.x of the Laravel SDK? I want to see if I can reproduce but knowing which version you are currently using will be very helpful and I would strongly recommend to always be using the most up-to-date Laravel SDK supporting your Laravel/PHP version combo (Laravel 7 and PHP 7.4 should be able to run the latest version no problem).

The logger option is not meant to be used in production and doesn't have any special handling to resolve it from the container or allow it to accept a callable.

I am currently using the logger option in my development environment, which is very similar to my production environment.

Maybe it's an idea to when you have the debug logger active not have config caching on?

Thank you for the suggestion, I will try this approach.

You mention you are only showing 4 out of about 100 routes, does php artisan route:list also show that many routes (I am not a 100% certain Laravel 7 has that command but it's worth a try)?
The original php artisan route:list showed exactly the number that sentry dashboard showed.

The original php artisan route:list command shows exactly the same number of routes as displayed on the Sentry dashboard.
I think you have pinpointed the real issue. We are using an API version control package called "dingo-api" (https://github.com/dingo/api). When using this package, routes only appear when using the php artisan api:routes command.
I am not sure how to deal with this issue, do you have any suggestions?

I have checked out that package a bit but I can't figure out a event or hook to get the custom router they are using. I'm guessing it's possible but they hi-jack the Laravel router and replace it with their own and do not fire any events and their middleware stack also runs before the route is matched... so I'm a bit at a loss, it also seems like the package is pretty inactive (even the fork) so I'm not sure if it's possible to correctly fix it at this point.
However what you can try is setting SENTRY_TRACE_MISSING_ROUTES_ENABLED=true in your .env assuming you are using 4.x of the Laravel SDK which might correctly record the routes but might also result in many duplicate routes because parameters are not considered because of the missing route data (so a /hello/{name} would normally be recorded but now it might be recorded as /hello/world and /hello/winfred etc.). Not a perfect solution but maybe good enough for now?

I tried the approach for missing routes, and it worked perfectly. Thank you for the tips.
Regarding the dingo-api, I am uncertain about how Sentry captures events. If I extend the php artisan route:list command to make my routes appear, would this assist Sentry in capturing the correct routes without the need to set SENTRY_TRACE_MISSING_ROUTES_ENABLED?
Additionally, does setting SENTRY_TRACE_MISSING_ROUTES_ENABLED=true increase performance quotas and application resource usage?

Regarding the dingo-api, I am uncertain about how Sentry captures events. If I extend the php artisan route:list command to make my routes appear, would this assist Sentry in capturing the correct routes without the need to set SENTRY_TRACE_MISSING_ROUTES_ENABLED?

No, that won't help. Sentry listens for the RouteMatched event fired by the Laravel router, dingo-api has a custom setup with their own router and do not fire that event nor set the route on the request ($request->route() always seems to be null) which is how we detect a route was matched and allow a parameterized transaction name (the {name} part of /hello/{name}), now you get the raw path from the URL which groups less nicely.

Additionally, does setting SENTRY_TRACE_MISSING_ROUTES_ENABLED=true increase performance quotas and application resource usage?

It increases performance quoatas of course but it won't have much impact unless you have a lot of calls to non-existent routes in your application since those will also be captured, normally we would only capture a transaction if a route exist for it to prevent search engines looking for URLs or hack script looking around consuming transactions. But the impact should be pretty low, but do keep an eye on it of course since its very specific to you and your application how large the impact is :smile:

Thank you for the assistance. I will investigate the issue further and try to find a solution myself. Your information has been really helpful.

Hello! @stayallive

The logger option is not meant to be used in production

As I understand this logger will log errors in sentry plugins.
For example, I tried to debug why sentry is not logging my error on production. Now I know that it is because of payload size > 1mb.
It's good to have a separate file to have sentry logs there (or even send these logs to sentry).
It's bad practice to have some objects in the config.
What do you think about adding 'logger' config parameter as class name (string) and then create it via DI?

Also trying to fix it here
https://github.com/getsentry/sentry-php/pull/1722

We can certainly look into getting the logger from the container at some point. If you need it today you can decorate the client builder and set the logger directly: https://docs.sentry.io/platforms/php/guides/laravel/usage/#decorating-the-client-builder. Please open up a new issue for this if you want.
The reason these errors cannot be transmitted to Sentry is because you can easily get into a situation where you get an loop of error sending causing errors to be sent causing errors to be sent etc. So that's a no-go unfortunately 😄

where you get an loop

forgot to say that it was joke :)

I've added this to my ServiceProvider
$this->app->extend(ClientBuilder::class, function (ClientBuilder $clientBuilder) {
            $clientBuilder->setLogger(new InternalSentryLogger);
            return $clientBuilder;
        });


Size batches by number of words

This adds support for batching by number of words via the --batch-type option.  For each bucket, a custom batch size (number of sentences) is set such that the average number of non-padding words per batch is (1) as close as possible to the requested size, (2) subject to being evenly divisible by the number of devices.  While the actual number of words per batch will vary (impossible to avoid without truncating sentences), reasonable batch sizes (~4096) and bucket widths (~10) keep the numbers pretty close to the average.

As of the last commit, things should be in shape for a merge.  Anyone want to sign off on this?

I think this looks good, but it would be great to have one of the system checks use the new option and assert on bleu for seq_copy/seq_sort.
Did Tobis suggestion with expand_requested_device_ids() not work?

expand_requested_device_ids() also writes log messages about acquiring GPUs, which we aren't actually doing here.  We could refactor it into two functions and re-use one, though I'm not sure that's worth it to replace one line of code.

yeah thats not worth it. I will approve & merge, but could you add --batch-type word in at least one of the system/integration tests so that we have the test suite run this code path at least once. Thanks!

Sounds good.  I added a test and started everything running.  I'll check in the commit once everything passes.


Upgrade pnpm to v8

pnpm v7 is released, and we should look into what it takes to upgrade

dependent on #1040

@storybook/addon-docs uses v1.x.x of @mdx-js/react and that version does not support React 18 (version 2 does) See also https://github.com/storybookjs/storybook/issues/18383 for some related discussions. I don't think this is of great importance for us since we are not using mdx

@storybook/addon-essentials -> @storybook/addon-actions -> react-inspector does not yet support React 18

┬ @equinor/eds-core-react
│ └─┬ @equinor/eds-utils
│   └─┬ react-popper
│     └── ✕ unmet peer<EMAIL_ADDRESS>|| ^17": found 18.1.0

react-popper v2.30 has fixed this, but the EDS team are holding back the upgrade for React 18 a bit. We don't use any components from EDS that relies on react-popper, so this is not a big deal for us

Forgot to add the one for Reach
No progress on any of the issues yet.

Why isn't this closed? pnpm is using latest version already

Because we are waiting on updates for all the library mentioned in the comments to get rid of peerDeps warnings

No official React 18 support for reach-ui yet

as we are phasing out reach-ui #1378, we can start looking at this again

Ready to be worked on after #1532

According to the migration guide for v8, we need to regenerate the pnpm lockfile as they have upgraded to lockfile version 6, that's missing in the PR still. Should be as simple as making sure your local pnpm version is 8.5.1 similar to the ones pinned in the PR, and then running pnpm setup-project - it'll autoregenerate the lockfiles then - it did for me at least.
Haven't fully tested the web and studio with the new lockfile/pnpm v8 yet though
Also looks like there isn't a Dockerfile in the v3 studio yet, but we'll need that to deploy the satellite studios as well. We can take that in another issue

Have pushed updated lock files, we should make sure everything still works as expected 😬

i have checked that the web and studio still works as expected, all of the regular pnpm commands still works. Other things to have in mind before i merge @fernandolucchesi @padms @SvSven ?

and dockerfile of sanityv3 should also be updated

reviewed sanity v3 docker and works fine! ✅


router.navigation includes invalid hrefs when using nav:true on a dynamic route

If you fail to specify an href on a route using nav: true, the default is to copy the route pattern, which may include dynamic segments. This will result in invalid hrefs being included in navigation links.
Eg, changing this skeleton-navigation route to
{ route: 'flickr/:tag', moduleId: './flickr', nav: true }

will result in Flickr in the skeleton's navigation menu.
I think the router should protect users from such mistakes, and ideally never return a bad href. We could...

Validate the route config and throw an error if  nav: true appears on a dynamic route,
Silently ignore the nav: true on dynamic routes,
Maybe try to run .generate() on the navigation routes using the current or parent context? This is probably too error-prone to use.

I like the idea of throwing an error if there's no href on a dynamic router marked with nav:true. What do you think? Want to work on it. Your work has been fantastic so far :)

I agree, and should be able to take care of this tonight. I think stricter validation with helpful errors is better than potentially surprising behavior. What's the reason for allowing a navigation href to differ from the route path? Shouldn't they always be static, and always be the same?
Thank you for the compliment. I've found the codebase very approachable and well-organized :-)


Bug in the UI buttons

As you can see in dark mode some buttons are white not convert into dark theme
i can fix this problem and enhance the user interface

Pull the latest code and then work on it

can i work on this

Assign this issue to @pallaviii21
I have another work , She can easily solve this problem.


Doesn't expected output when pre-release tags with same datetime

Describe the bug
The following flags are not producing the expected output when there are pre-release tags with same date.

--unreleased
--latest
--current

I think this issue has a low priority, because this issue is an edge case.
This is because it is rare to encounter a situation where the date and time of the tag are the same.
To Reproduce
I've created a test script.
test script
#!/bin/bash

set -e

rm -rf /tmp/cliff/option_test &&
	mkdir -p "$_" &&
	cd "$_"

git init

git config --local commit.gpgsign false
git config --local tag.gpgsign false

date_now="$(date)"

function commit() {
	tag="v$1"
	git commit --allow-empty -m "chore: $tag"
	GIT_COMMITTER_DATE="$date_now" git tag $tag --message $tag
}

commit '1.0.0'
commit '1.1.0-rc.1'
commit '1.1.0-rc.2'
commit '1.1.0'

echo '====================================='
echo 'git log --oneline'
echo '====================================='
git log --oneline

echo '====================================='
echo 'git tag --sort=-taggerdate'
echo '====================================='
git tag --sort=-taggerdate

echo '====================================='
echo 'git-cliff version'
echo '====================================='
git-cliff --version

git-cliff --init
#
function output_changelog() {
	echo '====================================='
	echo "git-cliff $@"
	echo '====================================='
	git-cliff $@
}

output_changelog
output_changelog --unreleased
output_changelog --latest
output_changelog --current

output
Initialized empty Git repository in /tmp/cliff/option_test/.git/
[main (root-commit) f296b1e] chore: v1.0.0
[main 7d62cf8] chore: v1.1.0-rc.1
[main adc2ee1] chore: v1.1.0-rc.2
[main 5224e82] chore: v1.1.0
=====================================
git log --oneline
=====================================
5224e82 (HEAD -> main, tag: v1.1.0) chore: v1.1.0
adc2ee1 (tag: v1.1.0-rc.2) chore: v1.1.0-rc.2
7d62cf8 (tag: v1.1.0-rc.1) chore: v1.1.0-rc.1
f296b1e (tag: v1.0.0) chore: v1.0.0
=====================================
git tag --sort=-taggerdate
=====================================
v1.0.0
v1.1.0
v1.1.0-rc.1
v1.1.0-rc.2
=====================================
git-cliff version
=====================================
git-cliff 1.1.1
 INFO  git_cliff > Saving the configuration file to "cliff.toml"
=====================================
git-cliff
=====================================
# Changelog

All notable changes to this project will be documented in this file.

## [1.1.0] - 2023-01-20

### Miscellaneous Tasks

- V1.1.0

## [1.1.0-rc.2] - 2023-01-20

### Miscellaneous Tasks

- V1.1.0-rc.2

## [1.1.0-rc.1] - 2023-01-20

### Miscellaneous Tasks

- V1.1.0-rc.1

## [1.0.0] - 2023-01-20

### Miscellaneous Tasks

- V1.0.0

<!-- generated by git-cliff -->
=====================================
git-cliff --unreleased
=====================================
# Changelog

All notable changes to this project will be documented in this file.

## [1.1.0] - 2023-01-20

### Miscellaneous Tasks

- V1.1.0

<!-- generated by git-cliff -->
=====================================
git-cliff --latest
=====================================
# Changelog

All notable changes to this project will be documented in this file.

## [1.1.0-rc.2] - 2023-01-20

### Miscellaneous Tasks

- V1.1.0-rc.2

<!-- generated by git-cliff -->
=====================================
git-cliff --current
=====================================
# Changelog

All notable changes to this project will be documented in this file.

## [1.1.0] - 2023-01-20

### Miscellaneous Tasks

- V1.1.0

## [1.1.0-rc.2] - 2023-01-20

### Miscellaneous Tasks

- V1.1.0-rc.2

## [1.1.0-rc.1] - 2023-01-20

### Miscellaneous Tasks

- V1.1.0-rc.1

<!-- generated by git-cliff -->

Unreleased
git-cliff --unreleased
# Changelog

All notable changes to this project will be documented in this file.

## [1.1.0] - 2023-01-20

### Miscellaneous Tasks

- V1.1.0

<!-- generated by git-cliff -->

Latest
git-cliff --latest
# Changelog

All notable changes to this project will be documented in this file.

## [1.1.0-rc.2] - 2023-01-20

### Miscellaneous Tasks

- V1.1.0-rc.2

<!-- generated by git-cliff -->

Current
git-cliff --current
# Changelog

All notable changes to this project will be documented in this file.

## [1.1.0] - 2023-01-20

### Miscellaneous Tasks

- V1.1.0

## [1.1.0-rc.2] - 2023-01-20

### Miscellaneous Tasks

- V1.1.0-rc.2

## [1.1.0-rc.1] - 2023-01-20

### Miscellaneous Tasks

- V1.1.0-rc.1

<!-- generated by git-cliff -->

Expected behavior
Unreleased
git-cliff --unreleased
# Changelog

All notable changes to this project will be documented in this file.

<!-- generated by git-cliff -->

Latest
git-cliff --latest
# Changelog

All notable changes to this project will be documented in this file.

## [1.1.0] - 2023-01-20

### Miscellaneous Tasks

- V1.1.0

<!-- generated by git-cliff -->

Current
git-cliff --current
# Changelog

All notable changes to this project will be documented in this file.

## [1.1.0] - 2023-01-20

### Miscellaneous Tasks

- V1.1.0

<!-- generated by git-cliff -->

System (please complete the following information):

OS Ubuntu 20.04 LTS (WSL2)
Project Version: v1.1.1

Additional context
Thank you.

Thanks for the detailed issue! 🐻 Loved your repro script!
This is indeed an edge case but 4df5656c1239b0252ce9e7571efa06e9d11490ea should fix this.

Hmm, it looks like https://github.com/orhun/git-cliff/commit/4df5656c1239b0252ce9e7571efa06e9d11490ea was a breaking change: https://github.com/orhun/git-cliff/actions/runs/3967220267/jobs/6798926881
I will revert this for now. I think it's better to have precise timestamp comparison rather than unforeseen commit order behavior.

Thank you for your response.

I will revert this for now. I think it's better to have precise timestamp comparison rather than unforeseen commit order behavior.

I agree with your thoughts.
It is your decision whether or not to close this issue.


2.0.8 fails to build

because of guard on empty pkg-config output in 967198e2b9adb38844d296d1f6b0803d25d04006

The latest release 2.0.9 should now fix this.


Ignore sourceforge links

Sourceforge project websites are all down for maintenance - this should make the merge build green again

https://ci.openmicroscopy.org/view/Docs/job/OMERO-DEV-merge-docs/1041/ green again now

build is green today again


Changed ControllerSingleton to support multiple connections

Multiple instances of ExactOnlineClient using different connections are supported through this change.

The ControllerSingleton is renamed to ControllerList and it's no longer a singleton. A few more changes in other files resulted from this.
Added the force_login=1 parameter to the authorization url when the user has to enter his credentials.
Fixed 2 UserAcceptanceTests that had a hardcoded division number.
Minor cleanups.

Looks good


Not able to load .onnx files in detectnet.py

Hey @dusty-nv how do I use a custom model i trained on detection algorithm.
When i give my model .onnx path as input to the network  argument it throws me this error.

The output,

Also it's import jetson_utils in the GitHub repo and jetson.utils in cloned repo there is some discrepancy, cuz it says in the python file in the GitHub reop that if i uncomment that line i can load .onnx files into the Python file as well, but i get an error saying module detectNet not found

Hi @SaTz1483, it looks like you need to set the other command-line parameters for loading custom model, like the following:
detectnet --model=models/fruit/ssd-mobilenet.onnx --labels=models/fruit/labels.txt --input-blob=input_0 --output-cvg=scores --output-bbox=boxes

Also it says it can't find the model file that you specified, so double-check it exists.

@dusty-nv I'm actually trying to train a custom dataset that has a resolution of 4208x3120 and its taking ridiculously long. Is there any way of optimizing this?
Does resolution play a role in training time?

Hey @dusty-nv
Could you help me out with this?
I'm actually trying to train a custom dataset that has a resolution of 4208x3120 and its taking ridiculously long. Is there any way of optimizing this?
Does resolution play a role in training time?