restart electron app as root

When i try to restart the app as root i get the error Error: User did not grant permission, although I did enter the password and clicked the OK button.
// ... imports
var sudo = require('sudo-prompt');
const app = require('electron').remote.app;
console.log('app exe', app.getPath('exe'));

// ... check if started programm as root
var user = process.env['USER'];
if (user === 'root' || user === 'administrator') {
    console.log('started as root');
} else {

    // try restarting as root
    sudo.exec(app.getPath('exe'), {name: 'Appname'}, function(error, stdout, stderr) {
        stdout && console.log('output:', stdout);
        stderr && console.log('error:', stderr);
        error && console.log('error:', error);
        if (!error) {
            app.exit(0)
        } else {
            // Error: User did not grant permission
            alert('Sorry we could not restart the app with administrator/root privileges, which is necessary for certain functions.');
        }
    });
}

Any ideas?
But no matter what, thank you so much for creating this!

I really do not know a lot of linux, but i thought with try and error it may works. But finally giving up, all failed:
t = 'script/to/start.sh';
startNew(t);
startNew(app.getPath('exe'));
startNew(t + ' &');
startNew(app.getPath('exe') + ' &');
startNew('nohup ' + t);
startNew('nohup ' + app.getPath('exe'));
startNew('nohup sudo ' + t + ' &');
startNew('nohup sudo ' + app.getPath('exe') + ' &');

startNew('fork || exec "' + app.getPath('exe') +'"'); // starts at least the app new, but not as root :(
startNew('echo "" | fork || exec sudo -S "' + app.getPath('exe') +'"');
startNew('sudo -S fork || exec "' + t +'"');
startNew('exec "' + app.getPath('exe')  + '"');
startNew('exec "' + t  + '"');

ok, got it i should learn to read the readme and look into the closed issues #15 ;) non-graphical terminal commands only. But if somebody has an idea let me hear it.

Thanks @mnewmedia
Which platform is this, and what version?
Can you try changing into the node_modules/sudo-prompt directory and then running node test.js?

Ubuntu 16.04. test works and all other commands are also working just not the to restart the electron-app, but thats's probably because of  non-graphical terminal commands only #15.

Yes, it's not a good idea to run graphical commands using sudo or sudo-prompt. You can try using pkexec or gksudo directly on Linux for that.

So then thanks anyway! repeat with me: i will read the readme, i will read the readme.. haha


New version with improved docstrings and python 3.7 support

This PR improves the docstrings for the keep_params and keep_types methods to provide some examples and it adds tests for python 3.7.

Coverage remained the same at 97.423% when pulling 566322d260c9114ca4c89b5623ceb392644d9316 on dev into 5154fcda05bb64664e084b0f74d19eea15c181b5 on master.


Delete default ipset on namespace termination

What ?
Fix for https://github.com/weaveworks/weave/issues/3247
What it does?
On namespace deletion default ipset will cleaned for the namespace
Status of PR
Test in progress in local cluster

This should be based off the 2.2 branch so we can put it in a patch release.

@bboreham Closed in favour of https://github.com/weaveworks/weave/pull/3250, made a new PR based on 2.2 branch


After the PC is started, MonitorControl is always at 0

Hello,
Please help, how to set MonitorControl to volume level ?
After the PC is started, MonitorControl is always at 0
Thanks
PS: EFI/CLOVER/drivers64UEFI - is OK

I've experienced the same issue. I guess it's because MonitorControl doesn't read the values on startup. However, it was just a display bug for me, sound worked fine (no muting). Pressing Volume Up / Down got the correct value displayed for me.

It should restore the last saved values now.


CAB-3483: add e2e for customized boolean Facets values

Coverage remained the same at 83.437% when pulling 2295d2040992e5375443f79446e26a3cd8a2ff21 on feature/cab-3483-e2e into 7fdb9635702648ddf1d3bc7fea5a19cccd7477a2 on develop.


selectionChange fires twice in Select component while clearing the value

Bug, feature request, or proposal:
selectionChange output in the select component fires twice when clearing the value which got selected.
What is the expected behavior?
Should fire once
What is the current behavior?
firing twice
What are the steps to reproduce?
Providing a StackBlitz reproduction is the best way to share your issue.
StackBlitz starter: https://goo.gl/wwnhMV
select an item from select list. ( selectionChange fires once, which is expected)
select 'None' from the list ( selectionChange fires twice which is unexpected)
https://stackblitz.com/edit/angular-pmbyc3-65mwhu?file=app/select-value-binding-example.html
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
angular 6.1.7 angular material 6.4.7
Is there anything else we should know?

Closing as a duplicate of https://github.com/angular/material2/issues/10675.


Stuck loading if port already in Use #bug

Ganache is stuck in launching screen when the port is already in use.
Expected Behavior
Show an error message.
Current Behavior
Stuck at launching screen.
Possible Solution
Show some warning.
Steps to Reproduce (for bugs)

Start geth on :8545
Set Ganache to start on :8545

Your Environment

Version used: 1.0.1.
Operating System and version: Ubuntu 16

Since this issue was created, we added the bug modal to display the EADDRINUSE error to the user.
Further,  we're making this more streamlined with https://github.com/trufflesuite/ganache/issues/665 and PR https://github.com/trufflesuite/ganache/pull/712
Thanks for reporting this however! Closing in favor of the above issue/PR

For anyone who may run into this in the future. My problem was that I was loading a truffle.js config file and it was getting stuck on the loading screen.
Running npm install inside my project folder, where the truffle.js file is, fixed the problem.


[Windows] C drive is siginificant slower than D drive which causes issue with workflow runtime being significantly increased in general

Description
This seems to affect all Windows based hosted runners.
In general tool installation, download speeds and compression and decompression on anything that is on the C drive as in any IO is significantly slower compared to D drive.
Somewhat based on research in #3577 and https://github.com/actions/setup-dotnet/issues/260
Seems like actions/setup-go seems to have made a workaround for https://github.com/actions/setup-go/pull/393
There is a suggestion to make similar workarounds in the actions/setup-dotnet https://github.com/actions/setup-dotnet/issues/260#issuecomment-1794326743
Hopefully we can find a solution that is more generic for all 😅
Maybe we can simply make the C drive similar to the D drive? That way there is no difference.
I assume this is most likely a small change in the packer script?
Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[X] Windows Server 2019
[X] Windows Server 2022

Image version and build link
https://github.com/jetersen/dotnet.restore.slow.github.action/actions/runs/6736383956/job/18311632176
https://github.com/jetersen/dotnet.restore.slow.github.action/actions/runs/6736262624
Is it regression?
Yes/No it has been a constant regression
Expected behavior
Windows actions should be similar or only a few seconds slower not like 30 seconds more.
Actual behavior
Depending on IO everything is significantly slower sometimes a whole minute slower or longer depending on how much IO.
Repro steps
https://github.com/jetersen/dotnet.restore.slow.github.action

Hello @jetersen,
We will have a look

As far as I understand, this would need a change of $GITHUB_WORKSPACE at its core. Then, actions/checkout would be able to use the D drive too.

I don't like the solution to just move everything to the D drive 😅
It means changes throughout many actions and something all actions developers have to be aware of.
I would hope the solution was to make C drive have the same iOPS, throughput and disk technology (Premium SSD, Standard SSD, Standard HDD in azure terms)

@jetersen, unfortunately, there is no simple fix to put C drive's performance on par with D drive.
There are certain limitations that we don't expect to be solved in the near future.
I will close the issue for now. Feel free to reach out to us in case of further concerns.

@shamil-mubarakshin 👋🏻 G'Day. I'm not sure I quite understand the solution here?
So changing the "C" drive's hardware isn't going to happen right now / short-term, etc. Fine. .. but surely there's still some possibility of doing some of the actions, running on the "D" drive, right?
or even making some approved actions that work on "D" allowing people to "opt-in" to this (for backwards compat)?

aren't we using the D drive by default anyway ?
Working directory is 'D:\a\<repo>\<repo>'
      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
      - uses: actions/checkout@v4
        with:
          ref: ${{needs.should_run.outputs.output1}}
          submodules: recursive


Change write_write method signatures

I was trying to achieve getting spreadsheet into memory using following code:
let mut data: Vec<u8> = Vec::new();
umya_spreadsheet::writer::xlsx::write_writer(&spreadsheet, &mut data)?;
Ok(data)

It was failing so:

I removed unnecessary Seek trait
and moved mut into parameter

After that it works perfectly

@ggodlewski
Thanks for the PR.
We have confirmed that there are no problems with the revisions and have merged them.


Make request factory return a JSONHandler

In order to guarantee encapsulation of the JSONObject's be used throughout the wrapper the JSONHandler class was created. But, it wasn't instantiated as soon as the JSONObject` was returned from the API. This PR will change that.
The benefit of this is proxy classes will not be instantiating their own JSONHandler's. Instead, it will automatically be returned from the RequestFactory.

Everything is looking great, however there is a test class present.


DRILL-7603: Allow default schema to be set for HTTP queries

DRILL-7603: Allow default schema to be set for HTTP queries
Description
This allows REST API requests and Web UI requests to specify a default
schema.  Otherwise this is not possible for HTTP clients because the
"USE" command requires a session, which HTTP clients do not have.
Documentation
POST /query.json
Submit a query and return results.
Parameters

queryType--SQL, PHYSICAL, or LOGICAL are valid types. Use only "SQL". Other types are for internal use only.
query--A SQL query that runs in Drill.
autoLimit--Limits the number of rows returned from the result set. (Drill 1.16+)
defaultSchema--Specify the default schema for the request, as if the USE command was run before the query

Testing
I added a JUnit test, and also did a bit of manual testing.
e.g.
 curl -d '{"query":"SHOW FILES","defaultSchema":"dfs.tmp","queryType":"SQL"}' -H 'Content-Type: application/json' -H 'User-Name: test' localhost:8047/query.json

I can't quite see why the tests failed, I guess maven ate the stack trace.  Locally the tests pass.  Anyone have any hints?

Looks like the Java 13 build failed for real bugs:
[ERROR] Errors:
[ERROR]   TestQueryWrapper.testShowSchemas:90->run:65->runWithDefaultSchema:85 » NullPointer
[ERROR]   TestQueryWrapper.testSpecifyDefaultSchema:99->runWithDefaultSchema:85 » NullPointer

Not sure why Java 8 failed:
##[error]The operation was canceled.

Who would cancel the operation? I've had tests fail due to running too slowly. @vvysotskyi, any suggestions?

@paul-rogers If one test fails, it cancels the others, that's why the tests were cancelled.
As for the test failure I agree it looks related to this change for sure, but I can't reproduce it.    If I had a stack trace there's a decent chance I could make a really good guess what is stopping it.

@dobesv the builds are pretty noisy (too much detail about Maven downloads), but it turns out that if I pawed though all the noise, I found your stack trace:
[ERROR] org.apache.drill.exec.server.rest.TestQueryWrapper.testSpecifyDefaultSchema  Time elapsed: 0.111 s  <<< ERROR!
java.lang.NullPointerException
at org.apache.drill.exec.server.rest.TestQueryWrapper.runWithDefaultSchema(TestQueryWrapper.java:85)
at org.apache.drill.exec.server.rest.TestQueryWrapper.testSpecifyDefaultSchema(TestQueryWrapper.java:99)

 [ERROR] org.apache.drill.exec.server.rest.TestQueryWrapper.testShowSchemas  Time elapsed: 0.049 s  <<< ERROR!
 java.lang.NullPointerException
at org.apache.drill.exec.server.rest.TestQueryWrapper.runWithDefaultSchema(TestQueryWrapper.java:85)
at org.apache.drill.exec.server.rest.TestQueryWrapper.run(TestQueryWrapper.java:65)
at org.apache.drill.exec.server.rest.TestQueryWrapper.testShowSchemas(TestQueryWrapper.java:90)
202

The "Search Logs" function in GitHub seems to not work. I had to download the logs as an archive (cleverly hidden in the "..." button.)

+1 regarding autocanceling after the failure of one of the builds.
Also, it may be simpler to look up the logs when selecting "View raw logs".
Regarding this failure, it is also present in JDK 8 build.

@dobesv for the PR that make changes in the Web UI, please also add screenshots for better visibility.

@dobesv code review summary:

please add screenshot;
address code review comment;
update commit message: must include : after Jira number: DRILL-1234: Jira title.

@paul-rogers Thanks for finding that!  Unfortunately, I think the stack trace must be incomplete.

I don't see how that line would throw NPE.  The NPE must be coming from within the run method somewhere.

Looks like I have fixed the test failures now.


h264 with Chrome

I have the mp4 / h264 codec working with Firefox v49.0.2, using: video/mp4; codecs="avc1.64001e, mp4a.40.2".
However, this doesn't stream for Chrome v55.0.2883.87.
According to window.MediaSource.isTypeSupported('video/mp4; codecs="avc1.64001e, mp4a.40.2"'), the type is supported in the Chrome browser.
Also, test file is fragmented and video is definitely using this version of the codec (tested using http://nickdesaulniers.github.io/mp4info/ and mp4file.
Any ideas what may be the problem?

Mediasource is very picky about the files that it accepts. There's probably some issue with the file you're providing that makes Chrome not happy with. I suggest taking a really close look at all the mp4 details using a tool like mp4box or even mp4-parser.

Thanks @feross !

FYI the problem was that the fragmentation wasn't applied to the keyframes under -movflags default_base_moof+frag_keyframe.
Full encode command to have this accepted by Chrome (using baseline and level 3):
ffmpeg -i ~/path/to/original.MOV -c:v libx264 -profile:v baseline -level 3.0 -c:a libfdk_aac -b:a 128k -f mp4 -reset_timestamps 1 -movflags empty_moov+default_base_moof+frag_keyframe+faststart ~/path/to/output.mp4

Glad you got it figured out! What a command! ffmpeg is true dark magic.


overfullrule=true results in overfull warnings on odd sides (chapters and pagetitles)

If I set overfullrule=true in the header to view overfull warnings I see a warning with 160pt for chapters and another other overfull warnings for  every page header:

and

Any Idea how to get rid of those warnings?

Thank you for reporting this. Unfortunately, being overfull is part of the design and cannot be avoided. The header extends into the margin and this is why LaTeX sees this as an overfull box.

Am 20-12-06 um 15.22 schrieb Federico Marotta<EMAIL_ADDRESS>
Unfortunately, being overfull is part of the design and cannot be avoided. The header extends into the margin and this is why LaTeX sees this as an overfull box.

This is bad layout.  If you want to extend material horizontally into margins you should wrap it in some horizontal box with outer width zero.  Same applies accordingly to vertical material.
Furthermore, cluttering the log with a plethora of overfull box warnings hampers the search for real pagination problems such as protruding words or hyphenation problems, e. g. in the final formatting run.
Regards,
-Moss-
Martin Wilhelm Leidig
Dante Member #1580

Ahh, sorry, I had no idea, forget about what I said. Thank you for the heads-up, I will try and use a box as suggested.

After the latest commit I don't get any warnings about overfull boxes (at least for chapters and headers) when compiling the documentation. Let me please know if there is something else.

Am 20-12-08 um 21.53 schrieb Federico Marotta<EMAIL_ADDRESS>
After the latest commit I don't get any warnings about overfull boxes (at least for chapters and headers) when compiling the documentation. Let me please know if there is something else.

I’ll take a look (see my remarks on free time in my other mail ;-), but no matter what: Kudos!
Regards,
-Moss-
Martin Wilhelm Leidig
Dante Member #1580


prep.sh --bootstrap needs updates from no longer building runtime-portable.

prep.sh --bootstrap is going to fail next time PSB is updated because it will no longer contain runtime-portable assets.  This is because the bootstrap process is trying to read various LinuxX64 package versions as shown here.
This code should be updated to reference the non-linux-x64 variants which exist for everything except the following:

MicrosoftAspNetCoreAppRuntimeLinuxx64Version
MicrosoftNETCoreAppCrossgen2LinuxX64Version

For these we should utilize the ExtraPackageVersionPropsPackageInfo infra to define non-linux-x64 variants with values defined to be the RID specific package versions.

Yes, this should all be taken care of now.


Ideas : get start session intent in jeedom

Hi,
It would be usefull to get the snips client's "start session" mqtt intent in jeedom. To make actions, like turn on lamps, turn volume down, etc...

Yes, the intent is captured by the plugin, but there is no way to launch a scenario if no binding are detected. So the plugin say the default sentence. It would be cool to have the possibility to launch a scenario for an intent with no binding detected.
And for my first idea : BEFORE the binding is detected, it would be usefull to detect when someone say the hotword "Hey snips" => launch a scenario.

In fact, the intent detection is the only trigger of any actions. hotword detected signal or session start signal. For your idea, maybe we can set a variable/ command which will be updated when an intent detected, then this updating can be the trigger of the scenario?

Yes, as a scenario can be triggered by a variable. So it do the job.
But can you set a variable or command on session start if no intent where detected?

I think it's possible for sure, but to change this we need a "good" reason. I am wondering that if there is no intent detected, how can you use this session start signal?

My reason is simple :
I would like to down the TV/music volume when a session start/a hotword is detected.
And I would like to know / run a scenario when no bindings are detected for the incoming intent.

It's a good idea though. So it means that you may have a better "sound environment" to speak your query? If so I would say the end session should also be an event to trigger the reverse scenario?
Will take into consideration.

That's it!
The best is to have all this trigger :

start session
end session
no binding found for an intent.

Thank you :)

Please check out the latest [Beta] branch (Also released beta on Jeedom market).
It added a variable (snipsMsgSession), this variable will be assigned the session id when a session started. Then when the session ended, this variable will be assigned with an empty string.
This can be the trigger of a scenario : )

I'll check and test it as soon as it will be available.
Thank you very much.
When we start a scenario with snipsMsgSession, is it possible to check the SiteId ?

Hi @CoorFun : I didn't see any update from Snips Plugin on my jeedom.
I'm set up with the git repository.
Is it normal?

Probably you have the stable version installed? I will merge this to stable these 2 days since today I would push a little configuration change to beta branch. All of these will be merged to master within this week.

Hum... I don't think..
Is there a way to going back to the beta without loozing equipments and settings?


Open up a little the OAuth/OIDC support

As a customization, I may want to change the user info endpoint in the OIDC support.

 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.


Publish version 7.1.0 to gradle plugin repository

I see that the latest version of newrelic android agent is 7.1.0 but gradle plugin repository contains only 7.0.0.
Please publish latest version of newrelic android agent to gradle plugin repository(https://plugins.gradle.org/plugin/com.newrelic.agent.android).

@LanShunoda  The New Relic plugin on the Gradle Plugin Portal is still in the Proof of Concept stage and is not fully functional. We need to make some changes on our end to make it work from the Gradle Plugin Portal. Currently, using the plugin from the Gradle Plugin Portal is not working as expected. Therefore, we recommend using the classpath method to integrate the New Relic plugin.

@LanShunoda A suggested workaround to use the plugins closure:
The Android agent plugin is not yet published to the Gradle Plugin Portal (we plan on doing this later this year), so until this is done you will have to provide the classpath to the plugin either through the buildscript DSL (as documented), or in settings.gradle(.kts) through the pluginManagement closure:
pluginManagement {
  var nr_version = "7.1.+"

  repositories {
    mavenCentral()
  }
  resolutionStrategy {
    eachPlugin {
      if (requested.id.id.startsWith("newrelic")) {
        useModule("com.newrelic.agent.android:agent-gradle-plugin:${nr_version}")
      }
    }
  }

  // optiional: define here or root level build
  plugins {
    id("newrelic") version "${nr_version}"
  }
}

Then, the New Relic plugin can be declared in either pluginManagement (above), or the project level gradle build file:
pluginManagement {
  var nr_version = "7.+"

  repositories {
    mavenCentral()
  }
  resolutionStrategy {
    eachPlugin {
      if (requested.id.id.startsWith("newrelic")) {
        useModule("com.newrelic.agent.android:agent-gradle-plugin:${nr_version}")
      }
    }
  }

  // optiional: define here or root level build
  plugins {
    id("newrelic") version "${nr_version}"
  }
}

plugins {
  id("com.android.application") version "8.1.+ apply false
  id("org.jetbrains.kotlin.android") version "1.8.0" apply false
  id("newrelic") version "<version>" apply false
}

And then applied in the app-level build file with:
// Top-level build file where you can add configuration options common to all sub-projects/modules.
plugins {
    id("com.android.application")
    id("org.jetbrains.kotlin.android")
    id("newrelic")
}

Hi there! Is there any development on this?

We have updated the gradle plugin with the latest release, you can find more details here


could the crc error correction return wrong result?

that is not discarded?
{"group":"2A","pi":"0x141D","prog_type":"No PTY","radiotext":"Jetzt on air: ** KUNGS feat. JAMIE N COMMONS ** DONT YOU KNOW","tp":true}
{"group":"2A","pi":"0x141D","prog_type":"No PTY","radiotext":"Jetzt on air: ** KUNGS feat. JAMIE N COMMONS ** DOOL YOU KNOW","tp":true}
{"group":"2A","pi":"0x141D","prog_type":"No PTY","radiotext":"Jetzt on air: ** KUNGS feat. JAMIE N COMMONS ** DONT YOU KNOW","tp":true}
DONT -> DOOL -> DONT

Weird indeed. I'll need to write test for the error detector.
This much is said about RDS error protection scheme:

Detects all single and double bit errors in a block.
Detects any single error burst spanning 10 bits or less.
Detects about 99.8% of bursts spanning 11 bits and about 99.9% of all longer bursts.
Maybe it could be a long error burst (like<PHONE_NUMBER>1)?

I let my computer record the bit stream tonight for 5-6 hours but I couldn't reproduce the problem unfortunately. This is somehow related to the noise introduced by the usb cable, dongle, computer and antenna constellation.
I have recorded samples with cases when the radiotext message is not fully displayed first, then more symbols are shown and then the full message is shown. Maybe it's somehow related but maybe it's ok

I tested the error detector with a million known error vectors, and it works as advertised. (However, error correction doesn't do anything for some reason. Erroneous blocks are discarded however).
This means that 0.1 - 0.2 % of long error bursts go undetected, so there will inevitably be some errors when the signal is very noisy.

Just for the record - this is affected by the correction algorithm.
Here's a test run to measure error detection rates for errors of different length when correction is disabled vs. enabled for 1-2 bit errors:

burstLen
don't correct
correct 1bit
correct 1-2bit

1
100.0 %
100.0 %
100.0 %

2
100.0 %
100.0 %
100.0 %

3
100.0 %
100.0 %
100.0 %

4
100.0 %
100.0 %
100.0 %

5
100.0 %
100.0 %
100.0 %

6
100.0 %
97.4 %
89.0 %

7
100.0 %
99.8 %
98.6 %

8
100.0 %
98.2 %
98.3 %

9
100.0 %
99.0 %
98.1 %

10
100.0 %
97.3 %
96.5 %

11
99.8 %
97.1 %
94.6 %

12
99.9 %
97.5 %
95.7 %

13
99.9 %
97.5 %
95.7 %

...

This shows that error detection rates are somewhat impacted by enabling error correction. This will result in some errors slipping through. I think it's an expected tradeoff of the error protection scheme used.

hm, interesting distribution. So what's the default currently? Don't correct, discard?

Currently (at least in the latest commit) errors of 1 or 2 bits will be corrected. I based this on Kopitz & Marks 1999: "RDS: The Radio Data System", p. 224: "...the error-correction system should be enabled, but should be restricted by attempting to correct bursts of errors spanning one or two bits."
1-bit errors should not be very common because of delta encoding; perhaps 2-bit errors only would suffice.

Will reopen if it causes further problems :) The restrictions mentioned in that document seem to keep it in order.


Updated gradle versions

Updated the gradle wrapper properties distributionUrl.

Great Package and cool Pull request! Can we merge this?
Would love to get around forking this Repo.

Please merge

any update on this ? can u please merge


Getting the credentials

How can I get the createPaymentURL & executePaymentURL ?
Is there specific documentation link for getting and using those values?
thanks in advance.

It will come from your backend API. To understand how to implement bKash on your backend see this library, https://github.com/shahriar-shojib/bkash-payment-gateway
Docs @ #2

This thing seems like very confusing to me. Do you guys know how to use sslcommerz in react?


eqMac versions higher than 1.3.2 cut off first half-second of every sound (like a sleep mode)

There actually already is a similar issue, but I'm unable to comment on it in order to provide my insights, so I'm opening a new issue instead. Maybe someone can merge it? I don't know, I'm new to GitHub.
The bug: For me, every version of eqMac higher than 1.3.2 is cutting off the first half-second of every sound that plays, as long as nothing is already playing. System notifications is where it's most notable, but it applies to every other sound as well.
Interesting thing is, that as long as there's something else playing, the other sounds seem perfectly fine. So when I listen to music, system sounds play like normal, but when I stop the music, they get cut off again.
It's like eqMac is going into a sleep mode and just takes some time to wake up. I actually had the same thing happen on a JBL soundbar and it was infuriating enough for me to return it. Luckily, with eqMac, I can just revert to version 1.3.2 which still works like a charm.  Every new version, I'm crossing my fingers, hoping that this time around it will work just as well, but so far, no luck.
I'm using eqMac on a Mac Mini M1 on macOS Ventura 13.1 right now, but the same problem was present on previous versions. Sound is playing on my TV through HDMI, if that helps.
I do love eqMac and I don't want to miss out on it, I just wish this one issue could be resolved so I don't have to be stuck with version 1.3.2 all my life.

This seems like a duplicate to #739. I am closing this issue now and please comment on that issue if you like. Also please let me know if this issue is still happening in the latest version of eqMac. Thanks!


fix: change acl permissions for delete and edit datasources

Description

Edit and Delete datasources functionalities are not working as expected.
Problem: Edit datasource when the edit permissions are not given works because the DatasourceServiceCEImpl#update doesn't force AclPermissions when updating, hence even when the user doesn't have the Editing permissions, the edit works.
Solution: Need to introduce AclPermission#MANAGE_DATASOURCE to the update functionality.

Problem: Delete datasource doesn't work even when the delete permissions are provided to the user, because DatasourceServiceCEImpl#archiveById uses AclPermission#MANAGE_DATASOURCES, and not all users who will have delete permissions have manage permissions.
Solution: Need to replace the AclPermission#MANAGE_DATASOURCES with AclPermission#DELETE_DATASOURCES

Fix the ACL permissions being used for the Delete and Edit Datasources

Fixes #18237
Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions, so we can reproduce.
Please also list any relevant details for your test configuration.
Delete anything that is not important

Manual
Jest
Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

#18030

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/ok-to-test sha=9a9e894

Permissions on EE do not need to be affected with the EE features.
So closing this PR.


/status endpoint should return scheme of the nodes

Description
/status endpoint currently doesn't return the scheme of the corresponding nodes which is needed by client libraries.
This feature requires changing NodeStatus message in private.proto.
Success criteria (What criteria will consider this ticket closeable?)
/status endpoint returns Scheme field in the Nodes field.

Implemented by https://github.com/pilosa/pilosa/pull/892


Question on interaction constraints

This is not a bug report but rather a question on how LightGBM deals with overlapping interaction constraints. If I understand the doc string correctly, each branch from root to leaf will split only on features appearing in one set of constraints.
So if the (Python) constraints are [[0, 1], [1, 2, 3, 4]], then the split path x0 -> x1 -> x2 is not possible because there is no constraint containing 0, 1, 2. Is this correct?
I think/hope the answer is "yes". I am asking, because for XGB, the answer surprisingly is "no".
https://github.com/dmlc/xgboost/issues/7115
@btrotta maybe?

@mayer79
The answer is "yes".
LightGBM keeps track for each leaf the features on the path from the root to the leaf. And when splitting each leaf, only features in a interaction constraint set that contains all the features in the path are allowed.
See
https://github.com/microsoft/LightGBM/blob/5b7a6f3e7150aeb704d1dd2b852d246af3e913a3/src/treelearner/col_sampler.hpp#L92-L111

Wonderful, thanks for confirmation and also the code snippet @shiyu1994 !


#2926 added go generate cloud-events-spec command

closes #2926
Signed-off-by: warber<EMAIL_ADDRESS>

@warber please rebase/merge current master branch and fix the conflict.


Grunt can't run SASS

Hi.
I have configured my Gruntfile.js with this module, but when I run Grunt it's not working, it stops. This is my code:
'use strict';
module.exports = function(grunt) {
    grunt.initConfig({
        pkg: grunt.file.readJSON('package.json'),
        sass: {
            dist: {
                files: {
                    'assets/css/estilos.css' : 'assets/css/scss/*.scss'
                }
            }
        }
    });
    grunt.loadNpmTasks('grunt-contrib-sass');
    grunt.registerTask('sass', ['sass']);
};

I have it installed with -g and --save-dev, so, this it what happened:
http://subefotos.com/ver/?2587793b6c11cd7a7b11535357c1354co.jpg
Which is it the problem?
Thanks!

Support questions are better asked on Stack Overflow:
http://stackoverflow.com/questions/tagged/gruntjs
Paste in the link to the question here so others can follow ;)

Here is the post in Stackoverflow:
http://stackoverflow.com/questions/35717218/grunt-cant-run-sass-grunt-contrib-sass


Document report: [Technical | Text field]

Description
On 'Text Field' part, you are exposing the fact that fields should have minimum and maximum length.
Can a user put a description of 0 characters or 2 000 characters?
Severity

Critical (Severe impact)

Version
1.01
Expected Correction
You should find the right limit for the:

passwords
description of a candidate
description of a company
...

Other Details
These limits will also be useful for the development of the responsiveness of the app, as thanks to this the developer will know in advance the possible mobility of the fields.

My bad

Results in commit: d5a750ee186ac41e782bf86855da0d594d99428b


[SPARK-48777][BUILD][FOLLOW] Set version to v35 since v1 is not allowed and it follows the Spark release.

What changes were proposed in this pull request?
Cleanup from #23 that needs to set the package version to something that is not v1.
Why are the changes needed?
Go compatibility
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existing tests.

Merged to master.


WASM builds for type/no-std/"universal" crates.

Testing on WASM (or other limited architectures) should help us prove out how we're doing no-alloc.

Completed with #179 and to some extent #181


.../CURRENT: Operation not permitted

"IO error: /var/mobile/Containers/Data/Application/B8C7E31C-AE41-4C00-AA807458AFA6024E/Documents/ShareStore/DataBase/CURRENT: Operation not permitted"
Errors encountered when opening the database，Is there any solution?

Did you try to put the database file in the Application Support folder?

Did you try to put the database file in the Application Support folder?

If the database is placed in the application sandbox, it should not be unreachable without access rights. Seeing the error is that the error was reported when opening the CURRENT file failed, but unfortunately I failed to reproduce this bug, do you have any ideas for solutions?

Did you try to put the database file in the Application Support folder?

The database is created in the application sandbox and must have access permissions. I saw that the error was reported when the CURRENT file failed to open. Unfortunately, I failed to reproduce this bug. Do you have any solutions?

Do you have a solution

I don't. I have never seen this issue.

I encapsulated a set of Swift calls based on LevelDB's C language API, which is compatible with Objective-LevelDB. Can you help me review the code? It's best to give some advice。https://github.com/CoderYFL/Swift-LevelDB


Auto start harvesting when NCC is started

Just like auto boot NIS, we could have "auto start harvesting" when NCC starts.

its a good idea


Pop-ups over external links

To adhere to the dotgov.gov guidelines, we should pop-up an alert message when user hovers over:

[ ] Allegheny County links
[ ] Amazon S3 links
[ ] Bidnet links

Did we confirm that we need to do this for the S3 links? They aren't ever "leaving" the page in that case, correct?

Web team didn't respond to our ask re: S3 links specifically, just that they wanted to err on the side of caution generally.


problem with @media 1++

Hi everybody i try it to add some @media with StyledComponent, when i set 2 @media don't work, only work the first @media but the second is null (the browser don't take this condition) so it's my code: if i do some wrong please tell me.
Sorry for my EnglishLive..
const Cuadrado = styled.div`

@media only screen and (max-width : 768px) and (max-device-width : 1024px) and (orientation : portrait) and (-webkit-min-device-pixel-ratio : 1) {
     #carrosel{
      background: blue;
    }
}
@media only screen and (max-width: 425px) and (max-device-witdh: 1024px) and (orientation: portrait) and (-webkit-min-device-pixel-ratio: 1) {
  #carrosel{
  background: orange;
      }
    }
 }`

@enderlabo Firstly, you have an extra bracket in second media query. Secondly, please, provide a reproduction with https://codesandbox.io

ty @Fer0x i found styled-component-breakpoint https://github.com/jameslnewell/styled-components-breakpoint so i can fix my problem, thank's.


Include SkEncodedImageFormat.h in TestSkia.cpp.

Some IWYU to allow TestSkia.cpp to build with newer versions of Skia
where SkEncodedImageFormat is not implicitly included through other
includes.

LGTM. Thanks for the PR!


feat: update wallet connection splash

Description
Updates the wallet connection splash screen to the new design.

Issue (if applicable)
Closes https://github.com/shapeshift/web/issues/7761
Risk
Low

What protocols, transaction types, wallets or contract interactions might be affected by this PR?

None.
Testing
With the REACT_APP_EXPERIMENTAL_MM_SNAPPY_FINGERS / Snaps feature flag on, the new wallet connection UI should look like this:

With the feature flag disabled it should look like this:

Also ensure that the wallet connection flow works as expected.
Engineering
☝
Operations

[ ] :checkered_flag: My feature is behind a flag and doesn't require operations testing (yet)

☝
Screenshots (if applicable)
See above.

@reallybeard this is open for review, you might want to tweak the background gradient as I had a best effort attempt at replicating the mock.

@reallybeard this is open for review, you might want to tweak the background gradient as I had a best effort attempt at replicating the mock.

Oh, I felt like this was a placeholder but wasn't intended to be changed
In this case, I think we can simply export the whole left gradient into an SVG and use it as a backgroundImage to replicate it 100% and in a safe way

@reallybeard this is open for review, you might want to tweak the background gradient as I had a best effort attempt at replicating the mock.

Oh, I felt like this was a placeholder but wasn't intended to be changed
In this case, I think we can simply export the whole left gradient into an SVG and use it as a backgroundImage to replicate it 100% and in a safe way

Yeah that ticket/mock isn't really clear. I'm also not convinced that we want to remove the ShapeShift logo entirely, but that's what the mocks seem to suggest...

Also @NeOMakinG from "incorporate gradient on left" on the ticket I'm guessing it is meant to be changed!

Also @NeOMakinG from "incorporate gradient on left" on the ticket I'm guessing it is meant to be changed!

sure! It was sneaky 😆
If you want to replace it by an SVG to replicate the mockup, feel free

Thanks for the excellent review, @NeOMakinG!
Agree about the log removal... @reallybeard @twblack88 are we sure we wanna drop it?


Update SBT to 0.13.9

+1

How about 0.13.11? ;)

Closing in favor of https://github.com/1science/docker-sbt/pull/2


Redeemables (gifts cards or coupon codes)

EDIT: Original title - Gift cards
-- @patcon

It would be fantastic if Gittip allowed us to purchase Gift cards, that could be emailed, printed, or issued via the developer API.
This would be a great way to get the non-initiated into the community.
Such use cases could be:

When one of us evangelises gittip to a friend, we can get them in by buying them a $20 gittip gift card. This technique is common place with bitcoin evangelists.
We can get people gittip gift cards for their birthdays or whatever other special occasion. While this may be disgruntled by the regular joe, it's not the case for everyone, in fact a dear friend of mine @nikolayhg is working on The Sharing Birthday Initiative that focuses on reframing birthdays from one of taking, to one of giving, with good success.
It would also allow some really interesting business models to arise.

One such example is allowing the customer direct control over where the commission/profit of a physical product actually goes. This can work by the retailer providing an online service where you enter your receipt and barcode number of the product into their online service, and the comisision/profit of the product is then given to you as a gittip gift card, that you can then distribute to whomever you pleased. This I feel is a game changer, for the purpose that vast vast majority of those whom I tell gittip about, never compute the model, however they already understand the typical value sale model. I buy a product for its perceived value, the seller gets the commission/profit, and unfortunately, I have no control of where that money goes, or who it should go to. With this change, it changes "commission/profit" into "mandatory donation" instead.

The actual conversations I have with those in the retail industry goes something like this: "I don't think this model of sales commission is ethical, as it is fundamentally excludes people — which retailer misses out on my commission? and which retailer gets to eat?" — "Yes... but it is still better than the pyramid scheme of Woolworths, at least, we the people, are getting the money" — "Yes, no doubt it is an improvement, though no stopping there, there is always room to aim for the best, not just what is better, perhaps, considering no one would deny the product is worth the price it is fixed at, how about, instead we give the user control of where there commission goes, to ensure they can feed all those they wish to feed with their commission. Now instead of the consumer deciding who starves and who gets to eat, dictated by who they conduct the sale with, now, when a sale is performed, the consumer can ensure all those who've given them value and who they believe in, gets to eat" — "Holy cow, that's amazing! We'd get behind that." — "Cool, I'll chat with the gittip people about it."

Update: I'll turn this new business model idea into a blog post instead, so it doesn't detract from the discussion about gift cards.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Closing in light of our decision to shut down Gratipay.
Thank you all for a great run, and I'm sorry it didn't work out! 😞  💃


[Question] How do I set different iam_role for prod and non-prod folders ?

How do I set different iam_role for prod and non-prod folders?
considering this PR from 2018 => https://github.com/gruntwork-io/terragrunt/pull/599/files#diff-04c6e90faac2675aa89e2176d2eec7d8 it seems that I can configure a specific iam_role to be used by terragrunt (and terraform).
My goal is to have a CI/CD (Atlantis) to assume roles when executing the terragrunt command.
How can I set up one role for non-prod folder and a different one for the prod folder?

There are a number of options, including:

Have a different root prod/terragrunt.hcl and non-prod/terragrunt.hcl, each with different iam_role setting, that all the child modules include.
Have a single root terragrunt.hcl that uses generate to generate a provider block with an assume_role block within. The assume_role block can set role_arn to a variable, which in prod envs you set to a different value than non-prod envs.

To add another option:
I am making use of direnv (https://direnv.net) for which I create .envrc files in the different account folders. This is what I include:
export TERRAGRUNT_IAM_ROLE=arn:aws:iam::ACCOUNTID:role/ROLE and other env variables as needed.
I am then able to go into the directory with the right role assumed and then being able to run Terragrunt.

Based on the input of @brikis98, I have created an example for option 2, see:
https://github.com/nilsdebruin/terragrunt-infrastructure-live-example/tree/assumed-role-example
If it is interesting enough, I could create a pull request for it.


Defined product details block target and added docs

Resolves https://github.com/Shopify/pos-next-react-native/issues/39082
Background
This PR follows the same pattern as the previous post purchase block target PR.
Solution
Creates the new target for pos.product-details.block.render, and utilizes the previous defined BlockComponents type. It also uses the APIs defined in the tech doc
🎩

The target list https://shopify-dev.ui-extensions-c5yb.jeansebastien-goupil.us.spin.dev/docs/api/pos-ui-extensions/unstable/targets
The new docs and examples for product details block: https://shopify-dev.ui-extensions-c5yb.jeansebastien-goupil.us.spin.dev/docs/api/pos-ui-extensions/unstable/targets/product-details/pos-product-details-block-render

Make sure that the new docs and examples don't have any typos and are using the correct target names and APIs.
Make sure that the new doc page is linked properly everywhere

Checklist

[ ] I have :tophat:'d these changes
[ ] I have updated relevant documentation

Since were doing docs all together with the targets, we should start adding them into the 2024-10 version change log as well. Could you start a section here adding the post-purchase block and also this new details block to https://github.com/Shopify/ui-extensions/blob/unstable/packages/ui-extensions/docs/surfaces/point-of-sale/staticPages/pages/versions.doc.ts


Fixes to slack.attachment support

When attempting to emit slack.attachment from a router response in our hubot, I saw the dreaded ReferenceError: robot is not defined error in the logs. I updated the customMessage function to check the passed username with @robot.name rather than robot.name.
Then I noticed by passed name wasn't working (was showing up as 'Bot'). Fixed that too. :wink:
Works great now! Thanks for adding support for attachments back into the adapter!

Any idea when this will find its way into NPM? Would love to be able to use a custom username and emoji when also using attachments.

:+1: on getting this out the door!

cc https://github.com/slackhq/hubot-slack/issues/228 for tracking getting this released


CLI: kontena service logs --tail skips loglines

$ kontena service logs --tail sidekiq | grep QUEUE

then run
$ kontena container exec railsapp-1 rails runner \"puts EnqueueJobForAllRecordsOfClass.perform_async(\'SomeModule::SomeClass\', \'User\')\"

You are expecting to see log lines with numbers 1-600 in log tailing, but you only see a random batch from the middle of the log lines.
The following command shows the correct log lines:
$ kontena service logs --lines=10000 sidekiq | grep QUEUE

I'm unable to reproduce this on 0.15.1 or current master. I'm testing with a minimal docker test image:
FROM debian:jessie

CMD ["bash", "-c", "sleep 10 && for i in {1..600}; do echo 'log' $i; done; sleep 60"]

Running kontena service create test test, I haven't been able to spot any missed log lines in kontena service logs --tail test.
How exactly does the kontena service logs command behave in this case with the current release? Does it exit (see #978) or start eating memory (see #972)?
Can you test if this still happens with the current kontena master or upcoming 0.15.2 bugfix release containing those fixes?

@juhazi can you jump in here?

On 07 Sep 2016, at 12:33, Tero Marttila<EMAIL_ADDRESS>wrote:
I'm unable to reproduce this on 0.15.1 or current master. I'm testing with a minimal docker test image:
FROM debian:jessie
CMD ["bash", "-c", "sleep 10 && for i in {1..600}; do echo 'log' $i; done; sleep 60"]
Running kontena service create test test, I haven't been able to spot any missed log lines in kontena service logs --tail test.
How exactly does the kontena service logs command behave in this case with the current release? Does it exit (see #978) or start eating memory (see #972)?
Can you test if this still happens with the current kontena master or upcoming 0.15.2 bugfix release containing those fixes?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Second unsuccesful attempt to repro with the "exec in client to trigger server logs" flow, using the minimal test-server and test-client Docker images here: https://gist.github.com/SpComb/559ab58a232d679183fdaddb781ba9dc
kontena service create test-server test-server && kontena service start test-server
kontena service create test-client test-client && kontena service start test-client
And then watching: kontena service logs -t test-server while running kontena container exec test-client-1 /test.sh. All of the /test/1 to /test/600 logs show.
I suspect this might be something related to the multiple-partial-json-chunks issue fixed in #972 combined with some SocketError that triggers a CLI-side retry of the get_stream("services/..../container_logs")request, but that's tricky to confirm. Alternative is some bug in the server-side stream-loop mongodb queries.

confirmed that your repro is also unsuccessful in our grid.
also our original repro no longer reproducres either. Kontena in our grid has been updated to 0.15.1 after the original issue report.
I did not make a note of kontena version when originally reporting this. :(
I recommend closing this.

BTW, are you sure this was with kontena service logs and not kontena app logs?
I just submitted some fixes in #984 that could easily have caused this kind of issue with kontena app logs...

it's possible. I mix and match kontena grid logs, kontena service logs and kontena app logs as needed.

With the fixes for kontena app logs (#987) and kontena service logs (#972) in master, I hope this should be fixed.
Please re-open if this still happens with git master or the upcoming 0.15.2 release.


build(dgeni): updated daffodil packages

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] The commit message follows our guidelines: https://github.com/graycoreio/daffodil/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Fixes: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[ ] No

Other information

@Nolan-Arnold Can the packages search be "inverted"? That way we exclude the packages we don't want to be included in docs, as opposed to the reverse.

@Nolan-Arnold Can the packages search be "inverted"? That way we exclude the packages we don't want to be included in docs, as opposed to the reverse.

This is a good idea, as it will have us not have to add packages each time. Check out the changes in 2b6cb3486f65f130a82613bc64268ad74a295227


AddRouteAnnotationRector ignore prefix on resource files

I've started the migration of a very old Symfony 2.3 project and it have a routing.yml file to import other files.
From a YAML like this
api_public_webservice:
    resource: "routing_api_public_webservice.yml"
    prefix: /api-public

the result is (after apply annotations to routes rule too)
#[Route("/webservice", name: "api_public_webservice")]

because in recent Symfony versions (in my case 4.4) the files in the routes directory are loaded automatically without see the content of the routing.yml file.
I don't know if this could be relevant or not, but could happend in other cases.

Hi, thanks for reporting.
What is the responsible rector rule?

Is AddRouteAnnotationRector

Thanks! Could you add a failing test fixture to AddRouteAnnotationRectorTest?

Closing for lack of further response. Feel free to reopen with failing test fixture, thanks for understanding :+1:


Fix removal of VCS icon

The script was using the hCtBAQ class to select the VCS icon in the project view, however this no longer works in the 3.7.0-beta1 version of the Unity Hub (and presumably other future versions as well).
I'm guessing this is because the class name is generated at build time and changes with each release. Instead we can use the fact that the VCS element is the only element with the role="presentation" attribute set to select it in css and hide it.

thanks!


Issue 29 : Fixed all grammatical and punctuation errors in the entire website.

Linked Issue
Closes: #29
Describe the changes you've made

Fixed all grammatical errors.
Fixed all punctuation errors.
Reduced the number of words on the page for a better user experience.

Type of change
What sort of change have you made:

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Describe how have you verified the changes made
Checklist:

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[ ] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] Any dependent changes have been merged and published in downstream modules.

Screenshots
**Original Text: **

**Fixed/Enhanced Text: **

This issue is against the norms of KSoC.


using EntryPointNotFoundException instead of ApplicationException

The documentation for ApplicationException remarks to not throw or catch any Exceptions of this type.
I replaced it with the EntryPointNotFoundException I found referenced in NativeLibrary.GetExport(IntPtr, String).
Besides that I made some refactoring and started using the Range-Operator in Span.Slice Method calls.

Hi firstly thanks for getting involved. I'm not going to merge this pull request as most of it is just stylistic opinion.
With that in mind, I do think your point about the EntryPointNotFoundException is valid. If you could open a new pull request with the change from ApplicationException to EntryPointNotFoundException (without any of the refactoring,) I'll get that merged in.

You can actually pick the changes you want to get merged.
You could also just merge the relevant commit.
Do you want to try that?

I tried to do something similar earlier but GitHub has change their interface so much since I last accepted a PR I couldn't figure out how to do it.  Maybe it would be easier to just rebase your branch back to the 1830e50 commit and send that through?


[AMBARI-24303] [Log Search UI] Move the dev environment information from .gitignore to README.md

What changes were proposed in this pull request?
In this change the webpack develompent configuration information has been moved from .gitignore to README.md file.
How was this patch tested?
No need testing, but the unit test are all successful.
Please review Ambari Contributing Guide before opening a pull request.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3154/
Test PASSed.


Unmounted routes do not lose params

Describe the bug
Navigating away from a route does not affect useParams used in other components.
Your Example Website or App
https://stackblitz.com/edit/tanstack-router-8wswvp?file=src%2Fmain.tsx
Steps to Reproduce the Bug or Issue
Change route, reload and change route again. Uncomment line 40 to make it work.
Expected behavior
Text should change
Screenshots or Videos
No response
Platform

v0.0.1-beta.209

Additional context
No response

Fixed latest!


expose error_code in ResponseError

This addresses Issue #20. Accessing both the symbol name and string is necessary, since the fallback from the JSON failing to be parsed uses the symbol :error_code, but the actual JSON key is a string.

Thanks, merged.


Telecommand scheduling: suffix tag parser, executor thread, agenda/schedule

Main Change: Schedule command exeuction in the future with: CTS1+hello_world()@tsexec=25000!
Features:

Created suffix tag parser (for parsing @tsexec=uint64 values), with unit tests
Implemented telecommand executor thread (TASK_execute_telecommands), and moved execution from the UART receive thread to this executor thread
Developed telecommand agenda/schedule (TCMD_agenda array)
Isolated parsing from execution steps (parsing in umbilical UART receive thread still)

Other Updates:

Added warning in TIM_set_current_unix_epoch_time_ms if a resync timestamp is before the previous resync timestamp, as that case will create confusing log messages (but should never happen in reality).

Closes #15

Thanks for the review! Fixed that comment, and opened 3 new issues to capture those agenda-related operations. Great comments!
I'll advise that persisting the agenda to the filesystem and reading it from the filesystem (now Issue #110), while nice to have, is probably a task that would be better to leave until all other mission requirements are satisfied.


Shap.plots.bar and shap.plots.waterfall - Are these working currently?

Hi -
Issue# 1
I am following the example plot for for bar and waterfall here but not able to run the code. Can anyone confirm are these deprecated in the latest versions of SHAP.
import xgboost
import shap

# train XGBoost model
X,y = shap.datasets.adult()
model = xgboost.XGBClassifier().fit(X, y)

# compute SHAP values
explainer = shap.Explainer(model, X)
shap_values = explainer(X)

Exception                                 Traceback (most recent call last)
/usr/local/lib/python3.6/dist-packages/shap/explainers/_linear.py in supports_model_with_masker(model, masker)
268         try:
--> 269             Linear._parse_model(model)
270         except e:
3 frames
/usr/local/lib/python3.6/dist-packages/shap/explainers/_linear.py in _parse_model(model)
255         else:
--> 256             raise Exception("An unknown model type was passed: " + str(type(model)))
257
Exception: An unknown model type was passed: <class 'xgboost.sklearn.XGBClassifier'>
During handling of the above exception, another exception occurred:
NameError                                 Traceback (most recent call last)
 in ()
7
8 # compute SHAP values
----> 9 explainer = shap.Explainer(model, X)
10 shap_values = explainer(X)
/usr/local/lib/python3.6/dist-packages/shap/explainers/_explainer.py in init(self, model, masker, link, algorithm, output_names, feature_names, **kwargs)
97
98                 # use implementation-aware methods if possible
---> 99                 if explainers.Linear.supports_model_with_masker(model, self.masker):
100                     algorithm = "linear"
101                 elif explainers.Tree.supports_model_with_masker(model, self.masker): # TODO: check for Partition?
/usr/local/lib/python3.6/dist-packages/shap/explainers/_linear.py in supports_model_with_masker(model, masker)
268         try:
269             Linear._parse_model(model)
--> 270         except e:
271             return False
272         return True
NameError: name 'e' is not defined
Issue 2:
When I try to use plots.bar and plots.waterfall with TreeExplainer, I get below error:
shap.plots.bar(shap_values_train)

AssertionError                            Traceback (most recent call last)
 in ()
----> 1 shap.plots.bar(shap_values_train)
/usr/local/lib/python3.6/dist-packages/shap/plots/_bar.py in bar(shap_values, max_display, order, clustering, clustering_cutoff, merge_cohorts, show_data, show)
49         cohorts = shap_values.cohorts
50     else:
---> 51         assert isinstance(shap_values, dict), "You must pass an Explanation object, Cohorts object, or dictionary to bar plot!"
52
53     # unpack our list of Explanation objects we need to plot
AssertionError: You must pass an Explanation object, Cohorts object, or dictionary to bar plot!
Note: I am using Colab

Hi, I am not able to run the code either...
Python 3.8.3
Shap version: 0.37.0
I get the same error

hi, have u solved the problem, I met the same problem when running this  https://github.com/slundberg/shap/blob/master/notebooks/general/Explainable AI with Shapley Values.ipynb

I am getting:
shap.plots.waterfall(shap_values[1])

TypeError                                 Traceback (most recent call last)
 in
----> 1 shap.plots.waterfall(shap_values[1])
TypeError: 'module' object is not callable

I am getting:
shap.plots.waterfall(shap_values[1])

TypeError                                 Traceback (most recent call last)
 in
----> 1 shap.plots.waterfall(shap_values[1])
TypeError: 'module' object is not callable

I had the same problem, replaced the shap.values with explainer(X) and it worked.

I had the same problem, replaced the shap.values with explainer(X) and it worked.

Could you please provide the code detailed? I can't fix this either. Thank you very very much in advance

I'm having the same issue. Upvoting for visibility.

same issue here,
TypeError: 'module' object is not callable

Has this issue ever been resolved?

I had the same problem, replaced the shap.values with explainer(X) and it worked.

Could you please provide the code detailed? I can't fix this either. Thank you very very much in advance
@slundberg

In this line: shap.plots.bar(shap_values_train), I replaced the shap_values_train parameter with explainer(X). I hope this solves your problem too. I will re-run my script and will update this answer if anything changes.

It seems that waterfall has become a module, and the function to be called is waterfall_plot. But curiously, it's not specified that way in the docs.

For me
This:
ex = shap.TreeExplainer(model)

ex(X)

resulted in:

ValueError: could not convert string to float: 'MY_CATEGORY_NAME'

and this:
ex = shap.TreeExplainer(model, X)

resulted in

Found a NULL input array in _cext_dense_tree_update_weights!
...
ValueError: could not convert string to float: 'MY_CATEGORY_NAME'
...
Exception: Currently TreeExplainer can only handle models with categorical splits when feature_perturbation="tree_path_dependent" and no background data is passed. Please try again using shap.TreeExplainer(model, feature_perturbation="tree_path_dependent").

Same errors using tree_path_dependent and Explainer instead of TreeExplainer.
Anyone resolved?

I have the same issue. Anyone?

I have the same issue too.

I also have similar issue

Same issue this library looks broken . . .

Given some dataframe with column text that contains a sentence.
cv = CountVectorizer(max_features=4000)
X = cv.fit_transform(sentimentTrain.text)
y = sentimentTrain.sentiment
model = xgboost.XGBClassifier().fit(X, y)
explainer = shap.Explainer(model, X)

Causes that issue.

I have the same issue too. Anyone solved?

shap.plots.bar(explainer(x_test))

The problem solution:
shap.summary_plot(shap_values[1], X_test, plot_type="bar")

The two issues described in the OP both work for me on shap 0.43.0, so maybe this has been resolved and can be closed?

Closing as this issue appears to be fixed since we merged in the various fixes from the "Community fork" in #2943.
Please don't hesitate to open a new issue if you encounter this again.


chore: Add GitHub Action for CI

Adds a GitHub action for automated CI, including:

Lint Go code using golangci-lint
Codegen linter to ensure that all codegen is up-to-date in a single change
Ensure that license headers are correct for Go code using lsm-dev/license-header-checker
Test Go code and upload coverage to Codecov

Not sure why the action is not running... 🤔  perhaps it doesn't work when creating a new workflow for the first time in a separate branch... will merge and try again


K8s not successfully started when using too few nodes/small flavor size

Running on OpenStack (SSC) using:
master_flavor = ssc.small
node_count = "2"
node_flavor = "ssc.medium"
edge_count = "1"
edge_flavor = "ssc.medium"
running:

terraform apply openstack

finishes successfully, but running the following command to show that everything worked says that many of the kubernetes pods are not running due to STATUS "Outofcpu":

ansible master -a 'kubectl get pods --show-all --all-namespaces'

We tried bumping flavor size and node_count/edge_count but that results in the same "OutOfcpu" STATUS for many pods.

@jonandernovella did you experience the same on SSC?

@mcapuccini @StaffanArvidsson I did not experience this. Please come by tomorrow if you continue experiencing this issue.

Running with three medium nodes now (one master, one edge and one node), the kubedns pod get's stuck at ContainerCreating (0/4). The logs for the pod looks like
log.txt

@jonalv is this before or after running ansible-playbook playbooks/install-core.yml?

This was before. Will try to run that stuff as well now

It seems medium sized nodes are needed. As for the getting stuck part that doesn't happen once the core stuff is installed. I suggest this ticket can be closed.


Route intercept does not work with generateStaticParams in layout

Description
Route intercept seizes to work once generateStaticParams along with unstable_setRequestLocale are added to [locale]/layout.tsx. The params passed to the route group (modal) does not include locale.
NOTE: this does not manifest when running on local - only in prod mode.
Verifications

[X] I've verified that the problem I'm experiencing isn't covered in the docs.
[X] I've searched for similar, existing issues on GitHub and Stack Overflow.
[X] I've compared my app to a working example to look for differences.

Mandatory reproduction URL
https://github.com/IikkaWinter/nextagram-intl
Reproduction description
Steps to reproduce:

Clone my fork of nextagram-intl example repo
npm run build and npm start to start in prod mode
Open landing page and notice that the prefetched photo server components are responding with 404
Click on the picture and the photo root route is rendered instead of the modal
Observe the console log on server taking note on missing locale in modal params

Expected behaviour
The picture modal should be shown as when running in dev

Possibly related to https://github.com/amannn/next-intl/issues/255.


onActivityResult from Activity is never called

Hi,
I really would like to use your library but I have the above mentioned issue.
Here's the code I'm using:
public class SplashActivity extends AppCompatActivity {

    static final Map<Integer, Integer> mImages;
    static {
        final Map<Integer, Integer> map = new HashMap<>();
        map.put(0, R.drawable.overview);
        map.put(1, R.drawable.bring_color);
        map.put(2, R.drawable.detail);
        mImages = Collections.unmodifiableMap(map);
    }

    @Override
    protected void onCreate(final Bundle savedInstanceState) {

        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_splash);

        new IntroductionBuilder(this)
                .withSlides(generateSlides())
                .withStyle(IntroductionBuilder.STYLE_FULLSCREEN)
                .withOnSlideListener(new IntroductionConfiguration.OnSlideListener() {
                    @Override
                    protected void onSlideInit(final Fragment context, final int position, final TextView title, final ImageView image, final TextView description) {

                        ImageLoader.getInstance().displayImage(String.format("drawable://%s", mImages.get(position)), image);
                    }
                })
                .introduceMyself();
    }

    private List<Slide> generateSlides() {
        List<Slide> result = new ArrayList<>();

        result.add(new Slide().withTitle("Behalte den Überblick")
                .withDescription("Ordne deine Bücher in virtuellen Regalen.")
                .withColorResource(R.color.primary));
        result.add(new Slide().withTitle("Bring Farbe ins Spiel")
                .withOption(new Option("Nutze dynamische Farbgebung", true))
                .withColorResource(R.color.primary_dark));
        result.add(new Slide().withTitle("Detail").withDescription("Another description")
                .withColorResource(R.color.accent));

        return result;
    }

    void proceed() {

        final Intent i = new Intent(App.getContext(), MainActivity.class);
        startActivity(i);
        finish();
    }

    @Override
    protected void onActivityResult(final int requestCode, final int resultCode, final Intent data) {

        if (requestCode == IntroductionBuilder.INTRODUCTION_REQUEST_CODE &&
                resultCode == RESULT_OK) {

            for (final Option option : data.<Option>getParcelableArrayListExtra(IntroductionActivity.OPTION_RESULT)) {
                if (option.getPosition() == 1) {

                    PreferencesHelper.setBooleanPreference(R.string.settings_category_ui_dynamic_coloring_key, option.isActivated());

                }
            }

            proceed();

        } else {
            //Disable Feature A.
            //Handle other request codes.

            proceed();
        }

        proceed();
    }
}

Is there any error in my code?

Hmm, seems correct from a quick look. Have you tried to debug to see if it is called, but maybe result was not RESULT_OK?
I will look into that.

Yes, I did. I've set a breakpoint at the if statement
if (requestCode == IntroductionBuilder.INTRODUCTION_REQUEST_CODE &&
                resultCode == RESULT_OK)

and that breakpoint is never hit.

Ok, I will have a look.

I was just looking around StackOverFlow about this problem. Have you set anything to your Activity in the Manifest like android:launchMode="singleInstance" or android:noHistory?

Yes, I've set the android:noHistory attribute of the SplashActivity.

Ok, that's the reason why it does not work.

Here you can find some info about htat: http://stackoverflow.com/questions/28589494/androidnohistory-true-behavior-but-still-catch-onactivityresult

Thank you for your quick reply. I will check that an report back

Okay, great.

The answer provided in your SO link does the trick. This "issue" can be closed.
Tank you very much

Okay, no problem.


Consider explaining term "Just" in readme

Hi, I've never used a language with Maybe/Monads before and don't understand why a value is "Just" if it's defined. Nothing is intuitive but Just doesn't really make sense to me. I tried googling to find the historical precedent. I can see that it's the same terminology as Haskell but couldn't find an explanation of the etymology.
Could you add something to the README to explain why it's called just? Would help me wrap my head around it.

This is a guess but I imagine it's to facilitate the nice fluent interface maybe(value).orJust('default').

Yeah it's just a reference to Haskell.
For example: Just a is just a (where a is a value).


Error: Buffer is not defined

Describe the bug
After creating a NodeJS project, try to connect to Github as a new private repository, enter a name and click create repo and push, the Error: Buffer is not defined pops up, the repo is created in Git but it does not push its contents:
https://www.screencast.com/t/k2rd8mHyolDl
Link to the blitz that caused the error
https://stackblitz.com/edit/node-q8cb9b
Steps to reproduce

Click on new Node.js blank project

Once the workspace loads, click on Connect repository

Enter a name, make it a private repo and click Create and Push

Expected behavior
The repo should be created and pushed to Github completely without issues
Screenshots

Platform
Browser name  = Chrome
Full version  = 97.0.4681.0
Major version = 97
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4681.0 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 77005951,
  "usedJSHeapSize": 70911239,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Hash = f0f0e35d34e6f38828752db79b041c48b98806b5

Additional context
No response

Looks like the issue is no longer reproducible (perhaps fixed already)

I confirm this is not happening to me anymore.

:tada: We shipped a fix for this recently, glad that it's gone.


New version: OSGeo.QGIS_LTR version 3.34.5

Pull request has been created with komac v2.1.0 :rocket:

Resolves #147286

Microsoft Reviewers: Open in CodeFlow

@wingetbot run

@wingetbot run

@wingetbot run

@wingetbot run

This package installs and launches normally on a Windows 10 VM.

Hi @BiosPlus,
This manifest adds Apps and Features entries that aren't present in previous PR versions. These entries should be added to the previous versions, or removed from this version.
(Automated response - build 876.)

Reset approval workflow.

This package installs and launches normally on a Windows 10 VM.


Would it be possible to add 'config' to the list of template fields for EmrServerlessStartJobOperator?

We have a use case where we would like to start job runs in EMR Serverless where the job name is derived from the output from a previous task.
Since the job name is passed via the 'config' argument to the EmrServerlessStartJobOperator, this request is to add 'config' to the list of 'template_fields' in that operator (https://github.com/aws-samples/emr-serverless-samples/blob/main/airflow/emr_serverless/operators/emr.py#L144-L149), if at all possible.
Thanks in advance,
Franco Venturi

Hey Franco - this should definitely be feasible! There will likely be a new release in the coming weeks.


runtime error while executing cf-mgmt export-config

2019/02/20 07:04:15 I0220 07:04:15.093035 17876 yaml_config.go:391] Writing out bytes for security group taa-services-dev-asg
2019/02/20 07:04:15 I0220 07:04:15.093418 17876 exportconfig.go:328] Adding default security group default_security_group
2019/02/20 07:04:15 I0220 07:04:15.104757 17876 exportconfig.go:336] Adding rules for default_security_group
2019/02/20 07:04:15 I0220 07:04:15.105071 17876 yaml_config.go:397] Writing out bytes for security group default_security_group
2019/02/20 07:04:15 I0220 07:04:15.119147 17876 yaml_config.go:402] Writing out orgQuota default
2019/02/20 07:04:15 I0220 07:04:15.119588 17876 yaml_config.go:402] Writing out orgQuota runaway
2019/02/20 07:04:15 E0220 07:04:15.200351 17876 export_config.go:48] Export failed with error:  unauthorized
error: unauthorized
$ ./cf-mgmt-linux version
v1.0.17-db3a71d88c86f7a6cef1c3b05fd14336a7177599

Can you provide more output via export LOG_LEVEL=debug?  Setting this environment variable will provide more insights.

Believe this is due to missing permissions needed around routing.
https://github.com/pivotalservices/cf-mgmt/blob/master/README.md#create-uaa-client

Hi, the output was generated with LOG_LEVEL=debug.
But you are right: was missing !
$ uaac client get cf-mgmt
scope: uaa.none
client_id: cf-mgmt
resource_ids: none
authorized_grant_types: refresh_token client_credentials
autoapprove:
authorities: scim.write scim.read cloud_controller.admin
name: cf-mgmt
lastmodified:<PHONE_NUMBER>000
$ uaac client update cf-mgmt --authorities cloud_controller.admin,scim.read,scim.write,routing.router_groups.read
scope: uaa.none
client_id: cf-mgmt
resource_ids: none
authorized_grant_types: refresh_token client_credentials
autoapprove:
authorities: routing.router_groups.read scim.write scim.read cloud_controller.admin
name: cf-mgmt
required_user_groups:
lastmodified:<PHONE_NUMBER>000
Now, export-config is working !
Thanks a lot for your help
btw: nice work !


Add a space in Shortcut Guides for PowerToys's shortcuts

Description of the new feature / enhancement
As of today, we have the Shortcut Guide to display Windows's shortcuts, but often PowerToy's shortcuts are more complex and even if you choose to customize you will face a learning curve to make it part of your workflow. Navigating the program each time I forget a hotkey (default or customized) can be frustrating.
The idea is to have a section in the Shortcut Guide to show a cheat sheet of the user's current PowerToys hotkeys.
Thank you so much to every collaborator behind this project you have facilitated my life in the past few years!
Scenario when this would be used?
It would make usability more fluid as the user is learning to use the software via hotkeys. They wouldn't have to navigate through the software searching for a hotkey.
The same logic behind Shorcut Guide for Windows hotkeys, applied to PowerToys.
It would be a cheat sheet we easy access for the tool's shortcuts, may it be the default ones or the ones the user's customizations.
Supporting information
No response

/dup #890


Provisioning profiles endpoint should expose extra data

It is a common pattern to locate extra data with the provisioning profiles in profiles.yaml. For example, it is reasonable to have a profiles.yaml contain extra fields like what OS to provision, what VLAN the profile requires, what style of disk partitioning should be used, etc:
---
profiles:
    searchnode:
        label: "Search Server"
        prefix: "search"
        allow_suffix: true
        primary_role: "SEARCH"
        pool: "SEARCH_POOL"
        secondary_role: "MASTER"
        requires_primary_role: false
        requires_secondary_role: true
        requires_pool: false
        cobbler_profile: "centos-5.6-x86_64-db-v2"
        operating_system: "centos_5"
        vlans: ["search"]
        disks: hw_raid_10

When hitting the /api/provision/profiles endpoint, it omits all these juicy extra fields, which is very disappointing. Ideally these extra attributes could be made available to API consumers like provisioning systems to make appropriate decisions about how to do the needful. cc @Primer42 @defect @schallert @roymarantz
The data currently returned looks like:
#<Collins::Profile:0x007fdd1204d700 @options={:profile=>"devnode", :label=>"Dev Node", :prefix=>"dev", :suffix_allowed=>true, :primary_role=>"DEVELOPMENT", :requires_primary_role=>true, :pool=>"DEVELOPMENT", :requires_pool=>true, :secondary_role=>nil, :requires_secondary_role=>false}>

Perhaps there could be an extra field with extras: in it, and just dump json of all the other bits there?

I agree, and it's something that's been bothering me as well. I took a quick look at the yaml parsing and while it would be nice to just take "left over" keys and collect them under an extras key in the json i think that might be tricky without doing a lot of snakeyaml magic.
What i think might be easier (i haven't tried it though) would be to make extras an "official" key and just keep the data there instead of under arbitrary top-level keys. I'll try to get a PoC going when i have some time over to show what i mean.

I'm wondering why extras is visible at all.  To me it is an implementation detail that should be hidden and the "model" should be a flat key space.  I know there can be (and IIRC is) duplicate keys, but I consider that a bug.

@defect I agree on the extras key. Seems easiest. Only question I have is whether or not that field can be raw json data (i.e. arbitrarily nested objects) or if it has to be deserialized to a java object like Hash[String,String]. The API consumers are working with straight json, so id like to not remove any expressivity from the extras blob if possible. I was going to start knocking together a prototype as well :)
@roymarantz the extras is for other systems, not collins. the other systems are the implementation details of the provisioning systems.

@byxorna I guess that depends on what you mean by collins.  I like to think of it as a KV store which supports provisioning, but not really part of the provisioning system.  YMMV

@byxorna I messed around a bit with it the other day, and having arbitrary object as the key seems less than trivial. I think we'll need to support at least lists and maps in the extras. Just moving

@defect same with me. It looks to be really annoying, because the yaml is deserialized into a JProvisionerProfile. I couldnt find a way to mark a field as unparsed (ala json.RawMessage in go).
Heres a crazy thought: We could change the endpoint and instead of unmarshalling/remarshalling, we could just serve the yaml file straight away. It does't look like snakeyaml supports partial decoding on unknown fields, so thats one possibility. Another would be to not touch the existing JProfile nonsense, and add an additional YAML.load() step in the API action that would reparse the profiles.yaml and join in the extra data with the JProfile json? Or rewrite collins in a language that doesnt make this like punching yourself in the face.


deployClusterTask has the wrong name in task.prod.json

When you add the task to azure-pipelines.yml the following name is added to the task: databricksDeployScripts@0. The same name is being used by the databricksDeployScripts task.
The workaround for now was to use the deployClusterTask id directly: 14e92359-f063-4955-b3c0-96a5523b71f4.

Thanks for raising. I hope to release this fix by the end of the week.


'Add' button and scroll in the 'Periodic Table' window don't match the mockup

Steps to Reproduce

Launch Ketcher.
Click the 'Periodic Table' button.
Compare the size, shape and location of the 'Add button' on both 'Table' and 'Extended' tabs with the mockup.
Compare scroll on the 'Extended' tab with the mockup.

Expected behavior
Both 'Table' and 'Extended' tabs match the mockup.

Actual behavior
'Add' button size and shape don't match the mockup. The location of the 'Add' button differs between tabs.
Screenshots

Desktop:
OS: Windows 10
Browser - Chrome
Version 100.0.4896.75
Ketcher version:
v2.4.2-157-gу13ae6cb

The 'Add' button position changes when switching between two tabs

Tested in v2.4.2-184-g23626b99

It's necessary to click on a specific area of the 'Add' button on the 'Table' tab to select it.

Verified in Release 2.5


FancyZones zones are established too early when Run at Startup is enabled, causing zones to overlap the taskbar

Microsoft PowerToys version
0.64.1
Installation method
WinGet
Running as admin
Yes
Area(s) with issue?
FancyZones
Steps to reproduce

Enable Run at Startup
Attempt to use FancyZones after reboot

✔ Expected Behavior
Each zone should stop at the taskbar when the taskbar is always shown
❌ Actual Behavior
PowerToys/FancyZones starts before the taskbar is rendered on the desktop. When the zones for FancyZones are established, they go down all the way to the bottom of the screen instead of stopping at the taskbar, so when a window is snapped to the zone, part of it is hidden by the taskbar. Restarting PowerToys after the taskbar is rendered reestablishes the zones correctly so that they end at the beginning of the taskbar.
Other Software
Windows 11 Dev channel

Also experienced on Windows 10 21H2 120.2212.4180.0.
PowerToysReport_2022-12-02-08-34-10.zip

/dup of https://github.com/microsoft/PowerToys/issues/10903


Dropdown list fails to display contents when expanded

Dropdown list fails to display contents when expanded
Windows 10
Obsidian 1.6.3

Hi, I don't know how to change the CSS styling of this part of the theme. Please, if you know, let me know how.

I just tried not being able to change the background color of the dropdown list, I guess I didn't find the correct style property.

Can you try setting the default background color for all dropdown lists to see what happens?

I've finally corrected it! The colours may not be the best, but now we can read things properly.


fix: fix page order in navigationList

Description
Fix page order in navigationList
minor

fix page order in navigationList

Impaction
Screenshots

Scenarios
Before
After

Rearrange

Nice job! This is a good workaround.
Do you think we can leverage cms to order the navigation list? That would be much better if we can sort them by admins' preferred order.

Now we can rearrange the order of pages by modifying the Page order in cms.

Nice effort!


Update index.md to reflect Slack channel renaming

As per the recent renaming of enablement-leadership to enablement-staff Slack channel, I think the Handbook page should reflect the following changes as well.

Thank you for fixing this!


Return filekey

Is there any reason why the filekey isn't returned in the response body?

Seems fine to return it, sure 👍

Released v4.0.3 with this change... thanks


ci: test against python 3.13 and jupyterhub 5

I'm seeing test failures in tljh for jupyterhub 5.2.0, but not for 5.1.0, for when hubtraf User object's method ensure_server_simulate is called.
From this test run on GitHub Actions
    async def test_user_code_execute():
        """
        User logs in, starts a server & executes code
        """
        username = secrets.token_hex(8)

        assert (
            0
            == await (
                await asyncio.create_subprocess_exec(
                    *TLJH_CONFIG_PATH, "set", "auth.type", "dummy"
                )
            ).wait()
        )
        assert (
            0
            == await (
                await asyncio.create_subprocess_exec(*TLJH_CONFIG_PATH, "reload")
            ).wait()
        )

        async with User(username, HUB_URL, partial(login_dummy, password="")) as u:
            assert await u.login()
>           assert await u.ensure_server_simulate(timeout=60, spawn_refresh_time=5)
E           assert False

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 37.80%. Comparing base (df19256) to head (7e14f8d).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #49      +/-   ##
==========================================
- Coverage   38.08%   37.80%   -0.28%
==========================================
  Files           6        6
  Lines         365      365
==========================================
- Hits          139      138       -1
- Misses        226      227       +1

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

ty @consideRatio


Implement system unit arithmetics

Following operations should be implemented:
>>> 23 * AU.Length
Quantity(2.300e+01 #ALEN)
>>> Quantity(23, 's-1') * AU.Length
Quantity(2.300e+01 #ALEN*s-1)

System of units are now classes that return Quantity objects.
So now, the above calculations can be done as with any other Quantity objects.
`>>> 23 * AU.Length()
Quantity(2.300e+01 #ALEN)

Quantity(23, 's-1') * AU.Length()
Quantity(2.300e+01 #ALEN*s-1)`

finished


bugfix: fix some typo in doc and comments

Signed-off-by: Frank Yang<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
fix some typo in comments and docs
Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how you did it
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews
@HusterWan PTAL

LGTM

Codecov Report

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

@@           Coverage Diff           @@
##           master     #929   +/-   ##
=======================================
  Coverage   13.43%   13.43%
=======================================
  Files         121      121
  Lines        7800     7800
=======================================
  Hits         1048     1048
  Misses       6662     6662
  Partials       90       90

Continue to review full report at Codecov.

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


doc: getting_started: Add missing dependencies

The lpcxpresso devices need srec_cat from the srecord package to
generate their image files, and the nanopb module obviously requires
the hostside protobuf tooling.
Both of these are default platforms in an unadorned twister run, and
so produce failures on new systems that had only followed the
instructions in the guide.
Signed-off-by: Andy Ross<EMAIL_ADDRESS>

Kill this, no interest in merging as-is, and I'm not qualified to work up a fancier external dependency management layer.


Rework Firebase presence

It must be built with https://github.com/firebase/firebase-queue to be robust and safe. User info/connected state with onDisconnect must add items to the queue, and the queue must create a special read-only presence view.

Ok, it seems this works:
path /users-presence/{uid} is UserPresence[] {
  create() { isViewer(uid) }
  update() { true }
  delete() { true }
}

update and delete must allow public access, but it's not a big deal.


CAD-901: Peers list

Issue

Send the list of connected peers. Technically there's no need to send the number of connected peers in a separate metric, but it's temporarily kept for TUI.

This PR does not result in breaking changes to upstream dependencies.

Checklist

[ ] This PR contains all the work required to resolve the linked issue.

[ ] The work contained has sufficient documentation to describe what it does and how to do it.

[ ] The work has sufficient tests and/or testing.

[ ] I have committed clear and descriptive commits. Be considerate as somebody else will have to read these.

[ ] I have added the appropriate labels to this PR.

bors r+


AtCoder Tools Documentation Webapp

https://kyuridenamida.github.io/atcoder-tools/

Codecov Report

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

@@           Coverage Diff           @@
##           master      #95   +/-   ##
=======================================
  Coverage   91.69%   91.69%
=======================================
  Files          46       46
  Lines        1950     1950
=======================================
  Hits         1788     1788
  Misses        162      162

Continue to review full report at Codecov.

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


[OTHER] Change the 'Issues Result' title to 'All Unassigned Issues 👇'

Title
Change the Issues Result title to All Unassigned Issues 👇
Description
When you search issues of a particular language then on the middle part the title of Issues Result should be changed to All Unassigned Issues 👇
Screenshots (optional)

For more accuracy kindly refer to the above screenshot

I would like work on this issue :)

Hi @anand346 I have changed the title. Can you please review it?


Go get version is still old with v2.1.1+incompatible

Reproduce
go list -m -mod=mod -versions github.com/hyperledger/fabric
github.com/hyperledger/fabric v0.6.0-preview v0.6.1-preview v1.0.0-alpha v1.0.0-alpha2 v1.0.0-beta v1.0.0-preview v1.0.0-rc1 v1.0.0 v1.0.1 v1.0.2 v1.0.3 v1.0.4 v1.0.5 v1.0.6 v1.1.0-alpha v1.1.0-preview v1.1.0-rc1 v1.1.0 v1.1.1 v1.2.0-rc1 v1.2.0 v1.2.1 v1.3.0-rc1 v1.3.0 v1.4.0-rc1 v1.4.0-rc2 v1.4.0 v1.4.1-rc1 v1.4.1 v1.4.2 v1.4.3 v1.4.4 v1.4.5 v1.4.6 v1.4.7 v1.4.8 v1.4.9 v1.4.10 v1.4.11 v1.4.12 v2.0.0-alpha+incompatible v2.0.0-beta+incompatible v2.0.0+incompatible v2.0.1+incompatible v2.1.0+incompatible v2.1.1+incompatible
Solution
Update the fabric releases to the public Go module repository.

@yeasy What exactly is your proposal here?
We had previously decided not to update Fabric module to /v2, since Fabric is not a dependency that other Go projects should pull in with "go get", and we don't want to give that impression.
v2.1.1+incompatible is displayed because it was the last release prior to converting the project to go modules.

First, as an open source project, it's not appropriate to "decide" the users' usage method.
I get the point that fabric is not a pure dependency, but it's possible that the users want to take whole or part of its code.
On the other way, supporting go get does not mean it's an dependency, as most go projects do today. It is just a native way to obtain some golang based project.
Hence it will be more friendly to keep enabling the go get way, instead of freezing at 2.1.1.

The maintainers can certainly re-evaluate. It will require a specific proposal however. What changes would you like to contribute, what actions need to be taken, and what are the implications?

// What changes would you like to contribute
If need, I can help enable the new version. It's not difficult, but I believe that requires some privilege.
// what actions need to be taken,
Update the newer fabric releases to the public Go module repository.
// and what are the implications?
Several potential implications:

users can get confused as thinking the hlf only has 2.1.1 release from the Go repo history;
users cannot get the newer version using go get, etc.

Let me further explain the rationale of why the maintainers decided not to version the fabric go module:

Fabric codebase pre-dates go modules and therefore doesn't follow typical module project structure and assumptions.
Fabric repository is for the Fabric application runtime binaries and does not maintain and expose a public API. The fabric public API is in the various fabric-protos repositories that fabric repository pulls in and consumers can pull in.
There are functions exported for internal use within the repository that consumers may misinterpret as public APIs if it were published as a versioned module.
Since Fabric repository is for application runtime binaries, it uses semantic versioning based on runtime behavior rather than on internal API compatibility. However, module versioning requires semantic versioning based on API compatibility.
Go reference documentation around module versioning is all about consumers importing code. However, Fabric discourages consumers to import core fabric repository code, if they do it will change and break them in unexpected ways.

The maintainers concluded the above considerations outweighed the ability for users to go get fabric code.
So far, the proposal here does not bring any new information for maintainers to consider. Again, the maintainers could re-evaluate, but it would require a more detailed proposal that addresses the concerns and implications above. Considering the fundamental differences between an application binary repository and an importable repository, I would expect any such proposal would require significant code refactoring to get it aligned with expected Go module practices, and as such would likely require an RFC rather than a github issue, which you are welcome to open.

Hello, in regards to this, I have cloned the fabric branch 2.5.0 to use it as a local package. However, there seems to be a problem related to one of the package which would require using fabric go package to solve. More specifically, if I have any custom go application that imports protoutil and I try to use the Identity package I get the following:
package command-line-arguments
	imports github.com/alfredom/fabric/protoutil
	vendor/github.com/alfredom/fabric/protoutil/commonutils.go:17:2: use of internal package github.com/hyperledger/fabric/internal/pkg/identity not allowed

This is because identity is under the folder internal, and therefore it acts like a private folder. I then tried to import fabric v.2.1.1+ incompatible using go get, and the problem seems to go away. HOWEVER, at compilation time then I get many different kind of errors all relating to protobuffer, which I suspect is somewhat connected to protoutil.
Hence: either 2.1.1 needs to be upgraded to 2.5 or the identity package needs to be taken out of the internal folder and put somewhere else so that it doesn't cause this error.
More about this at: https://github.com/hyperledger/fabric/issues/4200
Looking forward to you answering

I am trying to add a custom validation plugin, really, and in order to do this I have no choice but to import hyperledger/fabric. If I were to use the google dependency I get all sort of errors, ie the one mentioned above. So, I believe my only option here is forking the repository and making all local changes I need and then importing it as a local copy altogether. Thanks for your comment though.

Certainly not something I have tried but thank you for clarifying what you're trying to do. It is definitely helpful in case others can offer suggestions.
I notice this post on the Fabric mailing list that might be helpful. I suspect that you are correct and either forking the Fabric codebase or just copying the bits of code you need to implement your plugin will be the best approach. Maybe somebody else has better information.