bug: automatic doc creation on forked main branch

See details for this bug at: https://github.com/peter-evans/create-pull-request/issues/1031
Describe the bug
Forks are triggering automatic documentation workflows including a PR  back to the fork's main branch .
To Reproduce
Steps to reproduce the behavior:

Fork the repo
Branch, commit and push a change to the fork
Submit a PR back to the project
Notice a workflow is started that submits a PR back to the forked repository's main branch

Expected behavior
Forked PRs get workflow feedback about the build, but never generate a PR back to the fork.
Additional context
Test a condition constraint on PR GitHub Action for forked repos:
https://github.com/peter-evans/create-pull-request/blob/main/docs/concepts-guidelines.md

Fixed with PR https://github.com/ourchitecture/hello-cloud/pull/168.
I discovered that the issue actually occurred after the original PR was merged into the primary repo and then the forked repository was synchronized. That caused a "merge" push to main in the forked PR which resulted in yet another PR from the forked action. It is properly skipping this second PR now.


Functions to delete and regenerate mapping rules + django shell script to execute them

changes now in #143


Raw public key provisioning is using certificate chain

According to SPDM ver 1.2.1 section 7.2.2 Raw public keys

Alternatively to certificate chains, the vendor can provision the raw public key of the Responder to the Requester in a
trusted environment; for example, during the secure manufacturing process. In this case, trust of the public key of the
Responder is established without the need for a certificate-based public key infrastructure. The definition of a trusted
environment is outside of the scope of this specification.
The format of the provisioned public key is out of scope of this specification. Vendors can use proprietary formats or
public key formats that other standards define, such as RFC7250 and RFC4716.

Libspdm uses certificate chain even in the raw public key provisioning (slot 0xFF) scenario.
Would you mind to let me know your opinion about this?

Libspdm uses certificate chain

Only the leaf certificate is required.
My opinion is that until the SPDM specification mandates a single raw public key format it will be difficult for a general purpose library like libspdm to provide support. I would be fine if it was a simple ASN.1 data structure that came with a simple parser and not an entire certificate chain parsing library. Maybe the specification could have its blessed format that it recommends everyone, including libspdm, use, but allow implementers to use their own format if, for example, ASN.1 doesn't work for them.

Only the leaf certificate is required.

Yes though, it is still a certificate instead of the raw public key.
How about change to use just ASN.1 SubjectPublicKeyInfo of a certificate, as the specification claims (RFC7250)?
as you mentioned:

a simple ASN.1 data structure that came with a simple parser and not an entire certificate chain parsing library.

11/7/2022 - One possible option - libspdm can include an ASN.1 parser, knowing it will only parse the raw public key. Not a full parser. Hope it is small portion of code. Also, we assume the provisioned public key is good, not malicious.
@xiangfeima, will you please take this issue and submit patch?

@jyao1

One possible option - libspdm can include an ASN.1 parser, knowing it will only parse the raw public key. Not a full parser.

I think we don't need to introduce such "raw public key parser", my idea is to add interface in spdm_crypt_ext_lib.h to read PEM public key, which would be implemented by mbedtls/openssl/null underlaying (similar to the private key reading process).
The PEM public key for testing can be extracted from existing requester/responder key file under unit_test/sample_key.


:bug: Respect consumer's ack_wait_ms when configuring HTTP push receive_timeout

Fixes #259

#260  👈
main

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

Join @acco and the rest of your teammates on  Graphite


Editing a NFT Workflow

This PR builds on top of having an exclusive "Asset Page" and introduces a new Edit NFT workflow, with a specific route to edit a given NFT

ping @tbergmueller


Update AboutUs

Updated AboutUs.md to include my personal introduction.

Commits should not be done in local master branch


Search for Match and Reconciliation DIVS get cutoff at bottom on smaller screen resolutions

Original author: thadguidry (October 05, 2011 22:29:45)
On smaller screen resolutions the divs for "Search for Match" and "Reconcile column" get cutoff at the bottom.
Users have to manually drag the container div up in order to see more.  This is especially cumbersome for the "Search for Match" which uses the Freebase Suggest widget, and "view more" becomes inaccessible for the user.
Tested on Standard Laptop 15" 1280x800 resolution.
Original issue: http://code.google.com/p/google-refine/issues/detail?id=458

This has now been verified as fixed tested and using latest Version 3.5-beta1 [1b9907e]
Closing.


Glyphs: Column Width control

Column Width should control the gutter width between the rows of glyphs, wrapping according to window width to form the column, which is not actually being controlled directly.

I believe this either has been solved or it’s impossible to be solved because a deskto window can be moved part way off the screen


Android emulator slow.

Build 21354.co_release.210402-1630.
I'm back to the Android emulator.  It's working (unlike 2 or 3 mths ago) - but it's very slow. Android Studio told me:

Detected ADB
The ADB binary found at D:\AndroidSDK\platform-tools\adb.exe is obsolete and has seriousperformance problems with
the Android Emulator. Please update to a newer version to get significantly faster app/file transfer.
OK

Upgraded Android SDK Platform-Tools (and other out-of-date SDK Tools).
However Haxm won't install - the prereqs aren't met and I believe this has to do with Hyper-V being turned on. I don't believe I'm supposed to have Hyper-V on Win10 Home but this is what I see in services.msc:
https://imgur.com/a/qkYZqYP

Haxm install log:

Version: 7.6.5
Output folder: C:\Program Files\Intel\HAXM
Extract: checktool.exe... 100%
Execute: C:\Program Files\Intel\HAXM\checktool.exe --verbose
CPU vendor          *  GenuineIntel
Intel64 supported   *  Yes
VMX supported       -  No
VMX enabled         -  No
EPT supported       -  No
NX supported        *  Yes
NX enabled          *  Yes
Hyper-V disabled    -  No
OS version          *  Windows 10.0.21354
OS architecture     *  x86_64
Guest unoccupied    *  Yes. 0 guest(s)
The system requirements are not satisfied.

This is unrelated to WSL. On Windows 10 Home you are looking for "Virtual Machine Platform" optional component.


Self hosted denokv with backup to amazon S3

#!/usr/bin/env bash
#
# run-denokv.sh
#
# Example script to run denokv locally with S3 sync enabled (without Docker).

# 1) Set AWS environment variables (or set them beforehand)
export AWS_ACCESS_KEY_ID="<>"
export AWS_SECRET_ACCESS_KEY="<>"
export AWS_REGION="eu-north-1"

# 2) Run denokv
denokv \
  --sqlite-path $HOME/database/denokv.sqlite \
  serve \
  --access-token password \
  --s3-bucket my-bucket \
  --s3-prefix some-prefix/6aea9765-2b1e-41c7-8904-0bdcd70b21d3/

I am using this script to start my local denokv service. I want it to replicate the local database in amazon S3. However this does not work. Denokv is starting without issues but it is not syncing data into S3. Where is the problem?

Nvm, will use litestream


feat(results): update cyclonedx reports to support v1.5

Closes: #6827
Proposed Changes
-update cyclonedx reports to support v.1.5 from v.1.3
I submit this contribution under the Apache-2.0 license.

The change looks minimal & clean. Thanks.
Do we need to change anything in the report itself in addition the schema reference?
For example - v1.5 support critical severity
https://cyclonedx.org/docs/1.5/xml/#type_severityType
https://github.com/Checkmarx/kics/blob/2afa90f7d7c466496a49abdd186a7de786d94391/pkg/report/model/cyclonedx.go#L19-L24


14.0 Ready Check trigger no longer works.

Description
All other triggers are working, all options for Ready Check are enabled in the new control panel. No notifications or sounds are playing for my/others ready checks.
Additional information
If available, please include any logs or screenshots depicting the issue you're experiencing.

same issue here

Hmm, that's odd.  The ready check works just fine for me.  What language are you using? Do you have anything set in your cactbot/user/ file?

english i have it defaulted

had to do that to get it fixed

What do you mean by you had to do that to get it fixed? What did you do that fixed it?

I'm using English,
I've never manually edited any of the files.

it want loading the files just removed the customised one from the older versions.

now its randomly working

It doesn't work in French too

It works fine if you do the ready check.  ;)


Add support for .cjs and .mjs input files

I got fed up with not having IntelliSense or type checking in .cjs and .mjs files, so I’ve decided to fix this myself.

Fixes #27957
Fixes #38784

I will review this tomorrow and will provide feedback

Sorry to say that but your implementation is not spec compliant :( While this is a way to do it i am not sure about all the sideeffects this will need more testing.
[ ] - Test case import myCjs from './a/CJS' // Should return default of CJS and CJS is a Directory NodeJS will resolve that in the current version of the loader. see the esm loader Imlementation.
[ ] - Test case import myEsm from './ESM' // Should return ./ESM/package.json.exports node or import propertie or main the complet resolve algo. so find ./ESM/dist/es/module.mjs
Tons more stuff....
I agree that the ts lang server now works as in our old patches befor without spec compliance :(

Sorry to say that but your implementation is not spec compliant

Those examples seem to be about the resolver features, not about the file extensions. The resolver is equally "broken" for .js right now, unless I'm missing something?

@jkrems it is not broken for JS as you can activate syntetic import handling and only import mjs via dynamic import

I think this issue can finaly not get fixed in this way typescripts module system needs refactor much more then accepting .mjs and cjs as extension for js handling.

I think this issue can finaly not get fixed in this way typescripts module system needs refactor much more then accepting .mjs and cjs as extension for js handling.

I think you are right that a more fundamental fix may be desirable. The question is: If just letting people import ./my-file.mjs in vscode and get proper auto-complete is blocked on that and this PR makes the auto-complete work (for people who potentially never touch Typescript), is it fair to delay these quality-of-life fixes until such a fundamental fix is ready? So far it doesn't sound like there's resources and/or a timeline for a major redo of the TS module system. At least that seemed to be the public communication.
So what is the path forward short term, if not a patch like this? People who want to write packages that contain (some) native ESM should stop using vscode to do it? They should use some community fork with these changes and override the project TS (which the ts language server might then pick up..?)?

@jkrems there exists a other workaround without recode that enables that
assume this files
index.d.ts
// interface other typescript types export import

myapp.mjs
import some from 'some-other'

myapp.mjs.d.ts
// This is typescript syntax it can now import .ts .d.ts and .js types and rexport them
export * as types from './index.d.ts'
export = types

The export = is correct typescript syntax it makes now myapp.mjs import able and it will show it with correct types if you want to even import it with specifier as you would do in nodejs you can create additional
myapp.d.ts
// This is typescript syntax it can now import .ts .d.ts and .js types and rexport them
export * as types from './index.d.ts'
export = types

@jkrems and the path forward is clear drop typescript and replace it with solutions like assert calls and jsdoc typechecking :+1:

how to replace typescript linting with eslint
How I proceed:

install globally eslint : npm install -g eslint
install babel-eslint : npm install --save-dev babel-eslint
install eslint-plugin-react : npm install --save-dev eslint-plugin-react
create .eslintrc file in you root directory. here is my config:

{
"env": {
        "browser": true,
        "node": true,
        "es6": true,
        "jest": true,
        "jquery": true
    },
    "parser": "babel-eslint",
    "parserOptions": {
        "ecmaVersion": 6,
        "sourceType": "module",
        "ecmaFeatures": {
            "arrowFunctions": true,
            "binaryLiterals": true,
            "blockBindings": true,
            "classes": true,
            "defaultParams": true,
            "destructuring": true,
            "forOf": true,
            "generators": true,
            "modules": true,
            "objectLiteralComputedProperties": true,
            "objectLiteralDuplicateProperties": true,
            "objectLiteralShorthandMethods": true,
            "objectLiteralShorthandProperties": true,
            "octalLiterals": true,
            "regexUFlag": true,
            "regexYFlag": true,
            "spread": true,
            "superInFunctions": true,
            "templateStrings": true,
            "unicodeCodePointEscapes": true,
            "globalReturn": true,
            "jsx": true,
            "experimentalObjectRestSpread": true
        }
    },
    "plugins": [
        "react"
    ],
    "rules": {
        "strict": 0
    }
}

In VSC, push F1, then write "extension", select "install extensions" and then, write "eslint" and validate. you will have to relaunch VSC
In VSC code, open the user parameters (settings.json) and write:

{
    //disable default javascript validator replaced by eslint
    "javascript.validate.enable" : false
}

Now, it should lint as wanted your ES7 code. If there is any issue with VSC reading eslint config, you can see it in the VSC console (Ctrls
ShiftU).
As a result, ES7 code (spread operator in objects for example) is well linted:

PS: may be my .eslintrc uses some useless extra data for ES7 linting so feel free to remove it :)

I'm not sure how eslint relates to autocomplete. The following currently works in vscode without any .d.ts or other Typescript files involved:
// b.js
export default class Foo { bar() {} }

// a.js
import Foo from './b.js';
new Foo(). // <suggests bar() as an available method>

It doesn't work if b.js is renamed to b.mjs or b.cjs (the latter with the respective syntax change to CommonJS). No amount of eslint can fix that afaik. And writing exhaustive manual .d.ts files for every JavaScript file doesn't sound like a practical workaround.

@jkrems that is your opinion at all and i understand why you have this point i only wanted to explain that so it is clear at present that is the method how you can ship .mjs bundels.
Any way as all this is of topic and i will solve it at a other front i only wanted to point out that this is the same patch that was already posted in the issue befor but now ported for current typescript.

@frank-dspeed

Any way as all this is of topic and i will solve it at a other front i only wanted to point out that this is the same patch that was already posted in the issue befor but now ported for current typescript.

That is incorrect, as that patch only hacks together a way for the TypeScript language server to recognise the .mjs file extension as a JavaScript file, but everything else is still broken with it.

This PR adds proper validation, import auto‑complete and enforces that .cjs files always parse as CommonJS modules and .mjs files always parse as ECMAScript modules.
As for the package.json exports field, that’s issue https://github.com/microsoft/TypeScript/issues/33079, which is out of scope for this PR.

@ExE-Boss do not get me wrong it is a good thing but microsoft will not merge it we would need to maintain a vscode fork for that and i am not joking i am fighting with them since 5+ years.
Your Solution is better then nothing. And it is more then i got done till today :) So i already cherry picked it internal.
but we need to make it more easy useable as sayed overall the path forward is to create or fork the deprecated language-server project then integrate for example this typescript version and create a installer for that so that existing vscode users can simple install this as additional language server
then we could start to solve the problem complet via refactoring this indipendent.

Just wanted to say thank you for doing this work @ExE-Boss 🙏🏻

I got fed up with not having IntelliSense or type checking in .cjs and .mjs files, so I’ve decided to fix this myself.

If some one does want to test this https://github.com/stealify/typescript
npm i -g vscode-typescript@https://github.com/stealify/typescript
# Getting global path
npm root -g

Hit f1 on keyboard open user settings and set
"typescript.tsdk": "{your_global_npm_path}/vscode-typescript/typescript/lib"

restart is not needed.

BUGS
The following 2 bugs to apply for the .mjs and .cjs extension

This should NOT resolve to './module-without-dts.js' './module-without-dts.ts' even if they exist!

import './module-without-dts.mjs'

should resolve './module-with-dts.mjs', './module-with-dts.mjs.d.ts' if thex exist

import './module-with-dts'

should resolve './module-with-dts.mjs', './module-with-dts.mjs.d.ts' if they exist

import './module-with-dts'

That is the intended behaviour.

@ExE-Boss
Sorry that i ask that this only does auto complet for the language server right?
because when i create a module-with-dts.mjs and a module-with-dts.mjs.d.ts
i get no types for that when i do import 'module-with-dts' so it does not resolve module-with-dts.mjs.d.ts

@frank-dspeed That’s because all engines (including Node.js) forbid loading native ES Modules without the file extension.
// This will fail at runtime if `module-with-dts` doesn't exist in the same directory,
// even if `module-with-dts.js` (or `module-with-dts.mjs`) does:
import "./module-with-dts";

@ExE-Boss the 'module-with-dts.mjs'.d.ts part worked already befor.
@ExE-Boss that is not true with the extension part we got a new node --experimental-specifier-resolution=node index and in general we support that all over in v8 and in deno and in node-graaljs we do allow specifiers for esm all over the place inside the ecosystem but ok anway i now understand the full impact of that pull request
I will go ahead then now with rollup-language-server to solve all that compat issues once and for ever with and without typescript :+1: thanks for your effort.

A few years ago when I was working on early support for .vue files, I had pretty good luck with manually telling emacs to treat arbitrary extensions as Typescript. That might still work, although probably intra-file support won't be great.

UPDATE*  At present i expirence no down sides in the EDITOR with such Changes even not with my version that sets everything to .js


InvalidCastException doesn't include type names

Instead of Unable to cast object of type 'System.Object' to type 'IFoo'., we have Specified cast is not valid..

This is by design. The metadata with type names can be removed from the executable image to save space. We only have it sometimes and it's better to be consistent.

This is in the same category as getting good stacktraces for exceptions. I agree that this should not work in the maximum optimization mode, but it should work in the diagnostics friendly mode, e.g. if the data for good exception stacktraces are included, this one should work too.

I would keep this one open in the future milestone.


Rename to azure-pipelines

Rename there was a typo in what @evangelink posted, and I copied it. Now it is missing s in the name, and that does not align with Roslyn.

Merging, it won't have any effect here.


Panel display conditionally

I want to know if there is a way to display a PanelBuilders element conditionally.
For example, if the associated .setData returns empty, I would like to turn the whole panel off.
So if the item displays 'No data', I would rather turn off the whole panel.
The element is part of a SceneFlexLayout, in which one of the children is, but this is probably not important.
Thank you in advance.

@korinekgergely you have to define the data on the layout element, then add a behavior to the layout element. We do not provide these behaviors out of the box yet, but you can easily create them with a few lines of code:
https://github.com/grafana/scenes/blob/main/packages/scenes-app/src/demos/behaviors/HiddenWhenNoDataBehavior.ts


Legacy plugin inlines CSS

⚠ IMPORTANT ⚠ Please check the following list before proceeding. If you ignore this issue template, your issue will be directly closed.

[x] Read the docs.
[x] Use Vite >=2.0. (1.x is no longer supported)
[x] If the issue is related to 1.x -> 2.0 upgrade, read the Migration Guide first.

Describe the bug
When attaching @vitejs/plugin-legacy, the index.css content is inlined into the index-legacy.[hash].js output file. This is reproducible with the base Preact template (and presumably others).
// index-legacy.[hash].js
var __vite_style__=document.createElement("style");__vite_style__.innerHTML="body,html{height:100%;width:100%;padding:0;margin:0;background:#fafafa;...",document.head.appendChild(__vite_style__) // ...`

truncated CSS for brevity

No changes/issues with the non-legacy output.
Reproduction
https://github.com/lukeed/bug-vite-legacy-inline-css
System Info

vite version: 2.0.1
Operating System: Mac OS
Node version: 14.15.5
Package manager (npm/yarn/pnpm) and version: pnpm 5.11.1

Logs (Optional if provided reproduction)
Don't see anything useful within --debug output. Providing summary instead:
dist/assets/index-legacy.13201260.js       4.47kb / brotli: 1.82kb
dist/assets/vendor-legacy.14fe4df4.js      8.71kb / brotli: 3.26kb
dist/assets/polyfills-legacy.1b3a07f4.js   40.77kb / brotli: 14.08kb
dist/assets/favicon.17e50649.svg   1.49kb
dist/index.html                    1.09kb
dist/assets/index.e8186b7a.css     0.35kb / brotli: 0.17kb
dist/assets/index.2844346d.js      4.51kb / brotli: 1.87kb
dist/assets/vendor.cc9d1722.js     8.64kb / brotli: 3.27kb

This is somewhat intentional - right now the modern build preloads the js chunk in parallel to the css using a preload directive. In the legacy build, this will have to be done with an XHR request (which I didn't bother to implement).
I don't think this breaks anything behavior wise, but it surely can be improved.

Yeah, it doesn't break anything, but it duplicates all of the CSS that's already included via the <link rel=stylesheet/> in the markup. Granted, this doesn't apply beyond the initial payload... but maybe deduping the CSS from initial/main entrypoint is all that needs to be done?

Would love an option to not have the CSS inlined in the legacy build since I'm integrating it in a backend-based project where I don't have an index.html entrypoint to transform and thus enqueue the JS and CSS manually.

I would be willing to look into this and make a PR adding that option. But so far, I even fail to see where this inlining is happening - it doesn't seem to come from vite or vite-plugin-legacy (unless I missed it). So it seems so happen in one of the dependencies? Any hint would be welcome!

Same problem here. Backend-based PHP project, enqueuing asset links manually, the inline styles only appear in the index-legacy.abc12345.js file.
I was however able to track down where this is coming from. It's in Vite's core code directly, not the legacy plugin, and is triggered when CSS code-splitting is enabled. The CSS chunk gets produced by these lines:
https://github.com/vitejs/vite/blob/88ded7f16382d83603511de043785e01ee1e4a3a/packages/vite/src/node/plugins/css.ts#L434-L454
If you set config.build.cssCodeSplit = false, the inlining no longer occurs. It's an unfortunate tradeoff, but until a more direct control is available this is your best workaround.
I'm wondering, though... is it actually correct behavior for the whole stylesheet to get inlined here? Shouldn't it only be the aggregated CSS chunks imported in async modules?

Update: turns out there's a bug that causes CSS files to be omitted from the manifest if build.cssCodeSplit is set to false... which could make this a real pain for backend projects. See #3629 and #6477 .
Given that, I can't see a clean workaround. We need an option to turn off the CSS inlining entirely, or only include the async chunks instead of the whole stylesheet.

It'd be really nice to have the option to remove CSS from the legacy file altogether.
I also have a PHP application, WordPress to be spesific.
add_action('wp_enqueue_scripts', function() use ($app, $localizeData) {
  $build = $app->manifests['vite'];

  // Legacy bundle for browsers that don't support modules.
  // Only gets downloaded by older browsers
  $legacyPolyfill = $build->enqueue('vite/legacy-polyfills')[0];
  $handles = $build->enqueue('src/js/app-legacy.js', ['react', 'react-dom', $legacyPolyfill]);

  // This is the modern bundle. This one also enqueues CSS.
  $handles = $build->enqueue('src/js/app.js', $handles[0]);

  // localize_script(...
}

This inlining results in my legacy bundle being much larger than it otherwise would be. The nomodule attribute ensures that modern browsers won't waste their time so it doesn't even matter, but chasing perfection is really rough with an issue like this.

Hello @sapphi-red, recently you fix: allow tree-shake glob eager css in js
Looks like it's a similar issue in legacy plugin
maybe you will have time to fix it
Thanks

The css-js file compiled by non-modern browsers will write the styles twice, and the volume will increase sharply, which should be a problem.
example：
dist/assets/style-legacy.e8e8324b.js
System.register([], function (e, t) {
  "use strict";
  var n = document.createElement("style");
  return (
    (n.innerHTML = "table{color:red},xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\n"),
    document.head.appendChild(n),
    {
      execute: function () {
        e("default", "table{color:red}xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\n");
      },
    }
  );
});

I would also like to see this fixed in a way where I can disable legacy output for CSS, since I already use autoprefixer which is enough legacy compatibility for me.
I have written a small plugin that seems to do the trick for me right now, but please be cautious with using it since I do not understand the inner workings of vite or rollup very well, so it might cause other bugs. It does remove the legacy CSS from the manifest.json and the build output, which is what I wanted, but I do not know if it potentially breaks other things, just to state it again.
import type { Plugin } from 'vite';

export const removeLegacyCss = (): Plugin => {
    return {
        name: 'remove-legacy-css',
        enforce: 'post',
        generateBundle: (_, bundle) => {
            const remove = Object.entries(bundle)
                .filter(([key, value]) => {
                    if ('facadeModuleId' in value) {
                        return key.includes('legacy') && value.facadeModuleId?.endsWith('css');
                    }

                    return false;
                })
                .map(([id]) => {
                    return id;
                });

            for (const key of remove) {
                delete bundle[key];
            }
        },
    };
};

It is then usable like any normal imported plugin, by adding it to the plugins array: plugins: [ removeLegacyCss() ]

@bocom - Would love an option to not have the CSS inlined in the legacy build since I'm integrating it in a backend-based project where I don't have an index.html entrypoint to transform and thus enqueue the JS and CSS manually.

@k1sul1 - It'd be really nice to have the option to remove CSS from the legacy file altogether.

@andronocean - Given that, I can't see a clean workaround. We need an option to turn off the CSS inlining entirely, or only include the async chunks instead of the whole stylesheet.

I also think adding an option to

a) Disable the legacy plugin for SCSS/CSS etc.; or
b) Disable the CSS inlining (not sure if these two points are really that different)

would make a lot of sense for cases like these? For backend integration it breaks stuff for me currently. I already run autoprefixer through postcss over my CSS and then include the generated files directly via <link rel="stylesheet" /> tags. For me that is fine enough.
Is one of the options acceptable to the Vite team? I think one of us would surely create a PR if there is confirmation that we are good to go with that.

Being hit by this issue as well. In general I'm not very fond of the approach used by this plugin as essentially having two builds takes twice the time, twice the space and it creates hard-to-track-down bugs "works on my machine" where a user and developer might run different variants of the build.
Anyway, this issue feels like a showstopper. If anyone can give some overall pointers I would gladly create a PR to fix the issue by just excluding the CSS from the legacy bundle (as it is still loaded normally using <link rel="stylesheet" src="./assets/.."> unrelated to module/legacy).

I've fixed this by creating a manual chunk for each CSS file I have. This allows me the have more than one stylesheet while also omitting all the CSS in my legacy chunks. It will however generate an extra JS file with just the CSS. But those can just be ignored.

How did you "ignore" the files? They are still referenced by System.import(..) in the legacy build, did you find a way to remove it from there?

This is how we managed to remove unecessary inlined styles when Vite emited those same styles as separate file.
Following plugin call will process only chunks inside entry-points directory ending with .scss:
function removeLegacyStyleInject({ include }) {
  let config;
  return {
    configResolved(_config) {
      config = _config;
    },
    async renderChunk(code, chunk) {
      if (
        code.includes("__vite_style__") &&
        include(chunk)
      ) {
        const t = babel.types;
        const result = await babel.transformAsync(code, {
          sourceMaps: config.build.sourcemap,
          plugins: [
            {
              visitor: {
                Identifier(path) {
                  if (path.node.name.includes("__vite_style__")) {
                    const found = path.findParent((path) => {
                      return (
                        path.isVariableDeclaration() ||
                        path.isExpressionStatement()
                      );
                    });
                    if (found) {
                      found.remove();
                    }
                  }
                  if (path.node.name.includes("exports")) {
                    const found = path.findParent((path) => {
                      const args = path.get("arguments");
                      return (
                        path.isCallExpression() &&
                        path.get("callee").node?.name === "exports" &&
                        args.length === 2 &&
                        args[1].isStringLiteral()
                      );
                    });
                    if (found) {
                      found
                        .get("arguments")[1]
                        .replaceWith(t.stringLiteral(""));
                    }
                  }
                },
              },
            },
          ],
        });
        return { code: result.code, map: result.map };
      }
      return null;
    },
    enforce: "post",
    apply: "build",
  };
}

// Add this as Vite plugin
removeLegacyStyleInject({
  include: (chunk) => {
    return (
      chunk.facadeModuleId?.includes("/entry-points/") &&
      chunk.facadeModuleId?.includes(".scss")
    )
  }
})

I don't think this breaks anything behavior wise, but it surely can be improved.

it does! I am using the legacy plugin with renderModernChunks: false and it is noticeable when user open my app that first a white screen appears quickly for some seconds then the css is loaded by javascript, I am using vite to create and package webxdc.org apps and size is constrained so I can't afford the duplicate data

Also getting bit by this. We're trying to use the plugin in an application where a traditional (Java) backend renders the HTML and generates script/link tags manually by reading the manifest to know which static CSS/JS imports are used by a given entrypoint (we don't require modern browser feature support and don't ship ES Modules in production). Due to this behavior, I have to choose between shipping JS that's compatible with our supported browser list or splitting CSS into its own set of chunks. We want to do both, which is possible in Webpack via separate loader chains for scripts/styles, but not via this plugin currently.

Has this issue been forgotten? It seems like it hasn't been optimized for a long time.

any update?


Document how to use persistent connections

Fixes #74

Hi @timgraham will this also solve issues like the token authentication token expiration issue?
I am having an issue with my django connection expiring after 4 hours.

I'm not a Snowflake expert, but according to https://community.snowflake.com/s/article/Authentication-token-has-expired-The-user-must-authenticate-again, setting client_session_keep_alive might be the solution. Let me know if it works.

Yes I think this works thank you.
On Tue, 5 Dec 2023, 18:52 Tim Graham, @.***> wrote:

I'm not a Snowflake expert, but according to
https://community.snowflake.com/s/article/Authentication-token-has-expired-The-user-must-authenticate-again,
setting client_session_keep_alive might be the solution. Let me know if
it works.
—
Reply to this email directly, view it on GitHub
https://github.com/Snowflake-Labs/django-snowflake/pull/78#issuecomment-1841426481,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFIQGII73UKRAWQRESB4DI3YH5UQNAVCNFSM6AAAAABAGWR7S6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBRGQZDMNBYGE
.
You are receiving this because you commented.Message ID:
@.***>


Add support for sessionToken

I use this library on ec2 using instance roles. AWS creates temporary
credentials in this case which require a sessionToken. I modified this
library to allow an optional sessionToken.
I also changed the default Vertx.vertx() creation to not use a static
initializer. This was causing multiple vertx instances to be created when
used in an existing vertx project.

Thanks for doing this. The PR looks good to me (sorry for the delay!).


Test the Auth Samples in Cloud Build

The Auth Library has a few handwritten samples (https://github.com/googleapis/google-auth-library-java/tree/main/samples/snippets) that should be tested in the CI. We should ensure that these samples (which are published to our docs) work with the latest auth code changes.

Samples to test: AuthenticateImplicitWithAdc.java, IdTokenFromImpersonatedCredentials.java, and AuthenticateImplicitWithAdc.java. The other samples do not need to be tested and can continue to live in the repo.


Invert unary ops

Fixes #201
I added some test cases in the well_tested test crate, but I feel like I should add some test cases for a few unviable mutations (e.g. !1.0, let x: u32 = -1). I wasn't sure where exactly I should put these, hence the draft PR.
The only existing place I saw asserting unviable cases were for struct_with_no_default. Should I create a new crate under testdata/ for unviable unary operators?

Fixes #201
I added some test cases in the well_tested test crate, but I feel like I should add some test cases for a few unviable mutations (e.g. !1.0, let x: u32 = -1). I wasn't sure where exactly I should put these, hence the draft PR.
The only existing place I saw asserting unviable cases were for struct_with_no_default. Should I create a new crate under testdata/ for unviable unary operators?

I don't think we need to add a test that !1.0 does not compile; that's more like an assertion about the behavior of rustc.
There are tests, you probably saw, that just check what mutants are generated, and maybe that's enough to say that some expected but unviable mutants are generated...
I'll have a look at your test changes and maybe it will be more clear to me.

Looks like I tripped up the spellchecker...
It's not really a spelling error or typo, but I'll change it to something else.

It looks like at least the delete ! case gets some good exercise in cargo-mutants itself in e.g. https://github.com/sourcefrog/cargo-mutants/actions/runs/8755264639/job/24029345649?pr=340

This looks good to me: flip it to 'ready to review' if you think it's ready.
Please also add to NEWS.md something like:

New: Generate mutations that delete the ! and - unary operators.

Done. I squashed the commits a bit.


various cross and gobject-introspection fixes

remove unnecessary preInstall
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Can we now start setting strictDeps on these too or do you want to defer that?

Can we now start setting strictDeps on these too or do you want to defer that?

lets do it in a separate pr
i use a command like this to generate the list of attrs and then i input that in to diffing
git diff --name-only HEAD HEAD~6 | rev | cut -d '/' -f 2 | rev > attrlist

draft because im still working on this

Can we set strictDeps to prevent regressions?

First fix then https://github.com/NixOS/nixpkgs/pull/177538#issuecomment-1154264286

Many meson projects are looking for gir, vapi, and gtk-doc wrong
See https://gitlab.gnome.org/GNOME/libgudev/-/merge_requests/27 for how to fix it

Btw, haven't tested building this, might do that but I don't have that much time right now. We'll see.

list of files in which strictDeps will be enabled in separate PRs

Yes, please. This PR is getting quite big.

Hey Artturin, can we get this in soon rather than piling up stuff? I don't think it's very convenient to keep adding things, we can always iterate on this later on, right?
Especially the more leafy fixes are fine to add later, IMO.
Also cc @Ericson2314 who may be interested in this.

Modemmanager (a dep of networkmanager) should be fixed before merge
I'll do it tomorrow as I was on vacation for 3 days

Also strictDeps gobject-introspection native will be broken due to not propagating itself to buildInputs while in nativeBuildInputs when not specified in buildInputs

reverted the propagation
original commits can be found in https://github.com/Artturin/nixpkgs/tree/fixcross3-backup

this flake built
{
  description = "cross-compile the sd-image-aarch64 on x86_64-linux to aarch64-multiplatform";
  inputs = {
    #nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
    nixpkgs.url = "/home/artturin/nixgits/my-nixpkgs/.worktree/1";
  };

  outputs = { self, nixpkgs }: {

    nixosConfigurations.cross-vm = nixpkgs.lib.nixosSystem {
      system = "x86_64-linux";
      modules = [
        ({ pkgs, lib, modulesPath, ... }: {
          nixpkgs = {
            crossSystem = lib.systems.examples.aarch64-multiplatform;
          };

          imports = [ (modulesPath + "/installer/sd-card/sd-image-aarch64.nix") ];

          users.mutableUsers = false;
          users.users.root = {
            password = "root";
          };
          users.users.user = {
            password = "user";
            isNormalUser = true;
            extraGroups = [ "wheel" ];
          };
          system.stateVersion = "22.05";
        })
      ];
    };

    packages.x86_64-linux.default = self.nixosConfigurations.cross-vm.config.system.build.sdImage;
    packages.x86_64-linux.vm = self.nixosConfigurations.cross-vm.config.system.build.vm;
    apps.x86_64-linux.vm = {
      type = "app";
      program = "${self.defaultPackage.x86_64-linux}/bin/run-nixos-vm-cross";
    };
  };
}

Bisect claims that gtk2 broke after a83d2f7c918a5badab204d57d8620adb926e618b gobject-introspection: cross improvements:
$ nix build -f. gtk2 -L
...
(lost logs will update in a ~hour)

gtk+> make[4]: *** No rule to make target 'g-ir-scanner', needed by 'Gtk-2.0.gir'.  Stop.

fixed in https://github.com/NixOS/nixpkgs/pull/181413

Bisect claims 10362d728084d8810f6af2f8588b172e092b01e6 librdf_raptor2: 2.0.15 -> unstable-2022-06-06 boroke a bunch of packages in staging-next. All have the same symptom: underlinked liblrdf.so library is not usable by it's final depends:
Broken packages are non, tony, rascal, hydrogen, guitarix. Example failure:
$ nix build -f. non -L
...
non-unstable> /nix/store/ydvvnn6mi99kyp9an1gnrcga1dr5v5x0-binutils-2.38/bin/ld: /nix/store/1kkgkg3irmk78pk6c96154fns1k5133g-lrdf-0.6.1/lib/liblrdf.so: undefined reference to `xsltNewSecurityPrefs'
non-unstable> /nix/store/ydvvnn6mi99kyp9an1gnrcga1dr5v5x0-binutils-2.38/bin/ld: /nix/store/1kkgkg3irmk78pk6c96154fns1k5133g-lrdf-0.6.1/lib/liblrdf.so: undefined reference to `xmlXPathNewContext'

I think lrdf library is linked incorrectly and is missing some xml library.
The simplest way to trigger the bug earlier is to add an LDFLAGS = "-Wl,--no-undefined" hack locally:
$ nix build --impure --expr 'with import ./.{}; lrdf.overrideAttrs (oa: { LDFLAGS = "-Wl,--no-undefined"; })' -L
...
lrdf> libtool: link: gcc -shared  -fPIC -DPIC  .libs/lrdf.o .libs/lrdf_multi.o .libs/md5.o   -L/nix/store/28xxhxqb97j48yj4ivvl0c6kih9l2r52-raptor2-unstable-2022-06-06/lib -lraptor2  -g -g -O2 -g -O2 -Wl,--no-undefined   -Wl,-soname -Wl,liblrdf.so.2 -o .libs/liblrdf.so.2.0.0
lrdf> /nix/store/ydvvnn6mi99kyp9an1gnrcga1dr5v5x0-binutils-2.38/bin/ld: /nix/store/28xxhxqb97j48yj4ivvl0c6kih9l2r52-raptor2-unstable-2022-06-06/lib/libraptor2.a(raptor_sax2.c.o): in function `raptor_sax2_parse_chunk':
lrdf> (.text+0x511): undefined reference to `xmlParseChunk'
lrdf> /nix/store/ydvvnn6mi99kyp9an1gnrcga1dr5v5x0-binutils-2.38/bin/ld: (.text+0x55d): undefined reference to `xmlCreatePushParserCtxt'
lrdf> /nix/store/ydvvnn6mi99kyp9an1gnrcga1dr5v5x0-binutils-2.38/bin/ld: (.text+0x589): undefined reference to `xmlCtxtUseOptions'

Bisect claims 10362d7 librdf_raptor2: 2.0.15 -> unstable-2022-06-06 boroke a bunch of packages in staging-next. All have the same symptom: underlinked liblrdf.so library is not usable by it's final depends:

I think lrdf library is linked incorrectly and is missing some xml library.

Possible fix (or workaround) is to enable shared libs by default. Proposed as: https://github.com/NixOS/nixpkgs/pull/182727


Question: does it impact performance for performance critical applications?

Hi,
Planning to use this for a CPU intensive application with lots of function calls and that needs to run at 60fps without stuttering.
Can you let me know if using this library would impact performance?
Thank you!

Yes. I would not recommend this library.


fix spell error

Thanks again, same as in #348 though, the changes need to me made in electron/electron 👍


[ANALYSIS] Area of Influence numeric inputs parameters improvement

edit: updated numbers based on new numbers given in #8166
By Distance (buffer)
-> m: min: 10, max: 1500, step: 1
-> km&mi: min: 1, max: 5, step: 0.5
new values:

m (10-1000)
km (0.5-100)
mi (0.5-100)

By Time (trade-area)
-> walking: min: 60s, max: 3600, step: 1
-> driving: min: 60s, max: 14400, step: 10
On the future we should think how to change the unit when reaching high values

Not "easy" as in "trivial", since the backbone forms we're using doesn't easily allow to change the schema (and its validators/min/max restrictions) dynamically, whoever will work on this need to look into this.

prioritize since this is getting important with the demos

ok, I've bumped it up the pending list

From #8870 by @AbelVM:

Allow negative values for buffering (areas of influence).
In some cases you need that kind of analysis. v.G.: find the people living close to the coast

@saleiva, @rochoa would this work? What should be the range then?

I'd not add that for the time being, We might want to add a separate analysis
for that :)
On Jul 14 2016, at 4:00 pm, Nicklas Gummesson<EMAIL_ADDRESS>wrote:

From #8870 by
@AbelVM:

Allow negative values for buffering (areas of influence).
In some cases you need that kind of analysis. v.G.: find the people living
close to the coast

@saleiva, @rochoa
would this work? What should be the range then?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on
GitHub,
or mute the
thread.


Measure and report time from method to updated DDP frames for method calls

If I'm understanding the Kadira source correctly, the current Response Time reported for Meteor method calls is measuring elapsed time from method received to result sent DDP frames
https://github.com/meteorhacks/kadira/blob/59b1b27035ad4a2ad5a911fad37ec8eb8b7aed40/lib/hijack/wrap_session.js#L99
https://github.com/meteor/meteor/blob/devel/packages/ddp/DDP.md#procedure-3
I would like to also be able to see the time from method to updated.  Some of my methods return result quite quickly, but the side effects they cause in turn cause a much larger delay before updated is sent.  It would help us understand the complete view of method behavior to have both of these events measured and visualized on the same chart.  Right now we're not getting the complete picture.
Thanks for your consideration; I love Kadira.

@egoldblum That's a good suggestion.


Missing CoC and so

@danielgruesso kindly add it here also as in https://github.com/coti-io/coti-sdk-typescript-examples/pull/8

@gmesika-coti see https://github.com/coti-io/coti-sdk-python-examples/pull/11


feat!: Update S3 module to v3.6.1 and switch to resource aws_s3_object

Description

Updated module terraform-aws-s3-bucket to v3.6.1 to remove the warnings about deprecated attributes.
Switch from resource aws_s3_bucket_object to aws_s3_object to remove the warnings about deprecated arguments.

Motivation and Context
We got the following warnings during deploying the Datadog log forwarder:
╷
│ Warning: Deprecated attribute
│
│   on .terraform/modules/datadog_integration.this_s3_bucket/main.tf line 34, in resource "aws_s3_bucket" "this":
│   34:       acceleration_status,
│
│ The attribute "acceleration_status" is deprecated. Refer to the provider
│ documentation for details.
│
│ (and 4 more similar warnings elsewhere)
╵
╷
│ Warning: Argument is deprecated
│
│   with module.datadog_integration.aws_s3_bucket_object.this[0],
│   on .terraform/modules/datadog_integration/modules/log_forwarder/main.tf line 134, in resource "aws_s3_bucket_object" "this":
│  134:   bucket = var.create_bucket ? module.this_s3_bucket.s3_bucket_id : var.bucket_name
│
│ Use the aws_s3_object resource instead
│
│ (and one more similar warning elsewhere)
╵

and also see Issue: https://github.com/terraform-aws-modules/terraform-aws-datadog-forwarders/issues/27
Breaking Changes

Upgrade the S3 module to v3.3.1 and newer requires minimum v4.9 of the AWS provider
How Has This Been Tested?

[x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[x] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

This PR is included in version 5.0.0 :tada:


New Sonoff device with firmware 3.3.1 not recognized  by DIY tool

My older sonoff mini devices were version 3.3.0 and I could flash them with tasmota without any issue.
Today I received some new sonoff mini devices.
They have a firmware 3.3.1 out of the box.
They are not recognized by the DIY tool.
I can connect with the eWeLink software, but after I put the jumper and try to connect with the diy tool,the device is not recognized.
Does the app not support version 3.3.1?

Check to see if you have mDNS on your system.  That's what eWelink uses to find you mini.  I don't have DNS, and therefore I have about 10 Mini's that are bricked.


Fatal Exception: NSInternalInconsistencyException

Open YPImagePicker. Library mode;
Switch to an another app;
Save some image to the library.
Switch back to the app. Crash!
@s4cha

Invalid update: invalid number of items in section 0. The number of items contained in an existing section after the update (209) must be equal to the number of items contained in that section before the update (209), plus or minus the number of items inserted or deleted from that section (1 inserted, 0 deleted) and plus or minus the number of items moved into or out of that section (0 moved in, 0 moved out).

Fatal Exception: NSInternalInconsistencyException
0  CoreFoundation                 0x181343164 __exceptionPreprocess
1  libobjc.A.dylib                0x18058c528 objc_exception_throw
2  CoreFoundation                 0x181343038 +[NSException raise:format:]
3  Foundation                     0x181cdd7f4 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:]
4  UIKit                          0x18b399760 -[UICollectionView _endItemAnimationsWithInvalidationContext:tentativelyForReordering:animator:]
5  UIKit                          0x18b39d250 -[UICollectionView _endUpdatesWithInvalidationContext:tentativelyForReordering:animator:]
6  UIKit                          0x18b39d534 -[UICollectionView _performBatchUpdates:completion:invalidationContext:tentativelyForReordering:animator:]
7  UIKit                          0x18b39d390 -[UICollectionView _performBatchUpdates:completion:invalidationContext:tentativelyForReordering:]
8  UIKit                          0x18b39d314 -[UICollectionView _performBatchUpdates:completion:invalidationContext:]
9  UIKit                          0x18aab921c -[UICollectionView performBatchUpdates:completion:]
10 YPImagePicker                  0x100d044f8 (Missing)
11 YPImagePicker                  0x100d0419c (Missing)
12 YPImagePicker                  0x100cf28c4 (Missing)
13 libdispatch.dylib              0x180cc2a54 _dispatch_call_block_and_release
14 libdispatch.dylib              0x180cc2a14 _dispatch_client_callout
15 libdispatch.dylib              0x180ccf698 _dispatch_main_queue_callback_4CF$VARIANT$mp
16 CoreFoundation                 0x1812eb344 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__
17 CoreFoundation                 0x1812e8f20 __CFRunLoopRun
18 CoreFoundation                 0x181208c58 CFRunLoopRunSpecific
19 GraphicsServices               0x1830b4f84 GSEventRunModal
20 UIKit                          0x18a9615c4 UIApplicationMain

@Ewg777 nice catch, I will take a look tomorrow 👍

@Ewg777 This should be fixed in 2.7.0
https://github.com/Yummypets/YPImagePicker/releases/tag/2.7.0
Thanks for taking the time to report the issue 👍


Script extended from other script doesn´t show ENUM members in autocomplete

Operating system or device, Godot version, GPU Model and driver (if graphics related):
Godot 3 beta 1 and Godot 2.1.4 win 7
Issue description:

Extending a script from other and trying to access a "enum member" with:  enum_name.CONST_NAME works as expected, but autocomplete doesn´t show the constants inside the enum if the enum was declared in the base script.

Still relevant in master. In fact it seems autocomplete for enums even in the same file is broken.

Works in 3.2


[docs] Remove alias from configuration options

alias options should now be configured in vite.config.js, this makes me wonder though if we should have a short section about the vite.config.js file ?
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[ ] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[ ] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

nvm, it changed from kit.vite.resolve.alias to kit.alias which is why it was not working :)


Traces: Sample JSON doesn't appear to be valid.

The sample JSON file on this page is not validating properly.

For page:
https://opentelemetry.io/docs/concepts/signals/traces/

End of file expected is to be expected. Perhaps this should be split into three separate code blocks.

I don't think this is intended to be proper JSON, although one option would be to put those into a JSON array. @cartermp wdyt?

My immediate response was to copy the whole thing and stick it into my VSCode so I could minimize parts and see how things related to each other.
This is why I think it should probably be valid JSON and you should probably have one span per code block. Just my 2c.

I decided to go with splitting up the blobs and rephrasing a few things. Thanks for the report!

Excellent! Thanks.


[ci/cd] Hash-pin GitHub Actions, set up dependabot to keep them updated

Fixes #34929.
This PR hash-pins all Actions used in workflows and sets up dependabot to keep them up-to-date.
Dependabot will send at most one PR per month. That PR will update the hashes and version comments of all Actions with new versions.
I also suggest you enable Dependabot Security Updates in the repo's Code security & analysis settings (if you haven't already). This will make Dependabot send a PR as soon as a dependency is found to have a vulnerability.

@XuanWang-Amos neat, we should do the same to the migrated psm-interop workflow: https://github.com/grpc/psm-interop/blob/main/.github/workflows/psm-interop.yaml


[Fix - build error]Set the working version of Gemma.cpp Git tag

since the dependencies are managed within Cmake , remove gitmodules - makes the repo simple
the master branch fails when using the latest commit in the parent Gemma.cpp origin/main, this is because of the updated libgemma interface. This PR sets the Gemma.cpp git tag to the first commit.
Note to the maintainer: please consider updating the commit hash to a working version that you might have locally.
The actual fix would be update the bindings to support the latest libgemma interface. This commit is intended to support the current version.

Hi @pagakarthik, thank you for contributing to this project. Your work seems good to me, we will make the release more carefully for the next time.

the gemma-cpp-python still needs a lot of improvements. If you have any suggestions for us, feel free to raise your comments and suggestions. We would like to get all the feedback and make the project better.


RTD build failing

Looks like our RTD builds have been failing for the last 3 days.
The HTML pages are in _build/html.
/home/docs/checkouts/readthedocs.org/user_builds/xray/conda/latest/lib/python3.7/site-packages/sphinx_rtd_theme/search.html:20: RemovedInSphinx30Warning: To modify script_files in the theme is deprecated. Please insert a <script> tag directly in your theme instead.
  {{ super() }}

Traceback (most recent call last):
  File "/home/docs/checkouts/readthedocs.org/user_builds/xray/conda/latest/lib/python3.7/site-packages/sphinx/cmd/build.py", line 284, in build_main
    app.build(args.force_all, filenames)
  File "/home/docs/checkouts/readthedocs.org/user_builds/xray/conda/latest/lib/python3.7/site-packages/sphinx/application.py", line 380, in build
    self.events.emit('build-finished', None)
  File "/home/docs/checkouts/readthedocs.org/user_builds/xray/conda/latest/lib/python3.7/site-packages/sphinx/events.py", line 103, in emit
    results.append(callback(self.app, *args))
  File "/home/docs/checkouts/readthedocs.org/user_builds/xray/conda/latest/lib/python3.7/site-packages/sphinx_gallery/gen_gallery.py", line 313, in sumarize_failing_examples
    "\n" + "-" * 79)
ValueError: Here is a summary of the problems encountered when running the examples

Examples expected to fail, but not failing:
Please remove these examples from
sphinx_gallery_conf['expected_failing_examples']
/home/docs/checkouts/readthedocs.org/user_builds/xray/checkouts/latest/doc/gallery/plot_rasterio.pyin your conf.py file
/home/docs/checkouts/readthedocs.org/user_builds/xray/checkouts/latest/doc/gallery/plot_rasterio_rgb.py
-------------------------------------------------------------------------------

Exception occurred:
  File "/home/docs/checkouts/readthedocs.org/user_builds/xray/conda/latest/lib/python3.7/site-packages/sphinx_gallery/gen_gallery.py", line 313, in sumarize_failing_examples
    "\n" + "-" * 79)
ValueError: Here is a summary of the problems encountered when running the examples

Examples expected to fail, but not failing:
Please remove these examples from
sphinx_gallery_conf['expected_failing_examples']
/home/docs/checkouts/readthedocs.org/user_builds/xray/checkouts/latest/doc/gallery/plot_rasterio.pyin your conf.py file
/home/docs/checkouts/readthedocs.org/user_builds/xray/checkouts/latest/doc/gallery/plot_rasterio_rgb.py
-------------------------------------------------------------------------------

More information here: https://sphinx-gallery.github.io/configuration.html#don-t-fail-the-build-on-exit

Has anyone with access tried just wiping the env? https://docs.readthedocs.io/en/stable/guides/wipe-environment.html
Specifically, when I was testing locally my rasterio was not importing, but at some point in the past, had run successfully. I was able to fix by removing the auto_gallery dir from the docs dir.

So it looks more like a conda channel mixing problem to me now. Perhaps just bumping rasterio to 1.0.24?

Thanks @DocOtak, how would you feel about bumping rasterio in a PR? Would be great if we can get this working again.

@max-sixty I made a PR which bumps rasterio.
Something else to consider is enabling channel_priority strict in the conda environment. When I had enabled that in local testing, the conda solver was unable to create the requested environment. It seemed the requested rasterio version was no longer on conda-forge (though maybe under the cf201901 label?). Though if I recall, there was also a mismatch between the requested pandas and python versions when strict was enabled.
It seems the trade off is where you want the failure to occur, either in making the environment in conda, or when some package stops working.

Seems the docs are still failing to build, except this time it is being killed due to too much resource consumption.

All green! and the docstrings look great!
Thanks @DocOtak :clap: :clap:

Thanks a lot @DocOtak !

Thanks indeed!


Script cancelling

I have some automations and scripts set up to turn on the lights when motion is detected. However, something is causing the script with the delay to skip the delay and execute the remaining commands in the sequence, when it is canceled. Here's the relevant configuration:
When motion is detected and the lights are off:
alias: Bedroom Motion - Lights Off
trigger:
  platform: state
  entity_id: sensor.bedroom_motion
  state: 'yes'
condition:
  platform: state
  entity_id: light.bedroom
  state: 'off'
action:
  service: homeassistant.turn_on
  entity_id: script.bedroom_start_timer

When motion is detected and the lights are on:
alias: Bedroom Motion - Lights Already On
trigger:
  platform: state
  entity_id: sensor.bedroom_motion
  state: 'yes'
condition:
  platform: state
  entity_id: light.bedroom
  state: 'on'
action:
  service: homeassistant.turn_on
  entity_id: script.bedroom_restart_timer

Start the timer (turn on the lights first):
sequence:
- execute_service: light.turn_on
  service_data:
    entity_id: light.bedroom
- execute_service: script.turn_on
  service_data:
    entity_id: script.bedroom_timer

Restart the timer:
sequence:
- execute_service: script.turn_off
  service_data:
    entity_id: script.bedroom_timer
- execute_service: script.turn_on
  service_data:
    entity_id: script.bedroom_timer

And the timer itself:
sequence:
- delay:
    minutes: 30
- execute_service: light.turn_off
  service_data:
    entity: light.bedroom

Now, here's the relevant logs. First is it working correctly. This is the first time everything is triggered upon HA restart:
# the lights are off and I trip the motion sensor.
15-12-05 11:14:39 INFO (Thread-6) [homeassistant.components.automation] Executing Bedroom Motion - Lights Off
15-12-05 11:14:39 INFO (Thread-7) [homeassistant.components.script] Executing script bedroom_start_timer
15-12-05 11:14:39 INFO (Thread-7) [homeassistant.components.script] Executing script bedroom_start_timer step light.turn_on
15-12-05 11:14:39 INFO (Thread-7) [homeassistant.components.script] Executing script bedroom_start_timer step script.turn_on
15-12-05 11:14:39 INFO (Thread-19) [homeassistant.components.script] Executing script bedroom_timer

# the lights are on and I trip the motion sensor again, waiting about a minute.
15-12-05 11:15:41 INFO (Thread-24) [homeassistant.components.automation] Executing Bedroom Motion - Lights Already On
15-12-05 11:15:41 INFO (Thread-7) [homeassistant.components.script] Executing script bedroom_restart_timer
15-12-05 11:15:41 INFO (Thread-7) [homeassistant.components.script] Executing script bedroom_restart_timer step script.turn_off
15-12-05 11:15:41 INFO (Thread-7) [homeassistant.components.script] Executing script bedroom_restart_timer step script.turn_on
15-12-05 11:15:41 INFO (Thread-6) [homeassistant.components.script] Cancelled script bedroom_timer
15-12-05 11:15:41 INFO (Thread-22) [homeassistant.components.script] Executing script bedroom_timer

# 30 minutes later, with no further motion, the lights go off, as expected.
15-12-05 11:45:42 INFO (Thread-20) [homeassistant.components.script] Executing script bedroom_timer
15-12-05 11:45:42 INFO (Thread-20) [homeassistant.components.script] Executing script bedroom_timer step light.turn_off

Now here's where it breaks when I test it 5 minutes later:
# the lights are off and I trip the motion sensor (this part seems ok):
15-12-05 11:50:51 INFO (Thread-19) [homeassistant.components.automation] Executing Bedroom Motion - Lights Off
15-12-05 11:50:51 INFO (Thread-25) [homeassistant.components.script] Executing script bedroom_start_timer
15-12-05 11:50:51 INFO (Thread-25) [homeassistant.components.script] Executing script bedroom_start_timer step light.turn_on
15-12-05 11:50:51 INFO (Thread-25) [homeassistant.components.script] Executing script bedroom_start_timer step script.turn_on
15-12-05 11:50:51 INFO (Thread-4) [homeassistant.components.script] Executing script bedroom_timer

# 5 seconds later, I trip the motion sensor again, and instead of cancelling and then executing the timer, it accelerates through the delay and turns off the lights, then cancels the timer.
15-12-05 11:51:57 INFO (Thread-5) [homeassistant.components.automation] Executing Bedroom Motion - Lights Already On
15-12-05 11:51:57 INFO (Thread-13) [homeassistant.components.script] Executing script bedroom_restart_timer
15-12-05 11:51:57 INFO (Thread-13) [homeassistant.components.script] Executing script bedroom_restart_timer step script.turn_off
15-12-05 11:51:57 INFO (Thread-13) [homeassistant.components.script] Executing script bedroom_restart_timer step script.turn_on
15-12-05 11:51:57 INFO (Thread-22) [homeassistant.components.script] Executing script bedroom_timer
15-12-05 11:51:57 INFO (Thread-22) [homeassistant.components.script] Executing script bedroom_timer step light.turn_off
15-12-05 11:51:57 INFO (Thread-4) [homeassistant.components.script] Cancelled script bedroom_timer

Just looking at your code without the means of testing it I can see anything wrong.
Have you tried adapting the example code from the cookbook to see if the results are the same?
Quick cut and paste with your variables inserted should probably work.
https://gist.github.com/Landrash/7d699724200ac2eefb65

If a script is in a delay and turn_on is called, it will continue execution. (relevant code).
The cookbook example is indeed correct.

Yes, but I'm calling turn_off first.

Ah I see the problem, scripts are not waiting for services to finish but fire them all. Being threaded, it might be that turn_on is processed earlier. Fixed this in b2ae3655587c5c28d73eaba41cf59e94c7708a7b - let me know if this resolves it.

So far so good. But it is hard to be sure with this kind of thing. I'll run it for a few days to be sure, then close this ...

I'm still having some problems. Take a look at the following log:
# I trigger the motion sensor
15-12-07 20:45:31 INFO (Thread-4) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.bedroom_motion, old_state=<state sensor.bedroom_motion=no; friendly_name=Motion, icon=mdi:walk @ 20:43:36 07-12-2015>, new_state=<state sensor.bedroom_motion=yes; friendly_name=Motion, icon=mdi:walk @ 20:45:31 07-12-2015>>

# lights are off, automation (number 1) correctly triggered
15-12-07 20:45:31 INFO (Thread-4) [homeassistant.components.automation] Executing Bathroom Motion - Lights Off

# automation (number 2) for when the lights are already on is triggered is run as well (why does this happen?)
15-12-07 20:45:31 INFO (Thread-9) [homeassistant.components.automation] Executing Bathroom Motion - Lights Already On

# automation number two runs first, with the restart script (shouldn't scripts run in the order they were triggered?)
15-12-07 20:45:31 INFO (Thread-21) [homeassistant.components.script] Executing script bathroom_restart_timer
15-12-07 20:45:31 INFO (Thread-21) [homeassistant.components.script] Executing script bathroom_restart_timer step script.turn_off
15-12-07 20:45:31 INFO (Thread-23) [homeassistant.components.script] Cancelled script bathroom_timer

# now automation number one runs, which starts the timer (which is already running due to above)
15-12-07 20:45:31 INFO (Thread-18) [homeassistant.components.script] Executing script bathroom_start_timer
15-12-07 20:45:31 INFO (Thread-18) [homeassistant.components.script] Executing script bathroom_start_timer step light.turn_on

# ... and turns off the lights immediately (not the desired outcome ...)
15-12-07 20:45:31 INFO (Thread-8) [homeassistant.components.script] Executing script bathroom_timer
15-12-07 20:45:31 INFO (Thread-24) [homeassistant.components.script] Executing script bathroom_timer step light.turn_off

This seems to be a separate, but related problem. The automations and scripts involved are nearly the same as above; just with an extra condition and different entity naming.

This seems to be fixed per my testing.


axis name becomes undefined after illegal transform of pseudo-var

Reported by Ansley B Manke on 3 Sep 2003 16:40 UTC
yes? use coads_climatology
yes? list t[gt=time,l=@shf]
**ERROR: command syntax: cannot transform pseudo-variables: L=@SHF
use DEFINE VARIABLE (e.g. DEF VAR ii=i) and transform that
yes? sh grid sst
GRID GSQ1
name       axis              # pts   start                end
COADSX    LONGITUDE          180mr   21E                  19E(379)
COADSY    LATITUDE            90 r   89S                  89N
normal    Z
%%        TIME                12mr   16-JAN      06:00    16-DEC      01:20
This occurs after v5.0 and before v5.20.  Does it have to do
with the changes to make NetCDF grids dynamic?
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/599

Comment by<EMAIL_ADDRESS>on 10 Nov 2003 17:32 UTC
reassign to Ansley

Comment by<EMAIL_ADDRESS>on 10 Nov 2003 17:57 UTC
The presence of a "%%" on an axis shown by SHOW GRID has in the past generally
meant that the axis was "deallocated" (incorrect behavior for the given
commands)
For a variable (as opposed to a pseudo-variable) "var[gt=TIME]" would create a
dynamic grid that "used" the axis "TIME" instead of its native T axis.  In doing
so it would "allocate" (bump up the use count of) the axis TIME.  If Ferret then
detected an error in the command it would deallocate the dynamic grid, which
would in turn decrement the use count on TIME back to its original value.
A first guess at the cause of the problem reported here: the use count on TIME
is getting decremented during the processing of the Ferret error by one more
than it was incremented.

Comment by<EMAIL_ADDRESS>on 16 May 2005 16:44 UTC
Removing Joe Mclean from the CC list after Joe's departure.


How to manage version for a API family release

Problem description
In the context of the Device Location API family we have several API (Yaml). One API for checking location, another for retrieving location and a third soon to be delivered for geofencing.
We wanted to manage release management at the family level as we have to provide consistency between the family.
Using numerical version for the family seems to us not a great idea as it will bring confusion - indeed, the Family in v0.2 will cover this API in v0.3, the other API in v0.2 and the third API in v0.1. Confusing right?
Perhaps have a name for a family version should be better but as this issue will come in several project we need to have a global common naming. Could the name of the family and then a release name using a word following alphabetical like Device Location family - Release Avocado, Device Location family - Release Banana, etc...
Expected action
Have a common agreement on API family release management
Additional context
Need to discuss if we manage this family stuff for one api family. I do not have clear idea on this as consistency is always good but not sure of the value of the family release in this case.

Another option is to label Releases using some date convention, e.g. Release 2023-09, 23.09...

I'm fine with using the date convention.... as long as we can clearly distinct yaml version from the family release version it works for me :)

@bigludo7 Do I understand this right, that you would like to change the current release number V0.1.0 to something like Device Location family -Release Avocado or Device Location family -Release 2023-09?

@shilpa-padgaonkar I'm not sure we have "Family" release number as of now.
I do not want to change the API version.
But as we have 'family' release we should have a way to identify them. A family release is a set of API (in a version) consistently aligned.  Using numerical version for family release will be confusing with API version. The proposal here is to use a name or a date to identify API family release.
For example:
Device Location API family - Release 2023-10 features;

Retrieve location in v0.1
Verify Location in v0.2

Device Location API family - Release 2024-01 features:

Retrieve location in v0.1
Verify Location in v0.3
Geofencing in v0.1

This is perhaps specific of the device location where we have several API and we have to consistently align them. We can quickly discuss this on next Commonalities meeting.

there is the same issue with the Edge Cloud API Family. Actually I see a value in using the Family name in the "release tag" for a branch (https://github.com/camaraproject/Commonalities/blob/main/documentation/Camara_Versioning_Guidelines.md). So the Release Tag can be "Family Name - vx.y.z" while inside the branch we have the different APIs with different versioning ("version" field in the YAML file).
I don't see any need to overcomplicate the tag using the the term "release" or adding the year.
For example:
"Release tag" for the branch:  "Edge Cloud - v1.0.0"
the branch includes:
TrafficInfluence.yaml: version: 1.1.4   (this is not a tag, this is written inside the yaml file)
SimpleEdgeDiscovery.yaml:  version: 1.0.2

Thanks @FabrizioMoggio for pointing this document.
So we have a guideline and probably we have to stick to it.
I'l still uncomfortable about using number version for Family as it is confusing with the API version themselves but  if I'm the only one I have to live with that ;)

To me it is also confusing to see v1.x, v2.x for Releases containing APIs in v0.x. Maybe in EdgeCloud could makes sense if the APIs are already v1, etc. In other WGs, that gives the impression to be major releases, while they are really some intermediate milestones towards first major Release. About using the term "Release" as part of the tag, I don't mind using another convention.

In the Ericsson view, using semver for groups of API endpoints is not meaningful and may even be misleading (since semver doesn't really give any further information of what has changed). As proposed above, a date convention, or a quarter+year, or even simply a sequential numbering are enough without tying any specific semantics to the "group version"  and instead just reasoning about it as cadence.
Added this comment here for completeness and the same has been mentioned in the "consolidation issue" https://github.com/camaraproject/Commonalities/issues/67#issuecomment-1790210646.


Correcting error 405 when hosting on linux distro

I'm running into problem of server returning "405 Method now allowed" when trying to push nupgk to server. I there any way to correct this on linux hosted server? So far typical suggestions like in Issue #195 of adding more configuration in web.config file have not helped so far.
Server running on debian stretch. Tried both docker version and just running with dotnet BaGet.dll.
Any suggestions?

Are you using the default configuration (SQLite database and local filesystem)? I'm not sure how to best debug this... Could you try raising the LogLevel to Debug on your appsettings.json file. Please attach the logs to this issue (make sure there's no sensitive information in your logs!)
Also, have you tried attaching a debugger and stepping through the code? You'll want to set a breakpoint here: https://github.com/loic-sharma/BaGet/blob/master/src/BaGet.Core.Server/Controllers/PackagePublishController.cs#L40

HowTo Tracing
assuming that you have access to the console and that you are using a modified version of the original "appsettings.json", you can modify the following section:
    "Console": {
      "LogLevel": {
        "Default": "Warning",
        "Microsoft.AspNetCore.Routing": "Trace"
      }
    }

The last settings enables full TRACE but onlY for the routing engine.
if you change the "default" setting into
"Default": "Trace",
then you get the full blown aspnet Core Trace.....
You can do the same WITHOUT changing appsettings.json
by setting some environment variable (used specially on hosting environments like Azure AppService etc....
On Linux (VM or container) define a environment variable
Name=Logging__Console__LogLevel__Microsoft.AspNetCore.Routing
Value="Trace"
Important to know:

the name represents the Json hierarchy from appsettings.json
on linux you must use double underscores (!!!) "__" to separate Items, on Windows you can use ":"

Yes. I am using mostly default settings, only changed ApiKey and Storage path. And launched via "ASPNETCORE_URLS="http://*:5000" dotnet BaGet.dll" for now. Plan was to later on was to rely on nginx reverse proxying baget.
Log and settings attached below. Now sure if app startup part is required, but if needed will append to this reply.
Haven't tried to debug any deeper than looking for various solutions via google. Don't know if other approach for me would be any good as I'm not familiar with C# and I tinker in code only on automation tool level and some smaller apps.
appsetting.json
{
  "ApiKey": "derpderp",
  "PackageDeletionBehavior": "Unlist",
  "AllowPackageOverwrites": false,

  "Database": {
    "Type": "Sqlite",
    "ConnectionString": "Data Source=baget.db"
  },

  "Storage": {
    "Type": "FileSystem",
    "Path": "/home/krisjanis/packages"
  },

  "Search": {
    "Type": "Database"
  },

  "Mirror": {
    "Enabled": false,
    "PackageSource": "https://api.nuget.org/v3/index.json"
  },

  "Logging": {
    "IncludeScopes": false,
    "Debug": {
      "LogLevel": {
        "Default": "Debug"
      }
    },
    "Console": {
      "LogLevel": {
        "Default": "Debug",
        "Microsoft.AspNetCore.Routing": "Trace"
      }
    }
  }
}

web.config
<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <location path="." inheritInChildApplications="false">
    <system.webServer>
      <validation validateIntegratedModeConfiguration="false" />
      <modules runAllManagedModulesForAllRequests="true">
        <remove name="WebDAVModule" />
        <remove name="WebDAV" />
      </modules>
      <aspNetCore processPath="dotnet" arguments=".\BaGet.dll" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" />
    </system.webServer>
  </location>
</configuration>
<!--ProjectGuid: 284366CB-C68F-473E-908A-50A382616AE0-->

debug - response to put request.
info: Microsoft.AspNetCore.Hosting.Internal.WebHost[1]
      Request starting HTTP/1.1 PUT http://<IP_ADDRESS>:5000/v3/index.json multipart/form-data; boundary=---------------------------8d6ab9e664342d7 5413
dbug: Microsoft.AspNetCore.HostFiltering.HostFilteringMiddleware[0]
      Wildcard detected, all requests with hosts will be allowed.
trce: Microsoft.AspNetCore.HostFiltering.HostFilteringMiddleware[0]
      All hosts are allowed.
dbug: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[1]
      PUT requests are not supported
dbug: Microsoft.AspNetCore.Routing.Matching.DfaMatcher[1001]
      1 candidate(s) found for the request path '/v3/index.json'
dbug: Microsoft.AspNetCore.Routing.Matching.DfaMatcher[1005]
      Endpoint '405 HTTP Method Not Supported' with route pattern '(none)' is valid for the request path '/v3/index.json'
dbug: Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware[1]
      Request matched endpoint '405 HTTP Method Not Supported'
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
      Executing endpoint '405 HTTP Method Not Supported'
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
      Executed endpoint '405 HTTP Method Not Supported'
dbug: Microsoft.AspNetCore.Server.Kestrel[9]
      Connection id "0HLLBHMHQFNT2" completed keep alive response.
info: Microsoft.AspNetCore.Hosting.Internal.WebHost[2]
      Request finished in 64.7363ms 405
dbug: Microsoft.AspNetCore.Server.Kestrel[25]
      Connection id "0HLLBHMHQFNT2", Request id "0HLLBHMHQFNT2:00000001": started reading request body.
info: Microsoft.AspNetCore.Server.Kestrel[32]
      Connection id "0HLLBHMHQFNT2", Request id "0HLLBHMHQFNT2:00000001": the application completed without reading the entire request body.
dbug: Microsoft.AspNetCore.Server.Kestrel[26]
      Connection id "0HLLBHMHQFNT2", Request id "0HLLBHMHQFNT2:00000001": done reading request body.

i had only a few minutes today...but 2 ideas:
maybe the same problem like here:
https://stackoverflow.com/questions/16451183/405-method-not-allowed-in-nuget-push
OR:
the Method "Upload" inside the PackagePublishController has NO Http Attribute....
may be for some bug/implicit solution the "PUT" is not recognized ?
we should doublecheck is we must add a [HttpPut] attribute there....
BUT basically push on linux should be working, i was able to push on my demo instance (Azure Linux WebApp docker container) yesterday.....
syntax: nuget push  %nupkg% -source "https://bagetbasic.azurewebsites.net/v3/index.json"
Werner

Found my problem. Packet client for some reason when using apikey throws out this 405 error. Same thing if choco.exe (chocolatey nuget client) is used.
PS D:\nuget> .\paket.exe push --url "http://<IP_ADDRESS>:5000/v3/index.json" --api-key "derpderp" winbox.3.18.2.nupkg
Paket version 5.198.0
Pushing package winbox.3.18.2.nupkg to http://<IP_ADDRESS>:5000/v3/index.json - trial 1
Could not push winbox.3.18.2.nupkg: The remote server returned an error: (405) Method Not Allowed.
Pushing package winbox.3.18.2.nupkg to http://<IP_ADDRESS>:5000/v3/index.json - trial 2
Could not push winbox.3.18.2.nupkg: The remote server returned an error: (405) Method Not Allowed.
Pushing package winbox.3.18.2.nupkg to http://<IP_ADDRESS>:5000/v3/index.json - trial 3
Could not push winbox.3.18.2.nupkg: The remote server returned an error: (405) Method Not Allowed.
Pushing package winbox.3.18.2.nupkg to http://<IP_ADDRESS>:5000/v3/index.json - trial 4
Could not push winbox.3.18.2.nupkg: The remote server returned an error: (405) Method Not Allowed.
Pushing package winbox.3.18.2.nupkg to http://<IP_ADDRESS>:5000/v3/index.json - trial 5
Performance:
 - Runtime: 571 milliseconds
Paket failed with
-> WebException: The remote server returned an error: (405) Method Not Allowed.

PS D:\nuget> choco.exe push winbox.3.18.2.nupkg --source "http://<IP_ADDRESS>:5000/v3/index.json" --api-key="derpderp" --force
Chocolatey v0.10.11
Attempting to push winbox.3.18.2.nupkg to http://<IP_ADDRESS>:5000/v3/index.json
Failed to process request. 'Method Not Allowed'.
The remote server returned an error: (405) Method Not Allowed..

When I push from nuget.exe with no apikey or previously saved credentials all works fine.
I guess I was looking for problem in wrong direction previously.

Receiving the same error on Win10. No modifications to config.
❯ publish-module -Name PS-CoolModuleIMade -Repository TestBaGET -NuGetApiKey $apikey
Publish-PSArtifactUtility : Failed to publish module 'PS-CoolModuleIMade': 'Failed to process request. 'Method Not Allowed'.
The remote server returned an error: (405) Method Not Allowed..
'.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\<IP_ADDRESS>\PSModule.psm1:1227 char:17
+                 Publish-PSArtifactUtility -PSModuleInfo $moduleInfo `
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : FailedToPublishTheModule,Publish-PSArtifactUtility

It seems like Paket has some weird behavior where they do a PUT request on the service index (like api.nuget.org/v3/index.json. I need to dig deeper, but it looks like I'll need to file an issue on paket.

I've improved the documentation on the Upload page, please let me know what you think! See: https://github.com/loic-sharma/BaGet/pull/247

I'm having the same issue on my linux machine.
dotnet nuget push -s http://localhost:50561/v3/index.json  mypackage.1.0.0.nupkg Failed to process request. 'Method Not Allowed'.  The remote server returned an error: (405) Method Not Allowed.
I changed the logging level and this is what it shows
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]       Executing endpoint '405 HTTP Method Not Supported' info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]       Executed endpoint '405 HTTP Method Not Supported'
which I assume points to http://localhost:50561/api/v2/package and http://localhost:50561/api/v2/symbol.
During debuging I realized that it doesn't hit the breakpoint in PackagePublishController.Upload(CancellationToken).
Could (https://docs.microsoft.com/en-us/nuget/api/nuget-protocols) be the reason?

git clone source code ,  edit  PackagePublishController.cs file like:
[HttpPut]  //append attribute
public async Task BaGet.Web.PackagePublishController.Upload(...){...}

You can solve "(405) Method Not Allowed" error .


New reviewers: Luigi Mario Zuccarelli, Sherine Khoury

Luigi and Sherine are taking over the leadership and maintenance of the project, let's add them as new reviewers for the start.

/assign @dinhxuanvu
/assign @soltysh

/lgtm


Add introduction file for starting contributions to Mboalab community, also update Task0

This pull request adds a new file to the repository/directory that introduces myself to the open source community. Although I have not yet made any contributions, I am eager to start and this file serves as my first step towards getting involved.
In this file, I have shared some information about my background, skills, and interests, as well as my motivation for contributing to open source. I have also included my socials.
I hope this introduction will help me connect with others in the community and find opportunities to make meaningful contributions.

I’m adding a new commit which adds a list of 50 active global hospitals to the open-source project repository. The hospitals were researched based on the criteria of being general medical facilities with co-existing sub-units. Each hospital in the list includes its location, services offered, and a link to its official website.
The  research was conducted using a variety of sources including online directories of hospitals, government health agency websites, and international healthcare organizations' databases. All sources used are cited in the accompanying Task0 file.
As an Outreachy contributor, I am excited to have been able to contribute to this open-source project. I hope that this list of hospitals will be useful for linking up medical facilities around the world and improving global healthcare access.


package mod_tls for apache httpd

Project description
mod_tls provides a Rust implementation of the TLS stack for the popular Apache httpd server.
nixpkgs will be a great place to showcase this work so people can experiment and provide feedback to the ongoing development of mod_tls.
Metadata

homepage URL:  https://github.com/abetterinternet/mod_tls
source URL: https://github.com/abetterinternet/mod_tls
license: Apache 2.0
platforms: linux, (maybe darwin)

I initially created this in https://github.com/abetterinternet/mod_tls/issues/6.
I plan to use this issue for tracking a WIP PR to add it to nixpkgs.

I believe we need to package https://github.com/ctz/rustls first because mod_tls requires it.
I'm new to nix packaging but what I understand is that if your package depends on another source it would be best to add that to nixpkgs so you can easily consume it via buildInputs.


Can not use up arrow key to search the history in debug mode

when using ipython interpreter.
But using python interpreter does not have this issue.

This is a limitation of the IPython/Jupyter kernel architecture. At the moment we can't do anything about it, sorry.
We're aware of this problem and hopefully we could address within Spyder in a future release (not Spyder 3.0 for sure :-)


Add study features to broadcasts

Some features of the studies are interesting for people commenting on broadcast matches
such as the numbered arrows
And it is worth remembering that each round in the broadcast is a study

I've never watched a broadcast match. The problem with numbered arrows and other things is that there is a completely different mechanism working for playing game pages and analysis game pages. Much harder to do anything in playing games. There is also a "law" of lichess to not modify the playing part.
I understand you mean the spectators, not the players, but I don't know the details of these broadcasts. I will investigate.

I think you can explore the Word Cup part (since it's going on)
https://lichess.org/broadcast/fide-world-cup-2023-open-section/round-2-game-1/weZnNhIY
The board interface is like a study
For example, this round of the broadcast
https://lichess.org/broadcast/leca-chess-open-2023/round-3/DUSZfIpw
It represents this study
https://lichess.org/study/DUSZfIpw
Usually these games are not taking place within lichess and stockfish can be switched on
And I can even say
each round a pgn link is inserted as source with all games
and the organisers update that pgn whenever there is movement
also if the organiser asks for a delay the lichess can add it without problems.

Fixed in v2.0.41


Minor update due to recent changes in core API

Waiting for https://github.com/realm/realm-core/pull/881

https://github.com/realm/realm-core/pull/881 has now been merged.

this still needs to wait until the binding updates to a core release that includes those changes

Do we want to keep this PR open until a release of core is made @tgoyne? It's simple enough to warrant just closing this IMO. I'm tidying up our PRs and issues.


chore(package): update mocha to version 4.0.1

Codecov Report

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

@@           Coverage Diff           @@
##           master     #108   +/-   ##
=======================================
  Coverage   84.61%   84.61%
=======================================
  Files           1        1
  Lines          13       13
=======================================
  Hits           11       11
  Misses          2        2

Continue to review full report at Codecov.

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


olaris-server: init at 0.4.0

Description of changes
Fixes #114305
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1490

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 203710 run on x86_64-linux 1

1 package built:

olaris-server

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 203710 run on x86_64-linux 1

1 package built:

olaris-server

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1541


db:push script missing from drizzle and postgres configuration

Config File
{
"hasSrc": true,
"packages": [
"shadcn-ui",
"drizzle",
"lucia"
],
"preferredPackageManager": "pnpm",
"t3": false,
"alias": "@",
"analytics": true,
"rootPath": "src/",
"componentLib": "shadcn-ui",
"driver": "pg",
"provider": "postgresjs",
"orm": "drizzle",
"auth": "lucia"
}
Describe the bug
I used pnpm dlx kirimase@latest init to create a new project. It all seemed to work fine but the "db:push": "drizzle-kit push:pg", was missing from package.json.
I believe it should be there. If not, sorry about the confusion.
To Reproduce
Create a new project with the options above.
Expected behavior
It should have the db:push command
Desktop (please complete the following information):
MacOS 14.4.1

fixed with #196


[fix][fn] Add function name and id to producer name to avoid conflict

Fixes #21911

Main Issue: #xyz

PIP: #xyz

Motivation
there will be producer name conflicts error when function enable effectively_once and subscribed to a partitioned input topic
Modifications
Add functionId and instanceId to the suffix of the producer name to avoid conflicts
Verifying this change

[x] Make sure that the change passes the CI checks.
[ ]
[x] This change is a trivial rework / code cleanup without any test coverage.

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository: https://github.com/jiangpengcheng/pulsar/pull/21

Thanks for your fix. I have a question. After adding the instance name to producerName, can the effectively_once be guaranteed? For example, there was no ack for the message before the failure, but the message was resent after switching to another instance. I think deduplication is invalid at this time because of different producerNames. @jiangpengcheng

@graysonzeng  hm, you are right, let's consider an another way to fix the issue

Codecov Report
Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (24c927e) 73.60% compared to head (247c4af) 36.37%.
Report is 12 commits behind head on master.

Additional details and impacted files

@@              Coverage Diff              @@
##             master   #21912       +/-   ##
=============================================
- Coverage     73.60%   36.37%   -37.24%
+ Complexity    32359    12894    -19465
=============================================
  Files          1859     1725      -134
  Lines        138373   136499     -1874
  Branches      15160    15494      +334
=============================================
- Hits         101853    49648    -52205
- Misses        28640    80255    +51615
+ Partials       7880     6596     -1284

Flag
Coverage Δ

inttests
24.11% <0.00%> (-0.06%)
:arrow_down:

systests
23.67% <0.00%> (-0.06%)
:arrow_down:

unittests
32.15% <0.00%> (-40.73%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

...a/org/apache/pulsar/functions/sink/PulsarSink.java
53.84% <0.00%> (-20.01%)
:arrow_down:

... and 1443 files with indirect coverage changes


Cache path vs Local path

This aims to fix an issue where providing a directory for a model in a different parent directory/tree results in an error.
There is a split handling between cache path and local path - mostly because I wasn't sure behind all use case implementations (browser vs local vs X). This solutions solves providing file paths such as ../../your_model_dir as the env.localModelPath variable.

@xenova

@xenova

@xenova

Xenova is currently overwhelmed with the release of v3, but will for sure review your PR as soon as possible.
Don't worry, your PR won't be left behind.

Thank you! Happy to help however I can (PR's / Issues / etc), please let me know how to contribute best 😃

@felladrin @xenova
Hi! This has been open for a bit... its a small change I promise :)
Fixes issues in this issue (multiple people are experiencing): https://github.com/xenova/transformers.js/issues/520

@felladrin @xenova
Following up on this! Please let me know how to move forward with your merging process?

Sorry it hasn't been merged yet, @axrati. But only Xenova can make it.

@xenova following up on this!

@xenova @felladrin following up on this!


Replace main to master value in branch scope.

Replace the wrong value main in the branch scope.

Release Notes

Fix of wrong branch scope value used in migration workflow.


Timepicker doesn't initialize with ngModel

Hi,
this is my code :
<timepicker [ngModel]="startTime" name="startTime" [hourStep]="1" [minuteStep]="15"
                                [showMeridian]="false"></timepicker>

the startTime variable is initialized inside the ngOnInit function with a specific DateTime object :
let momentTime = moment(this._event.startDateTime * 1000, 'x');
this.startTime = momentTime.toDate();

but the timepicker component never show the value of startTime ! only the the current time :(
Does someone have this problem too ?

Yes same problem here.

If you use my hack, be aware that the change event will no longer propagate to the parent.  To get around this, I implemented AfterViewChecked in my component, do a comparison to the bound value, and perform onChanges actions if they're not equal.


Fix regenerate test cpg script.

Previous version required pressing enter for whatever reason.
Also made script less arcane.

asking for the java2cpg home was a feature, not a bug. the script made an educated guess, but allowed the user to use a different location.


MAIN - use eslint-config-vivy

Motivation
This will replace our previous eslintrc with our rules.
Also will fix all the issues that existed in the project :)

Messages

:book:
✅ Get a 👍 for requesting reviewers. - Celebrating every win!

:book:
✅  Get a 🏆 for adding description on this PR. - Celebrate on every step!

  Generated by :no_entry_sign: dangerJS against e8eaf26778261a85f003ae0018a3c11daeeff8d9


Language Driver Request for Ruby

Thanks @obie, will add it to our list this year!

Thanks @obie, will add it to our roadmap for this year!

Great to hear!

I want to echo support for this request. I'd love to make or contribute to a gem that enables TypeDB support for Rails, but we need a driver first.

I hope still in this year for ruby


swift4  memory  issues

warning this when i run my app in operation.swift:
implicit Objective-C entrypoint +[owner.HTTP keyPathsForValuesAffectingIsReady] is deprecated and will be removed in Swift 4
implicit Objective-C entrypoint +[owner.HTTP keyPathsForValuesAffectingIsFinished] is deprecated and will be removed in Swift 4
implicit Objective-C entrypoint +[owner.HTTP keyPathsForValuesAffectingIsExecuting] is deprecated and will be removed in Swift 4

Resolved in version 3.0.0 (just released).