Update docs with additional information on using checkout

If using this action in a workflow triggered by push on something other than refs/tags, e.g.
on:
  push:
    branches:
      - 'main'

it is necessary to specify a fetch-depth of 0 in order for tag information to be included in the repo. Otherwise this action's git command will fail when attempting to describe the repo's tags.
      - uses: actions/checkout@v2
        with:
          fetch-depth: 0 # indicates all history for all branches and tags. needed for changelog.

@hartman-michael-PFG thanks for your report.
There are actually 2 solutions to this.
Either the fetch-depth is adjusted to a value to have the relevant tags in range (0 would mean all history which in a ton of cases would significantly slow down the checkout)
this can be made obsolete too if the toTag is provided.
I'll add the info to the README. thanks!

@hartman-michael-PFG thanks for your report.
There are actually 2 solutions to this.
Either the fetch-depth is adjusted to a value to have the relevant tags in range (0 would mean all history which in a ton of cases would significantly slow down the checkout)
this can be made obsolete too if the toTag is provided.
I'll add the info to the README. thanks!


Rewritten ptototype.query method

This method now uses the same request doZabbixAPIRequest without code
dublication. Please check on your installation cause I have only one
metric per graph
I thinl idea is clear to remove code dublication with auth, and do all requests thru doZabbixAPIRequest

Alex, is it possible in grafana by default replace word alias with the metric name from zabbix api, and add check box "autoupdate metric name fro api" if it is set to true, than every time when graph is loaded to take metric name from api, not from alias field? It more convenient for zabbix users.

It's good idea. I'll try to realize this feature later.

Have you fully tested this patch ?
Is it work for you from every beginning? Cause I see in console there errors sometimes.
There is cosole.log().

Yes, I check for errors and for my installation all right. if you see errors again, please open issue with detailed error description.


Anything like stylelint-config-standard for this?

https://github.com/bjankord/stylelint-config-sass-guidelines is the only config I found, and it doesn't care about a lot of inconsistencies.

Nvm it's fine.


Adopt "php.validate.executablePath" handling to new TS behaviour

VSCode Version: 1.9.
OS Version: all

"php.validate.executablePath" should behave in the following way:

the setting can be set in the user and workspace settings
if present in the workspace setting warn the user once that the setting starts an executable and that the user trust the executable.
if the workspace setting changes (points to a different executable) ask again.

@egamma @chrmarti please verify.

The question should mention that the path is from the workspace setting and that it will be used for all PHP files, not just the current one: "Do you allow /Users/chrmarti/Development/repos/canary2.sh to be executed to lint this file?"
This message is still mentioning Path status bar item: "Cannot validate since /foo/bar is not a valid php executable. Click on the Path status bar item to configure the executable."
When there are both a user and a workspace settings' executable and I answer 'No' to the question regarding the workspace's executable, I would expect the user settings' executable to be used. Instead none is used.
Note that the UI for the tsdk is using a drop-down, not a message.
Reopening for the wording.
/cc @kieferrm @mjbvz

Also: After rejecting the workspace setting, I'm asked again after restart/reload. That's unexpected. (I'm not asked again after accepting.)

Made the following changes:

the initial message is now Do you allow C:\apps\php\php.exe to be executed to lint PHP files?. I changed this already on Tuesday, but didn't make it into Tuesday's build
removed the mentioning of the Path status bar item. It now says: .... Use the setting 'php.validate.executablePath' to configure the PHP executable.

@egamma and I discussed quite some time about what to do if the user says No. We decided to ask him on next startup since the alternate actions aren't easy to explain either. Options were:

remember in the local store that the user doesn't trust this. How would the use then trust the path if he click no by accident. We would either need UI on the local store again or we need to teach the user to edit the second two times.
remove the setting from the workspace settings.
disabled PHP validation by adding a setting to the workspace settings.

Both last once would requires another message dialog since we shouldn't change workspace settings without confirmation.
Given the fact that we want to slow down Erich and I decided to not do any code changes anymore. I did the wording changes.

I'm fine with that, two thoughts:

The question should mention that this executable is set in the workspace settings.
There is no way to change a Yes to a No either. Have you considered using the same UI as for the tsdk? (Or maybe that's the plan now?)

The tsdk UI doesn't work since the php setting points to a file which is usually not local to your workspace. And we don't have a file picker UI in the extension host :-). That is why editing the setting is still something users have to do in the settings file.
The way from yes to no is easy. Simply remove the setting from the .vscode/settings.json file. I am very reluctant to introduce another setting story. IMO all settings should be maintained in the settings store and the used settings should be clear to the user when he opens the settings editor. If I store additional information in the local store the user would open the .vscode/settings.json file sees a correct entry but no indication that he disabled the entry a while ago. Will be confusing IMO.
I will tweak the question to point to the workspace setting.

The message now reads:
'Do you allow {0} (defined as a workspace setting) to be executed to lint PHP files?'

VSCode Version: Code - Insiders 1.10.0-insider (f02f9930255b5804166bd26c804de474ebb96799, 2017-02-24T07:04:53.237Z)
OS Version: Darwin x64 15.6.0
Extensions: None

The message shows up twice:

Changing a Yes to a No when you want to avoid local changes against the checked out repository is not that easy. It is not enough to remove the setting and then add it back - that just keeps the Yes (also with a reload in between). You have to set it to a different path (a non-existant works) and accept that with a Yes (a No won't do) before reverting back to the original.
I agree that the settings should be apparent from the settings.json, that does not seem to hold in this case yet.
Also:

Could add a 'Open Workspace Settings' button to the message so the user can inspect what else is in there.
The webpage linked to with 'Learn More' does not list / explain the special cases where the user is asked for confirmation. Maybe drop that button?

Reopening so you can decide if any this should be changed.

Moving to March for consideration.

I removed the Learn More. TS doesn't provide this anymore either and the setting is something the user edits anyways.

I added an action to the command palette that lets you 'untrust' the php validation path.

The action is only available if the validation path has been trusted before.

Best person to re-verify would be @chrmarti

Would it make sense to align the command's name with the message:

E.g.: PHP: Disallow PHP validation executable (defined as a workspace setting)
Marking verified.

Yes makes sense.

Done.


Azure CLI output is corrupted!

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug

It is not a valid JSON string. Finished appears in final output.
~$ az vm run-command invoke -g fy -n vm1 --command-id RunShellScript --scripts 'echo $1 $2' --parameters hello world
{- Finished ..
  "value": [
    {
      "code": "ProvisioningState/succeeded",
      "displayStatus": "Provisioning succeeded",
      "level": "Info",
      "message": "Enable succeeded: \n[stdout]\nhello world\n\n[stderr]\n",
      "time": null
    }
  ]
}

To Reproduce

Expected behavior

Environment summary

WSL Ubuntu 20.04 LTS
Additional context

Compute

@Juliehzl was this issue related to Storage or Compute?

@Juliehzl was this issue related to Storage or Compute?

It is related to progress bar

@qwordy I haven't checked in progress bar related code, so I am not sure how you get such output.
In addition, in my progress bar test, I cannot see your issue, either.
Could you provide more information to help figure out why you get the issue?

I ran into this issue today as well with this command:
dotnetcore-sqldb-tutorial$ az sql server create --name dotnetcore-sqldb-tutorial-sql1 --resource-group dotnetcore-sqldb-tutorial-rg --location "westus2" --admin-user jonbgallant --admin-password asdfasdf
{/ Finished ..
  "administratorLogin": "jonbgallant",
  "administratorLoginPassword": null,
  "fullyQualifiedDomainName": "dotnetcore-sqldb-tutorial-sql1.database.windows.net",
  "id": "/subscriptions//resourceGroups/dotnetcore-sqldb-tutorial-rg/providers/Microsoft.Sql/servers/dotnetcore-sqldb-tutorial-sql1",
  "identity": null,
  "kind": "v12.0",
  "location": "westus2",
  "minimalTlsVersion": null,
  "name": "dotnetcore-sqldb-tutorial-sql1",
  "privateEndpointConnections": [],
  "publicNetworkAccess": "Enabled",
  "resourceGroup": "dotnetcore-sqldb-tutorial-rg",
  "state": "Ready",
  "tags": null,
  "type": "Microsoft.Sql/servers",
  "version": "12.0"
}

dotnetcore-sqldb-tutorial$ az version
{
  "azure-cli": "2.22.1",
  "azure-cli-core": "2.22.1",
  "azure-cli-telemetry": "1.0.6",
  "extensions": {
    "azure-devops": "0.18.0",
    "fzf": "1.0.2",
    "imds": "0.1.0",
    "noelbundick": "0.0.17"
  }
}

WSL2/Ubuntu 20
ddcc1

Thanks for feedback. I will investigate the issue soon and plan in S187.


how to run in firefox and safari with the command line ?

how to run in firefox and safari with the command line ?

anyone got a fix for this? I'd like to run my app on Firefox but am unable to add it as a virtual device in VSCode

Originally posted by @hiashutoshsingh in https://github.com/flutter/flutter/issues/40232#issuecomment-690998181

Please ask support questions on StackOverflow. Closing this as not a bug or feature request, but a how to question.


Urgent: Update Library License For Enterprise usage

Hey, kudos to @esafirm and all contributors to this repository.
I noticed the link at the bottom the ReadMe You can find the original license here does not work.
It takes you to a "404 not found" page.
Expected: Expecting Apache 2.0 License or similar
There doesn't seem to be a clear standardized license for this library. Currently considering removing this library from my dependencies since it doesn't have the legally approved licenses required by the enterprise. I was expecting there to be an MIT or Apache 2.0 License, but it seems like there isn't one and it's more like a disclaimer template license.
Suggestions
Can the license be updated to one of the following

Apache 2.0 License or
MIT license or any other similar license.

This would help enterprises testing out the functionality provided by this library do so without fear of any legal repercussions.
Please provide updates to this request in a timely manner. @esafirm

I think I will update the license to MIT due to there's little to no correlation to the original project. Also, the original project take some code from here and not giving any credit whatsoever 😬
Example:
CameraModule in AIP -> CameraModule


thriftrw should handle bad thrift req format gracefully

cc: @kriskowal @Raynos @jcorbin
Refer to https://github.com/uber/tchannel/pull/1188

test sending a request with a malformed thrift IDL where we send an empty body. Assert BadRequest
Actual response:
/Users/juncaoli/workspace/tchannel/src2/node/hyperbahn/handler.js:390
var serviceName = body.query.serviceName;
^
TypeError: Cannot read property 'serviceName' of null
at discover (/Users/juncaoli/workspace/tchannel/src2/node/hyperbahn/handler.js:390:33)
at HyperbahnHandler.handleThriftRequest (/Users/juncaoli/workspace/tchannel/src2/node/as/thrift.js:165:9)
at RequestCallbackHandler.handleRequest (/Users/juncaoli/workspace/tchannel/src2/node/request-handler.js:62:23)
at HyperbahnHandler.handleRequest (/Users/juncaoli/workspace/tchannel/src2/node/endpoint-handler.js:71:17)
at ServiceDispatchHandler.handleRequest (/Users/juncaoli/workspace/tchannel/src2/node/hyperbahn/service_proxy.js:121:22)
at TChannelConnection.runHandler (/Users/juncaoli/workspace/tchannel/src2/node/connection_base.js:134:26)
at runHandler (/Users/juncaoli/workspace/tchannel/src2/node/connection_base.js:116:14)
at process._tickCallback (node.js:419:13)

test sending a request with a malformed thrift IDL where we send a body with a query without the serviceName field. Assert BadRequest
Actually response is the same as above.

test sending a request with a malformed thrift IDL which has zero exceptions defined; Send a request with empty string serviceName. Assert that the client doesn't blow up and gets back a not ok response.
Actually response:
assert.js:92
throw new assert.AssertionError({
^
AssertionError: expected not-ok response to have typeName
at handleThriftResponse (/Users/juncaoli/workspace/tchannel/src2/node/as/thrift.js:9:8146)
at onResponse (/Users/juncaoli/workspace/tchannel/src2/node/hyperbahn/handler.js:9:18233)
at handleResponse (/Users/juncaoli/workspace/tchannel/src2/node/as/thrift.js:9:11266)
at DefinedEvent.onResponse [as listener] (/Users/juncaoli/workspace/tchannel/src2/node/out_request.js:9:22423)
at DefinedEvent.emit (/Users/juncaoli/workspace/tchannel/src2/node/lib/event_emitter.js:9:3685)
at V2OutRequest.emitResponse (/Users/juncaoli/workspace/tchannel/src2/node/out_request.js:9:13637)
at TChannelConnection.onCallResponse (/Users/juncaoli/workspace/tchannel/src2/node/connection.js:9:12385)
at DefinedEvent.onCallResponse [as listener] (/Users/juncaoli/workspace/tchannel/src2/node/connection.js:9:7490)
at DefinedEvent.emit (/Users/juncaoli/workspace/tchannel/src2/node/lib/event_emitter.js:9:3685)
✓ get no hostelV2Handler.handleCallResponse (/Users/juncaoli/workspace/tchannel/src2/node/v2/handler.js:9:20587)

FYI. The tests revealing these issues are present but commented out in the referenced PR.

Fixed in #56


eth_estimateGas should revert with small gasLimit

{
    "id": 0,
    "jsonrpc": "2.0",
    "method": "eth_estimateGas",
    "params": [
        {
            "from": "0x6f0ed2098E9528c203173578cAE8C8C6f8ba7833",
            "to": "0x0000000000000000000100000000000000000000",
            "data": "0xa9059cbb0000000000000000000000001000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000174876e800",
            "value": "0x0",
            "gasLimit": "0x0",
            "type": "0x1"
        },
        "latest"
    ]
}

If the specified gasLimit is too small, it should be revert with outofgas

https://github.com/AcalaNetwork/Acala/blob/c93798018a865d1fd5da4eb63edf5de9dec31d94/ts-tests/tests/test-transaction-cost.ts#L16


fix(table): enable horizontal scroll in table

Closes IBM/carbon-components-angular#
Enable horizontal scroll in table to match Carbon React implementation. Refer Carbon React implementation: https://github.com/carbon-design-system/carbon/blob/main/packages/react/src/components/DataTable/Table.js#L34

Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

Holding on merging - as we discuss with @carbon/styles team to add display block to .bx--data-table-content class. We can then use @hostbind the class - This would prevent unnecessary elements in template & make it easier to manage.
For the time being, you can add .bx--data-table-content class to ibm-table tag with display set to block as follows:
<ibm-table class="bx--data-table-content" style="display: block">
     ....
</ibm-table>

Holding on merging - as we discuss with @carbon/styles team to add display block to .bx--data-table-content class. We can then use @hostbind the class - This would prevent unnecessary elements in template & make it easier to manage.
For the time being, you can add .bx--data-table-content class to ibm-table tag with display set to block as follows:
<ibm-table class="bx--data-table-content" style="display: block">
     ....
</ibm-table>

Thanks for the update, @Akshat55. Actually my initial attempt was to use @hostbind the class. I did not end up using that approach since the table component also @hostbind bx--data-table_inner-container for sticky header. So we would end up having both .bx--data-table-content and bx--data-table_inner-container on the host. I don't know Carbon team intends to support this or not. Adding display: block is the easy part.

New PR created: https://github.com/IBM/carbon-components-angular/pull/2235


Enhancement: Add client setting for auto-scroll on client start

Hi!
I always end up checking the Lock scrollbar to end box so I can see the last messages on a long running server (like performing an on demand backup).  Perhaps add a setting to the client config screen that sets this value on open to checked or unchecked?
Thanks!

Absolutely can! This has been implemented and I will push a new release shortly. Thanks man!

Works great!


Unit testing

This issue will probably need to be split out into smaller pieces.
Right now: 0 unit tests.
Where I want to be: near-full test coverage.
This doesn't cover overall tests for identifying licenses; that's in #4.

Stuck a test stub here: https://github.com/amzn/askalono/blob/54299c7db3ca1dc443ff890015c7e87891a09c24/src/ngram.rs#L110
Added to familiarize myself, but this is still free for hacking on.

I'm comfortable with the state of tests in askalono right now. There's always room for improvement, but I think this is resolvable.


Snippet without children matches code with children

NB please do not edit the editor from this link. Copy a forked version to experiment.
https://app.grit.io/studio?key=hWu-nA-6hu6_esJtvoXag

This is the default behavior for a snippet. I recently added a way to specify that a node with no children in a snippet must only match other nodes with no children. we could invert this, but it could break backwards compatibility for a patterns (would have to try and see).

I think we should try inverting it and see if the stdlib breaks.


[Alpha] Wrapping ListItem in  or  (Redux Router) is resulting in red colored wave

Wrapping ListItem in <a> or <Link> (Redux Router) is resulting in awkward red colored wave which otherwise would be grey wave.
Screenshot:

Also, any way to find the cause (eg: theme setting) of such occurrence?

I have noticed the same, can also be blue ><.

Yup, this particular case the red wave ends with flash of blue color.

This is a recent regression. I'm looking into it.

I have found the source of the issue when I was talking about a regression, that was on my app side, not Material-UI, basically, the issue comes from the default colours of a <a /> the browser is using.


Tag a GitHub release

It would be great if you'd be willing to create releases on GitHub that coincide with the versioning you're already using. I'd be interesting in making a Homebrew formula for wsedit but having a tagged release makes that a lot easier.
Nice work on this, by the way!

Thanks, I'll check it out. Still kinda new to all of this.
What do you mean with "homebrew formula"?

@SirBoonami Creating a Homebrew package for OSX.

While the thought that anyone would want to package my software certainly is humbling, I don't think wsedit is quite there yet.

Even as the editor is close to what I'd call "initial feature-completeness", I'm still pushing potentially big changes at least once per week.
At this point, stability is still a happy coincidence and the error handling routines are somewhat lacking (I've had a plaintext editor core dump reach 500MB o.0). I'm in the process of writing an extensive test suite to help with this, but it won't be finished for at least another week.
I haven't even thought about OSX support yet, and since I don't own a Mac, I have no way of testing wsedit there. Since you are appearently willing to package it, I assume it should run somewhat reliably, but I'm almost 100% certain some features (e.g. OS clipboard compatibility) don't work as intended. I'd like to go over my code once again with OSX in mind before declaring it "probably compatible".
There are a couple of small features missing (search/highlight functionality, "scroll bar"-like vertical position indicator) which I'd consider pretty important for production use.

So I'd ask you to give me at least 2-3 more weeks to clean up my mess before releasing it to the maybe less adventurous general public =)

Sure, of course you've free to do all of this at your discretion on your own schedule, I just figured I'd get the conversation started about releases and packaging. Let me know once you have a version that you feel comfortable packaging and I'll get the Homebrew installer set up. 😄

Alright Gentlemen, here's the plan:

I want to implement three more features, resulting in v1.0 RC, due next Friday.
In the following week, I will improve the built-in documentation and test the RC.
On Friday the 15., v1.0 will go live.

In the meantime, I'd ask two things of you:

Take a look at the tagged v0.3.1 release. Is that enough for the package, or do you need binaries? (which I'm not sure I can provide for OSX)
Could someone on OSX please test #2 for me?

Cheers

Something that would be really nice if I may make a request would be the option to specify an installation directory, perhaps defaulting to the current .local if none is specified. I don't know about other platforms, but I think that would make Homebrew packaging on OS X easier. (Homebrew doesn't like things to be installed outside of its prefix in /usr/local/Cellar.)

Looks like that can be done directly without any extra work from you. stack install is a synonym for stack build --copy-bins, so I can just make the package use stack build then deal with the binaries myself.
tl;dr disregard previous comment

wsedit is now installable via Homebrew on OS X! 🎉
brew tap ararslan/pints
brew install wsedit

(wait about 15 minutes because holy crap Haskell Stack takes forever)
wsedit -h

It installs the prerelease now and I'll update it to install 1.0 once that's ready. 😄

Very nice, thank you =)

FYI this is where the installer lives, in case you're curious: https://github.com/ararslan/homebrew-pints


FD can't save a file if it has the "hidden" attribute set

FlashDevelop can't save an edited file if it has the "hidden" attribute set. (Notepad can save the same file). Not a permission problem: attrib -h file and FD can save it again.
Access to the path 'C:\project\apps\FXCalc\fonts\.FontLibrary-config.xml' is denied.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   ...

I know it's easy to reproduce this, but providing the full stack trace would be better :)
Access to the path '{0}' is denied.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
   at System.IO.StreamWriter.CreateFile(String path, Boolean append)
   at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize)
   at System.IO.StreamWriter..ctor(String path, Boolean append)
   at PluginCore.Helpers.FileHelper.WriteFile(String file, String text, Encoding encoding, Boolean saveBOM)
   at FlashDevelop.Docking.TabbedDocument.Save(String file)
   at FlashDevelop.Docking.TabbedDocument.Save()
   at FlashDevelop.MainForm.Save(Object sender, EventArgs e)

Sorry I didn't provide the stack trace

Verified, it works now. Thanks!

I'm suspecting that this fix causes #1270 !
To reproduce, open any file, delete some of it's contents (reduce it's size), and save. The new contents are saved on top of the old contents, but the file size is not reduced. Whatever was at the end of the file, remains there. It doesn't show up in FD until file is closed&reopened.


Duplicate key error thrown when extending Faker class

Describe the bug
If a class that extends the Faker class has two methods returing the same type, calling one method of the Faker class throws the following error:
Exception in thread "main" java.lang.IllegalStateException: Duplicate key String (attempted merging values public java.lang.Long org.example.BaseFaker.anotherMethodReturningString() and public java.lang.Long org.example.BaseFaker.oneMethodReturningString())
	at java.base/java.util.stream.Collectors.duplicateKeyException(Collectors.java:135)
	at java.base/java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1(Collectors.java:182)
	at java.base/java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
	at java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:179)
	at java.base/java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:1024)
	at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)
	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)
	at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:921)
	at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
	at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:682)
	at net.datafaker.providers.base.ObjectMethods.scanMethodsByReturnType(ObjectMethods.java:26)
	at java.base/java.util.Map.computeIfAbsent(Map.java:1066)
	at net.datafaker.providers.base.ObjectMethods.getMethodByReturnType(ObjectMethods.java:44)
	at net.datafaker.providers.base.ObjectMethods.executeMethodByReturnType(ObjectMethods.java:50)
	at net.datafaker.providers.base.ProviderRegistration.getProvider(ProviderRegistration.java:20)

To Reproduce
BaseFaker class:
import net.datafaker.Faker;

public class BaseFaker extends Faker {

    public String oneMethodReturningString() {

        return this.name().fullName();
    }

    public String anotherMethodReturningString() {

        return this.name().fullName();
    }
}

The error is thrown when calling oneMethodReturningString()
public class Main {

    public static void main(String[] args) {

        BaseFaker baseFaker = new BaseFaker();

        baseFaker.oneMethodReturningString();
    }
}

Expected behavior
The error should not be thrown
Versions:

OS: Windows
JDK: Java 21
Faker Version [e.g. 2.4.0]

Additional context
The error starts to happen after version 2.3.0. With version 2.2.2 the code provided works well

Hi @jsolferreira , I think this may have been introduced as part of https://github.com/datafaker-net/datafaker/pull/1271.
@asolntsev , is this something you could have a look at?

@jsolferreira could you please give the snapshot release a try? If it works, I'll publish a new release.

@bodiam @asolntsev  Just tested the same code example and it worked with version 2.4.1-SNAPSHOT
Thanks for the quick fix!


APK Generation fails

Description
The app builds well on the simulator when I try to generate the signed APK, I get:
 Transform firebase-analytics-impl.aar (com.google.firebase:firebase-analytics-impl:16.0.0) with AarTransform
> Transform full.jar (project :emoji) with DexingTransform

> Task :app:mergeExtDexPlayRelease FAILED
AGPBI: {"kind":"error","text":"Class descriptor \u0027Landroid/support/customtabs/ICustomTabsCallback/;\u0027 cannot be represented in dex format.","sources":[{}],"tool":"D8"}

FAILURE: Build failed with an exception.

What went wrong:
Could not resolve all files for configuration ':app:playReleaseRuntimeClasspath'.

Failed to transform file 'jetified-classes.jar' to match attributes {artifactType=android-dex, dexing-is-debuggable=false, dexing-min-sdk=22} using transform DexingTransform
Error while dexing.

Devices and Versions

Your Rocket.Chat.Android version: (e.g. 2.1.0)
Your Rocket.Chat Server version: (e.g. 0.63.1-develop)

Mobile device model and OS version: (e.g. "Nexus 7 - Android 6.0.1")
Steps to reproduce

Logs

Any luck with this issue?

Add the following in your app level gradle file inside android tag and try sync, clean build apk .
compileOptions {
sourceCompatibility JavaVersion.VERSION_1_8
targetCompatibility JavaVersion.VERSION_1_8
}

@real19 if you try the above and still no luck, try switching to oracle jdk instead of openjdk and tell us if it all worked fine

Thanks @isanalWipro and @leonardoaramaki . Adding the following worked:
compileOptions {
sourceCompatibility JavaVersion.VERSION_1_8
targetCompatibility JavaVersion.VERSION_1_8
}


OctoEditable xxx cleared on startup

Description
When I start up NeoVim with an Octo command
nvim -c ":Octo issue edit 98"

the following message is logged and I'm forced to hit enter to dismiss it
OctoEditable   xxx cleared

I'm using lazy.nvim to load Octo and Catppuccin:
  {
    "pwntester/octo.nvim",
    cmd = "Octo",
    -- ...
  },
  {
    "catppuccin/nvim",
    priority = 1000,
  }

I've confirmed that this only happens because of Catppuchin.
Can the OctoEditable xxx cleared message be removed? I look through the source code and can't figure out what is causing the message to be displayed in the first place. It seems it may be an issue with Octo loading before Catppuchin then the highlight group is cleared, causing the message.
Workaround
Putting silent in front of the command will ignore the message and open the Octo buffer directly.
nvim -c ":silent Octo issue edit 98"

Neovim version
NVIM v0.9.4
Build type: release
LuaJIT 2.1.1700008891

Terminal and multiplexer
wezterm 20231017-091526-fec90ae0
Catppuccin version / branch / rev
"catppuccin": { "branch": "main", "commit": "4fbab1f01488718c3d54034a473d0346346b90e3" },
Steps to reproduce

Install Octo and Catppuchin plugins
Open Neovim with an Octo command

nvim -c ":Octo issue edit 98"

You will see the OctoEditable   xxx cleared that requires user interaction to dismiss.

Expected behavior
I can open Neovim with an Octo command and be taken directly to the Octo buffer with no messages.
Actual behavior
The message is shown and has to be dismissed
Repro
n/a

Cannot reproduce with nvim -u /tmp/repro.lua -c "Octo issue edit 1"
https://github.com/catppuccin/nvim/assets/56817415/3e79f323-2cbe-4647-9029-8f65b45b7116
/tmp/repro.lua content:
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
	vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
	vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
	{ "catppuccin/nvim", name = "catppuccin", priority = 1000 },
	{
		"pwntester/octo.nvim",
		dependencies = {
			"nvim-lua/plenary.nvim",
			"nvim-telescope/telescope.nvim",
			"nvim-tree/nvim-web-devicons",
		},
		config = true,
		cmd = "Octo",
	},
}
require("lazy").setup(plugins, {
	root = root .. "/plugins",
})

vim.cmd.colorscheme("catppuccin")

Hey, thanks for the response. I played around with your feedback and realize that this is something to do with LazyVim and I actually ended up seeing another plugin do this.
I originally thought it was a trailing debug print statement or something, but I don't think so now.
Thanks for the feedback.


panic happens in log.WithFields

If a struct(for example, Model) has a child array([]*Model), and element type of the array has the same type with the struct, panic will happen when trying to log that struct with log.WithFields.
Try the code below.
package main

import (
    "github.com/sirupsen/logrus"
    golog "log"
)

type Model struct {
    Name     string
    Value    int
    Children []*Model
}

func main() {
    testGoLog()
    testLogrusLog()
}

func testLogrusLog() {
    var log = logrus.New()
    log.SetFormatter(&logrus.JSONFormatter{})
    model := &Model{Name: "Tesla", Value: 100}
    model.Children = []*Model{model}
    log.WithFields(logrus.Fields{
        "model": model,
        "topic": "Free topic",
    }).Info("Failed to send event")
}

func testGoLog() {
    model := &Model{Name: "Go", Value: 100}
    model.Children = []*Model{model}
    golog.Println("testGoLog", model)
}

Following is the panic info:
runtime: goroutine stack exceeds<PHONE_NUMBER>-byte limit
fatal error: stack overflow

runtime stack:
runtime.throw(0x10f4178, 0xe)
        /usr/local/go/src/runtime/panic.go:608 +0x72
runtime.newstack()
        /usr/local/go/src/runtime/stack.go:1008 +0x729
...
...

You have a stack overflow here because you have a loop in your data structure.
It's not about the data struct definition itself but the way you fill
model.Children = []*Model{model}

here you fill the child array with a pointer on the parent data, hence the infinite loop

Yes, you are right about this. But the default "log" provided by Go kit have a different behavior. Is a panic appropriate on such  a case?

I've run your test case, the standard library log behave the same way than logrus with a stack overflow.
I don't think logrus is the right place to implement complicated structure check. The contract is that the field you're adding must be convertible to the JSON format as done by the standard library JSON encoder. If there are some potential loop in the data, the user can then implements for such a struct the json.Marshaler interface, so that the check can be done at this level (see https://golang.org/pkg/encoding/json/#example__customMarshalJSON and https://golang.org/pkg/encoding/json/#Marshal)
Basically for the structure to be output with logrus configured with a JSONFormatter this sample code needs to work: https://play.golang.org/p/jV23gXmu3rL

I do not think a log function should raise a panic even if the data structure is inappropriate. Also, I agree that a log lib should not do much heavy data structure check.
It's not that urgent, but we need to know that it's a potential issue, so others do not need to raise a same issue.
 I ran go version and  the output is go version go1.11.4 darwin/amd64.
With the test code I posted before, I commented out the testLogrusLog(), and ran it again. No panic happened. See the picture below.

This is not the log function which panics.
There is a stack overflow in the standard lib JSON formtter.
You may want either to implement for struct the json formatter interface or open an issue at the golang repository.
Can you avoid to put images as code sample, this is very not practical at all.


Change Env to &Env on contract functions

Closing as after further consideration this doesn't seem to add much value.


The [temporary modifier] part of the menu cannot be used

The [temporary modifier] part cannot be used in the menu. For example, the command is: lp user id permission settemp 1 true 1m replace. I can use the command directly, but it cannot be used in the menu to replace the original time.

In the menu?
Assuming you're referring to the LuckPerms GUI plugin, that has nothing to do with the main project.

No, no, I’m not talking about luckperms GUI, I’m talking about trmenu, you cannot use [temporary modifier] in the event section

Can you send a screenshot of what you mean?


Codestyle version is pretty old

I started trying to get my project moved over to using Code Climate for Checkstyle analysis and I discovered that the version I've been using. In particular 7.2 introduced an improvement to DesignForExtension that is very useful for anybody using Bean annotations.
Any chance of getting a newer version of Checkstyle?

Absolutely. Do you want to try doing that via a PR?

I could do that. Is there any standard way to test these engines before
submitting changes?
On Mon, Feb 6, 2017 at 10:35 PM, Sivakumar Kailasam <
<EMAIL_ADDRESS>wrote:

Absolutely. Do you want to try doing that via a PR?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sivakumar-kailasam/codeclimate-checkstyle/issues/4#issuecomment-277892209,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFw0D0t1JS-O0Di2HIbuHyqDQ7NpP_1Wks5rZ-aTgaJpZM4L43qN
.

the usual way is to publish the docker image to local with tag codeclimate/codeclimate-checkstyle and try it in an actual app. But since we're already on 7.0, it should be fairly safe to upgrade


Broken Operator test / kiwi / Full operator test

    Broken Operator test / kiwi / Full operator test

TASK [handle_operator_bundle_validate_output : Get output] *********************
fatal: [localhost]: FAILED! =>
  msg: |-
    the field 'args' has an invalid value ({'hobvo_bundle_validate_error': '{{ hobvo_result.stdout | from_json }}'}), and could not be converted to an dict.The error was: Expecting value: line 1 column 1 (char 0)

    The error appears to be in '/playbooks/upstream/roles/handle_operator_bundle_validate_output/tasks/main.yml': line 4, column 3, but may
    be elsewhere in the file depending on the exact syntax problem.

    The offending line appears to be:

    #     var: hobvo_result
    - name: "Get output"
      ^ here

PLAY RECAP *********************************************************************
localhost                  : ok=80   changed=16   unreachable=0    failed=1    skipped=86   rescued=0    ignored=0

2
2
Error: No such container:path: op-test:/tmp/operator-test/operator-files/operator_sdk_bundle_validate_warnings_and_errors.txt
Error: No such container:path: op-test:/tmp/operator-test/operator-files/operator_sdk_bundle_validate_info.txt
Error: Process completed with exit code 2.

-- https://github.com/redhat-openshift-ecosystem/community-operators-prod/actions/runs/3387113663/jobs/5627574910
I don't think this failure is caused by the changes in the cert-manager OLM bundle.
Originally posted by @wallrj in https://github.com/redhat-openshift-ecosystem/community-operators-prod/issues/1811#issuecomment-1302325671

It was fixed


Disable LLVM ABI breaking checks by default when building swift

The LLVM ABI breaking checks require that all uses of llvm's ADT library must also link libSupport. Parts of the Swift standard library use ADT without Support intentionally. To make this work we must disable the ABI breaking checks when building swift.
This patch changes the default value of the option that controls the ABI breaking checks to disable the checks by default if the swift source directory is present in the LLVM build tree.
Currently disabling these checks is handled by the swift build-script, but to support non-build-script builds having the default work is ideal.

@swift-ci please test

This should be going to master, not swift-4.0-branch.

@jrose-apple it is an LLVM change. There is no master. My thought was to put it in swift-4.0 (which merges to stable), then upstream-with-swift. Is there a reason to leave it out of 4.0?

Oops, sorry, I thought it was a Swift change. Usually we would put something in upstream-with-swift first and then cherry-pick down, just like Clang changes usually go into trunk before they're cherry-picked.
However, why turn this off by default? Why not just turn it off for swiftRuntime?

The setting gets baked into an LLVM configuration-driven header that is included by the ADT headers. It has to be off in the configuration of LLVM in order for it to be off, you can't just override it for a subdirectory. We currently disable it in build-script-impl when building LLVM.

:-/ All right. That doesn't seem like a good long-term answer to me, but I'm not going to put myself into the discussion for now.

@swift-ci please smoke test

@swift-ci please test

Do you need to change LLVM? @bob-wilson had added a way for client to include ADT without getting check inject, why isn't it enough on the swift side?

As far as I can tell, Swift disables the checks when building LLVM, and that is how it gets around the problem.
All this patch does is default the value to off if you are building Swift, so that running CMake with no options produces build files that will actually build successfully.

The files in Swift that include ADT needs to have this defined on the command line: -DLLVM_DISABLE_ABI_BREAKING_CHECKS_ENFORCING, without any need to change the way LLVM is configured at all. That the most recent plan I've been aware of, but @bob-wilson should confirm the direction here.

@joker-eph The Swift workaround @bob-wilson made is here: https://github.com/apple/swift/blob/6c1eec81c44400fd4cefb5d7df32b861a3e6a066/utils/build-script-impl#L728
From this patch:
https://github.com/apple/swift/commit/4081418e04b3a15ff52d6a3b71a875d1423a7b13
This patch allows you to put Swift under LLVM/tools, and run "cmake  && ninja" and get a swift compiler and standard library.
Without this patch the standard library build will fail.

To clarify, when I wrote -DLLVM_DISABLE_ABI_BREAKING_CHECKS_ENFORCING needs to be set on the command line, I didn't mean the cmake invocation, but the clang++ invocation that will compile the swift source code.

The LLVM change to make this possible was: https://reviews.llvm.org/D29919 "allow migrating away from cmake option for LLVM_DISABLE_ABI_BREAKING_CHECKS_ENFORCING"

Ah. That patch is newer than this PR. This PR has been around for over a month, but PR testing was broken when I first tried to land it.

I already put my LLVM change r295090 into swift-4.0-branch (22f170f618). I have been holding the Swift side of the change for a few weeks to minimize the impact on Swift developers, giving more time for people to rebuild their copy of LLVM (https://github.com/apple/swift/pull/7469). I suppose it has been long enough. I'll plan to do that tomorrow.


[Advice] Chinese documentation

Will there be a Chinese document in the future, I am looking forward to it

@1191000814 documentation translation is not on our short-term roadmap, so I'll be closing this issue for the time being.


echo $SHELL prints /bin/bash

echo $SHELL prints /bin/bash
shouldn't it be printing /bin/zsh

Probably. $SHELL is the path to your default shell, so it seems like your default shell didn't get changed to zsh. If this is the case, you can fix it yourself with chsh -s /bin/zsh.

I hope my problem is relevant to this issue. I am having problems making oh-my-zsh work in both Terminal an iTerm2. I tried everything from changing the default shell, to configuring the settings. Here is a screenshot of my attempt to apply the agnoster theme in iTerm:

Same attempt in Terminal:

Regarding the issue, here is what $SHELL command gives me:

Agnoster requires a special Powerline-patched font in order to display properly. See its README.

@apjanke So from what I understood, my oh-my-sh is running correctly my terminal. Like you said, I just need to read README files more often. Is that also might be why the background is in no way influenced by the themes?

That's what it seems like. But in this case I think I misled you: there's no README for Agnoster in Oh My Zsh. (Only in the upstream Agnoster repo.) Sorry.
The themes/agnoster.zsh-theme has info about the fonts it needs in the comments of the file itself. So if a theme isn't working, taking a look at the theme's source code to see if there are notes on its requirements is also a good place to look.

@chirag7jain is your issue fixed?

Closing for the time being. Reopen if it's not solved.

i think some recent update has fixed the issue.
I am getting the correct output now


Fix #3757 and #4836 - enable/disable improvements

This pull requests contains 2 fixes:

#3757 - separates --enable/--disable from the run in progress lock. Allowing to disable during a puppet run.
4836 - allow to set a --disable message when disabling

I get one test failure testing this against the latest 2.7.x.
   Failure/Error: @agent.run
   NoMethodError:
     undefined method `lockfile_path' for AgentTestClient:Class
   # ./lib/puppet/agent.rb:24:in `lockfile_path'
   # ./lib/puppet/agent/disabler.rb:15:in `disable_lockfile'
   # ./lib/puppet/agent/disabler.rb:25:in `disable_message'
   # ./lib/puppet/agent.rb:38:in `run'
   # ./spec/unit/agent_spec.rb:99

Any chance you'd have time to look into resolving it, Brice?

I'm looking at it.

It should be fixed now

It's probably worth migrating the tests in test/util/pidlock.rb (97a2cb82e7f817454aa9f599288eb4c0f6478dac) that aren't covered by the spec counterparts over to be part of the spec suite, and getting rid of test/util/pidlock.rb entirely.
Not required, but it would make me very happy to see the tests under test/ whittled down, since we're not writing any of our new tests there.

Here's a new version which should address all comments.

I'm seeing a test failure.  Which makes sense (#lock_pid is a private method).
Failures:

  1) Puppet::Util::Pidlock with a stale lock#lock should replace with new locks
     Failure/Error: @lock.lock_pid.should == 6789
     NoMethodError:
       private method `lock_pid' called for #<Puppet::Util::Pidlock:0x00000119ae2be8>
     # ./spec/unit/util/pidlock_spec.rb:121:in `block (4 levels) in <top (required)>'

I'm inclined to say that #lock_pid shouldn't be private, but I'm not sure why it was marked private in the first place.  Thoughts?
3c6509befafed9b89bfc8073730125bfc88c22d8


K8S pod logs are not tagged

Describe what happened:
Short-lived cronjob pods (less than 10 seconds) and deployment pods are sometimes not tagged correctly in Datadog.
In this example below, I have a cronjob that runs every 2 mins but only half of the pods have the correct tags such as "Pod Name" and other labels I'm setting. It is not specific to any node.

Incorrect:

Correct:

For deployments, logs may be tagged correctly for roughly ~12 log entries.
I have switched between the Docker socket and K8S File method of log collection and both have this issue. The Docker socket is worse and sometimes misses the logs completely.
Describe what you expected:
All logs to be captured and tagged correctly. We can miss issues that happen in production.
Steps to reproduce the issue:
Run a short-lived cronjob from Kubernetes and watch the logs coming in.
Additional environment details (Operating System, Cloud provider, etc):

Datadog Agent 6.14.1
Google Kubernetes Engine

Pod YAML
apiVersion: v1
kind: Pod
metadata:
  annotations:
    ad.datadoghq.com/snapshot.logs: '[{"source":"kubernetes","service":"campaigns"}]'
...
spec:
  containers:
  - name: snapshot

Environment variables:
DD_APM_ENABLED: "false"
DD_COLLECT_KUBERNETES_EVENTS: "false"
DD_EXCLUDE_PAUSE_CONTAINER: "false"
DD_KUBERNETES_POD_LABELS_AS_TAGS: '{"environment":"environment","process":"process","service":"service"}'
DD_LEADER_ELECTION: "false"
DD_LOGS_CONFIG_CONTAINER_COLLECT_ALL: "true"
DD_LOGS_CONFIG_K8S_CONTAINER_USE_FILE: "true"
DD_LOGS_ENABLED: "true"
KUBERNETES: "true"

i am experiencing the exact same issue! settings are identical...
agent version is
Agent 6.15.1 - Commit: 44c5066 - Serialization version: 4.14.0 - Go version: go1.12.9

@zbutt-muvaki datadog/agent-dev:6-15-1-logs fixed the issue.


LEDC Temporal Dithering Support (IDFGH-11085)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
The lower 4 bits of duty register allow for dithering. Is there any reason why this basic feature is not implemented?

Should we reopen this issue? Any update on this one? I need the dithering feature in my projects too, if esp32 hardware offers such feature is there a reason it's not implemented? I can make a pull request if needed


luna: implement MergingScanner

Closes #303

@skyzh The plan is to merge the two different iterators manually in https://github.com/engula/engula/blob/main/src/engine/luna/src/version.rs#L39.


Video in post hader

In the "read me" file there is a note about using "featured" to have the first image in the post  or a video show in the post header and in the loop. How do you do that? I have tried - but no luck...

Hello,
New version of the theme supports the featured images built into Ghost since ~v.0.5


Inconsistent Usage of .format() and f-strings in FLAML Codebase

In the FLAML codebase, there is inconsistent usage of string formatting methods such as .format() and f-strings (f""). This inconsistency can lead to confusion and hinder readability, especially for contributors who may expect a consistent style throughout the codebase.
Thank you for addressing this issue to improve the quality and consistency of the FLAML project.

I think together with bumping the min python version to 3.8 (all bellow 3.7 are not maintained already) we can normalize all to f-string
https://github.com/microsoft/FLAML/blob/0fe284b21f8eaf55cfccf5c8bb5608e50a554128/setup.py#L170


sort function

It would be nice to have a sorting function in Elvish (maybe named something else, to avoid conflicting with the standard Unix sort command). Ideally it would support structured data, and allow specifying a sorting function (like Clojure's sort-by).

Since Elvish uses strings for numbers, a sort function needs an explicit sorting criteria. Let's call it sort-as:
~> put 2 100 | sort-as number
▶ 2
▶ 100
~> put 2 100 | sort-as string
▶ 100
▶ 2
~> sort-as number [2 100] # also take list argument, like each
▶ 2
▶ 100

This works fine for strings and numbers, but how about structured types? One idea would be to allow the specification of a comparator function which returns whether two elements are in the correct order. For example:
~> edit:command-history | sort-with [a b]{ <= a[id] b[id] } # sort using the id field

If number and string were two "magical" comparator numbers, then the same function could be used for both purposes (i.e. builtin or user-specified comparators).

Yes, the most generic solution is to use functions as comparators.
On the other hand defining functions as comparators can be a bit verbose, and I like the idea of making a mini-DSL for specifying how things should be ordered, string and number being just the simplest examples. For instance, to sort maps first based a numeric score field, and then on the lexical order of a name field can be sort-as [id=number name=string] (this cannot use the map syntax because map pairs are unordered).
Let's make two functions, the one that takes a comparator named sort-with and the one taking the "order DSL" named sort-as.
Why not just one function? It is doable now, because strings and lists are not callable, so comparator functions and order DSLs are disjoint. But it might be possible that we make strings or lists callable in future, and it might make sense for sort-as [a list] and sort-with [a list] to do different things.

@xiaq makes sense. I think the order-DSL should be sufficient for most cases, but the generic function would be nice for more complex ones.

@xiaq just a gentle ping on this topic, since I've recently wished we had it :)

Now that Elvish has a dedicated number type, the sort function does not need to take an explicit sorting criteria any more.

I'm not sure I understand - you would still need a function that receives two elements of the list to sort, and tell which one should go first, no? Number comparison would allow sorting lists of numbers natively, but for strings or structured data you still need a sorting criteria function.

Well, sort can still accept such a function as an option, but it no longer needs to be required for the common use cases of sorting numbers, strings and lists - they all have a natural ordering. It will be be required for sorting other types of values.

Hmm, this needs another name since sort is taken by the classical Unix command sort(1).

How about order?

Sounds good. order then.

I can live with order but prefer sorted from Python: sorted(iterable, cmp=None, key=None, reverse=False) --> new sorted list. Obviously the Elvish signature will be different but it still seems useful for the command, whatever it ends up being called, to accept options for specifying a comparison function and whether the output should be reversed.

I don't have strong feelings between order and sorted, both would be fine.
I fully agree with the need to be able to specify at least a comparison function (maybe a key as a special case).
With respect to the reverse option - I think it would be much better to have a separate reverse function, which can be applied to lists in general, including the output from the sorting function.

A reverse (or reversed) command would be useful in its own right. But it's important, from an efficiency perspective, for the sorting command to have a means of easily inverting the results of the comparison function. Sure, you could pass a custom comparator but when all you want is the "natural" order, but descending rather than ascending, it's far simpler and clearer to say something like sorted &reversed $@list.

The name sorted could be confused for a predicate that determines whether some values are already sorted. Moreover, Python needs a sort/sorted dichotomy since the former is destructive; Elvish has very few destructive operations, so having a sorted without a sort is weird.

The name sorted could be confused for a predicate that determines whether some values are already sorted.

Yes, but that is mitigated, somewhat, by the well established pattern for commands that implement boolean predicates to have a has- or is- prefix; e.g., has-key. Having said that sorted isn't normally used as a verb. Of the synonyms for sort the only candidate I like is order so let's go with that.

I don't find the argument that sorted is not a verb compelling. Rather, I imagine an implicit verb: “Give me the sorted data”. If the command had side effects, such as replacing the data by a sorted version, I would find the argument more convincing.
Even so, I do like order, more as a personal preference – even if one could argue that the verb form indicates a side effect.


Lombok may be used at the provided scope

https://github.com/flashvayne/mysql-mybatis-pagination/blob/060fbd4cb8c2c9f390eb1190a622aec38928d2a9/pom.xml#L58
Pls reference on the

https://stackoverflow.com/questions/29385921/maven-scope-for-lombok-compile-vs-provided
https://projectlombok.org/mavenrepo/
https://www.cnblogs.com/tomcatandjerry/p/10342345.html

Thank you for your comment.
I also think it's better to set lombok scope by "provided".
I will update it in next release.

lombok scope has been updated to "provided"


fix(server): actually perform shutdown on connection loss

Codecov Report
Patch coverage has no change and project coverage change: +0.11 :tada:

Comparison is base (bb19bdf) 83.10% compared to head (8f13f34) 83.21%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #90      +/-   ##
==========================================
+ Coverage   83.10%   83.21%   +0.11%
==========================================
  Files          11       11
  Lines         728      727       -1
==========================================
  Hits          605      605
+ Misses        123      122       -1

Impacted Files
Coverage Δ

lib/src/dtls_server.dart
87.66% <ø> (+0.38%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


README: use correct query string in HTTP API response example

This PR removes the leading > operator from the example query string: >defaults is not valid query syntax.

Thanks!


[Accessibility] Padding on certain components is not adjusted with large font size and hinders readability

Environment Information

Package version(s): 0.1.43
Android SDK version: (fill this out if relevant)

Please provide a reproduction of the bug:

Increase Font size (Setting->Accessibility->Font size-Increase to MAX)
Use the following components:

ListItem.Item
Pills in PillBar
SearchBar
FloatingActionButton
Button

Actual behavior:

ListItem.Item:

PillBar:

SearchBar:

FloatingActionButton:

Button:

Expected behavior:
Components should resize accordingly so that even with the font increase all the text is fully visible, and padding

Priorities and help requested:
Are you willing to submit a PR to fix? (Yes, No)
Requested priority: (Blocking, High, Normal, Low)
Products/applications affected: (if applicable)

I see that on latest 0.1.47, the button padding has been fixed..but the rest I think still needs to get fixed

Seems like issues are fixed on 0.1.47

still worth taking a look at it


Update coffeelint

Update the coffeelint.json file for this project, and fix almost all of the style issues it exposed.

LGTM :tada:


Unable to refer to env variables in args

This does not work when running npm start:
"scripts": {
    "start": "dotenv next -- start -p $PORT"
}

The exiting error being:
TypeError [ERR_INVALID_OPT_VALUE]: The value "{ port: true }" is invalid for option "options"
    at Server.listen (net.js:1450:9)
    …

But this does work:
"scripts": {
    "start": "dotenv npm run start:next",
    "start:next": "next start -p $PORT"
}

Unfortunately the Next.js CLI does not respect a PORT env variable, only the CLI -p arg.

@jaydenseric This seems very logical to me, this is because $PORT is a shell variable so it value is expanded before the dotenv comand is run. This is just due to how shell scripting works AFAIK, so I'm gonna close this, especially given that it seems you've found a solution


Base-Inference.yaml

Excuse me, why is the content in this path: UnSniffer/detection/configs/Base-Inference.yaml empty?

Excuse me, why does the time suddenly increase several times after adding the GOC branch? @Went-Liang


Make number of restarts user choice

quick fix for now: added RESTARTS variable in run.sh

Fixed in 617a2a3


Add enum type test about case insensitive

What changes were proposed in this pull request?
Add enum type test about case insensitive

Why are the changes needed?
The enum type is the case insensitive. This PR is to add some test case to indicate this.

Does this PR introduce any user-facing change?
No.

How was this patch tested?
UTs

Minor improvement. @jerqi @frankliee PTAL

Codecov Report

Merging #280 (a157a64) into master (47effb2) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #280      +/-   ##
============================================
- Coverage     59.71%   59.69%   -0.02%
+ Complexity     1377     1376       -1
============================================
  Files           166      166
  Lines          8918     8918
  Branches        853      853
============================================
- Hits           5325     5324       -1
- Misses         3318     3319       +1
  Partials        275      275

Impacted Files
Coverage Δ

...storage/handler/impl/DataSkippableReadHandler.java
81.25% <0.00%> (-3.13%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


build it so people using Github dependency can benefit too

I forgot to build it yesterday.
Pushing built code to Github is not the best practice but I suppose there's a number of people using the Github URL as their dependency (they probably haven't caught up with the fact you just pushed a new version to npm).

Hi @not-raspberry

people using the Github URL as their dependency

I don't support this since this is against Github's terms of service. FWIW, I have pushed the latest changes on NPM so this should be fine now. Appreciate the PR, but I'm afraid I can't merge it.


sourcekite-lsp -> sourcekit-lsp

Fixed a very confusing typo.

@343max Good catch! Thanks a lot. Seems like my iOS favors sourcekite over sourcekit.


shadow props of parent shouldn't inherit to children element...

Issue Description
take a look at this screenshot...

take a look at row3 text... it inherit shadow props from parent component <View />...
Steps to Reproduce / Code Snippets
<View
  key={id}
  style={styles.box}
  shadowOffset={{height: 10}}
  shadowColor='black'
  shadowOpacity={0.5}
>
  <Text style={styles.text}>{title}</Text>
</View>

Expected Results
shadow props of parent shouldn't inherit to children element...
Additional Information

React Native version: latest
Platform(s) (iOS, Android, or both?): ios
Operating System (macOS, Linux, or Windows?): mac

Hi @MeKarina, checking in on this open issue. I'm hoping an updated version of RN has resolved this issue for you. I'll be closing the issue. If it still persists reopen the issue and I'll find someone to review.

@ericnakagawa Which version of RN solved this? I'm running 0.40.0 now and still experiencing the same issue.

I can reproduce this with transparent or RBGA backgrounds on my view using RN 0.43.4
import React from 'react';
import {
  StyleSheet,
  Text,
  View,
} from 'react-native';

export default class App extends React.Component {
  render() {
    return (
      <View style={styles.container}>
      	<View style={ styles.withShadow }>
      		<Text style={styles.text}>HELLO WORLD solid</Text>
      	</View>

        <View style={[styles.withShadow,{backgroundColor:'transparent'}]}>
          <Text style={styles.text}>HELLO WORLD transparent</Text>
        </View>

        <View style={[styles.withShadow,{backgroundColor:'rgba(33,33,33,0.05)'}]}>
          <Text style={styles.text}>HELLO WORLD rgba</Text>
        </View>

        <View style={[styles.withShadow,{backgroundColor:'rgba(33,33,33,0.05)'}]}>
          <Text style={styles.text}>HELLO WORLD rgba</Text>
        </View>
      </View>
    );
  }
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
    justifyContent: 'center',
    alignItems: 'center',
    backgroundColor: '#fff',
  },
  text: {
    fontSize:24,
    color:'white',
    textAlign:'center',
  },
  withShadow: {
    margin: 20,
    height: 150,
    width: 150,
  	backgroundColor: '#EEE',
    borderWidth:1,
    shadowColor: "#000000",
    shadowOpacity: 0.85,
    shadowRadius: 5,
    shadowOffset: {
      height: 0,
      width: 0
    }
  }
});

Can we reopen this? Child element still seem to inherit their parent's shadows.

I have the same issue on RN 0.51

0.53 and I'm also experiencing this issue.

Same here.

Please re-open this issue. I am experiencing this on 0.55.2 .
Thankfully @sanderfish provided a temporary fix.

Noticing that when using @sanderfish it will work with Text children, but if the child is an ImageBackground it will still inherit the shadow.
react-native: 0.55.3

Can we re-open this issue. On React-Native 0.55.0 and experiencing this bug as well.

Experiencing this issue as well, please re-open.

Please re-open. Thanks.

Same issue on 0.55.4 version

Having this issue as well

Same Issue.


Staged upstream repositories

/test all

/test all
/verify-owners

/lgtm

/approve

/lgtm cancel

Oh weird it's probably reading from the OWNERS file that attached to the commit and not this repository's current OWNERS file.

/verify-owners
/lgtm

/verify-owners

Superseded by #5
/close


Consider ways of getting partner's data

Link in the partner data for partners who also filled out the survey?
Is there anything useful in the household data?

I wrote code that merges in the partner's fertility intention data, for people whose partner also responded to the LISS survey.
We have data on partner's 2020 fertility intentions for 30% of the people with non-missing outcome data in the training set. Most of those people also answered the fertility intentions questions themselves, so the marginal benefit of adding in the partner's fertility intentions is that the intentions might differ from the respondent's intentions. I compared the respondent's intentions with the partner's intentions, and they generally align, so my guess is we aren't going to get much boost in F1 score from adding the partner's intentions, but I'm excited to find out! You can see the comparisons in the PDF below.
There is also a small handful of people for whom the respondent didn't answer the fertility intention questions, but the partner did answer these questions.
exploration_of_linking_partner_data.pdf
My next step is to integrate the partner linkage code into our main codebase (within submission.R) and test models with it.

TLDR: I am going to change the partner-merging code so that it does NOT draw on the supplementary data.
Details:
My original code merged in partner data from two sources: (1) the training data, and (2) the supplementary data. In other words, partners who were outside the 18-45 age range were included.
However, I realized two challenges with using partners from the supplementary data:

(1) For the time-shifted training data, merging in partners from the supplementary data would require that we time-shift the supplementary data too. This is feasible, but would likely be a lot of work relative to the potential gain.
(2) submission.R (where we need to insert the code for merging the partner data) is not currently set up to use the supplementary data. I think that to get submission.R to use the supplementary data when the organizers run the code on the holdout set, we would also need to edit Run.R. This is feasible, but we can't test it unless we create a fake version of the supplementary data.

These reasons led me to consider discontinuing the use of the supplementary data. My next question was, how much benefit is there of using partners from the supplementary data? For non-time-shifted data, we can merge in 390 partners in total. 41 of these come from the supplementary data. Of those that come from the supplementary data, 40 do NOT have a new child in the outcome window, and 1 does have a new child.

So, while we do lose some partner data if we don't use the supplementary data, I think the model is likely to already determine that no new child is expected based on the partner's age, so there may not be much benefit of merging features from partners in the supplementary data.
We can add in partners from the supplementary data later if desired.

Previously, our best F1 score on CV folds was 0.778. With partner survey data merged in, our best F1 score on CV folds is 0.779 -- so, technically better, but probably not really an improvement. See here for a comparison of various runs.
The partner's response to cf20m130 (within how many years do you expect to have children) did end up being one of the most important features, though. Here's a screenshot of the feature importance from this model (it's just screenshot of the top half; 80 features were chosen in total):

As a next step, I will play around with some minor tweaks, then make the submission!

After adding a few extra features that I thought seemed important, and keeping the raw features on partner's birthyear in addition to the coalesced partner birthyear feature, I got an mean F1 score of 0.782 on the CV folds. I noted this in the google sheet. I tested both of these changes at the same time, so it's possible that one change mattered and the other didn't. This is the model I'm going to submit, so we'll see how it generalizes on the holdout set!

In the code we last submitted to the leaderboard, we have partner data for 829 out of 2839 people in our data. However, these 829 people include 205 people whose outcomes are not available, either because they are out of age range or because it was difficult to calculate the outcome. We would not be able to get partner data for people with such partners in the test set because the PreFer organizers "excluded people for whom the outcome is missing from the holdout set."
If we were to add these 205 people's partner data back into our current model, the F-1 score would increase by 0.0004 from 7963717 to 7967333. I interpret this as virtually no difference in performance, and the model with more partner data runs the risk of being overly reliant on partner data. Therefore, I have excluded the partner data for these 205 people.


bug: HelmState.scatterGather ignores item parameter

Came across this in #782
See https://github.com/roboll/helmfile/blob/bce2f4728b71a7a173766f11e1018c200e4c602c/pkg/state/state_run.go#L15-L20
It looks like the intention was to make that method generic and be informed of the number of items coming in, but it seems to default/max against the number of releases instead.
This may be the first/only non-release based usage.  It would be good to re-use it for environment secrets.
My proposal is to use the items parameter, which is currently unused.  Can put in a PR if that makes sense.

@travisgroth Wow! Good catch.
Yeah items should be used instead of len(st.Releases) when concurrency isn't specified(0).
To be extra clear, I believe it should be:
 if concurrency < 1 {
 	concurrency = items
 } else if concurrency > items {
 	concurrency = items
 }

Or even just:
 if concurrency < 1 || concurrency > items {
 	concurrency = items
 }

Btw concurrency > items is there to cap concurrency to number of items. This isn't strictly needed, but for avoiding unnecessary/redundant goroutines.
I'd appreciate it if you could submit a PR 😄


move test_util out of q, rework due to es6

[x] rework test_util
[x] check passed tests locally
[x] check correct behavior if some test failed
[x] update node version in CircleCI to LTS (tests were failed on previous v8)
[ ] change octaral literals to something different

I don't know how to fix it:
Octal literals are not allowed in strict mode
console.log('\n>>> \033[1;32mpass\033[0m');

@cnishina , could you take a look at this PR, please

Let's leave the octal literals as is. This should be blocked by #5038. In #5038, the PR turns on more of the error tests.

Reference #4995

It fix change octal to plain text. So, in console is just >>> \033[1;32mpass\033[0m

I suggest change:

\n>>> \033[1;31mfail: ' + err.toString() + '\033[0m, that produce just "pass" to \n>>> test was passed
\n>>> \033[1;31mfail: ' + err.toString() + '\033[0m, change to \n>>> test was failed. Error: ${error}

Hmmm... something is broken. The tests pass but nothing is running.

I'm going to work on a separate PR and I'll get it to work today.

Wow, CircleCI passed! We need just fix octal message. @cnishina

@cnishina , sorry but I'm not aware how to fix it if you want to show test duration :)

So here's how I would fix up the PR.... https://github.com/angular/protractor/pull/5058
The octal is problematic but we are not required to update everything. Leaving that last section as is in test_util is fine. The bigger concern is to remove q. Please feel free to borrow / steal as much as you need.


Feature submission template updated

Following the discussion, happened at the SIG PM regular meeting 2017-03-14, agreed in the document, feature submission template is much simplified and enhanced.

cc @kubernetes/kubernetes-pm @kubernetes/features-maintainers

cc @kubernetes/sig-contributor-experience-misc

Approvers are automatically assigned based on files modified and the OWNERS files.  Do we need that field?

@idvoretskyi What's blocking us from merging this now?

@bgrant0607 I'd like to adjust this a bit today; let's discuss the final version tomorrow (4/11) on SIG-PM meeting.

The template looks fine to me @idvoretskyi and I think that the simplified template is a good incremental improvement.
I would really like to see the issue of how to make changes to the project tackled as a general governance issue. Personally I believe an RFC (Rust) or PEP (Python) process may be more helpful in the medium term to collect all "major" changes to the project.
I also feel like it would be nice to move away from GitHub Issues as a way of tracking "features" in favor of maintaining files under source control which would a) reduce our reliance on GitHub and b) allow for contributors to look at historical changes to the project more easily and c) associate design documentation with the change proposal. Again,  Rust or Python provide interesting prior art in this area.

@calebamiles

I also feel like it would be nice to move away from GitHub Issues as a way of tracking "features" in favor of maintaining files under source control which would a) reduce our reliance on GitHub and b) allow for contributors to look at historical changes to the project more easily and c) associate design documentation with the change proposal.

I agree that some work is needed in this area; I disagree that we should move away from GitHub (if GitHub is able to solve our questions). I would prefer to use as fewer instruments as possible (without quality and efficiency reducing).
I suppose we should start moving to GitHub projects consuming for this area - as we have already discussed at one of the previous SIG-PM meetings.

+1 to tracking features in source control instead of issues.   Github issues pretty much guarantee incoherency for any non-trivial conversation.
@idvoretskyi I'm not sure what your concerns are here.  Feature proposals would still evolve through github, just in successive PRs instead of a single issue.  To me the clear advantage would be that each PR merge would result in a new and coherent version of the proposal.

@calebamiles @marun
The features repo wasn't originally intended to be a replacement for the proposal process (which also needs to be formalized/improved). It was supposed to be a tracking system.

@marun I second @bgrant0607. The feature proposal lands to https://github.com/kubernetes/community/tree/master/contributors/design-proposals - under the source control.
We need to have the easiest way to track and visualize the features, that's why we have created the dedicated features repo and been using it for almost four release iterations. @calebamiles and I have started looking at the possible areas to enhance the area regarding visualization (GitHub projects that I've mentioned above), but it's not about the source control - it's a different story.

Since we are rapidly approaching features repo freeze, I'd really like to get this merged (today if possible).
I realize there are still outstanding policy discussions (why features repo vs community, version controlled vs issues, and what exactly constitutes a feature).  Can we save those for the next sig-pm meeting and get this merged for now.

@grodrigues3 sounds good to me. @bgrant0607 any objections?

Squashed and merging.


Missing Typescript Definitions

Hey devs! Thank you so much for making this wonderful utility! So the original node-bunyan has typescript definitions under DefinitelyTyped - for consistency (and ease of use for the friendly typescript developer) is there a chance that we could get some typescript definitions?

hi @jrkienle  i just added to DefinitelyTyped
https://github.com/DefinitelyTyped/DefinitelyTyped/pull/56638


add ThermoPro and Shelly temperature/humidity sensors

I will create a new PR with an extra sensor (Goovee)


Adding a new final field to a class with @RequiredArgsConstructor gives error "Variable xxx might not have been initialized"

Short description
I have an existing Spring @Service class with the annotation @RequiredArgsConstructor.  It has a series of private final fields.  These fields should all be in the constructor generated by Lombok.  If I add a new final field like:
private final String foo;
The field shows up in the generated constructor (I can see it in the Structure view) but I get the error message "Variable 'foo' might not have been initialized".  If I close the project and reopen it, the error has gone away.  This works but is a bit annoying.
Expected behavior
Adding the new field should not generate an error message.
Version information

IDEA Version: IntelliJ IDEA 2020.2 (Ultimate Edition)
Build #IU-202.6397.94, built on July 27, 2020
Licensed to Fox Corporation / Gary Peskin
Subscription is active until May 2, 2021
Runtime version: 11.0.7+10-b944.20 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 2000M
Cores: 4
Registry: decompiler.dump.original.lines=true
Non-Bundled Plugins: Lombook Plugin, com.godwin.json.parser, MavenRunHelper

JDK Version: _What is your JDK version, including update level?_Amazon Corretto JDK 11.0.8_10

OS Type & Version: _Are you on Mac/Windows/Linux? Provide as much information as possible about versions_Windows 10 Enterprise 10.0.17134 Build 17134

Lombok Plugin Version: _What is the version of the plugin installed?`_0.30-EAP

Lombok Dependency Version: _What version of lombok.jar are you using?_1.18.12

Steps to reproduce

Start with a working class annotated with @RequiredArgsConstructor and several private final fields.
Add a new private final field like (private final String foo).
Observe "Variable foo might not have been initialized" error.

Sample project
I am unable to share my existing project.  If you need a sample project, please let me know.

[ ] Sample project provided
[ ] I am able to reproduce this error on the sample project by following the steps described above

Additional information
Is there any additional information you can provide to help us understanding and solving the issue? No.
Stacktrace
If you are experiencing an issue and IntelliJ throws an error please provide the stacktrace.

STACKTRACE HERE (inside code markup)

```N/A

I met same problem recent days. After I upgrade to IDEA 2020.02

IntelliJ  2020.2 has a bug and is incompatible with lombok plugin. Please upgrade to at least IntelliJ IDEA 2020.2.1 RC Build #IC-202.6948.36, built on August 18, 2020
Similar #840


Join tests broken

This may be a result of going to left outer join.  If you look at the
berkeley_tables in demo you'll see why it is so nice to have.  For the case
where there is a unique item in each table, these all are the same.  I do
think the asymmetry is quite natural.
David E. Culler
Friesen Professor of Computer Science
Electrical Engineering and Computer Sciences
University of California, Berkeley
On Tue, Jul 28, 2015 at 9:31 AM, Alvin Wan<EMAIL_ADDRESS>wrote:

—
Reply to this email directly or view it on GitHub
https://github.com/dsten/datascience/issues/22.

@deculler I see I see. However, it looks like the left outer join isn't preserving unmatched rows from the "left" (first) table.
Output of table.join('points', table2)
E      points | letter | count | totals | names
E      2      | c      | 3     | 6      | two
E      2      | b      | 3     | 6      | two
E      1      | a      | 9     | 9      | one

where table is:
	letter | count | points
	a      | 9     | 1
	b      | 3     | 2
	c      | 3     | 2
	z      | 1     | 10

From table, the last row is missing. Right now, it looks like it's still an inner join, except with duplicate matches in the indexed column, repeated.
Let me know if I'm missing something, or if I should fix it.

I went ahead and changed join so that it included rows in left and not in right, amended tests.

The result only includes matched rows.  The difference we were after is
that a row in the right might match multiple rows in the left.  There would
be a row in the result for each left row that had a matching right.  The
more general form would have a row in the result for each pairwise match.
Thanks for looking into this.
David E. Culler
Friesen Professor of Computer Science
Electrical Engineering and Computer Sciences
University of California, Berkeley
On Tue, Jul 28, 2015 at 10:43 PM, Alvin Wan<EMAIL_ADDRESS>wrote:

@deculler https://github.com/deculler I see I see. However, it looks
like the left outer join isn't preserving unmatched rows from the "left"
(first) table.
Output of table.join('points', table2)
E      points | letter | count | totals | names
E      2      | c      | 3     | 6      | two
E      2      | b      | 3     | 6      | two
E      1      | a      | 9     | 9      | one
where table is:
letter | count | points
a      | 9     | 1
b      | 3     | 2
c      | 3     | 2
z      | 1     | 10

From table, the last row is missing. Right now, it looks like it's still
an inner join, except with duplicate matches in the indexed column,
repeated.
Let me know if I'm missing something, or if I should fix it.
—
Reply to this email directly or view it on GitHub
https://github.com/dsten/datascience/issues/22#issuecomment-125849613.

Ah, I see. Sounds good.
Yep.


[Bug]: Palm2: Text-Bison-001 is no longer working

Contact Details
<EMAIL_ADDRESS>What happened?
Text-Bison is no longer working under the Palm2 model selection. Chat Bison is working fine. Text Bison is giving "bad request" error message.
Additional Context
Text Bison is interesting because it allows for the changing of safety parameters to get more or less censored outputs. It is unclear whether its specific implementation in LibreChat allows this. Clarification/implementation here would be useful.
Steps to Reproduce

Select Palm2
Select Text-Bison
Submit a query.

What browsers are you seeing the problem on?
Microsoft Edge
Relevant log output
},
    paramsSerializer: [Function: paramsSerializer],
    body: '{"instances":[{}],"parameters":{"model":"text-bison","modelLabel":null,"temperature":0.2,"maxOutputTokens":1024,"topP":0.95,"topK":40}}',
    validateStatus: [Function: validateStatus],
    responseType: 'json'
  },
  code: 400,
  errors: [
    {
      message: 'Invalid instance: struct_value \t {\n}\n',
      domain: 'global',
      reason: 'badRequest'
    }
  ]
}

Screenshots
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Was resolved with the recent google update, just forgot to close this: https://github.com/danny-avila/LibreChat/commit/583e978a820225c4dda94d35d6058e8106efb3e8


Could not find the method .execute() within drive.files.get(id)

Hi, you'll need to read the new documentation on how to migrate your code to 1.x. See the README and code examples on how to use the 1.x (or recently released 2.x) code. We no longer use .execute().
Here's the migration guide which may also help: https://github.com/google/google-api-nodejs-client/blob/master/MIGRATING.md

Problem fixed. Thanks for your help. I should close the issue now.


data can't be downloaded

The data on this link: data/original-xml-part.tar.gz cannot be downloaded it's asking for username and password credentials.  Is there another place where it can be found?

I apologise for not making this more explicit. To download the dataset you need to register first on this page ("Download" section). After registration you will be able to download the data/original-xml-part.tar.gz. :)

Thank you!


Add David Dotson as team member

@conda-forge/core Could you please add @dotsdl to the team for this repository

So this hasn't happened yet only because our team update script is having issues. There is a proposed fix in the pipeline that merely needs a review and merge.
xref: https://github.com/conda-forge/conda-forge.github.io/pull/280

It appears he is already added to this team. So closing this out. Please us know if there are other issues.


[request] Change number of pages

The books that I wish to print actually allows 10 pages per print job.  Is it possible to modify the code to print 10 pages at a time?
Thanks.

Yes, this is doable. Does the regular script with 2 pages work for you? I ask because a few users have ran into issues with the tab, and I want to make sure that at a baseline, the normal script works before I proceed.

Yes, the 2 page at a time script works great. Thank you for your efforts!

You're welcome. I wrote a new script. I got it to compile, but I don't have a book that allows 10 pages, so I'm not sure if it works. It's on a test branch:
https://github.com/LifeAlgorithm/VitalSourcePrinter/blob/TabFix/VitalSourcePrinter.py

It works great!  Thank you very much.
Note: The first print still only prints 2 pages, but the next print does however many you tell it.

I did that for speed reasons, but I can see how it might be unclear to someone who uses the script. I'll look into changing that later, but I'm glad the script is functional for now.


Install package error

When running ".\vcpkg install cpprestsdk" at command line I get this error:
-- CURRENT_INSTALLED_DIR=C:/Users/MYUSER/AppData/Roaming/vcpkg/installed/x86-windows
-- DOWNLOADS=C:/Users/MYUSER/AppData/Roaming/vcpkg/downloads
-- CURRENT_PACKAGES_DIR=C:/Users/MYUSER/AppData/Roaming/vcpkg/packages/cpprestsdk_x86-windows
-- CURRENT_BUILDTREES_DIR=C:/Users/MYUSER/AppData/Roaming/vcpkg/buildtrees/cpprestsdk
-- CURRENT_PORT_DIR=C:/Users/MYUSER/AppData/Roaming/vcpkg/ports/cpprestsdk/.
-- Cloning done
-- Adding worktree and patching done
-- Configuring x86-windows-rel
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:14 (message):
Command failed: C:/Program Files
(x86)/CMake/bin/cmake.exe;C:/Users/MYUSER/AppData/Roaming/vcpkg/buildtrees/cpprestsdk/src/Release;-DBUILD_TESTS=OFF;-DBUILD_SAMPLES=OFF;-DCPPREST_EXCLUDE_WEBSOCKETS=ON;-G;Visual
Studio 14
2015;-DCMAKE_VERBOSE_MAKEFILE=ON;-DCMAKE_BUILD_TYPE=Release;-DCMAKE_TOOLCHAIN_FILE=C:/Users/MYUSER/AppData/Roaming/vcpkg/triplets/x86-windows.cmake;-DCMAKE_PREFIX_PATH=C:/Users/MYUSER/AppData/Roaming/vcpkg/installed/x86-windows;-DCMAKE_INSTALL_PREFIX=C:/Users/MYUSER/AppData/Roaming/vcpkg/packages/cpprestsdk_x86-windows
Working Directory:
C:/Users/MYUSER/AppData/Roaming/vcpkg/buildtrees/cpprestsdk/x86-windows-rel
See logs for more information:
  C:\Users\MYUSER\AppData\Roaming\vcpkg\buildtrees\cpprestsdk\config-x86-windows-rel-out.log
  C:\Users\MYUSER\AppData\Roaming\vcpkg\buildtrees\cpprestsdk\config-x86-windows-rel-err.log

Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_cmake.cmake:27 (vcpkg_execute_required_process)
ports/cpprestsdk/portfile.cmake:34 (vcpkg_configure_cmake)
scripts/ports.cmake:96 (include)
Error: build command failed
LOGS contents for C:\Users\MYUSER\AppData\Roaming\vcpkg\buildtrees\cpprestsdk\config-x86-windows-rel-out.log:
-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
-- Configuring incomplete, errors occurred!
See also "C:/Users/MYUSER/AppData/Roaming/vcpkg/buildtrees/cpprestsdk/x86-windows-rel/CMakeFiles/CMakeOutput.log".
See also "C:/Users/MYUSER/AppData/Roaming/vcpkg/buildtrees/cpprestsdk/x86-windows-rel/CMakeFiles/CMakeError.log".
My CMAKE version is : cmake-3.6.2-win32-x86

Hi lsalamon, thanks for reporting this issue.

Do you have Visual Studio 2015 Update 3 installed?
What are the contents of the environment variable "VS140COMNTOOLS"?
Are you able to build trivial CMake projects externally to Vcpkg?

Hi R. Schumacher, this is the answers:

Version 14.0.25421.03 Update 3
VS140COMNTOOLS=H:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools\
no errors on build Vcpkg

Can you build a cmake project normally from the command line without using vcpkg at all? Something like a simple "hello, world!" project.

No, no success in my "Hellow, world!" project. But this help me to correct environment. I try to build https://github.com/jameskbride/cmake-hello-world and this give me direction: "The Windows SDK version 10.0.10586.0 was not found." in CMakeError.log.
After that I install SDK and build successful.
-- CURRENT_INSTALLED_DIR=C:/Users/MYUSER/AppData/Roaming/vcpkg/installed/x86-windows
-- DOWNLOADS=C:/Users/MYUSER/AppData/Roaming/vcpkg/downloads
-- CURRENT_PACKAGES_DIR=C:/Users/MYUSER/AppData/Roaming/vcpkg/packages/cpprestsdk_x86-windows
-- CURRENT_BUILDTREES_DIR=C:/Users/MYUSER/AppData/Roaming/vcpkg/buildtrees/cpprestsdk
-- CURRENT_PORT_DIR=C:/Users/MYUSER/AppData/Roaming/vcpkg/ports/cpprestsdk/.
-- Cloning done
-- Adding worktree and patching done
-- Configuring x86-windows-rel
-- Configuring x86-windows-rel done
-- Configuring x86-windows-dbg
-- Configuring x86-windows-dbg done
-- Build x86-windows-rel
-- Build x86-windows-rel done
-- Build x86-windows-dbg
-- Build x86-windows-dbg done
-- Package x86-windows-rel
-- Package x86-windows-rel done
-- Package x86-windows-dbg
-- Package x86-windows-dbg done
-- Warning: Could not find a matching pdb file for:
C:/Users/MYUSER/AppData/Roaming/vcpkg/packages/cpprestsdk_x86-windows/bin/cpprest_2_8.dll
-- Performing post-build validation
-- Performing post-build validation done
Package cpprestsdk:x86-windows is installed
Tanks


Class metadata fix for Windows [5.0, ABI]

On Windows we can't reference the runtime's Builtin.NativeObject value witness table directly from class metadata. Instead fill it in at runtime for singleton metadata initialization.
Do this on all platforms, even though its not needed on Linux or Darwin, for simplicity. A subsequent Windows-specific change will force the use of singleton metadata initialization for all classes, even when the class is otherwise fixed.

Convergence: no; ABI impact: yes

I am merging this as it's a low risk ABI change.


[FEATURE]: Support customIndex for MySQL

Feature hasn't been suggested before.

[X] I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request
Background
MySQL and MySQL ecosystem exists all kinds of create index scenes as below.

create normal index:

CREATE INDEX idx_name on users(name) ;
CREATE INDEX idx_name on users(name) using hash;
CREATE UNIQUE INDEX idx_id on users(id);

create spatial index:

CREATE SPATIAL INDEX idx_geom on users(geom);

create fulltext index:

CREATE FULLTEXT INDEX idx_doc(doc) WITH PARSER NGRAM;

create vector index for MySQL:

CREATE VECTOR INDEX idx_embedding ON users(embedding) SECONDARY_ENGINE_ATTRIBUTE=\'{"type":"spann", "distance":"cosine"}\';

create vector index for OceanBase (a MySQL-like database but not 100% compatible):

CREATE VECTOR INDEX idx_embedding ON users(embedding) WITH (distance=L2, type=hnsw);

Proposal
Current Dizzle index couldn't implement these demands. So I proposal to add customIndex to provider flexible API.
const users = mysqlTable(
    "users",
    {
      id: bigint({ mode: "bigint" }).autoincrement().primaryKey(),
      name: varchar({ length: 255 }).notNull(),
      embedding: vector("embedding", { length: 3 }),
    },
    () => {
      return {
        idx_embedding: customIndex({
	  name: 'idx_embedding',
	  raw: 'CREATE VECTOR INDEX idx_embedding ON users(embedding) SECONDARY_ENGINE_ATTRIBUTE=\'{"type":"spann", "distance":"cosine"}\';',
	}),
        idx_fulltext: customIndex({
	  name: 'idx_fulltext',
	  raw: 'CREATE FULLTEXT INDEX idx_doc(doc) WITH PARSER NGRAM;',
	}),
      };
    }
  )

Could cover vectorIndex requirement in #3695

This would be much better 10000000%


inhouse tip: investigate node 02 dockerd constantly restarting

https://git.speag.com/oSparc/osparc-infra/-/issues/incident/56


Serialize tensors in PyTorch 0.4

As of PyTorch 0.4.0, type(t) where t is a tensor will always equal torch.Tensor. To get the original types, you need to call t.type(). This change fixes serialization for torch tensors. Otherwise, they're truncated (at least upon deserialization in Ray).

The change looks basically good to me. Unfortunately, I don't think our CI setup currently tests with PyTorch anymore (there were problems with the binary packages available), and the failures look unrelated.

@robertnishihara See here and search for The type() of a Tensor has changed. Basically, type(t) for any tensor type will always be torch.Tensor. To do a proper comparison, you need to use isinstance or run t.type()

Thanks @alok, can you try rebasing on the master and see if the test failures go away?

LGTM, the test failure was fixed in https://github.com/apache/arrow/commit/4b8511f92d24dc9d5ace150218a2902c8e32dc76


Constraint reference is not supported

Configuration information
<status>
  <ehrbase_version>0.17.2</ehrbase_version>
  <openehr_sdk_version>30e3c81</openehr_sdk_version>
  <archie_version>1.0.3</archie_version>
  <jvm_version>Oracle Corporation 11.0.6+10</jvm_version>
  <os_version>Linux amd64 4.15.0-91-generic</os_version>
  <postgres_version>PostgreSQL 10.14 (Ubuntu 10.14-0ubuntu<IP_ADDRESS>) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0, 64-bit</postgres_version>
</status>

Steps to reproduce
This issue is the same fixed by https://github.com/ehrbase/ehrbase/issues/594 but with a different template.
I have merged develop into my branch and still getting this error: o.e.v.constraints.wrappers.CDvCodedText  : Constraint reference is not supported, path: /content[openEHR-EHR-SECTION.adhoc.v1]/items[openEHR-EHR-OBSERVATION.demo.v1]/data[at0001]/events[at0002]/data[at0003]/items[at0004]/items[at0011]
That happens with the POST /composition of the RIPPLE example: (upload the template first)
EHRbase.postman_collection.json.txt
Actual result
In the response I get an exception message.
Expected result (Acceptance Criteria)

Response should be a 201 Created
No error logs should appear in ehrbase terminal

While working in the conformance test cases found that the type of constraint when there is a CONSTRAINT_REF in ADL is mapped to a C_CODE_REFERENCE in the OPT.
I would like to confirm is this issue is due to EHRBASE not supporting C_CODE_REFERENCE or because of the missing constraint_bindings.
Please @chevalleyc @stefanspiska @birgerhaarbrandt do you have some insights on C_CODE_REFERENCE being supported by the OPT model we use internally? Thanks.


 But later on, when that creature dies, it drops a corpse again. So you can endlessly reanimate. The reanimated need to not drop corpses.
Possible solution: Custom undead creature blueprint that has 0% corpse drop chance

Alternative suggestion: when creating the reanimated creature run creature.RemovePart<Corpse>()

Great suggestion @librarianmage , thanks. Much less work than all these new XMLs


Set http.route attribute as path template

We have seen issues with the current spans exported from the http
library in observability backends, due to too granular span names when
the routes contain path variables.
As per the opentelemetry specification, this PR extracts the path
template from the UriRouteMatch object, and sets it as the
http.route attribute.
https://opentelemetry.io/docs/reference/specification/trace/semantic_conventions/http/#http-server-semantic-conventions

appreciate any feedback @sdelamo


Parcels are not rendered inline and not "flex"-ible

Parcels do not render inline with content which makes it difficult to style with flexbox. It renders within an extra div that also is not style-able, especially when the Parcel needs to rest flexed/inline with another element.
It would be nice to either:

Accept React.Fragment as a component to wrapWith
Add a class property to the wrapping div, or perhaps pass style props directly to the wrapping div
Use react-mount-point-unstable and insert Parcels inline so it can flow naturally

Alternatively, wrapWith could also be a fragment, right?

Closing because this is old. Feel free to reopen if there's continued interest in this.


qiuckstart

Hi, I follow the your steps to install the packages but failed to run the quick start code.
I use your test data ‘test_points.vg’
It shows 'NameError: name 'bounds' is not defined'

then I add ‘from trimesh import bounds’
but it shows ‘TypeError: 'module' object is not subscriptable’

this are my environment
ubuntu 20.04
python=3.9.13
abspy=0.2.1
sage=9.4
others are installed by ‘pip install -r requirements’
Can I get any tips? thank you

Hi @fangxunyes, here bounds is just some arbitrary placeholder representing the bounding box of the geometry (hence bounds[:, 0, 2] means the minimal Z-value, therefore additional_planes to append here actually represents the bottom plane of the geometry). You can assign any plane parameters to additional_planes, e.g.,
additional_planes = [[0, 1, 2, 3], [100, 200, 300, -500]]

You can get some idea by checking test_primitive and test_combined.


[TOA-154] Add firebase cloud messaging support

https://droidsonroids.atlassian.net/browse/TOA-154

SonarQube analysis reported 1 issue
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 Navigator.kt#L35: Prefer splitting up complex methods into smaller, easier to understand methods. MCC 11 is greater than the threshold 10.

SonarQube analysis reported 1 issue
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 Navigator.kt#L35: Prefer splitting up complex methods into smaller, easier to understand methods. MCC 11 is greater than the threshold 10.