[BUG] Convert markdown to PDF

Describe the bug
My pipeline goes into error during the "Convert markdown to PDF" step (see screenshot 1).
Despite the validation of the "Convert markdown to HTML" step, the errors seem to start at this step (see screenshot 2)
To Reproduce
I get this error every time I launch the pipeline.
Expected behavior
The pipeline completes without errors.
Screenshots

Run type (please complete the following information):

Mode: 1
Client: Pipeline
Version: 2.3.0

Additional context
Contents of my azure-pipelines.yml file :
# PIPELINE VARIABLES THAT NEEDS TO BE DEFINED FIRST FOR THIS PIPELINE TO WORK:
# CLIENT_ID (application ID), CLIENT_SECRET (application secret), TENANT_NAME, USER_EMAIL (email that will be used in the commit), USER_NAME (name that will be used in commit)
# based on https://github.com/aaronparker/intune-backup-template

trigger:
  none
schedules:
  - cron: '0 1 * * *'
    displayName: "1am"
    branches:
      include:
      - main
    always: true

jobs:
  - job: backup_document
    displayName: Backup configuration and generate markdown
    pool:
      vmImage: ubuntu-latest
    continueOnError: false
    steps:
    - checkout: self
      persistCredentials: true

    # Set git global settings
    - task: Bash@3
      displayName: Configure Git
      inputs:
        targetType: 'inline'
        script: |
          git config --global user.name $(USER_NAME)
          git config --global user.email $(USER_EMAIL)
        workingDirectory: '$(Build.SourcesDirectory)'
        failOnStderr: true

    - task: Bash@3
      displayName: Remove existing prod-backup directory
      inputs:
        targetType: 'inline'
        script: |
          rm -rfv "$(Build.SourcesDirectory)/prod-backup"
        workingDirectory: '$(Build.SourcesDirectory)'
        failOnStderr: false

    # Install IntuneCD
    # https://github.com/almenscorner/IntuneCD
    - task: Bash@3
      displayName: Install IntuneCD
      inputs:
        targetType: 'inline'
        script: |
          pip3 install IntuneCD
        workingDirectory: '$(Build.SourcesDirectory)'
        failOnStderr: true

    # Backup the latest configuration, using the current directory
    - task: Bash@3
      displayName: IntuneCD backup
      inputs:
        targetType: 'inline'
        script: |
          mkdir -p "$(Build.SourcesDirectory)/prod-backup"
          IntuneCD-startbackup \
              --mode=1 \
              --output=json \
              --path="$(Build.SourcesDirectory)/prod-backup" \
              --exclude CompliancePartner \
              --ignore-omasettings \
              --autopilot \
              --audit
        workingDirectory: '$(Build.SourcesDirectory)'
        failOnStderr: true
      env:
        TENANT_NAME: $(TENANT_NAME)
        CLIENT_ID: $(CLIENT_ID)
        CLIENT_SECRET: $(CLIENT_SECRET)

    # Commit changes and push to repo
    - task: Bash@3
      displayName: Commit changes
      name: commitAndsetVariable
      inputs:
        targetType: 'inline'
        script: |
          DATEF=`date +%Y.%m.%d`
          git add --all
          # modified files in folder prod-backup
          var=$(git diff --name-only --staged -- prod-backup)
          echo "##vso[task.setVariable variable=CHANGE_DETECTED;isOutput=true;]$var"
          git commit -m "Intune config backup $DATEF"
          git push origin HEAD:main
        workingDirectory: '$(Build.SourcesDirectory)'
        failOnStderr: false

    # Create markdown documentation
    # Install IntuneCD
    # https://github.com/almenscorner/IntuneCD
    - task: Bash@3
      displayName: Generate markdown document
      inputs:
        targetType: 'inline'
        script: |
          if [ ! -z "$(commitAndsetVariable.CHANGE_DETECTED)" ]
          then
            INTRO="Intune backup and documentation generated at $(Build.Repository.Uri) <img align=\"right\" width=\"96\" height=\"96\" src=\"./logo.png\">"
            IntuneCD-startdocumentation \
                --path="$(Build.SourcesDirectory)/prod-backup" \
                --outpath="$(Build.SourcesDirectory)/prod-as-built.md" \
                --tenantname=$TENANT_NAME \
                --intro="$INTRO" \
                --split
          else
            echo "no configuration backup change detected in the last commit, documentation will not be created"
          fi
        workingDirectory: '$(Build.SourcesDirectory)'
        failOnStderr: true
      env:
        TENANT_NAME: $(TENANT_NAME)

    # Commit changes and push to repo
    - task: Bash@3
      displayName: Commit changes
      inputs:
        targetType: 'inline'
        script: |
          DATEF=`date +%Y.%m.%d`
          git add --all
          git commit -m "Intune config as-built $DATEF"
          git push origin HEAD:main
        workingDirectory: '$(Build.SourcesDirectory)'
        failOnStderr: false

  - job: tag
    displayName: Tag repo
    dependsOn: backup_document
    condition: and(succeeded(), ne(dependencies.backup_document.outputs['commitAndsetVariable.CHANGE_DETECTED'], ''))
    pool:
      vmImage: ubuntu-latest
    continueOnError: false
    steps:
    - checkout: self
      persistCredentials: true

    # Set git global settings
    - task: Bash@3
      displayName: Configure Git
      inputs:
        targetType: 'inline'
        script: |
          git config --global user.name $(USER_NAME)
          git config --global user.email $(USER_EMAIL)
        workingDirectory: '$(Build.SourcesDirectory)'
        failOnStderr: true

    - task: Bash@3
      displayName: Pull origin
      inputs:
        targetType: 'inline'
        script: |
          git pull origin main
        workingDirectory: '$(Build.SourcesDirectory)'
        failOnStderr: false

    - task: PowerShell@2
      displayName: Git tag
      inputs:
        targetType: 'inline'
        script: |
          # change in configuration backup folder detected, create TAG
          $DATEF= Get-Date -format 'yyyy.MM.dd_HH.mm'
          git tag -a "v$DATEF" -m "Microsoft Intune configuration snapshot $DATEF"
          git push origin "v$DATEF" *> $null # even status information goes to stderr :(
        failOnStderr: true
        pwsh: false
        workingDirectory: '$(Build.SourcesDirectory)'

  - job: publish
    displayName: Publish as-built artefacts
    dependsOn: tag
    condition: and(succeeded(), ne(dependencies.backup_document.outputs['commitAndsetVariable.CHANGE_DETECTED'], ''))
    pool:
      vmImage: ubuntu-latest
    continueOnError: false
    steps:
    - checkout: self
      persistCredentials: true

    # Install md-to-pdf
    # https://github.com/simonhaenisch/md-to-pdf
    - task: Bash@3
      displayName: Install md-to-pdf
      inputs:
        targetType: 'inline'
        script: |
          npm i --location=global md-to-pdf
        workingDirectory: '$(Build.SourcesDirectory)'
        failOnStderr: true

    # Convert markdown document to HTML
    - task: Bash@3
      displayName: Convert markdown to HTML
      inputs:
        targetType: 'inline'
        script: |
          cat "$(Build.SourcesDirectory)/prod-as-built.md" | md-to-pdf --config-file "$(Build.SourcesDirectory)/md2pdf/htmlconfig.json" --as-html > "$(Build.SourcesDirectory)/prod-as-built.html"
        workingDirectory: '$(Build.SourcesDirectory)'
        failOnStderr: false

    - task: PublishBuildArtifacts@1
      inputs:
        pathToPublish: "$(Build.SourcesDirectory)/prod-as-built.html"
        artifactName: "prod-as-built.html"

    # Convert markdown document to PDF
    - task: Bash@3
      displayName: Convert markdown to PDF
      inputs:
        targetType: 'inline'
        script: |
          cat "$(Build.SourcesDirectory)/prod-as-built.md" | md-to-pdf --config-file "$(Build.SourcesDirectory)/md2pdf/pdfconfig.json" > "$(Build.SourcesDirectory)/prod-as-built.pdf"
        workingDirectory: '$(Build.SourcesDirectory)'
        failOnStderr: false

    - task: PublishBuildArtifacts@1
      inputs:
        pathToPublish: "$(Build.SourcesDirectory)/prod-as-built.pdf"
        artifactName: "prod-as-built.pdf"

No more errors by removing this parameter: --autopilot

The --autopilot command doesn't really have anything to do with the PDF generation, what is in your pdfconfig.json?
I have also seen timeouts in the PDF generation even if the timeout is configured to 0 in puppeteer, unfortunately out of IntuenCD's control.

The pdfconfig.json is used to configure how the output PDF will be formatted as well as some puppeteer configurations, according to your pipeline, it should be located in the $(Build.SourcesDirectory)/md2pdf/pdfconfig.json path.
If you are encountering puppeteer timeout issues like it seems you are, you can add a configuration to this file to disable the timeout.

The problem seems to be resolved after adding the md2pdf folder (and the pdfconfig.json file) to my repository.
Thank you for the help and this top backup solution :)


CPU Runtime

Hi, I need some Few-Shot-Segmentation model for my Uni project and due to budget can't rent any gpus.
Does this repo support CPU running?

Hi,
Sorry for the reply that probably comes way too late. Unfortunately, this project does not support CPU running :(


chore(master): release 2.0.8

:robot: I have created a release beep boop
2.0.8 (2024-01-02)
Bug Fixes

fetch error not thrown correctly (cbc7778)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/keq-request/keq/releases/tag/v2.0.8 :sunflower:


Product backlog

Allows you to edit existing release plans. DB doesn't update yet though.

I think that after you click the edit button, the create/hide form button should probably not show because it is a little confusing since it seems like the edit and create forms are 2 completely different functions.
Also, when creating/editing a new release plan, I thought we wanted the user stories section to be renamed to product backlog as well.

We are redoing this anyways, so closing this PR.


Do not get double values then clamp to a Int

Not sure what the intentions of using NSUInteger here was but this was causing issues where gifs played very fast.
Reverted NSUInteger back to TimeInterval

@mattt should I be fabs this instead?

Ah, thanks for catching that, @MerinoA. I think I'd started to rewrite the logic to express frame duration in centiseconds, but neglected to revert that once realizing that Core Graphics converted everything to and from NSTimeInterval.
I'll cut a new patch release with this change now.


VeraCode issue in FABByteUtility.m

[REQUIRED] Step 1: Describe your environment

Xcode version: 11.3
Firebase SDK version: 6.13.0
Firebase Component: Fabric (Auth, Core, Database, Firestore, Messaging, Storage, etc)
Component version: 1.10.2
Installation method: CocoaPods

[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
VeraCode has found a low severity issues in Fabric/Base/Fabric/Settings/Utilities/FABByteUtility.m , called "Unchecked error condition " and "Use after Free".
Unchecked error condition issue states that return value from malloc() is not been checked before been used in subsequent call.
Use after free issue states that variable reference occurs after its memory allocation has been freed.
Relevant Code:
Unchecked error condition

Fabric/Base/Fabric/Settings/Utilities/FABByteUtility.m [Path 1: FABNSDataPrettyDescription, line 55 (1 step)]

Use after free

Fabric/Base/Fabric/Settings/Utilities/FABByteUtility.m [Path 1: FABNSDataPrettyDescription, line 64 (1 step)]

This issue has been fixed in 4.0.0-beta.2: https://github.com/firebase/firebase-ios-sdk/pull/4669.


parcel/transformer-css: Could not resolve module

Hello, has anyone had this issue before or know a fix?
App runs fine locally, when i try to deploy it i'm getting this issue.
I've tried uninstalling and installing most packages.
`
Error: Could not resolve module
13:04:25.555 | "/vercel/path0/node_modules/lightningcss/lightningcss.linux-x64-gnu.node" from
13:04:25.555 | "/vercel/path0/node_modules/lightningcss/node/index.js"
`

This is from the href right? I am having the same problem

Hi @Dembe7 @kailew
Are you using Netlify as the deploy service?
I triggered a new deploy using Netlify from the master branch and I was able to do it with no issues: https://the-simplefolio.netlify.app/
I see some vercel folders from your error message. Can you me more explicit on what service are you using? maybe there's some missing setup if you are trying to deploy it using Vercel.


Improve SQL Query method in DocumentsManager

Currently we just append sql for the type at the end. Lets actually handle other cases like order by.
sql = sql + " and " + result + "._type = \"" + typeof(T).FullName + "\"";

21bc350 isn't the best solution however it is a big improvement. It's still fragile in edge cases.

Also we should probably split that out into an ISqlParser or something to make it easier for unit tests and in we find a better solution.


fix: revert recursive remove -causing crashes

test sdk_ng

test sdk_ng

I think, i know what causes this.
I removed the test for Span and FormattedString, thinking isDetachedView would handle it.

I have fixed 1.  in https://github.com/NativeScript/NativeScript/pull/7237
However, the issue with the TabView seems more tricky. That's why we decided to revert for now.


PRs? No PRs?

What's the policy here? No preference, just want to know if we should have some ground rules.

heh sorry man, should have pushed all these changes as PRs, just hadn't looked at the project for a while and wanted to get back in an crank some stuff out. I think that we should have PRs, makes this more open to discussion. I'll refrain from just pushing to master in future :)


Flying through dense obstacles

1.adjust pixel_size in Line 664 local_map_publisher.py ( 0.1m )
2. Change the safety distance radius in Line 238 in local_map_publisher.py (0.6)
3.adjust the global map resolution in the launch file Line 33(0.1)
note:The aircraft will stagnate in some places, probably because the RRT star algorithm takes too long to calculate

Sorry for asking but I can't seem to find the changes you made for placing the local_map under the actual obstacle position again?

Hi Lars-Ki，As you said, when I only adjust the above three parameters, the  occupied cells are  underneath the actual obstacles .

This is the previous image

I am ready to verify other path planning algorithms based on your open source code. When I finish this work, I will share my code and create a merge request or a new branch。Because I'm not very familiar with Python and ROS, this job may take a long time。
Thanks


Improve IovReader/IovWriter achitecture

Dependencies
The currently documented way to create an IovReader is complicated:
const knownChains = await withConnectors([await bnsConnector("ws://localhost:22345")]);
// reader is already there: knownChains[0].client, no writer required

const writer = new IovWriter(profile, knownChains);
const chainId = writer.chainIds()[0];
const reader = writer.reader(chainId);

So that the moment we need a reader to make a writer but need a writer to make a reader.
IovReader is responsible for writing to the blockchain
The term "reader" is irritating as IovReader is not only reading from the blockchain but also write signed transactions to it. It serves more as a networking component.
This becomes important when thinking about disconnect(). Right now, in order to disconnect a writer, you need to disconnect all the readers and as soon as you disconnect a reader, the writer does not work anymore. This behavior would make more sense, if it was clear, that IovReader is IovWriter's networking component.

The uglyness commented on above was fixed with #323
The naming clarity part is still outstanding.
I would suggest IovReader -> ChainConnection or BcpConnection or something similar
IovWriter is a multi-chain signer. If we look at the separation of components in #301, we consider when this is out of process (eg. in extension, mobile phone), and the client using the IovWriter would maintain it's own set of Connections for queries.
I would also suggest naming the concrete class IovWriter -> MultiChainSigner or such, and defining an interface (with chainId(), but without getReader() functionality) that can refer to the in-process or out of process key management and transaction signing portion.
Maybe Wallet?
In short, my suggestion:

IovReader interface -> BcpConnection (or similar)
IovWriter concrete class -> MultiChainSigner (with a disconnect that handles all connections)
MultiChainSigner implementes newWallet interface, which we use in all the signing code. This Wallet does the signing can asks for user-approval, designed for the case where the TransactionRequest and the private key management are performed by different processes.

From my point of view, this issue is mostly done. The current usage is much simpler and consistent
const writer = new IovWriter(profile);
await writer.addChain(bnsConnector("ws://localhost:22345"));
const chainId = writer.chainIds()[0];
const connection = writer.reader(chainId); // a BCP connection

I'd just rename the getter reader(chainId: ChainId): BcpConnection to connection(chainId: ChainId): BcpConnection before closing.

I agree on that rename.
I would also like to rename IovWriter to something nicer.
Since Wallet is taken, I gotta dream again...
Authenticator? Signer? Bank?
Please give me a good name. This is something we will also want to connect with out-of-process to handle private keys and signing material. In that case, we won't expose the connection() over the wire.
I mean I think IovWriter should implement an interface that explains the above concept. And then have a name to match the interface name (like Local*, Embedded*, etc.)

I can live with IovWriter for now until we find a natural fit. It is unique and not misleading. From the ideas that exist now, I like MultiChainSigner most.

MultiChainSigner seems pretty good and explicit about what it does. I like it.

This can be closed now, only remaining task is it's own issue #416


Error in sp_updateextendedproperty when adding field comments

What steps will reproduce the problem?
$this->createTable('MY_TABLE', [
            'name' => $this->string(32)->notNull()
                ->comment('An unique name for this group like group_fisc or group_cash'),
...

Results in
*** applying m181009_061513_modarq_init
    > create table MY_TABLE ...Exception: SQLSTATE[42000]: [Microsoft][ODBC Driver 13 for SQL Server][SQL Server]
An invalid parameter or option was specified for procedure 'sp_updateextendedproperty'.
The SQL being executed was:
sp_updateextendedproperty @name = N'MS_Description',
@value = 'An unique name for this group like group_fisc or group_cash',
@level1type = N'Table',  @level1name = [MY_TABLE],
@level2type = N'Column', @level2name = [name] (C:\Users\...\vendor\yiisoft\yii2\db\Schema.php:664)

Additional info

Q
A

Yii version
<IP_ADDRESS>

PHP version
7.1

SQL Server
13.0

Operating system
Win10 64

I am tracing this again.
Till now I found MSSQL has two functions: sp_updateextendedproperty and sp_addextendedproperty.
I can test wether the description already exists before update or add a description. After add the description an update doesn't generate any errors.
Hope to make a PR next weeks, according to my free time.

@samdark I would appreciate your help in a question.
This would be the new mssql\QueryBuilder::addCommentOnTable() method:
    public function addCommentOnTable($table, $comment)
    {
        $schemaName = $this->db->schema->defaultSchema;
        $comment = $this->db->quoteValue($comment);

        return <<< SQL
        -- Maybe we can simplify this later
        IF
            NOT EXISTS (
                SELECT 1
                FROM fn_listextendedproperty (
                    NULL,
                    'SCHEMA', N'$schemaName',
                    'TABLE', N'$table',
                    null, null
                )
            )
        BEGIN
            EXEC sys.sp_addextendedproperty
                @name = N'MS_description',
                @value = $comment,
                @level0type = N'SCHEMA', @level0name = N'$schemaName',
                @level1type = N'TABLE', @level1name = N'$table';
        END
        ELSE
        BEGIN
            EXEC sys.sp_updateextendedproperty
                @name = N'MS_description',
                @value = $comment,
                @level0type = N'SCHEMA', @level0name = N'$schemaName',
                @level1type = N'TABLE', @level1name = N'$table';
        END
        GO
SQL;
    }

Instead of:
    public function addCommentOnTable($table, $comment)
    {
        return "sp_updateextendedproperty @name = N'MS_Description', @value = {$this->db->quoteValue($comment)}, @level1type = N'Table',  @level1name = {$this->db->quoteTableName($table)}";
    }

In my tests, sp_(whatever)extendedproperty() will not work without schema name. But the mssql\Schema\defaultSchema defaults to null. So, if schema name is not provided, this will generate an error. Should the docs be updated about it or do you see some other way?

Is it possible to get the name of default schema?

I tryed to found that yesterday but I could not. Today I found :unamused:
The sql will be a bit longer yet (MS way to make things simple!)

I managed to fix this issue. But I found similar problems in dropCommentFromColumn|Table() that I will fix too (unless I need open a new issue... but i think not).

I will provide tests too.


MLP implementation

This is an outdated PR, but I implemented most of your suggestions. The finalized MLP needs to implement batched GEMM, which I'm still waiting to be fully finished and pushed. The part that isn't finished is listed here in a comment in the batched gemm pim file:
// Concatenate matrices. Needs to be done once
std::vector<std::vector> batchedSrcMatA;
for (uint64_t i = 0; i < colA; ++i)
{
std::vector temp;
for (uint64_t j = 0; j < batchSize; ++j) {
// TODO: Add replicate a pattern API in the simulator
for (uint64_t k = 0; k < row; ++k) {
temp.push_back(srcMatrixAT[i][k]);
}
}
batchedSrcMatA.push_back(temp);
}


Android Build failure

Hi,
I tried to use the package in my flutter app to scan simple barcode, however as soon as I have added the package and method to scan the bar code, the application is giving build failure.
For android, I went through the suggested article about Dex, and was able to resolve the error by setting the minSdkVersion to 21
I have not yet built the application for iOS, but I am curious if similar build failure may occur for iOS.
Please suggest and also if possible could you please improve the package so that it no more gives build failure irrespective of SdkVersion.
Below is the failure log :
Launching lib/main.dart on <DeviceName> in debug mode...
 lib/main.dart
D8: Cannot fit requested classes in a single dex file (# methods: 69638 > 65536)
com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives:
The number of method references in a .dex file cannot exceed 64K.
Learn how to resolve this issue at https://developer.android.com/tools/building/multidex.html
	at com.android.builder.dexing.D8DexArchiveMerger.getExceptionToRethrow(D8DexArchiveMerger.java:131)
	at com.android.builder.dexing.D8DexArchiveMerger.mergeDexArchives(D8DexArchiveMerger.java:118)
	at com.android.build.gradle.internal.transforms.DexMergerTransformCallable.call(DexMergerTransformCallable.java:102)
	at com.android.build.gradle.internal.tasks.DexMergingTaskRunnable.run(DexMergingTask.kt:444)
	at com.android.build.gradle.internal.tasks.Workers$ActionFacade.run(Workers.kt:335)
	at org.gradle.workers.internal.AdapterWorkAction.execute(AdapterWorkAction.java:50)
	at org.gradle.workers.internal.DefaultWorkerServer.execute(DefaultWorkerServer.java:47)
	at org.gradle.workers.internal.NoIsolationWorkerFactory$1$1$1.create(NoIsolationWorkerFactory.java:65)
	at org.gradle.workers.internal.NoIsolationWorkerFactory$1$1$1.create(NoIsolationWorkerFactory.java:61)
	at org.gradle.internal.classloader.ClassLoaderUtils.executeInClassloader(ClassLoaderUtils.java:98)
	at org.gradle.workers.internal.NoIsolationWorkerFactory$1$1.execute(NoIsolationWorkerFactory.java:61)
	at org.gradle.workers.internal.AbstractWorker$1.call(AbstractWorker.java:44)
	at org.gradle.workers.internal.AbstractWorker$1.call(AbstractWorker.java:41)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:416)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$CallableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:406)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor$1.execute(DefaultBuildOperationExecutor.java:165)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:250)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:158)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:102)
	at org.gradle.internal.operations.DelegatingBuildOperationExecutor.call(DelegatingBuildOperationExecutor.java:36)
	at org.gradle.workers.internal.AbstractWorker.executeWrappedInBuildOperation(AbstractWorker.java:41)
	at org.gradle.workers.internal.NoIsolationWorkerFactory$1.execute(NoIsolationWorkerFactory.java:56)
	at org.gradle.workers.internal.DefaultWorkerExecutor$3.call(DefaultWorkerExecutor.java:215)
	at org.gradle.workers.internal.DefaultWorkerExecutor$3.call(DefaultWorkerExecutor.java:210)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.runExecution(DefaultConditionalExecutionQueue.java:215)
	at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.runBatch(DefaultConditionalExecutionQueue.java:164)
	at org.gradle.internal.work.DefaultConditionalExecutionQueue$ExecutionRunner.run(DefaultConditionalExecutionQueue.java:131)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
	at java.lang.Thread.run(Thread.java:748)
Caused by: com.android.tools.r8.CompilationFailedException: Compilation failed to complete
	at com.android.tools.r8.utils.t.a(:55)
	at com.android.tools.r8.D8.run(:11)
	at com.android.builder.dexing.D8DexArchiveMerger.mergeDexArchives(D8DexArchiveMerger.java:116)
	... 34 more
Caused by: com.android.tools.r8.utils.AbortException: Error: null, Cannot fit requested classes in a single dex file (# methods: 69638 > 65536)
	at com.android.tools.r8.utils.Reporter.a(:21)
	at com.android.tools.r8.utils.Reporter.a(:7)
	at com.android.tools.r8.dex.VirtualFile.a(:33)
	at com.android.tools.r8.dex.VirtualFile$h.a(:5)
	at com.android.tools.r8.dex.ApplicationWriter.a(:13)
	at com.android.tools.r8.dex.ApplicationWriter.write(:35)
	at com.android.tools.r8.D8.d(:44)
	at com.android.tools.r8.D8.b(:1)
	at com.android.tools.r8.utils.t.a(:23)
	... 36 more

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:mergeDexDebug'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
   > com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives:
     The number of method references in a .dex file cannot exceed 64K.
     Learn how to resolve this issue at https://developer.android.com/tools/building/multidex.html

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 20s
[!] The shrinker may have failed to optimize the Java bytecode.
    To disable the shrinker, pass the `--no-shrink` flag to this command.
    To learn more, see: https://developer.android.com/studio/build/shrink-code
Exception: Gradle task assembleDebug failed with exit code 1
Exited (sigterm)

I had this issue and to solve this, I added multiDexEnabled: true in /android/app/build.gradle. Like this:
defaultConfig {
...
minSdkVersion 16
targetSdkVersion 29
multiDexEnabled true
}
It works for me.

Hey,
is here any workaround to solve this problem?

Try to enable multidex:
flutter run --multidex or flutter build --multidex


Feat/rev string

Added a "Reverse a string" challenge.
Includes a couple of very simple tests.
The contributing guidelines were very clear and easy to follow! I would, however, appreciate any feedback on things I may have missed or done incorrectly.

@garroadran this looks perfect, thanks! You hit all the points including adding the solution to the app tests (and the solution you chose is a great one).
Great job, and thanks for pitching in! Unfortunately it doesn't seem like the post on FCC is getting a lot of love, but I still hope to make something out of this and every bit of help counts 👍
Feel free to keep the project in mind if you ever have some free time to contribute some more, or if you know of anyone else who might like to get some open source contributions under their belt!

working towards #19


Python SDK incompatible with old GLIBC

In short
The Rerun Python SDK is incompatible with GLIBC 2.17, and therefore CentOS 7.
I don't know what is our minimum required GLIBC version.
Problem
A user reported trying to use the Rerun Python SDK in a university cluster running CentOS 7, which uses GLIBC 2.17 (released 2012-12-25). The result:

ERROR: Could not find a version that satisfies the requirement rerun-sdk (from versions: none)

The user further reports:

I see that the wheel file on PyPy specifies the platform tag manylinux_2_31 which  is incompatible with my GLIBC version (2.17)

Solution
I think the solution is building the wheels on a machine with an old glibc version.
There are some clues here:

https://kobzol.github.io/rust/ci/2021/05/07/building-rust-binaries-in-ci-that-work-with-older-glibc.html
https://github.com/explosion/tokenizations/pull/7

We should at least try, and we should also figure out what is the exact minimum GLIBC version required by the Rerun Python SDK.

Hi,
I'm the user who originally created this issue.
My university cluster was updated to CentOS 8 finally but our GLIBC is still only 2.28. I'd really like to try out your tool so I'm wondering if there's any progress on this?

@nchodosh when we tried to do this before we ran into some issues with build environments that were old enough to include the older glibc not having access to a recent enough libgtk3.
However, I just found out that the packages we build for conda-forge are built using an older glibc that should be compatible with centos8.
Is there any possibility you could use the Conda package instead of the pypi wheel?

Ubuntu 18 is still stuck at glibc 2.28 (2.27?), can we get this on pip? Don't like conda installs.

My university cluster was updated to CentOS 8 finally but our GLIBC is still only 2.28. I

Exactly my situation as well.

Same here; our cluster is still on CentOS 7.
I'd imagine that most users on very old glibc versions (maybe not Ubuntu 18, but likely CentOS 7) care less about display support, especially given the excellent support for streaming w/re-run, if that makes things any easier!

We actually made some good progress on this recently. The viewer is no longer linked into the wheel .so. Instead we bundle a separately built rerun executable which we launch via subprocess. This means these deps shouldn't be necessary for building the wheel anymore.
I think this makes it possible to try moving the wheel-building environment to a manylinux container with an older glibc. I'll try taking a look at this again sometime soon.

I noticed that our latest 0.17.0 wheels (linux x86) affectively use 2.29 max. We should consider advertising that version instead of 2.31 as we currently do.
~/Downloads/rerun_sdk-0.17.0-cp38-abi3-manylinux_2_31_x86_64.whl
❯ greadelf -W -s rerun_sdk/rerun_cli/rerun  |  rg -o<EMAIL_ADDRESS>| awk '{freq[$0]++} END {for (x in freq) print x, freq[x]}'
@GLIBC_2.2.5 345
@GLIBC_2.3.2 8
@GLIBC_2.3.4 8
@GLIBC_2.25 2
@GLIBC_2.3 4
@GLIBC_2.4 10
@GLIBC_2.27 12
@GLIBC_2.28 2
@GLIBC_2.7 2
@GLIBC_2.29 12
@GLIBC_2.8 2
@GLIBC_2.9 2
@GLIBC_2.10 2
@GLIBC_2.12 2
@GLIBC_2.14 2
@GLIBC_2.15 2
@GLIBC_2.17 2
@GLIBC_2.18 2

~/Downloads/rerun_sdk-0.17.0-cp38-abi3-manylinux_2_31_x86_64.whl
❯ greadelf -W -s rerun_bindings/rerun_bindings.abi3.so  |  rg -o<EMAIL_ADDRESS>| awk '{freq[$0]++} END {for (x in freq) print x, freq[x]}'
@GLIBC_2.2.5 241
@GLIBC_2.3.2 8
@GLIBC_2.3.4 8
@GLIBC_2.3 4
@GLIBC_2.25 2
@GLIBC_2.4 4
@GLIBC_2.28 2
@GLIBC_2.7 2
@GLIBC_2.29 2
@GLIBC_2.8 2
@GLIBC_2.9 2
@GLIBC_2.10 2
@GLIBC_2.12 2
@GLIBC_2.14 2
@GLIBC_2.15 2
@GLIBC_2.17 2
@GLIBC_2.18 2

Related: https://github.com/corsix/polyfill-glibc

We should be compatible with any glibc 2.17+, see:

https://blog.rust-lang.org/2022/08/01/Increasing-glibc-kernel-requirements.html
https://github.com/rerun-io/rerun/issues/7788
https://github.com/rerun-io/cpp-example-vrs/pull/15


feat: CategoryBar now supports values more than 100 or less than 100 (while more than 1)

Description
This pull request brings the CategoryBar component to support values with any sum, whereas the previous one required the values sum to be exactly 1 or 100.
By dynamically normalizing the input values to represent each category proportionally, regardless of the total, this enhancement increases flexibility and applicability in a variety of data environments. Additional unit tests ensure proper functioning in a variety of situations.

Related issue(s)
#1035

What kind of change does this PR introduce? (check at least one)

[x] Bug fix (non-breaking change which fixes an issue)
[x] New Feature (non-breaking change which adds functionality)
[ ] New Feature (BREAKING CHANGE which adds functionality)
[ ] Refactor
[ ] Build-related changes
[x] Other, please describe: typo fix

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
How has this been tested?

I have added unit test in src/tests/vis-elements/CategoryBar.test.tsx via jest and it passes all the tests.
I have added two storybook examples in src/stories/vis-elements/CategoryBar.stories.tsx and it works as expected.

You may visit the following link to learn about storybook:
With Values More Than 100 (https://tremor-storybook-git-fork-lcandy2-main-tremor.vercel.app/?path=/story/visualizations-vis-categorybar--with-values-more-than-100)
With Values Less Than 100 (https://tremor-storybook-git-fork-lcandy2-main-tremor.vercel.app/?path=/story/visualizations-vis-categorybar--with-values-more-than-100)
Screenshots (if appropriate):
The screenshot values sum more than 100 (live):

The screenshot values sum less than 100 (more than 1) (live):

The PR fulfils these requirements:

[x] It's submitted to the main branch
[x] When resolving a specific issue, it's referenced in the related issue section above
[x] My change requires a change to the documentation. (Managed by Tremor Team)
[x] I have added tests to cover my changes
[x] Check the "Allow edits from maintainers" option while creating your PR.
[x] Add refs #XXX or fixes #XXX to the related issue section if your PR refers to or fixes an issue.
[x] By contributing to Tremor, you confirm that you have read and agreed to Tremor's CONTRIBUTING.md guideline. You also agree that your contributions will be licensed under the Apache License 2.0 license.

Good stuff! Thank you @lcandy2 for this contribution. Planned for v3.17.


[CAFV-38] Remove hardcoded main-branch from building images and include infrastructure-components.yaml in image building

Description
Please provide a brief description of the changes proposed in this Pull Request

Remove hardcoded main-branch from building images and include infrastructure-components.yaml in image building

Checklist

[x] tested locally
[ ] updated any relevant dependencies
[ ] updated any relevant documentation or examples

API Changes
Are there API changes?

[ ] Yes
[x] No

If yes, please fill in the below

Updated conversions?

[ ] Yes
[ ] No
[ ] N/A

Updated CRDs?

[ ] Yes
[ ] No
[ ] N/A

Updated infrastructure-components.yaml?

[ ] Yes
[ ] No
[ ] N/A

Updated ./examples/capi-quickstart.yaml?

[ ] Yes
[ ] No
[ ] N/A

Updated necessary files under ./infrastructure-vcd/v1.0.0/?

[ ] Yes
[ ] No
[ ] N/A

Issue
If applicable, please reference the relevant issue
Fixes #

This change is

This looks good to me


Custom titlebar cannot be dragged with fingers

Describe the bug
My code is as follows
tauri.conf.json
`
"windows": [
{
"decorations": false,
"title": "渔田自助机",
"width": 800,
"height": 600,
"transparent": true
}
],
"window": {
    "all": false,
    "close": true,
    "hide": true,
    "show": true,
    "maximize": true,
    "minimize": true,
    "unmaximize": true,
    "unminimize": true,
    "startDragging": true
  }

My Components

`
Using a mouse is normal, but there is no response when using fingers. Clicking and double clicking on the toolbar are both normal. Simply dragging with fingers without any response; I changed it to "decorations": true. Fingers are normal and can be dragged. Why is this?
使用鼠标是正常的，但是使用手指没有反应，点击和双击tablebar都是正常的。仅仅是手指拖动无反应；我修改为 "decorations": true,手指是正常的，可以手指拖动，这是为什么？
Reproduction
Using a mouse is normal, but there is no response when using fingers. Clicking and double clicking on the toolbar are both normal. Simply dragging with fingers without any response; I changed it to "decorations": true. Fingers are normal and can be dragged. Why is this?
使用鼠标是正常的，但是使用手指没有反应，点击和双击tablebar都是正常的。仅仅是手指拖动无反应；我修改为 "decorations": true,手指是正常的，可以手指拖动，这是为什么？
Expected behavior
Using a mouse is normal, but there is no response when using fingers. Clicking and double clicking on the toolbar are both normal. Simply dragging with fingers without any response; I changed it to "decorations": true. Fingers are normal and can be dragged. Why is this?
使用鼠标是正常的，但是使用手指没有反应，点击和双击tablebar都是正常的。仅仅是手指拖动无反应；我修改为 "decorations": true,手指是正常的，可以手指拖动，这是为什么？
Full tauri info output
[✔] Environment
    - OS: Windows 10.0.22631 X64
    ✔ WebView2: 122.0.2365.92
    ✔ MSVC: Visual Studio ���ɹ��� 2022
    ✔ rustc: 1.76.0 (07dca489a 2024-02-04)
    ✔ cargo: 1.76.0 (c84b36747 2024-01-18)
    ✔ rustup: 1.27.0 (bbb9276d2 2024-03-08)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 20.11.0
    - pnpm: 8.15.4
    - yarn: 1.22.21
    - npm: 10.2.4

[-] Packages
    - tauri [RUST]: 1.6.1
    - tauri-build [RUST]: 1.5.1
    - wry [RUST]: 0.24.7
    - tao [RUST]: 0.16.7
    - @tauri-apps/api [NPM]: 1.5.3
    - @tauri-apps/cli [NPM]: 1.5.11

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite

Stack trace
No response
Additional context
No response

duplicate of https://github.com/tauri-apps/tauri/issues/4746


Missing OpenAPI path: /users/{user-id}/chats/getAllMessages

The converted OpenAPI document is missing /users/{user-id}/chats/getAllMessages in beta. See https://docs.microsoft.com/en-us/graph/api/chats-getallmessages?view=graph-rest-beta.
AB#8760

We are also missing permissions navigation property under driveItem e.g. drives/{drive-id}/items/{item-id}/permissions. See https://docs.microsoft.com/en-us/graph/api/driveitem-list-permissions?view=graph-rest-1.0&tabs=http.

We are missing the following paths as well. These are navigation properties of deviceManagement.

/deviceManagement/configurationSettings -> https://docs.microsoft.com/en-us/graph/api/resources/intune-deviceconfigv2-devicemanagementconfigurationsettingdefinition?view=graph-rest-beta.
/deviceManagement/configurationPolicies -> https://docs.microsoft.com/en-us/graph/api/resources/intune-deviceconfigv2-devicemanagementconfigurationsetting?view=graph-rest-beta.

Also missing:

/users/{id | user-principal-name}/informationProtection/policy/labels -> https://docs.microsoft.com/en-us/graph/api/informationprotectionpolicy-list-labels?view=graph-rest-beta&tabs=http#http-request


[Logging v2] enabling control plane nodes in Airgap setup I ended up with error on the additionalLoggingResources configcheck workload

What kind of request is this:
bug
Steps to reproduce:

Install Rancher v2.5.0-alpha4 single node Airgap
In the local cluster (k3s) go to Dashboard
Install the rancher-logging app enabling the Control Plane Logs chart option.

Result:

rancher-logging gets installed but the additionalLoggingResource has a configcheck issue and workloads are not created

Seems like the workloads are trying to pull a newer image from upstream banzaicloud/fluentd:v1.11.2-alpine-3
ImagePullBackOff: Back-off pulling image "banzaicloud/fluentd:v1.11.2-alpine-3"
rancher-images.txt only lists rancher/banzaicloud-fluentd:v1.11.2-alpine-2
Other details that may be helpful:
Environment information

Rancher version: v2.5.0-alpha4
Installation option: Single Rancher Airgap

https://github.com/rancher/charts/pull/671

Reopening there's a registry issue to be fixed in alpha5 #29026

https://github.com/rancher/charts/pull/691

Rancher version: v2.5.0-rc1
https://github.com/rancher/rancher/issues/29026#issuecomment-698583479
This is now working.


OrderImports with removeUnused=true removes types+annotations used in record components

I've created this config
---
type: specs.openrewrite.org/v1beta/recipe
name: com.fprochazka.Experiments
recipeList:
  - org.openrewrite.java.OrderImports:
      removeUnused: true

and then executed that over my project that uses a lot of records. It removed every import, that was used within a file only in record components.

@fprochazka Thanks for the detailed report! A fix has been integrated and will be available in the next release (and the next SNAPSHOT build).


feat(deploys): add deploy_now, deployed attributes and POST /v2/apps/example-go/releases/deploy/

Related to https://github.com/deis/controller/pull/1269

A good example is https://deis.com/docs/workflow/applications/managing-app-configuration/#custom-health-checks.

@bacongobbler Added some documentation. English is not my primary language, so might need some adjustments.

These PRs haven't been updated in a few months. @kwent I'm going to close this, but please re-open if you can address the remaining issues, and thanks again!


Improve the repo README.md with info on how to use the plugin.

Mr. @delphyne Please add "How to"!
Thanks!!

done. let me know if you have questions.


Added code to display battery percentage and resolution in termux on android devices

Description
Only fill in the fields below if relevant.
Features: Added code to display battery percentage and resolution in termux
Issues
TODO

Currently code for resolution in termux requires adb to be installed on termux and connected over tcpip.
In future if termux gets a feature to create screenshot, resolution can be obtained by taking screenshot and obtaining size in pixels of that screenshot using imagemagick or other tool, because the resolution of screenshot image is always equal to screen resolution


Forge 1355+ compatibility

I see there was a commit to revert?
https://github.com/aidancbrady/Mekanism/commit/03e45cc40134d2a6a004d8aa594bc5b3ab1be600
Is there a reason not to go to later Forge versions?
The Electrolytic Separator appears to be broken in anything above 1355.

We will update forge in the next week.

Good news, the sooner the better.
Thanks!


Change all cdn.jsdelivr.net links to raw GitHub content links

Note: the following tests were performed after both services fully cached all the files, using Curl and HTTP Debugger.

Results
GitHub
https://raw.githubusercontent.com/FlafyDev/auto-nong-indexes/dist/official.json.gz
1st: 0.014s
2nd: 0.011s
3rd: 0.011s
Avg: 0.012s
https://raw.githubusercontent.com/FlafyDev/auto-nong-indexes/dist/sfh-yt.json.gz
1st: 0.033s
2nd: 0.032s
3rd: 0.031s
Avg: 0.032s
https://raw.githubusercontent.com/FlafyDev/auto-nong-indexes/dist/sfh-rooot.json.gz
1st: 0.041s
2nd: 0.030s
3rd: 0.038s
Avg: 0.036s
https://raw.githubusercontent.com/FlafyDev/auto-nong-indexes/dist/sfh-pingusmc.json.gz
1st: 0.036s
2nd: 0.045s
3rd: 0.034s
Avg: 0.038s
Avg for all: 0.0295s
cdn.jsdelivr.net
<EMAIL_ADDRESS>1st: 0.024s
2nd: 0.021s
3rd: 0.024s
Avg: 0.023s
<EMAIL_ADDRESS>1st: 0.054s
2nd: 0.047s
3rd: 0.043s
Avg: 0.048s
<EMAIL_ADDRESS>1st: 0.053s
2nd: 0.061s
3rd: 0.058s
Avg: 0.057s
<EMAIL_ADDRESS>1st: 0.058s
2nd: 0.050s
3rd: 0.062s
Avg: 0.056s
Avg for all: 0.046s

Using raw GitHub is faster by 0.0165s, and should probably also solve the need to purge the CDN's cache.

I don't want to use GitHub as the CDN.

It's against GitHub's TOS
GitHub might start ratelimiting users if they restart their game/refresh indexes a lot
The auto-nong-indexes repo might get flagged if it's being fetched a lot through raw.githubusercontent.com


Removing a path could lead to duplicated flows.

While exploring from issue #45:

i. Allocate and deallocate many individual vlans on an interface

The issue in failover_path (current_path is similar):

At the start of a failover_path installation, every needed VLAN is removed from the interfaces.
The installation could fail in the middle of sending flows.
E.g:

failover_path = {
"00:00:00:00:00:00:00:01:1",
"00:00:00:00:00:00:00:01:4", "00:00:00:00:00:00:00:03:3",    # Using VLAN 87, correctly installed
"00:00:00:00:00:00:00:03:2", "00:00:00:00:00:00:00:02:3",    # Using VLAN 87, failed installation
"00:00:00:00:00:00:00:02:1"
}

In this case the error was Service Unavailable which also is the error when trying to delete the flows from the paths.
All the VLANs used by the path are freed, code.
Notice that we have 4 switches which VLANs do not match their installed flows:

"00:00:00:00:00:00:00:01:4"     # Freed VLAN 87, Flow was not removed
"00:00:00:00:00:00:00:03:3"     # Freed VLAN 87, Flow was not removed
"00:00:00:00:00:00:00:03:2"     # Freed VLAN 87, Flow was not installed
"00:00:00:00:00:00:00:02:3",    # Freed VLAN 87, Flow was not installed

The next EVC will try its luck with the same VLAN 87 if it successfully installs its failover_path. It will install a flow in the same switch, port and VLAN.

TLDR, when it comes to paths, we create/delete flows by switch but add/delete VLANs by paths. Deleting VLANs by confirmed deleted switch flow could solve this issue :thinking:.

Things to keep in mind:

This issue was discovered when sending 2245 requests to create EVCs in ~7 threads~(turned out I created 2000 threads, thus the Service Unavailable error. Still this error is real.). This issue can be replicated by modifying flow_manager to detect a flow (a second or later addition flow) that is from a first EVC so a leftover installed flow is untouched. Then allowing every flow from a second EVC
The test reproduced Service Unavailable errors from both flow_manager and pathfinder. But, only error from flow_manager is important for this issue.
This issue does not seem critical. In my tests it only produced duplicated flows that would trigger constant consistency checks about a missing flow in a certain switch (related to the fail to remove path).
This error can occur in remove_path_flows and remove_current_flows although it was much more likely in the first in remove_path_flows. In practice I have not noticed an issue in practice with remove_current_flows but the steps for dealing with errors is the same.

Created a not ideal solution. I solves duplicated flows for this case only.

@Alopalao good finding, let's keep this in the backlog, since the service unavailable was due to a very high rate of requests that we don't expect in prod atm. As consistency check gets implemented it can also aid this case, and this one is already in progress, so let's avoid any other adjacent implementation in the meantime here. In the future, we can reassess if we'll augment the error handling part here and consider other adjacent efforts too like replacing requests or not.

@Alopalao can this be closed or was there something remaining to still be mapped and addressed?

This issue can still be present. The solution for this issue is ensure flow installation without errors or allocate/deallocate VLANS by confirmed flow installation/deletion only.

This issue can still be present. The solution for this issue is ensure flow installation without errors or allocate/deallocate VLANS by confirmed flow installation/deletion only.

Right. When you have the chance, let's clarify and map the remaining potential errors that you mean here. Are they the ones related to this issue here https://github.com/kytos-ng/mef_eline/issues/495? If there's anything else let's document in the issue body just so we get back to it later when gets prioritized

Added Possible solutions so it is documented when to close this issue.

With now a single request being sent per path, this issue does not longer exist. This issue can be closed.

Now thinking more about this, if the single request does gets the error Service Unavailable all their VLANS are going to still be freed which results in the same problem


[RESTEASY-1266]

Fixed client side representation of cookies.

Hey Thomas,
Your comment on June 5 put everything in perspective, I think. In particular, I just don't want to change things that aren't clearly broken, at least as far as JAX-RS is concerned. So I've created a new pull request, https://github.com/resteasy/Resteasy/pull/935, which is similar to this one but omits the changes to CookieHeaderDelegate. I'll close this pull request.
Thank you for your help.
-Ron


Change_history_table with hyphens

Hello.
I have a database with a hyphen like this: DATABASE-NAME. For this to work on snowflake I would have to use "DATABASE-NAME"."SCHEMACHANGE" but I can't make the application to grab it.
If I pass it without the quotes, it returns me a syntax error line 1 at position 38 unexpected '-'.
If I pass with the quotes it returns me a
raise ParserError("while parsing a block mapping", self.marks[-1] ...

   change-history-table: "DATABASE-NAME"."SCHEMACHANGE"."CHANGE_HISTORY"

I also tried to manually create the table and then ask to not created when running the application, but then when querying it, it won't find it and returns me the same error. I really would like some insight on how to make this work.
Thank you

This is not a bug


Fails on conversion on certain projects

First, thanks for this action! I’ve been able to use it to get codecov back on repos that use Xcode 13. I’ve found one weird case where it can’t convert the coverage files for the “iOS” project only in the ParseSwift repo. It converts all other OS’s fine. I’ve tried both text and Lcov formats.
There isn’t a lot of console output to debug, but here’s the error https://github.com/parse-community/Parse-Swift/pull/262/checks?check_run_id=3947393464#step:5:23
You can see the PR that runs into the error here: https://github.com/parse-community/Parse-Swift/pull/262
the original PR where I tried the text format is here: https://github.com/parse-community/Parse-Swift/pull/261

Thanks for reporting this!
This is indeed weird - I've never seen this before. And unfortunately, llvm-cov isn't really talkative.
You can try the following two things (one by one):

Add the following step before running the swift-codecov-action (this enables some debug output):- run: echo "RUNNER_DEBUG=1" >> $GITHUB_ENV

Add the following argument to the swift-codecov-action step:with:
    target-name-filter: '^ParseSwift$'

I've noticed that it seems to fail at generating coverage data for the TestHost application. That's why the second step adds a filter.
If these two things don't work let me know. We then need to try to find the cause locally - I'll collect the necessary commands then (after running a build locally).


Triangles

Dear Vincent,
first of all: Thanks a lot for this super cool script!
Is is somehow possible that instead of creating lines between two points to create lines between three points to build a triangle shape that could be filled with a color?
Thanks in advance!

+1

+1

+2

+1

+1

+1

Implemented here https://github.com/matteobruni/tsparticles/pull/315


"DJ info" column is empty in playlists

Hi, first of all, thank you for this very useful extension. However, while the info is visible in the "now-playing" section on the left bottom, I don't see the info visible in the playlist. The column is visible, but empty (see screenshot). Could there be something in the experimental features I have to enable/disable?
Thanks

I recently fixed this bug, at least i thought so. And for me the info is still displayed correctly.
Can you please run spicetify upgrade or spicetify apply to make sure you have the newest version of my extension. Or if you have installed it manually, make sure to replace the old Extension file with the newest one.
You can check if the newest version is used when you go in the menu at the profile picture and when there is a 'year' option in dj info settings, then you have the newest version already installed.
When you have the newest version, but still no info, could you please close spotify and open it again with this command spicetify enable-devtools and then press ctrl + shift + i to open the devtools, then go to the console and look for a red error which is caused by djinfo.js and make a screenshot.

Spotify updated today on my PC and then I had the same issue. Extension is fixed and should now work again!


ss7 knowledge

add me on icq and lets speak about this beauty off ss7 and gsm framwork  usrp is needed its not just about  software 720922345

Please read more about SS7 usrp is needed for different types of attacks
I don’t use icq send me ur email and I will contact y
On Wednesday, 28 March 2018, silverhigh1<EMAIL_ADDRESS>wrote:

add me on icq and lets speak about this beauty off ss7 and gsm framwork
usrp is needed its not just about software 720922345
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/SigPloiter/SigPloit/issues/127, or mute the thread
https://github.com/notifications/unsubscribe-auth/AXXuv4z5QF0sazfBgubRbzVDaNCrW7SJks5tisUBgaJpZM4S9xK2
.

@SigPloiter, what do you recommend as a starting text?

send me ur email and I could send u a few documents
On Wednesday, 28 March 2018, Saulius Krasuckas<EMAIL_ADDRESS>wrote:

@SigPloiter https://github.com/SigPloiter, what do you recommend as a
starting text?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SigPloiter/SigPloit/issues/127#issuecomment-376766082,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXXuv7Hvnq6MqUMceWJNiSY8Tc2n7h6Uks5tix9mgaJpZM4S9xK2
.

add me on icq and we can speak freely and consistently it will benefit both
of us i believe.
720922345
On 28 March 2018 at 11:17, Loay Abdelrazek<EMAIL_ADDRESS>wrote:

send me ur email and I could send u a few documents
On Wednesday, 28 March 2018, Saulius Krasuckas<EMAIL_ADDRESS>wrote:

@SigPloiter https://github.com/SigPloiter, what do you recommend as a
starting text?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/SigPloiter/SigPloit/issues/
127#issuecomment-376766082>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AXXuv7Hvnq6MqUMceWJNiSY8Tc2n7h6Uks5tix9mgaJpZM4S9xK2>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SigPloiter/SigPloit/issues/127#issuecomment-376835833,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AhAhruhv5RQJ_sY5vCPAZ2Q3ORQ8CuvLks5ti2MpgaJpZM4S9xK2
.

Please send me all reading staff related to it. Thanks<EMAIL_ADDRESS>

bro add me on icq andd if u want to thus  discuss this field let me know
720922345
On 30 March 2018 at 00:29, PeaceLover4all<EMAIL_ADDRESS>wrote:

Please send me all reading staff related to it. Thanks
<EMAIL_ADDRESS>—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SigPloiter/SigPloit/issues/127#issuecomment-377402923,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AhAhrrkis4AcSsDLXCJ6sGi1tiOkPrKqks5tjW5jgaJpZM4S9xK2
.


Improvements for Whole

These are a few improvements that I think would be nice to have in the short term for Whole.
I'm not sure about the name for quotientAndRemainder and the method signature inconsistency with Decimal.dividedAndRemainder, but I do think it is an important method to have.

I'm ashamed that this has been rotting for so long. Let me review it now.

If we can reach a consensus on those two points I'm happy to apply this.

What are the two points, and what does modPower() do?

The points I made on the "Files changed" tab: The renaming of powerRemainder to modPower and the name modulo being preferable to mod.

Well I was looking for the nutshell explanation of what they do...

powerRemainder == modPower: "The result of (this**exponent) % modulus."
mod: "The result of this mod modulus. This method differs from [[remainder]] in that the returned value will always be positive."
@jvasileff is also adding quotientAndRemainder: "Returns a pair containing the same results as calling divided() and remainder() with the given argument, except the division is only performed once."

We write (this^exponent)%modulus these days.

@tombentley the consistency was the reason for wanting to rename the function, to avoid confusion with remainder. From the commit:

The method name powerRemainder was misleading as it implied behavior similar to "remainder", where the result is always of the same sign as the dividend, rather than "mod", where the result is always positive.
powerRemainder/modPower always returns a positive value (or zero):

wholeNumber(5).remainder(wholeNumber(3));     // 2
wholeNumber(5).modPower(one, wholeNumber(3)); // 2

wholeNumber(-5).remainder(wholeNumber(3));     // -2
wholeNumber(-5).modPower(one, wholeNumber(3)); //  1

Or what I just tested prior to seeing that I had ^that:
    Whole minusThree = wholeNumber(-3);
    Whole three = wholeNumber(3);
    Whole twentySix = wholeNumber(26);
    print(minusThree.powerRemainder(three, twentySix));  // (-3)^3 mod 26 = 25
    print(minusThree.power(three).remainder(twentySix)); // (-3)^3 % 26   = -1

For naming, we need to consider these as a group:

Placeholder Name
Description

remainder(m)
result of modulo operation, possibly negative

mod(m)
result of modulo operation, always positive

modPower(e,m)
power followed by mod: this^e mod m

modInverse(m)
modPower(-1, x), if that were legal: this^(-1) mod m

I suppose modulo and powerModulo would work (although I think slightly confusing to deviate from the standard for the more technical modPower operation), but what about modInverse? Just moduloInverse?
Note: we don't have a modInverse function yet, but my opinion when I was working on this stuff is that we would want to once we go with a ceylon impl. It exists in my xmath module.

Sorry if I'm being dense, but I don't see how — having made a distinction between remainder and mod — the situation is helped by having powerRemainder delegate to modPower. Surely we should also fix powerRemainder so that it is consistent with remainder.
It sounds like we should consider having a modulo method on Integer or even on Integral.

Surely we should also fix powerRemainder so that it is consistent with remainder.

Then we'd also need powerModulo, since that is what everyone's algorithms use. And I'm not sure if anyone would ever need powerRemainder, but I could be wrong on that.

powerRemainder delegate to modPower

I was thinking we'd get rid of powerRemainder in 1.3. But at least the deprecated warning in 1.2 should signal to users that it may not do what they expect.

powerModulo is different from modPower?

No, same thing (sorry, I should have stuck with the placeholder name :smile:)
So, you're proposing having both?
My only concerns in all of this are:

Avoid confusion with the name remainder
At least offer modPower, since that's what people need

OK, I finally understand! I suppose I agree then that we should:

deprecate powerRemainder and plan to remove it later, since it's a bit broken and
add moduloPower (or powerModulo which I sort of prefer as a name because it gives me a hint that we do the power first and then the mod).
Rename mod to modulo

Ok, I renamed the methods to modulo and moduloPower. I went with moduloPower since I think moduloInverse will be better than inverseModulo, where 'inverse' reads much more like an adjective. But it's easy enough to change again if you decide we should have powerModulo.

Aside from the docs commit, those are the only changes. It's too bad that the GH interface doesn't show that the merge was clean. Maybe I prefer rebases for this.

Thanks @jvasileff, we got there in the end :-)

Great, thanks @tombentley!

Thanks you!

No, thank you for being so patient.


Update README.md of ShardingScaling

For #4322.
Changes proposed in this pull request:

Update README.md

Pull Request Test Coverage Report for Build 9870

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 59.961%

Totals

Change from base Build 9865:
0.0%

Covered Lines:
12542

Relevant Lines:
20917

💛  - Coveralls


Build for ARM Macs?

I'm trying to develop on a Mac with a fully native toolchain and ibazel is the last tool which doesn't have an ARM build. I've tried running ibazel from brew using rosetta but it spawns a bazel server under rosetta too which causes other problems with the toolchain. I've also tried to build ibazel myself using bazel build //ibazel and get errors about no matching toolchains found for types @io_bazel_rules_go//go:toolchain...
Is there a chance that someone with more experience could at least put up a build of v0.15.10 for darwin-arm64?

Both me and @mrmeku did some experiments around this and ultimately trace the problem to https://github.com/fsnotify/fsevents/issues/50
Last time we discussed this I was told @gregmagolan knows how to tackle it

Seems like a duplicate of https://github.com/bazelbuild/bazel-watcher/issues/482 ?
Though this issue has more info about how to fix it.

Anyway anyone else can help with this problem, @gregmagolan?
I managed to run bazel build //ibazel on my M1 Mac, after updating rules_go, but I'm not sure if there is something else I need to run too.

I also tried to have a look at https://github.com/fsnotify/fsevents/issues/50 , but I think for that we might need to do the different types of builds on machines with different architectures?

Sounds like @mistic figured it out in https://github.com/fsnotify/fsevents/issues/50#issuecomment-1015795295
And hopefully https://github.com/bazelbuild/bazel-watcher/pull/496 will fix it
Thanks @mistic!

Now we just need to get the PR I've opened to be able to move forward @zoidbergwill but it is still waiting for reviews

Unfortunately all the PRs that claim to fix this do not pass CI. There is no path forward if CI is red, and I don't have an arm mac to do any testing on.

@achew22 I dont think that is true, the red CI is being caused by the miss of https://github.com/bazelbuild/bazel-watcher/pull/496/commits/a28f5289b532deca1d8c058fa5e3f6e956bc15a8 which I've reverted as I was not sure about it and was waiting on your review to understand wether or not it make sense. I have arm hardware and I'm available to work with you to move the PR forward as long as you are available to do it...

Just reverted the change I mentioned and the CI is now green.


micro-metrics should optionall capture stats on events (queries and jobs)

See https://github.com/aol/micro-server/pull/231

Implemented in https://github.com/aol/micro-server/pull/231


Ejector design - Fluid Reverse

Fluid reverse in ejector
Hypothesis:

Incorrect formulas used in the calculation of ejector parameters.
Poor manufacturing quality—3D printing doesn't provide acceptable tolerances.
The design itself makes it difficult to ensure central symmetry.

Problem with the pump.
High quality pump with 8+ Bar and 10+ L/min is required


Incorporate symwalk functionality

See https://github.com/kubernetes/helm/commit/e1027fae732034e0390f5cd231c6116e63b75aa2.

Fixed in #109.


Similarity plugin (WIP)

https://github.com/getnikola/nikola/issues/1702

The $64,000 question is: how can WordPress plugins generate a list like that dynamically on every request? Perhaps this approach is a bit overdone?

Oh, they have all the text in a DB with FTS. With that, it's easier.


Timeout Error :(

Tried Coping 8TB and it throws Timeout Error.
Logs :-
2020-07-29T12:39:14.692732+00:00 app[worker.1]: An uncaught error was raised while running the promise
2020-07-29T12:39:14.692742+00:00 app[worker.1]: Traceback (most recent call last):
2020-07-29T12:39:14.692742+00:00 app[worker.1]:   File "/app/.heroku/python/lib/python3.7/site-packages/telegram/utils/promise.py", line 56, in run
2020-07-29T12:39:14.692743+00:00 app[worker.1]:     self._result = self.pooled_function(*self.args, **self.kwargs)
2020-07-29T12:39:14.692743+00:00 app[worker.1]:   File "clonerbot.py", line 158, in clone
2020-07-29T12:39:14.692744+00:00 app[worker.1]:     message.edit_text(to_send)
2020-07-29T12:39:14.692744+00:00 app[worker.1]:   File "/app/.heroku/python/lib/python3.7/site-packages/telegram/message.py", line 876, in edit_text
2020-07-29T12:39:14.692745+00:00 app[worker.1]:     chat_id=self.chat_id, message_id=self.message_id, *args, **kwargs)
2020-07-29T12:39:14.692745+00:00 app[worker.1]:   File "", line 2, in edit_message_text
2020-07-29T12:39:14.692745+00:00 app[worker.1]:   File "/app/.heroku/python/lib/python3.7/site-packages/telegram/bot.py", line 67, in decorator
2020-07-29T12:39:14.692746+00:00 app[worker.1]:     result = func(*args, **kwargs)
2020-07-29T12:39:14.692746+00:00 app[worker.1]:   File "/app/.heroku/python/lib/python3.7/site-packages/telegram/bot.py", line 1898, in edit_message_text
2020-07-29T12:39:14.692746+00:00 app[worker.1]:     return self._message(url, data, timeout=timeout, reply_markup=reply_markup, **kwargs)
2020-07-29T12:39:14.692747+00:00 app[worker.1]:   File "/app/.heroku/python/lib/python3.7/site-packages/telegram/bot.py", line 175, in _message
2020-07-29T12:39:14.692747+00:00 app[worker.1]:     result = self._request.post(url, data, timeout=timeout)
2020-07-29T12:39:14.692747+00:00 app[worker.1]:   File "/app/.heroku/python/lib/python3.7/site-packages/telegram/utils/request.py", line 333, in post
2020-07-29T12:39:14.692747+00:00 app[worker.1]:     **urlopen_kwargs)
2020-07-29T12:39:14.692748+00:00 app[worker.1]:   File "/app/.heroku/python/lib/python3.7/site-packages/telegram/utils/request.py", line 237, in _request_wrapper
2020-07-29T12:39:14.692748+00:00 app[worker.1]:     message = self._parse(resp.data)
2020-07-29T12:39:14.692748+00:00 app[worker.1]:   File "/app/.heroku/python/lib/python3.7/site-packages/telegram/utils/request.py", line 195, in _parse
2020-07-29T12:39:14.692756+00:00 app[worker.1]:     raise RetryAfter(retry_after)
2020-07-29T12:39:14.692756+00:00 app[worker.1]: telegram.error.RetryAfter: Flood control exceeded. Retry in 9 seconds

It just logs that exception as an Error but everything should go fine after some seconds. Anyway, if you face it often or if you do multiple clones, change the message update interval to something higher.
Telegram API Limits :

Private Chat Limit - 60 edits (or requests) per minute

Group Chat limit - 30 edits (or requests) per minute.

@jagrit007 Also can I use this to clone TeamDrive or just folder ?

@jagrit007 Also can I use this to clone TeamDrive or just folder ?

You need to have at least viewing rights in that TeamDrive.

If you're using SAs, your SAs/Google Group must be in the TD

If not using Service Accounts, your primary account should be in the TD but you will only be able to copy 750GB every 24 hours.

It just logs that exception as an Error but everything should go fine after some seconds. Anyway, if you face it often or if you do multiple clones, change the message update interval to something higher.

I'm sorry to ask but where do I change this update interval?


Add API Key Update command

Add a command that will allow you to generate a new key for an API Key Listing.

Completed in PR #56


Fix password reset

Exception on /auth/reset-password-request [POST]
Traceback (most recent call last):
  File "/Users/gfitzp/Sites/fitzflix/venv/lib/python3.7/site-packages/flask/app.py", line 2446, in wsgi_app
    response = self.full_dispatch_request()
  File "/Users/gfitzp/Sites/fitzflix/venv/lib/python3.7/site-packages/flask/app.py", line 1951, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/Users/gfitzp/Sites/fitzflix/venv/lib/python3.7/site-packages/flask/app.py", line 1820, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/Users/gfitzp/Sites/fitzflix/venv/lib/python3.7/site-packages/flask/_compat.py", line 39, in reraise
    raise value
  File "/Users/gfitzp/Sites/fitzflix/venv/lib/python3.7/site-packages/flask/app.py", line 1949, in full_dispatch_request
    rv = self.dispatch_request()
  File "/Users/gfitzp/Sites/fitzflix/venv/lib/python3.7/site-packages/flask/app.py", line 1935, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/Users/gfitzp/Sites/fitzflix/app/auth/routes.py", line 78, in reset_password_request
    send_password_reset_email(user)
  File "/Users/gfitzp/Sites/fitzflix/app/auth/email.py", line 9, in send_password_reset_email
    sender=app.config["ADMIN_EMAIL"],
NameError: name 'app' is not defined

Fixed in d19187d7eb6bea4b2fda3efa26de1ac65f756005


oopsy: specify flex props of flex childs

The width of the list can be fixed according to the size of the window, instead of its content.

Hi! Sorry, I'm not sure I understand what this is doing.  This doesn't seem to have any effect for me, regardless of window size.  Can you give me an example of what would change?

Maybe because I'm not using the death report, previewed size and real size are different (The overlay's background is white, for explanation):

Unlocked (Preview)
Locked (Real one)

Picked .livelist with dev tool
Picked .flexcontainer

The .death-report is properly display: none, but the .livelist width is 300px, its min-width.
This one tries to fix it putting like flex: 1 0 300px.

Thank you for the explanation!


Functional buttons, Finishing styling and Readme file

Functional buttons, Finishing styling and Readme file
In this PR, I:

Made the 'Add Ingredient' button functional
Styled the tables of the app, and the general buttons
Fixed button visibility if the user wasn't the owner, or there was no user logged in
Finished styling the remaining elements
Fixed the public recipes details
Updated the readme file


[UIE-117] Move Interactive's CSS to components package

https://broadworkbench.atlassian.net/browse/UIE-117
To support hover and focus styles, Interactive depends on some CSS. That CSS is currently located in style.css. Now that Interactive is distributed to other projects as part of the components package, that CSS should be distributed with it.
This moves the relevant CSS to packages/components/src/Interactive.css. When the components package is built, Vite bundles that CSS and outputs to packages/components/libs/style.css. In order for consumers of components to import style.css, it must be added to the exports config in package.json, which currently only allows importing from index.js.
And in order to convince ESLint that @terra-ui-packages/components/style.css could be resolved, I had to switch to a different ESLint import resolver: eslint-import-resolver-typescript. It looks more well maintained than the eslint-import-resolver-custom-alias that we're using now anyway.

I would like us to explore a bit more if there is another way to do this that doesn't require the "shadow dependency" of the consuming app having to remember to import the css.

https://github.com/DataBiosphere/terra-ui/pull/4147/commits/62db0add6201b27c0fd31368261d3f30b902c2f8 has Interactive inject a style element with the required CSS into the document. This removes the separate CSS file.

I would like us to explore a bit more if there is another way to do this that doesn't require the "shadow dependency" of the consuming app having to remember to import the css.

nice work switching to injectStyle solution.... I think the PR description needs updating to reflect the improved outcome.  No more css import requirement on consume project, YAY!


Auto-Compile Game Code after Package Update

As mentioned here, it would be really nice if the Duality Package Manager would also compile local game plugins after updating packages.

Wow, I feel like digging up old issues today.
Just chipping in what I think: it probably wouldn't be a good idea. The package update could introduce breaking changes or incompatibilities, so wouldn't it basically be an exercise in futility to try to compile the code in such cases? The user would probably be better off manually compiling the code, right?

In these cases, the editor could just tell the user that he needs to fix his code - which might be better than a runtime failure when trying to run outdated Assemblies.
Still, this is probably more or less a half-arguable, half-nice2have feature, depending on how it would be executed.

Closing this, because it seems a bit questionable and a lot like a nice2have feature.


Merge prTesting_201908270346 branch to master branch

Docs Build status updates of commit 38ec7fa:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon.md
:bulb:Suggestion

Details

split/updateTestCon.md

[Suggestion] Missing attribute: author. Add the current author's GitHub ID. NOTE: This Suggestion will be elevated to a Warning on 9/1/2019.
[Suggestion] Missing attribute: title. Add a title string to show in search engine results. NOTE: This Suggestion will be elevated to a Warning on 9/1/2019.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add multi-dimensional lists (similar to NDArray)

Don't feel like doing this. It would be far more efficient to use NDArray anyways.


Change Resolution

Hi,
I am not able to change the window size as mentioned in the documentation
<Unity unityContext={unityContext} height="100%" width="950px" />
I tried changing the values to percentage pixels my layout is still kinda landscape
like this
<Unity unityContent={unityContent} height="730px" width="480px" />

here are Unity3D settings

here is when I run the build as standalone on browser

as you can see it is running in the desired resolution
Am I missing something?
regards,
Nipun Davod

Hi! Thanks for opening an issue.
There is a little bit of misunderstanding about the WebGL width and height properties in Unity. As you can see below these options, you can choose a template which Unity will use when building your application. Some template provide some variables which Unity detects and allows the developer to enter from the enter. Height and width are such values, these do not change anything about your build, except they alter the HTML files that comes with your build and sets the height and width value. (TL;D'R Width and Height in Unity don't do anything, no need to use).
You can use percentages in as the Height and Width properties inside of React and then go with regular responsive styling in order to scale your application.

hi @jeffreylanters , so I am not able to follow you completely. I also tried the height and width in %age but they didn't change the resolution the view. Can you please share the exact steps or documentation which I can refer to?
regards,
Nipun David

Hi @nipundavid , I encountered the same issue with the 7.x version and the width/height props having no effects. My solution was to override the style with the !important rule, for example :
<Unity unityContent={this.unityContent} className="unity-content"/>

// CSS
.unity-content {
    height: 640px !important;
    width: 480px !important;
}

In my case, the main problem was actually what seemed like a fixed 2:1 aspect ratio (i.e. the height of the canvas being always equals to 50% of its width), so I'll let my somehow responsive solution here if anyone needs it.
componentDidMount() {
    window.addEventListener('resize', this.resize);

    this.resize();
}

componentWillUnmount() {
    window.removeEventListener('resize', this.resize);
}

resize = () => {
    const unityElement = document.getElementById("unity") as HTMLInputElement;
    const width = parseFloat(window.getComputedStyle(unityElement).width);

    unityElement.setAttribute("style", "height: " + (width / 16 * 9) + "px !important");
}

render() {
    return (

            <Unity unityContent={this.unityContent} />

    );
}

I had luck with this:
In my case I have a header which is why I'm subtracting 64px

        <Unity height='100%' width='100%' unityContext={context} />


Reproducing ToRA Quoted Results

Hi,
Today I executed the following steps:

modified infer.sh to point to ToRA code, as shown
MODEL_NAME_OR_PATH="llm-agents/tora-code-7b-v1.0"

Ran  ./scripts/infer.sh

Final Eval output was seen as shown below:

Num samples: 5000
Num scores: 5000
Timeout samples: 1
Empty samples: 8
Mean score: [29.1]
Type scores: {'Algebra': 41.2, 'Counting & Probability': 22.8, 'Geometry': 14.6, 'Intermediate Algebra': 22.1, 'Number Theory': 30.0, 'Prealgebra': 36.7, 'Precalculus': 19.8}

This does not seem to agree with the ~45% quoted in the paper and on the papers with code webpage. Why the large discrepancy, how can I reproduce the quoted numbers?
Edit, here are some relevant environment variables
>>> torch.__version__
'2.0.1+cu117'
>>> transformers.__version__
'4.35.0'
>>> vllm.__version__
'0.2.1.post1'

EDIT:
I think it might just have been the vllm mismatch that drove this difference, as I can replicate the benchmark now after doing pip install -r requirements.txt to sync
Num samples: 5000
Num scores: 5000
Timeout samples: 2
Empty samples: 1
Mean score: [44.6]
Type scores: {'Algebra': 61.2, 'Counting & Probability': 31.0, 'Geometry': 22.3, 'Intermediate Algebra': 36.2, 'Number Theory': 51.1, 'Prealgebra': 55.5, 'Precalculus': 29.7}

btw, any ideas why the discrepancy occurs?

Your analysis makes sense. We also found that vLLM has compatibility issues with different versions of Transformers. Apart from the version provided in the repo, we find that it's also fine to use transformers==4.33.1 and vLLM==0.2.0 for training and inference.


Make sure retries work when interacting with APIs (both server & object storage)

Tenacity is being used for retries, but should do some more tests to confirm this it's working correctly.

Fixed in https://github.com/simvue-io/client/pull/53. raise_for_status() was missing.


Add tests for the standalone executable "submit" command

After talking with @bettinaheim, I'm going to merge this PR as-is so we can merge the feature branch to master with some tests, but I'll add more tests to address the remaining comments in a separate PR.

@cesarzc @anpaz-msft. I've asked Sarah to make a separate PR to add the additional tests that you suggested and merge this one.  I'd much rather have a good set of tests than no tests, and I want to make sure that we have sufficient time for the release testing.


Best Async

Improve more async

Current coverage is 86.65% (diff: 82.08%)

Merging #186 into dev will increase coverage by 0.42%

@@                dev       #186   diff @@
==========================================
  Files            11         11
  Lines           770        832    +62
  Methods         143        169    +26
  Messages          0          0
  Branches        135        136     +1
==========================================
+ Hits            664        721    +57
- Misses          106        111     +5
  Partials          0          0

Powered by Codecov. Last update c0addef...b4ac147


Azure: Action recommended: Update your AKS pricing tier API parameters to avoid a breaking change

Update AKS pricing tier API parameters when you begin using Azure API 2023-02-01 or newer to avoid a breaking change  You're receiving this notice because you use Azure Kubernetes Service (AKS).As part of our efforts to improve AKS cluster and workload reliability, we're updating AKS pricing tiers. This includes removing the "Basic" parameter in ManagedClusterSKUName and the "Paid" parameter in ManagedClusterSKUTier in Azure API version 2023-02-01, which is a breaking change.The "Basic" parameter in ManagedClusterSKUName was replaced by "Base". The "Paid" parameter in ManagedClusterSKUTier was replaced by "Standard", which has the uptime SLA enabled by default, plus:   Support for up to 5,000 nodes per cluster. Improved cluster reliability and resources.

Recommended action
To avoid disrupting your AKS workloads, update any automated scripts, CD pipelines, ARM templates, Terraform, or other third-party tooling that relies on the ManagedClusterSKUName and ManagedClusterSKUTier parameters that use "Basic" or "Paid" to use "Base" or "Standard" when you adopt Azure API version 2023-02-01 or newer.Update AKS pricing tier API parameters when you begin using Azure API 2023-02-01 or newer to avoid a breaking change
You're receiving this notice because you use Azure Kubernetes Service (AKS).
As part of our efforts to improve AKS cluster and workload reliability, we're updating AKS pricing tiers. This includes removing the "Basic" parameter in ManagedClusterSKUName and the "Paid" parameter in ManagedClusterSKUTier in Azure API version 2023-02-01, which is a breaking change.
The "Basic" parameter in ManagedClusterSKUName was replaced by "Base". The "Paid" parameter in ManagedClusterSKUTier was replaced by "Standard", which has the uptime SLA enabled by default, plus:
Support for up to 5,000 nodes per cluster.
Improved cluster reliability and resources.
ManagedClusterSKU parameter changes in Azure API versions
2023-01-01 API or earlier	Starting with 2023-02-01 API

ManagedClusterSKUName	"Basic"	"Base"
ManagedClusterSKUTier	"Free"
"Paid"	"Free"
"Standard"
Recommended action
To avoid disrupting your AKS workloads, update any automated scripts, CD pipelines, ARM templates, Terraform, or other third-party tooling that relies on the ManagedClusterSKUName and ManagedClusterSKUTier parameters that use "Basic" or "Paid" to use "Base" or "Standard" when you adopt Azure API version 2023-02-01 or newer.

Would be great if one could verify my research and review this ticket.

helpfull command for me:
az aks list --output table
taken your command and checked it on every cluster example:
$az aks show --name cx-beta-aks --resource-group cx-beta-rg | jq .sku
{
  "name": "Base",
  "tier": "Free"
}
$az aks show --name cx-core-aks --resource-group cx-core-rg | jq .sku
{
  "name": "Base",
  "tier": "Free"
}
$az aks show --name cx-dev-aks --resource-group cx-dev-rg | jq .sku
{
  "name": "Base",
  "tier": "Free"
}
$az aks show --name cx-devsecops-testing-aks --resource-group cx-devsecops-testing-rg | jq .sku
{
  "name": "Base",
  "tier": "Free"
}
$az aks show --name cx-stable-aks --resource-group cx-stable-rg | jq .sku
{
  "name": "Base",
  "tier": "Free"
}
$az aks show --name cx-vault-aks-services --resource-group cx-vault-rg | jq .sku
{
  "name": "Base",
  "tier": "Free"
}

after description

i would suggest it is only a cost question
@Siegfriedk shall we stay on standard tier for the INT cluster?

found command to update an existing cluster to the Free tier if needed:
az aks update --name cxtsi-hotel-budapest-aks-services --resource-group cxtsi-hotel-budapest-rg --tier free

but found out that our default is sku=standard so for now i would also suggest nothing to do here:
https://github.com/catenax-ng/cloud-infra/blob/947a3688f6848725f2df347f1cfcd18307c38224/modules/consortium_cluster/main.tf#L12

also found yesterday a azure portal option to change the tiers if we want to:

Of course there is a possibility to change ;)


This crate looks unmaintained

Looking at the issues, PR and latest commit, this crate looks unmaintained, which is a pity.
Is there a fork that is maintained?

Looks like there isn't and there isn't any crate with similar functionality.

I probably should have replied earlier to this, sorry. I personally just don't have time to spare for this project, and I suspect @kabergstrom is in the same place with that. I would be quite happy to see someone fork this project and continue it forward.

It would be nice to represent the diff in a more space-efficient / binary way (maybe BSON/bincode).
And e.g. instead of encoding enum variants as strings, using their discriminant (int) instead.

@PPakalns Have you found a crate with similar functionality? Maybe even with more compact data representation like CBOR?

@Boscop
Hi, I have not found such crate. Additionally, this crate wasn't very efficient for my use case because it always tries to compare full state and it gets slow very fast with linearly growing state.
I have experimented with writing custom "StateTracking" library that tracks modifications of the data structure and stores them, so no additional comparison is needed.
Sadly the API interface ergonomics weren't very nice to use so I decided to use another approach.
In my use case for users of the diff full state is not needed, I manually store the changes that should be sent to the client and reconstruct the necessary state representation on the client side.

If intereseted, API interface that I explored. I can publish the library, but will not have time to improve it as I am not using it:
#[cfg(test)]
mod tests {
    use super::*;
    use crate as diff_tracker;

    #[derive(Default, Clone, DiffTracker, serde::Serialize, serde::Deserialize)]
    pub struct Test {
        a: u32,
        b: bool,
        unit: TestUnit,
        inner: TestInner,
    }

    #[derive(Default, Clone, DiffTracker, serde::Serialize, serde::Deserialize)]
    pub struct TestInner {
        a: u8,
        b: u16,
        c: u32,
        id_to_value: HashMap<i32, TestHashMap>,
    }

    #[derive(Default, Clone, DiffTracker, serde::Serialize, serde::Deserialize)]
    pub struct TestHashMap {
        a: u8,
    }

    #[derive(Default, Clone, Copy, serde::Serialize, serde::Deserialize)]
    pub struct TestUnit {
        a: u8,
    }
    diff_tracker_base!(TestUnit);

    #[test]
    fn it_works() {
        let mut test = Test::default();
        let mut test_old = test.clone();

        let mut test_changes = <Test as DiffTracked>::Change::default();

        let mut tracker = <Test as DiffTracked>::Tracker::new(&mut test, &mut test_changes);

        assert_eq!(tracker.a, 0);
        tracker.a_mut().get().set(10);
        assert_eq!(tracker.a, 10);

        assert_eq!(tracker.inner.a, 0);
        tracker.inner_mut().get().a_mut().get().set(5);
        assert_eq!(tracker.inner.a, 5);

        let a = tracker.with_inner(|mut inner| {
            inner.with_a(|mut a| {
                a.set(9);
                *a.cow() = 10;
                *a
            })
        });
        assert_eq!(a, 10);

        assert_eq!(tracker.inner.a, 10);

        assert_eq!(tracker.unit.a, 0);
        tracker.with_unit(|mut unit| {
            let mut unit = unit.cow();
            unit.a = 5;
        });
        assert_eq!(tracker.unit.a, 5);

        assert_eq!(tracker.inner.id_to_value.len(), 0);
        tracker
            .inner_mut()
            .get()
            .id_to_value_mut()
            .get()
            .insert(5, TestHashMap { a: 5 });
        tracker.with_inner(|mut inner| {
            inner.with_id_to_value(|mut id_to_value| {
                let mut entry = id_to_value.entry(&10);
                let mut value = entry.get_or_default();
                value.with_a(|mut a| {
                    a.set(14);
                });
            });
        });
        assert_eq!(tracker.inner.id_to_value.get(&5).map(|v| v.a), Some(5));

        {
            let mut inner_core = tracker.inner_mut();
            let mut inner = inner_core.get();
            let mut map = inner.id_to_value_mut();
            let mut map = map.get();
            let mut entry_core = map.entry(&5);
            let mut entry = entry_core.get_mut().unwrap();
            let mut a = entry.a_mut();
            let mut a = a.get();
            a.set(11);
        }

        assert_eq!(tracker.inner.id_to_value.get(&5).map(|v| v.a), Some(11));

        assert_eq!(&test_changes.a.as_ref().unwrap().value, &Some(10));
        assert_eq!(
            &test_changes
                .inner
                .as_ref()
                .unwrap()
                .a
                .as_ref()
                .unwrap()
                .value,
            &Some(10)
        );

        assert_eq!(test_old.a, 0);
        assert_eq!(test_old.inner.a, 0);
        assert_eq!(test_old.inner.id_to_value.get(&5).map(|v| v.a), None);
        assert_eq!(test_old.unit.a, 0);

        let serialized_test_changes = serde_json::to_string_pretty(&test_changes).unwrap();
        println!("{}", &serialized_test_changes);
        let test_changes: TestChange = serde_json::from_str(&serialized_test_changes).unwrap();
        test_old.apply(&test_changes);

        assert_eq!(test_old.a, 10);
        assert_eq!(test_old.inner.a, 10);
        assert_eq!(test_old.inner.id_to_value.get(&5).map(|v| v.a), Some(11));
        assert_eq!(test_old.inner.id_to_value.get(&10).map(|v| v.a), Some(14));
        assert_eq!(test_old.unit.a, 5);
    }
}

@PPakalns Interesting. Have you investigated whether any of these reactive/signals-based crates work for your use-case (instead of diffing: Send granular updates on each field change)?

https://crates.io/crates/futures-signals
https://crates.io/crates/dioxus-signals
https://crates.io/crates/rxrust
https://crates.io/crates/another-rxrust


engine_traits: allow chaos flush notification

What is changed and how it works?
Issue Number: Close #14113
What's Changed:
`OnFlushComplete` can be called out of order. What we can assume is
when a seqno finishes flush, all SSTs have smaller seqno must also
finish flush.

Check List
Tests

Unit test
Integration test

Release note
None

/check-issue-triage-complete

/merge


[$500]  Room - Invited user to Room does not receive message notification until open the chat first

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal team
Slack conversation:
Action Performed:

User A (mobile) create a Room and invite User B
User A send message to the Room

Expected Result:
User B should receive notification about the message
Actual Result:
User B does not receive notifications until he navigates to the room
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/5bc0bf7f-b6e8-4567-844d-6570266c4f52
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~016ef57f5ce2098531
Upwork Job ID:<PHONE_NUMBER>368362496
Last Price Increase: 2023-11-30

I guess this is related to the notification settings of the room on the receiver side

@thesahindia do we need to ask for help from Eng on this one?

This is a BE error, when B invited A, the pusher sent to A with notificationPreference setting as Daily; but when A opened the report, OpenReport returned with always.

@tienifr I haven't ever worked on this flow, so I could use a little more context. What value are you expecting to have returned?

@tienifr bump on the above question.

@flodnv I was wondering if you could help me with this one (also tagging @iwiznia @dangrous since you might be familiar. I tried to reproduce this, and I found that the issue doesn't seem to be related to notificationPreference. There are two cases here, and it's not clear to me which case the issue was opened about.
@kbecciv Can you please clarify which scenario this issue is about?

User A invites User B that does not have an existing account
User A invites User B that does have an existing account, they just haven't chatted together before

In the first case, there is no message sent because this code is triggered and the account is not found.
In the second case, it appears that there is a push message sent to user B and it contains a notification preference of always, which looks like it should be like we expect.

@tgolen It is scenario 2. User A invites User B that does have an existing account, they just haven't chatted together before

OK, thank you. I'll need to look at that one more closely. When I tried it earlier, everyone received an always push notification.

Any update on this one @tgolen?

Yeah, I'll be working on this one today and should know more by EOD.

I have been unable to reproduce this. Looking at the events from the backend, they are all sent with always set as the notification preference. On the frontend, I'm always receiving the notification.


Title: Improving the socials button

Is your feature request related to a problem? Please describe.
Hey @agamjotsingh18 I want to add the same color palette of the social button which is official. It will look nice on hove. Please assign me this issue. Thank you!
Describe the solution you'd like.
Changing colors of social buttons according to their official colors on hovering over them.
Describe alternatives you've considered.
NA
Add any other context or screenshots about the feature request here.
No response

I want to  contribute on this issue , under Gssoc'23'. i want to make changes please assign it to me.

@SamridhiNancy i have raised this issue and work on it. Please raise another issue if you wnat to contribute. Thank you.

Please assign me this issue so that I can resolve it under GSSOC-23

@adityavpawar i have raised this issue and work on it. Please raise another issue if you want to contribute. Thank you.

Sure @sumitkr2000 make sure it looks good with the theme

@agamjotsingh18 Sir is this is issue still open , if it is please assign it to me .

@agamjotsingh18 please see my pr and merge it


Examples

Please add some more examples.

I've added an answer on StackOverflow with example code.

A post I wrote in Oct 2019 for using MSAL.PS for Microsoft Graph with Application API Permissions.
Microsoft Graph using MSAL with PowerShell
A new post for using MSAL.PS for Microsoft Graph with Delegated API Permissions.
Microsoft Graph using MSAL with PowerShell and Delegated Permissions

Last one.
Microsoft Graph using MSAL with PowerShell and Certificate Authentication


Possible to pack SQLite file?

I have a program that read data from local sqlite db, and show data to users, I wanna to pack all assets include sqlite file to one binary file, this program only execute read operation from sqlite, is it possible to pack sqlite file?

That should be possible. You'll either have to give the file contents directly to sqlite lib(if thats even possible), or write the file to disk/tmp folder and start sqlite with that file.


Support: stats regex inclusions, exclusion, and suffixes

At present istio supports
sidecar.istio.io/statsInclusionPrefixes that translates into stats_matcher.inclustion_list...
In order to collect downstream stats at the main inbound port one needs to be able to use
http.{endpoint_ip}_{port} like http.<IP_ADDRESS>_8080.downstream_rq_time
This requires knowing your own IP, which the pilot agent already knows.
In addition to this, we need to be able to specify suffixes as well.
In absence of this feature, a user is required to add http. as prefix that drags in too many stats.

It is a common ask to have downstream_cx_total,downstream_cx_active,downstream_rq_total,downstream_rq_active which will be possible efficiently with endpoint_ip.
It will also be possible with regex matches.

@Stono you will have to add http. to the prefixes which is not recommended.

Yeah I guess I'll not bother for the time being! Thanks

We should include sensible defaults (no shooting yourself in the foot) with any updates here.

The https://www.envoyproxy.io/docs/envoy/latest/api-v2/config/metrics/v2/stats.proto#config-metrics-v2-statsmatcher doesn't let us mix inclusions and exclusions.  Our design can be improving inclusions.
It would be straightforward to offer sidecar.istio.io/statsInclusionRegexps and sidecar.istio.io/statsInclusionSuffixes annotations.  (There seems to be no point in doing exact).
The documentation is at https://www.envoyproxy.io/docs/envoy/latest/api-v2/type/matcher/string.proto#type-matcher-stringmatcher
@mandarjog Would you like to see sidecar.istio.io/statsInclusionRegexps or alpha.sidecar.istio.io/statsInclusionRegexps.

@mandarjog I don't see how to support {port}.  Do you have any ideas?
To support {endpoint_ip} the code in bootstrap_config.go could get the IP address, but this seems error-prone.  At the point the inclusion_list is constructed we don't yet have communication to pilot.
Would it be reasonable to skip implementing {endpoint_ip} and {port} and recommend developers do something like sidecar.istio.io/statsInclusionRegexps=http.[0-9]*\.[0-9]*\.[0-9]*\.[0-9]*_8080.downstream_rq_time?

@esnible look at the attached PR.
It already implements prefix and suffix inclusions with endpoint ip via bootstrap.

Closing because handled by https://github.com/istio/istio/pull/14212


EDU-312 Enable batch lesson creation

Closes https://educandu.atlassian.net/browse/EDU-312

The UI looks super nice 😍


Multi-Parent-Feature

I suggest multi-parent options in inscribing process.
Now, implementing single parent inscription using OP_3, wondering about that feature based on current opcodes.

This API does not do inscribing services, so closing this feature request.