How to use SQL Server's 'Select FOR JSON PATH' & OPENJSON() in AWS RDS Babelfish DB

Below existing T-SQL code which generates table data in JSON format just by using the keyword FOR JSON PATH, include_null_values & OPENJSON(). How to implement the same in Babelfish (Aurora PostgreSQL enabling Bablefish cluster) query by connecting to SSMS itself?
Need possible solutions. Thanks in Advance!!
/** Sample Table data in MS SQL server ***/
CREATE TABLE [dbo].[Employee] (
[id] INT,
[name] VARCHAR(25),
[state] VARCHAR(25) )

INSERT INTO [dbo].[Employee] values
(1,'Divya',NULL),
(2,'Akshay','Bengaluru'),
(3,'Kavya','Kolkata')

/** Fetching table data in JSON format ***/

DECLARE @json1 NVARCHAR(Max)
SET @json1 =
(
    SELECT *
    FROM dbo.Employee WITH(nolock)
    FOR JSON PATH, INCLUDE_NULL_VALUES
)
SELECT ',' AS [key],[value] FROM OPENJSON(@json1)

/** MS SQL results to **/

FOR JSON is not supported. The supported functions are:
ISJSON(  )
JSON_VALUE( ,  )
JSON_QUERY( [, ] )
OPENJSON(  [, path] ) [WITH clause]
Also note that currently a table alias after the WITH clause is not supported and there is a known phenomenon around using WITH clause in stored procedures.
Cheers,
/Stefan

Thanks Stefan.

Hi @SwapnaSurya, yes these functions are on our roadmap.


Changed docs.microsoft.com to learn.microsoft.com

Please inspect removal of /en-us in code listings.

@codepo8 should we merge this now?

sure
From: Patrick Brosset @.>
Date: Tuesday, 25 October 2022 at 10:18
To: microsoft/vscode-edge-devtools @.>
Cc: Chris Heilmann @.>, Mention @.>
Subject: Re: [microsoft/vscode-edge-devtools] Changed docs.microsoft.com to learn.microsoft.com (PR #1230)
@codepo8https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcodepo8&data=05|01|christian.heilmann%40microsoft.com|cbce67c4183d412f066308dab6618878|72f988bf86f141af91ab2d7cd011db47|1|0|638022827308512524|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=rr7edLjI7QAfUdfB0sdR4EATu1%2FSfXlBYVIzHD6CR0w%3D&reserved=0 should we merge this now?
—
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fvscode-edge-devtools%2Fpull%2F1230%23issuecomment-1290169105&data=05|01|christian.heilmann%40microsoft.com|cbce67c4183d412f066308dab6618878|72f988bf86f141af91ab2d7cd011db47|1|0|638022827308512524|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Eg4M35%2BHOI%2BhIS6hWPYjiGm9v%2Fpbwomzk06Ca1fClyo%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAADJRFM2JIEH6IVTTC54D3WE6JWJANCNFSM6AAAAAARJVVV2Y&data=05|01|christian.heilmann%40microsoft.com|cbce67c4183d412f066308dab6618878|72f988bf86f141af91ab2d7cd011db47|1|0|638022827308512524|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=HJqUa8cU5FN%2BsIU7Oh2JThWg179bVG5dMftSJpYNbNE%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

yes, merge it.


Fixes #147, tasks not exposed in cli - among other changes

This branch fixes #147 but also makes a few other adjustments:

Adds a task for installing and uninstalling an NPM plugin.  For installation, you can use taq install @taqueria/plugin-ligo once the packages are published to npmjs, but taq install /path/to/taqueria-plugin-ligo should also work. To uninstall, you must specify the package name - directory paths aren't supported.
Error messages aren't truncated. This will help with debugging.
Adds an argument flag for logging plugin requests. When debugging, I often have to uncomment a line in the source of taqueria and re-build. I can then see calls to a plugin logged to the console. I've asked others, like @russellmorton to do this. To make this a little easier, you can now just specify a hidden argument to the taq binary: taq --logPluginCalls
When you execute a task using taqueria for the first time, we generate a .taq/state.json file which makes taqueria fast and performant. However, when debugging, you often have to delete this file in-between executions. To make this easier, you can now specifiy a hidden argument: taq --disableState which will generate a new state file for every execution. This makes taqueria slower, but should only be used for debugging anyhow.
Its possible that we make changes to the schema used in state.json in later versions. Indeed, there's a slight schema change in this branch. The state.json file now includes a "build" property in the schema, which tracks the version of taqueria that generated the state.json file. Taqueria will now detect if the version of taqueria that you're using differs from the one that generated the state.json file, and regenerates it to assure that its using the most up-to-date schema
One of the things we want to be able to do is have taqueria report what build (branch, commit, etc) was used to generate the binary. Although I haven't added that, I did add a mechanism that can be used to provide that information to taqueria. The next step is now just displaying/reporting that.
In a call with Russel, we found that you cannot run npm install [pluginName] on a taqified directory if the directory isn't configured as an NPM project. This is done using the npm init command. Taqueria will now identify if this is an NPM project, and prompt you to run npm init if you try installing a plugin before the directory has been initialized as an NPM project

I think that's it. Although the above may look insignificant, there were changes required in a few different places to accommodate everything, so testing this branch before merging into main would be highly desirable.

Collaboratively the team tested this one together and feel confident merging.


--output is not compatible with --op-collection

Since the --dump-csv is replaced with --output, we have to specify the output file path when dumping csv. However, --op-collection mode can't specify a single output file path.

Lets error out when  both --output and --op-collection is specified. When --op-collection is specified, we require a --output-dir to dump the output to a directory.

Lets error out when both --output and --op-collection is specified. When --op-collection is specified, we require a --output-dir to dump the output to a directory.

sounds good to me. will do it this way.


Add and use common type aliases

As mentioned in #525, there are many common type aliases used in Windows documentation (e.g., DWORD, LPCSTR, etc.) that are not reflected in the Rust projection.
Take CreateWindowExA as an example. In the docs, the first argument is listed as a DWORD and the second is a LPCSTR. The Rust projection lists these two arguments as u32 and *const i8 respectively. This is correct as DWORD and LPCSTR as simply type aliases for u32 and *const i8, but it can lead to confusion when matching up the projection with the documentation. winapi uses these aliases and thus their documentation lines up more closely with the official documentation.

We definitely need something to take the place of unique types like LPCSTR and LPCWSTR as there are semantic details that are lost, but I'm not sure we need to turn u32 into DWORD. Many of the DWORDs are also being turned into enums by the metadata project (typically for flag parameters) so what remains will often just be simple len-style parameters. There's also clarity in using types that are native and familiar in Rust where you can see "oh a DWORD value is just a u32 value".
I do agree LPCSTR showing up as *const i8 is a bug, but that is partly a bug with metadata - it should be *const u8 in metadata and partly a lack of transformation in the windows crate where the additional parameter attribute still needs to be read to turn that into a special marker type or alias.


Slightly in consistent/unpredictable handling of multiple groups with same name

I have questions about group management vis-a-vis matching group names.  It looks like

it is possible to make new groups with the same name as an existing group,
each time the list of groups is queried, multiple groups with the same name are merged to a single group
groups can only be merged if they have the same name

It seems that instead of adding new groups with overlapping names, we should just add items to existing groups so that there is never more than one group with the same name.
In the current state, it is possible for multiple groups with the same name to exist but only briefly and sporadically.

I'm not sure of a use case either, but I'm not sure that it's dangerous. From the look of the DagMC::parse_properties method, if there's already an entry for a property from a previous group set, then it will be added the property tagmap that is being generated.
https://github.com/svalinn/DAGMC/blob/7e1cdb638b59ba22fd6ff0b09e94d8f658a1eadf/src/dagmc/DagMC.cpp#L1174
All the same, I think it's preferable not to have redundant Group instances hanging around. See comments in #15 on this. Thanks for these thoughts! I stood this up very quickly with the idea that it would primarily be a query interface, but it's nice to see it on it's way to something more.

Addressed by #17


Stats for the Freak Project

This issue is a Consolidated list of Statistics to be shown  in the Freak Project

[ ] Show a smooth Area Chart for the commits
[ ] Show top performing Repos by Stars
[x] Show Last 5 year Contribution Charts in a Separate Tab
[ ] Github Status on Home Page
[ ] Top Repos by Stars on Home Page

More Ideas: https://docs.github.com/en/rest/repos?apiVersion=2022-11-28#list-languages


Makes bin/veewee work for me.

 My mistake; I'll do that and re-submit the pull request more cleanly.


RuntimeWarning: invalid value encountered in true_divide

When the range for a parameter's bounds are two equal numbers, like:
'phi1': (1, 1)
a runtime warning is thrown:
RuntimeWarning: invalid value encountered in true_divide

...why are you sending the code a parameter that can never change? just set it as a constant?

I know I could set it as a constant but still, why is there a warning? I don't think there should be one.

...why are you sending the code a parameter that can never change? just set it as a constant?

I want to get a suggestion with a fixed parameter.


Adding Plugin Event Emitter

Plugin Event emitters.

Structure has been made in #26
Still some things to do for parameter validation, mapping and parsing.
For example the playerinfochange. Needs to be transformed into a internal change and needs validation and parsing (of the spectatorstatus for example).
Also needs some kind of functions to add support for filtering, such as playerfinish, only when time is > 0. (because start map also calls finish few times)


Docs/smol fixes

Not 100% on using the graphic vs the logo (if we use the logo… it should be bigger)

Yeah I don't love the way images sit in the hero theme. Not personally attached to either though.


fix closing of the http.Request.Body

Fixes #2551.
On the server side, the http.Request is consumed by the HTTP handler. The HTTP handler may close the body (it doesn't have to though). In any case, closing the stream is the wrong thing to do, since that closes the write side of the stream. All we want to do is cancel the stream (if the
EOF hasn't been read yet).
On the client side (for the http.Response) the same logic applies: When the application calls Body.Close(), all we want to do is cancel the stream (if the EOF hasn't been read yet).

Ah, you figured it out!! That's amazing! Would you like me to test as well? Let me know if I can do anything to help!


Typo - extra '.' in footer

There is an extra '.' in footer that needs to be removed.

Remove extra ' ' between click here and '.'


Reduce Electron app's startup time

Currently, the Electron app's initial startup time can take anything from a couple of seconds to ten. This is due to booting up the go-ipfs daemon first and only then displaying the "login" screen.
To fix this, we should display index.html immediately and start go-ipfs daemon after that (or in parallel). We should also display a "Loading..." text while loading in more assets or starting ipfs daemon.

Suggestion: Display something like Starting ipfs while the node is starting up.

This is being worked on as part of #166. cc @theobat.

This has been achieved. The startup time was massively reduced with the new startup sequence made by @theobat. We now first load the UI, ask for credentials and only after then we start the IPFS daemon.
This can be further reduced in go-ipfs (iiuc from @whyrusleeping and @jbenet) by boostrapping ipfs after starting the daemon (in go-ipfs), so hopefully in the future we have something instant for the startup sequence. It's not bad today either, feels very snappy :)
Good work everyone involved!


Add convenient synonyms to type constructors at the term level

Instead of having to write-
pcon $ PJust $ pcon PTrue

It'd be convenient to have-
pjust ptrue

(or some better names)

Good point.

After thinking about this a lot, I'm not sure this is a good idea. It saves some characteres, but it adds a lot of complexity, since you have to duplicate each data constructor definition, each import, etc. etc.

Debatable. I think people will be defining synonyms either way to reduce code clutter. This package might need to fill in synonyms as well if it starts including Plutarch definitions of Plutus API utilities.
I see two solutions here, so far-

The responsibility with defining synonyms could be offloaded to the user, which means they will probably have to define only as many synonyms as they need, but a lot of Plutarch codebases will be defining these same synonyms.
The responsibility is taken by Plutarch.

Either way, I don't think pcon $ PJust $ pcon PTrue is justifiable while writing business logic. In the end, if Plutarch itself doesn't provide the synonyms, there will probably be a utility package that defines these aliases so people can just import it instead of define every synonym everytime they need it. Which is fine - but at that point, why not just have that within the plutarch package itself?

I personally think pcon . PJust $ pcon PTrue is fine.

This is obsolete with the existence of pconstant now.


added support for flags input using toml config file

I've added full support for parsing the flags through the TOML config file. I used a py lib called tomli to parse the TOML file. It handles reading and parsing the file. Besides, it also takes care of the invalidity of the TOML through the use of exceptions. The PR also makes use of existing code that was written for cmd line args where it already checks whether a path or a directory is valid or whether a file is a txt or md file among other requirements. The purpose was to reuse the code as much as possible so I'm also converting the dictionary that tomli builds to a Namespace class object since argparse library converts the cmd line args to a Namespace class' object. This helps me reuse the existing logic which checks for the validity of the flags. Documentation has also been updated accordingly.
Features addressed with this PR:

The -c or --config flags accept a file path to a TOML-based config file.
If the file is missing, or can't be parsed as TOML, the program exits with an appropriate error message.
If the -c or --config option is provided, the program ignores all other options (i.e., a config file overrides other options on the command line).
The program ignores any options in the config file it doesn't recognize. For example, if the app doesn't support stylesheets, it ignores a stylesheet property.
If the config file is missing any options, it assumes the usual defaults.

@mnajibi This PR is read for review! Let me know if there are any changes to be made to the PR! Thanks! :)


Replace prompt with an ASCII character

wait-other-jobs main(710bebf)  via  v16.20.0 2s via ❄  impure (shell) zsh
❯

❯ is not ASCII, it it a bit hamful when copy and paste to issues or documents 🤔

Closed by https://github.com/kachick/dotfiles/commit/72ac51c432926aed90894aa89856804f71f41c16


Log to stdout in production

I figured out how to do this, but forgot to actually push and pull request it.

:+1:


Add Chinese translation for query-params.md

@Dustyposa @RunningIkkyu  Please take a look.

Great! Thank you @waynerv ! :cake: :coffee:
And thanks for the reviews @yanever and @Laineyzhang55 :bow:


Signed Rosetta package is no longer signed

Hello and thank you for this code ! I need to use your Rosetta package signed in MDS for macOS deployment but your package is not signed anymore. Do you have time to re-sign and upload a new package ? Thx by advance :) Clément

Hi, the signing certificate expired. I have now re-signed it. Let me know if you continue to have problems.

Hi, the signing certificate expired. I have now re-signed it. Let me know if you continue to have problems.

Thx ! I'll try now :)

The problem it's solved, thx again :)


Set keys to turn player

Describe your feature
currently you are able to make the player turn when performing various actions, such as attacking, interracting, and picking blocks. some mods which i am using this with use custom keybinds for some item abilities, which do not rotate the player on use. i suggest being able to add a list of keys which when pressed will make the player face the direction the camera is pointing, to allow compatibility with such mods.

This is already possible using the adaptive_crosshair_hold_items and adaptive_crosshair_use_items config options.


Add StableHLO conversion for concatenate. [#751]

Add concatenate end-to-end along with required conversion for stablehlo.
Dimension is i64 for stablehlo, si32 for ttir/ttnn concat.

@uazizTT @mmanzoorTT I added many more tests. I hope this PR is ready to merge now. Please let me know.

@uazizTT @mmanzoorTT I added many more tests. I hope this PR is ready to merge now. Please let me know.

Thank you for adding the tests. Yes I think it is ready to merge.


This plugin is awesome

I just went through the new Properties plugin and it is much less powerful than your plugin. Please don't go away.

Thanks a lot for your comment. My entire workflow depend heavily on it, so I guess I'll do my best to keep improving it.
From what the core team is explaining, I understand that the Property plugin is focused on UI improvement for frontmatter data.
It is very opinionated on the way data is structured (e.g. lists as indented list only and not as array) and has no plan to bound properties values lists with notes properties/tags/folders whatsoever; and last they don't provide access to a note's property from many locations (not in the tab header, not in explorer's context menu as far as I can tell from the tests I've made during alpha test phase..)
That's why I think there is still some added value with metadata menu, and I'm glad others think it too, and I will maintain it as long as I can

I really appreciate:

like you said, the icon allowing you to open the modal from pretty much anywhere
the modal :-)
ability to nest fileClasses
ability to maintain multi-select values in a plain note
"add missing fields" wherever I want in my note
edit key definitions via the modal
the right click menu functionality in general
full support for in-line, double colon syntax

The last is a big one. I use yaml happily when programming, but Obsidian's implementation caused problems every time I tried. And with the new icon view of frontmatter it isn't even nicely compact anymore.
I've only used your plugin a short time but I can't live without it already.

Hi @mdelobelle thank you so much for this Plugin. This supports me so much in structuring data.
I have actually generated the full Hierarchy of file-Classes from the Schema.org in my open-source Vault on Github: https://github.com/SpocWiki/_Standards/tree/main/fileClass
Anyone can clone this as a sub-vault into their own Vaults, so they can use an open-source Vocabulary for their data.
I hope that this is useful to many people and would like to get some feedback.


Tab Inside an ion-nav-view Does Not Update Title

I'm doing a sidebar-navigation in my app.  One of my views contains a tabbar.  It updates the title correctly if you switch between the tabs, but if you switch to another view and then back to the tab view sometimes it doesn't update the title.
codepen here: http://codepen.io/RangerRick/pen/NPbrLP/
Switch to "Other" and then back to "Events" and (usually) it does not update the title.

On all my templates I use the ion-nav-bar with ion-nav-title inside, works for me

I faced the same issue when title is updated asynchronously. The work around by using ion-nav-title does work.

Here's a codepen showing the issue http://codepen.io/toddhalfpenny/pen/MwwzoK
I tried several ways of reproducing this and the only way was using JS promises.

Workaround using ion-nav-title worked for me too

I'm using the workaround as well.

@cfjedimaster pointed this out some months ago. It did make sense to me what he said, but this is still odd to me. See here: http://www.raymondcamden.com/2015/12/18/is-your-ionic-view-title-not-updating/
And like he said, my memory is worthless and I keep crashing on it.

Hello! Are you all still experiencing this issue with the latest version of ionic? I just tried the codepen myself and couldn't reproduce it. Thanks for providing the codepen by the way!

Yes, I do. I still had to use the solution pointed out by @cfjedimaster.

Hello all! Since there is a well documented workaround for this (thanks @cfjedimaster !) and we do not plan on making any big changes to how navigation works in Ionic 1 i will be closing this issue for now. Thanks for using Ionic everyone!


Support for 80 columns

Hi,
The display doesn't look too great when you look at it on an 80 column display. Pretty much unusable. Any way that you'd consider supporting smaller displays that can't be resized?
Thanks!
Please read CONTRIBUTING.md

Version:
Installation method:

Have you tried changing the width of the side bar?


easy on/off

There are situations in which this plugin breaks the WebRTC functionality. Eg. in the university prevalent eduroam network (tested with this: https://pguth.github.io/peermesh/). It would be good to indicate the state via the extensions icon and allow it to be switched on and off there.

I've made a separate toggle extension that behaves this way. WebRTC Leak Prevent Toggle.
I don't currently intend on merging the two. But I may in the future if there's demand.

Ah, ok, thanks! 😄 Maybe point that out in the repo?


cds run call is deprecated and has to be replaced by cds-serve

Hi Team
We are from last Mile Testing Team
We run the Risk analytics automation test suit where we use your repository
https://github.com/SAP-samples/cloud-cap-risk-management/tree/launchpad-service
https://github.com/SAP-samples/cloud-cap-risk-management/tree/analytics
We are facing a different issue now when deployment of application is getting failed with CDS not found error.
As in package.json =  "start": "cds run", command is deprecated in latest version of CDS so we need to change to
"scripts": {
"start": "cds-serve",
https://cap.cloud.sap/docs/node.js/cds-server#cli-command-cds-serve
Please have a look and change the required one
Regards,
Vinay C

Hi Vinay,
I'll make the change.
Thanks for reporting!

Done.
best regards,
Maha

closing as this was done.


heimer: 3.1.0 -> 3.2.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/juzzlin/heimer/releases.
meta.description for heimer is: "Simple cross-platform mind map and note-taking tool written in Qt"
meta.homepage for heimer is: "https://github.com/juzzlin/Heimer"
meta.changelog for heimer is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/jmknxy8pylyylybcxgf1vf1imkb2d7wp-heimer-3.2.0/bin/heimer had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/jmknxy8pylyylybcxgf1vf1imkb2d7wp-heimer-3.2.0/bin/.heimer-wrapped had a zero exit code or showed the expected version
0 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 3.2.0 with grep in /nix/store/jmknxy8pylyylybcxgf1vf1imkb2d7wp-heimer-3.2.0
found 3.2.0 in filename of file in /nix/store/jmknxy8pylyylybcxgf1vf1imkb2d7wp-heimer-3.2.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
heimer

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/jmknxy8pylyylybcxgf1vf1imkb2d7wp-heimer-3.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A heimer https://github.com/r-ryantm/nixpkgs/archive/f547487c918cccbd9b6ea1830692890cfdfa727e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/jmknxy8pylyylybcxgf1vf1imkb2d7wp-heimer-3.2.0
ls -la /nix/store/jmknxy8pylyylybcxgf1vf1imkb2d7wp-heimer-3.2.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

heimer

Maintainer pings
cc @dtzWill for testing.

Result of nixpkgs-review pr 156507 run on x86_64-linux 1

1 package built:

heimer


Version 6.3

Check if NoteblockAPI Version is supportet.

Waiting some more Days until release.

Waiting some more Days until release.


Polyfills and browser compatibility (Affecting SEO)

Description
I had issues getting getstorybook.io listed on Google, because it doesn't render anything on Google's Fetch and Render feature.
I so I dig into the issue and it was Array.find() couldn't find on Google's browser env. Since Google's Fetch and Render didn't provide console.log output I had to debug this for more than 4 hours doing a lot of trial and error stuff.
Why?
This is happening because we don't use babel-polyfill or any other polyfill or shims.
What we can do?
I can understand the reason behind not using polyfills. But we should document clearly on why we do it and how to add some polyfills.
I simply added following line to src/index.js and everything works fine.
import from 'airbnb-js-shims';

I use Polyfill CDN for this https://polyfill.io/v2/docs/
It's fast and easy.

Hey! This worked great, you're my hero :-).

@arunoda thanks I tried airbnb-js-shims and it fixed both IE 11 and SEO issues. Payload cost is quite high though.
@thangngoc89 tried polyfill.io v2, did not work for me.

@rayshan I really hate it when people say "did not work for me". What do you mean by it's not working? what when wrong, ...


pocoscript licenses

It looks as if some of the pocoscripts have restrictive licenses and perhaps they should be removed or the authors contacted to get permission? Or if permission has been given to include them perhaps remove the text saying they can not be distributed etc to make it obvious that they are now ok to distribute.

I have not had much luck locating the original authors. I could remove the scripts ai suppose but keeping them here at least creates the opportunity of those folks finding me here and either giving permission to relicense, or send a C+D.y concession (though it may be confusing, imperfect, and perhaps outrageously legally unsound) was to add "unless where otherwise noted" in the readme. do you have a better idea?

Perhaps put them somewhere else, even just in its own GitHub project? Just to avoid the risk of this project getting into some kind of trouble?

i think i actually got most of them off textfiles.if i can find them there i can link to them.


organize imports in python files with isort

Clean up of imports in python files. A diff to address https://github.com/ambuda-org/ambuda/issues/296
Test plan

Ran py-lint

$ make py-lint
Running Python Black to check formatting
All done! ✨ 🍰 ✨
129 files left unchanged.
Running Python isort to organize module imports
Running Python flake8 to conform with PEP8
Python lint completed

make install
make devserver
Tested tabs (Texts, Dictionaries, About, Login, help).
Not tested:
Proofing.

@ambuda-org/reviewers , I'm new to this project. Please take a close look at this https://github.com/ambuda-org/ambuda/pull/318. I've done enough testing to my knowledge.
I need help with tests on proofing. Please DO NOT merge without testing proofing.

I noticed Ramayana seed is failing. It was failing before my changes. I'm happy to look into it if needed.
 make db-seed-all
python -m ambuda.seed.lookup.role
python -m ambuda.seed.lookup.page_status
python -m ambuda.seed.texts.gretil
INFO:root:Downloading the latest data ...
Already on 'main'
Your branch is up to date with 'origin/main'.
HEAD is now at 6899592 Clean up Catuḥślokī
INFO:root:Initializing database ...
INFO:root:- Skipped amarushatakam (already exists)
INFO:root:- Skipped kumarasambhavam (already exists)
INFO:root:- Skipped raghuvamsham (already exists)
INFO:root:- Skipped kiratarjuniyam (already exists)
INFO:root:- Skipped shishupalavadham (already exists)
INFO:root:- Skipped rtusamharam (already exists)
INFO:root:- Skipped shatakatrayam (already exists)
INFO:root:- Skipped bhattikavyam (already exists)
INFO:root:- Skipped meghadutam-kale (already exists)
INFO:root:- Skipped kokilasandesha (already exists)
INFO:root:- Skipped bodhicaryavatara (already exists)
INFO:root:- Skipped saundaranandam (already exists)
INFO:root:- Skipped caurapancashika (already exists)
INFO:root:- Skipped hamsadutam (already exists)
INFO:root:- Skipped mukundamala (already exists)
INFO:root:- Skipped shivopanishat (already exists)
INFO:root:- Skipped catuhshloki (already exists)
INFO:root:Done.
python -m ambuda.seed.texts.ramayana
Initializing database ...
Cleaning up old state ...
Parsing text ...
Traceback (most recent call last):
  File<EMAIL_ADDRESS>line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File<EMAIL_ADDRESS>line 86, in _run_code
    exec(code, run_globals)
  File "/Users/kvic/src/ambuda-kvic/ambuda-kvic-local/ambuda/seed/texts/ramayana.py", line 94, in <module>
    run()
  File "/Users/kvic/src/ambuda-kvic/ambuda-kvic-local/ambuda/seed/texts/ramayana.py", line 78, in run
    kandas.append(parse_kanda(text))
  File "/Users/kvic/src/ambuda-kvic/ambuda-kvic-local/ambuda/seed/texts/ramayana.py", line 54, in parse_kanda
    lines = list(iter_lines(raw))
  File "/Users/kvic/src/ambuda-kvic/ambuda-kvic-local/ambuda/seed/texts/ramayana.py", line 34, in iter_lines
    assert m, f"Bad match: {line}"
AssertionError: Bad match: à¤à¤¸à¥à¤¤à¥à¤¯ à¤à¥à¤°à¤¾à¤¤à¤°à¤ à¤¤à¤¥à```

Thanks!

I noticed Ramayana seed is failing. It was failing before my changes. I'm happy to look into it if needed.

I think this is an issue in the uptsream file -- the Unicode encoding looks completely broken. I'll ping the team there.

Thanks!

I noticed Ramayana seed is failing. It was failing before my changes. I'm happy to look into it if needed.

I think this is an issue in the uptsream file -- the Unicode encoding looks completely broken. I'll ping the team there.

Got it.

@kvchitrapu Thankfully @shreevatsa has fixed this issue in #325

Overall LGTM after we resolve diffs. The only open question I have is why some of the double blank lines after imports are being
removed.

@ambuda-org/reviewers, please review and merge if you have write access.

@ambuda-org/reviewers, please review and merge if you have write access.

Thanks, merging. Right now I'm the only one with merge access (since if something goes wrong in prod, I have to fix it), but once we have a staging deploy we can relax this and have others sign off as well.


[Feature] Change camera when recording

Is your feature request related to a problem?
When the user is recording, changing camera's while double tapping, stops the recording without saving.
Describe the solution you'd like
A possibility to change camera angle when recording video.
Additional context
A must have in a modern app that uses the camera

I don't think it's implementable based on the camera plugin. Please submit requests against the camera plugin.

Link to flutter/plugins#6478.

The feature is still broken, filed https://github.com/flutter/flutter/issues/126227.

Camera package supports this by default after version 0.10.4: https://pub.dev/packages/camera


Issue with PSPs handling when upgrading to 4.3 on Kubernetes 1.26

Bugs should be filed for issues encountered whilst operating logging-operator.
You should first attempt to resolve your issues through the community support
channels, e.g. Slack, in order to rule out individual configuration errors. #logging-operator
Please provide as much detail as possible.

Describe the bug:
When upgrading from 4.2 to 4.3 on an EKS 1.26 cluster, the following error appears, seemingly due to the usage of policy/v1beta1 APIs for working with PodSecurityPolicies that were removed in Kubernetes 1.25

Error log on logging-operator 4.3

{"level":"error","ts":"2023-08-10T15:41:34Z","msg":"Reconciler error","controller":"logging","controllerGroup":"logging.banzaicloud.io","controllerKind":"Logging","Logging":{"name":"logging-operator"},"namespace":"","name":"logging-operator","reconcileID":"c7bf25c7-33f0-43de-88da-64eedf08c769","error":"failed to reconcile resource: failed to delete resource: getting resource failed: failed to get API group resources: unable to retrieve the complete list of server APIs: policy/v1beta1: the server could not find the requested resource","errorVerbose":"failed to get API group resources: unable to retrieve the complete list of server APIs: policy/v1beta1: the server could not find the requested resource\ngetting resource failed\ngithub.com/cisco-open/operator-tools/pkg/reconciler.(*GenericResourceReconciler).delete\n\t/go/pkg/mod/github.com/cisco-open/operator-tools@v0.30.0/pkg/reconciler/resource.go:651\ngithub.com/cisco-open/operator-tools/pkg/reconciler.(*GenericResourceReconciler).ReconcileResource\n\t/go/pkg/mod/github.com/cisco-open/operator-tools@v0.30.0/pkg/reconciler/resource.go:523\ngithub.com/kube-logging/logging-operator/pkg/resources/fluentd.(*Reconciler).Reconcile\n\t/usr/local/src/logging-operator/pkg/resources/fluentd/fluentd.go:124\ngithub.com/kube-logging/logging-operator/controllers/logging.(*LoggingReconciler).Reconcile\n\t/usr/local/src/logging-operator/controllers/logging/logging_controller.go:261\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.0/pkg/internal/controller/controller.go:118\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.0/pkg/internal/controller/controller.go:314\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.0/pkg/internal/controller/controller.go:265\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.0/pkg/internal/controller/controller.go:226\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1598\nfailed to delete resource\nfailed to reconcile resource","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.0/pkg/internal/controller/controller.go:324\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.0/pkg/internal/controller/controller.go:265\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.0/pkg/internal/controller/controller.go:226"}

As a workaround for anyone else encountering this, you can set the environment variable PSP_ENABLED=0.
It might be a good idea to automatically add the environment variable to the Deployment when using the Helm chart, the same way that PSPs are ignored if the cluster lacks the API.
Expected behaviour:
Steps to reproduce the bug:

I wasn't able to reproduce it on a fresh kind 1.26 cluster, only happened after upgrading from 4.2 on one of our testing clusters so it might be due to something carried over from previous versions installations.

Additional context:
Kubernetes API removals: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25
Environment details:

Kubernetes version (e.g. v1.15.2): 1.26
Cloud-provider/provisioner (e.g. AKS, GKE, EKS, PKE etc): EKS
logging-operator version (e.g. 2.1.1): 4.3.0
Install method (e.g. helm or static manifests): Helm
Logs from the misbehaving component (and any other relevant logs):

Error log on logging-operator 4.3

{"level":"error","ts":"2023-08-10T15:41:34Z","msg":"Reconciler error","controller":"logging","controllerGroup":"logging.banzaicloud.io","controllerKind":"Logging","Logging":{"name":"logging-operator"},"namespace":"","name":"logging-operator","reconcileID":"c7bf25c7-33f0-43de-88da-64eedf08c769","error":"failed to reconcile resource: failed to delete resource: getting resource failed: failed to get API group resources: unable to retrieve the complete list of server APIs: policy/v1beta1: the server could not find the requested resource","errorVerbose":"failed to get API group resources: unable to retrieve the complete list of server APIs: policy/v1beta1: the server could not find the requested resource\ngetting resource failed\ngithub.com/cisco-open/operator-tools/pkg/reconciler.(*GenericResourceReconciler).delete\n\t/go/pkg/mod/github.com/cisco-open/operator-tools@v0.30.0/pkg/reconciler/resource.go:651\ngithub.com/cisco-open/operator-tools/pkg/reconciler.(*GenericResourceReconciler).ReconcileResource\n\t/go/pkg/mod/github.com/cisco-open/operator-tools@v0.30.0/pkg/reconciler/resource.go:523\ngithub.com/kube-logging/logging-operator/pkg/resources/fluentd.(*Reconciler).Reconcile\n\t/usr/local/src/logging-operator/pkg/resources/fluentd/fluentd.go:124\ngithub.com/kube-logging/logging-operator/controllers/logging.(*LoggingReconciler).Reconcile\n\t/usr/local/src/logging-operator/controllers/logging/logging_controller.go:261\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.0/pkg/internal/controller/controller.go:118\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.0/pkg/internal/controller/controller.go:314\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.0/pkg/internal/controller/controller.go:265\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.0/pkg/internal/controller/controller.go:226\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1598\nfailed to delete resource\nfailed to reconcile resource","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.0/pkg/internal/controller/controller.go:324\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.0/pkg/internal/controller/controller.go:265\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.15.0/pkg/internal/controller/controller.go:226"}

Resource definition (possibly in YAML format) that caused the issue, without sensitive data:

/kind bug

hey @Roberdvs ! thanks for reporting!
It should only happen on K8s version 1.24 and lower, see:
https://github.com/kube-logging/logging-operator/blob/4.3.0/main.go#L241
can you verify your test clusters weren't older than 1.25?

I'm having the same issue, on a fresh 1.26 cluster.

@oschira are you also running on eks? If the server version of eks produces a different result than we expect, I guess we should switch to listing api resources and disable psp-s based on that.

I have the same problem on EKS 1.27.


[CT-1733] [Bug] Macro lookup between packages

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
Specifying my_macro() without package scoping (my_package.my_macro()) can result in calling an external package even though my_macro() is defined in my own package (project).
As far as I can tell, this seems to only happen in the compilation step rather than in runtime, though not sure.
Here's what I think happens in more details and context to the actual problem that occurred.
Expected Behavior
I'd expect doing my_macro() to first look up in my own project, then dbt, and only then (if at all), at 3rd party packages.
Steps To Reproduce
Install two non-dependent packages with the same macro name.
Relevant log output
No response
Environment
No response
Which database adapter are you using with dbt?
No response
Additional Context
No response

@elongl Which version of dbt were you using when you saw the unexpected resolution order, as described in https://github.com/calogica/dbt-expectations/issues/230#issuecomment-1366518509?
It looks like the macros were being called within custom generic tests, which do use a slightly different macro rendering context at parse time. I'm asking about the version because, we included a change in v1.3 (https://github.com/dbt-labs/dbt-core/pull/5907) that fixed an issue when a macro in a generic test was being called as {{ dbt.type_timestamp() }} instead of just {{ type_timestamp() }} (https://github.com/dbt-labs/dbt-core/issues/5720).
In any event, I would expect calling {{ my_macro() }} to prefer your own package version, wherever it's being called, rather than the version defined in a package. If you can provide a simplified reproduction case, that would be much appreciated!


Support the case where only one is rendered.

In the case of only one item rendered, it would make sense to have the rounded border on all sides. Else we end up with only rounded border on right since it was the last to be applied.

If there's only one item, it wouldn't be an input add-on. It'd just be an input or a button.
I understand how that flexibility could be useful in general (for dynamically generated form items), but for the purposes of this demo, I'd prefer to keep the clarity and simplicity of only what's needed for the site.

👍


Use alpine base

This is to fix #19
I took what @bradmccormack wrote but made DYNAMODB_VERSION a build arg instead, this way you can support multiple versions in your CI system without modifying the Dockerfile.

sure, I'll add the commits now

Thoughts?


tree-wide: Drop rpm-ostree cleanup -m

This command just deletes content from /var/cache, but that's no longer needed since it's part of
https://github.com/ostreedev/ostree-rs-ext/pull/367

Keeping as draft until the new rpm-ostree has time to propagate.


yne.fr

Domain: https://yne.fr
Size: 4.7KB
GTMetrix: https://gtmetrix.com/reports/yne.fr/4e1MdKLZ/

Thank you for the suggestion. I am afraid I will not this website to the club right now because it does not satisfy rule 5.

Thank you for the suggestion. I am afraid I will not this website to the club right now because it does not satisfy rule 5.

Sorry about that.
I guess it's advertisement time then  ;)

Sorry about that.
I guess it's advertisement time then  ;)


Rename _dynamic.html to _common.html

Match the name of the common page logic too.

Decided against this: Dynamic is only run when there is no matching page to the request. Common is run on all requests. There is a difference.


Support density matrix simulation

I think we can close this as wont do, as the remote MPS will be retired? @cqc-alec

I think we can close this as wont do, as the remote MPS will be retired? @cqc-alec

Unless we want a local DM simulator; does qiskit offer one of these?

It would be possible to do that locally: https://qiskit.github.io/qiskit-aer/stubs/qiskit_aer.QasmSimulator.html


Generate combined markdown docs file per build

Our current story for generating docs suitable for ingestion in
docs.microsoft.com is "generate a single markdown file with all the
commands and use anchors to cross reference". Since that's not
something the Cobra markdown formatters support out of the box, PC has
manually been merging these files together and doing some small
tweaks.
This PR attempts to automate that logic.
My first attempt at these changes had us to continue to use the Cobra
logic directly (by importing the package it was in) and then try to
clean up small things with some post processing. However, once I
realized that we would need to re-order the default output of the list
commands from SEE ALSO I decided to just take the existing code and
bring it in here and make small tweaks.
At some point, we will move to a different strategy where we have
multiple files and TOC that stitches them together, but until that
point this frees up a bunch of PC's time.

Azure Dev CLI Install Instructions
Install scripts
MacOS/Linux

May elevate using sudo on some platforms and configurations

curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/uninstall-azd.sh | bash;
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/install-azd.sh | bash -s -- --base-url https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116 --version '' --verbose

Windows
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/uninstall-azd.ps1' > uninstall-azd.ps1; ./uninstall-azd.ps1;"
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/install-azd.ps1' > install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116' -Version '' -Verbose;"

Standalone Binary

Linux - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/azd-linux-amd64.tar.gz
MacOS - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/azd-darwin-amd64.zip
Windows - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/azd-windows-amd64.zip

Container
docker run -it azdevcliextacr.azurecr.io/azure-dev:pr-116

Azure Dev CLI Install Instructions
Install scripts
MacOS/Linux

May elevate using sudo on some platforms and configurations

curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/uninstall-azd.sh | bash;
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/install-azd.sh | bash -s -- --base-url https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116 --version '' --verbose

Windows
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/uninstall-azd.ps1' > uninstall-azd.ps1; ./uninstall-azd.ps1;"
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/install-azd.ps1' > install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116' -Version '' -Verbose;"

Standalone Binary

Linux - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/azd-linux-amd64.tar.gz
MacOS - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/azd-darwin-amd64.zip
Windows - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/azd-windows-amd64.zip

Container
docker run -it azdevcliextacr.azurecr.io/azure-dev:pr-116

@puicchan I applied the feedback from the content writer.  You can see the new generated documentation here:  https://gist.github.com/ellismg/d14ad642969588e39ffac8e9c868d780
There are a few changes we couldn't adopt.

When listing output formats, we use "json" instead of "JSON" as the  content writer suggested. This matches what is expected on the command line.

When showing help for a command option with a default value, we print (default: <value>) at the end of the help text for that option. This behavior comes from the library we use for our CLI and is not easy to change.

There are a handful of remaining diffs, most of which are due to the same content being repeated twice and sourced from the same location (e.g. provision and infra create share the help text) and the content writer putting slightly different changes in each place. This was also common for global options. I've applied some level of judgement here, but in cases where there was a majority of support for one form, I adopted that.
There were some edits to the generated markdown that would be hard to bring back into the code (especially around URL formatting, where the markdown reads very poorly from a CLI). In these cases I did my best to make it look nice on the command line first and then to have a reasonable rendering in the generated markdown second.
You can do the comparison yourself, but I think this is probably the best we can do given the level of investment we're willing to put in here right now.
Let me know if you have any blocking concerns - otherwise I am going to get this in so we star the ball rolling on having automation here.

Thanks! @ellismg . Can you update "## Azure Developer CLI"  to "## azd"?So the link for "Back to top" work? We actually ignored the content editor's suggestion and used azd in the end. And Savannah wants to have azd used more in content to boost SEO.

Azure Dev CLI Install Instructions
Install scripts
MacOS/Linux

May elevate using sudo on some platforms and configurations

curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/uninstall-azd.sh | bash;
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/install-azd.sh | bash -s -- --base-url https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116 --version '' --verbose

Windows
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/uninstall-azd.ps1' > uninstall-azd.ps1; ./uninstall-azd.ps1;"
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/install-azd.ps1' > install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116' -Version '' -Verbose;"

Standalone Binary

Linux - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/azd-linux-amd64.tar.gz
MacOS - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/azd-darwin-amd64.zip
Windows - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/azd-windows-amd64.zip

Container
docker run -it azdevcliextacr.azurecr.io/azure-dev:pr-116

Azure Dev CLI Install Instructions
Install scripts
MacOS/Linux

May elevate using sudo on some platforms and configurations

curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/uninstall-azd.sh | bash;
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/install-azd.sh | bash -s -- --base-url https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116 --version '' --verbose

Windows
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/uninstall-azd.ps1' > uninstall-azd.ps1; ./uninstall-azd.ps1;"
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/install-azd.ps1' > install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116' -Version '' -Verbose;"

Standalone Binary

Linux - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/azd-linux-amd64.tar.gz
MacOS - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/azd-darwin-amd64.zip
Windows - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/azd-windows-amd64.zip

Container
docker run -it azdevcliextacr.azurecr.io/azure-dev:pr-116

Azure Dev CLI Install Instructions
Install scripts
MacOS/Linux

May elevate using sudo on some platforms and configurations

curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/uninstall-azd.sh | bash;
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/install-azd.sh | bash -s -- --base-url https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116 --version '' --verbose

Windows
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/uninstall-azd.ps1' > uninstall-azd.ps1; ./uninstall-azd.ps1;"
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/install-azd.ps1' > install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116' -Version '' -Verbose;"

Standalone Binary

Linux - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/azd-linux-amd64.tar.gz
MacOS - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/azd-darwin-amd64.zip
Windows - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/116/azd-windows-amd64.zip

Container
docker run -it azdevcliextacr.azurecr.io/azure-dev:pr-116


Update Example's ReadMe.md...

... to reflect the fact that now we have only one example

Coverage remained the same at 47.466% when pulling 96251cefaf0dcad204e7e4ccd855568adf974bab on ceilican:examples into ffa9c8b3e7b18ec6eebe0128beab654451077ec7 on ScorexFoundation:master.


Swap delete and enter button after removing IdP from preferred list

Addresses the issue where a IdP that has been moved from the preferred IdP list to the regular IdP list still shows a delete button.

@arnoutt @thijskh

:beers:

:accept:


Configuration binder performance

It seems that the current implementation of the ConfigurationBinder is relying heavily on reflection which would have significant performance impact when binding a type multiple times over.
I know the current options pattern leveraging this binding is using Singletons and only rebinds on reload but in our application we are tweaking the options behavior so it can be resolved per lifetime scope instead which would cause all our options classes to be rebound for every request.
Would leveraging expression trees help in this case to limit the reflection on a given options type?
Thoughts?

As a standalone component that can be used over and over I think it would be a fine contribution to have a method that creates a typed binder. It wouldn't be something we'd use by default since as you said, we do this mostly on singletons.

but in our application we are tweaking the options behavior so it can be resolved per lifetime scope instead which would cause all our options classes to be rebound for every request.

How are you "tweaking" the options behavior? You can't change the lifetime of the existing IOptions<T> that would potentially break too much stuff.

There are lifetime changes happening in 2.0 due to IOptionsSnapshot<T> and enabling scoped IConfiguredOptions<T> so in principle this is relevant. It would be good to have some measurements of the perf.
Cc @haok

@davidfowl,

How are you "tweaking" the options behavior? You can't change the lifetime of the existing IOptions that would potentially break too much stuff.
I'm using IOptionsSnapshot which is registered per Lifetimescope, since it needs to reload on change. However it has currently a dependency on IOptionsMonitor which is still registered as a singleton.
I am planning to test today to change the registration of this latter to a Lifetime scope also which I hope would give me the correct behavior.
However, the main down side I see is that it will now bind the options for every request, which is where Performance during Configuration binding will be a big deal.

@divega, if my change above works, I'm planning to make some measurements of the perf but I'm assuming the current implementation is not great, and implementing a TypeBinder would help greatly for repeated binding of the same type.
Cc @HaoK

Yup that was actually a bug and we fixed that in 2.0, where the snapshot is basically just a scoped equivalent of IOptions/OptionsManager, see https://github.com/aspnet/Options/pull/164
I'll take a look at the binder performance

Considering for 2.0 for now, since binder may be used more. May punt if perf looks okay in common scenarios.

We should start by adding micro benchmarks.


A lot of repeating code in nuxt build pages

I don't know if that's the issue or it's my misunderstanding of how this all works. When I run nuxt build --analyze, I get the following picture:

I see there a lot of pages, and many of them contain the same jquery library (and some other as well). Is it necessary to include jquery into the every page file?
Assume it's for server rendering (like rendering the page has to use the complete bundle of that page). But then, when I open any page in the browser, I see the following requests:

It seems that all pages files are loaded for any request.
Why so?
If the system requires to load every page js file, then why there's no single bundle file for the front end that contains everything without repeating libraries?
If it's incremental, then why the front end requests all the pages?

You should add common libs such as jQuery to vendor: https://nuxtjs.org/api/configuration-build#vendor


Canadian research in Research Presentation

Chris/Andy:  is there anything that you want me to add about recently completed, ongoing, or new research at DFO that pertains to hake? I'm putting together a research presentation - very short like the one we did at the JTC meeting - which will just be a bullet of hake related research mostly as an FYI for the SRG.  I want to make sure to cover anything in Canada as well.  Also no worries if nothing pops out.

Can't think of anything specifically hake related. Maybe a bullet paraphrased from the SRG reply (to give something from DFO!) could be:

Work on making fisheries advice robust to time-varying productivity is being conducted as part of DFO's initiative on an Ecosystem Approach to Fisheries Management, and will be monitored by the JTC.

The only thing that comes to mind strictly Canada-based is Stephane’s work on the upward looking sonar mounts but I think we should leave that for the survey team.

Thanks, this is helpful, so closing now


Kinks accepts LineString

With this pull request:

The ring iteration has been moved to its own function to allow reuse
The second ring iteration starts from the first ring current index, to prevent yielding duplicate kinks
The input now can be also a LineString Feature or Geometry
If no valid input is received, it will throw an informative error

I just noticed that the duplicate detection is the intended behavior.
@morganherlocker why is this so? I wouldn't mind modifying either the code (if you want to keep this behavior) or the test (if you adopt my proposed behavior).


Extra .0 should be removed for Centos and RHEL sudo yum-config-manager --enable docker-ee-stable-18.09

false: sudo yum-config-manager --enable docker-ee-stable-18.09.09
correct: sudo yum-config-manager --enable docker-ee-stable-18.09
I bumped into this while setting up a test env on Centos.  Did a quick test on RHEL, and I could see the same issue.

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Deploy preview for docsdocker ready!
Built with commit 78d626d551cc2bd7d064e16cbf0a7068ef671319
https://deploy-preview-7768--docsdocker.netlify.com

reviewed -- looks good!


Padding of element per Time in TimetableList is different from Figma

Overview
As the title says, the Padding per time appears to be half of Figma
The same is true for FavoriteScreen and SearchScreen as well as TimetableScreen.

Figma
Actual

Figma
https://www.figma.com/design/XUk8WMbKCeIdWD5cz9P9JC/DroidKaigi-2024-App-UI?node-id=54876-39860&t=HSvuYQHvkIqBfsAc-4

i would like to try it !!

Thanks! Assigned 👍


refactor: split CSS class tasks-modal-section

Description

Split tasks-modal-section class into classes depending on their content (date, recurrence, description, etc)
Remove some unused properties
Use <section> elements to make the HTML code more explicit semantically
Remove a nesting level (<div> at the top level of the modal)
Remove redundant comments
Slight change in the look of the modal

Motivation and Context
Make possible extraction of components from EditTask.scss and EditTask.svelte. Now CSS class tasks-modal-section contains properties related to all the sections (dependencies, dates, description, etc) that makes that impossible.
How has this been tested?
Some changes were covered by unit tests, but most of them verified by manual test in demo vault.
Screenshots

Before
After

Types of changes
Internal changes:

[x] Refactor (prefix: refactor - non-breaking change which only improves the design or structure of existing code, and making no changes to its external behaviour)

Checklist

[x] My code follows the code style of this project and passes yarn run lint.
[ ] My change has adequate Unit Test coverage.

No test coverage on the CSS code

Terms

[x] My contribution follows this project's contributing guide
[x] I agree to follow this project's Code of Conduct

@claremacrae the diff of the .svelte file is not rendered well on GitHub due to one nesting level on very top being gone now (a <div> removed), I suggest taking a look at it in WebStorm the changes are seen in a clearer way.


Fix all implicit type conversions

Besides a variety of other warnings, there are a lot of type narrowing and type conversions in the libcie-pkcs11 C++ project.
These are not just GCC poking fun at C++ developers, if you're building with clang some become errors and in some platforms others are actually broken code. See for example a Darwin build here, where DWORD is unsigned int, not unsigned long as implicitly assumed.
Being a Java application and a native library with just a handful of universal libraries for dependencies, I'm pretty sure this project could actually work on a lot more platforms than just GNU/Linux distro if these issues could be fixed.

Can you try with latest commits? I managed to fix some issues here and there for clang.
On my machine I can build the library with clang 14

Thanks, I can confirm it builds with clang on x86_64 and aarch64 Linux.
There remains the DWORD issue in SCardListReaders (and probably other functions).

This
https://github.com/M0Rf30/cie-middleware-linux/commit/17fd24bf265fca19b423ed622038a27d39c73c9f
should fix issues on macOS


Added 'ASTRO' to valid vals and removed 'ROSMAP-IA', renamed 'ROSMAP-…

…IA' row to 'ASTRO'
These changes reflect the renaming of the 'ROSMAP-IA' study to 'ASTRO'

Until Brody, Richard or Tracy confirm that the change from 'ROSMAP-IA' to 'ASTRO' is intentional, this PR should not be merged. I will add a second comment or edit this comment if anything changes.

Richard confirmed he wants to keep the 'ROSMAP-IA' study name, closing this out


let eventlogger create new logs for me (needs admin)

This may be wrong headed but it's a bit confusing when you try and create  a new log by specifying a new log/source name and you just get nothing. Perhaps we should do this? Or is there better guidance around using the event log?

Hi @paulgmiller, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.dotnetfoundation.org.

TTYL, DNFBOT;

@paulgmiller, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;

I don't think this is a good idea, looking at the msdn about EventLog https://msdn.microsoft.com/en-us/library/2awhba7a(v=vs.110).aspx#Anchor_2 it says you need to rerun the application or maybe even restart the machine for the creation to take effect. Also, having an option that requires admin is not a good idea usually.

Agreed with @BrennanConroy.  @paulgmiller, thanks for the PR though!


Video and Audio out of sync

Describe the bug
in this recording:
https://live.rbg.tum.de/w/anainfo/37210
video and audio are quite a lot out of sync (about 12 real seconds)
To Reproduce

Go to https://live.rbg.tum.de/w/anainfo/37210
Most noticeable with  the sound of chalk on the blackboard
( more specific example: starts writing at 0:44:34 but sound only comes in at 0:44:46 )

Desktop (please complete the following information):

OS: Ubuntu 22.04 LST
Both on Firefox 120 and (real and ungoogled) chromium 119

But I can see that the original one is good now, it's probably already fixed before I uploaded the new one.


Fix category arg behavior for problem routes

Hmm, can you please provide a paragraph or so to explain this change, ideally inside the git commit message so that the explanation lives with the code? For example, what is the problematic behavior before this change and what is the desired behavior that this change provides? Thanks!


Portus configuration

Can I manually update the srv/portus/config/config.yml file? What about the config-local.yml file?
Changes made to these files directly do not seem to be taken int account (e.g. ldap_enabled: true).
Do I need to run portusctl setup again after making changes to the config files?
config.yml seemes ot remain unchanged by the portusctl setup command.
but the config-local.yml file is modified by the portusctl setup command.

It appears that portusctl setup has to be run. Direct edits to the config files are not taken into account.
But since portusctl overwrites the config-local.yml file, some settings MUST be passed on the command line every single time.
For example, if the ldap settings are not passed to portusctl setup on the command line, then config-local.yml will be written with ldap_enabled: false.
ALL the ldap settings need to be passed on the command line, or they will get written with default values in config-local.yml.
This is incredible inconvenient. I suggest the following handling of defaults:
defaults are set in config.yml
anything NOT defined via a command line argument remains undefined in config-local.yml (which means that the default values in config.yml will apply).

It gets worse! portusctl setup will override the storage settings in /etc/registry/config.yml.

Configuration of Portus on the RPM has to be more clear, that's for sure :)
portusctl setup is meant to get you started from scratch. We will try to accommodate portusctl in situations where:

Some pieces already exist.
The user is just upgrading.

For now this is just too cumbersome.

Can I manually update the srv/portus/config/config.yml file? What about the config-local.yml file?
Changes made to these files directly do not seem to be taken int account (e.g. ldap_enabled: true).

As explained here, you should never do that. The config.yml file contains the default configuration values. You can either directly edit the config-local.yml file or provide the proper environment variables. After doing that, you have to restart Portus.

This is incredible inconvenient. I suggest the following handling of defaults:
defaults are set in config.yml
anything NOT defined via a command line argument remains undefined in config-local.yml (which means that the default values in config.yml will apply).

Bear in mind that this is indeed the current behavior. Take a look at this. So, in portusctl what you provide is what you want to be different from the default settings.
I will close this issue since all the valid concerns are already being tracked in one of these issues: #709, #711 and #712. Thanks for reporting all these issues. We are well aware that there are tons of things that can be improved in the RPM setup of Portus.

"this i indeed the current behavior" : well, for example, the ldap settings are always overwritten in config-local.yml when running portusctl setup, unless the appropriate command-line argument is supplied. I should be able to set them once and for all in either config.yml or config-local.yml, and not have them change when I run portusctl setup again, unless I explicitly provide a command line argument.
"you have to restart portus": How do you restart portus? is this the portusctl setup command? Something else (could not see it in the docs) ? If portusctl setup is meant to be run once only, that is rather dangerous. It would be better if the command was safe to run repeatedly.

The config.yml file is shipped with the RPM and is a 1:1 copy of what we have in master. This file contains the default configuration for a generic Portus project. We need to overwrite this file from release to release to provide the settings for the new values we are going to add.

you have to restart portus": How do you restart portus? is this the portusctl setup command?

There's no command for that. That's a good point, we should create a portusctl restart which just restarts apache.


Upgrade to Cargo 0.22

Only breaking change was the addition of a 6th parameter to
Config.configure for unstable flags: https://docs.rs/cargo/0.22.0/cargo/util/config/struct.Config.html#method.configure
I don't think we need that.

dependency-ci has broken with some unlicensed dependencies but reckon we can merge this anyway. Thanks.

@daithiocrualaoich I find it a bit concerning that we depend on bindings to Google's experimental mobile kernel for building some pretty documentation pages. But I guess that's the world we live in now.


fix: optimize queries

Description
Seems the dead_letters_check query takes a long time to run. And even when it's not spiking like this, it still takes the longest out of the other queries. Attempting to optimize it by not doing maths in the query, and instead leveraging the existing indexes.
Also removed an redundant dead_letter_give_up_check query for checking created_at value.

How Has This Been Tested?
Automated tests
Due Diligence

[ ] Breaking change
[ ] Requires a documentation update
[ ] Requires a e2e/integration test update

I don't think this 14s spike in latency on the graph is because of the simple SELECT query in the dead letter check as we are selecting by the indexed field with a simple query.

I don't think this 14s spike in latency on the graph is because of the simple SELECT query in the dead letter check as we are selecting by the indexed field with a simple query.

Yeah not sure why this would cause it, it could be the result of other things. But it still seems to be poor-performing to some extent, and we can optimize it.


Couldn't pass ProxyInitializeEvent to autoviaupdater 9.5

Attempting to use the plugin on my Velocity 3.4.0 server. I use floodgate, geyser, and AutoViaUpdater. When launching AutoViaUpdater, I get the following terminal error. Tried re-downloading, but still have the issue. I am currently using v9.5 from Spigot.
Could It be the ports I have forwarded? I have a non-standard port configuration for our server.  Geyser uses 25566 and floodgate uses 25565 (Long story)
See Attached Error:
[22:22:32 INFO]: Booting up Velocity 3.4.0-SNAPSHOT (git-4aa9ee77-b455)...
[22:22:32 INFO]: Loading localizations...
[22:22:32 INFO]: Connections will use NIO channels, Java compression, Java ciphers
[22:22:32 INFO]: Loading plugins...
[22:22:33 INFO]: Loaded plugin autoupdategeyser 5.5 by NewAmazingPVP
[22:22:33 INFO]: Loaded plugin autoviaupdater 9.5 by NewAmazingPVP
[22:22:33 INFO] [floodgate]: Took 289ms to boot Floodgate
[22:22:33 INFO]: Loaded plugin floodgate 2.2.3-SNAPSHOT (b114-83fbd6e) by GeyserMC
[22:22:33 INFO]: Loaded plugin geyser 2.6.0-b731 (git-master-c8dadd8) by GeyserMC
[22:22:33 INFO]: Loaded 5 plugins
[22:22:33 ERROR]: Couldn't pass ProxyInitializeEvent to autoviaupdater 9.5
java.lang.NullPointerException: Cannot invoke "java.lang.Boolean.booleanValue()" because the return value of "com.moandjiezana.toml.Toml.getBoolean(String)" is null
at velocity.AutoViaUpdater.onProxyInitialize(AutoViaUpdater.java:68) ~[?:?]
at velocity.Lmbda$5.execute(Unknown Source) ~[?:?]
at com.velocitypowered.proxy.event.UntargetedEventHandler$VoidHandler.lambda$buildHandler$0(UntargetedEventHandler.java:56) ~[velocity-3.4.0-SNAPSHOT-455.jar:3.4.0-SNAPSHOT (git-4aa9ee77-b455)]
at com.velocitypowered.proxy.event.VelocityEventManager.fire(VelocityEventManager.java:676) ~[velocity-3.4.0-SNAPSHOT-455.jar:3.4.0-SNAPSHOT (git-4aa9ee77-b455)]
at com.velocitypowered.proxy.event.VelocityEventManager.lambda$fire$5(VelocityEventManager.java:541) ~[velocity-3.4.0-SNAPSHOT-455.jar:3.4.0-SNAPSHOT (git-4aa9ee77-b455)]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]
[22:22:33 WARN]: The server channel initializer has been replaced by java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
[22:22:33 WARN]: The backend channel initializer has been replaced by java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
[22:22:34 INFO] [geyser]: Loading extensions...
[22:22:34 INFO] [geyser]: Loaded 0 extension(s)

@RichWaWa Try regenerating the config.yml and see if it fixes it. I still haven't had the chance to add an auto reload config feature to this plugin and if that's the reason why sorry for the inconvenience!

Actually found just found a config bug, make sure java 8 options judt have java8 and not java8b, if it says java8b remove the b from the end, I will fix this soon!

That Fixed it!
Thank you for the prompt reply!

That Fixed it!
Thank you for the prompt reply!
Perfect thank you for reporting the bug, appreciate it! I'll release the new fixed version in a couple of hours.

Thank you for informing again, here is the new fixed version https://github.com/NewAmazingPVP/AutoViaUpdater/releases/download/v.9.5.1/AutoViaUpdater-9.5.1.jar


router is not responding out of the blue

Nov 06 14:00:07 surfer systemd[1]: Started Logrotate Service.
Nov 06 14:00:07 surfer systemd[1]: logrotate.service: Deactivated successfully.
Nov 06 15:00:12 surfer systemd[1]: Started Logrotate Service.
Nov 06 15:00:12 surfer systemd[1]: logrotate.service: Deactivated successfully.
Nov 06 16:00:03 surfer systemd[1]: Started Logrotate Service.
Nov 06 16:00:03 surfer systemd[1]: logrotate.service: Deactivated successfully.
Nov 06 17:00:18 surfer systemd[1]: Started Logrotate Service.
Nov 06 17:00:18 surfer systemd[1]: logrotate.service: Deactivated successfully.
Nov 06 18:00:18 surfer systemd[1]: Started Logrotate Service.
Nov 06 18:00:18 surfer systemd[1]: logrotate.service: Deactivated successfully.
Nov 06 18:09:05 surfer dnsmasq-dhcp[918]: DHCPREQUEST(br-lan) <IP_ADDRESS> ea:c6:81:11:7e:2b
Nov 06 18:09:05 surfer dnsmasq-dhcp[918]: DHCPACK(br-lan) <IP_ADDRESS> ea:c6:81:11:7e:2b OnePlus-7T
Nov 06 19:00:18 surfer systemd[1]: Started Logrotate Service.
Nov 06 19:00:18 surfer systemd[1]: logrotate.service: Deactivated successfully.
Nov 06 20:00:00 surfer systemd[1]: Started Logrotate Service.
Nov 06 20:00:01 surfer systemd[1]: logrotate.service: Deactivated successfully.
Nov 06 20:16:58 surfer dnsmasq-dhcp[918]: DHCPREQUEST(br-lan) <IP_ADDRESS> e0:b6:55:e9:5c:9a
Nov 06 20:16:58 surfer dnsmasq-dhcp[918]: DHCPACK(br-lan) <IP_ADDRESS> e0:b6:55:e9:5c:9a
Nov 06 21:00:07 surfer systemd[1]: Started Logrotate Service.
Nov 06 21:00:07 surfer systemd[1]: logrotate.service: Deactivated successfully.
Nov 06 22:00:13 surfer systemd[1]: Started Logrotate Service.
Nov 06 22:00:13 surfer systemd[1]: logrotate.service: Deactivated successfully.
Nov 06 22:05:45 surfer dnsmasq-dhcp[918]: DHCPREQUEST(br-lan) <IP_ADDRESS> 68:3e:26:90:27:61
Nov 06 22:05:45 surfer dnsmasq-dhcp[918]: DHCPACK(br-lan) <IP_ADDRESS> 68:3e:26:90:27:61 focus
Nov 06 23:00:04 surfer systemd[1]: Started Logrotate Service.
Nov 06 23:00:04 surfer systemd[1]: logrotate.service: Deactivated successfully.

likely duplicate of #36 but this one rules out any gc related issue

no longer happens


Consider removing setup_requires from setup.py

Using setup_requires requires that pip has no way of controlling where these dependencies are located.
https://github.com/KenKundert/quantiphy/blob/4223ebb2fe3bf3047a9379307055672443280a05/setup.py#L30
See

https://github.com/pytest-dev/pytest-xdist/issues/136
https://pip.pypa.io/en/stable/reference/pip_install/#controlling-setup-requires

This makes it difficult/impossible to bundle this library for offline installs, for example, using pip download or if a pip.conf file is needed to configure pip for a proxy settings, etc.
Typically test dependencies would be specified in tox.ini, which is already done:
https://github.com/KenKundert/quantiphy/blob/4223ebb2fe3bf3047a9379307055672443280a05/tox.ini#L15
This would make the sdist for this package much more portable. Users will likely just want to use tox to run the tests anyway?

Fixing #15 also helps with this, as users will normally have a wheel option and won't need to install the sdist itself.

Thanks!
I made the change on github. Do you need me to fix this in pypi right away, or can you wait for the next release?

Since the wheel has been uploaded now, this can wait until the next release.
Thanks for the great package!


MCS-768: Add 'cora' as a valid team name

Leaving mit just in case we need to run any old files that have that prefix.


Very simple question

Thank you for the wonderful software!
It used to work fine, until I attempted using a very basic code, and for whatever reason it does not work. Why?
import soundfile as sf
sample_rate = 48000
wavdata = []

for i in range(10):
    wavdata.append(0)

for x in range(40):
    wavdata.append(1)

for y in range(10):
    wavdata.append(0)

sf.write('blip.wav', wavdata, sample_rate)

Thank you so much!!

what's the error message?

Thank you for the reply! When viewed in Audacity, the wav is simply all zeros.

@zeke800 You might want to explicitly specify the data format subtype i.e., in your case maybe 'FLOAT'?

Try writing float data


Gabriel undo and redo

Resolves #117 , #58

Coverage decreased (-1.4%) to 77.816% when pulling 552e8b792a171b3e5d2589a708bac4d1b503c43f on gabriel-undo into e4296d9bf9209fa271e79564596cae3823c55429 on v0.4.


Support int type zero-points in weight-only GEMM

Currently some quantized huggingface models save zero-points in int4 datatype directly, like Qwen/Qwen2-7B-Instruct-GPTQ-Int4 and Qwen/Qwen2-1.5B-Instruct-AWQ · Hugging Face.
But the weight_only_groupwise_quant_matmul in TensorRT-LLM only support fp16 zero-points as input, thus causing a data type conversion like https://github.com/NVIDIA/TensorRT-LLM/blob/a96cccafcf6365c128f004f779160951f8c0801c/tensorrt_llm/models/qwen/weight.py#L104.
For groupwise quantization, memory cost of zero-points is not neglected. Would you pls add int type zero-points support in the weight-only GEMM?

@Tracin  Could you please have a look? Thanks

@xiaonans For group_size let's say 128, means every 128 4bit weights will have one fp16 zero_point. Memory ratio of zp / weight is 16 / (128 * 4). That's about 3% if my calculation is correct. I think it is neglected. On the other hand, dequantize zp in kernel will bring overhead. Do you agree with me?

@xiaonans For group_size let's say 128, means every 128 4bit weights will have one fp16 zero_point. Memory ratio of zp / weight is 16 / (128 * 4). That's about 3% if my calculation is correct. I think it is neglected. On the other hand, dequantize zp in kernel will bring overhead. Do you agree with me?

@xiaonans For group_size let's say 128, means every 128 4bit weights will have one fp16 zero_point. Memory ratio of zp / weight is 16 / (128 * 4). That's about 3% if my calculation is correct. I think it is neglected.

If group_size=64 and 2bit weights are used, the memory ratio of zero-point/weight can be about 12%, 16/(64*2).

On the other hand, dequantize zp in kernel will bring overhead. Do you agree with me?

If the fpA_intB_gemm kernel is able to load int4 zp directly from the global memory, overhead of this loading will be reduced compared with fp16 zp. When dealing with memory-bound scenarios, it should bring in acceleration.

@xiaonans  How to deploy this model（Qwen/Qwen2-1.5B-Instruct-AWQ · Hugging Face.） on TensorRT-LLM?
because  TensorRT-LLM only support fp16 transformer models.
Thank you!

@xiaonans If you have no further questions, we will close this issue in one week.


Are we able to report Phishing Polkadot addresses?

I think i may have answered my own question being a, no.

Yes. The address.json  file has them.

Yes. The address.json  file has them.

thanks for your reply. I have 3 more questions.

Once the Phishing addresses are entered and updated into the Git hub database,  what happens to the address? Are future victims then unable to send funds into the scammers wallet as the address becomes listed as Phishing?

Does that address also become useless in that the owner is unable to move crypto out of this Phishing address?

Does the URL link also become listed as Phishing on the Brave Browser, just like it is on Google Crome and Firefox web browser?

thanks for your reply. I have 3 more questions.

Once the Phishing addresses are entered and updated into the Git hub database,  what happens to the address? Are future victims then unable to send funds into the scammers wallet as the address becomes listed as Phishing?

Does that address also become useless in that the owner is unable to move crypto out of this Phishing address?

Does the URL link also become listed as Phishing on the Brave Browser, just like it is on Google Crome and Firefox web browser?

To you questions -
For the addresses/sites to be used/detected it needs to be integrated into wallets. So on the polkadot-js extension (if installed) if you try for instance to go to https://polkadot.express, it does the following -

(The above would be the same for any wallets forked off the polkadot-js extension, of which there are a couple)
In the same vein wallets need integration to check the actual addresses. At this point (since it is new), as far as I know the apps UI is the only one that checks against this list. For instance if you try to send to the polkadot.company address listed, you will be greeted with -

(At this point it doesn't disallow the account completely in the UI, but does protect the victims - originally wanted to go very hard, but rather decided to phase it in)
TL;DR The lists are available to be integrated as-is and it comes with a library for all checks for wallet providers.

To you questions -
For the addresses/sites to be used/detected it needs to be integrated into wallets. So on the polkadot-js extension (if installed) if you try for instance to go to https://polkadot.express, it does the following -

(The above would be the same for any wallets forked off the polkadot-js extension, of which there are a couple)
In the same vein wallets need integration to check the actual addresses. At this point (since it is new), as far as I know the apps UI is the only one that checks against this list. For instance if you try to send to the polkadot.company address listed, you will be greeted with -

(At this point it doesn't disallow the account completely in the UI, but does protect the victims - originally wanted to go very hard, but rather decided to phase it in)
TL;DR The lists are available to be integrated as-is and it comes with a library for all checks for wallet providers.

For now and future reference - if you have a favorite wallet, direct them to https://github.com/polkadot-js/phishing/tree/master/packages/phishing for integration.

For now and future reference - if you have a favorite wallet, direct them to https://github.com/polkadot-js/phishing/tree/master/packages/phishing for integration.


Error adding nuget to project targeting .net Core 2.1

When i attempt to add this to an ASP.NET 2.1 project via the dotnet command, i get the following error:
Package 'System.Activities' is incompatible with 'all' frameworks in project
Any ideas to work around that?

I think this is better suited for StackOverflow.


Bug?: Untracked files still end up in the commit context

Don't know if this is intended or not, or if there is a config flag to disable the behavior. It seems as though making a commit in which there are some untracked files, still references the untracked files.
To reproduce:

Make some changes to a file
Add a file, but don't add it to git
Run git commit to activate the hook

In my case it generated a commit message that mentioned the untracked files, as well as the one file that was tracked and had changes.

This was just addressed in #48. Waiting for a reviewer to merge into dev


iob 3.3 warnings

tvprogram.0
2021-05-10 20:29:00.348
warn
(1402) Read-only state "tvprogram.0.tv1.cmd" has been written without ack-flag with value "new|program|2021-05-13"

tvprogram.0
2021-05-10 20:29:00.342
warn
(1402) Read-only state "tvprogram.0.tv1.cmd" has been written without ack-flag with value "new|program|2021-05-11"

tvprogram.0
2021-05-10 20:29:00.327
warn
(1402) Read-only state "tvprogram.0.tv1.cmd" has been written without ack-flag with value "new|program|2021-05-14"

tvprogram.0
2021-05-10 20:29:00.326
warn
(1402) Read-only state "tvprogram.0.tv1.cmd" has been written without ack-flag with value "new|program|2021-05-12"

tvprogram.0
2021-05-10 20:28:59.967
warn
(1402) Read-only state "tvprogram.0.tv1.cmd" has been written without ack-flag with value "new|program|2021-05-15"

tvprogram.0
2021-05-10 20:28:59.865
warn
(1402) Read-only state "tvprogram.0.tv1.cmd" has been written without ack-flag with value "new|program|2021-05-10"

tvprogram.0
2021-05-10 20:28:58.032
warn
(1402) Read-only state "tvprogram.0.tv1.cmd" has been written without ack-flag with value "new|channels"

tvprogram.0
2021-05-10 20:28:57.983
warn
(1402) Read-only state "tvprogram.0.tv1.cmd" has been written without ack-flag with value "new|genres"

tvprogram.0
2021-05-10 20:28:57.891
warn
(1402) Read-only state "tvprogram.0.tv1.cmd" has been written without ack-flag with value "new|categories"

tvprogram.0
2021-05-10 20:33:10.876
warn
(1783) Read-only state "tvprogram.0.tv1.cmd" has been written without ack-flag with value "new|categories"

tvprogram.0
2021-05-10 20:33:10.856
warn
(1783) Read-only state "tvprogram.0.tv1.cmd" has been written without ack-flag with value "new|channels"

tvprogram.0
2021-05-10 20:33:10.834
warn
(1783) Read-only state "tvprogram.0.tv1.cmd" has been written without ack-flag with value "new|genres"

+1

fixed


Declare clone() on Response in api.d.ts

Is your feature request related to a problem? Please describe.
I'm attempting leverage adobe/fetch in a place where the typescript for the framework is expecting the fetch Response type to implement the clone() function.
https://developer.mozilla.org/en-US/docs/Web/API/Response/clone
https://github.com/apollographql/apollo-utils/blob/main/packages/fetcher/src/index.ts#L60
Describe the solution you'd like
Add clone() to the Response type.

fixed in https://github.com/adobe/fetch/releases/tag/v4.0.11


[OSPP]: 添加 buddy-codesign 作为 submodule

【OSPP】将 buddy-codesign 作为 submodule 提交到 buddy-mlir

Please just add the in-tree autotuner directory for the OSPP project (do not use the submodule in case OSPP evaluation fails), and writing all the code into the autotuner directory is fine for now.

Please just add the in-tree autotuner directory for the OSPP project (do not use the submodule in case OSPP evaluation fails), and writing all the code into the autotuner directory is fine for now.

Sorry about that.
So should I just clone repo "buddy-codesign" or add files manually?

In the future, this part will be used separately in the buddy-codesign repository, so I switched the target branch, and this PR will be merged into the co-design branch instead of the main branch.

Use English as comments.
Check license head 80-col rule.
Use the black tool format all the Python files.

Sorry about that.
Done now!


Fix generator-method-with-computed-name test

Q
A

Bug fix?
yes (test fix)

Breaking change?
no

New feature?
no

Deprecations?
no

Spec compliancy?
not sure

Tests added/pass?
yes

Fixed tickets
comma-separated list of tickets fixed by the PR, if any

License
MIT

This test was previously checking that a block does not parse as an object, though the intent appeared to be to validate that you can have [yield iter] be the key of an object.
I'm not sure if this is compliant with the spec, or if it makes any sense. If this is indeed supposed to raise an error, I'd be happy to try to submit a patch fixing the parser.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@57aacea). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master    #360   +/-   ##
========================================
  Coverage          ?   97.8%
========================================
  Files             ?      21
  Lines             ?    3504
  Branches          ?     925
========================================
  Hits              ?    3427
  Misses            ?      29
  Partials          ?      48

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 57aacea...4a58492. Read the comment docs.

All parsers seem to parse this correctly so I assume this is correct.


Adds ability to filter posts by tag and updates footer blog links

Relates https://github.com/elixirschool/school_house/issues/75
Ok I had a go at it @kinson! I'm still fairly new to Elixir so lots of feedback welcome re: naming conventions, better ways to structure stuff, etc...
I also made a small change to the existing post preview template to downcase the post tags because some are i.e. "Announcement" vs "announcement".

Ok made the next changes @kinson - sorry it took me a few days to come back to this 😅


bump credhub_exporter to v0.3.0

This PR bumps credhub_exporter from v0.2.0 to v0.3.0.
Changelog

credhub_exporter:

bump internal golang dependencies
replaced github.com/prometheus/common/log by github.com/sirupsen/logrus as log facility
add --log.level, --log.stream and log.json command line flags

bosh spec changes

remove credhub_exporter.log_format
replaced by credhub_exporter.log_stream (default stderr)

Blobs
# fetch credhub exporter new release
wget https://github.com/orange-cloudfoundry/credhub_exporter/releases/download/v0.3.0/credhub_exporter_0.3.0_linux_amd64.tar.gz
# add tarball to blobs
bosh add-blob credhub_exporter_0.3.0_linux_amd64.tar.gz credhub_exporter/credhub_exporter_0.3.0_linux_amd64.tar.gz
# remove old blob
bosh remove-blob credhub_exporter/credhub_exporter_0.2.2_linux_amd64.tar.gz

Thx @psycofdj


Make more clear registration is required

I used my app for the first time yesterday and registered about 10 cameras. AFTER that I got a message telling me I have to register my username at the webpage - resulting in a loss of these 10 positions.
So the App should be more clear about this or should store and upload such positions after successful registration or should force registration on first start-up.

That should not be possible. When you try to mark the first camera the app should immediately prompt you to set a username. Were you offline or in odd network conditions when you marked the ten cameras?  I have not seen this behavior.
I agree, registration should be made more clear. It is not mandatory because some users only want to browse the map, for which no username is needed.

I have been online via mobile connection (quality of this connection is not clear but should not have been that bad). It took at least 1 minute before the message popped up, my phone's screen was switched of in the meantime, so I have seen the message about 5 minutes later. It is an Android 4.4.2 phone

Hmm, that's odd. What was the exact message you got? It should pop up an error right away if you have no username set in preferences.
If you do have a username set, but it's not a registered one, then the phone should vibrate and send off a network request, and an error message will appear when the server returns that the username is wrong.

Yes, it was exactly that message with the "no username" which then guided me to the webpage where I could register. Anyway, a clear message at start-up of the application that informs about the need for registration should solve this problem. This message could be shown as long as the user is not registered.

A clear message at start-up of the application that informs about the need for registration should solve this problem

I agree. Adding an alert at start time if no username is set is now planned for the next release.

This is now implemented on iOS for v1.4. Next up, implementing on Android.


FEATURE: Automated Greeting Workflow

I propose to create a GitHub workflow named "Greetings". This workflow will automatically greet users who create new issues or pull requests in this repository. The Greeting will look like "Hi there! Thanks for opening this issue. We appreciate your contribution to this open-source project. We aim to respond or assign your issue as soon as possible.
Hey @Devanik21 please assign me this task with labels "gssoc-ext", "hacktoberfest-accepted" and "level1"

Hi, have you reviewed this issue.
I'm waiting for the update.

yes @Devanik21 I am working on this

Hey @Devanik21 I have raised the PR
Thanks


Remove Spring Cloud Contract Wiremock support

WireMock has added an official Spring Boot & WireMock integration.

what if I don't use spring boot?

Spring Cloud Contract WireMock assumes that you are using Spring Boot.

oh, right - so wiremock as standalone stub runner stays the same?


svdtools does not handle derivin registers from another peripheral

Example:
PADS_QSPI:
  _delete:
    "VOLTAGE_SELECT":
  _derive:
    "VOLTAGE_SELECT":
      _from: "PADS_BANK0.VOLTAGE_SELECT"

fails with svdtools.patch.SvdPatchError: register PADS_BANK0.VOLTAGE_SELECT not found
Could be related to def derive_from searching for the target register in the parent only rather than decomposing the target register's name.

All we can do here is disabling search for complicated paths.
Try https://crates.io/crates/svdtools instead

Thank you for the feedback.
The rust implementation returns similar results:
[2023-04-02T09:27:51Z ERROR svdtools::cli] by svdtools (0.3.0)

    Caused by:
        0: Processing device `RP2040`
        1: According to `PADS_QSPI`
        2: Processing peripheral `PADS_QSPI`
        3: Deriving register `VOLTAGE_SELECT` from `Hash({String("_from"): String("PADS_BANK0.VOLTAGE_SELECT")})`
        4: register PADS_BANK0.VOLTAGE_SELECT not found

There cannot be "complicated path" as according to the SVD specs:

Specify the register name from which to inherit data. Elements specified subsequently override inherited values.
Usage:

Always use the full qualifying path, which must start with the peripheral <name>, when deriving from another scope. (for example, in periperhal B, derive from peripheralA.registerX.
You can use the register <name> only when both registers are in the same scope.
No relative paths will work.

Remarks: When deriving, it is mandatory to specify at least the <name>, the <description>, and the <addressOffset>.

A register is either in the current scope or using an absolute path.
If I can find some time, I'll try to come we with a proposal to fix that. (I recon it may not be easy due to how iter muts are used).

So, I spent the day trying to get something working.
I made some progress (a really tiny bit) on svdtools but, although svd2rust does handle the paths correctly, it does not handle derivedFrom very well.
So even if svdtools did process these, we couldn't do much beyond that.
I'm closing this, at least it'll be logged if someone tries to do something similar in the future.


Improve godoc. Add testable examples.

Thanks for the PR.  It's always good to have runnable/testable examples.
Would you mind putting the example in an example_test.go file for consistency with the rest of the code base?  See base58/bloom/hash160/hdkeychain.

Since all of the examples print either a correct result or the conversion error, I would do:
amt, err := btcutil.NewAmount(...)
if err != nil {
        fmt.Println(err)
} else {
        fmt.Println(amt)
}

This removes the need to return early on error.
You can also reuse the same error variable for each call.

I'd rather it return early myself.  It's more consistent with the standard way of handling errors and there is really not much point in printing multiple errors.
I agree that err should be reused instead of separate err1, err2, err3, etc.

Also, once you've moved it into example_test.go, please squash everything down into a single commit.

early returns make no sense if you want to show testable examples for each of the error cases.

Yeah two ways:
Show testable examples for each of the error cases OR
Show standard production grade code samples on the godoc.
I suspect most people who find the godocs helpful appreciate code that demonstrates a standard way of doing things in production mode.

Whats breaking the build. I wonder.

./example_test.go:10: ExampleNewAmount redeclared in this block
	previous declaration at ./amount_test.go:114

The example is in both files.  It only should be in example_test.go.

:-1: For me.
Thanks.

Thanks for the update.  Please squash to a single commit and then it's OK from me.

Squashed.

Status check. @davecgh Is this acceptable now?

Yep.  Looks good.  Thanks.  I'll merge it in a second.
OK.