Recommended way to set title and meta using this package

When using graphQL to get the info about an entity such as a product on a product page, you need to include the product's name in the title of the page, along with metadata for SEO purposes.
This is the way next.js supports dynamic title and metadata.
https://nextjs.org/docs/app/api-reference/functions/generate-metadata
export async function generateMetadata({ params }) {
  return {
    title: '...',
  }
}

Well you can't run a hook in there cause it's a server component, you can probably do it the this way:
https://github.com/apollographql/apollo-client-nextjs#in-rsc
But still that means you'll be using both RSC and SSR at the same time, which probably means 2 requests will be sent for getting the same thing, I couldn't find a way to set title and metadata right inside the render method cause if we could that could be much simpler.

You can also just render a <title> element in a Client Component and React will automatically scope it into the head, but it could be worse for SEO.
If you want to use generateMetadata, there's just no way around doing two requests here. There is no possible way of sharing data.

You can also just render a <title> element in a Client Component and React will automatically scope it into the head, but it could be worse for SEO.
If you want to use generateMetadata, there's just no way around doing two requests here. There is no possible way of sharing data.

Thank you so much for the response, did you mean that the title tag will only be set after Javascript has run in the browser and it won't be set on the server-side and that's why it's worse for SEO?

Setting title didn't seem to work perfectly as you mentioned, clearly not much thought was put into a lot of things in NextJS 13 and this is one of them, I ended up using:
generateMetadata  with https://github.com/apollographql/apollo-client-nextjs#in-rsc
and it worked perfectly, the only downside is that it sends two requests, maybe in the close future Next team will provide a better way for doing this or at least, making it possible to share data between SSR and RSC somehow.

Thank you so much for the response, did you mean that the title tag will only be set after Javascript has run in the browser and it won't be set on the server-side and that's why it's worse for SEO?

It would be happening later, so depending on the crawler engine it might be worse for SEO - but I'm not a SEO expert, so I can only point out that it might have some influence, but I don't know the real implications.
As for lifting a rendered <title tag into the document head automatically - this is something that React should do, so it's not directly a Next.js thing - but of course it's only in React canary builds, and while Next runs with them and both the React and Next team call it stable, I can't tell you if this will actually work in all situations - it's one more of those "undocumented" features that may or may not actually be stable.

I thought React.cache should handle things like this
Looks like this
export async function generateMetadata() {
  const data = await getClient().query(...);
  ...
}

// MyClientPage.tsx

export const MyClientPage = () => {
  const {data} = useSuspenseQuery(...);
  ...
}

should use the same cache and dedupe queries with React.cache. Or not?

Thank you so much for the response, did you mean that the title tag will only be set after Javascript has run in the browser and it won't be set on the server-side and that's why it's worse for SEO?

It would be happening later, so depending on the crawler engine it might be worse for SEO - but I'm not a SEO expert, so I can only point out that it might have some influence, but I don't know the real implications.
As for lifting a rendered <title tag into the document head automatically - this is something that React should do, so it's not directly a Next.js thing - but of course it's only in React canary builds, and while Next runs with them and both the React and Next team call it stable, I can't tell you if this will actually work in all situations - it's one more of those "undocumented" features that may or may not actually be stable.

I thought React.cache should handle things like this
Looks like this
export async function generateMetadata() {
  const data = await getClient().query(...);
  ...
}

// MyClientPage.tsx

export const MyClientPage = () => {
  const {data} = useSuspenseQuery(...);
  ...
}

should use the same cache and dedupe queries with React.cache. Or not?

I'm doing some housekeeping so I'm closing some older issues that haven't seen activity in a while.
If this is still relevant, please feel free to reopen the issue.

Woud love to see this be integrated w/ https://github.com/apollographql/apollo-client-nextjs#in-rsc


Local disk
Expected behavior
Restic should log any errors accessing files it discovers, but continue the backup anyway
Actual behavior
Restic stopped at 3.03% with:
error for \\?\D:\System Volume Information: open \\?\D:\System Volume Information: Access is denied.

CPU and disk activity went to basically 0.
I hit Ctrl+C and it got to 3.08% and got stuck again, but the error message didn't change. Then I hit Ctrl+C again and it is still going, now at about 6%. I won't be here much longer to see it finish but I hope it will finish!
Steps to reproduce the behavior
No idea, try backing up a drive with "System Volume Information" I guess?
Do you have any idea what may have caused this?
I ran restic without being Administrator.
Do you have an idea how to solve the issue?
See "Expected behavior" above

I'm not sure if I just misconfigured restic, but I have this backup scheduled weekly, it'd be nice if it just skipped over permissions errors (with an optional log). However, if I've misconfigured something, do let me know. :)

Update: Okay, at about 11% it got stuck again and I had to give it another kick with Ctrl+C. (The error message didn't change.)

Hm, this is odd indeed. It should print an error message and then continue. So it looks like you've stumbled upon a bug.
Where is the repository located? What was your current working directory when running restic?

The repository is located in E:\restic_backup. The current directory when I ran this particular command was, I think, just %HOME%.

Thanks for the details. I need to find a Windows machine and have a look for myself. I think this may be a bug that only occurs on Windows. Hm.

I'd help, but I don't have Windows either. (This is on a family member's computer...)

Incidentally, what is Ctrl+C (SIGINT) supposed to do? I was kind of surprised it didn't kill the whole process, but somewhat pleased, I guess, that the "kick" got it un-stuck.

Good question. I'm not really sure what happened here. I'm surprised that it helped to move the process forward in your case.
On Unix, restic handles SIGINT by removing the locks it left in the repo, then it exits. This has the (unintended) side effect that when a remote repo is used, it will properly finish uploading first before the lock can be removed.
I have plans to properly tear down the internal processing pipelines (using context), but that's not in place yet.

Ah, one thing to try would be these free Windows VMs offered by Microsoft: https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/
I'm afraid I won't have time to do this in a while though, as classes are starting :(

Well, I've had this running as a scheduled task every week on my parents' computer and the task does seem to stop after a while. I need to investigate if that's because the scheduler is killing it after a while or if it's because, under the hood, restic is actually continuing and finishing. I probably should observe it and check CPU and disk usage... I thought I did this but let me do it again and confirm.

Would you mind checking if this is still an issue with 0.9.0?

I have good news.
I just went to my parents' house today and tried it out, but after I downloaded 0.9.0 and ran restic snapshots, I found that, indeed, snapshots had been created every week for the last year! (I had set up a task in the Scheduler to run it regularly.)
So, I guess that means the backups are completing. Now it is running 0.9 so I will check up with it again in a few weeks.
Thanks for the ping!

Thanks for the feedback :)


Can we get DCS BIOS RS485 going on STM Blue Pills - both master and slave?

Hi all,
Been playing with a few devices on the the bench today and got RS485 running, very happy.
At this point the RS485 master requires the device to be an Arduino MEGA2560
Not hard to get them, but they're a big and expensive board.
The STM Blue Pill has 3 or 4 USARTS in addition to the USB port it seems like a great candidate for an RS485 master, more compact and less than 1/4 of the price.
Also would be great to get these going as a slave as well, but not sure how to tell DCS BIOS which USART is connected to a 485 transceiver.
Just a random lookup on ali express, an STM Blue Pill USD $3.33 delivered.
5 / 10 packs are available too.
I'm not great with code, but would be happy to participate  / test code.

pretty please! ;)

+1
On Aug 1, 2022, at 7:22 PM, OzGadget @.***> wrote:

pretty please! ;)
—
Reply to this email directly, view it on GitHubhttps://github.com/DCSFlightpanels/dcs-bios-arduino-library/issues/28#issuecomment-1200945215, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARRX4OAKBIT47Y727JXTPATVW6JNZANCNFSM55G2D34Q.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Anyone had a chance to look at this?
From what I can see there is some code for the 32BIT STM in the  libraries but not being any good with code I can't understand it enough to figure out what to do.
Being able to run multiple busses' off a small, compact, powerful and cheap uC sounds like a great idea.
I'd even go as far as to issue a bounty to someone who could implement and document the use of a BluePill as a standalone USB DCS BIOS unit, a Master for RS485 and as a slave for RS485.
Would this interest anyone?

Anyone had a chance to look at this?
From what I can see there is some code for the 32BIT STM in the libraries but not being any good with code I can't understand it enough to figure out what to do.
Being able to run multiple busses' off a small, compact, powerful and cheap uC sounds like a great idea.
I'd even go as far as to issue a bounty to someone who could implement and document the use of a BluePill as a standalone USB DCS BIOS unit, a Master for RS485 and as a slave for RS485.
Would this interest anyone?

I just posted a bounty for STM32 slaves, maybe you want to join forces so to speak? STM32 master support would be great as well. https://github.com/DCSFlightpanels/dcs-bios-arduino-library/issues/45


Filtering displays incorrect instances and makes duplicates in DB

Created by: @dusan-kovacik-profiq Apr 06 2022 at 11:20 CET
Last updated: Apr 19 2022 at 09:08 CET
ClickUp ID: IK-2615
Description
When you create some social login configurations and then you want to filter them the page will show an incorrect results and moreover it creates a new duplicates. These duplicates are present even after refreshing the page.
And it looks like it's not related to social login configurations only. Pouyan mentioned that it also affects Email configurations.
Steps to reproduce
Create two social login configurations (I've tried to create Google and Facebook)
Put at least 2 characters into the filter input (I've tried to enter oo string)
Expected behavior
Only configurations which contains the filtered value are visible.
Actual behavior
Incorrect configurations are visible and moreover a new duplicated configurations are visible.

Commented by: @dusan-kovacik-profiq Apr 06 2022 at 11:32 CET
cc @indyboox @bakkelim @pepe-zamarripa @bayegan
(I'm not sure whether it's DB or BE issue)


[FANBOX] 9999 Unsupported embed provider, please update content_provider.json for some post formats

Prerequisites

[x] Did you read FAQ section?
[x] Did you test with the latest releases or commit ?

Description
SoundCloud (and possibly other video/sound formats) FANBOX posts will crash the script with the following error message:
9999 Unsupported embed provider = soundcloud for post = *, please update content_provider.json.
hasDumpPage=Y
pageData={'id': '*', 'title': '*', 'coverImageUrl': *, 'feeRequired': 0, 'publishedDatetime': '*', 'updatedDatetime': '*', 'type': 'video', 'body': {'text': '', 'video': {'serviceProvider': 'soundcloud', 'videoId': '*'}}, 'tags': [], 'excerpt': '', 'isLiked': *, 'likeCount': *, 'commentCount': *, 'restrictedFor': None, 'user': {'userId': '*', 'name': '*', 'iconUrl': '*'}, 'creatorId': '*', 'status': 'published'}

Workaround: Manually creating a skip post rule for such posts.
Steps to Reproduce

Fetch any artist with a public or non-restricted post of that kind.
As soon as the script reaches an unsupported post format, fatals and exits.

Expected behavior: Downloading the post and attachment or skipping with a warning.
Actual behavior: Fatal.
Versions
3a9b74cd558c6359c548a01d6f398d86f4ae8cb2

you can update the content_provider.json file and if possible upload it here.

content_provider.json.txt
Thanks for the pointers and very quick reply Nandaka.
I had to upload as txt because github wouldn't let me attach the JSON directly.
This should work fine when embedded in the HTML file with HTML file option on but I couldn't get the contentId anywhere from the API so I went with videoId alone.
The API flow now works properly but make sure you edit it to something less clunky if the content provider entry is weird.

It should throw a message to update the content_provider.json.
For the key, you only need to use whichever exists in the embed reply.
https://github.com/Nandaka/PixivUtil2/blob/master/PixivModelFanbox.py#L265


Error when attempting to setup Systemd

Reproduction steps:

Open shell for existing distro (Ubuntu).
Paste in the first command specified in the README.md under Setup systemd.wsl.exe -d wsl-vpnkit --cd /app cat /app/wsl-vpnkit.service | sudo tee /etc/systemd/system/wsl-vpnkit.service

Press enter to run the command.

Expected results:
The wsl-vpnkit.service should be created according to documentation in the README.md.
Actual results:
The following error occurs.
There is no distribution with the supplied name.
Error code: Wsl/Service/WSL_E_DISTRO_NOT_FOUND

> wsl --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19044.3086

> wsl --list
Windows Subsystem for Linux Distributions:
Ubuntu-20.04 (Default)

Hi, please note that
wsl.exe -d wsl-vpnkit
Specifically refers to the wsl-vpnkit as distro. So if you did not import this first it will fail.
So this step is if you placed this as distro in which case you need to extract wsl-vpnkit.service from the image.


fix: 修复 countTo 显示 和 start && 重置功能

Description

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[ ] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).

有一个冲突，记得要解决一下哈


log_response method deduplicated as function in lib.py

Contributor offers to license certain software (a “Contribution” or multiple
“Contributions”) to sewer, and sewer agrees to accept said Contributions,
under the terms of the MIT License.
Contributor understands and agrees that sewer shall have the irrevocable and perpetual right to make
and distribute copies of any Contribution, as well as to create and distribute collective works and
derivative works of any Contribution, under the MIT License.
Pulled duplicated log_response method out as standalone function.  @AlecTroemel was right, this makes a good place to start the unified auth work, it just wasn't obvious obvious to me at the time!

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

See the complete overview on Codacy

LGTM !

Since it hasn't been merged yet, consider this the first half of #173, which adds the open-coded (twice, at least) logger creation to the logic shuffled off to lib.py.


Game: animate_with_blink, dash, move, blink

Dependent of Moonad/PR12

[x] animate_with_blink
[x] dash
[x] blink
[x] is_rooted

Merged on Moonad#15


What is the difference between Proton Native and React Native for Windows by Microsoft ?

I am confused between Two

What is the difference between Proton Native and React Native for Windows by Microsoft ?

And Do proton support Windows XP and Windows 7

RN for Win by microsoft  support only windows 10 . But I need windows Xp and 7 support ?

Do you support all React Native Components ?

For example , if I use react native camera and use react native paper library ... Can I build for windows without any problem ?

Proton Native use QT, and react-native-windows use UWP platform


xcode 11 js inspector

guys please someone help me I find nothing on the internet with this error. already deleted derived data and does not work CompileC
`/Users/vanixgoncalves/Library/Developer/Xcode/DerivedData/Entremasons-cvtojofshnpjljdymxtfqfjqhren/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-jsinspector.build/Objects-normal/x86_64/InspectorInterfaces.o /Users/vanixgoncalves/Desktop/Entremasons/node_modules/react-native/ReactCommon/jsinspector/InspectorInterfaces.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'React-jsinspector' from project 'Pods')
cd /Users/vanixgoncalves/Desktop/Entremasons/ios/Pods
export LANG=en_US.US-ASCII
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x c++ -target x86_64-apple-ios9.0-simulator -fmessage-length=0 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0 -std=gnu++14 -stdlib=libc++ -fmodules -fmodules-cache-path=/Users/vanixgoncalves/Library/Developer/Xcode/DerivedData/ModuleCache.noindex -fmodules-prune-interval=86400 -fmodules-prune-after=345600 -fbuild-session-file=/Users/vanixgoncalves/Library/Developer/Xcode/DerivedData/ModuleCache.noindex/Session.modulevalidation -fmodules-validate-once-per-build-session -Wnon-modular-include-in-framework-module -Werror=non-modular-include-in-framework-module -Wno-trigraphs -fpascal-strings -O0 -fno-common -Wno-missing-field-initializers -Wno-missing-prototypes -Werror=return-type -Wdocumentation -Wunreachable-code -Werror=deprecated-objc-isa-usage -Werror=objc-root-class -Wno-non-virtual-dtor -Wno-overloaded-virtual -Wno-exit-time-destructors -Wno-missing-braces -Wparentheses -Wswitch -Wunused-function -Wno-unused-label -Wno-unused-parameter -Wunused-variable -Wunused-value -Wempty-body -Wuninitialized -Wconditional-uninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wconstant-conversion -Wint-conversion -Wbool-conversion -Wenum-conversion -Wno-float-conversion -Wnon-literal-null-conversion -Wobjc-literal-conversion -Wshorten-64-to-32 -Wno-newline-eof -Wno-c++11-extensions -DPOD_CONFIGURATION_DEBUG=1 -DDEBUG=1 -DCOCOAPODS=1 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator13.2.sdk -fasm-blocks -fstrict-aliasing -Wdeprecated-declarations -Winvalid-offsetof -g -Wno-sign-conversion -Winfinite-recursion -Wmove -Wcomma -Wblock-capture-autoreleasing -Wstrict-prototypes -Wrange-loop-analysis -Wno-semicolon-before-method-body -Wunguarded-availability -index-store-path /Users/vanixgoncalves/Library/Developer/Xcode/DerivedData/Entremasons-cvtojofshnpjljdymxtfqfjqhren/Index/DataStore -iquote /Users/vanixgoncalves/Library/Developer/Xcode/DerivedData/Entremasons-cvtojofshnpjljdymxtfqfjqhren/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-jsinspector.build/React-jsinspector-generated-files.hmap -I/Users/vanixgoncalves/Library/Developer/Xcode/DerivedData/Entremasons-cvtojofshnpjljdymxtfqfjqhren/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-jsinspector.build/React-jsinspector-own-target-headers.hmap -I/Users/vanixgoncalves/Library/Developer/Xcode/DerivedData/Entremasons-cvtojofshnpjljdymxtfqfjqhren/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-jsinspector.build/React-jsinspector-all-target-headers.hmap -iquote /Users/vanixgoncalves/Library/Developer/Xcode/DerivedData/Entremasons-cvtojofshnpjljdymxtfqfjqhren/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-jsinspector.build/React-jsinspector-project-headers.hmap -I/Users/vanixgoncalves/Library/Developer/Xcode/DerivedData/Entremasons-cvtojofshnpjljdymxtfqfjqhren/Build/Products/Debug-iphonesimulator/React-jsinspector/include -I/Users/vanixgoncalves/Desktop/Entremasons/ios/Pods/Headers/Private -I/Users/vanixgoncalves/Desktop/Entremasons/ios/Pods/Headers/Private/React-jsinspector -I/Users/vanixgoncalves/Desktop/Entremasons/ios/Pods/Headers/Public -I/Users/vanixgoncalves/Desktop/Entremasons/ios/Pods/Headers/Public/React-jsinspector -I/Users/vanixgoncalves/Library/Developer/Xcode/DerivedData/Entremasons-cvtojofshnpjljdymxtfqfjqhren/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-jsinspector.build/DerivedSources-normal/x86_64 -I/Users/vanixgoncalves/Library/Developer/Xcode/DerivedData/Entremasons-cvtojofshnpjljdymxtfqfjqhren/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-jsinspector.build/DerivedSources/x86_64 -I/Users/vanixgoncalves/Library/Developer/Xcode/DerivedData/Entremasons-cvtojofshnpjljdymxtfqfjqhren/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-jsinspector.build/DerivedSources -F/Users/vanixgoncalves/Library/Developer/Xcode/DerivedData/Entremasons-cvtojofshnpjljdymxtfqfjqhren/Build/Products/Debug-iphonesimulator/React-jsinspector -include /Users/vanixgoncalves/Desktop/Entremasons/ios/Pods/Target\ Support\ Files/React-jsinspector/React-jsinspector-prefix.pch -MMD -MT dependencies -MF /Users/vanixgoncalves/Library/Developer/Xcode/DerivedData/Entremasons-cvtojofshnpjljdymxtfqfjqhren/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-jsinspector.build/Objects-normal/x86_64/InspectorInterfaces.d --serialize-diagnostics /Users/vanixgoncalves/Library/Developer/Xcode/DerivedData/Entremasons-cvtojofshnpjljdymxtfqfjqhren/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-jsinspector.build/Objects-normal/x86_64/InspectorInterfaces.dia -c /Users/vanixgoncalves/Desktop/Entremasons/node_modules/react-native/ReactCommon/jsinspector/InspectorInterfaces.cpp -o /Users/vanixgoncalves/Library/Developer/Xcode/DerivedData/Entremasons-cvtojofshnpjljdymxtfqfjqhren/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/React-jsinspector.build/Objects-normal/x86_64/InspectorInterfaces.o
error: error reading '/Users/vanixgoncalves/Desktop/Entremasons/node_modules/react-native/ReactCommon/jsinspector/InspectorInterfaces.cpp'`

have the same problem any solution i get this error only when i run from xcode

yes running via terminal the project works, but by xcode it presents this error.
One previous solution that works for me is to recreate the project.
but when I turn off the computer the error comes back.
it is very strange this error

If your system is Catalina, please give XCode disk access. The easiest way is to:

Restart your computer
Open your project with Xcode
Then Product--->Archive
Then pop up the disk access in the Archive, click on the permission to come

@bashen1  not working for me

I can't find any solution to that

finally i resolved the problem you have to give xcode full disk access all toy have to do
1- open system preference
2- open security & privacy
3- click on full disk access

4- click on this to add new one and choose xcode

after that you will able to run your project from xcode this is work for me i hope it will help you

Thanks @mostafagalal94  your solution works for me

如果您的系统是Catalina，请授予XCode磁盘访问权限。最简单的方法是：

重启你的电脑
使用Xcode打开您的项目
然后产品--->存档
然后在存档中弹出磁盘访问权限，单击权限即可

真的很不错，成功的解决了这个问题，困扰我很多天了

@mostafagalal94 thank you so much! Was feeling helpless the last few weeks not being able to get my app running on my physical device (runs on simulator just fine) because of read errors of yoga files that I couldn't find any information on anywhere until I tried your suggestion. THANK YOU!!!


Fix StyleCI

For now, StyleCI enforces PHP 5.6 compatible syntax. PHP 7 support is coming soon.

Cheers Graham!

No problem. :)


Could not select "Download Button" even though selected checkbox for "agree to the above terms"

[Enter feedback here]
I could not select "Download SVG icons" button even though selected "I agree to the above terms". I found, if locale is "ja-jp", URL is "https://docs.microsoft.com/ja-jp/azure/architecture/icons/", there are this issue. If locale is "en-us", URL is "https://docs.microsoft.com/en-us/azure/architecture/icons/" , there are no this issue.

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

ID: 6624d44c-f9f6-02f8-2c67-0f0637fed62e
Version Independent ID: 9346a8ff-bab5-be2c-9dc1-d546fda1efa9
Content: Azure Icons - Azure Architecture Center
Content Source: docs/icons/index.md
Service: architecture-center
GitHub Login: @doodlemania2
Microsoft Alias: pnp

Thanks for reporting - this issue is under review.  This is a Microsoft Internal DevOps Bug ID AB#

Thank you for your information. I'll close this issue.


[Question] How do I persist user state (e.g. refreshing page) without service worker?

Issue and Steps to Reproduce
Before anything, huge thanks for the library, it is amazing and you should all be proud of it and how well you are maintaining it!
I have a question regarding persisting user state (i.e. user is still logged in) after refreshing a page. I've used your demo and changed it locally to test. I only commented the configuration below:
    client_id: 'interactive.public.short', //  interactive.public.short
    redirect_uri: window.location.origin+'/authentication/callback', // http://localhost:4200/authentication/callback
    scope: 'openid profile email api offline_access',
    authority: 'https://demo.identityserver.io',
    refresh_time_before_tokens_expiration_in_second: 70,
    //service_worker_relative_url:'/OidcServiceWorker.js',                  // commented here
    //service_worker_only: false,                                           // commented here

With this, the demo should use the memory storage, which in fact works (the access token is not hidden by the service worker).

However, when I refresh the page, the user is no longer authenticated 🤔

Keep in mind, if I had used the service worker, it would have worked and persisted the user state between refreshes. However, when I choose not to, it does not.
I was under the impression the access and ID tokens were saved in local storage, that way this doesn't happen. Am I missing something? How can I achieve normal behaviour (refreshing and user still be logged in) without using a service worker?
Thank you!
Versions
Latest version
Expected
Expected user to not be asked to login again after refreshing page.
Actual
User loses "logged in" status and has to login again.
Additional Details
None

hi @LuchoTurtle , thank you for your issue.
We are using Session Storage that must be keep until your close your tabulation.
if you it F5 the data should be still here.
if you it ctrl+F5, it erase the data, it is a normal behavior for developers.
if you do not have this behavior, what is your browser?

Service Worker mode is really more secure than the other mode.

Service Worker mode is really more secure than the other mode.

I fully agree! I'm inclusively using it right now 🙂! However, there was a situation that I could not and I tried to see if it worked without service worker.

hi @LuchoTurtle , thank you for your issue. We are using Session Storage that must be keep until your close your tabulation.
if you it F5 the data should be still here. if you it ctrl+F5, it erase the data, it is a normal behavior for developers.
if you do not have this behavior, what is your browser?

If I comment those lines (not use the service worker), after logging in, if I F5, it shows me as unauthenticated and I have to login again (even by hard refreshing with CTRL + F5). I was using Chrome and I did this experiment with your demo 🙂.
I'm just wondering if this is expected. It works wonderfully with service worker though! If it is not, I'd be happy to try and make a PR for a feature like this for those who need it, I find your work amazing 🙏!

Thank you it is really an issue => https://github.com/AxaGuilDEv/react-oidc/pull/731


Fix use from prelude

Part of https://github.com/gtk-rs/gio/pull/284
cc @GuillaumeGomez , @sdroege

Please merge this PR as is

Trust merge it is then!


Import published PointCloud2 to OSF

Summary of Changes

Import published PointCloud2 to OSF
Currently only support the ouster::Point type

Looks good. Can't figure out how approve.

I will say this is moot with updated sdk, since this also requires the sdk.


enable armclient to deal with Azure German Cloud

In the AzureGermany environment, REST-endpoints are reachable under different URLs. In addition, the APIs are older and require different connection paramters.
Defining separate environments with different parameters allos armclient to operate against other Microsoft Cloud environments as well.

btw, thank you for developing armclient!


Add meta tags to default swagger-ui index page

Hi,
I would like to force the swagger-ui index page not to be cached, adding these meta tags in the head section :
META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE"
META HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE"
META HTTP-EQUIV="EXPIRES" CONTENT="0"
How can I do that ?
I would like to use the native index page, not using my own index file through CustomAsset functionnality.
Is there a way to add meta tags to the default index swagger-ui page ?
Thanks.

You could inject some javascript that inserts the tags you need, but it is still a customAsset

Thanks @VisualBean
Problem is javascript injected with "InjectJavaScript" is executed after the page is loaded.
For such elements as meta, it can not be done this way.
I just tried to add these code in one javascript file I inject with "InjectJavaScript" :
var meta = document.createElement('meta');         meta.httpEquiv = "CACHE-CONTROL";         meta.content = "NO-CACHE";         document.getElementsByTagName('head')[0].appendChild(meta);
But as expected, it has no effect.
I think the only way to add meta tags without injecting a custom index page would be to add these tags with a dedicated method in the SwaggerConfig Register method.
But I did not see any methods to do that in the documentation.
It would be something like :
c.InjectMeta(thisAssembly, "<META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE>");
I don't know if it is something that can be added to upcoming swashbuckle versions ?

Fundamentally, Swashbuckle is a Swagger JSON generator. To provide a complete documentation solution, it ships with an embedded version of the swagger-ui. However, the value-add is really in the generator. It would actually be quite trivial to host the swagger-ui assets yourself and simply point to the Swagger JSON endpoint generated by Swashbuckle.
For these reasons, direct UI enhancements are outside the current scope of the Swashbuckle project. With that said, I will endeavor to keep the embedded version up-to-date so that new features implemented by the swagger-ui folks are made available through Swashbuckle. Although it is currently a major version behind :(
But, with all that said, you CAN still achieve your goal by simply injecting your own of the index.html page and applying your meta tags there. See the readme for instructions.


Added as contributor

This change is

@MaanavD Please post links to your github PRs you have contributed to Kubeflow. This helps us document your contributions towards the membership.

@MaanavD Please post links to your github PRs you have contributed to Kubeflow. This helps us document your contributions towards the membership.

Hi there, here is a PR that I have added. I'm working towards making more in the near future as well.
https://github.com/kubeflow/website/pull/763

/assign @abhi-g Other than the PR that was closed, I have also contributed to answering questions on slack and am currently working on documentation for Azure. See this for more information.

/lgtm
/approve


[Bug] Copy as Image Not Working on iOS

Hello @zhouhua !!!!
First of all, thank you very much for this plugin. I have been looking for an export plugin for a long time.
When I use the command Copy as Image on iPadOS, unfortunately its not working :(
I noted 2 things:
ℹ The Copied! notification is not visible
ℹ The console is showing negative value for scollHeight: -16
📹 On the right is the Note <-> On the Left is the Console
https://user-images.githubusercontent.com/85180696/202857998-57eff892-ae37-4817-a1b1-35e98e6b1f8c.MOV

I hope you could find a solution for iOS 🙏🙏🙏
Thank you very much for reading this
Have a great day !

I didn't test it on ipad yet. I'll try to fix the bug in this week.

Thank you very much for your reply @zhouhua !
I hope you find a solution 🙏🙏🙏

Clean up outdated issues. If the problem persists in the new version, please reopen this issue.


how to output transactionId in my log

Here is my log output：
Catalina. Out
2018-09-06 12:34:49,084 [INFO] [catalina-exec-101] [XXXXXXXServiceImpl. Java: 58] - [TxId:, SpanId:] xxxxLog is exist.
TxId:, SpanId: unreachable
Java's logging plug-in is logback，why TxId and SpanId No values are output

https://github.com/naver/pinpoint/blob/master/doc/per-request_feature_guide.md


Vasil update

Update BPI (and plutus-apps) accord to this PR https://github.com/mlabs-haskell/bot-plutus-interface/pull/103
We also need the updated wallet for the cluster: https://github.com/input-output-hk/cardano-wallet/pull/3318

Plutip updated according to related BPI PR.
Cluster uses node version 1.35.3


The creation of dynamic properties is deprecated in PHP 8.2

In PHP 8.2 the creation of dynamic properties was deprecated, hence the module installation spawns lots of
PHP Deprecated:  Creation of dynamic property FrontendForms\DefaultImageCaptcha::$[...] is deprecated in /var/www/html/site/modules/FrontendForms/Formelements/Tag.php on line 103

notices.
Although it doesn't really matter, here are the versions:

PHP: 8.2.2
ProcessWire: 3.0.213 dev
OS: Kubuntu 22.04.1

Hello Gabriel,
thank you for your feedback. I know, that it does not work properly in 8.2, but there are so many people out there who run a lower version than 8.2, that I had decided to do not take care about PHP 8.2.
In PHP 8.1 it should work without warnings.
I will add a hint on the readme file, that using 8.2 will lead to warnings at the moment.
Thank you for reporting and using the module. I will update the module to be 8.2 ready, when the time is fine :-)
Best regards Jürgen

AllowDynamicProperties class added to class Tag to prevent warnong on PHP 8.2 for dynamically decleared properties

All dynamic properties were replaced by a declared property. Should now work without problems in PHP 8.2 (if I have not forgotten a property to replace ;-). Corrected version is now available in the download section. Version number will be increased after more testing.

You work faster than I think :grin:
I apologize for not being specific about the issue description. In my case it was - and it still is - caused by:

57 non-defined properties, taken from the module config, and assigned to AbstractCaptcha in the constructor (Formelements/Captcha/AbstractCaptcha.php, line 43), and
the public TextElements $topLabel property of InputRadioMultiple, assigned in the constructor (Formelements/Inputelements/Inputs/InputRadioMultiple.php, line 37).

The module spawned no more notices after I defined those properties, but I didn't grok your code enough to understand what would be the better solution.
The complete properties list is:

AbstractCaptcha::$github_modified
AbstractCaptcha::$input_alertErrorText
AbstractCaptcha::$input_alertSuccessText
AbstractCaptcha::$input_appendLabel
AbstractCaptcha::$input_bgcolorchooser
AbstractCaptcha::$input_bgCustomColors
AbstractCaptcha::$input_bgnumberOfColors
AbstractCaptcha::$input_blacklist
AbstractCaptcha::$input_blurlevel
AbstractCaptcha::$input_captchaCharset
AbstractCaptcha::$input_captchaFontFamily
AbstractCaptcha::$input_captchaFonts
AbstractCaptcha::$input_captchaFontsize
AbstractCaptcha::$input_captchaHeight
AbstractCaptcha::$input_captchaLinesColor
AbstractCaptcha::$input_captchaNumberOfCharacters
AbstractCaptcha::$input_captchaNumberOfLines
AbstractCaptcha::$input_captchaTextColor
AbstractCaptcha::$input_captchaType
AbstractCaptcha::$input_captchaWidth
AbstractCaptcha::$input_charactersOffLine
AbstractCaptcha::$input_colorchooser
AbstractCaptcha::$input_dateformat
AbstractCaptcha::$input_emailTemplate
AbstractCaptcha::$input_framework
AbstractCaptcha::$input_grayscale
AbstractCaptcha::$input_html5_validation
AbstractCaptcha::$input_logFailedAttempts
AbstractCaptcha::$input_maxAttempts
AbstractCaptcha::$input_maxTime
AbstractCaptcha::$input_minTime
AbstractCaptcha::$input_numberOfColorsOfLines
AbstractCaptcha::$input_pixelatelevel
AbstractCaptcha::$input_preventIPs
AbstractCaptcha::$input_privacy
AbstractCaptcha::$input_removeCSS
AbstractCaptcha::$input_removeJS
AbstractCaptcha::$input_requiredHintPosition
AbstractCaptcha::$input_requiredText
AbstractCaptcha::$input_showasterisk
AbstractCaptcha::$input_timeformat
AbstractCaptcha::$input_useHoneypot
AbstractCaptcha::$input_useIPBan
AbstractCaptcha::$input_wrapperFormElements
AbstractCaptcha::$input_wrapperFormElementsCSSClass
AbstractCaptcha::$input_wrappers
AbstractCaptcha::$last_check
AbstractCaptcha::$toppasswords_download
InputRadioMultiple::$topLabel

You are right: There was an relict from the old version, which I haver overlooked. Please update to 2.1.20 and let me know if the warnings are gone.
Best regards

 Uncaught Error: Call to a member function setText() on null in site/modules/FrontendForms/Formelements/Captcha/AbstractImageCaptcha.php:33

The error is gone after making InputRadioMultiple::$topLabel public.

Thanks for reporting and offering the solution :-)
I have made it public! I do not know why I have made it protected, but I guess I have made it out of habit...

:+1:  It's good now.
Time to put your module to work :grinning:


Optimize rendering sensor pose updates

🦟 Bug fix
Related PR: https://github.com/gazebosim/gz-sensors/pull/439
Summary
Currently we are updating the pose of all rendering sensors every iteration. This is not necessary as we currently do not expect sensor pose to change at runtime. This PR removes the pose updates every iteration and it now just sets the pose of these rendering sensors once they created. For camera based sensors, their pose transform is the combined result of //sensor/pose and //sensor/camera/pose (previously the //sensor/camera/pose sdf element was ignored and never used).
Here is an example world for test: camera_test.sdf. The world consists of 2 cameras sensors (rgb and depth) with pose offsets in //sensor/pose and //sensor/camera/pose. Together with https://github.com/gazebosim/gz-sensors/pull/439, the camera sensor pose should be set correctly and you should see images like below:

Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

previously the //sensor/camera/pose sdf element was ignored and never used)

I imagine this would break some existing SDF files. I wonder if we should provide a flag to enable/disable this bugfix. We should add an entry in the migration guide regardless.

if we should provide a flag to enable/disable this bugfix

I am thinking that I can remove the camera pose change in this PR which is targeting a release branch so we don't break existing sdf files in Harmonic. I'll then create a separate PR targeting main with the camera pose change and a migration guide entry. How does that sound?

That sounds great!

removed camera pose changes in a129d93. I'll merge this forward to main first and then apply the camera pose changes in a separate PR.


dubbo rds for dubbo proxy

Title: dubbo rds for dubbo proxy
Dynamic routes is importatant feature for proxy. In the #19982, @tkovacs-2 added rds support for the thrift proxy and provides template codes for rds.
Then, we can try to add dubbo rds to Envoy just by adding little codes.
[optional Relevant Links:]

Any extra documentation required to understand the issue.

#21087


Why not use strict return types?

composer.json shows that minimum PHP version is 7.1.x - so why don't use strict types everywhere? eg. https://github.com/propelorm/Propel3/blob/master/src%2FPropel%2FCommon%2FTypes%2FSQL%2FBooleanType.php
<?php
declare(strict_types=1);

public function databaseToProperty($value, FieldMap $fieldMap): bool
public function propertyToDatabase($value, FieldMap $fieldMap): int

Because we decided to use php 7.1+ after the most code was written.

So is strict return types a nice to have (something a contributer should to for newer code) or do you want to keep the code consistent by not using strict return types in general?

Actually, I would prefer strict :)

While refactoring some parts and fixing test suite, we're moving to strict types (see #64 and #61).
At the end, Propel 3 will be almost totally strict typed.


Wrong documenation

This article is speaking about Import-VM for Windows 10/Windows 2016 host, mentioning XML files.
Hyper-V doesn't use XML file for configurations in Windows 10 & Windows 2016.

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

ID: 42fa5406-e41f-9941-9bc4-3c305f9135af
Version Independent ID: 3274511d-d9d5-6397-f168-db8918a4bebb
Content: Import-VM (hyper-v)
Content Source: docset/windows/hyper-v/import-vm.md
Product: w10
Technology: powershell-windows
GitHub Login: @coreyp-at-msft
Microsoft Alias: coreyp

@officedocsbot assign @e0i

@SergeGrd Thank you for your feedback. We have made changes to the document to reflect the correct formar (.vmcx)
Thanks
Sri

@SergeGrd
It has been found that the issue has already been addressed with the following commit.
[689ab24 ] Changed xml to newly vcmx format
We are thus marking this issue as resolved. Feel free to re-open it if you feel it hasn't been resolved.
Thank you for taking the time to provide feedback.

@officedocsbot close


AttributeError: 'CustomSearch' object has no attribute 'getShelfComponent'

Hi, I get this error:
AttributeError: 'CustomSearch' object has no attribute 'getShelfComponent'
What might be wrong please. Thank you.

Upgraded to version 1.4.6 and slightly changed the search term, now it is working. Thanks anyway.


Cannot quit vim gracefully after delete all buffers with :%bd

Describe the bug
The bug is related to cmp.setup.cmdline(':',...)
Delete all buffers with :%bd and then :q create this warning

I have to quit vim with :q! instead
Minimal config based on this
if has('vim_starting')
  set encoding=utf-8
endif
scriptencoding utf-8

if &compatible
  set nocompatible
endif

let s:plug_dir = expand('/tmp/plugged/vim-plug')
if !filereadable(s:plug_dir .. '/plug.vim')
  execute printf('!curl -fLo %s/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim', s:plug_dir)
end

execute 'set runtimepath+=' . s:plug_dir
call plug#begin(s:plug_dir)
Plug 'hrsh7th/nvim-cmp'
Plug 'hrsh7th/cmp-buffer'
Plug 'hrsh7th/cmp-cmdline'
Plug 'hrsh7th/cmp-nvim-lsp'
Plug 'hrsh7th/vim-vsnip'
Plug 'neovim/nvim-lspconfig'
call plug#end()
PlugInstall | quit

" Setup global configuration. More on configuration below.
lua << EOF
local cmp = require "cmp"
cmp.setup {
  snippet = {
    expand = function(args)
      vim.fn["vsnip#anonymous"](args.body)
    end,
  },

  mapping = {
    ['<CR>'] = cmp.mapping.confirm({ select = true })
  },

  sources = {
    { name = "nvim_lsp" },
    { name = "buffer" },
  },
}

cmp.setup.cmdline(':', {
  sources = cmp.config.sources({
    { name = 'path' },
    { name = 'cmdline' }
  })
})
EOF

lua << EOF
local capabilities = require('cmp_nvim_lsp').updat_capabilities(vim.lsp.protocol.make_client_capabilities())

require'lspconfig'.cssls.setup {
  capabilities = capabilities,
}
EOF

To Reproduce

Setup this

cmp.setup.cmdline(':', {
  sources = cmp.config.sources({
    { name = 'path' },
    { name = 'cmdline' }
  })
})

Open some files
Delete all buffers with :%bd
Quit vim with :q

Expected behavior
Vim should quit without any warning
Additional context

I think the command causes deletion of the buffer that the float window completion menu uses, and this somehow breaks some code which runs on exit. Not sure.

Question: is having cmp.setup.cmdline required for this bug to occur?

Question: is having cmp.setup.cmdline required for this bug to occur?

yes, but only for the : syntax, not /


Remove channel as input from performance tests

So we can get build cache hits between different pre-tested commit branches.

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test and merge

OK, I've already triggered a build for you.


Draw multiple cursors per output

Multiseat (#350) requires to draw potentially multiple cursors on the same output. The current API isn't designed for this, as an output can only draw zero or one cursor. That's because of hardware cursors: no more than one hardware cursor can be set per output (if hardware cursors are supported).
The functions affected are:

wlr_output_set_cursor and wlr_output_set_cursor_surface
wlr_output_move_cursor

A first question is: do we want to support drawing multiple cursors in wlr_output or in wlr_cursor? Currently it's possible to draw and move a cursor without wlr_cursor (see examples/pointer.c). Also, currently the wlr_cursor is responsible for moving the cursor on the output.
We could either:

Add support for multiple cursors per output in wlr_output. We'll need a wlr_output_cursor_create(struct wlr_output *) function that returns a new cursor for that output, and wlr_output_cursor_{move,set_image} functions to move and set its image.
Add support for multiple cursors per output in wlr_cursor. We'll just need to add a wlr_cursor_set_image function and wlr_output will be responsible for moving and drawing the cursor.

Note that we can add wlr_cursor_set_image even with if solution 1 to make things more easy for compositors. Also, solution 2 dangerously ties wlr_output to wlr_cursor: it won't be possible to use wlr_output without wlr_cursor anymore.

The first solution seems better to me. It's conceptually simpler, keeps outputs separate from cursors, and would be easier to wrap in wlroots-rs (since the ownership is more straightforward, with a cursor being owned by an output)


Document seamless caveats on small textures in NoiseTexture2D and NoiseTexture3D

This also harmonizes "normal map" spelling across the class reference.

This closes https://github.com/godotengine/godot/issues/77008.

Note: When cherry-picking, undo the NoiseTexture3D changes as that class doesn't exist in 4.0.

Thanks!


[lint] otp_ctrl is (sort of) failing verible lint

If you look at the generated lint.log, you'll find that Verible is choking on a syntax error. This is currently being ignored by the parse-lint-report.py (another bug, addressed by PR #5026).

I guess that Verible just doesn't support this sort of SVA yet. Is the problem just that we should be excluding the auto-generated CSR assertion files from the file list?
Note that this bug blocks merging #5026, because fixing parse-lint-report.py will (correctly) cause us to fail CI.
@msfschaffner: Since you know about both OTP and linting, I'm hoping you'll have a clever idea! :-)

Oh! Looking at #5026 again, it's not just otp_ctrl. But I think the errors are essentially the same across the board.

Oh! Looking at #5026 again, it's not just otp_ctrl. But I think the errors are essentially the same across the board.

Yeah I just stumbled over this 2 days ago as well when we removed the unnecessary waivers in https://github.com/lowRISC/opentitan/commit/9ce4bd9eba8ee99a301ce52f136ca70aa06ccf93
It looks like that regex pattern masked some of the errors that occurred during Verible runs.
For this extra syntax error, I had provisioned https://github.com/lowRISC/opentitan/commit/268692c5b6afcf51d5146be6c024aa4760ede4a6 but I backed both these commits out again since I thought they may have led to the flaky CI issues we where seeing.
I've opened https://github.com/google/verible/issues/652 since this needs to be fixed upstream.
Unfortunately it's not possible to waive syntax errors easily: https://github.com/google/verible/tree/master/verilog/tools/lint#syntax-errors.
In the mean time, we could (in order of my preference ;)):

fix the DV code to use a different syntax (@cindychip can you check whether that would be possible?)
tweak the DV core files to not include the offending file for Verible runs
detect and waive this particular condition in the parser script
disable DV linting in PR CI (it kills all lint targets anyway)
let the status quo be until this issue has been resolved upstream (may take a while)

WDYT?

Yeah I just stumbled over this 2 days ago as well when we removed the unnecessary waivers in https://github.com/lowRISC/opentitan/commit/9ce4bd9eba8ee99a301ce52f136ca70aa06ccf93
It looks like that regex pattern masked some of the errors that occurred during Verible runs.
For this extra syntax error, I had provisioned https://github.com/lowRISC/opentitan/commit/268692c5b6afcf51d5146be6c024aa4760ede4a6 but I backed both these commits out again since I thought they may have led to the flaky CI issues we where seeing.
I've opened https://github.com/google/verible/issues/652 since this needs to be fixed upstream.
Unfortunately it's not possible to waive syntax errors easily: https://github.com/google/verible/tree/master/verilog/tools/lint#syntax-errors.
In the mean time, we could (in order of my preference ;)):

fix the DV code to use a different syntax (@cindychip can you check whether that would be possible?)
tweak the DV core files to not include the offending file for Verible runs
detect and waive this particular condition in the parser script
disable DV linting in PR CI (it kills all lint targets anyway)
let the status quo be until this issue has been resolved upstream (may take a while)

WDYT?

Thanks Rupert for investigating the issue. And thanks Michael for the alternatives.
For 1). It is possible to not use keyword property, but the sequence will be quite messy.
I could prefer 2) if it is not too hard to implement.
Otherwise I am happy to try to implement 1) or disattach the CSR FPV check for DVs until it is fixed (Since we have the CSR DV tests, i do not think FPV check is very important)

Thanks Rupert for investigating the issue. And thanks Michael for the alternatives.
For 1). It is possible to not use keyword property, but the sequence will be quite messy.
I could prefer 2) if it is not too hard to implement.
Otherwise I am happy to try to implement 1) or disattach the CSR FPV check for DVs until it is fixed (Since we have the CSR DV tests, i do not think FPV check is very important)

Thanks for checking @cindychip.
I have added a workaround to #5026 that implements solution 2. above.
PTAL and let me know what you think,

Thanks for checking @cindychip.
I have added a workaround to #5026 that implements solution 2. above.
PTAL and let me know what you think,


Implement embedded_hal::i2c::I2c

Created helpers for waiting, setting R/W, and reading/writing so that it's possible to chain together operations in a transaction.
This was tested on an stm32h747igt6 against multiple i2c peripherals.

Looks good!


Refine access note descriptions in diagnostics

This PR will finalize the way diagnostics describe when they're caused by access notes.
Specifically, the pre-existing access note remarks are now only emitted for valid attributes; for invalid attributes, the diagnostic is augmented with text explaining that it was added for an access note and has been disabled:
class MyClass: NSObject {
    // Both of these methods have ObjC: true in access notes

    func good(_: Int) {}
    // remark: implicitly added '@objc' to this method, as specified by access note for <reason string>
    // note: add '@objc' explicitly to silence this warning

    func bad(_: Int?) {}
    // remark: ignored access note: the type of the parameter cannot be represented in Objective-C;
    //         did not implicitly add '@objc' to this method, even though it was specified by access
    //         note for <reason string>
}

To accomplish this behavior, this PR makes it possible for a diagnostic to take a DiagnosticInfo * as a parameter; it then adds an InFlightDiagnostic::wrapIn() method which uses this capability. Thus, an error like diag::objc_invalid_on_func_single_param_type can be wrapped in diag::wrap_invalid_attr_added_by_access_note to add verbiage relating to access notes.
This PR also:

Emits one access note success remark covering all attributes added to each declaration, instead of separate ones for each attribute.
Softens selector conflicts caused by access notes into remarks.
Adds a command-line option which controls whether and how access note remarks are emitted; in particular, you can use it to strengthen ignored access notes back to errors.

I will probably be tweaking this further before I'm finished with this PR.
Fixes rdar://71872575.

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 60b2836707d87fa17c1dbca3c49ec1bc6809bacc

Build failed
Swift Test OS X Platform
Git Sha - 60b2836707d87fa17c1dbca3c49ec1bc6809bacc

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - ccf86c46b34d9c25d8d02d93f40200c157989a76

Build failed
Swift Test OS X Platform
Git Sha - ccf86c46b34d9c25d8d02d93f40200c157989a76

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 5cd34ee37e0250d3fad297ed7a92e5652009bffe

@swift-ci smoke test and merge

@swift-ci smoke test and merge


[External] Codeunit 6620, Function InitAndCheckSalesDocuments

Please make the Function InitAndCheckSalesDocuments from codeunit 6620 externally available.

Please also make the Function CheckCustomer externaly available.

In Addition following functions from Codeunit 6620:
UpdateSalesHeaderWhenCopyFromSalesHeader;
ClearSalesLastNoSFields;
CopyFieldsFromOldSalesHeader;


Create unit test for testing markdown_to_html function

Create a unit test for the following function in src/convert.py:
def markdown_to_html(path, output_folder, css_url)
This function takes an input md file path and writes to a new .html file
Please create a temporary input file to test the following:
# Replace *italic* and _italic_ with italic
# Replace **bold** and __bold__ with bold
# Replace `text` with text
# Replace multi-line code blocks that are inside ```...``` with
...

parameters of markdown_to_html:
path: the path to an input file (ex: "examples/test3.md")
(create a temporary file using: helpers.new_file(tmpdir, "your_file_name.md", pytest.your_global_var))
set pytest.your_global_var in conftest.py pytest_configure() to a long string which represents the markdown content of the input file (see other global variables in conftest.py to get an idea)
output_folder: the path for the output file (ex: til) (you can use a temporary directory, just put tmpdir)
css_url: no need to test this param, just use empty string

Create the unit test in tests/convert_test.py
To name the unit test, use def test_markdown_to_html(tmpdir, helpers):
How to compare the output of markdown_to_html after running the function:
    # Compare actual output file contents to expected
    output_path = tmpdir.join('your_file_name.html')
    assert helpers.file_contents(output_path) == pytest.your_html_global_var

you must set pytest.your_html_global_var in conftest.py pytest_configure() to a long string which represents the expected html content.

I'd like to work on this issue.


PR: Fix test_sort_dataframe_with_category_dtypes

This is making our tests to fail in master

Sorry about this...

Sorry about this...

Don't worry about it, it was my fault :-)
I need to be more careful when merging with master after PR #3873.


Mongoid document proxy binding doesn't work with aliased updated_at field

The current implementation of Garner::Mixins::Mongoid::Document::_latest_by_updated_at currently checks for the existence of the updated_at field.  This doesn't cover documents that alias the updated_at field (typically by including include Mongoid::Timestamps::Short).  This should consider aliased fields.  The latest document query can also be optimized to return a single document.  Something along these lines:
def self._latest_by_updated_at
  # Only find the latest if we can order by :updated_at
  return nil unless fields['updated_at'] || aliased_fields['updated_at']
  only(:_id, :_type, :updated_at).order_by(updated_at: :desc).limit(1).first
end

May serve to document the proxied binding behavior on model classes in the readme, so devs know to create indexes on the updated_at field if they so choose.
Cheers!

Absolutely, would love a PR!

Sounds good.  I've tested locally so I'll make a push request for your review!


update ios header file so it'll work with expo sdk 44+

The fix is based on fixes from this issue: https://github.com/expo/expo/issues/15649

upgraded slipper so that ios build would work

@tran2 still facing the same issue https://github.com/expo/expo/issues/15649
I am using `"@react-native-community/progress-view": "1.3.1"
When would the change be merged?

@Naturalclar could you approve running the workflow to see if this fixes the ios build? Thanks!

@Naturalclar could you approve running the workflow to see if this fixes the ios build? Thanks!

Any update on this? eagerly waiting for this update.

May I hear any update on this?
I can proceed for further only if this progressView issue is resolved.

@Naturalclar could you approve running the workflow to see if this fixes the ios build? Thanks!

@Naturalclar @tran2
May I hear any update on this?
I can proceed for further in my project only if this progress-view issue is resolved.

@Yandamuri @tran2 sorry for the late response, I've just approved the CI run

@Yandamuri @tran2 sorry for the late response, I've just approved the CI run

@Naturalclar Thank you so much for your prompt response🙂.
May I know when will master branch be merged?

@Naturalclar  Thank you for approving the changes.
I have done changes in<EMAIL_ADDRESS>as per this commit and I can confirm that this commit resolves the issue.
Now, My doubt is which version of @react-native-community/progress-view resolves this? Because  v1.3.1  is still giving me the issue unless I do changes in<EMAIL_ADDRESS>

@Naturalclar Thank you for approving the changes.
I have done changes in<EMAIL_ADDRESS>as per this commit and I can confirm that this commit resolves the issue.
Now, My doubt is which version of @react-native-community/progress-view resolves this? Because v1.3.1 is still giving me the issue unless I do changes in<EMAIL_ADDRESS>
@Naturalclar Can you please comment over this?

@Yandamuri sorry for the late response. The fix is included in v1.3.2


Wrong helper function names used

Describe the bug
When using the externalHelpers option, the emitted code uses functions with their internal name (ie: _typeof) instead of their exported name from @swc/helpers (ie: typeof) making the exported code invalid.
Input code
const a = typeof 0;

Config
The 3 below has this flaw. I am myself the most interested with the last.
{
  "jsc": {
    "externalHelpers": true,
    "target": "es3"
  }
}

{
  "jsc": {
    "externalHelpers": true,
    "target": "es5"
  }
}

{
  "jsc": {
    "externalHelpers": true,
    "target": "es2015"
  }
}

Observed code
import * as swcHelpers from "@swc/helpers";
var a = swcHelpers._typeof(0);

Expected code
import * as swcHelpers from "@swc/helpers";
var a = swcHelpers.typeof(0);

Version
The version of @swc/core: 1.2.51

After further searches, it looks like this is a duplicate of #1458


[BACKLOG-34345] fixes issue adding unselected elements from dropdown

:white_check_mark: Build finished in 17m
Build command:
mvn clean verify -B -e -Daudit -amd -pl ui

:ok_hand: All tests passed!
Tests run: 1148, Failures: 0, Skipped: 0    Test Results

:information_source:  This is an automatic message


Avoid tedge from updating the base mosquitto.conf directly

Is your feature improvement request related to a problem? Please describe.
The postinst script of tedge updates the /etc/mosquitto/mosquitto.conf directly in-order to /etc/tedge/mosquitto-conf as a directory for tedge mosquitto config extensions. This is very error prone as we're tinkering with the base configuration of mosquitto directly.
Describe the solution you'd like
Mosquitto already provides the directoty /etc/mosquitto/conf.d to keep any config extensions like the bridge configurations that we create. It would be better to use this conf.d directory for the same rather than defining our own config extension.
Even though we can't completely eliminate our dependency on mosquitto with this change, as well still have to create the config extension at /etc/mosquitto/conf.d, it still eliminates one unnecessary dependency.
Additional context
We might need some strategy to make sure that the tedge-mosquitto.conf is loaded first, before other extensions are loaded as the per_listener_settings are enabled in it, which must be loaded first, before loading any other security settings defined in other extensions.

Though we'll have to be careful here as not all mosquitto installations create a /etc/mosquitto/conf.d folder (e.g. fedora does not do this!).

However I much prefer the configuration files being simply added via symlink to the individual mosquitto configurations to the /etc/mosquitto/conf.d/ directory.

This behaviour causes problems when building the system with Yocto.
Module common_mosquitto_config.rs creates file /etc/tedge/mosquitto-conf/tedge-mosquitto.conf which has following content:
per_listener_settings true
connection_messages true
log_type error
log_type warning
log_type notice
log_type information
log_type subscribe
log_type unsubscribe
message_size_limit 268435455
listener 1883 <IP_ADDRESS>
allow_anonymous true
require_certificate false

These are system-wide settings, which are normally managed by files in /etc/mosquitto/conf.d directory, as mentioned by original writer.  The tedge-mosquitto.conf contents conflict with previous settings, thus my solution was just remove the tedge-mosquitto.conf manually after initializing thin-edge in the device.
Also, the default Yocto installation of mosquitto broker already provides settings, which are somewhat compatible with those.
common_mosquitto_config.rs should be modified so that it does not create tedge-mosquitto.conf file at all.

@satel-kalletuulos Sorry we somehow missed your comment. Yes I think using the conf.d directory will lead to being more compatible with different setups (e.g. yocto, containers etc.) and just be more "linux friendly".
However we're also exploring implementing our own bridge functionality to allow for a more flexible approach (e.g. hot reloading of c8y bridge topics), and if that is done, then the number of mosquitto configuration files will be significantly reduced, making it easier overall to managed and switch to the conf.d setup.

@reubenmiller Point in my comment was, that global configuration topics should not be touched without prior permission.
It is likely, that thin-edge will be used in some systems, which don't yet use MQTT, but some systems have already configured MQTT broker. For example, device which acts as a router and MQTT broker to local network, has listener (etc) configurations in place. When thin-edge starts, it forcefully breaks these pre-defined configurations.

@reubenmiller Point in my comment was, that global configuration topics should not be touched without prior permission.
It is likely, that thin-edge will be used in some systems, which don't yet use MQTT, but some systems have already configured MQTT broker. For example, device which acts as a router and MQTT broker to local network, has listener (etc) configurations in place. When thin-edge starts, it forcefully breaks these pre-defined configurations.

Yes that is a very good point and we definitely want to avoid any integration pain, and also generally play nicely with different setups.
Though I'm pretty sure just installing thin-edge.io will not be destructive, the only potentially "unexpected/invasive edit" which is done is the insertion of the line include_dir /etc/tedge/mosquitto-conf into the /etc/mosquitto/mosquitto.conf file...though this line will hopefully not cause any existing mosquitto configuration to stop working as the referenced folder is empty. thin-edge.io only starts adding files to the /etc/tedge/mosquitto-conf folder once a user runs tedge connection xxx...and if they don't want to use specific settings, then they can run tedge config set to control the individual listeners (e.g. change port number etc.) so that it won't impact the existing mosquitto setup.


ValueError: '<P' is not a valid PEP 3118 buffer format string

Required Info

Camera Model
R200

Firmware Version
<IP_ADDRESS>

Operating System & Version
Mac OS X 10.13.6 (17G65) & Ubuntu 18.04.1 LTS (GNU/Linux 4.14.55-146 armv7l)

librealsense version
legacy branch, compiled from github clone

pyrealsense version
2.2

python version
3.7

Running the example code (on Mac OS X), I get the following error:
INFO:pyrealsense.core:There are 1 connected RealSense devices.
INFO:pyrealsense.core:Using device 0, an Intel RealSense R200
INFO:pyrealsense.core:    Serial number: XXXXXXXXXX
INFO:pyrealsense.core:    Firmware version: <IP_ADDRESS>
Traceback (most recent call last):
  File "test_pyrealsense.py", line 17, in <module>
    print(cam.color)
  File "/Users/user/.virtualenvs/test_pyrealsense/lib/python3.7/site-packages/pyrealsense/core.py", line 518, in <lambda>
    return lambda x: get_stream_data(s)
  File "/Users/user/.virtualenvs/test_pyrealsense/lib/python3.7/site-packages/pyrealsense/core.py", line 512, in get_stream_data
    data = lrs.rs_get_frame_data(self.dev, s.stream, ctypes.byref(e))
  File "_ctypes/callproc.c", line 911, in GetResult
  File "/Users/user/.virtualenvs/test_pyrealsense/lib/python3.7/site-packages/numpy/ctypeslib.py", line 183, in _check_retval_
    return array(self)
ValueError: '<P' is not a valid PEP 3118 buffer format string

I get the same error with Linux.

I thought it might be with using version python 3.7, so I tested with 3.6 in Linux, and got the same error:
INFO:pyrealsense.core:There are 1 connected RealSense devices.
INFO:pyrealsense.core:Using device 0, an Intel RealSense R200
INFO:pyrealsense.core:    Serial number: XXXXXXXXXX
INFO:pyrealsense.core:    Firmware version: <IP_ADDRESS>
Traceback (most recent call last):
  File "test_pyrealsense.py", line 17, in <module>
    print(cam.color)
  File "/usr/local/lib/python3.6/dist-packages/pyrealsense-2.2-py3.6-linux-armv7l.egg/pyrealsense/core.py", line 518, in <lambda>
    return lambda x: get_stream_data(s)
  File "/usr/local/lib/python3.6/dist-packages/pyrealsense-2.2-py3.6-linux-armv7l.egg/pyrealsense/core.py", line 512, in get_stream_data
    data = lrs.rs_get_frame_data(self.dev, s.stream, ctypes.byref(e))
  File "_ctypes/callproc.c", line 918, in GetResult
  File "/usr/local/lib/python3.6/dist-packages/numpy/ctypeslib.py", line 183, in _check_retval_
    return array(self)
ValueError: '<P' is not a valid PEP 3118 buffer format string

Seems like the camera is working fine though using the included examples:
$ cpp-headless
There are 1 connected RealSense devices.

Using device 0, an Intel RealSense R200
    Serial number: XXXXXXXXXX
    Firmware version: <IP_ADDRESS>
Writing cpp-headless-output-DEPTH.png, 480 x 360 pixels
Writing cpp-headless-output-COLOR.png, 640 x 480 pixels
Writing cpp-headless-output-INFRARED.png, 480 x 360 pixels
Writing cpp-headless-output-INFRARED2.png, 480 x 360 pixels
wrote frames to current working directory.

I have seen the same error recently too. I'm using conda for my install and doing a re-install did the work for me on python 3.6. I'm still not sure what is the reason : (
If you have some ideas, please post it here.

I am struggeling with the same issue.
Required Info |
-- | --
Camera Model | ZR300
Firmware Version | <IP_ADDRESS>
Operating System & Version | Mac OS X 10.13.6 (17G65)
librealsense version | legacy branch, compiled from github clone
pyrealsense version | 2.2
python version | 2.7 and 3.7
The reason for this issue is a byte order / format character: "<P" in the stream. According to section <IP_ADDRESS> at https://docs.python.org/3/library/struct.html "the 'P' format character is only available for the native byte ordering (selected as the default or with the '@' byte order character). The byte order character '=' chooses to use little- or big-endian ordering based on the host system. The struct module does not interpret this as native ordering, so the 'P' format is not available."
However, I have no idea how to overcome this issue.

I am not really sure what the actual problem is either.
It could be the result of an incompatibility between numpy and ctypes in relations to new commits supporting PEP 3118 buffer protocol.
There is little we do in pyrealsense apart from calling rs_get_frame_data  and setting restype. I tried some different flags when declaring the ndpointer but that has not solved the issue.
Swtiching back to python 3.6 and numpy 1.13 - again through conda - does remove the issue though.

Thanks for the additional testing.
Found this thread: https://github.com/numpy/numpy/issues/11150
which might be related.

I am having this on UP2, I downgraded numpy to 1.14.4 and using Python 3.5 I no longer get the <P error but the camera light (F200) does not come on and captured frames are black. R200 does not work still loads of errors, attempting to get F200 fixed at the moment but now I have no errors/warnings and stumped lol.

This is an upstream bug

This should be fixed upstream - can this issue be closed?


Fixes to xrootd logging config

Changes include:

Xrootd logging now uses the standard logrus logging values
Instead of string comparisons for mapping, we now use log.ParseLevel and compare the levels (which are unsigned ints)
The program now exits when there is an improper config value and returns a proper error
Anywhere these configs are listed, they are all listed alphabetically for consistency and an easier time finding each option
Unit tests for the generation of the xrootd config file

Let me know if I missed anything or need to add anything else!

Note: still need to make the config params more approachable and user-friendly, but thought I'd push my work in progress

Okay @haoming29 cleanup has happened. Just waiting for tests to pass to make sure I didn't remove anything important but I think everything should be good to go!

@joereuss12 You might need to ask @jhiemstrawisc to overwrite Brian's requested change to get this merged in

@Haoming, since you've been reviewing for Brian, can you resolve any of the the conversations that are open that have a fix? Once I see everything resolved, I'll merge

@haoming, since you've been reviewing for Brian, can you resolve any of the the conversations that are open that have a fix? Once I see everything resolved, I'll merge

@jhiemstrawisc  Peek through the conversations and looks to me they have all been taken care of. Resolved conversations accordingly

Perfect, thanks. Just wanted the acknowledgement from someone for bookkeeping since I'm not reviewing myself :) Consider it merged! Thanks to everyone who worked on this


[i18n] Update de-de.json (German Translation)

Best regards from the community-scripts ORG (ProxmoxVE) ;-)
German language updated to 100%

@MickLesk love your work! I will look through this.


correction to css for token titles

┆Issue is synchronized with this Jira Task by Unito

Confirmed with Miccy to merge into staging. If it passes test, we'll bring this across to Devcon Production (styling changes only to improve UI).


Update docs for the weighted τ

This short pull request update the documentation of stats.weightedtau() to clarify the notion of "rank" used.

Hey everyone,
thanks for all the effort regarding the  issue that was brought up. I think removing the note  about using ranks instead of scores (4638-4641) will clear up the confusion  about usage however this may  creates a new issue:
The documentation of weightedtau will  then read like it will always expect scores.  This seems inconsistent with the documentation/usage of kendalltau  which will expect ranks.
The correct solution in my opinion would be to make everything consistent: either use scores everywhere (weightedtau and kendalltau)  or ranks.

Good point. Kendall's original paper consider rankings, but since the correlation is between ranks, there is no difference between passing to the method scores or the associated ranks. Indeed, the SciPy code does not assume anywhere that the argument are rankings. I'm sure no user of stats.kendalltau() ever refrained from using vectors of reals—that's how τ is defined in every book today. But changing the wording might make this clear.

But changing the wording might make this clear.

Did you want to change that, then?

But changing the wording might make this clear.

Did you want to change that, then?

Yes, I think it would be clearer and more up to date with typical usage, but it's not my code.

Yes, I think it would be clearer and more up to date with typical usage, but it's not my code.

I see, so you think this should be merged as-is and kendalltau's documentation should be updated separately?

I see, so you think this should be merged as-is and kendalltau's documentation should be updated separately?

That's a judgment call, and not mine—as I said, I'm not the author of kendalltau(). scipy's documentation refers to "ranking" without defining what a ranking is, and reports a formula quoting "concordant" and "discordant" pairs without defining what they are. So I'm pretty sure users of kendalltau() know what they're doing from other sources (the formula is also written in a uselessly complicated way—look, e.g., at a simpler, alternative form).
It also depends on how you want to be close to the quoted paper by Kendall, which indeed defines the measure for rankings. Wikipedia's page, for example, follows the modern usage—it's a measure of correlation on arbitrary data that depends only on the order of the values, rather on the values themselves.
If you ask me: yes, the documentation of kendalltau() does not follow the current definition and applications of Kendall's τ. I see this as a very minor problem because, hopefully, if you're doing statistics you're not learning measures of ordinal association from scipy's docs :).

That's a judgment call, and not mine—as I said, I'm not the author of kendalltau(). scipy's documentation refers to "ranking" without defining what a ranking is, and reports a formula quoting "concordant" and "discordant" pairs without defining what they are. So I'm pretty sure users of kendalltau() know what they're doing from other sources (the formula is also written in a uselessly complicated way—look, e.g., at a simpler, alternative form).
It also depends on how you want to be close to the quoted paper by Kendall, which indeed defines the measure for rankings. Wikipedia's page, for example, follows the modern usage—it's a measure of correlation on arbitrary data that depends only on the order of the values, rather on the values themselves.
If you ask me: yes, the documentation of kendalltau() does not follow the current definition and applications of Kendall's τ. I see this as a very minor problem because, hopefully, if you're doing statistics you're not learning measures of ordinal association from scipy's docs :).

Ok. I agree that kendalltau documentation could be improved. It's odd that it says "ranks" when the example clearly shows scores. But this PR is an improvement to the weightedtau documentation, so merging. Thanks @vigna, @stde!

Ok. I agree that kendalltau documentation could be improved. It's odd that it says "ranks" when the example clearly shows scores. But this PR is an improvement to the weightedtau documentation, so merging. Thanks @vigna, @stde!


juliac: add CI configuration for compiling and running runic

Hmm, libjulia-internal.dylib isn't found on the macOS runner: https://github.com/fredrikekre/Runic.jl/actions/runs/10700991157/job/29665950017?pr=57


Add OnlySampleNegative in baggingSampling Logic

Current Shifu, user can do negative sampling by setting weight column. To add more functionality, add one hidden parameter for negative sampling only

Done in develop branch


TypeScript definitions for Pixi 3.0.x?

The wiki currently links to the type definitions for a 2.x release of Pixi.
Are there any official Pixi 3.x definitions?

https://github.com/pixijs/pixi-typescript

:+1: Thanks for updating the wiki, too!


Fetching custom properties

Issue
closes #14
Describe your changes
Create a new read-only property (user_properties) in the poi object that loops on jsonData and fetches custom properties of poi.
How to test

Fetch POI information and read user_property inside it
sample Code
if let test = POIs.getPOIbyIdStore(idstore: "leo_family_house"){
      let collectproperty = test.user_properties
      print(collectproperty["myProperty"])
}

Checklist:

[x] My code follows the style guidelines for this repo
[x] I have performed a self-review of my code
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings/errors
[x] I have added tests that prove my fix is effective or that my feature works
[x] I don't require ops changes for this PR to go to prod
[x] This change does not include a migration

Comments

SDK publish 4.0.1


Feature/improved plugin

Adds a Container plugin to the package which allows the client to add a block of people to the page and, using `django-admin-sortable2, allows them to drag and drop the order.

This is good. You should also update the README with this capability.

There will be another PR in the coming days with an update to the admin to allow for more customisation. Will update the readme when those changes are in place as well


.net sdk 1.6.0 notes added

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ ] Feature
[X] Maintenance/Chore

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65fc093d778809aceaa13417--harness-developer.netlify.app


CmPivot File() Date/Time Issues

In my Case i use a
Configuration Manager 1910 Hotfix (KB4537079) https://support.microsoft.com/help/4537079
And when i run :
File('C:\Windows\System32\atmfd.dll')
I experience errors in smsprov.log
##############
*** [22007][241][Microsoft][SQL Server Native Client 11.0][SQL Server]Conversion failed when converting date and/or time from character string.    SMS Provider    25.03.2020 14:33:29    15456 (0x3C60)
~~[22007][241][Microsoft][SQL Server Native Client 11.0][SQL Server]Conversion failed when converting date and/or time from character string.     ThreadID : 15456 , DbError: 241 , Sev: 16~~    SMS Provider    25.03.2020 14:33:29    15456 (0x3C60)
*** [HY010][0][Microsoft][ODBC Driver Manager] Function sequence error    SMS Provider    25.03.2020 14:33:29    15456 (0x3C60)
~~[HY010][0][Microsoft][ODBC Driver Manager] Function sequence error   [22007][241][Microsoft][SQL Server Native Client 11.0][SQL Server]Conversion failed when converting date and/or time from character string.  ThreadID : 15456 , DbError: 0 , Sev: -1~~    SMS Provider    25.03.2020 14:33:29    15456 (0x3C60)
CMPivotQuery failed to run query.    SMS Provider    25.03.2020 14:33:29    15456 (0x3C60)
######################
File('C:\Windows\System32\atmfd.dll')| projectDevice,Filename
It works when i don´t reutrn date/time....
Looks like a bug in Configuration Manager 1910 Hotfix (KB4537079)
If you have this issue exclude date/time in the returned properties ;-)
https://social.technet.microsoft.com/Forums/en-US/93923b1c-011a-4fb3-b606-c379e4814f3f/cmpivot-returns-no-results-for-some-queries?forum=ConfigMgrCBGeneral

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

ID: f0c8158c-1c8e-1567-d96d-222f5b4aec21
Version Independent ID: f6674943-3564-2250-2334-b88c42f3a8a6
Content: CMPivot for real-time data - Configuration Manager
Content Source: sccm/core/servers/manage/cmpivot.md
Product: configuration-manager
Technology: configmgr-other
GitHub Login: @mestew
Microsoft Alias: mstewart

Thanks @PehDeh for taking the time to share this with the Configuration Manager documentation team. I’m sorry that you’re having problems, and I want to make sure it gets to the right people that can help. There are a couple of options available to provide the best level of support for this:

Post on Configuration Manager forums. These are moderated by our community MVPs who are very experienced, knowledgeable, and helpful.
Use Microsoft Support to search for the issue, or open a case with professional support.
Contact your Microsoft Premier team, such as a Premier Field Engineer or Technical Account Manager.
I'm closing this issue as there's nothing actionable for docs at this time.


AutoMapper bug

Explicitly creating maps between types instead of member mapping

You had mentioned (on twitter) that it looked like there were never proper mappings for the various entity types, and so this PR fixes that (thanks!), but I have a question -- why isn't the Properties dictionary done in a similar way to the rest of the entity classes that required mapping?

And just to allow my discovery process unwind here some more... I guess the mapping requires assigning the entire dictionary, rather than trying to map items in the dictionary. So this leads me to believe that mapping a dictionary in the way we have it is not inherent in AutoMapper, whereas collections are (and I was using those without even thinking/realizing).

I'll merge this, since I need/want to fix my other entities to follow this approach. If you get around to my question about, that'd be great.
Thanks! #jimmystyle


How to work on Nested URL?

prefix('shop/:shop_id').
get('/item/:item_id', 'shop_item')

shop/5c41b7bc52fd6700080461c6/item/5c49c024a72f4c00092a2495/properties
Any other alternative way around?
Something like nested routes in https://github.com/alexmingoia/koa-router

@jeffijoe Sorry for not updating you sooner.
I have custom built a own library on top of https://github.com/zensh/route-trie which even support
Awilix.I will release it soon.
Thank you.


feat: verify claims in provenance match the certificate

I made a change to cache the TUF root during the execution. This should help with regression tests (see function TrustedRootSingleton()).
Additional e2e tests need to be created https://github.com/slsa-framework/slsa-verifier/issues/571
closes https://github.com/slsa-framework/slsa-verifier/issues/580
closes https://github.com/slsa-framework/slsa-verifier/issues/570

I didn't take a really close look at the tests but they looked mostly ok to me.

All comments addressed. PTAL

@asraa can you take a look?

I completely messed up the unit tests. Will take a look later

@ianlewis not sure what's wrong with the linter. I've tried to disable the deprecated method check but it's still failing:
Error: directive `//nolint:staticcheck we want to disable SA1019 only to use deprecated methods but there is a bug in golangci-lint.` should match `//nolint:staticcheck we want to disable SA1019 only to use deprecated methods but there is a bug in golangci-lint.[:<comma-separated-linters>] [// <explanation>]` (nolintlint)

Context: https://github.com/golangci/golangci-lint/issues/741#issuecomment-784171870
I tried disabling the linter in builder.go and builder_test.go.

@ianlewis not sure what's wrong with the linter. I've tried to disable the deprecated method check but it's still failing:
Error: directive `//nolint:staticcheck we want to disable SA1019 only to use deprecated methods but there is a bug in golangci-lint.` should match `//nolint:staticcheck we want to disable SA1019 only to use deprecated methods but there is a bug in golangci-lint.[:<comma-separated-linters>] [// <explanation>]` (nolintlint)

Context: golangci/golangci-lint#741 (comment) I tried disabling the linter in builder.go and builder_test.go.

The //nolint declarations are fairly particular and can't have a leading space and need to have a // delimiter before the comment message. I updated the comments.

The //nolint declarations are fairly particular and can't have a leading space and need to have a // delimiter before the comment message. I updated the comments.

Thanks!


[FE] Header fix request

Upon clicking on the 'Create account button, it shows 'Hi, {firstName}' in the header even though the user hasn't signed in yet.

Hi Younghyun,
Good job on finding the bug!
I fixed it by doing the following:
Back-end
I changed the register controller to return just success message instead of user data.
I figured that we do not need the user data as a response to register action.
(If we do, it will affect the header which takes in user.firstName and result in showing the unlogged-in user name)
-Before:
res.json({
      user: {
        firstName: user.firstName,
        lastName: user.lastName,
        email: user.email,
        role: user.role,
        _id: user._id,
      },
      token,
    });

-After:
 res.json({
      registrationStatus: "success",
    });

Front-end
In RegisterForm.js, upon registering, it used to receive user data from backend(as shown above) and save it in auth global state, which is then used on the header to show firstName.
On the front-end, I changed the code to not to set auth global state anymore(in fact, there is no data to save anymore since we altered the backend response), and in addition, it now shows a modal that notifies the end user that an e-mail verification was sent to their email address.
-Before:
// actions after successful registration
setAuth({ ...auth, token: data.token, user: data.user });
toast.success(`${data?.user?.firstName} Thank you for joining the club!`);
navigate(`/login`);

-After:
// actions after successful registration
 setIsModalOpen(true);


Fix permanent hover for touch screen devices

Partly fix #15

Now there is a problem with the priority of the :active selector and :hover. :active selector is overridden with :hover


Adding custom parameters to the command

So I'm trying to execute the follwoing:
$media = FFMpeg::fromDisk('shared_host')->open('axis-ACCC8E592904\20180221\15\20180221_155150_E932_ACCC8E592904\20180221_15\20180221_155150_E932_ACCC8E592904.mkv')
                                                ->export()
                                                ->inFormat(new \FFMpeg\Format\Video\X264)
                                                ->save('axis-ACCC8E592904\20180221\15\20180221_155150_E932_ACCC8E592904\20180221_15\test.mp4');

which works as it should, but I don't want any quality loss of the converted video... (it needs to be MP4, but size doesn't matter)... How should I get the quality not to get lost here?
I thought adding -qscale 0 would do the trick, but I have no clue what so ever on how to do this.

Adding custom filters is described in the README: https://github.com/pascalbaljetmedia/laravel-ffmpeg#usage

Yes, I added some, that DOES NOT WORK....
$media = FFMpeg::fromDisk('shared_host')->open("{$path}\\{$recording_id}.mkv")
                                                ->export()
                                                ->inFormat(new \FFMpeg\Format\Video\X264)
                                                ->addFilter(['-qscale', 0])
                                                ->save("{$path}\\{$recording_id}.mp4");

Gives the same output as code mentioned in the begin question.... also ->addFilter(['-qscale 0']) gives the same (big) quality loss on the file. If you see the file size difference it states enough; https://i.imgur.com/VGmNJfG.png

No need to use all caps.


AG News Dataset

Hi, I was just wondering if I can obtain model parameters and the poison dataset for AG News as shown in the paper.
I tried to generate the poisoned AG News dataset for BadNet by myself (5 random rare word triggers in random position of the sentence) but both the ASR and the CACC of the BERT model remained around 88% to 90% during the testing phase, while the paper suggests an ASR: 100% and CACC: 93.97%.  Is the model parameter same as the model for SST-2 and offenseval?
Screenshot of the Training:

I was also wondering if I can get the dataset for BN(m) and BN(h) if possible.
I will be waiting for the reply :)

Hi, thanks for watching!
I've uploaded BN(m) & BN(h) & Badnets to Google Drive. It will be available for around 5 days. Thanks!
And actually, I don't know what you mean by "Is the model parameter the same as the model for SST-2 and offenseval". We train these models on different poison datasets so the parameters are definitely different.
For the lower attack success rate, maybe the training paradigm should be adjusted. We follow the standard hyper-parameters setting (our default implementation).
If it still doesn't work, pls feel free to let me know. And it would be great if you can provide more detailed information (e.g. hyper-parameters setting, et al).
Can directly find me at<EMAIL_ADDRESS>

Thank you for the reply!
For this "Is the model parameter the same as the model for SST-2 and offenseval": I was referring to the hyperparameter for the model setting.


fix: alvr_client_core stability issues on smartphone androids

low-latency feature crashes on smartphone android, hence made it as a default-enabled feature https://github.com/PhoneVR-Developers/alvr-cardboard/issues/5

Building for x86 arch enables faster AVD emulation, wider client_core compatibility

Android enforces only x86 emulator images to run on x86 hosts from API 28 - https://stackoverflow.com/a/74819011

we can actually stably build for other ABIs as well but waiting for confirmation from https://github.com/googlevr/cardboard/pull/400
and fixes from upstream module https://github.com/rust-lang/socket2/issues/433

some useful logging

future todo: build for remaining two ABIs (ref: https://developer.android.com/ndk/guides/abis)

if you add another target (x86_64) expose it as a flag in xtask.
I felt that it would be redundant, let us build the client_core for widest compatibility and let the client implementation choose which ever ABI they wish to use (which gradle/cmake would automatically pickup). I actually wanted to do -t arm64-v8a -t armeabi-v7a -t x86_64 -t x86 but was waiting for aforementioned issues to be solve.

You also need to expose it for prepare-deps to download the toochain.
True, that would be a pr to alvr-cardboard repo

You don't need to expose a low latency flag. you are just modifying settings defaults, which should be accessed from the dashboard directly. The issue is that we didn't implement support for dictionaries yet.
True, its actually weird that low-latency (well documented flag) crashes with UNKNOWN error. That is default enabled on alvr_client_core, and crashes smartphone androids. I don't think we can request all smartphone android implementations to post installation first goto alvr dashboard and disable that flag :( Thought this would be best wayforward. what do you suggest ?

True, its actually weird that low-latency (well documented flag) crashes with UNKNOWN error. That is default enabled on alvr, and crashes smartphone androids. I don't think we can request all smartphone android implementations to post installation first goto alvr dashboard and disable that flag :( Thought default-enabled-feature would be best wayforward. what do you suggest ?

This is what I expected the user to do e.g. for an earlier version, where FFR would break the image on the GearVR. But indeed I agree we should apply fixes automatically if possible. The tricky part is detecting which devices support the flag and which don't. Also settings are set on the server side, so the feature flag you put doesn't make sense. My solution would be to add the feature flag on alvr_client_core, and when the client receives the mediacodec options, search for the low-latency entry and remove it conditionally.

This is what I expected the user to do e.g. for an earlier version, where FFR would break the image on the GearVR. But indeed I agree we should apply fixes automatically if possible. The tricky part is detecting which devices support the flag and which don't. Also settings are set on the server side, so the feature flag you put doesn't make sense. My solution would be to add the feature flag on alvr_client_core, and when the client receives the mediacodec options, search for the low-latency entry and remove it conditionally.

This is exactly what I did. alvr/alvr_client_core uses alvr/session too. When client_core is built its pulling in session/settings. And by default, server or default alvr_client_core, when using alvr/sessions will have low-latency enabled. Only when alvr_client_core is built with --no-default-features, low-latency will be removed from alvr/sessions and pulled into alvr_client_core. alvr/sessions is rightly being shared between client and server. I have tested this.

No, it's not working correctly. Changing the defaults on the client will do nothing since the settings are pulled from the server. If it works for you it's because you recompile the server without the flag and we don't want to have a separate server build for the cardboard version.

removed default "low-latency" flag, since it crashes on some clients
Upstream merged fixes (https://github.com/rust-lang/socket2/pull/434), now can build for all ABIs

That's good. So in the end the reason i'm ok with this is because we are still setting the vendor specific qcomm low latency flag. It's still missing the installation of the other targets in prepare-deps.

Updated deps ?

https://github.com/googlevr/cardboard/pull/400 Upstream updated, cardboard-sdk can now be built for x86, x86_64 (instructions are now added to https://developers.google.com/cardboard/develop/c/quickstart#enable_android_studio_x86_emulator).
Those changes have to be made manually to sdk codebase (to enable building) which are readily available @ https://github.com/ShootingKing-AM/cardboard/tree/phonevr


useful-programs: Mention ayatana-webmail

It's the best modern mail notification application I've seen, and it's not well known enough IMO.

Yes it got merged, but there is no release yet that includes that patch.

Yeah, but they've only made one release and that was nearly three years ago.
I'm happy to accept links to any useful programs, but linking to patches seems a bit much.
I suggest poking Ayatana into making a release, then everyone benefits.

I too thought they haven't made a release in 3 years, but they did made git tags. In anycase, thinking about it, that's not an important detail, as this feature is still useful - whether you have multiple mbsync accounts or not. I removed that last sentence.


az ad app permission admin-consent broken

Related command
az ad app permission admin-consent --id <appId>
Describe the bug
Error:
Failed to connect to MSI. Please make sure MSI is configured correctly.
Get Token request returned: <Response [400]>

To Reproduce
Create a service principal and assign tenant roles:
az ad sp create-for-rbac --name test-name \
                         --role owner \
                         --scopes /subscriptions/<subscriptionId>

az ad app permission add --id <appId> \
                         --api 00000003-0000-0000-c000-000000000000 \
                         --api-permissions e1fe6dd8-ba31-4d61-89e7-88639da4683d=Scope \
                         1bfefb4e-e0b5-418b-a88f-73c46d2cc8e9=Role \
                         62a82d76-70ea-41e2-9197-370581804d09=Role \
                         19dbc75e-c2e2-444c-a770-ec69d8559fc7=Role

az ad app permission admin-consent --id <appId>

Expected behavior
Creates the service principal, assigns API permissions, and then grants consent to those permissions.
Environment Summary
Linux-5.4.0-1100-azure-x86_64-with-glibc2.35 (Cloud Shell), CBL-Mariner/Linux
Python 3.9.14
Installer: RPM

azure-cli 2.44.1

Extensions:
aks-preview 0.5.64
ai-examples 0.2.5
ml 2.12.1
ssh 1.1.3

Dependencies:
msal 1.20.0
azure-mgmt-resource 21.1.0b1

Additional context
I've read from other GitHub issues elsewhere that this command is being deprecated. But, I need a viable workaround ASAP because our entire company's onboarding system for Azure customers is dependent on being able to grant admin consent.

@jiasli for awareness

I am running into the same issue - are there any temp workaround suggestions?
Running:
az ad app permission admin-consent --id
Returns:
Failed to connect to MSI. Please make sure MSI is configured correctly.
Get Token request returned: <Response [400]>

As explained in https://github.com/Azure/azure-cli/issues/12137#issuecomment-596567479, az ad app permission admin-consent doesn't work in Cloud Shell.
You may use a local machine and log in with your user account to make it work.

Thank you for replying.
Does it make sense to update Microsoft documentation and note that "az ad app permission admin-consent" doesn't work in Cloud Shell?
documentation link:
https://learn.microsoft.com/en-us/cli/azure/ad/app/permission?view=azure-cli-latest#az-ad-app-permission-admin-consent


Shelly Duo color temperature not working

Added Shelly Duo to my Hubitat Elevation <IP_ADDRESS>.
Changing color temperature works from the direct interface on the bulb, but from Hubitat does not work 100%. It's only possible to set either 2700 or 6500, no values in between. Setting values < 6500 sets to 2700 only. If I enter 6500 and above, then it sets to 6500.

I just checked this and it works for me. How are you trying to set it? The dashboard or device page?

It’s working fine after I upgraded the firmware to the latest version. When I first installed the bulbs it didn’t tell me that a new firmware was available.
Closing the issue.