Pretty permalinks not working

I'm trying out this plugin to get pretty permalinks (example.com/about instead of example.com/about.html).
When I run grunt assemble, I expect docs/pages/about.hbs to compile to docs/build/about/index.html, but instead it's compiling to docs/build/about.html. I've followed the example in the docs and my Gruntfile.coffee looks like so:
assemble:
  options:
    flatten: true
    plugins: ['assemble-middleware-permalinks']
    layoutdir: 'docs/layouts'
    assets: 'dist/assets'
    partials: 'docs/partials/*.hbs'
    helpers: 'docs/helpers/*.js'
    data: ['docs/data/*.{json,yml}']
  docs:
    options:
      permalinks:
        preset: 'pretty'
    files: [
      expand: true
      cwd: 'docs/pages'
      src: ['**/*.hbs']
      dest: 'docs/build/'
    ]

The plugin doesn't seem to be doing anything at all. Is there something I'm missing here?

Try using assemble-contrib-permalinks for assemble 0.4.x

Ah, good catch. OK, now my package.json dependencies look like so:
"assemble": "^0.4.42",
"assemble-contrib-permalinks": "^0.3.6",
"grunt": "^0.4.5",

I changed my Grunfile to:
assemble:
  options:
    flatten: true
    plugins: ['assemble-contrib-permalinks']
    ...

Now when I run grunt:assemble, I get the following error:
Warning: Arguments to path.resolve must be strings Use --force to continue.

Note: I'm getting this same error when I clone the assemble-middleware-permalinks repo, install npm dependencies, and run grunt:assemble.

Check your node_modules and make sure assemble-contrib-permalinks is version 0.3.6. I have that setup on:
Mac OSX 10.9.5
node 0.10.29
npm 1.4.26

Maybe something else is conflicting.

Yep, the package.json file for assemble-contrib-permalinks is telling the the version number is 0.3.6. I'm set up with:
Mac OSX 10.9.5
node 0.10.36
npm 1.4.28

The only other npm modules I have in the project are grunt, assemble, and load-grunt-tasks, so I don't think there should be any conflicts.

I updated and it's working fine. How are you using load-grunt-tasks? Can you post the entire gruntfile?

I'm using load-grunt-tasks so I don't have to manually include new plugins in the gruntfile.
module.exports = (grunt) ->
  grunt.initConfig
    pkg: grunt.file.readJSON('package.json')

    assemble:
      options:
        flatten: true
        plugins: ['assemble-contrib-permalinks']
        layoutdir: 'docs/layouts'
        assets: 'dist/assets'
        partials: 'docs/partials/*.hbs'
        helpers: 'docs/helpers/*.js'
        data: ['docs/data/*.{json,yml}']
      site:
        options:
          permalinks:
            preset: 'pretty'
        files: [
          expand: true
          cwd: 'docs/pages'
          src: ['**/*.hbs']
          dest: 'docs/build/'
        ]

  # Load plugins
  require('load-grunt-tasks') grunt,
    pattern: ['grunt-*', 'assemble']

  grunt.registerTask 'default', ['assemble']

Keep in mind that I'm getting the same error when running grunt assemble on the examples included in the repo, so I don't think it's specific to this project.

try this:
# Load plugins
  require('load-grunt-tasks') grunt,
    pattern: ['grunt-*', 'assemble*']

  grunt.registerTask 'default', ['assemble']

basically, wildcard the assemble string to pick up the plugin.

Ah, that did the trick. Thanks! I'm not sure why I was having the same issue on the assemble-middleware-permalinks repo, but fixing it here works for my project.


Prepare comments in literate programming style in script input/2report.py

Prepare comments in literate programming style in script input/2report.py

Added via https://github.com/RedHatInsights/insights-results-aggregator-utils/commit/6add93961a478e46fb4ef8801bf8187115ba4c36#diff-a43c1b0aa53a0c908810c06ab1ff3967


Will this be integrated in radix-vue / shadcn-vue?

This is a really cool component, any chance it's going to be directly added to radix-vue and/or shadcn-vue?

It will be added to shadcn-vue 😁


Add a comprehensive test corpus for the parser

I think we should do the same thing that we do in scalameta/scalameta - hand-pick a huge corpus of Scala files and write a test that ensures that our scanner and parser work for them in a reasonable fashion.

One cool thing that I liked about our tests is the fact that they verify that all characters in all sources are covered by tokens, with every character covered exactly by one token.

checkparse introduced in https://github.com/twitter/rsc/pull/85 is pretty thorough, so that's the half of the ticket. The other half will be figured out and ticketed once we tackle https://github.com/twitter/rsc/issues/88.


Formalise builtins registry

Database dumper will need to be able to look up the names of builtins, so create a Registry class providing bidirectional mapping and use it for .builtins_ (which loses the underscore, because it will need to be public).

Hold off on reviewing this for a moment; I have another commit coming.


Package name appears twice

Package name appears twice in .meteor/packages file, after crud generator is run.
Had to manually delete the repetition, in order for the server to function.
I am on Ubuntu 14 LTS. similiar issues in docker images too .
Meteor release@1.1.0.,2

Unable to add new users to role group,   Submit button doesn't do anything...
I am on Ubuntu 14 LTS. similiar issues in docker images too .
Meteor release@1.1.0.,2


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-22-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1141

Questions ?
Please refer to the Backport tool documentation


Correct numbering of two substeps in fig. 2

Where to find the issue
Fig. 2 ("Interaction flow for verification process"), step 3
Describe the issue
The numbering of the substeps 2a (give Tele-TAN to patient) and 2b (get Tele-TAN from verification server) should be the other way round: First get the Tele-TAN, then give it to the patient.
Suggested change
Replace "(2a)" by "(2b)" and vice versa.

The user is referencing the solution architecture document. @tklingbeil, please have a look, thanks!

You are absolutely right. I'll also add the (visual) information that a teleTAN is only created if it is actually needed.


Fixed package.json and tsconfig.json conflict

In package.json, 'main' is set as 'out/src/extension' whereas in tsconfig.json, 'outDir' is set as 'out' which causes runtime errors.
package.json 'main' parameter is changed to 'out/extension' to prevent those errors.

Thanks @harish095 :+1:


firecamp-autoscalegroup.template does not use AMI ID specified in the parent template (firecamp-existingvpc.template)

Please, fix

Thanks! The AMI ID mapping should be in firecamp-autoscalegroup.template. So we don't need to define the mapping in multiple places, firecamp-master.template and firecamp-existingvpc.template.
The AMI ID in firecamp-existingvpc.template is not used. Will remove it. Saw you created a pull request. If you want to remove it in your patch, it would be great.

The autoscalegroup template is shared by both existingvpc and master templates. The EC2 instance ImageId is not passed from the existingvpc template to the autoscalegroup template. Instead, the autoscalegroup template will select the ImageId based on the region and "NodeAMIOS" (default Amazon Linux AMI). The existingvpc template will call the autoscalgroup template to actually create the EC2 instances.
The other option is the existingvpc template selects the ImageId and passes to the autoscalegroup template. But the master template has to select the ImageId and passes to the autoscalegroup template as well. The AMI region map will be duplicated in the existingvpc and mater templates.

Got it. At first I decided you gonna delete existingvpc template. Thanks!

The fix from @jazzl0ver was merged.


log error when requiring an unavailable language

Solves #1899

OMG, thanks for running with this but I imagined a little more general solution.  Hmmmm, though it seems that right now Arduino is the only language that depends on another (though that may not be true for 3rd party languages).  What I had imagined:

Add requireLanguage API in addition to getLanguage.
While getLanguage might or might not return a language
requireLanguage always would, or would console.log that error (but generic to whichever langue was requested)...
So we don't need to catch any errors... if the language requested isn't found, that's a hard error and should be logged.

Thoughts?

https://github.com/highlightjs/highlight.js/pull/2236/
You might want to piggy back on this.

@yyyc514 So what do you suggest?

Same idea, just now you can reuse the error message.

Closing this for inactivity.  I'll circle back around to this eventually myself or if you want to try your hand at implementing a generic solution (as suggested above) you can always simply open another PR (or we can reopen this one).  Thanks.


Evaluate Global Resources Cache Within Provider Instances

The current implementation of the resources cache, managed by the Provider instance, utilizes a global cache.
This design ensures that the cache is shared among all Provider instances within the same dApp. This approach was chosen due to the possibility that multiple providers may be instantiated from different parts of the dApp, and transactions can be submitted from these various instances using resources owned by the same address.
While the global cache design has its advantages, it also introduces some unintentional issues:

Each Provider instance can set its cache Time-To-Live (TTL), leading to confusion since the actual cache is shared among all instances.
Developers might expect each Provider instance to manage its own cache independently, leading to potential misunderstandings.

Given the potential unintentional problems, this issue should serve as a reminder to continuously evaluate if another approach is more suitable.

Should we make the setter for the TTL a static method on the provider class?

@arboleya yes, if we're going to make the cache static then we should make the TTL setter static as well.
public class Provider {
  static cache?: ResourceCache = new ResourceCache(20000);

  static updateCacheTtl(ttl: number) {
    if (ttl === -1) { this.cache = undefined; return; }
    const activeData = this.cache?.getActiveData();
    // activeData as the second argument is used to invalidate the data based on the new ttl
    this.cache = new ResourceCache(ttl, activeData);
  }
}

I'm not sure about the name of updateCacheTtl but that's the idea.

@Torres-ssf Regarding the cache being public, I know that you had some reasoning behind it but I can't remember it... What was it?

@Torres-ssf Comment from Github.

@sergio.torres Comment from Linear.

@Torres-ssf @arboleya These are github handles.

@sergio.torres @anderson.arboleya these are handles from Linear.

Mentioning from Linear @torres-ssf @arboleya

Mentioning from GH @Torres-ssf @arboleya

Mentioning from GH @Torres-ssf @arboleya

Mentioning from Linear @torres-ssf @arboleya

Closing this as not planned based on investigations
See more here


Layout component issue

I used Layout component to show something. Sometimes I got an error like this.

I solved it in v0.3.3, can you try it and see if there is still this problem?

I solved it in v0.3.3, can you try it and see if there is still this problem?

I tested it and found no problems for now.


wip: qualtrics embedded feedback widget POC

Summary | Résumé
POC for qualtrics embedded feedback widget
Currently only works locally as changes will be needed to add the scripts to the CSP

Language settings issue [RESOLVED]
Language settings issue
When setting up the widget, qualtrics provides us with the option to choose. However, choosing the global variable option doesn't seem to work.

Advanced settings, global variable or browser language option

Screenshots of attempts to test the language options and settings
Although the global variable doesn't seem to work, qualtrics does change the language based on the user's brower settings. It detects what language the user has their browser set to.
No major differences in FR and FR-CA: I changed my browser language in Chrome to use either "French" or "French (Canada)" and it shows me the appropriate language. In this case, I setup qualtrics to only have one additional french translation - "French (Canada)" or "FR-CA". I tested it by adding another french translation, one for "French" or "FR", and it doesn't seem to matter. Even if I have my browser set to just "French" (not Canada) it still picks up "French (Canada)" from the qualtrics translation.

Expected: English domain with my browser set to english

Unexpected: English domain with my browser set to french (shows french)

Expected: French domain with my browser set to french

Testing the widget in two languages

English
https://pr-365.djtlis5vpn8jd.amplifyapp.com/
https://pr-365.djtlis5vpn8jd.amplifyapp.com/en/components/details/
Homepage

Button component

French
https://pr-365.d35vdwuoev573o.amplifyapp.com/
https://pr-365.d35vdwuoev573o.amplifyapp.com/fr/composants/details/
Homepage

Button component

ISSUE: Widget is blocked by ad blockers such as uBlock

I have to turn my browser extension off or view it using incognito, otherwise it is blocked from loading.

Closing this PR as it is merely a POC


Validation without messages

Is it possible to have validations done without a message being included? In this case the messages array would not contain a value for the invalid property.

You should be able to do
validator('length', { min: 1, message: '' });

I think this returns the default message, but I will have to confirm.

Any luck?

Just tried this myself, you would have to pass a string with a space
validator('length', { min: 1, message: ' ' });


[Platform][Broad Issue Category if applicable (eg Accessibility)] [Bug Title]

Platform
What platform is your issue or question related to? (Delete other platforms).

.NET HTML
.NET WPF
Android
iOS
JavaScript
UWP

Author or host
Are you an author (like sending something to Outlook), or a host that is rendering your own cards? If host, please specify the corresponding host (app) name.
If you're an author, who are you sending cards to?
Version of SDK
What version are you using? Ex: NuGet 1.0.2, or latest master, etc...
Details

Explain your issue. If you just have a question, please post on StackOverflow instead.


ReferenceError: use before declaration in Edge

The ES2015 distribution of aurelia-bootstrapper triggers an error in Edge: "ReferenceError: use before declaration". And then the application doesn't start.
I did test before and never noticed that, so I wonder if it is an Edge regression in a recent update.
I have Edge 14.14393, I would be interested in other people testing this.
The offending code is line 126:
.then(({ Aurelia }) => startResolve(() => new Aurelia(loader)));

And Aurelia is the variable that Edge complains about.
The code above looks fine to me (given that then is called with an object that contains an Aurelia property).
It runs fine in Firefox and according to Kangax tables it should be supported in Edge as well.
Just changing the code as follows work.
.then(({ Aurelia }) => {
  return startResolve(() => new Aurelia(loader));
});

So I'd say this is more of an Edge bug, but since it impacts us it's good to know.

I have a minimal repro, it requires several conditions to trigger the bug, notably nested lambdas.
This breaks Edge 14.4393:
function g(cb) { return g() }
let f = ({ x }) => g(() => x);
f({ x: 42 }); // should return 42 but throws "use before declaration".

Found a relevant Chakra bug: Microsoft/ChakraCore#2606.
It was opened 5 days ago, I guess it is a recent update. :(

We don't need the lambda, we can use function notation if it's going to help, since we only use the scope anyway (no this calls). I'd say we can re-release with a workaround.
Good catch, by the way!

The bug is not hard to work around as it's very sensible to syntax. Even just adding braces (block) make it vanish.
If we publish a fix the hardest part is making sure minifiers don't simplify the syntax back to broken. For instance, if we add braces I would expect a minifier to remove them...
It was not a hard catch as unfortunately now Aurelia ES6 does not run at all in Edge. 😦

@EisenbergEffect do you want to publish a fix? I can PR one if you want to.

Oh, definitely. If you send a PR I'll get it out today.

@EisenbergEffect The fix is in the linked PR, it works for me.

Merged.

Release coming in a few minutes.


test: disabling flaky test

Part of https://github.com/envoyproxy/envoy/issues/34639

I have prepared a possible fix. But havn't created the PR because the dragon boat day. Let's land this first.


Files are unnecessarily opened in multiplex by vscode.window.showTextDocument()

VSCode Version: any
OS Version: any

Steps to Reproduce:

User opens a.txt on ViewColumn.One.
User activates ViewColumn.Two.
Extension calls vscode.window.showTextDocument("a.txt", undefined);.

Result:
a.txt is opened on ViewColumn.Two too.
Desired behavior:
Activate ViewColumn.One.
Note:
Extension can knows only vscode.window.visibleTextEditors.map(i => i.viewColumn) as ViewColumn.
Extension can not knows ViewColumn of TextDocument that is inactively opened in TextEditer.

I think that the behavior of default does not have to be changed.
I want a new item of ViewColumn as like ViewColumn.Active and ViewColumn.Beside.

Do you want Beside for left instead of right?

No.
I made this extension and provided users with access to unsaved files.
I am thinking about a scenario when users process unsaved files. User uses many View.Columns and opens many files. User accesses each unsaved files, saves the file, or discards it without saving it.
Extension displays an unsaved file with vscode.window.showTextDocument(), it is unintentionally duplicated on the View.Column different the original View.Column. If user tries to close the unsaved file, the file can not be closed. Because it is just a duplicate in another View.Column.

/duplicate of #15178

Oh, sorry. >　duplicate
I am waiting for this problem to be solved.


"Vama", "Molid", "Prisaca Dornei", "Strâmtura" villages are listed in the drop-down menu.

Description:
The villages are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Preconditions:
The website (https://peviitor-ro.github.io/ui.orase/) is up and runing. After every step delete the text you typed from the search bar.

Step 1
Write in the search bar "Vama".

Expected results
The location is listed in the drop-down menu as "Sat Vama SUCEAVA (Vama)".

Step 2
Write in the search bar "Molid".

Expected results
The location is listed in the drop-down menu as "Sat Molid SUCEAVA (Vama)".

Step 3
Write in the search bar "Prisaca Dornei".

Expected results
The location is listed in the drop-down menu as "Sat Prisaca Dornei SUCEAVA (Vama)".

Step 4
Write in the search bar "Strâmtura".

Expected results
The location is listed in the drop-down menu as "Sat Strâmtura SUCEAVA (Vama)".


Multiple errors in export after edit (model previously working) - Removing edits, didn't work

Current Behavior
When exporting, a previously working project fails to export. No matter if I try to export only the LOD I edited, another one I did not edit, or all of them. The error is consistent among all tries. This is the first time after a few weeks not exporting the model, which previously was exported correctly
Error: Python: Traceback (most recent call last):
  File "C:\Users\Chris Da Ros\AppData\Roaming\Blender Foundation\Blender\3.1\scripts\addons\io_scene_gltf2_msfs\io\msfs_multi_export.py", line 171, in execute
    MSFS_OT_MultiExportGLTF2.export(
  File "C:\Users\Chris Da Ros\AppData\Roaming\Blender Foundation\Blender\3.1\scripts\addons\io_scene_gltf2_msfs\io\msfs_multi_export.py", line 45, in export
    bpy.ops.export_scene.gltf(
  File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\modules\bpy\ops.py", line 132, in __call__
    ret = _op_call(self.idname_py(), None, kw)
RuntimeError: Error: Python: Traceback (most recent call last):
  File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_gltf2\__init__.py", line 651, in execute
    return gltf2_blender_export.save(context, export_settings)
  File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_export.py", line 46, in save
    json, buffer = __export(export_settings)
  File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_export.py", line 71, in __export
    json = __fix_json(exporter.glTF.to_dict())
  File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_gltf2\io\com\gltf2_io.py", line 1203, in to_dict
    result["materials"] = from_union([lambda x: from_list(lambda x: to_class(Material, x), x), from_none],
  File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\addons\io_scene_gltf2\io\com\gltf2_io.py", line 56, in from_union
    assert False
AssertionError

location: C:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\modules\bpy\ops.py:132

location: <unknown location>:-1

Expected Behavior
Should be exporting correctly, AT LEAST LOD03 when trying to export that alone, which has not been edited
Steps To Reproduce
Load .blend file
try to export
Environment
- OS: Windows 11
- Blender: 3.1.2
- glTF-Blender-IO-MSFS: 1.1.6

Anything else?
Casetta.zip

Update 1 - been spending all night working on it and made a few tests.

removed all materials and references, all images and tried to export. Same error

tried exporting all LODs one by one hoping to find a faulty one. No luck. All of them are giving errors.

copied and pasted the project in a new .Blend file. Same error.

tried removing all items used from my Assets Library (appended). Still error.

Tried all the above at once. No materials, no images, no LOD00, 01 and 02, keeping only LOD03. Same error occurs

Hi @Losco-Nosciuto ,
FYI, the textures are not packed in your blender file
Did you try with blender 3.2 ? I did it and the export is OK
Is this bellow installed and activated in your blender settings :

Hi @Losco-Nosciuto , FYI, the textures are not packed in your blender file Did you try with blender 3.2 ? I did it and the export is OK Is this bellow installed and activated in your blender settings :

Hi Boris! No I haven't tried with Blender 3.2 as for now the most stable and reliable version working with the explorer seems to be 3.1.2.
Texture aren't packed due to size. 150MB don't fit in here, also yes. The gltf plugin included with blender is installed and active. I tried removing everything from the .blend file and add a cube only, and it exports, just won't export with something which is in here and that seems to affect all the rest for some weird reason

Here's the thing, which has been already reported.
Exporting with 3.2 fixes the exporting error but prevent the model from being compiled into the sim due to the KHR_Punctual_Lights glTF extension. Any plausible workaround in this inside 1.1.6 with Blender 3.2?

Hello,
I just pushed the fix for the "KHR_Lights_punctual" problem here:
https://github.com/AsoboStudio/glTF-Blender-IO-MSFS/pull/194
Thank your for your reports !

In the future we recommend to use the Blender 3.3 LTS versions to avoid problems with the blender exporter.

Traceback (most recent call last):
File "C:\Users\Chris Da Ros\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\io_scene_gltf2_msfs\io\msfs_multi_export.py", line 171, in execute
MSFS_OT_MultiExportGLTF2.export(
File "C:\Users\Chris Da Ros\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\io_scene_gltf2_msfs\io\msfs_multi_export.py", line 45, in export
bpy.ops.export_scene.gltf(
File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\scripts\modules\bpy\ops.py", line 113, in call
ret = _op_call(self.idname_py(), None, kw)
TypeError: Converting py args to operator properties: : keyword "export_displacement" unrecognized
Error: Python: Traceback (most recent call last):
File "C:\Users\Chris Da Ros\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\io_scene_gltf2_msfs\io\msfs_multi_export.py", line 171, in execute
MSFS_OT_MultiExportGLTF2.export(
File "C:\Users\Chris Da Ros\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\io_scene_gltf2_msfs\io\msfs_multi_export.py", line 45, in export
bpy.ops.export_scene.gltf(
File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\scripts\modules\bpy\ops.py", line 113, in call
ret = _op_call(self.idname_py(), None, kw)
TypeError: Converting py args to operator properties: : keyword "export_displacement" unrecognized
Now this ;) @y-khodja

My bad, didn't update the plugin properly. Now I get this.
still, 3.3 LTS
Error: Python: Traceback (most recent call last):   File "C:\Users\Chris Da Ros\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\io_scene_gltf2_msfs\io\msfs_multi_export.py", line 207, in execute     MSFS_OT_MultiExportGLTF2.export(   File "C:\Users\Chris Da Ros\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\io_scene_gltf2_msfs\io\msfs_multi_export.py", line 82, in export     bpy.ops.export_scene.gltf(   File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\scripts\modules\bpy\ops.py", line 113, in __call__     ret = _op_call(self.idname_py(), None, kw) RuntimeError: Error: Python: Traceback (most recent call last):   File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\scripts\addons\io_scene_gltf2\__init__.py", line 648, in execute     return gltf2_blender_export.save(context, export_settings)   File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_export.py", line 35, in save     json, buffer = __export(export_settings)   File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_export.py", line 60, in __export     json = __fix_json(exporter.glTF.to_dict())   File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\scripts\addons\io_scene_gltf2\io\com\gltf2_io.py", line 1192, in to_dict     result["materials"] = from_union([lambda x: from_list(lambda x: to_class(Material, x), x), from_none],   File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\scripts\addons\io_scene_gltf2\io\com\gltf2_io.py", line 45, in from_union     assert False AssertionError Location: C:\Program Files\Blender Foundation\Blender 3.3\3.3\scripts\modules\bpy\ops.py:113

Python: Traceback (most recent call last):
  File "C:\Users\Chris Da Ros\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\io_scene_gltf2_msfs\io\msfs_multi_export.py", line 207, in execute
    MSFS_OT_MultiExportGLTF2.export(
  File "C:\Users\Chris Da Ros\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\io_scene_gltf2_msfs\io\msfs_multi_export.py", line 82, in export
    bpy.ops.export_scene.gltf(
  File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\scripts\modules\bpy\ops.py", line 113, in __call__
    ret = _op_call(self.idname_py(), None, kw)
RuntimeError: Error: Python: Traceback (most recent call last):
  File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\scripts\addons\io_scene_gltf2\__init__.py", line 648, in execute
    return gltf2_blender_export.save(context, export_settings)
  File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_export.py", line 35, in save
    json, buffer = __export(export_settings)
  File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\scripts\addons\io_scene_gltf2\blender\exp\gltf2_blender_export.py", line 60, in __export
    json = __fix_json(exporter.glTF.to_dict())
  File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\scripts\addons\io_scene_gltf2\io\com\gltf2_io.py", line 1192, in to_dict
    result["materials"] = from_union([lambda x: from_list(lambda x: to_class(Material, x), x), from_none],
  File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\scripts\addons\io_scene_gltf2\io\com\gltf2_io.py", line 45, in from_union
    assert False
AssertionError
Location: C:\Program Files\Blender Foundation\Blender 3.3\3.3\scripts\modules\bpy\ops.py:113

@y-khodja
Tried again from "scratch"
re-exported the original model to a new blender file (Original model without LODs is inside a global blender file, then I create single blender files per model to export. I remade the exporting blender file for this cabin.)
re-exported the textures from Adobe Painter
Re-Created materials from scratch
Tried to export with the issue above. Hope a solution is incoming soon.

I've downloaded your blend file and can export the LODs using the multi export - I have to change the folder names, but that should not be the issue.
Are you downloading the release 1.1.6 - or are you downloading the "main" branch.  Please use the "main" branch as it has all the recent updates, including functionality with Blender 3.3
next try deleting the
C:\Users\Chris Da Ros\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\io_scene_gltf2_msfs
folder.  Do you know how to install via the install menu in the edit preferences menu using a zip file?
with that you must create a zip of the program in the addons/io_scene_glts2_msfs folder.

I've downloaded your blend file and can export the LODs using the multi export - I have to change the folder names, but that should not be the issue.
Are you downloading the release 1.1.6 - or are you downloading the "main" branch. Please use the "main" branch as it has all the recent updates, including functionality with Blender 3.3
next try deleting the
C:\Users\Chris Da Ros\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\io_scene_gltf2_msfs
folder. Do you know how to install via the install menu in the edit preferences menu using a zip file?
with that you must create a zip of the program in the addons/io_scene_glts2_msfs folder.

What you mean with change the folder names?
Apart from that yeah, I totally removed the old exporter and installed the new one from the main branch when I saw patches have been made without an actual release.
Those are the errors I'm getting no matter of the process. Unfortunately I'm not into python so can't help in reading what the error is about but I've been doing exactly as you suggested. And that's the error I've incurred into. Could this be because of appended assets from my personal assets library? If ever tho even removing those doesn't change the outcome.
I'm really finding an hard time understanding what's going on. That error appears both on 3.1.2 and 3.3 LTS with the main branch addon installed manually

I'm saying delete the version you have in the
C:\Users\Chris Da Ros\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\io_scene_gltf2_msfs
folder.
Then install a zip file of the downloaded "main" branch on git - but zip up the
glTF-Blender-IO-MSFS\addons\io_scene_gltf2_msfs
folder as shown in the picture above.  The release version 1.1.6 does not have the fixes you may need.
I also downloaded your blend file and it works on my system.. I can only conclude there is something wrong in your setup causing this error.
Please tell us step by step what you did so we can try to reproduce this error.

Addon is installed properly as I said above.
I installed 3.3LTS, downloaded the main branch from here, extracted the io_scene_gltf2_msfs to my 3.3 addon folder in AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons, then enabled it in Blender via Preferences / Add-Ons
What's weird is that, the error is consistent along 3.1.2 across to 3.3LTS.
So, might be something inside my blend file? That's why I asked if appended assets from the Asset Library work correctly or those might be the cause. Maybe messing something in the blend file which can't be still fixed after removing them?
Now gonna try to delete and clean Install Blender and see if that works. Gonna send a Loom video with the AddOn Installation process and exporter behviour if this doesn't fix it

So, seems like cleaning all Blender Files and installing 3.3 LTS from scratch fixed the issue.
Still can't figure out what has been going on, probably there are a few Blender files shared across versions.
3.3 Was freshly installed already at first try, but didn't help.
had to manually clean up registry keys, folders and all the user data in order to have it working back again!
Thanks for your help @ronh991 @y-khodja !


[Feature Request] Library list view from J2K

Please add a library view where categories are not in tabs, but in one long list, and each category can be minimized or expanded.
Why/User Benefit/User Problem
i like the j2k library list view

Not happening, waaaay to much work to maintain both


How do I turn off topic auto-creation?

If topic 'foo' does not exist in current Kafka topic list and I use  client.topics['foo'].get_sync_producer().produce('bar')  to push a message, it will automatically create a topic called 'foo' in Kafka, how do I turn this feature off? Can it simply raise an error or give me a return value?
Now I have to always check if the topic exists in kafka topic list before pushing, which causes extra CPU load.

Currently pykafka has no config option to disable this in the client. It wouldn't be hard to add.
But - if that works for you - you can disable it in the broker config through the auto.create.topics.enable option: http://kafka.apache.org/documentation.html#brokerconfigs - if you set this false, pykafka will still attempt to create the topic, but should then return an error.


proactive drops ("streaming mode") varies from run to run

Problem
Dropped blocks varies from run to run. The same inputs should produce exactly the same outputs.
To Reproduce
Run compare-current-and-expected/update.sh then compare-current-and-expected/compare.sh.
The differences often look like:
$ ./tools/compare-current-and-expected/update.sh

...

$ ./tools/compare-current-and-expected/compare.sh

...

Difference Preview of stderr:
+ diff --text -y --width=140 --suppress-common-lines ./tools/compare-current-and-expected/current.stderr ./tools/compare-current-and-expected/expected.stderr
        lines high    : 17                                           |        lines high    : 15
        streaming: BlockReader::drop_block()    : Ok 16, Err  5      |        streaming: BlockReader::drop_block()    : Ok 18, Err  3
        streaming: LineReader::drop_line()      : Ok 64, Err  0      |        streaming: LineReader::drop_line()      : Ok 66, Err  0
        streaming: SyslineReader::drop_sysline(): Ok 63, Err  5      |        streaming: SyslineReader::drop_sysline(): Ok 65, Err  3
        blocks high   : 14                                           |        blocks high   : 15
        lines high    : 12                                           |        lines high    : 13
        streaming: BlockReader::drop_block()    : Ok 5, Err 2        |        streaming: BlockReader::drop_block()    : Ok 4, Err 2
        streaming: LineReader::drop_line()      : Ok 3, Err 0        |        streaming: LineReader::drop_line()      : Ok 2, Err 0
        streaming: SyslineReader::drop_sysline(): Ok 3, Err 4        |        streaming: SyslineReader::drop_sysline(): Ok 2, Err 5
        streaming: BlockReader::drop_block()    : Ok  0, Err  1      |        streaming: BlockReader::drop_block()    : Ok 1, Err 2
        streaming: LineReader::drop_line()      : Ok  2, Err  3      |        streaming: LineReader::drop_line()      : Ok 4, Err 3
        streaming: SyslineReader::drop_sysline(): Ok  5, Err 10      |        streaming: SyslineReader::drop_sysline(): Ok 7, Err 8
        streaming: BlockReader::drop_block()    : Ok 1, Err 2        |        streaming: BlockReader::drop_block()    : Ok  0, Err  1
        streaming: LineReader::drop_line()      : Ok 4, Err 3        |        streaming: LineReader::drop_line()      : Ok  2, Err  3
        streaming: SyslineReader::drop_sysline(): Ok 7, Err 8        |        streaming: SyslineReader::drop_sysline(): Ok  5, Err 10
        streaming: BlockReader::drop_block()    : Ok  6, Err  0      |        streaming: BlockReader::drop_block()    : Ok  5, Err  1
        streaming: LineReader::drop_line()      : Ok 13, Err  0      |        streaming: LineReader::drop_line()      : Ok 11, Err  0
        streaming: SyslineReader::drop_sysline(): Ok  8, Err  0      |        streaming: SyslineReader::drop_sysline(): Ok  7, Err  1
        blocks high   : 12                                           |        blocks high   : 11
        lines high    : 14                                           |        lines high    : 13
        streaming: BlockReader::drop_block()    : Ok 3, Err 2        |        streaming: BlockReader::drop_block()    : Ok 4, Err 2
        streaming: LineReader::drop_line()      : Ok 5, Err 0        |        streaming: LineReader::drop_line()      : Ok 6, Err 0
        streaming: SyslineReader::drop_sysline(): Ok 5, Err 8        |        streaming: SyslineReader::drop_sysline(): Ok 6, Err 7
        streaming: BlockReader::drop_block()    : Ok  97, Err  39            |        streaming: BlockReader::drop_block()    : Ok  98, Err  38
        streaming: LineReader::drop_line()      : Ok 425, Err   0            |        streaming: LineReader::drop_line()      : Ok 426, Err   0
        streaming: SyslineReader::drop_sysline(): Ok 175, Err  43            |        streaming: SyslineReader::drop_sysline(): Ok 176, Err  42
        streaming: BlockReader::drop_block()    : Ok  5, Err  3      |        streaming: BlockReader::drop_block()    : Ok  5, Err  4
        streaming: LineReader::drop_line()      : Ok 21, Err  4      |        streaming: LineReader::drop_line()      : Ok 22, Err  4
        streaming: SyslineReader::drop_sysline(): Ok 24, Err  6      |        streaming: SyslineReader::drop_sysline(): Ok 25, Err  5
        streaming: BlockReader::drop_block()    : Ok  6, Err  1      |        streaming: BlockReader::drop_block()    : Ok 5, Err 2
        streaming: LineReader::drop_line()      : Ok 10, Err  0      |        streaming: LineReader::drop_line()      : Ok 9, Err 0
        streaming: SyslineReader::drop_sysline(): Ok 10, Err  1      |        streaming: SyslineReader::drop_sysline(): Ok 9, Err 2
        streaming: LineReader::drop_line()      : Ok 11, Err  0      |        streaming: LineReader::drop_line()      : Ok 10, Err  0
        streaming: SyslineReader::drop_sysline(): Ok 11, Err  0      |        streaming: SyslineReader::drop_sysline(): Ok 10, Err  1

...

    Different stderr ./tools/compare-current-and-expected/./logs/Debian11/alternatives.log.stderr
        lines high    : 11                                           |        lines high    : 12
        streaming: BlockReader::drop_block()    : Ok 6, Err 1        |        streaming: BlockReader::drop_block()    : Ok 5, Err 2
        streaming: LineReader::drop_line()      : Ok 4, Err 0        |        streaming: LineReader::drop_line()      : Ok 3, Err 0
        streaming: SyslineReader::drop_sysline(): Ok 4, Err 3        |        streaming: SyslineReader::drop_sysline(): Ok 3, Err 4

    Different stderr ./tools/compare-current-and-expected/./logs/Debian11/kern.log.stderr
        streaming: BlockReader::drop_block()    : Ok 0, Err 1        |        streaming: BlockReader::drop_block()    : Ok  0, Err  1
        streaming: LineReader::drop_line()      : Ok 4, Err 3        |        streaming: LineReader::drop_line()      : Ok  2, Err  3
        streaming: SyslineReader::drop_sysline(): Ok 7, Err 8        |        streaming: SyslineReader::drop_sysline(): Ok  5, Err 10

    Different stderr ./tools/compare-current-and-expected/./logs/Debian11/messages.stderr
        streaming: BlockReader::drop_block()    : Ok 0, Err 1        |        streaming: BlockReader::drop_block()    : Ok  0, Err  1
        streaming: LineReader::drop_line()      : Ok 3, Err 3        |        streaming: LineReader::drop_line()      : Ok  2, Err  3
        streaming: SyslineReader::drop_sysline(): Ok 6, Err 9        |        streaming: SyslineReader::drop_sysline(): Ok  5, Err 10

    Different stderr ./tools/compare-current-and-expected/./logs/Debian11/user.log.stderr
        streaming: BlockReader::drop_block()    : Ok  1, Err  4      |        streaming: BlockReader::drop_block()    : Ok  1, Err  3
        streaming: LineReader::drop_line()      : Ok  7, Err  4      |        streaming: LineReader::drop_line()      : Ok  6, Err  4
        streaming: SyslineReader::drop_sysline(): Ok 11, Err  7      |        streaming: SyslineReader::drop_sysline(): Ok 10, Err  8

...

Environment:
Tested to occur back to 0.6.60. Did this by rebuilding old builds and then running compare-current-and-expected/update.sh then compare-current-and-expected/compare.sh.
for ver in 0.6.68 0.6.67 0.6.66 0.6.65 0.6.64 0.6.63 0.6.62 0.6.61 0.6.60; do
    cargo clean
    git checkout $ver
    cargo build --release
    cp -av ./target/release/s4 "./s4_$ver"
    git checkout HEAD
    PROGRAM="./s4_$ver" compare-current-and-expected/update.sh
    PROGRAM="./s4_$ver" compare-current-and-expected/compare.sh || true
    echo ver is $ver
done

Other
I suspect this has been occurring since drop blocks was implemented.
Also, why weren't these differences caught by test_SummaryBlockReader or test_SummaryLineReader or test_syslinereadersummary

tl;dr not a bug. It's due to multi-threaded checks of owners of the shared data structures
This occurs because there are two threads that have access to the same underlying data structures, the Sysline, Lines, and Block; the file processing thread and the main printing thread.
Being multi-threaded, the timing of when the file processing thread calls drop_data_try versus when the main printing thread will print and then be done with the Sysline instance, that will vary from run to run.


Error: computer automatically shutdown by running CarlaUE4.sh on Ubuntu 20.04

Hey guys, i followed the build instruction by https://carla.readthedocs.io/en/latest/start_quickstart on Ubuntu 20.04.
After Installation i went into folder /opt/carla-simulator/bin and tried to run CarlaUE4.sh. It requires also entering password of sudo.
As the scene showed up, the computer was turned off automatically. Could anybody explain this issue? Is the carlar 0.99 with deb Installation not compatible with ubuntu 20.04?

@joel-mb could you try to launch the deb in a 20.04 distribution?

Hi @happengor ! I'll try to launch the deb package in Ubuntu 20.04 during this week to see if there is some kind of incompatibility. Regarding the issue entering the password, there is a PR fixing this (https://github.com/carla-simulator/carla/pull/2945). As soon as it gets merged I'll update the package.

Thanks, i have solved my problem with a bigger psu.

Thanks, guys, i have solved my problem with a bigger psu. Now i can launch the deb in 20.04.

Perfect! Thanks for the information!


how to encode barcode in stereo-seq

I only found a 'bpMatrix 1 in *.barcodeToPos.h5 file, which was encoded by 15 digits. Could I only translate these codes to barcode sequences with their coordinates, but not use the pairwise reads files?

Yes, you can use the mask format transfer function of ST_BarcodeMap to meet your requirement. Just run the command line as shown below.
ST_BarcodeMap-0.0.1 --in mask.h5 --out mask.txt --action 3

The output file "mask.txt" contains barcode sequences in  A, T, C, and G bases, along with their corresponding coordinates. Each line of the file contains a record in the following format: barcode, x, y.

thanks, it works


[Migration] Changed existing website name

This commit is to replace the existing website name with github.com.

Changes proposed in this PR:

Replaced github.sec.samsung.net with gihub.com
Updated instruction manuals in doc folder
Fixed a bug of webhook handler

Self evaluation

local test: okay
gbs test: okay
aging test: okay

Signed-off-by: Geunsik Lim<EMAIL_ADDRESS>
[Template] PR Description
In general, github system automatically copies your commit message for your convenience.
Please remove unused part of the template after writing your own PR description with this template.
$ git commit -s filename1 filename2 ... [enter]

Summarize changes in around 50 characters or less

More detailed explanatory text, if necessary. Wrap it to about 72
characters or so. In some contexts, the first line is treated as the
subject of the commit and the rest of the text as the body. The
blank line separating the summary from the body is critical;
various tools like `log`, `shortlog` and `rebase` can get confused
if you run the two together.

Further paragraphs come after blank lines.

**Changes proposed in this PR:**
- Bullet points are okay, too
- Typically a hyphen or asterisk is used for the bullet, preceded
  by a single space, with blank lines in between, but conventions vary here.

Resolves: #123
See also: #456, #789

**Self evaluation:**
1. Build test: [ ]Passed [ ]Failed [*]Skipped
2. Run test: [ ]Passed [ ]Failed [* ]Skipped

**How to evaluate:**
1. Describe how to evaluate in order to be reproduced by reviewer(s).

Add signed-off message automatically by running **$git commit -s ...** command.

$ git push origin <your_branch_name>

:octocat: cibot: :+1: This PR looks great - It is just a test message.

:octocat: cibot: :+1: This PR looks great - It is just a test message.


feat(Alabama): Resurrect Alabama Supremes

Draft PR for establishing PDF parsing
And the resurrection of the Alabama Supremes.
The parsing is simple enough and the PDFs are
standardized enough to use some simple logic
to parse them all out
But I've not added to abstract before and I wanted
to get a conversation going.

@mlissner As a son of the state of Alabama, I think its time we brought it back into the courtlistener fold.
I used -- pdfplumber and I think it works nicely enough.  Although I'm sure this may need a broader discussion with
@arderyp and @johnhawkinson and @satsuki-chan
I thought I would at least kick it back off.  Between the number of courts that do this its probably time to add
PDF parsing, and some testing infrastructure.

this looks clean to me.  My only suggestion is perhaps more commenting to explain some of the more cryptic PDF looping stuff.
Let's hope they have some consistent/automated way of producing these PDFs.  I've generally had a rough time parsing human generated PDFs online, but we might as well give it a go!

@arderyp I took the general idea - and put it to work in Colorado - I think it translates nicely.


Feature/user active organization

Why did we add tasks_and_annotations.json ? And also do we have some tests that cover this feature?

I removed tasks_and_annotations.json and added it to .gitignore to prevent this thing. Also added simple test for active_organization.


gboost-lambda

Create a library, gboost-lambda that's a middy plugin that when in dev mode, writes all events  (overwriting old ones) to s3 bucket. Then locally, in VS Code enable dev to quickly debug (line by line) the function by getting event from S3.
How will local line-by-line debug process know which key to access event from?
Investigate lambda-local vs node-lambda

Instead, use SST live lambda debugging.


#if canImport is better than #if os

Use the #if canImport(Darwin)...#elseif canImport(Glibc) dance move instead of the os one.

changed my mind. Not really better.


Path finding support for block bounding boxes.

This functionality is required for several block types, including slabs and stairs.

https://github.com/DarkStorm652/DarkBot/commit/67e7898a7eec95684d804d7eeafa8256b4b2f4f5
I'm currently just adding bounding boxes of other blocks and I will close this and merge the development branch once complete.


🐛 Compatibility Concerning Custom Parameters

It just came up in a discussion with @burgholzer that most (all) of the enumerations used to define the different parameters, e.g., QDMI_DEVICE_PROPERTY_T, define a couple of custom values. Those enable device implementers to quickly test the exposure of properties that are not yet included in the QDMI without requesting a change of QDMI.
The issue with those custom parameters is that they are supposed to follow after all regular enumeration values. The last member of the enumeration is then a value that defines the number of elements in the enumeration and is used for bounds checking, i.e., whether the passed enumeration value is valid.
When an upgrade of QDMI defines new enumeration values in some of those enumerations, those custom parameters are pushed back, and their value increases. Hence, old QDMI device implementations that support a custom parameter may not handle this parameter correctly anymore. Since the concrete integer value behind the enumeration constant is assigned to another identifier now. In the compiled library, however, not the identifier of the enumeration members is used but instead the actual value of those constants (which now became another meaning).
The proposal to solve this issue would be, to assign the maximal possible integer values to the custom parameter enumeration values in order to

fix the value of those custom parameters across versions of QDMI, and
enable better validation of the passed parameter values.
For the second point, note that the ...MAX member of each enumeration should denote the number of regular members, excluding the custom members of an enumeration. Hence, the custom parameters will always lay outside of the allowed range for parameter values. This is sensible, as no device is required to implement those custom parameters. They are only meant for custom experimental usage.

Good that we caught this before there are too many QDMI device implementations around. Those would be horrible bugs to debug. I like the suggestion very much. Let's do it that way 👍🏼


invalid syntax

Hello @varunr-uc,
It looks like you removed the description.  If you still see an issue, could you please update it?

Hello @varunr-uc,
It looks like you removed the description.  If you still see an issue, could you please update it?


How do you change the default region for amplify cli?

** Which Category is your question related to? **
configuration
** What AWS Services are you utilizing? **
Amplify
** Provide additional details e.g. code snippets **
I am not sure how my default amplify region was set to eu-west-2 but that's not the region I want. Now whenever I create a new resources, it's always in eu-west-2 but I'm in the US.
I tried doing amplify configure but that seems to just add a new profile to my .aws credentials. I also tried doing amplify storage add --profile profilename but that doesn't change anything.
Any ideas of how to change the amplify default region or do I need to uninstall/reinstall the cli? I don't even recall ever selecting eu-west-2 but could very well have been a misconfiguration on my part.

@ajohnsen ahh, I tried amplify configure which seems to create a new aws profile. I'll look at aws configure and see if somehow I have my default region incorrect.
Thanks for the info!

You could run amplify configure project and use a new profile with the desired region


docs: Minor text edits after review

This change is

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@adambhere, something's wrong with your Git history, there's a merge commit inside. Let's fix this up together.

Superseded by https://github.com/heremaps/oss-review-toolkit/pull/494.


Update dependencies to community versions.

@futurejones I did create tags, which I think is all that SPM cares for (note that CI did pass successfully).  It's a good point that I hadn't checked GitHub releases, though.  Is there really any reason to support them?  I see that OpenSSL doesn't even have releases for many of the prior tags.  Maybe just for major or minor releases, but not patch releases?

I missed the tag which should be ok but I thought the purpose of the update was to reflect the change to the Kitura Organization?
Shouldn't we be doing a proper release with an explanation as to what the release is for?

I missed the tag which should be ok but I thought the purpose of the update was to reflect the change to the Kitura Organization?
Shouldn't we be doing a proper release with an explanation as to what the release is for?

Yeah, that's a good point.  I'll start doing that.


Correct E2EE for Koofr

Reason

[X] Fix: Wrong information
[ ] Fix: Typo error
[ ] Fix: License violation
[ ] Add: New Item

Type

[X] Cloud
[ ] S3
[ ] Self-hosted

Name
Koofr does support E2EE with Vault.
Link
https://vault.koofr.net

Hey @bancek
Thank you for contributions and looking into my list
Sorry, i missed it. I will merge it soon


pip install grpcio fails on macOS with Python 3.11.0b3

What version of gRPC and what language are you using?
1.47.0
What operating system (Linux, Windows,...) and version?
macOS 12.4 (21F79)
What runtime / compiler are you using (e.g. python version or version of gcc)
Python 3.11.0b3 with pip 22.1.2 (setuptools 63.1.0 and wheel 0.37.1) and Apple clang version 13.1.6 (clang-13<IP_ADDRESS>.5)
What did you do?
$ python3.11 -m venv env-3-11
$ . env-3-11/bin/activate
(env-3-11) $ python -m pip install -U setuptools wheel
Requirement already satisfied: setuptools in ./env-3-11/lib/python3.11/site-packages (58.1.0)
Collecting setuptools
  Using cached setuptools-63.1.0-py3-none-any.whl (1.2 MB)
Collecting wheel
  Using cached wheel-0.37.1-py2.py3-none-any.whl (35 kB)
Installing collected packages: wheel, setuptools
  Attempting uninstall: setuptools
    Found existing installation: setuptools 58.1.0
    Uninstalling setuptools-58.1.0:
      Successfully uninstalled setuptools-58.1.0
Successfully installed setuptools-63.1.0 wheel-0.37.1
WARNING: You are using pip version 22.0.4; however, version 22.1.2 is available.
You should consider upgrading via the 'env-3-11/bin/python -m pip install --upgrade pip' command.
(env-3-11) $ python -m pip install -U pip
Requirement already satisfied: pip in ./env-3-11/lib/python3.11/site-packages (22.0.4)
Collecting pip
  Using cached pip-22.1.2-py3-none-any.whl (2.1 MB)
Installing collected packages: pip
  Attempting uninstall: pip
    Found existing installation: pip 22.0.4
    Uninstalling pip-22.0.4:
      Successfully uninstalled pip-22.0.4
Successfully installed pip-22.1.2
(env-3-11) $ python -m pip install grpcio

What did you expect to see?
Successful install
What did you see instead?
python -m pip install grpcio output
commands.CommandError: We expect a missing `_needs_stub` attribute from older versions of setuptools. Consider upgrading setuptools.

Anything else we should know about your project / environment?

@gnossen Technically mine was 3 days earlier and on 3.11.0b3 not 3.11.0b4. But yes, they are duplicates… his of mine.

Then how do I fix it


code-oss serve-web built from source doesn't include code-tunnel-oss executable

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: main
OS Version: Linux Devcontainer

Steps to Reproduce:

Clone out repository
Start Devcontainer
Run yarn gulp vscode-linux-x64

Executing ../VSCode-linux-x64/bin/code-oss serve-web results in error spawn ../VSCode-linux-x64/bin/code-tunnel-oss ENOENT.

@connor4312 Can we have a gulp task which builds both and assembles it in the correct location? This cost me a day to figure this out and is very hostile to contributors who don't know this.


Use only rows for tutorial grid cards in home page

This updates the cards in the home page based on a personal design preference (please provide opinions) and adds static captures to avoid build warnings.

@yvonnefroehlich this is what the frontpage looks like in this PR
https://github.com/user-attachments/assets/b3ef15bf-e8d4-48aa-9549-1de3d6ef56d1

I am definitely open for improvements on the layout of the intro page! @weiji14 already tried different card setups in PR #12 .
I agree haven equally sized images would definitely look nicer. Do you mean with "Use only rows" that all six cards are now placed in one row? Maybe you can provide a screenshot how the intro page would look like with your changes 🙂 .

I'm willing to compromise on equal sized images (or equal sized cards rather). My biggest gripe was that the Tutorial 4 image was too tall, but it seems like this has been shortened now for the front page, so it might look better with equal sized cards.

Let's stick with the original home page, since it allows for nice long-form images like the choropleth map


Night CI 2024-01-30: Failed

action url: https://github.com/spidernet-io/egressgateway/actions/runs/7704583967

for testing


Issue while using salesforce volos-connectors.

I am getting the following error:--
{
"fault": {
"faultstring": "Script node executed prematurely: Error: Cannot find module 'volos-salesforce'\nError: Cannot find module 'volos-salesforce'\n    at module.js:340:0\n    at module.js:280:0\n    at module.js:364:0\n    at require (module.js:380:0)\n    at /organization/environment/api/server-express.js:1:0\n    at module.js:456:0\n    at module.js:474:0\n    at module.js:356:0\n    at module.js:312:0\n    at module.js:497:0\n    at startup (trireme.js:142:0)\n    at trireme.js:923:0\n",
"detail": {
"errorcode": "scripts.node.runtime.ScriptExitedError"
}
}
}
I am getting this error when, I am using salesforce volos-connectors without avault. I am referring to this link... https://github.com/apigee-127/volos-connectors/tree/master/volos-salesforce

Did you npm and download the volos-salesforce ?


Aws#241Added support for HTTPRoute BackendRef ports

What type of PR is this? bug

Which issue does this PR fix: #241
What does this PR do / Why do we need it: It gives the user the ability to control what which posts are registered as targets in Lattice's Target Group.
If an issue # is not available please add repro steps and logs from aws-gateway-controller showing the issue:
Testing done on this change:

?       github.com/aws/aws-application-networking-k8s/pkg/aws   [no test files]
ok      github.com/aws/aws-application-networking-k8s/pkg/aws/services  0.020s  coverage: 2.9% of statements
ok      github.com/aws/aws-application-networking-k8s/pkg/config        0.008s  coverage: 77.4% of statements
ok      github.com/aws/aws-application-networking-k8s/pkg/deploy        0.019s  coverage: 20.6% of statements
?       github.com/aws/aws-application-networking-k8s/pkg/k8s   [no test files]
?       github.com/aws/aws-application-networking-k8s/pkg/model/lattice [no test files]
?       github.com/aws/aws-application-networking-k8s/pkg/runtime       [no test files]
?       github.com/aws/aws-application-networking-k8s/pkg/utils [no test files]
?       github.com/aws/aws-application-networking-k8s/pkg/utils/retry   [no test files]
?       github.com/aws/aws-application-networking-k8s/pkg/utils/ttime   [no test files]
ok      github.com/aws/aws-application-networking-k8s/pkg/deploy/lattice        0.043s  coverage: 86.1% of statements
ok      github.com/aws/aws-application-networking-k8s/pkg/gateway       0.054s  coverage: 78.5% of statements
ok      github.com/aws/aws-application-networking-k8s/pkg/latticestore  0.004s  coverage: 73.3% of statements
ok      github.com/aws/aws-application-networking-k8s/pkg/model/core    0.004s  coverage: 40.9% of statements
ok      github.com/aws/aws-application-networking-k8s/pkg/model/core/graph      0.003s  coverage: 17.2% of statements
ok      github.com/aws/aws-application-networking-k8s/pkg/utils/log     0.003s  coverage: 0.0% of statements [no tests to run]

Automation added to e2e: Yes

Will this PR introduce any new dependencies?: No

Will this break upgrades or downgrades. Has updating a running cluster been tested?: No
Does this PR introduce any user-facing change?: No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

30 of 33 (90.91%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 32.806%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/gateway/model_build_targetgroup.go
0
1
0.0%

pkg/gateway/model_build_targets.go
30
32
93.75%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
3400

Relevant Lines:
10364

💛  - Coveralls

Thank you for the pull request.
Here I am worried about a scenario when a service is referenced by two different backendRefs with different backendRef.Port. I believe only one target group is created per service right now (TG name is like k8s-{service_name}-{namespace}) - so this change might cause another conflict issue.
I think separate target groups should be created either per each backendRef or per each port to fully address the issue. Per port seems better for me personally.

Thank you for the pull request.
Here I am worried about a scenario when a service is referenced by two different backendRefs with different backendRef.Port. I believe only one target group is created per service right now (TG name is like k8s-{service_name}-{namespace}) - so this change might cause another conflict issue.
I think separate target groups should be created either per each backendRef or per each port to fully address the issue. Per port seems better for me personally.

Is this a scenario we support today? Multiple httproutes using the same backendref?

Thank you for the pull request.
Here I am worried about a scenario when a service is referenced by two different backendRefs with different backendRef.Port. I believe only one target group is created per service right now (TG name is like k8s-{service_name}-{namespace}) - so this change might cause another conflict issue.
I think separate target groups should be created either per each backendRef or per each port to fully address the issue. Per port seems better for me personally.

This PR only confine num of targets that intend to be regiestred and didn't change model_build_target_group behavior, does it can indeed introduce new target group creation conflict? For this scenario: "when a service is referenced by two different backendRefs with different backendRef.Port", (if replicas: 1) controller could register 2 targets(same ip different ports) in one same target group?

After some discussion we have decided that we can move forward with disabling such usage (multiple backendRefs) for now.
Can you please update all example configs under examples/ so that they correctly refer to service port? It was okay until now because we have been ignoring port under backendRef, but I am seeing most of the values are incorrect which will start to break things.  examples/inventory-route.yaml for example:
apiVersion: gateway.networking.k8s.io/v1beta1
kind: HTTPRoute
metadata:
  name: inventory
spec:
  parentRefs:
  - name: my-hotel
    sectionName: http
  rules:
  - backendRefs:
    - name: inventory-ver1
      kind: Service
      port: 8090 # wrong, should be service port instead of target port.
      weight: 10

I think we should test e2e on following config mutation(s) and both in happy path and non-happy-path/mismatch and back and forth

modify the port in backendref of HTTPRoute
modify the port in K8S service object

Issue was corrected in #335, closing.


nullable annotations RCTURLRequestDelegate, RCTURLRequestHandler

Summary
I'm working on my own custom networking module for React Native, and found that we can improve DX with nullability annotations, especially on Swift.
Changelog
[Internal] [Changed] - nullable annotations RCTURLRequestDelegate, RCTURLRequestHandler
Test Plan
No behavior changed, but Objective-C nullability annotations

@TheSavior please review and merge

Hey @dulmandakh ,
do you think we could use NS_ASSUME_NONNULL_BEGIN, NS_ASSUME_NONNULL_END macros here? We wouldn't have to write nonnull for every parameter.


Broken release

Currently its possible to release new version on npm but the git commit will fail with a lint error
Error as text:
$ npm run release 0.5.0

><EMAIL_ADDRESS>release
> release-it 0.5.0

WARNING Environment variable "GITHUB_TOKEN" is required for automated GitHub Releases.
WARNING Falling back to web-based GitHub Release.
WARNING The recommended bump is "minor", but is overridden with "0.5.0".

🚀 Let's release @opendesign/psd-ts (0.0.0-experimental...0.5.0)

Changelog:
## [0.5.0](https://github.com/opendesigndev/psd-ts/compare/0.2.0...0.5.0) (2023-01-11)

### Features
* AdditionalLayerInfos; LinkedLayers ([#54](https://github.com/opendesigndev/psd-ts/issues/54)) ([bf9540b](https://github.com/opendesigndev/psd-ts/commit/bf9540b784e23dcfe49b30fdba2931177d500ae2))
* expose ICC profile ([aa7679e](https://github.com/opendesigndev/psd-ts/commit/aa7679e6e79e22b8ea8ff8a8d4414cc90d6d7bf7))
* Implement additional ImageResources ([#55](https://github.com/opendesigndev/psd-ts/issues/55)) ([1d1e702](https://github.com/opendesigndev/psd-ts/commit/1d1e70234282e09da2404132368d5bbbb4d31aa5))
* implement EngineData parsing ([8c5f09c](https://github.com/opendesigndev/psd-ts/commit/8c5f09cf5b0338cda1344b56dd1aa9b1979da195))
* Implement reading mask data ([#56](https://github.com/opendesigndev/psd-ts/issues/56)) ([0f99674](https://github.com/opendesigndev/psd-ts/commit/0f9967493297a139d4773b1bb63991a6d8ae6b72))

### Bug Fixes
* ALI block 'cinf' has diffent size for PSB ([70ffd71](https://github.com/opendesigndev/psd-ts/commit/70ffd7107490400a6d4d5f9a595e8e0b95e60c91))
* Don't align ALI block size to 4 byte boundary ([f4fc949](https://github.com/opendesigndev/psd-ts/commit/f4fc9497d2826aeaed17910194dc9e8f7130ebe9))
* handle empty channel data ([9cd2d8f](https://github.com/opendesigndev/psd-ts/commit/9cd2d8f1caeeed778a9c902892f524d2d96b3f1b))
* left sidebar width in wider screen ([702eeed](https://github.com/opendesigndev/psd-ts/commit/702eeed01ae1da5338cf7aeb2b45002cb33c45ef))
* readme update. need to fileVariable name instead of module name ([1b6d1ca](https://github.com/opendesigndev/psd-ts/commit/1b6d1ca25d295bf2956191f466d358bc4a823a59))

Changeset:
 M ../../package-lock.json
 M CHANGELOG.md
 M package.json

? Publish @opendesign/psd-ts to npm? Yes
? Commit (Release 0.5.0)? Yes
ERROR Error:
> lint
> eslint . && prettier --check .

/Users/tomasrychlik/work-local/psd-ts/packages/benchmark/src/psd-js.d.ts
   15:11  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
   16:15  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  302:24  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  324:21  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  327:18  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  381:13  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  408:23  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  409:27  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  410:19  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

/Users/tomasrychlik/work-local/psd-ts/packages/example-browser/src/main.ts
  47:46  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  83:55  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

/Users/tomasrychlik/work-local/psd-ts/packages/psd/tests/unit/engineData.test.ts
  11:9  warning  'Cursor' is defined but never used  @typescript-eslint/no-unused-vars

/Users/tomasrychlik/work-local/psd-ts/packages/psd/vite.config.ts
  9:30  warning  'env' is defined but never used  @typescript-eslint/no-unused-vars

✖ 13 problems (0 errors, 13 warnings)

Checking formatting...
[warn] packages/psd/CHANGELOG.md
[warn] Code style issues found in the above file. Forgot to run Prettier?
husky - pre-commit hook exited with code 1 (error)
Rolling back changes...
npm ERR! Lifecycle script `release` failed with error:
npm ERR! Error: command failed
npm ERR!   in workspace<EMAIL_ADDRESS>npm ERR!   at location: /Users/tomasrychlik/work-local/psd-ts/packages/psd

i think it doesnt crash on the lint warnings but on the formatting, which is actually generated by release-it:
checking formatting...
[warn] packages/psd/CHANGELOG.md
[warn] Code style issues found in the above file. Forgot to run Prettier?

also the changelog generated by release-it seems wrong, it's comparing 0.2.0...0.5.0 even though there is version 0.3.0. I'm not familiar with how it works so hard for me to debug now


Should SignalR pass a resource into IPolicyEvaluator?

MVC passes in the AuthorizationFilterContext.  SignalR should decide what resource is appropriate (if any)

I don't think this is much work. We should just look at what MVC passes in and pass a similar thing that contains SignalR-related state. For the HTTP connection level we can't pass much extra in, but when authenticating a specific invocation we can.

Pass in the endpoint IMO. We're converging around that as the thing that has all of the infoZ.

Is that true for SignalR though? There's all the connection metadata on ConnectionContext and I don't know if that's replicated on the endpoint.

If it's truly metadata then you should add it to the endpoint metadata. If it's part of the request, then I dunno 🤷♂

Triage decision:

Add relevant metadata to the endpoint
Pass the endpoint in as the resource

We don't have Hub-level auth any more, but we do still do method-level auth. We need to prepare a resource and pass it in. We can't just use the endpoint here because we need to include the method being executed (and the args?)

How does that work if you're doing middleware-based auth?

We still do that auth ourselves by manually calling AuthorizeAsync.

Ah gotcha. I saw you reply and had a minor panic because I thought I understood what you were doing here already. It makes sense since the middleware won't run on arbitrary signalR messages.

Acceptance checklist (check one item)

[ ] We decided not to take this fix.
[ ] The fix is tests-only.
[x] The fix contains product changes (check all items below).

[x] Relevant XML documentation comments for new public APIs are present.
[x] Narrative docs (docs.microsoft.com) are updated. (check one item below)

[x] The change requires a new article. An issue with an outline has been filed here: [aspnet/AspNetCore.Docs/issues/13050]
[ ] The change requires a change to an existing article. A docs PR with these changes is linked here: [PR LINK]
[ ] The change requires no docs changes.

[x] Verification has been completed. (check one item below)

[x] The change is in the shared framework and was verified against the following versions

SDK installer: [3.0.100-preview7-012687]
ASP.NET Core Runtime: [3.0.0-preview7.19326.10]
.NET Core Runtime: [3.0.0-preview7-27826-04]

[ ] The change is in an OOB NuGet/NPM/JAR package and was verified against the following version of that package: [PACKAGE ID] [VERSION]


Add support for litex_vexriscv GPIO interrupts

This adds support for GPIO interrupts which has been added to LiteX recently: https://github.com/enjoy-digital/litex/blob/master/litex/soc/cores/gpio.py#L21

Here's a patch that resolves the device tree problems (but not the IRQ disable problems):
https://gitlab.raptorengineering.com/kestrel-collaboration/kestrel-firmware/zephyr-rtos/-/commit/4769452c23d02bd3635669205dd5a62261144b4c
And an example DT entry:
https://gitlab.raptorengineering.com/kestrel-collaboration/kestrel-firmware/zephyr-rtos/-/commit/34b7ae41364bc6666f86eb897602248e17f17945

@madscientist159 since your solution looks nice for our custom CSR offset issue I cherry-picked this commit from the Kestrel Project: https://gitlab.raptorengineering.com/kestrel-collaboration/kestrel-firmware/zephyr-rtos/-/commit/4769452c23d02bd3635669205dd5a62261144b4c. However the DCO checker is not happy with the commit https://github.com/zephyrproject-rtos/zephyr/pull/33778/checks?check_run_id=2410239087. Are you OK with signing-off this commit? Just to be on the same page - signing-off the commit means you agree with https://docs.zephyrproject.org/latest/contribute/index.html#developer-certification-of-origin-dco.

@madscientist159 Great, thanks! I changed commit message and it passed CI check so it is good now.

@mnkp could you take a look at CI tests? For some reason it fails and it doesn't look like something relevant to this PR.
1: https://github.com/zephyrproject-rtos/zephyr/pull/33778/checks?check_run_id=2419806413
2: https://github.com/zephyrproject-rtos/zephyr/pull/33778/checks?check_run_id=2419806439

I noticed that when I created this PR LiteX has already added support for changing interrupts mode and edge by CSRs. I've added commit that provides support for this feature in Zephyr driver. I tested it again on Arty A7 and it works as expected.

There have been quite a few errors in the last CI run but at least some of them are legitimate errors that have already been fixed on master. Let's rebase this PR on the latest master and see what happens.

I resolved latest conflict with 1b5542056b818e224fc86fb33862bf46c2277707.
I would appreciate if someone looked at this and got it merged.


Inference with audio

Thank you for this amazing work.
I have been trying to run the inference script (i.e. demo.ipynb) but there is no function in there which takes ASR transcript along with the video. It would be great, if you could point me to the function which also takes ASR transcript for answer generation or provide that script.

same question

Hi, thanks for your interest.
We currently have code for ASR available for pre-processing purposes (see https://github.com/RenShuhuai-Andy/TimeChat/blob/master/docs/DATA.md#automatic-speech-transcription).
I agree that it would be beneficial to integrate this into a function for easier use. I plan to add this feature when I have some free time. Alternatively, if you're interested, you could contribute to adding this feature. Let me know if you're interested!


[Module] Microsoft.Storage/StorageAccounts policy exemption

Description
This update adds the deployment of policy exemptions at the Storage Account level which is a useful deployment orchestration when we must deploy storage accounts with public access allowed and we have policy deployed at a higher scope that blocks that resource creation. Addresses Issue #2996.
Pipeline references

Type of Change
Please delete options that are not relevant.

[X] New feature (non-breaking change which adds functionality)
[X] Update to documentation

Checklist

[X] I'm sure there are no other open Pull Requests for the same update/change
[X] My corresponding pipelines / checks run clean and green without any errors or warnings
[X] My code follows the style guidelines of this project
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation (readme)
[X] I did format my code

@shawntmeyer This is a new feature that we are introducing like how we do RBAC on resource level.
may I suggest we put this one on hold to bring in this topic into one of internal discussions. I will tag the issue https://github.com/Azure/ResourceModules/issues/2996. as well.
CC: @rahalan

Marked as draft as per offline discussion

Marking as draft until we found the best way to integrate this


Cucumber html report screen is blur and couldn't able to access the report

Using cucumber-js automation testing, after all test cases run html report screen is not visible properly and looks like blur screen action couldn't perform on it.

Imported - `
const fs = require('fs');
const path = require('path');
const reporter = require('cucumber-html-reporter');

In package.json using version -  "cucumber-html-reporter": "^7.1.0"

Command to run - "sudo npx cucumber-js features/ -f json:test/report/cucumber_report.json && node index.js"

Can anyone help me to fix this issue?

I think you're in the wrong project. You probably meant https://github.com/gkushang/cucumber-html-reporter.


Paths should follow the styleguide

Following the Houston app demo;

[ ] The directory structure need to be only including routes (not components, services or pipes). Components, services and pipes need to be in an _ directory inside the route
The following commands need to be changes (feel free to check those that are solved):

[ ] new: simply a matter of updating the scaffold.
[ ] generate:

[ ] component/service/pipe: need to be added to an _ directory in the route specified. For example, ng generate component foo/bar/blah should be generated in the directory foo/bar/_/blah. If the _ is included then we don't need to add it (an _ route would be invalid here).
[ ] route: the scaffold need to include an empty _ directory under the route itself.

[ ] Adding an index.ts file to all scaffolds that export the component/route/service/pipe of that directory.

I think that's it for this.

We should put off merging this this PR until the official style guide is in. Otherwise users will have no idea nor guidance as to how the structure is meant to be used.

That is the official styleguide though. The document is going to adhere to this, not the other way around.

The repo is not a document. We can't direct users to the repo for insights on style guide issues.
We need a document that users can read and understand before we change the CLI to use it.

At the current state of the project (pre-alpha) I think we can make changes without documentation in place. Especially given our milestone goals.

Hi @hansl. Would you have a link to the repo mentioned?

Fixed via #427


sudoswapの改造について、考える

[ ] Request form
[ ] Fix title
[ ] Ask in Slack
[ ] JIRA issued
[ ] Prepare with the organizer
[ ] Setting the goal
[ ] Slides
[ ] Movies preparation
[ ] The day!
[ ] PDF release in SlideShare
[ ] Publish the movie
[ ] Subtitle to the movide
[ ] Publish the blog

Details of request

https://sudoswap.xyz/#/


Train Simple Audio Recognition - TinyML

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
2.12.0
Custom code
Yes
OS platform and distribution
Windows 11
Mobile device
No response
Python version
3.10.12
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
Issue Report - Error in Training Audio Recognition Model
Description:
I am trying to train a simple audio recognition model as described in the book "TinyML." I am using Google Colab to train the model. However, I encountered errors during both the installation of dependencies and the training process.
Error during Install Dependencies:
When attempting to install dependencies using the command
!pip uninstall -y tensorflow tensorflow_estimator tensorboard
!pip install -q tf-estimator-nightly==1.14.0.dev2019072901 tf-nightly-gpu==1.15.0.dev20190729
I encountered the following error:
ERROR: Could not find a version that satisfies the requirement tf-nightly-gpu==1.15.0.dev20190729 (from versions: 2.12.0)
ERROR: No matching distribution found for tf-nightly-gpu==1.15.0.dev20190729
Error during Training - ModuleNotFoundError:
Error to Begin Training:
Upon running the training script with TensorFlow in the "Begin Training" Section, I received the following error:
Traceback (most recent call last):
File "/content/tensorflow/tensorflow/examples/speech_commands/train.py", line 81, in
import input_data
File "/content/tensorflow/tensorflow/examples/speech_commands/input_data.py", line 35, in
from tensorflow.contrib.framework.python.ops import audio_ops as contrib_audio
ModuleNotFoundError: No module named 'tensorflow.contrib'
Observations:
I suspect that these errors are occurring because the code provided in the book is intended for TensorFlow 1.15, while I am using TensorFlow 2.12.0. Since TensorFlow 1.15 is no longer supported. Not sure how I can resolve this. Please help me to fix this issue.
Standalone code to reproduce the issue
https://colab.research.google.com/drive/1t2QMMiCdIxP3xnoNyiz9FjmPmbrF0_iD?usp=sharing

Relevant log output
ERROR: Could not find a version that satisfies the requirement tf-nightly-gpu==1.15.0.dev20190729 (from versions: 2.12.0)
ERROR: No matching distribution found for tf-nightly-gpu==1.15.0.dev20190729

Traceback (most recent call last):
  File "/content/tensorflow/tensorflow/examples/speech_commands/train.py", line 81, in <module>
    import input_data
  File "/content/tensorflow/tensorflow/examples/speech_commands/input_data.py", line 35, in <module>
    from tensorflow.contrib.framework.python.ops import audio_ops as contrib_audio
ModuleNotFoundError: No module named 'tensorflow.contrib'

@petewarden
@dansitu

@siddarthnandy,
tensorflow.contrib is not available in tensorflow v2.x. Removed the old tf.contrib.layers and replace them with TF Slim symbols.
Could you please take a look at this official migration doc link which refers to the Migrate from TensorFlow 1.x to TensorFlow 2.
https://www.tensorflow.org/guide/migrate
Thank you!

It is not straight forward on how to do this migration. Need some help. Thanks

Has anyone else already completed the migration that I can use

Need some help. Thanks. Still not resolved

Need some help. Thanks. Still not resolved

Need some help. Thanks. Still not resolved

This issue is not resolved. Any help would be grateful.

will try it thanks

Hi @siddarthnandy
Did you get a chance to try the example?
Feel free to close the issue if it is resolved.
Thanks.

fixed thanks.


CSS-Networking - Update firewall-faq.yml

Updating the Requirement for AZFW from this ICM
https://portal.microsofticm.com/imp/v3/incidents/incident/507758151/summary

@vhorne

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

Never mind. Changes were merged in private repo PR:
https://github.com/MicrosoftDocs/azure-docs-pr/pull/278194
#please-close


ci: Run gittuf workflows only on gittuf/gittuf

This avoids failures of gittuf workflows for forks that may not have the gittuf refs.

Possibly, we need to recognize too that the RSL entries synced here pertain to pushes to the main repo. So it's also possible someone wants a separate RSL for their mirror...


Disabling a monitor causes it to no longer be detected

Disabling through either kanshi, wlr-randr, or hyperctl makes the monitor undetectable through either.
So for example if I run hyprctl keyword monitor LVDS-1, disable , the monitor LVDS-1 can no longer be found through: hyprctl monitors, or wlr-randr. Thus making it impossible to re-enable. Perhaps the issue that is being alluded to all the way at the end of #453. Perhaps this is even introduced by the fix?
running latest git version.

So for example if I run hyprctl keyword monitor LVDS-1, disable , the monitor LVDS-1 can no longer be found through: hyprctl monitors, or wlr-randr.

Correct

Thus making it impossible to re-enable.

Incorrect. Run hyprctl keyword monitor LVDS-1,pref,auto,auto and it will come back

And so it does. Reading the wiki I tried to create way to re-enable monitors regardsless of their name, through
hyprctl keyword monitor ,pref,auto,auto
but that doesn't work. Can I ask why it is removed, as opposed to disabled (like sway / wayfire do)?
It becomes more challenging to have kanshi automatically react to monitor disconnects, since it can't match anymore to the now removed internal monitor

disable does exactly what it says. I think you're confusing it with dpms.

That might very well be the case. The reason I bring it up, is that kanshi profiles disabling a display when an external monitor is connected, depend on the original still being found (though in disabled state) when external monitor is subsequently disconnected (as is apt to happen with laptop docking). This is how it does work with wayfire and sway. However due to hyperland actually removing (also through kanshi / wlr-randr) this plug and play behavior no longer functions.
the tooling can no longer differentiate between a disconnected and disabled monitor
I'll show some output of wlr-randr when disabling primary screen in another wlroots based comp.

LVDS-1 "LG Display 0x02EB (LVDS-1)"
  Physical size: 310x170 mm
  Enabled: no
  Modes:
    1366x768 px, 40.015999 Hz
    1366x768 px, 59.995998 Hz (preferred)

Note the Enabled: no

thats dpms

I am not saying it isn't,but the way to get that output still detected, but also in the disabled state is through kanshi, wlr-randr --output bla disable , etc.
consequence: no windows, or workspaces can be on that monitor.
Now with DPMS, there can be. It's late here now, but tomorrow I'll run a test that will show wlr-randr output in a DPMS powered down state. But the point is, the outcome of that won't imply that the disabled state can *only * be set through DPMS. (as we  know it can be done manually).
the fact is that hyprland removes monitors after wlr-randr disable, and sway/wayfire don't. It might also be that the others do it "wrong". However tools like kanshi expect their behavior, to enable this scenario:

laptop is docked
internal screen is "disabled", external screen enabled
after undock, internal screen is re-enabled

step 3 will only work, if the internal monitor isn't removed after kanshi profile application (as happens with sway/wayfire and doesn't happen with Hyprland) .
of course manually re-enabling through hyprctl keyword monitor LVDS-1,pref,auto,auto  would work, but requires hardcoding internal display name.
So way too much words to say, could the different ways these compositors handle this be reason to consider not removing the monitor?

not really, no. You can always make a script to move all the workspaces out when you do dpms.

All but one, but

Hey,
sorry to comment on a closed and "old" issue. Just wanted to report this conversation we've had on Gitlab regarding kind of the same problem. From the last comment of Hendrik Wolff (author of that Shikane tool):

I just went over to #wlroots on Libera Chat, asked around and emersion clarified that hyprland behaves incorrectly. Adding that "[…] the main difference between wl_output and wlr_output_management_head [is that] the former goes away when disabled, but not the latter".
The wayland server should send the enabled event (with the 0 value) instead.
If you need more explanations just head over to the #wlroots IRC channel.

Do you think that it could be possible to "update" Hyprland behaviour, Vaxry? (I'm available to help if necessary). Thanks :)

mhm

patch.txt
try this patch

Tried, but still didn't work

For me neither. It's not a big deal, but as I mentioned in OP tooling expects the other behavior.

Running hyprctl reload re-connects all monitors for me. I have all of them defined in my hyprland.conf file.
I came across this fix by reading this comment on a similar issue.

Gosh, this is still happening, it would be nice if Hyprland had a way to define a fallback-monitor settings to try to re-enable it if there are no monitors marked as available.
The problem with using dpms instead of disabling is that the monitor will get the workspaces/windows anyway.

I've been investigating this a bit, but I have no time at the moment to fully understand how to implement something (will definitely try in the future), but I'll post my findings here, maybe they help somebody else (or vaxry himself, I'll tag him).
As mentioned, the problem is that apparently Hyprland is not exactly following the wayland protocol somewhere.
When a monitor is disabled, Hyprland is sending the finished and done signals via wl_roots (see my previous comment): this shouldn't happen. It seems to me that the reason this is happening is in src/events/Monitors.cpp, in the last line of function listener_change. That call to wlr_output_manager_v1_set_configuration is what is (then) activating the wrong signals.
I'm not sure whether this function shouldn't be called at all in this case, or should be called but with a different CONFIG or g_pCompositor->m_sWLROutputMgr (aka wlr_output_manager_v1) state.
That said, I believe the problem is also in src/helpers/Monitor.cpp. I think the "actually completely destroy the monitor" signal is  sent by wlr_output_manager_v1, whereas the current connection to wlr_output should be used for the "disabling monitor" signal. I'm not too sure about this, in general my plan is to read sway code to understand what they're doing.
Once this is fixed, tools like kanshi or shikane can be correctly used in Hyprland too.
@vaxerski FYI

if that's the root cause, change line 25's m_vMonitors to m_vRealMonitors then and test that.

@leiserfg https://github.com/hyprwm/Hyprland/pull/3718 could you please try with this branch?

@levnikmyskin  it didn't work, when I unplugged the external monitor the laptop screen stayed off.
The logs of hanshi don't mention any status change.

@levnikmyskin  this issue regressed after aquamarine, can you have a look again?

@leiserfg I noticed Vaxry has an open pr on this. I wanted to check anyway as soon as I get some time, but lately I'm a little overworked by my daily job...I'm indeed still running hyprland 0.41 I think, or whatever version before aquamarine

I tried the PR from @vaxerski and that didn't work.

problem is that, kanshi is interfering with hyprland monitors
my case, say I have two monitors, Left and Right
and if I disable the right one using kanshi profile  kanshictl switch left , right monitor will be disabled, and in output of hyprland monitors i will see only the left monitor.
Now no matter what, i can not enable 2nd monitor using kanshi.
to enable it, I need to kill kanshi daemon. and then restart kanshi or run hyprctl keyword monitor ,pref,auto,auto
any fix please @vaxerski  . this is interfering in daily workflow when i want to enable and disable a monitor, and we only got kanshi as a reliable monitor configuration tool

Kanshi disables the monitor, which is correct. To see the full list do hyprland monitors all.
The correct way of allowing both enabling and disabling the same monitor with shikane  at least, is to have both profiles and switching to the second profile by hand. I advise moving from kanshi to shikane as its implementation is way more correct.

Kanshi disables the monitor, which is correct. To see the full list do hyprland monitors all. The correct way of allowing both enabling and disabling the same monitor with shikane at least, is to have both profiles and switching to the second profile by hand. I advise moving from kanshi to shikane as its implementation is way more correct.

i tried shikane, and it seems to be extremely buggy for me, can not switch between profiles with ease, sometimes it straight outs destroys my hyprland setup when i switch between profiles quickly for testsing, sometimes it keeps picking up a secondary profile as default.

Kanshi can also do profile switching, like shikane does, so no reason to jump from one to the other.
That said, that behaviour is weird, in my case I manage to re enable disabled monitor with kanshi with no problems. On what hyprland commit/tag are you on?

Kanshi can also do profile switching, like shikane does, so no reason to jump from one to the other. That said, that behaviour is weird, in my case I manage to re enable disabled monitor with kanshi with no problems. On what hyprland commit/tag are you on?

I know, I used to use Kanshi, I moved to shikane cause kanshi is easier to debug the events when something breaks.

Kanshi can also do profile switching, like shikane does, so no reason to jump from one to the other. That said, that behaviour is weird, in my case I manage to re enable disabled monitor with kanshi with no problems. On what hyprland commit/tag are you on?

hyprland 0.44.1-2 AUR version


[5.0] Eloquent model's static::$mutatorCache breaks for StudlyCased attributes

In the Eloquent model's class there is public static function cacheMutatedAttributes($class) that stores cache of mutators using lines:
# src/Illuminate/Database/Eloquent/Model.php (3238)

// Here we will extract all of the mutated attributes so that we can quickly
// spin through them after we export models to their array form, which we
// need to be fast. This'll let us know the attributes that can mutate.
foreach (get_class_methods($class) as $method)
{
	if (strpos($method, 'Attribute') !== false &&
				preg_match('/^get(.+)Attribute$/', $method, $matches))
	{
		if (static::$snakeAttributes) $matches[1] = snake_case($matches[1]);

		$mutatedAttributes[] = lcfirst($matches[1]);
	}
}

static::$mutatorCache[$class] = $mutatedAttributes;

As you can see, before matched attribute is stored in $mutatorCache it passed through lcfirst() function. And this is the problem if you are using StudlyCased column names, because Laravel don't see them in this cache when you are trying to get them and so doesn't fire associated mutator method:
# src/Illuminate/Database/Eloquent/Model.php (2403)

$mutatedAttributes = $this->getMutatedAttributes();

// We want to spin through all the mutated attributes for this model and call
// the mutator for the attribute. We cache off every mutated attributes so
// we don't have to constantly check on attributes that actually change.
foreach ($mutatedAttributes as $key)
{
	if ( ! array_key_exists($key, $attributes)) continue;

	$attributes[$key] = $this->mutateAttributeForArray(
		$key, $attributes[$key]
	);
}

Eloquent's convention is to use snake case column names.

@taylorotwell I understood, but I'm working with already existing database and I have no options. I'll try to adopt this behaviour. But anyway, thank you for the answer, I'm closing the ticket.


BUG - File already download log not showing up

Description of the issue
When I try to download same file few times, it doesn't give me message that file was already download both from imap-data-access and imap_cli command line. This message would help save time and understand that our cli is not downloading same file.
Steps to reproduce the issue
download same file using either imap-data-access or imap_cli command
Expected behavior (What should happen)
should give file already download message
Actual behavior (What does happen)
nothing in imap_cli or download successful shows up in imap-data-access cli
Code Snippet:
https://github.com/IMAP-Science-Operations-Center/imap-data-access/blob/main/imap_data_access/io.py#L80

Additional notes, affected areas, and suggested fixes
No response

The default log level is set to warning.
https://docs.python.org/3/howto/logging.html#a-simple-example
You should be able to run with -v to get verbose output, i.e. the INFO level details. Should this be changed to just a standard print message? That does introduce new spam to the output terminal though when you are using the utility as expected with no way of avoiding the message.


super.destroy() called twice when destroying Graphics

super.destroy() called twice when destroying Graphics
https://github.com/pixijs/pixi.js/blob/19d7cba1897abe1a0087b13a5c3a54c0c079c250/packages/graphics/src/Graphics.ts#L1367
    public destroy(options: IDestroyOptions|boolean): void
    {
        super.destroy(options);
        this._geometry.refCount--;
        if (this._geometry.refCount === 0)
        {
            this._geometry.dispose();
        }

        this._matrix = null;
        this.currentPath = null;
        this._lineStyle.destroy();
        this._lineStyle = null;
        this._fillStyle.destroy();
        this._fillStyle = null;
        this._geometry = null;
        this.shader = null;
        this.vertexData = null;
        this.batches.length = 0;
        this.batches = null;

        super.destroy(options);
    }

Expected Behavior
super.destroy() called only once.
Current Behavior
super.destroy() called twice.
Possible Solution
Call super.destroy() only at start of destroy()
Environment

pixi.js version: 5.3.2
Browser & Version: Opera 29
OS & Version: MacOS 10.15.6

Good one! That's a mistake we should remove the first destroy. Welcome fix for this.


Name section updates

Fix parsing so that it does not fail if function names do not come first
Add support for all name types in the core and extended-name-section specifications
Preserve index because it is significant (names can appear in any order)

Is it this spec, right?
https://webassembly.github.io/spec/core/appendix/custom.html#name-section
I checked in the testsuite but I cannot find any test stressing this aspect.
Would you mind adding a test that will, at least, cover the happy path and prevent us from breaking the functionality in the future?

The existing tests cover at least some of this: specifically function and global names.
We'll have to craft some kind of wast for the rest.

I've added test conditions to the existing test to verify that the name subsections which appear in the existing parser test file is fully parsed, and that the contents are correct where possible (validating the name of every function isn't feasible, and also isn't likely to remain stable across rebuilds of the test WASM file from Rust anyway AFAIK).
While it doesn't cover 100% of cases yet, all cases use the same two code paths so I would consider it unlikely that one kind of name would succeed where another fails. Additionally, this code is used in every existing test where a test file is loaded with a name section.
By any measure, the testing is more comprehensive now than before. But if there are additional test cases you'd like to see, please let me know.