port buildbot_travis to buildbot nine

The UI needs to be rewritten, but we have a working travis spawner, with git scm.
I don't want to spend too much time testing with svn, but I dont think this should be hard.
I think we should eventually push this project to upstream.
This branch still needs some changes to upstream:
https://github.com/tardyp/buildbot/tree/travis

added some nice configuration U via plugins.

So can we do something about the license?
If it were changed, I could look into taking bits and porting them to Buildbot's master...

Wow, that UI looks slick!
I've made an eight branch and changed the licence there to the same one as buildbot.
@tardyp - if it's OK with you i'll merge this as is, and then make the same licence change? (I figure the merge/rebase would be annoying)
Going forward, given everyone looking at this is already a buildbot committer, I could move the repo there?
Or we could aim to merge it all upstream?

Jc2k, you can merge it as is.
I am okay for GPLv2 for my contributions
I am also okay for merging this all in upstream (probably mark it experimental though)


New Theme: Zdoc

Theme submission
Please make sure that you have read the theme submission guidelines before submitting a theme. The guidelines provide all relevant information and requirements that have to be fulfilled before the submission. Please tick the relevant boxes for your theme in the checklist below:
Link to my theme repository: https://github.com/zzossig/hugo-theme-zdoc
I made sure that...

[x] the repository contains a good README.md describing my theme
[x] an open source license has been added to LICENSE.md
[x] all metadata have been added to theme.toml
[x] screenshots have been added in the images/ folder with the required dimensions
[x] in case I'm using a customized demo via the exampleSite folder that

[x] https://example.com is set as base url in exampleSite/config.{toml, yaml, json} to avoid the abuse of unused domains
[x] I tested that my theme's demo works with the content directory of gohugoio/HugoBasicExample

[x] I tested my theme against the gohugoio/HugoBasicExample

[x] I've checked the developer tools' console in my browser for error messages

[x] in case my theme is using Hugo Pipes features like toCSS and PostCSS that I have committed the /resources directory with all generated assets, for my theme to work in the basic version of Hugo

N.B. By submitting a theme to the Hugo Themes Showcase you understand that you need to maintain your theme. You will need to keep an eye on whether your theme's demo generates on the Hugo website, whenever there is a new release. We are a very small team and we just cannot keep up opening issues in the various theme repositories to notify authors. Whenever a theme demo breaks and remains broken then at some point it will be removed from the list without prior warning. If you no longer wish to maintain a theme please let us know.
Feel free to ask questions. We're glad to help.

Hello @zzossig
I have noticed the following issues with your theme submission:

In line 16  of exampleSite/content/_index.md you have entered a URL to /about however you have not provided this content file and therefore the Get Started button throws a 404.

The search functionality does not work when I test your theme demo. I cannot provide further feedback since debugging Javascript is beyond the scope of feedback that we are able to offer.

The line 8 of exampleSite/static/manifest.json mentions your other theme instead of this one.

The GitHub link on the menu also points to your other theme instead of this one.

Once you look into the above please let me know.

Hi, @onedrawingperday
Thank you for the feedback.
But I test the search on the local environment, but it works well on my end.
It also works well when I deployed my site to a host server.
Can you tell me how you tested it? So I can reproduce it on my end

@zzossig
As mentioned in the README the Hugo Themes Showcase has its own Build Script.
Instructions to test your theme with the Build Script locally are provided here
But in your case, for the theme demo to generate properly, you would also need to add your theme's name i.e. 'hugo-theme-zdoc' in the array of line 179 of _script/generateThemeSite.sh
When testing your theme, the browser console returns the following ERROR:
[404]Error: Not Found en:375:19
    onload http://localhost:1313/theme/hugo-theme-zdoc/en/:375

The console ERROR is the one you have specified in line 378  of layouts/partials/head/scripts.html
The problem appears to be in lines 356-359 of layouts/partials/head/scripts.html. You point fuse.js to the host root and as mentioned in the Common Permalink Issues of the README:

Make sure not to use a forward slash / in the beginning of a URL, because it will point to the host root and Hugo will not generate the correct URL for the demo's assets.

@onedrawingperday
Thanks for the degging.
I checked that the zzo theme and the zdoc theme has the same search logic.
I'm quite sure that the search is just not working in the local environment.
Once the zdoc theme deployed to the exampleSite, the search will work.
I fixed other issues too.

@zzossig
I hadn't noticed the addition of search to your other theme.

When I test the search functionality in the live demo by entering for example the keyword markdown I am indeed getting a list of search results.

When I place my cursor above the search results I can see that they point to proper URLs

However when I click on a search result the dropdown list with search results disappears and there is no way to click through the search result.

I am seeing the above behavior with the latest Firefox 72.0.02 on both macOS, and Xubuntu 18.04
Can you please fix this?
By the way I do not quite understand why you perform all those baseURL checks when loading the lunr.js index your Javascript, but just in case you don't know there is a Hugo variable to detect whether a website is served with the local Hugo server and that is .Site.IsServer

@onedrawingperday
I fixed the search bug.

By the way I do not quite understand why you perform all those baseURL checks

Thanks for pointing it!  I deleted that part. Instead, I use .permalink for the search URL.
I tested the zdoc theme with the Hugo Themes Site Build Script. All seems to be fine, but some style code is not imported. It's weird. It's only happened when I tested with the build script. Since I have added the generated resource file, the theme might work well in the example site.

@zzossig
I confirm the fix. I added your theme to the repo in  f701d71

@digitalcraftsman
This is a multilingual documentation theme.

@zzossig could you please update the name of your theme in theme.toml, i.e. changing zzo to Zdoc?
While looking for your www.themes.gohugo.io I noticed another theme called zzo which confused me at first.

@digitalcraftsman
Opps I just updated sorry

@digitalcraftsman
I updated the theme in fee1d12

Thank you @zzossig for the fix and @onedrawingperday for updating the theme. I was just about to do it myself.
@zzossig your theme will promoted on Hugo's official Twitter account soon.


Feature/baln token

IntegrationTests are probably failing since in python we had to toggle enable snapshots, which now instead disables it when it begins as enabled

IntegrationTests are probably failing since in python we had to toggle enable snapshots, which now instead disables it when it begins as enabled

Tests are failing for Governance#executeVote
and on dividends, where there is assertion for dividends to be true but actual is false. This should be coming from the changes made on dividends where the lp fees are removed but not in tests.


feat(rds): add support for monitoring to DatabaseCluster

Lets a user specify a monitoring interval period. This change will also auto-generate a valid Role to manage DB instances monitoring.
This change adds an optional prop monitoringInterval
closes #2826

Pull Request Checklist

[x] Testing

Unit test added (prefer not to modify an existing test, otherwise, it's probably a breaking change)
CLI change?: coordinate update of integration tests with team
cdk-init template change?: coordinated update of integration tests with team

[x] Docs

jsdocs: All public APIs documented
README: README and/or documentation topic updated
Design: For significant features, design document added to design folder

[x] Title and Description

Change type: title prefixed with fix, feat and module name in parens, which will appear in changelog
Title: use lower-case and doesn't end with a period
Breaking?: last paragraph: "BREAKING CHANGE: <describe what changed + link for details>"
Issues: Indicate issues fixed via: "Fixes #xxx" or "Closes #xxx"

[ ] Sensitive Modules (requires 2 PR approvers)

IAM Policy Document (in @aws-cdk/aws-iam)
EC2 Security Groups and ACLs (in @aws-cdk/aws-ec2)
Grant APIs (only if not based on official documentation with a reference)

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

Other than that, looks good!

Needs a merge from master, unfortunately :(

@rix0rrr rebased!

@rix0rrr rebased!

and rebased again :)

AWS CodeBuild CI Report

Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Archive themes float with window at a certain width

In both Safari and Chrome, Archive Main Page (card catalog) themes float and overlap when window is at a certain width.

@a-murry I've fixed this, but it's not perfect--if you're resizing the browser it can still get a little funky. But there should no longer be a browser width that is this weird if you reload the page. Assuming this is fine because for the most part people aren't going to be resizing the screen this way, but let me know if not.


Add hagezi’s lists

Hagezi has some lists that would be perfect with the current lists on dnswarden. There are 4 lists here that are adblocking and 1 list for malware blocking. I hope I filled these out as you wanted. You can find more information on these lists at https://github.com/hagezi/dns-blocklists

Merged it, should be live in couple of minutes.


[typescript-react-query] add ability to customize react-query key with a directive

Is your feature request related to a problem? Please describe.
The react-query key is automatically generated from the query name, but there are situations where you might want to change the query key (e.g. for easier invalidation).
Describe the solution you'd like
Add a @reactQueryKey directive on QUERY to allow customizing the generated key.
Describe alternatives you've considered
Add an argument to the generated hook that allows specifying the key. This might be useful but also feels like it could be overkill.

I don't know if my comment is related to this problem but I have a problem when using the generated hook by codgen and react-query plugins
I simply wrote a js file to match a pattern then change it to my needs
const fs = require('fs');

const filePath = 'src/generated/graphql.ts';
fs.readFile(filePath, 'utf8', (err, data) => {
  if (err) {
    console.error(err);
    return;
  }

  const pattern =
    /export const (\w+) = <TData = (\w+), TError = unknown>\(\s*(variables: \w+,\s*options\?: \w+<[^>]+>)\s*\)\s*=>\s*useQuery<([^>]+)>\(\s*\[([^\]]+)\]/gm;

  const modifiedContent = data.replace(
    pattern,
    (match, functionName, TData, variables, returnType, defaultQueryKey) => {
      const modifiedDeclaration = `export const ${functionName} = <TData = ${TData}, TError = Error>(${variables}, queryKey?: Array<unknown>) =>  useQuery<${returnType}>(queryKey ?? [${defaultQueryKey}]`;
      return modifiedDeclaration;
    }
  );

  fs.writeFile(filePath, modifiedContent, 'utf8', (err) => {
    if (err) {
      console.error(err);
      return;
    }
    console.log('File updated successfully!');
  });
});

before:
export const useGetAllCountriesQuery = <TData = GetAllCountriesQuery, TError = unknown>(
  variables: GetAllCountriesQueryVariables,
  options?: UseQueryOptions<GetAllCountriesQuery, TError, TData>
) =>
  useQuery<GetAllCountriesQuery, TError, TData>(
    ['GetAllCountries', variables],
    useAxios<GetAllCountriesQuery, GetAllCountriesQueryVariables>(GetAllCountriesDocument).bind(
      null,
      variables
    ),
    options
  );

after:
export const useGetAllCountriesQuery = <TData = GetAllCountriesQuery, TError = Error>(
  variables: GetAllCountriesQueryVariables,
  options?: UseQueryOptions<GetAllCountriesQuery, TError, TData>,
  queryKey?: Array<unknown>
) =>
  useQuery<GetAllCountriesQuery, TError, TData>(
    queryKey ?? ['GetAllCountries', variables],
    useAxios<GetAllCountriesQuery, GetAllCountriesQueryVariables>(GetAllCountriesDocument).bind(
      null,
      variables
    ),
    options
  );

hope this solves others problem

I was actually wondering if outputing the directives into the query/mutation metadata made sense, so you could do invalidation kind of like in this post https://tkdodo.eu/blog/automatic-query-invalidation-after-mutations
type Mutation {
  addLogin(args: LoginLogoutArgs!): [LogItem!]! @authorize(roles: ["CompanyEdit"]) @invalidates(keys: [Logins''])
}

would end up generating
useMutation([key], fn, {
 meta: {
 directives: {
    authorize: { roles: ["CompanyEdit"] },
    invalidates: { keys: ["Logins"] }
 }
})

Then you could override the queryClient on settled or something to do the invalidation


DCJ-649: Use OidcBroker for sign-out functionality

Addresses
https://broadworkbench.atlassian.net/browse/DCJ-649

Partially addresses https://broadworkbench.atlassian.net/browse/DCJ-89
Adds unit tests to start the coverage of auth.ts: https://broadworkbench.atlassian.net/browse/DCJ-328
Adds unit tests to start the coverage of oidcBroker.ts: https://broadworkbench.atlassian.net/browse/DCJ-330

Summary

This PR tries to carry forward the effort started in https://github.com/DataBiosphere/duos-ui/pull/2611
This implements a single feature - Sign Out via OIDC.
auth.ts is a minimized version of auth.ts in the above PR
oidcBroker.ts is a minimized version of oidcBroker.ts in the above PR
Due to testing, I updated the component test action to store failure screenshots for review.

Follow-on work is defined in a variety of tickets under the DUOS-2534 epic.
Testing Notes
Testing should include reviewing the developer panel in a browser when logging into a local instance.

Signing in is unchanged so there should be no regressions
Sign-out mimics the original implementation but additionally uses OidcBroker to invoke OIDC library functionality. This will be expanded in future work that layers in additional sign-in functionality
Inspecting local session storage should show user info when logged in, and cleared out when signed out.

Have you read Terra's Contributing Guide lately? If not, do that first.

Label PR with a Jira ticket number and include a link to the ticket
Label PR with a security risk modifier [no, low, medium, high]
PR describes scope of changes
Get a minimum of one thumbs worth of review, preferably two if enough team members are available
Get PO sign-off for all non-trivial UI or workflow changes
Verify all tests go green
Test this change deployed correctly and works on dev environment after deployment

This looks reasonable - I am curious how it works with sign in using previous auth, but sign out using oidc? Presumably its backwards compatible because Google Auth is included within OIDC?

Both sign-in and sign-out are fully functional. Sign-in is the bigger lift so I'm working on that now, but separately. The sign-out exercises both the old way of clearing local storage as well as triggering the OIDC library sign-out functionality.


Thanks

Just opened this to say a big thanks.

You're welcome @necenzurat, I hope this package has been helpful 😄

yes, i always hated setting up a bootstrap theme in Laravel. This was enjoyable.


tarsstat service crashes

What language are you using?
C++
What operating system (Linux, Ubuntu, …) and version?
CentOS Linux release 7.4.1708 (Core)
What runtime / compiler are you using (e.g. jdk version or version of gcc)
gcc version 4.8.5 20160623 (Red Hat 4.8.5-16)
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
coredump info:
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/local/app/tars/tarsstat/bin/tarsstat --config=/usr/local/app/tars/tarsnode'.
Program terminated with signal 6, Aborted.
#0  0x00007f4dd69e51f7 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install glibc-2.17-196.el7.x86_64 libgcc-4.8.5-16.el7.x86_64 libstdc++-4.8.5-16.el7.x86_64
(gdb) bt
#0  0x00007f4dd69e51f7 in raise () from /lib64/libc.so.6
#1  0x00007f4dd69e68e8 in abort () from /lib64/libc.so.6
#2  0x00007f4dd69de266 in __assert_fail_base () from /lib64/libc.so.6
#3  0x00007f4dd69de312 in __assert_fail () from /lib64/libc.so.6
#4  0x0000000000574ca1 in tars::TC_HashMap::Block::refreshSetList() ()
#5  0x0000000000578a46 in tars::TC_HashMap::set(std::string const&, std::string const&, bool, std::vector<tars::TC_HashMap::BlockData, std::allocatortars::TC_HashMap::BlockData >&) ()
#6  0x00000000004b5eae in StatHashMap::add(tars::StatMicMsgHead const&, tars::StatMicMsgBody const&) ()
#7  0x00000000004abd7e in StatImp::addHashMap(tars::StatMicMsgHead const&, tars::StatMicMsgBody const&) ()
#8  0x00000000004ac506 in StatImp::reportMicMsg(std::map<tars::StatMicMsgHead, tars::StatMicMsgBody, std::lesstars::StatMicMsgHead, std::allocator<std::pair<tars::StatMicMsgHead const, tars::StatMicMsgBody> > > const&, bool, tars::TC_AutoPtrtars::TarsCurrent) ()
#9  0x00000000004b4bc2 in tars::StatF::onDispatch(tars::TC_AutoPtrtars::TarsCurrent, std::vector<char, std::allocator >&) ()
#10 0x00000000004ef4bc in tars::Servant::dispatch(tars::TC_AutoPtrtars::TarsCurrent, std::vector<char, std::allocator >&) ()
#11 0x00000000004f5ec9 in tars::ServantHandle::handleTarsProtocol(tars::TC_AutoPtrtars::TarsCurrent const&) ()
#12 0x00000000004f6855 in tars::ServantHandle::handle(std::shared_ptrtars::TC_EpollServer::RecvContext const&) ()
#13 0x000000000056b07b in tars::TC_EpollServer::Handle::handleImp() ()
#14 0x00000000004f1c8b in tars::ServantHandle::run() ()
#15 0x00000000005a6a4a in tars::TC_Thread::threadEntry(tars::TC_Thread*) ()
#16 0x00007f4dd73402b0 in ?? () from /lib64/libstdc++.so.6
#17 0x00007f4dd779ee25 in start_thread () from /lib64/libpthread.so.0
#18 0x00007f4dd6aa834d in clone () from /lib64/libc.so.6
(gdb)
ipcs info:
[tars@localhost tarsstat]$ ipcs
------ Message Queues --------
key        msqid      owner      perms      used-bytes   messages
------ Shared Memory Segments --------
key        shmid      owner      perms      bytes      nattch     status
0x61005e3e 0          root<PHONE_NUMBER>    0
0x62005e74 32769      root<PHONE_NUMBER>    0
0x610048e3 65538      root<PHONE_NUMBER>    0
0x620048e5 98307      root<PHONE_NUMBER>    0
0xffffffff 131076     root<PHONE_NUMBER>    0
------ Semaphore Arrays --------
key        semid      owner      perms      nsems
tarsstat.log:
[ModifyIndex      = 1]
[OnlyKeyCount     = 0]
[MaxHash          = 2]
[OnlyKeyCount     = 0]
[MaxHash          = 2]
[MinHash          = 0]
[AvgHash          = 1.00568]

[DiffBlockCount   = 2]
[BlockSize        = 203][BlockCount       = 15362][BlockAvailable   = 15330]
[BlockSize        = 331][BlockCount       = 15362][BlockAvailable   = 15207]
2020-03-20 09:40:48|140707099219840|DEBUG|initDataBlockSize size: 128, 256, 2
2020-03-20 09:40:48|140707099219840|INFO|init hash mem，shm key: 0xffffffff
2020-03-20 09:40:48|140707099219840|INFO|
[Version          = 0.3]
[ReadOnly         = 0]
[AutoErase        = 0]
[MemSize          = 8388608]
[Capacity         = 8203308]
[SingleBlockCount = 15362 ]
[AllBlockChunk    = 30724]
[UsedChunk        = 187]
[FreeChunk        = 30537]
[MinDataSize      = 128]
[MaxDataSize      = 256]
[HashCount        = 15373]
[HashRadio        = 2]
[ElementCount     = 177]
[SetHead          = 3317897]
[SetTail          = 3318228]
[GetHead          = 3318228]
[GetTail          = 3317566]
[DirtyTail        = 3318228]
[SyncTail         = 0]
[SyncTime         = 600]
[BackupTail       = 0]
[DirtyCount       = 177]
[GetCount         = 95341]
[HitCount         = 95164]
[ModifyStatus     = 1]
[ModifyIndex      = 1]
[OnlyKeyCount     = 0]
[MaxHash          = 2]
[MinHash          = 0]
[AvgHash          = 1.00568]

[DiffBlockCount   = 2]
[BlockSize        = 203][BlockCount       = 15362][BlockAvailable   = 15330]
[BlockSize        = 331][BlockCount       = 15362][BlockAvailable   = 15207]
2020-03-20 09:40:48|140707099219840|INFO|StatServer::initHashMap init multi hashmap end...
2020-03-20 09:40:48|140707099219840|INFO|StatServer::initialize iSelectBuffer:0
problem  temporary Solution：
ipcrm -M 0xffffffff

shared memory is broken, delete ipc shm, and restart


[Linear] Copy ID and Title in one hotkey

Extension – Linear
Author: @thomaslombart

Describe the feature and the current behavior/state.
When I track what I've worked on during the day in my other applications, I like to have the ID and the Title (so I have context on what it means) of the linear issue I worked on. I have to do several keystrokes to do this as there are just separate copy actions for ID and title but not together.
EXAMPLE ACTION: Copy ID and Title
OUTPUT:  STE-749 Fix bug on position input component
Who will benefit with this feature?
Anyone who wants more context than the ID or just title alone
Any Other info.

Thanks for the feedback. Right now, the extension has the same copy actions as Linear.
This copy action seems specific to your workflow and I'm afraid adding it would bloat the actions. I'm thinking instead of something more customizable: a preference on which you can define a template of what to copy (e.g {ISSUE_ID} {ISSUE_TITLE}).
Then we could add an option (called "Custom copy" or something similar) so that other users could define their preferred format, regardless of their workflow. What do you think?

Love that idea!


Create an empty mesh section on packaged versions causes a crash

As the title says : If you try to create a mesh section without any triangles on packaged version, the game will crash instantly, regardless of the settings you input in the node.

Can we see some code please?

Well, just add the Create mesh section and set all the arrays to empty.

Yes it asserts out. Internally this version can't really handle empty sections.  It logs an error while you're in the editor.

Hello,
All existing issues for RMCv2 are being closed as RMCv2 is no longer being supported.  RMCv3 is in beta here : https://github.com/Koderz/RuntimeMeshComponent/tree/Version3Dev
If you encounter this or any new issues in v3 please feel free to open a new issue!
Thanks!
-Koderz


UI Performance Issues

Epic to track UI Performance issues:

[ ] https://github.com/rancher/dashboard/issues/6285

Closing this as we are using the area/performance label


Create a Playful 404 Page for Kids

Pull Request Details:

Title: Create a Playful 404 Page for Kids
PR Link: #36
Issue: #35

Next Steps:
I'm ready for feedback and any necessary revisions. Please review at your earliest convenience, and feel free to provide comments or suggest improvements.
Thank you for your time and consideration!

Hi User,
Thank you for your pull request. I appreciate your contribution to our project.
I have reviewed your changes and everything looks good. Please be patient, and I'll get back to you as soon as possible.
If you have any questions or need further assistance, don't hesitate to ask.
Best regards,
Jayesh


samples: posix: eventfd: Add sample.yaml for CI builds

Also, add prj.conf options to make the sample builds on more
platforms. Finally, update the sample source to print explicit
"Finished" message, to let user know that the processing is done.
Signed-off-by: Paul Sokolovsky<EMAIL_ADDRESS>

So, here's another case (after https://github.com/zephyrproject-rtos/zephyr/issues/25017) when m2gl025_miv board in CI fails testing process for unknown reason. There was zero response to the previous case, so I see only one way: to blacklist it. (Well, another way is to whitelist just the proverbial qemu_x86, and I tried to avoid it, as hopefully everyone else.)


sweep doesnt complete

2021-12-05T12:48:22Z INFO  farcaster_node::walletd::runtime] Corresponding address: 7Bec8paDCCmYwL2fhyVsEXEAfhGeLb7BYjFk3amiPjheaBwhirD4af1WFBhWW4kiHEAjjMxPNJeucNBXvBKmeF2gEEqVYmk
[2021-12-05T12:50:30Z INFO  farcaster_node::swapd::runtime] 0x169b…b101 | Monero are spendable now (height 979311), sweeping ephemeral wallet
[2021-12-05T12:50:34Z WARN  farcaster_node::syncerd::monero_syncer] error opening to be sweeped wallet: Server error: Failed to open wallet, falling back to generating a new wallet

[2021-12-05T12:57:17Z INFO  farcaster_node::swapd::runtime] 0x169b…b101 | Cancel transaction final with 1 confirmations
[2021-12-05T12:57:17Z WARN  farcaster_node::swapd::runtime] 0x169b…b101 | Cancel transaction with 1 confirmations evokes no response in state AliceState(RefundProcSigs)
[2021-12-05T12:57:17Z INFO  farcaster_node::swapd::runtime] 0x169b…b101 | Lock transaction final with 1 confirmations
[2021-12-05T12:57:17Z WARN  farcaster_node::swapd::runtime] 0x169b…b101 | Lock transaction with 1 confirmations evokes no response in state AliceState(RefundProcSigs)
[2021-12-05T12:57:17Z INFO  farcaster_node::swapd::runtime] 0x169b…b101 | Refund transaction final with 1 confirmations
[2021-12-05T12:57:17Z INFO  farcaster_node::swapd::runtime] 0x169b…b101 | Watching Refund transaction with scriptPubkey: OP_0 OP_PUSHBYTES_20 d5e3f1359370549f13b5536a10ab2f13e7ab52ce

alice.log
bob.log

@TheCharlatan Alice did not manage to Sweep

keys were wrong, #302 fixed it


Linux Diagnostics Agent installation issues

Got the below error when i'm trying to add the Linux Diagnostics agent .  I tried both UI and Azure CLI for installation.
[ExtensionOperationError] Non-zero exit code: 1, /var/lib/waagent/Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.141/diagnostic.py -install [stdout] [stderr] File "/var/lib/waagent/Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.141/diagnostic.py", line 54 print 'A local import (e.g., waagent) failed. Exception: {0}\n' \ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?

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

ID: 13249027-1524-dd0c-9d83-15a9733a3d19
Version Independent ID: bf8a2d1a-8d9b-228a-6919-16127f315d40
Content: Azure Compute - Linux diagnostic extension 4.0 - Azure Virtual Machines
Content Source: articles/virtual-machines/extensions/diagnostics-linux.md
Service: virtual-machines
Sub-service: extensions
GitHub Login: @GabstaMSFT
Microsoft Alias: gabsta

@kgopi1
Thanks for your feedback! We will investigate and update as appropriate.

@kgopi1
Thank you for your feedback!
I'd recommend working closer with our support team via an [Azure support request] (https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request). Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds.
[Teams Q&A forum] (https://docs.microsoft.com/en-us/answers/topics/46488/office-teams-windows-itpro.html) for technical questions about the configuration and administration of Microsoft Teams on Windows.
[Microsoft Teams Community forum] (https://answers.microsoft.com/en-us/msteams/forum?sort=LastReplyDate&dir=Desc&tab=All&status=all&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&isFilterExpanded=false&page=1)
Thank you for your time and patience throughout this issue.


Token expiry issue causing problems in CF/broker-registrar/cfoundry gem?

When updating to CF v236, we noticed the following problem in combination with https://github.com/pivotal-cf/broker-registrar and https://github.com/cloudfoundry-attic/cfoundry:
[stderr]
E, [2016-05-18T05:19:17.339846 #5378] ERROR -- : can't convert nil into an exact number (TypeError)
/var/vcap/data/packages/broker-registrar/46213225d775263932e072a461e524baf0994967.1-ad63b0913a21f7559dce0e6374ec4793184d54c9/vendor/bundle/ruby/2.2.0/gems/cfoundry-4.7.1/lib/cfoundry/auth_token.rb:56:in `at'
/var/vcap/data/packages/broker-registrar/46213225d775263932e072a461e524baf0994967.1-ad63b0913a21f7559dce0e6374ec4793184d54c9/vendor/bundle/ruby/2.2.0/gems/cfoundry-4.7.1/lib/cfoundry/auth_token.rb:56:in `expiration'
/var/vcap/data/packages/broker-registrar/46213225d775263932e072a461e524baf0994967.1-ad63b0913a21f7559dce0e6374ec4793184d54c9/vendor/bundle/ruby/2.2.0/gems/cfoundry-4.7.1/lib/cfoundry/auth_token.rb:60:in `expires_soon?'
/var/vcap/data/packages/broker-registrar/46213225d775263932e072a461e524baf0994967.1-ad63b0913a21f7559dce0e6374ec4793184d54c9/vendor/bundle/ruby/2.2.0/gems/cfoundry-4.7.1/lib/cfoundry/baseclient.rb:137:in `needs_token_refresh?'
/var/vcap/data/packages/broker-registrar/46213225d775263932e072a461e524baf0994967.1-ad63b0913a21f7559dce0e6374ec4793184d54c9/vendor/bundle/ruby/2.2.0/gems/cfoundry-4.7.1/lib/cfoundry/baseclient.rb:82:in `request'
/var/vcap/data/packages/broker-registrar/46213225d775263932e072a461e524baf0994967.1-ad63b0913a21f7559dce0e6374ec4793184d54c9/vendor/bundle/ruby/2.2.0/gems/cfoundry-4.7.1/lib/cfoundry/baseclient.rb:66:in `get'
/

Can it be that changes introduced to CF v236, specifically bringing https://github.com/cloudfoundry/cf-release/releases#identity -> https://github.com/cloudfoundry/uaa/releases/tag/3.3.0 introduced the issue and therefore https://github.com/cloudfoundry-attic/cfoundry/blob/master/lib/cfoundry/auth_token.rb#L56 (Time.at(token_data[:exp])) isn't fitting the bill anymore? Is it a regression on UAA side or a bug on cfoundry gem side?

@vlerenc Are you able to capture the actual token, decode it, and post the claims here?
From the error it says that the exp claim is not even present, nil to be exact.

@vlerenc Any updates?

@fhanik Sorry, no. It was failing, but as the CF/broker-registrar/cfoundry gem was only a tiny component, we removed/replaced it to get going again. Feel free to do with the ticket what you see fit.


setup error

Hello,
When running ./setup to install, I encounter the following error from the ./compile command:
scala.reflect.internal.MissingRequirementError: object scala.runtime in compiler mirror not found.
Is this a bug, something I can work around, or very strange indeed (possibly a problem my end)?
thanks, Andrew

Helleo,
I would like use JAMR parser on Mac os X.

Is-it possible ?
What modifications are necessary ?
Best regards,
Bernard.


Aries#0036 support as JIRA IS-1281 contribution, based vs. 2019-07 hy…

…perledger aries-cloud-agent
Signed-off-by: sklump<EMAIL_ADDRESS>

https://github.com/hyperledger/aries-cloudagent-python/pull/130
supercedes and augments with Aries#0037.


Misleading regarding the requirement for the load balancer or Application Health probe

In the requirements section of the doc it specifically states:

Use application health probes or Application Health extension for non-Service Fabric scale sets

In numerous other places in the document it makes it sound more like it's optional. For example:

"Integrates with application health probes and Application Health extension." --> Makes it sound like it works well with it, but that it isn't a required thing.

"You can also integrate an Azure Load Balancer application health probe or Application Health extension. We recommended incorporating an application heartbeat and validate upgrade success for each batch in the upgrade process." --> This makes it sound like it is recommended, but not required.

"For scale sets with configured application health probes or Application Health extension, the upgrade waits up to 5 minutes for the instance to become healthy, ...." --> This also makes it sound like it's not required as it implies there can be scale sets that don't have them.

"During an OS Upgrade, VM instances in a scale set are upgraded one batch at a time. The upgrade should continue only if the customer application is healthy on the upgraded VM instances. We recommend that the application provides health signals to the scale set OS Upgrade engine. By default, during OS Upgrades the platform considers VM power state and extension provisioning state to determine if a VM instance is healthy after an upgrade. " --> This implies there is a default that the platform uses for health and that an additional probe is an option.

Most annoying though is : "A scale set can optionally be configured with Application Health Probes to provide the platform with accurate information on the ongoing state of the application. Application Health Probes are Custom Load Balancer Probes that are used as a health signal. " --> This actually uses the word 'optionally'.

However, when setting up Automatic OS updates and turning on the flag when creating the VM Scale Set if we make a call to create the scale set and do not have a health probe or health extension specified we will receive an error.

Automatic OS Upgrade is not supported for this Virtual Machine Scale Set because a health probe or health extension was not specified.

The document is confusing because in one place it states it's required, and in many others it implies it's not required, but optional. If the rule is that a health probe or application health extension is required if the scale set is not part of a Service Fabric Cluster I think the verbiage on all the optional reference above may need some clarification.
It would be nice if there was the default that the status of the VM power state and extension provisioning status is enough and you could use automatic OS updates without having to provide a health probe or app health extension. I understand the recommendation for these, and agree with it, but sometimes you may just want to have auto OS upgrades set without needing this type of info beyond the box isn't down and was deployed well (extensions completed successfully).

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

ID: 51c75ce7-2144-d81a-693c-fb51cc00f3e5
Version Independent ID: cba654ea-ee84-fca4-a76d-717bfb9d9bf5
Content: Automatic OS image upgrades with Azure virtual machine scale sets - Azure Virtual Machine Scale Sets
Content Source: articles/virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-upgrade.md
Service: virtual-machine-scale-sets
GitHub Login: @shandilvarun
Microsoft Alias: vashan

+1 same problem here. The documentation seems to imply that health probes/extensions are optional, but I am getting the error "Automatic OS Upgrade is not supported for this Virtual Machine Scale Set because a health probe or health extension was not specified."

I believe the issue is mentioned here: https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-custom-probe-overview#probes

A probe definition is not mandatory or checked for when using Azure PowerShell, Azure CLI, Templates or API. Probe validation tests are only done when using the Azure Portal.

So if you are using the Azure portal, it is a requirement, but not if you are using PS, CLI, etc.
I will review this doc and see how we can rework the language as I agree it is confusing call out optional but then having issues if you don't do it.
Also adding @peterpogorski @athinanthny as we do link from the Service Fabric documentation to this page and it might make sense to have two pages one for VMSS and one specifically for SF on VMSS.

We are using Terraform to create these scale sets, which would mean the Go SDK hitting the API. Not the portal.

I have read through the doc a few times now and I see we do clearly call out that automatic OS upgrades require either health probes or health extensions.
At this point in time I don't find the document to be unclear and I don't see any edits that need to be made. That being said, this issue will remain on this page so if others feel it is also confusing they can comment and w can always reconsider in the future.

when I use LB health probe for VMSS, I always see the instances are Unhealthy (health_probe_id = azurerm_lb_probe.lbprobe.id)
how to use "Application health extension" in terraform instead of LB health probe ?


Uncaught TypeError: setting getter-only property "top" when calling axis function

Using the latest release (1.0.12), I was unable to produce axes, always getting the error Uncaught TypeError: setting getter-only property "top" when calling an axis function, e.g.
const years = [2019,2018,2017,2016,2015]
const margin = {top: 0, right: 60, bottom: 40, left: 0}
const Y = scaleLinear() // time axis
	.domain([Math.min(...years),Math.max(...years)])
	.range([0,height-margin.bottom])
svg.append('g')
	.attr('transform',`translate(${width-margin.right},0)`)
	.call(axisRight(Y)) // <-- it always failed right here

Reverting the package to 1.0.0 solved the problem with no change to my code.

I could not reproduce the issue https://observablehq.com/d/0ab1d4e6db80f3c1

I don't know how to use observable, but I will offer the following in case it helps:

I am using Firefox 79 (Same error in Chrome though)
I am getting this package via NPM and bundling everything with Rollup
I tried working backwords from the current version (1.0.12), building with each patch version until I got something that worked. 1.0.2 worked for me, indicating that the problem (whatever it may be) was introduced in 1.0.3.
My other dependencies are:

  "dependencies": {
    "accessible-autocomplete": "^2.0.3",
    "d3-axis": "1.0.3",
    "d3-fetch": "^1.2.0",
    "d3-scale": "^3.2.1",
    "d3-scale-chromatic": "^1.5.0",
    "d3-selection": "^1.4.2",
    "d3-shape": "^1.3.7",
    "d3-time": "^1.1.0",
    "d3-time-format": "^2.2.3",
    "d3-transition": "^1.3.2"
  }

The only change in 1.0.3 was adding a module entry to the package.json, which suggests that this is a bundler misconfiguration in your project.
https://github.com/d3/d3-axis/compare/v1.0.2...v1.0.3

Aha.
I don't quite understand the difference yet, but I switched to bundling into UMD format from CommonJS. The latest version now works for me without error. I had been using the same bundler settings on other projects for a while now without error, so I assumed the problem was with this package. Sorry for the bother if the problem was just on my end. Looks like I have some reading to do on JS module formats!
Thanks!

I had the same issue - maybe commonJS does not use proper namespaces and this causes a collision with whatever package was added in the package.json? Anyway, UMD fixed it for me too


fixed broken devtools link in main nav of tools

..what the title says :)

@gauntface can you take a look and merge?


Fix flaky BABE test

The authoring_blocks test of BABE was calculating the slot based on the timestamp it sometimes failed in CI. The problem is that we combine all the notifications and authoring futures in one big future. This one big future may first polls one authoring future to build a block. Then it polls all notification futures again to import the block. Then some other authoring future is polled and builds on the imported block using the same slot and making the import fail. The solution is that we just artificially increase the slot to make the test work.
Part of: https://github.com/paritytech/substrate/issues/11321

bot merge


settings: Clean schemas and types used for group settings.

Removed "type"/"Type" from schema and type names used for group settings because we want to use "type"/"Type" only for "type of a type" cases.
So, this commit renames-

anonymous_group_type => anonymous_group_schema
group_setting_type_schema => group_setting_value_schema
GroupSettingType => GroupSettingValue

We also had duplicate definitions for GroupSettingType, in state_data.ts and in settings_components.ts. So, removed it from settings_components.ts.

https://github.com/zulip/zulip/pull/31623#discussion_r1795968511

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Merged, thanks @sahil839!


Improve get tasks

Description
A few improvements for the get_tasks method:

The endpoint /api/tasks never returns the field userfields field. So, although present in TaskResponse, it was never actually filled in. By changing the call to /api/objects/tasks, the field is returned.
Added the possiblity to filter out completed tasks, the endpoint allows an optional query[] param that will allow to do the filtering. In this case the query would be done=0  which will not return all done tasks with done=1. It's a non breaking change as by default the filtering is disabled.

Related issue (if applicable): fixes #
Checklist

[x] The code change is tested and works locally.
[x] tests pass. Your PR won't be merged unless tests pass
[x] There is no commented out code in this PR

Hi @marcelvriend ,
Thank you for pointing it out. I guess at this point I am not sure what is the correct implementation here. Remove userfields from TaskResponse, change the contract of TaskResponse to only have ids for assigned_to_user and category. Another alternative would be to get get_tasks make multiple calls to fill up all the fields, but for long lists this is not ideal.
Ideas?


Gradle 8.0.+ silently dropped support for custom compilers in JavaCompile

In some cases, it may be desirable to use a custom Java compiler (e.g., ECJ) instead of javac (ref). Since Gradle does not currently have first-class support for this, I accomplished this by configuring the JavaCompile tasks manually. Specifically, in Gradle 7.x (including 7.6), first I set the javaCompiler to null. Second, I configure the forkOptions.executable to point at a java (not javac!) executable. Finally, the ECJ jar and its entrypoint are injected into the commandline arguments.
This works fine as can be seen when inspecting the debug output of a project that was configured accordingly. Importantly, there is no warning about this being unsupported or subject for removal.
Expected Behavior

The configuration should work fine on Gradle 8.+, just like it did on 7.6.
Current Behavior

On Gradle 8, however, this is broken. First, setting the javaCompiler to null straight up does not work anymore. An ISE is thrown because Gradle attempts to access the value unconditionally. Additionally, Gradle introduced a check that validates that the forkOptions.executable and the javaCompiler properties of JavaCompile tasks point to the same file. Thus, even without setting the javaCompiler to null, the build fails.
As it stands right now, I'm also questioning the purpose of forkOptions.executable as the value is forced match the value of the javaCompiler property. However, it is not deprecated which leads me to believe that something is incorrect here.
Steps to Reproduce

An MCVE is available at https://github.com/TheMrMilchmann/MCVE/tree/gradle/15942-ecj-7.6-repro
Running gradlew compileJava on this project (using Gradle 7.6) works. The debug output can be inspected to validate the compiler invocation. When using Gradle 8.+, the behavior described above can be observed.

Thank you for providing a valid reproducer.
The issue is in the backlog of the relevant team and is prioritized by them.

Hey! We are looking into fixing this here. In the meantime, here are some comments on the issue.

First, setting the javaCompiler to null straight up does not work anymore.

This is intentional, because javaCompiler is not an optional property anymore. However, setting it to null should not be required, as the compiler property gets inferred from the forkOptions.javaHome or forkOptions.executable if those are configured. The fork options paths take priority even if the project level java { toolchain { ... } } is configured.

the purpose of forkOptions.executable as the value is forced match the value of the javaCompiler property. However, it is not deprecated which leads me to believe that something is incorrect here.

For the majority of cases, if a build configures javaCompiler on the compilation task directly, there is no reason to configure the executables as well. Therefore, having both is most likely an error, as one will be ignored. If a build does end up having both configured, they should either agree on the value or the conflict should be resolved by the user. Normally that would be removing the usage of forkOptions and relying directly on toolchains.
The reason it is not deprecated is that most builds that do use the executable (without migrating to toolchains) simply point it to a javac in the existing JDK installation, which is the main use case and is supported.

First, setting the javaCompiler to null straight up does not work anymore.

This is intentional, because javaCompiler is not an optional property anymore.

But shouldn't setting to null then have been deprecated before?
As far as I understood it gave no deprecation warning in 7.6, yet breaks with 8.0 which is uncommon for Gradle.

After putting some more thought into it and running into a somewhat related issue, I agree with @Vampire here. I've filed #24055 to track this separately.

@TheMrMilchmann we merged the fix for this into the Gradle 8.0.x line and published a snapshot.
Could you please verify that it works for you now?
You can use the wrapper with 8.0.2-20230301020537+0000 version. Here is a command to update the wrapper:
gradle wrapper --gradle-version=8.0.2-20230301020537+0000

I can confirm that this does seem to work mostly. However, I have one remaining issue/question: In an attempt to prevent potential ordering issues, I have deferred the retrieval of the tool and, thus, the configuration of forkOptions.executable to the execution phase (via doFirst). This looks roughly as follows:
val javaLauncher = provider {
    if (java.toolchain.languageVersion.orNull?.canCompileOrRun(REQUIRED_JAVA_VERSION) == true) {
        javaToolchains.launcherFor(java.toolchain).orNull ?: error("Could not get launcher for toolchain: ${java.toolchain}")
    } else {
        javaToolchains.launcherFor {
            languageVersion.set(JavaLanguageVersion.of(PREFERRED_JAVA_VERSION))
        }.orNull ?: error("Could not provision launcher for Java $PREFERRED_JAVA_VERSION")
    }
}

inputs.property("javaLauncher", javaLauncher.map { it.metadata.languageVersion.asInt() })

/* See https://docs.gradle.org/7.4.2/userguide/validation_problems.html#implementation_unknown */
@Suppress("ObjectLiteralToLambda")
doFirst(object : Action<Task> {
    override fun execute(t: Task) {
        options.forkOptions.executable = javaLauncher.get().executablePath.asFile.absolutePath
    }
})

This, too, works fine on Gradle 7.6.1 but fails on 8+ (including 8.0.2-20230301020537+0000) in some cases. For example, if a project toolchain is available but incompatible). Since this is a somewhat hacky approach I'm wondering if it should be supported. However, I tend to believe it should until forkOptions.executable becomes or is replaced by a property.
I've updated the MCVE in https://github.com/TheMrMilchmann/MCVE/commit/e195bf30f8c3dbd6cfcffba3e704bf2b78e98215 to reproduce this.

How about you set the toolchain you want to have on the JavaCompile task directly instead of adding it in a "sneaky" way via a new input property?
The following setup allows doing that. The only downside it has is that it selects the executable by path manipulation. Though I think it is much cleaner. The input tracking for the Java version works out of the box.
val currentJavaToolchain = provider {
    java.toolchain
}

val selectedCompiler = currentJavaToolchain.map { toolchain ->
    val currentCompiler = project.javaToolchains.compilerFor(toolchain).get()
    if (currentCompiler.metadata.languageVersion.canCompileOrRun(REQUIRED_JAVA_VERSION)) {
        currentCompiler
    } else {
        project.javaToolchains.compilerFor { languageVersion.set(JavaLanguageVersion.of(PREFERRED_JAVA_VERSION)) }.get()
    }
}

withType<JavaCompile>().configureEach {
    javaCompiler.set(selectedCompiler)

    /* ECJ does not support generating JNI headers. Make sure the property is not used. */
    options.headerOutputDirectory.set(provider { null })

    options.isFork = true
    options.forkOptions.jvmArgumentProviders.add(CommandLineArgumentProvider {
        mutableListOf("-cp", ecj.asPath, "org.eclipse.jdt.internal.compiler.batch.Main")
    })
    @Suppress("ObjectLiteralToLambda")
    doFirst(object : Action<Task> {
        override fun execute(t: Task) {
            val javacExecutable = javaCompiler.get().executablePath.asFile
            val javaExecutableName = javacExecutable.name.replace("javac", "java")
            val javaExecutablePath = javacExecutable.parentFile.resolve(javaExecutableName).absolutePath
            options.forkOptions.executable = javaExecutablePath
        }
    })

}

Thanks for the input @wolfs! I've considered doing something similar before but it didn't cross my mind that manipulating the path like that is possible now. Given that this is possible, I think we can consider this issue to be fixed.


Fix typo .check -> .is

This is my fault. I saw that another library puts their type guard behind a .check() method and I liked that name a lot better than .is(). So I started to switch the documentation over from .is to .check, must've gotten distracted halfway through. For the moment .check should be considered the "canonical" API and .is should be considered deprecated (but still supported until a v2 is released).


V5 beta3 - in RTL the select tag with class "form-select" the arrow should be on the left #css

In RTL the select tag with class "form-select" the arrow should be on the left not to the right side.
FIX
[dir="rtl"] .form-select{   background-position: left .75rem center;   padding: .375rem .75rem .375rem 2.25rem; }

Bug reports must include a live demo of the issue. Per our contributing guidelines, please create a reduced test case via CodePen or JS Bin and report back with your link, Bootstrap version, and specific browser and operating system details.

This is a saved reply.

Back on this, based on our RTL cheatsheet the arrow is left aligned. Please provide more insights and a reduced test case, I'm closing this for now.


Comparing two same AsyncValue objects always returns false

Describe the bug
The current implementation of the == operator in the AsyncValue class is like this:
@override
  bool operator ==(Object other) {
    return runtimeType == other.runtimeType &&
        other is AsyncValue<T> &&
        other.isLoading == isLoading &&
        other.hasValue == hasValue &&
        other.error == error &&
        other.stackTrace == stackTrace &&
        other.valueOrNull == valueOrNull;

When I write Unit tests:
expect(actualAsyncError, AsyncError('any error', StackTrace.current));

It never returns true, even if two errors are equal because the StackTrace of the actual error is always different from the StackTrace in Unit Tests.
Also, when I compare two same AsyncData<List<T>>, it always returns false as well
expect(AsyncData([1]), AsyncData([1]));

Expected behavior
I think the == operator should be implemented like this. If you have the same point as me, I can create a pull request to update it and its tests.
@override
  bool operator ==(Object other) {
    return runtimeType == other.runtimeType &&
        other is AsyncValue<T> &&
        other.isLoading == isLoading &&
        other.hasValue == hasValue &&
        other.error == error &&
        const DeepCollectionEquality().equals(other.valueOrNull, valueOrNull);
  }

There's nothing wrong with that. The stacktrace is different, therefore the AsyncError is different.
Maybe you don't want a full comparison and only want to check a few properties.
You can do:
expect(
  value,
  isA<AsyncError<List<int>>>()
    .having((e) => e.error, 'error', 'any error'),
);

@rrousselGit It's OK but when I compare two same AsyncData<List>, it always returns false as well. Is this a bug?
expect(AsyncData([1]), AsyncData([1]));

It's because [1] == [1] is false.
If you use const [1] == const [1], only then it will be true.
You can either use a constants or use a list which overrides ==


Unhandled Exception with 'Browse' button

When the program is first downloaded (only the .exe exists), the 'Rom Image Path' is blank (i.e. no lastFile.txt) the program throws an exception when the 'Browse' button is pressed.
Workaround is to copy/paste in the path to the Rom file manually.

Ah, I think I see what's going on... it says could not find file "C:\whatever"... I bet it also was an "empty string" type of thing.  I think I just need to skip the error.  Thanks for the report; I'll look into fixing that!

I think this is taken care of, EvilAsh.  Please test, and, if you're good with it, close the issue.  Thanks!


Intelligent subheading management

The tool copies the .md file verbatim. Could it be more intelligent about the number of hashes (#) before subheadings? The image below shows many ## headings, but there should be ### subheadings for items under the main ticket title.

Fixed in: https://github.com/ChainAccelOrg/trello_to_audit_report/pull/10


WebSocket

Describe the bug
Notifications can't be used, is the error from me or from you, I couldn't find a solution
Reproduction

System Info
Notifications are unavailable

Logs
No response
Validations

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

Maybe your network is unstable. Check your network

Please try again or change to another Test Network.
You can find the Honer Node list and port on http://scan.ibax.io


toEqual behavior against copy-by-value primitives

Do you want to request a feature or report a bug?
bug
What is the current behavior?
expect('-1').toEqual(-1) fails
What is the expected behavior?
expect('-1').toEqual(-1) should pass
Essentially, toBe() is meant to be the strict equality expectation and toEqual() is meant to be a looser check. It seems that toEqual does a strict equality check (===) on primitives like String, Number, and Boolean when it should probably do a loose equality check (==).
Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.
Jest 19
Latest macOS

It's not a bug. With this kind of reasoning you'd end up with expect(undefined).toEqual(null) to be true. We're not going to change it.

@thymikee Right, which is why people should be using toBe() in their tests. It's the same argument in the JS community in general about using triple equal. Is equal is meant to be like a double equal though, so I still think the behavior doesn't make sense.
If the library doesn't want to make the change, that's cool... but I do think there's a valid argument.

i don't think toEqual was ever meant to be ==. It's mostly just a recursive ===


🐛 Fix matching submatches when cmd held down

Currently, holding down the command key short-circuits the allowCombinationSubmatches configuration due to the command key hiding keyup events. You can find more information about the reasoning here.
This fix maintains that behaviour, however it only applies when the key map being compared against includes the command key.
Fixes https://github.com/greena13/react-hotkeys/issues/296
Fixes https://github.com/greena13/react-hotkeys/issues/234

Thanks!


Illegal use of unsafe.Pointer to store cgo.Handle

I noticed you're using unsafe.Pointer(uintptr(cgo.NewHandle(slot)).
I recently ran into this issue myself, where I wanted to store a cgo.Handle into a unsafe.Pointer field.
The general consensus seem to be that it is not a legal use of unsafe.Pointer.
Relevant:
https://github.com/golang/go/issues/49633
https://github.com/golang/go/commit/d2f4c935f2e247dd9949094c8a4f3ab8df2ba3a0#diff-ffa0f0c347d78cbdf6478bbdfb43131be08b1db600aa9968430ac9424a6361ed
The suggestion is to instead pass the address of your cgo.Handle.
But since it's a callback, I suppose it needs to be properly pinned as well.

Maybe the void *slot parameters could instead be changed into intptr_t, that'd allow cgo.Handle to fit in there

Great catch, thank you. I agree an int type sounds better than double indirection. I'll make this change,


Uncaught TypeError: Cannot read property 'options' of undefined

I get this error when i try to set the slider when the video is not playing. But it works fine when it's playing. plus setValueSider is not working it's not even showing any errors.

Could you explain a bit more please? Are you using .min version of videojs? how is your initialization of rangeslider?

Okay. I some how managed to make it work but it's not working with the current version of videojs. I'm using the one present in your repository.

Billy is trying to upgrade the plugin version in https://github.com/danielcebrian/rangeslider-videojs/issues/22. You can see the changes and talk with him if you are still interested


Bug: It's too white.

Use it every single day. My team uses teams for work. Love it. Works fairly well.
It's just.. so.. white. Please add a dark theme. Succeed where Slack has so miserably failed. Please give us a dark theme. It's searing my retinas.
Thank you.

I'm seeing this issue as well (pun intended) in the Electron app. Please allow for theme/color customization, or at the very least provide a dark theme. It's very difficult to focus my eyes on the chat screen, and I've found that, generally speaking, dark-theme UIs are easier to discern.

I would really like to see this too.

Maybe a temporary "fix":
Darkens the whole UI a little bit.
I have that plugin on Firefox and it already helps a lot on white websites: https://addons.lightalex.com/darkview
It just dims out the light a little bit.

Dark mode released in Keybase 4.6.0 under Settings->Display->Appearance.


add dark theme

I would like to work on this issue. Please assign it to me under GSSoC'23.

hey I would like to work on this issue. Kindly assign it to me

Sure assigning this task.

I'm here to contribute to the GSSOC'23.
Please assign me to do that.

@PiyushKalyanpy I want to work on this.Please assign me


Show more comprehensible status text

Here are a few thoughts I have on the status text after having used rawtx for a few days.
Right now when creating a new wallet rawtx will first sync to the chain which is nicely shown in orange and updated information on how far it has synced already. But maybe a percentage display of how far it has currently synced could be added (even though strictly speaking as blocks can have different weight/sizes a calculation of percentage using the current number of synced blocks divided by the total number of blocks is only a rough estimate of the percentage).
After rawtx is synced with the blockchain it shows in green that it is fully synced to the chain. Then rawtx will build up the lightning network graph and therefore also show in orange the text that it is syncing with the lightning network.
But at first I did not catch the subtly different text (Syncing to the chain vs Syncing with lightning network) and therefore thought that it was now fully synced and ready to be used and the text in orange just a bug/leftover.
Building up the network graph can take many hours and so I already opened a channel but afterwards realised that only few routes if any were possible for payments. Knowing how it works now, I easily understand the messages, but the first time I did not catch the differences. Therefore I think it would be good to make it even more clear.
Maybe instead of showing synced to the chain in green immediately after having synced to the blockchain, rawtx could then say "Building the lighting network graph" or something similarly distinct from the syncing-to-the-chain message and wait until it is both synced to the chain and has build up the network graph to show that it is fully synced in green? Maybe rawtx could also block the possibilities of paying/receiving invoices with a notice to wait until synced with the lightning network when the user tries it before, or at least show this message when trying to pay/receive invoices as long as the network graph is still being build?
Just my 2 cents.

Makes sense, thanks for the detailed feedback. Will change the message to be more intuitive and show warning/block when trying send and receive payments.
Currently working on improving the network sync time, for the initial sync, it should take less than 30 minutes very soon instead of hours and eventually want to bring it to less than 10min.

Closing this one for now as it will be obsolete in the next release of the wallet which will be available shortly after lnd 0.5 release is official.


[Feature request] Multiple dialogue happening simultaneously

Just a thought. I'm thinking something like when two (sometimes more) characters are saying different things at the same time or are overlapping each other; something like these:

Two messages being shown on each side, rather than the usual one message at a time, so the text would wrap around the middle. Would be cool to have this feature

Thank you for your suggestion, but I'm not sure if it fits within the scope of a dialogue and maybe it would be more suitable for another plugin (for screenwriting)?
I'll leave this open for now and maybe i'll eventually figure out some elegant way to implement this.

For better or worse, centered dialogues are now a thing. See #16.


Fix identifier formatting for migrations when used with Oracledb

Presently, knex encounters issues in Oracle database when certain migration commands are executed when a custom wrapIdentifier option is specified in the knexfile - particularly when this option is used to normalize casing and formatting of database objects (ex. camelCase to UPPER_SNAKE_CASE). The cause of the issue is inconsistent usage of identifier formatting with formatter.wrap() throughout the oracle schema query compilers, where some parts of the code are formatting identifiers, and others are not in places that alter the same resource. This is problematic as Oracle treats any identifier surrounded in quotes as case-sensitive and knex routinely quotes all identifiers in its queries.
A prime example of this is the table and column renaming schema builder methods, which would not format identifiers that were passed-in to these methods. This contrasts with how table and column names are formatted on initial creation. This inconsistency sometimes results in failing queries when the exact same name used during creation and renaming of a table or column were used if the name passed to the query builder was later formatted by wrapIdentifer in a way that would alter the casing of the name. An example of such a scenario would look like this:
// knex created from knexfile w/wrapIdentifier configured to convert lower_snake and camelCase to UPPER_SNAKE_CASE
const knex = require('knexInstance');

await knex.scema.createTable('exampleTable', (table) => {  // Resultant table name would be "EXAMPLE_TABLE"
    // table builder statements
});

await knex.schema.renameTable('exampleTable', 'newTable');
// Fails with error from Oracle stating that table "exampleTable" does not exist.

Another instance of inconsistent formatting was causing issues with the dropTableIfExists() method as well. The table name would be successfully formatted and dropped, though the auto-generated sequence for a .increments() id column would fail with an error. This is because knex always generates these auto-generated sequences in all lowercase regardless of what is specified in wrapIdentifier, while the dropSequenceIfExists() schema builder compiler for Oracle would always format the sequence name. Building off of the previous example, the following statement would also fail:
// auto-generated sequence for exampleTable is named "example_table_seq"

await knex.schema.dropTableIfExists('exampleTable');
// drops "EXAMPLE_TABLE", attempts to drop "EXAMPLE_TABLE_SEQ"
// Oracle throws an error because "EXAMPLE_TABLE_SEQ" does not exist

This was fixed by altering the code path for related sequence deletion to not format the sequence name on deletion. I took this approach instead of removing formatting in dropSequenceIfExists() directly as previous changelogs indicated that this may have been previously, or is intended to be used if or when a public API for sequence creation in Oracle is added to knex. If this is not the case, I can refactor that to eliminate some dead code since dropSequenceIfExists() is not presently in use by any other part of the codebase (either by removing that function or prefixing it with _ to indicate that it is intended for private use).  This approach was taken instead of formatting auto-created triggers going forward to avoid breaking migration commands that manipulate these triggers and sequences (as new implementations would always format these names where prior versions would have always lower_snake_case'd the trigger and sequence name).
I had to make several adjustments to some of the existing unit tests for oracle since the code now calls the wrapIdentifier function an additional time during the affected tests. I also added several new unit tests to check that wrapIdentifier is called properly in the schema builder functions that were affected by the inconsistent formatting issues.
Fixes #5801

coverage: 92.86% (+0.02%) from 92.843%
when pulling 523d91c2dd82dd97970715bcf9034ad27c96a79f on Kytech:oracle-autoinc-trigger-formatting
into 9659a20753e22939ffb547e3b10d5bfa6a3fd941 on knex:master.


ci(web-app): improve caching

Closed as action/cache still the better option: https://gist.github.com/belgattitude/0ecd26155b47e7be1be6163ecfbb0f0b


Assert that the main source file name is non-empty.

The Darwin linker won't process the debug info if the source file name
is invalid so there is no point in having a fallback implemented there.
rdar://problem/25130236

@swift-ci please test and merge

@swift-ci please smoke test OS X platform and merge

@swift-ci please smoke test OS X platform

This broke my PR testing. What happened?

@adrian-prantl , should we have someone force merge your revert to get PR testing working again?
https://github.com/apple/swift/pull/4986

@atrick that would be a good idea, thanks!

@jrose-apple not sure yet. It supposedly passed a full macOS platform test but the assertion triggered in your PR while building the macosx stdlib, which doesn't make sense.
It's definitely an indicator that the assertion was spot-on ;-)
I'll update this PR once I figured out what happened here.


The following directories listed in your path were found to be non-existen

/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/paths.py:27: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('/usr/local/nvidia/lib'), PosixPath('/usr/local/nvidia/lib64')}
warn(
/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/paths.py:105: UserWarning: /usr/local/nvidia/lib:/usr/local/nvidia/lib64 did not contain libcudart.so as expected! Searching further paths...
warn(
/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/paths.py:27: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('/sys/fs/cgroup/memory.events /var/colab/cgroup/jupyter-children/memory.events')}
warn(
/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/paths.py:27: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('http'), PosixPath('//<IP_ADDRESS>'), PosixPath('8013')}
warn(
/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/paths.py:27: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('//colab.research.google.com/tun/m/cc48301118ce562b961b3c22d803539adc1e0c19/m-s-3kyfolly38eid --tunnel_background_save_delay=10s --tunnel_periodic_background_save_frequency=30m0s --enable_output_coalescing=true --output_coalescing_required=true'), PosixPath('--logtostderr --listen_host=<IP_ADDRESS> --target_host=<IP_ADDRESS> --tunnel_background_save_url=https')}
warn(
/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/paths.py:27: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('/env/python')}
warn(
/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/paths.py:27: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('//ipykernel.pylab.backend_inline'), PosixPath('module')}
warn(
CUDA_SETUP: WARNING! libcudart.so not found in any environmental path. Searching /usr/local/cuda/lib64...
CUDA SETUP: CUDA runtime path found: /usr/local/cuda/lib64/libcudart.so
CUDA SETUP: WARNING! libcuda.so not found! Do you have a CUDA driver installed?
Traceback (most recent call last):
File "/content/train_dreambooth.py", line 18, in
from accelerate import Accelerator
File "/usr/local/lib/python3.10/dist-packages/accelerate/init.py", line 3, in
from .accelerator import Accelerator
File "/usr/local/lib/python3.10/dist-packages/accelerate/accelerator.py", line 35, in
from .checkpointing import load_accelerator_state, load_custom_state, save_accelerator_state, save_custom_state
File "/usr/local/lib/python3.10/dist-packages/accelerate/checkpointing.py", line 24, in
from .utils import (
File "/usr/local/lib/python3.10/dist-packages/accelerate/utils/init.py", line 131, in
from .bnb import has_4bit_bnb_layers, load_and_quantize_model
File "/usr/local/lib/python3.10/dist-packages/accelerate/utils/bnb.py", line 42, in
import bitsandbytes as bnb
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/init.py", line 6, in
from .autograd._functions import (
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/autograd/_functions.py", line 5, in
import bitsandbytes.functional as F
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/functional.py", line 13, in
from .cextension import COMPILED_WITH_CUDA, lib
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/cextension.py", line 41, in
lib = CUDALibrary_Singleton.get_instance().lib
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/cextension.py", line 37, in get_instance
cls._instance.initialize()
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/cextension.py", line 15, in initialize
binary_name = evaluate_cuda_setup()
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/main.py", line 132, in evaluate_cuda_setup
cc = get_compute_capability(cuda)
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/main.py", line 105, in get_compute_capability
ccs = get_compute_capabilities(cuda)
File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/cuda_setup/main.py", line 83, in get_compute_capabilities
check_cuda_result(cuda, cuda.cuDeviceGetCount(ctypes.byref(nGpus)))
AttributeError: 'NoneType' object has no attribute 'cuDeviceGetCount'

Same issue as you.

export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu
for ubuntu 22.04 this command will solve all the issues

Bitsandbytes was not supported windows before, but my method can support windows.（yuhuang）
1  open folder J:\StableDiffusion\sdwebui，Click the address bar of the folder and enter CMD
or WIN+R, CMD  。enter，cd /d J:\StableDiffusion\sdwebui
2  J:\StableDiffusion\sdwebui\py310\python.exe -m pip uninstall bitsandbytes
3 J:\StableDiffusion\sdwebui\py310\python.exe -m pip uninstall bitsandbytes-windows
4 J:\StableDiffusion\sdwebui\py310\python.exe -m pip install https://github.com/jllllll/bitsandbytes-windows-webui/releases/download/wheels/bitsandbytes-0.41.1-py3-none-win_amd64.whl
Replace your SD venv directory file（python.exe Folder） here（J:\StableDiffusion\sdwebui\py310）

Bitsandbytes was not supported windows before, but my method can support windows.（yuhuang）
1  open folder J:\StableDiffusion\sdwebui，Click the address bar of the folder and enter CMD
or WIN+R, CMD  。enter，cd /d J:\StableDiffusion\sdwebui
2  J:\StableDiffusion\sdwebui\py310\python.exe -m pip uninstall bitsandbytes
3 J:\StableDiffusion\sdwebui\py310\python.exe -m pip uninstall bitsandbytes-windows
4 J:\StableDiffusion\sdwebui\py310\python.exe -m pip install https://github.com/jllllll/bitsandbytes-windows-webui/releases/download/wheels/bitsandbytes-0.41.1-py3-none-win_amd64.whl
Replace your SD venv directory file（python.exe Folder） here（J:\StableDiffusion\sdwebui\py310）


Update index.html to v<IP_ADDRESS>

v<IP_ADDRESS>b/Wasabi-<IP_ADDRESS>.msi.asc the 1b is needed. I created the tag stupidly...

Post-merge ACK. Checked that links work and signatures match.


:student:  Update case.md > create real table with real data

:grey_question: Context
Currenlty, we cannot run the examples out of the box.
For example on CASE statement, if I dumb run the tutorial I get this:

... where as is we provide the following code:
-- Create & feed example table
CREATE OR REPLACE TABLE INTEGERS as SELECT UNNEST([1, 2, 3]) as i;
-- CASE example
SELECT i, CASE WHEN i>2 THEN 1 ELSE 0 END AS test FROM integers;

:moneybag: Benefits

:heavy_check_mark: Make code samples runnable
:heavy_check_mark: Help people discover other duckdb functiions... and help improve people knowldge (cf  my discussion)

:bookmark: Related stuff

https://github.com/duckdb/duckdb/discussions/6674#discussioncomment-5272110
UNNEST
CASE

Thanks! We love having concrete examples in the docs. Much appreciated!


Possibility to upload a background image to align grid with my design

Hello !
I love your website and your project, I would love to be able to change the background image to align the grid with my image!
Thanks, you can delete/move this since it's not an issue but a “request”.

@Pernifloss Sir could you please assign me this issue it would be my first contributions

Hello @pragyamishra56 I don't think I have the right to assign issues. If I do, I don't know how to do it. :)

@sdras, I believe you can assign this issue.  @pragyamishra56, please fork the repository, create a separate branch for your work, make your changes in that branch, and then push your updates. Once done, kindly send a pull request.


[Service Bus] Avoid rethrowing exception with throw ex syntax when exception unchanged

Attempt to address #11639

Before
    [TestFixture]
    public class AmqpExceptionHelperTests
    {
        [Test]
        public void Translates()
        {
            try
            {
                MethodThatThrows();
            }
            catch (Exception e)
            {
                throw AmqpExceptionHelper.TranslateException(e);
            }
        }

        private static void MethodThatThrows()
        {
            throw new InvalidOperationException();
        }
     }

leads to
Azure.Messaging.ServiceBus.Tests.Amqp.AmqpExceptionHelperTests.Translates

System.AggregateException : One or more errors occurred. (Rethrown)
  ----> NUnit.Framework.Internal.NUnitException : Rethrown
  ----> System.InvalidOperationException : Operation is not valid due to the current state of the object.
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at NUnit.Framework.Internal.Commands.TimeoutCommand.Execute(TestExecutionContext context) in D:\a\1\s\src\NUnitFramework\framework\Internal\Commands\TimeoutCommand.cs:line 102
--NUnitException
   at NUnit.Framework.Internal.Reflect.InvokeMethod(MethodInfo method, Object fixture, Object[] args) in D:\a\1\s\src\NUnitFramework\framework\Internal\Reflect.cs:line 274
   at NUnit.Framework.Internal.Commands.TestMethodCommand.Execute(TestExecutionContext context) in D:\a\1\s\src\NUnitFramework\framework\Internal\Commands\TestMethodCommand.cs:line 64
   at NUnit.Framework.Internal.Commands.TimeoutCommand.<>c__DisplayClass2_0.<Execute>b__0() in D:\a\1\s\src\NUnitFramework\framework\Internal\Commands\TimeoutCommand.cs:line 102
   at System.Threading.Tasks.Task`1.InnerInvoke()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot)
--InvalidOperationException
   at Azure.Messaging.ServiceBus.Tests.Amqp.AmqpExceptionHelperTests.Translates() in C:\p\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\tests\Amqp\AmqpExceptionHelperTests.cs:line 22

After
    [TestFixture]
    public class AmqpExceptionHelperTests
    {
        [Test]
        public void Translates()
        {
            try
            {
                MethodThatThrows();
            }
            catch (Exception e)
            {
                ExceptionDispatchInfo.Capture(AmqpExceptionHelper.TranslateException(e))
                    .Throw();
                throw;
            }
        }

        private static void MethodThatThrows()
        {
            throw new InvalidOperationException();
        }
    }

leads to
Azure.Messaging.ServiceBus.Tests.Amqp.AmqpExceptionHelperTests.Translates

System.AggregateException : One or more errors occurred. (Rethrown)
  ----> NUnit.Framework.Internal.NUnitException : Rethrown
  ----> System.InvalidOperationException : Operation is not valid due to the current state of the object.
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at NUnit.Framework.Internal.Commands.TimeoutCommand.Execute(TestExecutionContext context) in D:\a\1\s\src\NUnitFramework\framework\Internal\Commands\TimeoutCommand.cs:line 102
--NUnitException
   at NUnit.Framework.Internal.Reflect.InvokeMethod(MethodInfo method, Object fixture, Object[] args) in D:\a\1\s\src\NUnitFramework\framework\Internal\Reflect.cs:line 274
   at NUnit.Framework.Internal.Commands.TestMethodCommand.Execute(TestExecutionContext context) in D:\a\1\s\src\NUnitFramework\framework\Internal\Commands\TestMethodCommand.cs:line 64
   at NUnit.Framework.Internal.Commands.TimeoutCommand.<>c__DisplayClass2_0.<Execute>b__0() in D:\a\1\s\src\NUnitFramework\framework\Internal\Commands\TimeoutCommand.cs:line 102
   at System.Threading.Tasks.Task`1.InnerInvoke()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot)
--InvalidOperationException
   at Azure.Messaging.ServiceBus.Tests.Amqp.AmqpExceptionHelperTests.MethodThatThrows() in C:\p\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\tests\Amqp\AmqpExceptionHelperTests.cs:line 31
   at Azure.Messaging.ServiceBus.Tests.Amqp.AmqpExceptionHelperTests.Translates() in C:\p\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\tests\Amqp\AmqpExceptionHelperTests.cs:line 19
--- End of stack trace from previous location where exception was thrown ---
   at Azure.Messaging.ServiceBus.Tests.Amqp.AmqpExceptionHelperTests.Translates() in C:\p\azure-sdk-for-net\sdk\servicebus\Azure.Messaging.ServiceBus\tests\Amqp\AmqpExceptionHelperTests.cs:line 23

The ugly part is the non-reachable throw statements to make the compiler happy

Can one of the admins verify this patch?

Because the AmqpExceptionHelper was not yet under tests I decided to not add tests given that I kept the control flow exactly the same.

The ugly part is the non-reachable throw statements to make the compiler happy

So what is the compiler complaining about when you don't include the throw statement?

So what is the compiler complaining about when you don't include the throw statement?

Return statement missing

What are your thoughts on inverting the pattern to be:
                ExceptionDispatchInfo.Capture(AmqpExceptionHelper.TranslateException(e))
                    .Throw();

The benefit is that we wouldn't have to propagate the ExceptionDispatchInfo into AmqpExceptionHelper, assuming that this still works as expected.

Chnanged the approach to what you suggested because it is much leaner

/azp run net - servicebus - tests

/azp run net - servicebus - tests

@danielmarbach any chance you can do a rebase? A new yml file was added to workaround a live test run issue that is not getting picked up when running the live tests against this PR.

@danielmarbach any chance you can do a rebase? A new yml file was added to workaround a live test run issue that is not getting picked up when running the live tests against this PR.

Actually, hold off on this.. There was a bug with the path being used.

/azp run net - servicebus - tests


[Bot] Update API inference documentation

This PR automatically upgrades the @huggingface/tasks package and regenerates the API inference documentation by running:
cd scripts/api-inference
pnpm update @huggingface/tasks@latest
pnpm run generate

This PR was automatically created by the Update API Inference Documentation workflow.
Please review the changes before merging.

(low priority) we could update the script that generates this PR to not push anything if the git diff is only package.json and pnpm-lock.yaml


Moved to using react-accessible-accordion for

This does remove the animation, but that seems like a small price for accessibility, we can work out how to put back in animation later.

Demo https://2383-84182601-gh.circle-artifacts.com/0/artifacts/build/index.html
Fixes #321

that seems like a small price for accessibility, we can work out how to put back in animation later.

@orangemug agree, what about
https://github.com/maputnik/editor/blob/master/src/components/layers/LayerListGroup.jsx ?

<LayerListGroup/> is slightly different it needs to be a 'tree view', see #320. I've got something partially working for that but it's slight more involved.

Thanks @orangemug, looks good to merge.

Thanks, merging!


https://openmoocers-slackin.herokuapp.com/  link broken

if this is the rigth link, herokapp is down
(application error)

Nope, it broke, so had to rebuild to: https://osmooc.herokuapp.com/
Where did you find that link? Need to make sure they're replaced.

It is everywhere... https://travis-ci.org/OpenScienceMOOC/Module-5-Open-Research-Software-and-Open-Source/builds/490508222?utm_source=github_status&utm_medium=notification

In the GH files, yes, perhaps still. Can you pinpoint where @jcolomb? I've fixed virtually all on Eliademy itself.

I am on it, will pull request later.

Perfect, thanks @jcolomb!

This was fixed, #77
I also needed to change one folder name:never use spaces in folder or filenames !!!!


checkSSLCert: 1.80.0 -> 2.12.0

Things done
Updated checkSSLCert to latest release.

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Updated to 2.19.0 in #155043, still thanks for your contribution!

Thanks for the heads-up!


Tools 2815 2

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

Comparison is base (9536b83) 87.44% compared to head (201af2d) 86.92%.

Files
Patch %
Lines

config/conf.go
12.50%
6 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #10      +/-   ##
==========================================
- Coverage   87.44%   86.92%   -0.53%
==========================================
  Files          15       15
  Lines         693      696       +3
==========================================
- Hits          606      605       -1
- Misses         65       70       +5
+ Partials       22       21       -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Carthage update failure

I'm using Xcode 8.3.3. When running the 'carthage update --platform iOS' command, I encountered the following build error:
`$ carthage update --platform iOS
*** Downloading ios-sdk.framework binary at "v0.10.0"
*** Skipped installing ios-sdk.framework binary due to the error:
"Incompatible Swift version - framework was built with 3.0.1 and the local version is 3.1."
*** Checking out ios-sdk at "v0.10.0"
*** xcodebuild output can be found in /var/folders/x8/hsf3xrrx6cl75t_cby6g809w0000gn/T/carthage-xcodebuild.m97psa.log
*** Building scheme "AlchemyDataNewsV1" in WatsonDeveloperCloud.xcodeproj
*** Building scheme "TradeoffAnalyticsV1" in WatsonDeveloperCloud.xcodeproj
*** Building scheme "DialogV1" in WatsonDeveloperCloud.xcodeproj
*** Building scheme "ToneAnalyzerV3" in WatsonDeveloperCloud.xcodeproj
*** Building scheme "ConversationV1" in WatsonDeveloperCloud.xcodeproj
*** Building scheme "RetrieveAndRankV1" in WatsonDeveloperCloud.xcodeproj
*** Building scheme "VisualRecognitionV3" in WatsonDeveloperCloud.xcodeproj
*** Building scheme "RestKit" in WatsonDeveloperCloud.xcodeproj
*** Building scheme "RelationshipExtractionV1Beta" in WatsonDeveloperCloud.xcodeproj
*** Building scheme "TextToSpeechV1" in WatsonDeveloperCloud.xcodeproj
*** Building scheme "AlchemyLanguageV1" in WatsonDeveloperCloud.xcodeproj
*** Building scheme "SpeechToTextV1" in WatsonDeveloperCloud.xcodeproj
Build Failed
Task failed with exit code 65:
/usr/bin/xcrun xcodebuild -project /Users/xxx/Documents/xx/NearBY/NearBY/NearBY-iOS/Carthage/Checkouts/ios-sdk/WatsonDeveloperCloud.xcodeproj -scheme SpeechToTextV1 -configuration Release -derivedDataPath /Users/xxx/Library/Caches/org.carthage.CarthageKit/DerivedData/ios-sdk/v0.10.0 -sdk iphoneos ONLY_ACTIVE_ARCH=NO BITCODE_GENERATION_MODE=bitcode CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES clean build
This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/x8/hsf3xrrx6cl75t_cby6g809w0000gn/T/carthage-xcodebuild.m97psa.log`

@kkkum Can you try the code here? This repo is up to date with Swift 3.1.


Tunable genesis time

Currently the genesis time is not very tune-able and is instead always at a timestamp where genesis_time % MIN_GENESIS_DELAY == 0. Due to the desire to generally configure testnets at "mainnet" config, MIN_GENESIS_DELAY == 24hrs and thus genesis_time is always at midnight UTC for mainnet configuration.
Depending on who is working on the testnet (e.g. @q9f), this can lead undesirable late nights.
Background
The genesis time is computed such that regardless of when MIN_GENESIS_ACTIVE_VALIDATOR_COUNT is hit, genesis_time is always at the exact same time of day.
genesis_time=eth1_timestamp - eth1_timestamp % MIN_GENESIS_DELAY + 2 * MIN_GENESIS_DELAY

This is so even if the exact day is known the exact time of some day is known so the teams can plan accordingly. (this being a very important feature is probably debatable).
Option 0
Don't change anything and just deal with it.

Option 1
This option preserves the notion of knowing exactly what time of day genesis will be, but instead allows us to tune that time. It is backwards compatible for networks that use the default configuration values.
It simply takes the previous calculation and adds  GENESIS_TIME_OFFSET to the result to tune the precise time of day. A GENESIS_TIME_OFFSET of 0 would result in the same genesis time as in current specs.
genesis_time=(
    eth1_timestamp
    - eth1_timestamp % MIN_GENESIS_DELAY
    + 2 * MIN_GENESIS_DELAY
    + GENESIS_TIME_OFFSET
)

For example, if we use MIN_GENESIS_DELAY = 86400 and GENESIS_TIME_OFFSET = 21600 (6hrs), then genesis time will be at 6am UTC.
Option 2
This option does not preserve knowing exactly what time of day genesis will happen. This instead just uses a fixed offset from the initial eth1 block timestamp at which point genesis conditions were first met.
genesis_time=eth1_timestamp + GENESIS_DELAY

In cases in which MIN_GENESIS_ACTIVE_VALIDATOR_COUNT is hit prior to MIN_GENESIS_TIME - GENESIS_DELAY,  genesis will be approximately at MIN_GENESIS_TIME (thus highly predictable on most smaller test/devnet scenarios). The time becomes much less predictable in larger testnets and/or mainnet where the MIN_GENESIS_ACTIVE_VALIDATOR_COUNT is not guaranteed to happen at a certain time.

So, my personal opinion on this as I brought this up. This is low priority and just a cosmetic change.

:shrug: If we stick to Option 0, we'll be probably fine.
:heavy_multiplication_x: Option 1 is just necessarily adding another constant.
:heavy_check_mark: I'm personally in favor of Option 2.

:memo: It's not much of a difficult change, requires a minor spec version bump though.
:partying_face: It introduces some randomness and makes launching chains so much more fun.
:hourglass_flowing_sand: It's still very predictable especially when launching testnets.
:baby: It significantly reduces complexity of the genesis_time formula.

I don't feel strongly, but would lean towards option 2. If we do this, I would suggest doubling MIN_GENESIS_TIME to 48 hrs for mainnet.
Perhaps this is tangential, but I would even advocate for making MIN_GENESIS_TIME a few days to give us plenty of time to test the genesis state and distribute it in binaries.


MWPW-145389 Push sync for floodgate and graybox

Push sync for floodgate and graybox to avoid future security issues

Skipping sync for excluded files

Resolves: MWPW-145389
Example summary:

Synced: https://github.com/sukamat/repo-a/actions/runs/10085603734
Skipped: https://github.com/sukamat/repo-a/actions/runs/10085613879

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 96.21%. Comparing base (143d68e) to head (5529f3c).

Additional details and impacted files
@@           Coverage Diff           @@
##            stage     #228   +/-   ##
=======================================
  Coverage   96.21%   96.21%
=======================================
  Files          11       11
  Lines        1082     1082
=======================================
  Hits         1041     1041
  Misses         41       41

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

thanks @Brandon32 !


Update GCP Readme

Corrects a minor spelling error.

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