2024-12-03 02:18:19,160 INFO  org.apache.flink.runtime.jobmaster.JobMaster                 [] - Disconnect TaskExecutor <IP_ADDRESS>:45917-f81c14 because: Stopping JobMaster for job 'insert-into_apache_kickstarter.airlines.flight_kafka_sink' (4443c93037d620ac81c8c28fbce3f8ae).
2024-12-03 02:18:19,160 INFO  org.apache.flink.runtime.jobmaster.JobMaster                 [] - Close ResourceManager connection 257d1985c5ae60006687f2202cd6d683: Stopping JobMaster for job 'insert-into_apache_kickstarter.airlines.flight_kafka_sink' (4443c93037d620ac81c8c28fbce3f8ae).
2024-12-03 02:18:19,160 INFO  org.apache.flink.runtime.resourcemanager.StandaloneResourceManager [] - Disconnect job manager<PHONE_NUMBER>0000000000000000000000@pekko.tcp://flink@jobmanager:6123/user/rpc/jobmanager_5 for job 4443c93037d620ac81c8c28fbce3f8ae from the resource manager.
2024-12-03 02:18:19,161 INFO  org.apache.flink.runtime.resourcemanager.slotmanager.DefaultSlotStatusSyncer [] - Freeing slot b2b526eac34ff284c858389b2bc34d27.
2024-12-03 02:18:19,289 INFO  org.apache.flink.runtime.executiongraph.ExecutionGraph       [] - Map (1/1) (d70bb348f76d72d498eb64ab5a3e23f4_bed55925f464d5ca7e68a0232d5b7b2f_0_0) switched from INITIALIZING to RUNNING.
2024-12-03 02:18:19,290 INFO  org.apache.flink.runtime.source.coordinator.SourceCoordinator [] - Source Source: sunset_kafka_source[11] registering reader for parallel task 0 (#0) @ <IP_ADDRESS>
2024-12-03 02:18:19,291 INFO  org.apache.flink.runtime.source.coordinator.SourceCoordinator [] - Source Source: skyone_kafka_source[9] registering reader for parallel task 0 (#0) @ <IP_ADDRESS>
2024-12-03 02:18:19,291 INFO  org.apache.iceberg.flink.source.enumerator.AbstractIcebergEnumerator [] - Added reader: 0
2024-12-03 02:18:19,291 INFO  org.apache.iceberg.flink.source.enumerator.AbstractIcebergEnumerator [] - Added reader: 0
2024-12-03 02:18:19,292 INFO  org.apache.iceberg.flink.source.enumerator.AbstractIcebergEnumerator [] - Received request split event from subtask 0
2024-12-03 02:18:19,292 INFO  org.apache.iceberg.flink.source.enumerator.AbstractIcebergEnumerator [] - Received request split event from subtask 0
2024-12-03 02:18:19,292 INFO  org.apache.iceberg.flink.source.enumerator.AbstractIcebergEnumerator [] - Assigning splits for 1 awaiting readers
2024-12-03 02:18:19,292 INFO  org.apache.iceberg.flink.source.enumerator.AbstractIcebergEnumerator [] - Assigning splits for 1 awaiting readers
2024-12-03 02:18:19,292 INFO  org.apache.iceberg.flink.source.enumerator.AbstractIcebergEnumerator [] - No more splits available for subtask 0
2024-12-03 02:18:19,292 INFO  org.apache.iceberg.flink.source.enumerator.AbstractIcebergEnumerator [] - No more splits available for subtask 0
2024-12-03 02:18:19,293 INFO  org.apache.flink.runtime.executiongraph.ExecutionGraph       [] - Source: skyone_kafka_source[9] -> TableToDataSteam -> (Map, Filter, Map, Filter) (1/1) (d70bb348f76d72d498eb64ab5a3e23f4_cbc357ccb763df2852fee8c4fc7d55f2_0_0) switched from INITIALIZING to RUNNING.
2024-12-03 02:18:19,293 INFO  org.apache.flink.runtime.executiongraph.ExecutionGraph       [] - Source: sunset_kafka_source[11] -> TableToDataSteam -> (Map, Filter, Map, Filter) (1/1) (d70bb348f76d72d498eb64ab5a3e23f4_6cdc5bb954874d922eaee11a8e7b5dd5_0_0) switched from INITIALIZING to RUNNING.
2024-12-03 02:18:19,296 INFO  org.apache.flink.runtime.jobmaster.JobMaster                 [] - Triggering a manual checkpoint for job b45175964987486b841d1320442acd5d.
2024-12-03 02:18:19,297 INFO  org.apache.flink.runtime.checkpoint.CheckpointCoordinator    [] - Triggering checkpoint 1 (type=CheckpointType{name='Checkpoint', sharingFilesStrategy=FORWARD_BACKWARD}) @<PHONE_NUMBER>297 for job b45175964987486b841d1320442acd5d.
2024-12-03 02:18:19,311 INFO  org.apache.flink.runtime.checkpoint.CheckpointCoordinator    [] - Completed checkpoint 1 for job b45175964987486b841d1320442acd5d (518 bytes, checkpointDuration=14 ms, finalizationTime=0 ms).
2024-12-03 02:18:19,312 INFO  org.apache.flink.runtime.source.coordinator.SourceCoordinator [] - Marking checkpoint 1 as completed for source Source: skyone_kafka_source[9].
2024-12-03 02:18:19,312 INFO  org.apache.flink.runtime.source.coordinator.SourceCoordinator [] - Marking checkpoint 1 as completed for source Source: sunset_kafka_source[11].
2024-12-03 02:18:19,342 INFO  org.apache.flink.runtime.executiongraph.ExecutionGraph       [] - Source: skyone_kafka_source[9] -> TableToDataSteam -> (Map, Filter, Map, Filter) (1/1) (d70bb348f76d72d498eb64ab5a3e23f4_cbc357ccb763df2852fee8c4fc7d55f2_0_0) switched from RUNNING to FINISHED.
2024-12-03 02:18:19,343 INFO  org.apache.flink.runtime.executiongraph.ExecutionGraph       [] - Source: sunset_kafka_source[11] -> TableToDataSteam -> (Map, Filter, Map, Filter) (1/1) (d70bb348f76d72d498eb64ab5a3e23f4_6cdc5bb954874d922eaee11a8e7b5dd5_0_0) switched from RUNNING to FINISHED.
2024-12-03 02:18:19,404 INFO  org.apache.flink.runtime.executiongraph.ExecutionGraph       [] - Map (1/1) (d70bb348f76d72d498eb64ab5a3e23f4_bed55925f464d5ca7e68a0232d5b7b2f_0_0) switched from RUNNING to FINISHED.
2024-12-03 02:18:19,404 INFO  org.apache.flink.runtime.executiongraph.ExecutionGraph       [] - Job avro_flight_consolidator_app (b45175964987486b841d1320442acd5d) switched from state RUNNING to FINISHED.
2024-12-03 02:18:19,404 INFO  org.apache.flink.runtime.resourcemanager.slotmanager.FineGrainedSlotManager [] - Clearing resource requirements of job b45175964987486b841d1320442acd5d
2024-12-03 02:18:19,405 INFO  org.apache.flink.runtime.checkpoint.CheckpointCoordinator    [] - Stopping checkpoint coordinator for job b45175964987486b841d1320442acd5d.
2024-12-03 02:18:19,406 INFO  org.apache.flink.runtime.dispatcher.StandaloneDispatcher     [] - Job b45175964987486b841d1320442acd5d reached terminal state FINISHED.
2024-12-03 02:18:19,407 INFO  org.apache.flink.runtime.jobmaster.JobMaster                 [] - Stopping the JobMaster for job 'avro_flight_consolidator_app' (b45175964987486b841d1320442acd5d).
2024-12-03 02:18:19,407 INFO  org.apache.flink.runtime.source.coordinator.SourceCoordinator [] - Closing SourceCoordinator for source Source: skyone_kafka_source[9].
2024-12-03 02:18:19,407 INFO  org.apache.flink.runtime.source.coordinator.SourceCoordinator [] - Closing SourceCoordinator for source Source: sunset_kafka_source[11].
2024-12-03 02:18:19,407 INFO  org.apache.flink.runtime.source.coordinator.SourceCoordinator [] - Source coordinator for source Source: skyone_kafka_source[9] closed.
2024-12-03 02:18:19,407 INFO  org.apache.flink.runtime.checkpoint.StandaloneCompletedCheckpointStore [] - Shutting down
2024-12-03 02:18:19,407 INFO  org.apache.flink.runtime.source.coordinator.SourceCoordinator [] - Source coordinator for source Source: sunset_kafka_source[11] closed.
2024-12-03 02:18:19,408 INFO  org.apache.flink.runtime.jobmaster.slotpool.DefaultDeclarativeSlotPool [] - Releasing slot [3cb134713921d04bb8356f5fe89afd42].
2024-12-03 02:18:19,408 INFO  org.apache.flink.runtime.jobmaster.JobMaster                 [] - Disconnect TaskExecutor <IP_ADDRESS>:39585-0b0669 because: Stopping JobMaster for job 'avro_flight_consolidator_app' (b45175964987486b841d1320442acd5d).
2024-12-03 02:18:19,408 INFO  org.apache.flink.runtime.jobmaster.JobMaster                 [] - Close ResourceManager connection 257d1985c5ae60006687f2202cd6d683: Stopping JobMaster for job 'avro_flight_consolidator_app' (b45175964987486b841d1320442acd5d).
2024-12-03 02:18:19,408 INFO  org.apache.flink.runtime.resourcemanager.StandaloneResourceManager [] - Disconnect job manager<PHONE_NUMBER>0000000000000000000000@pekko.tcp://flink@jobmanager:6123/user/rpc/jobmanager_6 for job b45175964987486b841d1320442acd5d from the resource manager.
2024-12-03 02:18:19,411 INFO  org.apache.flink.runtime.resourcemanager.slotmanager.DefaultSlotStatusSyncer [] - Freeing slot 3cb134713921d04bb8356f5fe89afd42.


Async / Await Support for the Python parser

Hello,
I use your dt-python-parser for my web-based Python IDE as a syntax validator.
However I found out, that the grammar of your parser does not support async / await keywords.
URL
Do you plan to include this into the ANTLR grammar? I will appreciate that because my web-based IDE runs the Python in event-driven environment.
Thanks for answer.

@evonox Hi, thanks for your support.  We have support Async/Await statement at version 0.9.0, you can try this. And this project is based on grammars-v4 repo, maybe we haven't synced the latest features immediately, i think you can try to compile this grammar by yourself if you need.

@evonox It's interesting project, we have a similar dt-sql-parser project built with Molecule.


Documentation missing "describe" and "it" imports

I'm currently reading the "Get started" documentation here:
https://mochajs.org/#getting-started
And here is the first example:
var assert = require('assert');
describe('Array', function() {
  describe('#indexOf()', function() {
    it('should return -1 when the value is not present', function() {
      assert.equal([1,2,3].indexOf(4), -1);
    });
  });
});

This code won't compile because describe and it are never imported. I can't even find where thery are supposed to be imported from. Is it from the mocha package itself?
Anyway, the documentation needs to be updated in this regards. Newcomers can't use mocha by relying solely on the official documentation.

You need to run the code through mocha, not by running node my-test.js
If you keep on reading the next code block in the documentation you'll figure it out.

Back in the terminal:
$ ./node_modules/mocha/bin/mocha

Im going to close this as resolved, if you have further questions feel free to re-open.

Oh, that means that describe and it are only available as globals through mocha runtime?
Doesn't it make impossible to write tests in TypeScript? They would never compile.

@ericmorand You can run mocha with typescript through requiring ts-node/register in mocha's configurations (cli or mocha.opts file), I believe there are plenty of resources in the wild about this topic, you can also chat with us on gitter.


chore: upgrade typescript and shared eslint configuration

The same maintenance work as being done on all other repos.

Merging via #432


Security problem

Hi guys, nice work!
I found a problem that allows me to post with name of other people...
How the security layer works in resolvers?

Hi @fabiooshiro, thanks for opening the issue. However, please respect the issue template, so the bug you are encountering is easily understandable and replicable for other people.
You need to elaborate more on describing the bug and explaining steps to reproduce.

step 1, find the user id

step 2, replace the access token and the id
curl 'https://csn-api.herokuapp.com/graphql' \
  -H 'Connection: keep-alive' \
  -H 'accept: */*' \
  -H 'authorization: <YOUR-ACCESS-TOKEN>' \
  -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.105 Safari/537.36' \
  -H 'content-type: application/json' \
  -H 'Origin: https://worldexplorer.netlify.app' \
  -H 'Sec-Fetch-Site: cross-site' \
  -H 'Sec-Fetch-Mode: cors' \
  -H 'Sec-Fetch-Dest: empty' \
  -H 'Referer: https://worldexplorer.netlify.app/' \
  -H 'Accept-Language: en-US,en;q=0.9,pt;q=0.8' \
  --data-binary $'{"operationName":null,"variables":{"input":{"title":"Some post","image":"","authorId":"<THE-USER-ID>"}},"query":"mutation ($input: CreatePostInput\u0021) {\\n  createPost(input: $input) {\\n    id\\n    __typename\\n  }\\n}\\n"}' \
  --compressed

the result

If you dig more you will see that all system parts suffer from the same problem...
Good news is that's not difficult do solve

take your time

@fabiooshiro Once again, thank you for reporting the bug.
Currently, I'm busy with other projects, and I'm planning to address this issue soon when I'm available.
At first, we need to investigate what parts of the application contain the bug. Then create an issue with a detailed description of the bugs, explanation of how to reproduce them, and plan how to fix them.
Finally, we can start working on a PR based on a plan.
If you want to take part in this process, your work will be much appreciated, but please keep the "plan" and "issue/PR" templates in mind.

Closing in favor of #73 https://github.com/DimiMikadze/create-social-network/issues/73


Auto-Publish Documentation

The purpose of this PR is to auto-publish Canon Bootstrap's documentation to GitHub Pages every time a commit is made to the master branch. This will make sure the published documentation is always up-to-date without human intervention.
To implement this feature, this PR introduces the following changes:

Build documentation on every Travis build.
Cache node_modules to speed up Travis builds.
Execute on_success script that publishes to GitHub pages using a shell script.

In the future, I can see this being improved in a number of ways:

Only publish documentation to the root of gh-pages when a tag is pushed. This will synchronize documentation with official releases.
Provide archived versions of documentation for official releases at releases/VERSION.
When commits to master are made, push documentation to builds/SHA within gh-pages so documentation for master is also publicly available. We could also use the same approach for publishing/previewing documentation changes in a pull request, but it might result in a crazy number of pushes to gh-pages.

@eddywashere Please review. Thanks!

:shipit:


[Bug?] Audio being transcribed forever despite following standard

Hello, this might or might not be a bug, but I wanted to mention it as this package could be well used in combination with node-mic as well.
import { Logger } from '@src/logger';
import path from 'path';
import { nodewhisper } from 'nodejs-whisper'
import fs from 'fs';
import NodeMic from 'node-mic';

const voicesPath = path.resolve(process.cwd(), 'src/voice');

export const initVoice = async (): Promise<void> => {
    const mic = new NodeMic({
        rate: 16000,
        encoding: 'signed-integer',
        bitwidth: 16,
        endian: 'little',
        channels: 2,
        threshold: 20,
        fileType: 'wav',
        debug: true,
    });

    const micInputStream = mic.getAudioStream();
    const outputFileStream = fs.createWriteStream(`${voicesPath}/output.wav`);

    micInputStream.pipe(outputFileStream);

    micInputStream.on('data', (data) => {
        // Do something with the data.
    });

    micInputStream.on('error', (err) => {
        console.log(`Error: ${err.message}`);
    });

    micInputStream.on('started', () => {
        console.log('Started');
    });

    micInputStream.on('stopped', () => {
        console.log('Stopped');
    });

    micInputStream.on('paused', () => {
        console.log('Paused');
    });

    micInputStream.on('unpaused', () => {
        console.log('Unpaused');

    });

    micInputStream.on('silence', async () => {
        console.log('Silence');
        mic.stop();
    });

    micInputStream.on('exit', async (code) => {
        console.log(`Exited with code: ${code}`);
        await transcribeWAV();
    });

    mic.start();

    Logger.DEBUG(`Voices path: ${voicesPath}`);

};

const transcribeWAV = async () => {
    try {
        Logger.DEBUG('Transcribing voice...');
        const transcript = await nodewhisper(`${voicesPath}/output.wav`, {
            modelName: "tiny",
            verbose: true
        });

        Logger.INFO(`Transcript: ${transcript}`); // output: [ {start,end,speech} ]
    } catch (error: any) {
        Logger.ERROR(`Error occurred while transcribing voice: ${error.message}`);
    }
};

This is my code.
Output:
Microphone stopped
Found silence block: 21 of 20
Recording has finished with code = 1
Exited with code: 1
[DEBUG] Transcribing voice...
[Nodejs-whisper] Checking file existence: /home/wolf/develop/nodejs/okuuai/src/voice/output.wav
[Nodejs-whisper] Converting file to WAV format: /home/wolf/develop/nodejs/okuuai/src/voice/output.wav
[Nodejs-whisper] Checking if the file is a valid WAV: /home/wolf/develop/nodejs/okuuai/src/voice/output.wav
[Nodejs-whisper] File is a valid WAV file.
[Nodejs-whisper] Constructing command for file: /home/wolf/develop/nodejs/okuuai/src/voice/output.wav
[Nodejs-whisper] Executing command: ./main   -l auto -m ./models/ggml-tiny.bin  -f /home/wolf/develop/nodejs/okuuai/src/voice/output.wav

output.wav seems to be at 16kHz, following the same codec I use to make a test recording using Audacity. The audacity one is properly transcribed, whereas the one using the node-mic doesn't, but they both have exactly the same stream info.

Am I missing something?
Update
Somehow this came out after leaving it to transcribe a while
[09:15:25.440 --> 09:15:35.440]   [BLANK_AUDIO]
[09:15:35.440 --> 09:15:45.440]   [BLANK_AUDIO]
[09:15:45.440 --> 09:15:55.440]   [BLANK_AUDIO]
[09:15:55.440 --> 09:16:05.440]   [BLANK_AUDIO]
[09:16:05.440 --> 09:16:15.440]   [BLANK_AUDIO]
[09:16:15.440 --> 09:16:25.440]   [BLANK_AUDIO]
[09:16:25.440 --> 09:16:35.440]   [BLANK_AUDIO]
[09:16:35.440 --> 09:16:45.440]   [BLANK_AUDIO]
[09:16:45.440 --> 09:16:55.440]   [BLANK_AUDIO]
[09:16:55.440 --> 09:17:05.440]   [BLANK_AUDIO]
[09:17:05.440 --> 09:17:15.440]   [BLANK_AUDIO]
[09:17:15.440 --> 09:17:25.440]   [BLANK_AUDIO]
[09:17:25.440 --> 09:17:35.440]   [BLANK_AUDIO]
[09:17:35.440 --> 09:17:45.440]   [BLANK_AUDIO]
[09:17:45.440 --> 09:17:55.440]   [BLANK_AUDIO]
[09:17:55.440 --> 09:18:05.440]   [BLANK_AUDIO]
[09:18:05.440 --> 09:18:15.440]   [BLANK_AUDIO]
[09:18:15.440 --> 09:18:25.440]   [BLANK_AUDIO]
[09:18:25.440 --> 09:18:35.440]   [BLANK_AUDIO]
[09:18:35.440 --> 09:18:45.440]   [BLANK_AUDIO]
[09:18:45.440 --> 09:18:55.440]   [BLANK_AUDIO]
[09:18:55.440 --> 09:19:05.440]   [BLANK_AUDIO]
[09:19:05.440 --> 09:19:15.440]   [BLANK_AUDIO]

(Please to take in consideration that this is a 0:06 seconds recording)

Ahh, interesting , i will test this with node-mic, also it can be a issue in whisper cpp

Ahh, interesting , i will test this with node-mic, also it can be a issue in whisper cpp

Indeed, script works just fine, issue is when transcribing so it could as well be whisper cpp too.
Do let me know what you can find! :)


Search - Chats: docx/zip/txt/html files are present on Links tab

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: 9.0.54-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/cases/view/3284915
Issue reported by: Applause - Internal Team
Action Performed:
Precondition: there are chats with sent links and files (txt, zip, html, docx)

Go to Search > Chats
Go to Links tab
Go to Attachment tab

Expected Result:
On step 2: Sent messages with links are displayed
On step 3: Sent files are displayed
Actual Result:
On step 2: Sent messages with links are displayed. Sent files (with formats txt/zip/docx/html) are also present on a tab.
On step 3: Sent files are displayed (also files with formats txt/zip/docx/html)
Workaround:
Unknown
Platforms:

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

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

Screenshots/Videos

Add any screenshot/video evidence

https://github.com/user-attachments/assets/e1b4ecc3-1f41-442a-948d-65ed0f0dc7b2
View all open jobs on GitHub

@adelekennedy  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #wave-control

This appears to be a backend filtering issue in the Search endpoint

jsonQuery in the case of attachment;
{"type":"chat","status":"attachments","sortBy":"date","sortOrder":"desc","filters":null,"inputQuery":"type:chat status:attachments sortBy:date sortOrder:desc","hash":34196984,"offset":0}
jsonQuery in the case of links;
{"type":"chat","status":"links","sortBy":"date","sortOrder":"desc","filters":null,"inputQuery":"type:chat status:links sortBy:date sortOrder:desc","hash":2089317297,"offset":0}

We are sending the correct status in each payload, but the Links response includes all chat types.

@adelekennedy I think this is more of a retain bug since migrated customers won't have any chats once they migrate and the links are more of an edge case.

I'm going to close this for now - I think this is something we will want to address in the future but it being a BE bug and a semi-edge case makes me think we should deprioritize


Use Mixamo animations?

For almost a week now I was looking where I could download free vrma animations, and... Couldn't really find it. Found some guides how to convert some other types (mixamo in particular) using say blender. Still haven't gotten to it, but searching again I see that seems underlying library already support mixamo animations: https://github.com/josephrocca/ChatVRM-js and it's even in repo https://github.com/semperai/amica/blob/ff7bb037cabc981600140c8ba89025f3b839d913/src/lib/VRMAnimation/loadMixamoAnimation.ts#L13 but not exposed in any way. As mixamo is free and provides loads of anims, I think it would be of great benefit to allow loading those animations via interface or maybe adding to server dir (like I did with bunch of vrm's) to select from menu. I'm so bummed out by idle only animation, that might look into it myself come weekend or so.

Did a quick and dirty code tweas, it loads :) Will create PR later.

Should be good now.

This is great!
I started on /share and /import/[sqid] pages for making&sharing characters, maybe these come with a default animation? Not sure how to best do this.
I think the fbx files too big to import all of them into repo, but in working on the character creator I set up a s3 compatible bucket for big files.. maybe I can just download all mixamo files and provide the urls? Or a script to allow users to download them to their own computers, so they aren't dependent on internet at all.

Are you sure that there would be no legal trouble from rehosting them? miximo is adobe after all... Imo people can just be pointed where to download and they can make selection :)

I think it's ok. If adobe lawyers message me that this is in violation then I guess they disagree. As far as I understand they just dont want you reselling asset packs using their stuff, since this is a "Game" making it available for "Players" should be fine.
But yes, we should/could point people towards it as well. There's some customization options people may want for these. Have to think more on it.

I think issue can be closed no?


force:source:deploy "No results found" on CLI version 7.85.1

Summary
Short summary of what is going on or to provide context.
After "sfdx update" to 7.85.1, "force:source:deploy" has stopped working for us.  Get the message "No results found" and nothing is deployed.
Steps To Reproduce:
Repository to reproduce: dreamhouse-lwc
NOTE: If your issue is not reproducable by dreamhouse-lwc, i.e. requires specific metadata or files, we require a link to a simple Salesforce project repository with a script to setup a scratch org that reproduces your problem.

Run the command: sfdx force:source:deploy -m ApexClass:GeocodingService -u TARGETUSERNAME
A) Got the message "No results found" and nothing was deployed.  B) If not, run the command again and get the message "No results found".

Expected result
Describe what should have happened.
The specified metadata should have been deployed, like previous versions of the CLI did.
Actual result
Describe what actually happened instead.
Nothing is deployed.  Get the message "No results found".
Additional information
Feel free to attach a screenshot.
SFDX CLI Version(to find the version of the CLI engine run sfdx --version): 7.85.1
SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core)
@oclif/plugin-autocomplete 0.1.5 (core)
@oclif/plugin-commands 1.3.0 (core)
@oclif/plugin-help 3.2.1 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.9.5 (core)
@oclif/plugin-update 1.3.10 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-trust 3.6.0 (core)
alias 1.1.5 (core)
analytics 1.12.1 (core)
auth 1.4.6 (core)
config 1.2.3 (core)
generator 1.1.3 (core)
salesforcedx 51.0.2 (latest-rc)
├─ schema 1.0.3
├─ limits 1.0.3
├─ user 1.1.0
├─ custom-metadata 1.0.11
├─ templates 51.1.0
├─ apex 0.1.4
├─ @salesforce/sfdx-plugin-lwc-test 0.1.7
└─ salesforce-alm 51.0.1
sfdx-cli 7.85.1 (core)
OS and version: Windows 10 Pro 1909

We have a similar issue. I cant pull/push to/from a Scratch org retrieve/deploy from a sandbox.

Duplicate of https://github.com/forcedotcom/cli/issues/851


ISS270: Can't read in directories of files

Thank you for submitting your PR. Please read the template below, fill it out as appropriate, and make additional changes to your code as needed. Please feel free to submit your PR even if it doesn't satisfy all of the requirements below - simply prepend [WIP] to the PR title until it is ready for review by a maintainer. If you need assistance or review from a maintainer, add the label Status: Help Needed or Status: Review Needed respectively. After review, a maintainer will add the label Status: Revision Needed if further work is required for the PR to be merged.
Description
Fixed sol.data.coco.geojson2coco() so that it can handle paths to directories fed to it. In short, it wasn't loading in the full set of images.
While fixing this, I found a bug in sol.vector.polygon.geojson_to_px_gdf() such that it throws an error if you pass it an empty GeoDataFrame (or a geojson with no geometries in it). I added a catch for that.
Closes #270
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
Please describe tests that you added to the pytest codebase (if applicable).
Checklist:

[x] My PR has a descriptive title
[x] My code follows PEP8
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[n/a] I have made corresponding changes to the documentation
[x] My changes generate no new errors
[x] I have added tests that prove my fix is effective or that my feature works
[x] My PR passes Travis CI tests
[x] My PR does not reduce coverage in Codecov

If your PR does not fulfill all of the requirements in the checklist above, that's OK! Just prepend [WIP] to the PR title until they are all satisfied. If you need help, @-mention a maintainer and/or add the Status: Help Needed label.

@jshermeyer this should fix the problem you were having.


alarmo/event MQTT never triggered

Alarmo Version
1.9.9
HA Version
2023.05.1
Bug description
MQTT alarmo/event is never triggered.
I have created an automation to respond alarmo/event (FAILED_TO_ARM or TRIGGERED events) to perform some actions (Alarmo only supports one action by event at the same time) but the alarmo/events aren't sent.
alarmo/state events are sent but not the correspondient alarmo/event
Steps to reproduce
Create an automation to see the events.
I attach the one I have created:
alias: Notificar si falla al ARMAR la alarma
description: ""
trigger:
  - platform: mqtt
    topic: alarmo/event
condition:
  - condition: template
    alias: Failed to Arm?
    value_template: "{{ event == 'FAILED_TO_ARM' }}"
action:
  - service: notify.telegram_urgente
    data:
      message: La alarma NO SE PUDO ENCENDER   {{ sensor }}
      data:
        parse_mode: html
variables:
  event: "{{ trigger.payload.event }}"
  sensor: "{{ trigger.payload.sensors[0].name }}"
mode: parallel

Relevant log output
No response

My mistake, event is triggered. Thanks


More small CLI improvements

Closes https://github.com/xataio/client-ts/issues/365
Improves error message when there's no API key
Closes https://github.com/xataio/client-ts/issues/351
Closes https://github.com/xataio/client-ts/issues/348 See screenshot

Closes https://github.com/xataio/client-ts/issues/348 See screenshot

This does not close the issue because there has not been UX/UI input. Sure, we've tweaked the UI a bit and it's a great improvement, but it still does not look finished.

I wonder if it's time for automated test runs on each command.

I removed the Closes word. I think this should unblock this PR in that regard. There's no urgency for a more polished design, especially when the current implementation is a plain text message.
In another PR we can implement a design from @DavidCnoops or @AlenaNik

@TejasQ @SferaDev I've fixed the canary build. There was a missing dependency. I've added a changeset to bump the version.


[FLINK-11039]  LogicalExchange and HashPartitioner realization

What is the purpose of the change
(For example: This pull request makes task deployment go through the blob server, rather than through RPC. That way we avoid re-transferring them on each deployment (during recovery).)
Brief change log
(for example:)

The TaskInfo is stored in the blob store on job creation time as a persistent artifact
Deployments RPC transmits only the blob storage reference
TaskManagers retrieve the TaskInfo from the blob cache

Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (100MB)
Extended integration test for recovery after master (JobManager) failure
Added test that validates that TaskInfo is transferred only once across recoveries
Manually verified the change by running a 4 node cluser with 2 JobManagers and 4 TaskManagers, a stateful streaming program, and killing one JobManager and two TaskManagers during the execution, verifying that recovery happens correctly.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Jira links
FLINK-11039
RelTimeIndicatorConverter.visit(exchange: LogicalExchange) function realization.
FlinkLogicalExchange realization org.apache.calcite.rel.logical.LogicalExchange and
HashPartitioner is Partitioner that implements hash-based partitioning using Java's Object.hashCode. support org.apache.calcite.rel.RelDistribution.Type HASH_DISTRIBUTED
Review code is ok？

Could you update the description of this PR? That is needed as context for a proper review.

Could you update the description of this PR? That is needed as context for a proper review.

It was implemented as RelTimeIndicatorConverter.visit(exchange: LogicalExchange) function. Then found this function cannot be used directly in SQL statements, just this.


Rewrite OpenTelemetry properties to OTel prefix

Fixes https://github.com/quarkusio/quarkus/issues/32064
Note that I haven't handled Yaml config files as it doesn't work very well when adding a new prefix (it does not separate configuration properties on dots and thus doesn't work properly with Quarkus).
/cc @rsvoboda
@brunobat could you check it makes sense?

@brunobat I removed the sampler ones and added the ones you mentioned. Let me know if that works for you.


[FLINK-27050][BP-1.15][runtime][tests] Removes default RpcSystem instance

1.15 backport of parent PR #19353

Rebased to most recent release-1.15 to include changes around the Dispatcher*Test classes

Merging since the parent PR is approved and there were not conflicts or test failures.


Add Unix timestamp example to README.md

Because it's a common use and I keep forgetting how to do it!

Thanks for the PR!


Calling .shift() on a Go slice fails

I stumbled upon the following error: TypeError: Can't delete from Go slice at shift (native) upon calling .shift() on an array that was set in Go, so I wrote the following tests:
func TestGoSliceShift(t *testing.T) {
	const SCRIPT = `
	a.shift();
	`
	r := New()
	r.Set("a", []interface{}{1, 2, 3, 4})
	_, err := r.RunString(SCRIPT)
	if err != nil {
		t.Fatal(err)
	}
}

func TestJsArrayShift(t *testing.T) {
	const SCRIPT = `
	a = [1, 2, 3, 4];
	a.shift();
	`
	r := New()
	v, err := r.RunString(SCRIPT)
	if err != nil {
		t.Fatal(err)
	}
	println(v.String())
}

Running them I see the first one fails, but the second doesn't. Replacing this line with something like:
	(...)
	s := *o.data
	ns := append(s[:idx], s[idx+1:]...)
	o.data = &ns
	(...)

Fixes TestGoSliceShift. I'll gladly open a PR to fix this, but I figured I'd open an issue first to understand if there's any side effects applying the above change that I'm not envisioning.

This is not how deleting from arrays works in ECMAScript. And the way it does work is not possible to emulate with Go slices, see my comment in #253.
Having said that, this particular case (Array.prototype.shift) theoretically could be supported as long as the Go slice is addressable (i.e. when sliceExtensible is set to true). This support would need to be added to arrayproto_shift. I will consider a PR.

It should work now, however you need to make sure you pass a pointer to a slice, otherwise it will fail on trying to set the length.


Different steady-state values for different regimes?

Hi Junior,
Hope everything is going well with you.
Recently I encountered two problems in specifying steady-state values in the steady_state_model block, and I was wondering if you could help me with them.

I know how to specify different parameters values for different regimes in the parameterization block (e.g. bind(zlb,1), 0; and bind(zlb,2), 0;), but could I specify different steady-state values for different regimes in the steady_state_model block?

It seems that if I only specify the steady-state values for a subset of endogenous variables in the steady_state_model, then RISE will automatically set the steady-state values for the rest of endogenous variables to zero. Is that true?

Cheers,
Zexi

Hi Zexi,
You write the steady state block as if the model was a constant-parameter model. RISE will call the block with the parameters of each regime and if a parameter is changed in the block, the changed value will be assigned to the corresponding regime and not to the others unless you impose the steady state in which case the value calculated will be assigned to all regimes. In brief you don't need to think about whether the model is switching or not when writing the steady state block.
Your intuition concerning the values for the variables you do not declare is correct. RISE will try zero. This means you do not need to declare the variables for which the steady state is zero.
Cheers
J.

On 22 Jun 2017, at 14:28, Zexi Sun<EMAIL_ADDRESS>wrote:
Hi Junior,
Hope everything is going well with you.
Recently I encountered two problems in specifying steady-state values in the steady_state_model block, and I was wondering if you could help me with them.
I know how to specify different parameters values for different regimes in the parameterization block (e.g. bind(zlb,1), 0; and bind(zlb,2), 0;), but could I specify different steady-state values for different regimes in the steady_state_model block?
It seems that if I only specify the steady-state values for a subset of endogenous variables in the steady_state_model, then RISE will automatically set the steady-state values for the rest of endogenous variables to zero. Is that true?
Cheers,
Zexi
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Got it! Thanks so much for your help Junior!
Best,
Zexi


Add links to a comment

For Discord or email it would be great to have a link to a comment for an article. For example I want to point to this comment in Discord:

An example is github or Slack. Here we can link to a certain contribution / comment. For example this comment has the link https://github.com/serlo-org/athene2/issues/822#issue-387329168

We might add something like that with the new commenting system. I'll keep it in mind

Actually, moving to the commenting system repo


Errors In Example JSON Data

When using the following example component file,
https://raw.githubusercontent.com/EasyDynamics/oscal-content/manual-fix-of-component-paths/examples/component-definition/json/example-component-min.json,
we get the following error:
Yikes! Something went wrong loading the OSCAL data. Sorry, we'll look into it. (Unexpected token : in JSON at position 3).
Steps to reproduce

Go to component viewer
Enter the above component file in the component url box
Click on the reload button

Acceptance Criteria

The above error does not occur in the example-component-min file or in any of the other example files

Error seems to be specifically due to this line having a 404
https://github.com/EasyDynamics/oscal-content/blob/58af5c83ad7ab5620809c5701877a4b959516d25/examples/component-definition/json/example-component-min.json#L43

We didn't update the minified versions (*-min.json) in any of our temporary workarounds.
These issues are known to NIST and FedRAMP and fixes are planned on their side.


Use non virtual call of 'family or assembly' methods of base class.

PR Summary
Consider protected internal access modifier for non virtual calls of base class overridden methods.
Fix #7622
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[ ] Change is not breaking
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[x] Not Applicable
OR
[ ] User-facing Documentation needed

[ ] Issue filed - Issue link: #7622

Testing - New and feature

[ ] Not Applicable or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

@PowerShellTeam, looks like the fix falls into bucket 3 of breaking changes.

@yurko7 Thank you for the contribution!


ModuleNotFoundError: No module named 'six.moves.collections_ab

With version 2.02 I get this ModuleNotFoundError: No module named 'six.moves.collections_ab error when trying to run any of our stix scripts, for one example:
from stix2.v20 import EmailMIMEComponent, Artifact, File

attachment_type = 'application/pdf'
attachment_binary = b'ZW1haWwgYXR0YWNobWVudCBjb250ZW50cwo='
hashes = {
    'MD5': 'ffa4344d434659d6fc69eca166f870a7',
    'SHA1': '0e518dcead742e7127345d15ca7eba694b50d0fa'
}
artifact = Artifact(hashes=hashes, payload_bin=attachment_binary, mime_type=attachment_type)

email_mime_component_attachment = EmailMIMEComponent(
    body_raw_ref="0"
)

print(email_mime_component_attachment)

This happens both after upgrading to 2.02 and with a clean install of stix2 on a fresh virtual enviornment.

Hi @Lastrellik! this issue has been resolved on version 2.0.2 of the library. I tested locally (see attachment) and was able to run the script without problems. If you update via PyPI it should have updated your six dependency to something higher or equal to 1.13.0. Another suggestion would be to check your pip, setuptools and wheel packages are up-to-date on your environment. I will close this since we think it has been resolved.
duplicate #422


BarbRenderer::performRendering assumes extent dimensions are at least 3

BarbRenderer.cpp:316 tries to access rMinExtents[2] which is out of bounds.

I'm unable to reproduce this one.  Stas, can you share the steps that you took for this?


Glossary author : show and author Glossary owned Category tree

Navigating from Glossary in the Ui, there will be a button to show categories from the selected glossary. There are 2 useful ways of showing categories:

a list of the top categories, under which it is possible to navigate
a list of all categories owned by the glossary

By default we will show the top categories.
In either view is will be possible to

edit the selected category
delete a selected category
add a category - this will  be added under the parent glossary and have not parent category.


fix: remove deprecated timezone.utc from changes follower

PR summary
Remove deprecated timezone.utc for datetime.UTC from changes follower.
Fixes: #565
Note: An existing issue is required before opening a PR.
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the
Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

@emlaver thank you for the review, but I'm going to close it. It seems that I the root cause for the deprecation is not our use of timezone in follower, but rather dep of python_dateutil, so the warning whould go away once they releaze compatible version and we get dependabot PR


Implement compaction of the kvindex

The current implementation of the compact endpoint is just focused on cleaning up revoked leases, not on the kvindex at the moment.

Can compaction now be ticked off on https://github.com/microsoft/LSKV/issues/35?


Supporting C# 6.0?

(Original issue 1138 created by fatbigbright on 2015-08-11T15:32:13.493832+00:00)
Using pygments 2.0.2. Color of the following code does not seem good on html with vim style:
#!C#

var dic = new Dictionary<string, string> {
    ["love"] = $"{a} loves {b}."
   ,["hate"] = $"{a} hates {b}."

};

The source code segments contains new features(String Interpolation & Index Initializer) of C# 6.0.

(Original issue was assigned to tshatch)

(Original comment by tshatch on 2015-10-07T13:20:47.577262+00:00)
Can you point me at a doc of what's new in C# 6.0, so we can support all the new features?

(Original comment by fatbigbright on 2015-10-09T03:17:47.612654+00:00)
Thanks for reply, Tim. All I can find is a video on Channel 9 which introduces change of C# 6.0. But I am not sure whether this video is involving all of the changes.

(Original comment by tshatch on 2015-10-09T03:41:34.965721+00:00)
https://github.com/dotnet/roslyn/wiki/New-Language-Features-in-C%23-6 seems reasonably authoritative, and includes both the examples you mentioned.  I was hoping for something more grammar-like, but this will do.

(Original comment by fatbigbright on 2015-10-09T04:34:41.474681+00:00)
That's great! Thanks for sharing, Tim.

(Original comment by tshatch on 2015-10-17T01:10:38.258928+00:00)
I'll try to get to this in time for next release.


Fix a few Markdown tests

I was just looking at some tests in tests/markdown/mustache-span.test.js and there are a handful with FIXME tags that seem like they are fixed.  "Testing" isn't something I've really looked at until now, so before I submit a PR to just clean these up I thought I'd check my work.  If I remember right, @AlexeySachkov is the person to talk about tests with.......?
test('Renders a mustache span with text and class', function() {
	const source = '{{my-class text}}';
	const rendered = Markdown.render(source);
	// FIXME: why do we have those two extra spaces after closing "?
	expect(rendered).toBe('text');
});

There are 4 or 5 similar tests that have the same or similar "FIXME" tags about extra spaces, and it looks like the expected result in the test has just been changed to match the undesired behavior rather than fixing whatever is causing the spaces.  But on the live site those extra spaces aren't present....so not sure how it passes this test since it is expecting the spaces to be there?

Hold the phone....I guess maybe the browser dev tools is just automatically removing those spaces so I think they aren't there.  But when I "fix" the test, it fails.
Okay.

Hi @Gazook89,

I guess maybe the browser dev tools is just automatically removing those spaces

Yes, most likely this is what happening.

There are 4 or 5 similar tests that have the same or similar "FIXME" tags about extra spaces, and it looks like the expected result in the test has just been changed to match the undesired behavior rather than fixing whatever is causing the spaces.

My aim back than was to simply at least enable some testing and I decided that a couple of extra spaces which are not user-visible (i.e. they are in between tag arguments, not inside its "body") not require immediate bug fix. We might even decide that it doesn't worth fixing at all


Unable to install or update terminal from Win11 store

Windows Terminal version
No response
Windows build number
No response
Other Software
No response
Steps to reproduce

However, the preview version can be installed
Expected Behavior
No response
Actual Behavior
none

What build of windows are you on /?

What build of windows are you on /?

This honestly just sounds like a bug in the Store. I'd file feedback using the Feedback Hub app, on the Microsoft Store app.
Additionally, you can always manually install the Terminal using the .msixbundle from our Releases page

This honestly just sounds like a bug in the Store. I'd file feedback using the Feedback Hub app, on the Microsoft Store app.老实说，这听起来像是商店中的一个错误。我会使用 Microsoft Store 应用上的反馈中心应用提交反馈。
Additionally, you can always manually install the Terminal using the .msixbundle from our Releases page此外，您始终可以使用 .msixbundle 我们的“版本”页面手动安装终端

Ok thanks


[engine] Do not auto-submit your own withdrawals as Alice

Currently, Alice submits withdrawals immediately when they are signed. This makes sense for Bob's withdrawals since Bob needs it immediately. However, Alice does not need to submit her own withdrawals immediately. Alice should hold onto her withdrawal commitments and only submit them when it makes sense (i.e. gas is low). Ideally, we can batch the commitments but even without batching it makes sense to hold onto them until later.

[ ] Disable withdrawal submission by default for Alice's own withdrawals.
[ ] Add config item to enable the above.
[ ] Add endpoint to submit withdrawal(s) later.
[ ] Endpoint should check if the withdrawal has already been submitted by checking the nonce against submitted txs.

Alice has never been autosubmitting her own withdrawals, see code here

Duplicate of #358


Cookies handling with JSONHTTPClient

I my current project I am using +(void)postJSONFromURLWithString:(NSString*)urlString params:(NSDictionary*)params completion:(JSONObjectBlock)completeBlock; method to create account and log in my application for the very first time . For secound and onwards, log in call is not there, application directly opens the user's profile screen. But when I am updating user profile (name, contact number etc.), I am getting response status code 403 from by the statement
 NSLog(@"Response status code = %i", (int)response.statusCode);

added in implementation of method
+(NSData*)syncRequestDataFromURL:(NSURL*)url method:(NSString*)method requestBody:(NSData*)bodyData headers:(NSDictionary*)headers etag:(NSString**)etag error:(JSONModelError**)err

403 is generally invoked due to authorization failure in server side.
Is there any way to see what are the cookies are going to server side while I am making an API call with +(void)postJSONFromURLWithString:(NSString*)urlString params:(NSDictionary*)params completion:(JSONObjectBlock)completeBlock;?

You could MITM the requests to check the headers being sent. http://mitmproxy.org does this wekk

Also, as usual, JSONHTTPClient is designed to provide a very simple implementation. So for more complex use cases, probably best to go for another networking library.


how to reduce noise and echo

dear author,
when i try to use huawei pad to join a livekit room,the echo and noise is very loudly . Is there any funcion to solve the issue by code in the livekit_server? thanks anyway!

Hey @Hollymingyi, as an SFU, this isn't something livekit-server would be responsible for. Mobile SDKs should have solid echo cancellation. You just have to put the device in communication mode using methods provided by our SDK. Please reference the docs for the appropriate SDK for details.

ok，thank u，i will have a try


Forum improvements

deploy this before urbit/fora@160a2d0

I assume there's stuff I need to add to the headers of existing posts too?

Those changes are mutually backwards compatible so I just dropped those in
with sed.
On Friday, 29 July 2016, Raymond Pasco<EMAIL_ADDRESS>wrote:

I assume there's stuff I need to add to the headers of existing posts too?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/224#issuecomment-236325657, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhtXtp4a9KKejOmtexeDmiwG6l2wiks5qaptzgaJpZM4JYqO7
.


Change requests to enable SOLO wallet to use XUMM

I have 3 change requests for the SOLO Wallet to use XUMM.

issued_user_token param (stored in the device) can be set to submit().
Without API keys and secret, the frontend turns XUMM on/off.
The current way to initialize SologenicTxHandler wiht XUMM is as follows. As for the frontend, XUMM API key and secret should not be set in the frontend for security.

const sologenic = new s.SologenicTxHandler(
  // RippleAPI Options
  {
    server: appConfig.server // Kudos to Wietse Wind
  },
  {
    queueType: "hash",
    hash: {},
    signingMechanism: new XummSigner({
      xummApiKey: XUMM_API_KEY,
      xummApiSecret: XUMM_API_SECRET
    });
  }
);

clientType allows the backend to switch the XUMM API key and secret on the backend
Adding clientType into SologenicTxHandler is https://github.com/sologenic/sologenic-xrpl-stream-js/pull/21

const sologenic = new s.SologenicTxHandler(
  // RippleAPI Options
  {
    server: appConfig.server // Kudos to Wietse Wind
  },
  {
    queueType: "hash",
    hash: {},
    // Specify mobile or desktop
    clientType: "mobile",
  }
);

I don't understand the change in functionality you're looking for items 2 and 3.  The xumm API key and secret need to be be assigned to the signing mechanism somehow so I am not sure how you intend to do this in your mobile client application.  Item 1 is complete, where you can now pass the issued_user_token as part of the transaction itself.
See src/tests/signing/xumm.spec.ts:117 for an example transaction payload.

Item 1 is complete, where you can now pass the issued_user_token as part of the transaction itself.

@okanaganrusty  Thanks for adding this change for No. 1.

I don't understand the change in functionality you're looking for items 2 and 3. The xumm API key and secret need to be be assigned to the signing mechanism somehow so I am not sure how you intend to do this in your mobile client application

My point is that in the frontend (react native project), there is no secure way to store xumm API key and secret. In general, the frontend should not know any secrets, etc. for security reasons. In order to avoid putting (exposing) the API secret, etc.  on the frontend, I think that the backend should have a way to make an encrypted connection to the API like JWT tokens.
The xumm api docs also mentions the same thing as follows:  https://xumm.readme.io/docs/call-xumm-platform

! Anyone in possession of your X-API-Secret can create payloads (sign requests) on behalf of your application. If abused, this can damage the reputation of your application immensely. Please never implement the xumm API in a scenario where calls are made from the client side: only call the xumm API from your application backend, always ensuring you keep your xumm API secret safe on the server side.


add reset decorator for backoffs, refactor and add tests, lots of oth…

…er stuff

want this on my own repo


Bump commons-io to 2.13.0

We pin an old version of commons-io, released in 2020. commons-io had a bunch of improvements, including performance / memory footprint [1].


[DEV-2174] add fee blockchainFactor

Release Checklist
Pre-Release

[ ] Check migrations

No database related infos (sqldb-xxx)
Impact on GS (new/removed columns)

[ ] Check for linter errors (in PR)
[ ] Test basic user operations

Login/logout
Registration
Update user data
Create/delete payment routes

Post-Release

Test basic user operations
Monitor application insights log

Update existing addition fee + blockchainFactor after merging


Tokens on ionic serve and ionic emulate -l

We have learned that with Ionic we need to use storage: 'localStorage' #93 . But this helps only on real device (ionic run).
I could not get auth-tokens sent on ionic web (ionic serve). That really slows down my development since for everything I need current_user.
For emulator with live reload (ionic emulate -l) also the tokens are not sent (somehow validateUser is not called automatically on page load).
When I run on emulator without live reload, than works fine and I don't need to login again (although I need to run ionic emulate before each test).
Did anybody succeed to have already logged in user in ionic web or emulator with live reload ?

I have the same issue with $auth.submitLogin. The plugin is returned by the server but not stored in the locaStorage when I launch the app in the brower
This is a new issue but downgrading to an older version of the plugin don't seem to change anything.

I solved it by my own. For me, the issue was related to CORS problems with the browser and filtered headers properties. Using Ionic proxy solve the problem.
Check this article: http://blog.ionic.io/handling-cors-issues-in-ionic/
Hope it could help.

This is not a CORS issue (I'm using rails rack-cors that allow *, and I have no problems fetching other resources like api/posts on ionic serve or ionic emulate -l).
Problems is that on ionic serve or ionic emulate -l auth tokens are not sent (on ionic emulate or ionic run auth tokens are sent) .

The CORS security policies seems to have been recently updated in the major browsers. All the response body are accepted but the headers are often filtered.
If you want to check if your issue is related to the same issue I have faced, set up an http interceptor and log all the response headers. You should see the access-token in the response for the signin request.
I can advice you this very nice tutoriel to set up a ionic proxy to solve CORS issue: http://blog.ionic.io/handling-cors-issues-in-ionic/

Yes @gouroujo you are right. I will investigate how. I missed this cors issue before. Thank you.

@duleorlovic I would love to know any outcome you had from your research!

Running into same issue. I am only able to test this properly on a real device, which makes it really tedious. But I guess this is an Ionic issue in general, nothing about ng-token-auth itself.


Needs Laravel 9-compatible release

Please could you update package requirements to allow Laravel 9 upgrades? Thanks!

Done!


chetelolel

N.3s of chetelaol
his/her intoxication/dizziness
confirm? Charl confirmed.

In the context of inebriated, we would say "cheltelolel" derived from
"cheltelaol." There is also "chetelaol" which can also be used for
dizzy(iness). These are what I am more used to, I guess.
Examples:
Ng mlo er a party e meral milchetelaol me a bol rei eng cheltelolel me ng
oldidiu.
A kora di chetelaol le ng locha ngesonges a cheliuek.
Ng meral mekngit lomekall me ng di mo mengetelaol a btelud.
A rechad omekakou er ngak ra obekuk ra Ngesis el kmo ng di chetelaol meng
diak lodengei a ngerang. (Ediul, ngka dirrek el obekul a Charl! Lol!)
On Tue, Jan 17, 2023 at 7:41 PM John Bent @.***> wrote:

N.3s of chetelaol
his/her intoxication/dizziness
confirm? Charl confirmed.
—
Reply to this email directly, view it on GitHub
https://github.com/tekinged/missing/issues/397, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXYSPXXRUDIBY4FIHZ6F3VDWS5J5LANCNFSM6AAAAAAT6RYBGA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


fix: crawl directories recursively on drop and return all the files

Resolves #183

🐝 PR preview in Swarm
Preview URL: https://bah5acgzasxy5xlhjtgq2pz3beir7nxcpwi53l7zisjhal6vhlzefbzcuuuba.bzz.link
Swarm Hash: 95f1dbace999a1a7e7612223f6dc4fb23bb5ff28924e05faa75e4850e454a502
Commit Hash: 4eb82341b911f5cd627821328366aca4d885a147
Commit Message: fix: crawl directories recursively on drop and return all the files


Swift OSS has multiple projects

Thought this better reflects what the brief is about. What do you think, @jessesquires?

Can we also do something about the Spell Checker? It is more annoying than useful imo. 😐

Can we also do something about the Spell Checker?

Definitely! I just haven't had time. 😅
Lots of good docs on Danger online.

Lots of good docs on Danger online.
Agreed! Have been doing some things with Danger in the past few days, so I should be able to take a look at it soon :)


New SpikeDetekt doesn't give same results as old SpikeDetekt

Using the same (default) parameters, new SpikeDetekt (phy 0.3.0) returns slightly more spikes, and differently-timed spikes to phy 0.2.0.
new-old-npy.zip

(Attached file is using hybrid-10sec.dat)

are the new results sensible or nonsensical?
have you tried with a single chunk? overlapping is handled differently (using dask), that might be one explanation

New results look sensible at first glance (haven't investigated the differences too closely yet) but there are differences around 1000 samples into the dataset, so << 1 second (the chunk size)


Support for KKManager's mod enable/disable feature

So KKManager has a feature that allows users to enable/disable mods. This is achieved by changing a mod's file extension from .zipmod to .zi_mod. I was hoping BDSM could support this feature by considering .zi_mod files when deciding which mods not to download.
P.S. this might be similar to issue #4 but I felt it was different enough that it warranted its own post.

This would probably be good to implement just so that people who have disabled mods in that fashion don't have that disrupted. It's not a huge priority, but I suspect it will be fairly trivial and can be done for v0.3.


add search metrics

ACM-15663. Adds search metrics: https://github.com/stolostron/metrics-chronicle/blob/main/docs/acm/component/observability-search/metrics.md

cc @bjoydeep

Thanks a lot @smcavey for putting this together. Some minor promql query tweaks based on metric type.
So now you have added -

searchAPIRequestDuration
searchAPIDBConnectionFailed
searchAPIDBQueryDuration
searchIndexerRequestCount
searchIndexerRequestDuration
searchIndexerRequestsInFlight
searchIndexerRequestSize

So talking causal -
If 1 is high, its bad. And 2 is bad as well. So if we have high 1 or 2, we have a problem.
1 depends on 3, right? And 3 depends on 4,6,7, and 5 ?
Just something to think off. These relationship and analysis will be a part of a different PR.

BTW. dont we capture the number of api requests to the search api ?

@bjoydeep Regarding causality, I don't think we could necessarily say that 4, 5, 6, or 7 affects 3 unless we take into the picture postgres memory/cpu since the api and indexer have separate connection pools. But if 4, 5, 6, or 7 spike AND postgres memory/cpu spike, then we might be able to say they cause a spike in 3


Fix broken links on plugin docs

Description
Fix broken links for "What can plugins do" and example plugin.
Motivation and Context
Make docs great again. Fix 404 link.
Types of changes

[ ] Refactoring/add tests (refactoring or adding test which isn't a fix or add a feature)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] I have updated the documentation accordingly
[ ] I have updated the CHANGELOG with a summary of my changes
[ ] My changes have tests around them

Thank you!


SQL Commands - Create/Drop User

The following are two sections, each for the documentation regarding the 2 new commands,
create user and drop user. They are simply followed one by another in this page, but they are supposed to be separated and put each in his own file.
SQL - CREATE USER
Creates a user in the current database, with the specified password and an optional role.
Note that if a role isn't specified, a default role ("writer") is used.
Note this is simply a wrapper around OUser and ORole tables; Look up Security for more details.
Syntax
CREATE USER <user name> IDENTIFIED BY <password> [ROLE <role name>]

Examples
Creates a new user called 'Foo', with password 'bar', and role 'admin'
create user Foo identified by bar role admin

Creates a new user called 'Bar', with password 'Foo'
crete user Bar identified by Foo

To know more about other SQL commands look at SQL commands.
SQL - DROP USER
Drops a user from the current database.
Note this is simply a wrapper around OUser table; Look up Security for more details.
Syntax
DROP USER <user name>

Examples
Drop a user called 'Foo'
drop user Foo

To know more about other SQL commands look at SQL commands.

@matanshukry Thanks for this PR! We're in RC phase, I'll merge it for sure as soon as we'll switch to 2.2-SNAPSHOT.

lvca - There seem to be more conflicts. Please comment again when the project has moved to 2.2-SNAPSHOT, I'll fix it and push again then (it will send me an email notification).

@matanshukry Now develop is 2.2-SNAPSHOT ;-) About this what do you think on supporting multiple roles syntax like:
CREATE USER <user name> IDENTIFIED BY <password> [ROLES <role name>, <role name>*]

Example:
CREATE USER jay IDENTIFIED BY miner ROLES genius, creative

or
CREATE USER <user name> IDENTIFIED BY <password> [ROLE [<role name>, <role name>*] ]

Example:
CREATE USER jay IDENTIFIED BY miner ROLE [genius, creative]

I stayed with a single keyword, seems more consistent.
You can either do ROLE [admin, reader, etc] or ROLE admin
Also, merged again with develop.

Thanks!

I saw test cases are missing, I'm going to write them.


website portfolio.md updated

portfolio.md for the website was updated

Portfolio has already been added.
Closing as duplicate


Add Australia shields

Fixes #397.
The shape used by Aus/NZ State Routes is renamed to "fishhead".
Tagging transition work is currently under way. We'll need to wait for that to be finished before a tile update.

Perth, Western Australia

Humpty Doo, Northern Territory

Adelaide, South Australia

Brisbane, Queensland

Warwick, Queensland

Newcastle, New South Wales

Canberra, Australian Capital Territory

Melbourne, Victoria

Hobart, Tasmania


Both mido.get_input_names() and mido.get_output_names() ports listed twice

Hello, openSUSE TW with python38 and mido-1.2.10.
With mido.get_input_names() and mido.get_output_names() ports are listed twice, also I'm not sure if they are correct..
mido.get_input_names():
['Midi Through:Midi Through Port-0 14:0', 'SAMSON Graphite 49:SAMSON Graphite 49 MIDI-Out 16:0', 'SAMSON Graphite 49:SAMSON Graphite 49 Controller 16:1', 'SAMSON Graphite 49:SAMSON Graphite 49 Port3 16:2', 'SAMSON Graphite 49:SAMSON Graphite 49 Port4 16:3', 'SAMSON Graphite 49:SAMSON Graphite 49 Controller 16:4', 'UMA25S:UMA25S MIDI 1 20:0', 'Midi Through:Midi Through Port-0 14:0', 'SAMSON Graphite 49:SAMSON Graphite 49 MIDI-Out 16:0', 'SAMSON Graphite 49:SAMSON Graphite 49 Controller 16:1', 'UMA25S:UMA25S MIDI 1 20:0']
mido.get_output_names():
['Midi Through:Midi Through Port-0 14:0', 'SAMSON Graphite 49:SAMSON Graphite 49 MIDI-Out 16:0', 'SAMSON Graphite 49:SAMSON Graphite 49 Controller 16:1', 'UMA25S:UMA25S MIDI 1 20:0', 'Midi Through:Midi Through Port-0 14:0', 'SAMSON Graphite 49:SAMSON Graphite 49 MIDI-Out 16:0', 'SAMSON Graphite 49:SAMSON Graphite 49 Controller 16:1', 'UMA25S:UMA25S MIDI 1 20:0', 'Client-128:qjackctl 128:0']
screenshot with alsa connections from Qjackctl attached.

Same problem on Raspberry Pi 3 Model B+, Bullseye.

Same problem on Raspberry Pi 3 Model B+, Bullseye.

Workaround: list(set(mido.get_input_names()))
Also, IMHO, the name is too long. IMHO it should show only the part after ":" IN my case: SAMSON Graphite 49:SAMSON Graphite 49 Port3 20:2' should be SAMSON Graphite 49 Port3 20:2

Thanks for the workaround!

Echoing this. If this is a problem, casting to a set would just cover the issue.

This usually happens because the backend exposes multiple APIs. Also the names of the devices are decided by the OS stack, nothing we can really do about it.

May I ask if I'm understanding this correctly and this is happening on Raspberry Pi Bullseye because mido/rtmidi has been compiled to support both ALSA and JACK?

This usually happens because the backend exposes multiple APIs. Also the names of the devices are decided by the OS stack, nothing we can really do about it.

May I ask if I'm understanding this correctly and this is happening on Raspberry Pi Bullseye because mido/rtmidi has been compiled to support both ALSA and JACK?

Maybe, yes.
The names are provided by RtMIDI via python-rtmidi since you're using the default backend. You may want to ask there if you need a definitive answer.


Convergence issue under pseudo-huber loss for simple experiment data

Hi, I am recently conducting some numerical experiments for a new tree boosting trick. I designed a simple example for robust regression, in which there are three data points involved: (1.2, 1.5, 2.3, 100), (1.2, 1.5, 2.3, 300), and (1.2, 1.5, 2.3, 1000). The heading 3 value are features, and the last value is the regression target. I applied XGBoost with pseudo-huber error to fit this data, with huber-delta set as 1. Since pseudo-huber error is a smoothing variant of absolute-error, so the fitted value is expected to be around 300. However, no matter how hard I tried(e.g. by tuning the regularization weight lambda as well as the learning rate), the fitted value was consistently stuck in a large number, even when there were  just a few boosting iterations and large regularization weights were applied. Since the gradient of pseudo-huber error is bounded in absolute value by the huber-delta, this phenomenon was quite unexpected. Does anyone know how to resolve this issue?

For your information, this is the corresponding R script
library(xgboost)
data <- data.frame(X1=rep(1.4,3),
X2=rep(2.7,3),
X3=rep(3.5,3),
Y=c(100, 300, 2000))
train.input <- xgb.DMatrix(data=as.matrix(data[,1:3]), label=data$Y)
test.data <- as.matrix(data.frame(X1=1.4, X2=2.7, X3=3.5))
num.expr <- 1000
bst <- 1e10 #record the best loss value
best.res <- 0 #record the best fit value
set.seed(2023)
slope <- 1.0
pseudo.huber.loss <- function(x, y, slp) {
d <- x - y
cst <- sqrt(slp * slp + d * d) - slp
return(sum(cst))
}
for (i in c(1:num.expr)) {
randm <- runif(2)
model <- xgb.train(params=list(huber.slope=slope,
lambda=randm[1],
#tree.method='exact',
learning.rate=randm[2],
max.depth=1L),
data=train.input,
eval.metric='mae',
objective="reg:pseudohubererror",
nrounds=20)
res <- predict(model, test.data)
cost <- pseudo.huber.loss(rep(res, 3), data$Y, slope)
if (cost < bst) {
bst <- cost
best.res <- res
}
}
print(res)
print(bst)

Apologies for the slow reply, I will look into it next week.

Has this been solved?


Shortcut 2 disaster

I was just reading https://github.com/openstreetmap/iD/issues/9395#issuecomment-1334134084
So decided to give it a try. I was enjoying adding nodes to a way with the spacebar, until I realized that two taps of the space bar in the same spot didn't end the line. (It's "mouse over men": You got to have a real mouse if you want to click in the same spot to end a way, apparently.)
That is bug one.
So then I put in the cursor on the Line button. I learned via the help balloons about the shortcut "2".
So I guessed that maybe "2" is the way to end the line using keyboard shortcuts.
So, okay, I started the line a/k/a way via this 2 shortcut.
And happily added nodes using the space bar.
And, of course sooner or later it is time to end the way, so to end it I just reached for the 2 key on my keyboard and guess what happened...
Kabam! Entire painstakingly entered way blown to smithereens. Eliminated from the face of the earth.
That is bug two.
So now you're saying, "Dry your weeping eyes and simply reach for the  undo/redo buttons."
Well the undo/redo buttons deny any hint that any of this ever happened.
That is bug number three.
By the way, it's that "2" that wiped the undo memory, not the space bar to blame.
Digging in the help manual, we learn we're supposed to hit Enter. "My mistake," as Pee Wee Herman might have said.
Well it should also say, "Don't hit 2 again because something bad will happen."

While the above might not be a perfect issue report, I'd like to thank Jidanni for rising the issue, and try to summarize steps for reproduction:

Begin drawing a line or an area, and draw several points
While still in drawing mode, hit either 1,  2, 3, or Delete on the keyboard

As the result, the entered data is iretrievably gone, and cannot be restored by Undo.
Preferably, neither of the shortcuts (and probably none at all, except Backspace) should have any effect while in line drawing mode. Alternatively, Undo should restore the last drawn state.

P.S. We do need some shortcuts to work in this mode, such as the ones that (de)activate visibility of various features (B for Backgrounds, U for Map features or G for Green changes).
But should anyone want to tackle this, please also get rid of the goddam L for Locate me (which has usability of -1) (#9128, #8474).


PTFE-677: healthchecks

Codecov Report

Merging #353 (0d1fcec) into main (3db74c7) will decrease coverage by 27.20%.
Report is 1 commits behind head on main.
The diff coverage is 24.05%.

@@             Coverage Diff             @@
##             main     #353       +/-   ##
===========================================
- Coverage   84.53%   57.33%   -27.20%
===========================================
  Files          23       24        +1
  Lines         666      729       +63
===========================================
- Hits          563      418      -145
- Misses        103      311      +208

Flag
Coverage Δ

api
57.33% <24.05%> (-4.53%)
:arrow_down:

unit
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

runner_manager/jobs/healthcheck.py
0.00% <0.00%> (ø)

runner_manager/models/runner_group.py
62.22% <36.36%> (-34.17%)
:arrow_down:

runner_manager/models/runner.py
70.49% <50.00%> (-29.51%)
:arrow_down:

runner_manager/models/settings.py
83.01% <100.00%> (-16.99%)
:arrow_down:

... and 9 files with indirect coverage changes

[ ] Double check test coverage see if any gaps needs to be filled.


Test data links

The links to test data to be utilized with phy's template-gui are broken or missing.  Any chance they could be fixed?

Yes, see https://github.com/kwikteam/phy-contrib/pull/87, let me know if it works


Check LIDAR point cloud

The standalone lidar sensor uses the velodyne plugin under the hood to publish a point cloud to ROS. It is not clear whether this is working for all users. In addition, we need to check whether it is outputting a 145x145 point cloud or a 1450x1450 point cloud. The latter is better if possible.

How to verify:

Run: roslaunch nps_uw_sensors_gazebo uw_lidar_standalone.launch
In a separate terminal, run rostopic echo -n 1 /nps_uwl_points > lidar_msg.txt
Check that the point array (line 43) has the expected number of values

Reading the point array

The data outputted appears to be a raw array of bytes, but represented as a list with one entry for the value of each byte.
A lidar data point requires 22 bytes to store in total
Therefore the total number of points in the array is the number of entries divided by 22.
At 145 x 145 vertical and horizontal samples, we expect 462550 entries. This is what we get.

Setting the resolution

The actual number of points published is equal to the number of samples multiplied by the resolution.
Attempting to output a full 1450 x 1450 point array requires 46,255,000 bytes (about 44 MB) at each time step. This will cause a crash.
We are instead using 1450 x 1450 samples with a resolution of 0.1, which produces a 145 x 145 point array.
There is no difference in the output when using 145 x 145 with a resolution of 1 and 1450 x 1450 with a resolution of 0.1. The documentation for the resolution parameter is here. It seems to say the opposite of what I would expect.

Questions for OR

What is the impact, if any, of the resolution tag in the gpu_ray sensor?
Is the documentation correct?
Is there any advantage to using more samples with lower resolution?

This is working as expected. In the future we may want to look for ways to increase the number of samples. I have also made a note to reach out to OR to get answers to questions about the resolution setting.


Fix for phone number validation.

I have update the fix and is in the 0.7.7 release.
$ bower install --save structurejs


Triplanar terrain fix for gdx-gltf upgrade

The triplanar fix for gdx-gltf upgrade PR.
This is the exception if I use triplanar terrain with gdx-gltf-upgrade branch:
[11:29][Trace][Outline] Project changed. Building scene graph.
[11:29][Fatal][Log] com.badlogic.gdx.utils.GdxRuntimeException: Shader compilation failed:
Fragment shader:
0:385(13): error: v_position' undeclared
0:385(13): error: type mismatch
0:385(13): error: operands to arithmetic operators must be numeric
0:386(13): error: v_position' undeclared
0:386(13): error: type mismatch
0:386(13): error: operands to arithmetic operators must be numeric
0:387(13): error: v_position' undeclared
0:387(13): error: type mismatch
0:387(13): error: operands to arithmetic operators must be numeric
0:390(37): warning: uvX' used uninitialized
0:391(37): warning: uvY' used uninitialized
0:392(37): warning: uvZ' used uninitialized

    at net.mgsx.gltf.scene3d.shaders.PBRShaderProvider.checkShaderCompilation(PBRShaderProvider.java:516)
    at net.mgsx.gltf.scene3d.shaders.PBRShaderProvider.createShader(PBRShaderProvider.java:487)
    at com.mbrlabs.mundus.commons.shaders.MundusPBRShaderProvider.createShader(MundusPBRShaderProvider.java:29)
    at com.badlogic.gdx.graphics.g3d.utils.BaseShaderProvider.getShader(BaseShaderProvider.java:34)

In this fix I've added v_position as method parameter into getColor.
Plus I've upgraded gdx-gltf version to 2.2.1, because the jitpack doesn't find the current (7d70839) revision in its repo.
I've used this changes: https://github.com/mgsx-dev/gdx-gltf/compare/7d70839067...2.2.1 and I've updated only material.glsl with iridescenceThicknessTextureFlag flag.

I've found a better solution for the issue that I've changed the order of mateial.glsl and env.glsl files.


⚠ Processors has degraded performance

In 024b077, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 44 ms

Resolved: Processors performance has improved in 32e233f.


Squashed all layers

This PR tries to solve the squash-with-all-layer resolver issue, aligned to the newest version of syft.
Please let me know how to proceed further, I guess the solution here is not perfect, but it does knows how to handle deleted packages.
part of - https://github.com/anchore/syft/issues/15

@tomersein - I know very little about the Syft internals, and I'm trying to understand this PR. From the code and comments I understand that the new option will catalog packages from all layers, but then only include packages that are visible in the squashed file-system. How is that different from the regular squashed scope (or, I could probably rephrase this to: what is the difference between 'cataloging' and 'including')?
My main concern is whether this would (eventually) help to fix issue #1818
Many thanks!

hi @dbrugman ,
In this PR I am trying to display only packages which exists in the squashed layer, and in case they are, to include all of the layers they exist in so we can track down in which layer they were added.

Got it, thanks @tomersein

Hi @tomersein -- thanks for the contribution. I don't think we would want to merge this as-is, though. I wonder if there are any other things we may be able to do in order for you to accomplish what you're hoping to achieve.
So I understand correctly: the use case is to be able to find the layer which introduced a package, right?

yes correct @kzantow , let me know what are the gaps so I can push some fixes \ improvements.

any update? :) @wagoodman

did some static analysis corrections and all checks are now passed
@kzantow @wagoodman

@tomersein thank you for submitting a candidate solution to solve the problem of tracking the layer-of-first-attribution problem.
Let me first summarize how this PR is achieving attribution. The first change involves adding a new file Resolver, which makes use of the squashed resolver and all-layer resolver based on the use case. The second change is adding IsSquashedAllLayersResolver  and IsSquashedLayer  bools to the core LocationMetadata struct. The new file resolver will raise up locations that positively confirm if the location is from the squashed layer and if the new resolver is used. The last change is to update the syft json formatter to filter out all packages that has no locations from a squashed layer. This in combination with the existing deduplication logic would yield in the same number of packages found but additional layer attributions.
Take for example a (rather silly) Dockerfile:
FROM ubuntu:latest
RUN apt update -y
RUN apt install -y jq
RUN apt install -y vim
RUN apt install -y wget curl

And after build:
$ docker inspect localhost/squash-all-layers | jq '.[].RootFS.Layers'

[
  "sha256:c26ee3582dcbad8dc56066358653080b606b054382320eb0b869a2cb4ff1b98b",
  "sha256:5ba46f5cab5074e141556c87b924bc3944507b12f3cd0f71c5b0aa3982fb3cd4",
  "sha256:1fde57bfea7ecd80e6acc2c12d90890d32b7977fec17495446678eb16604d8c7",
  "sha256:9b6721789a2d1e4cef4a8c3cc378580eb5df938b90befefba0b55e07b54f0c33",
  "sha256:4097f47ebf86f581c9adc3c46b7dc9f2a27db5c571175c066377d0cef9995756"
]

Here we'll have multiple copies of the DPKG status file, which means classically we'll use the last layer for all evidence locations for packages (at least when it comes to the primary evidence location for the status file).
Let's take a look at just vims locations:
cat /tmp/after.json| jq '.artifacts[] | select(.name == "vim").locations'

[
  {
    "path": "/usr/share/doc/vim/copyright",
    "layerID": "sha256:9b6721789a2d1e4cef4a8c3cc378580eb5df938b90befefba0b55e07b54f0c33",
    "accessPath": "/usr/share/doc/vim/copyright",
    "annotations": {
      "evidence": "supporting"
    }
  },
  {
    "path": "/var/lib/dpkg/info/vim.md5sums",
    "layerID": "sha256:9b6721789a2d1e4cef4a8c3cc378580eb5df938b90befefba0b55e07b54f0c33",
    "accessPath": "/var/lib/dpkg/info/vim.md5sums",
    "annotations": {
      "evidence": "supporting"
    }
  },
  {
    "path": "/var/lib/dpkg/status",
    "layerID": "sha256:4097f47ebf86f581c9adc3c46b7dc9f2a27db5c571175c066377d0cef9995756",
    "accessPath": "/var/lib/dpkg/status",
    "annotations": {
      "evidence": "primary"
    }
  },
  {
    "path": "/var/lib/dpkg/status",
    "layerID": "sha256:9b6721789a2d1e4cef4a8c3cc378580eb5df938b90befefba0b55e07b54f0c33",
    "accessPath": "/var/lib/dpkg/status",
    "annotations": {
      "evidence": "primary"
    }
  }
]

Note that we see the original layer the package was added (sha256:9b6...c33) as well as the final unrelated modification of the status file (sha256:409...756). This is great! This is exactly what we're looking for in terms of results. There might be some debate around including one and only one spot for primary evidence, but lets ignore that for now.
Here's what I see when running a before and after:
❯ syft localhost/squash-all-layers:latest -o table=/dev/null
 ✔ Loaded image                                                                                localhost/squash-all-layers:latest
 ✔ Parsed image                                                                                sha256:6a78fd79097acadb77e57cd1c32fca596c3addc3d99c77e4fc977032a2ab3eb2
 ✔ Cataloged contents<PHONE_NUMBER>fcc7d28136e3ecffca4bfe371d89f0737cef299bdf378c87146bcf
   ├── ✔ Packages                        [132 packages]
   ├── ✔ File metadata                   [5,418 locations]
   ├── ✔ Executables                     [809 executables]
   └── ✔ File digests                    [5,418 files]

❯ syft localhost/squash-all-layers:latest -s squash-with-all-layers -o table=/dev/null
 ✔ Loaded image                                                                                localhost/squash-all-layers:latest
 ✔ Parsed image                                                                                sha256:6a78fd79097acadb77e57cd1c32fca596c3addc3d99c77e4fc977032a2ab3eb2
 ✔ Cataloged contents<PHONE_NUMBER>fcc7d28136e3ecffca4bfe371d89f0737cef299bdf378c87146bcf
   ├── ✔ Packages                        [132 packages]
   ├── ✔ File metadata                   [40,226 locations]
   ├── ✔ Executables                     [1,618 executables]
   └── ✔ File digests                    [40,226 files]

It looks like when cataloging ~138 packages was found then before finalizing the number dropped to ~132, so that's good.
But I noticed these runs took different times -- 8 seconds vs 11 seconds, not a big difference, but given that this is a small and simple image it is worth looking at. I believe this is because we're essentially doing both a squashed scan + an all-layers scan implicitly, since the resolver will return all references from both resolvers (not deduplicating file.Locations by the way). This isn't a problem in and of itself, since it might be that any approach may need to do just this, but I think this explains the mechanisms of what's happening time-wise.
Also note that there are several more executables and files cataloged! This is concerning since this should be behaving no different than the squashed cataloger from a count perspective. It's not immediately apparent what is causing this but it is a large blocker for this change (at first glance I think it's because catalogers are creating duplicate packages and relationships, but only the packages are getting deduplicated, but not the relationships... this should be confirmed though).
After reviewing the PR there are a few problems that seem fundamental:

LocationMetadata is being altered in a way where it's aware of the method used from the resolver perspective. Furthermore, since this is used during formatting this means that implicitly the format must know about the method of collecting the packages. This is less than ideal as it's leaking concerns about how to find the data vs the data itself. IsSquashedLayer is less of a problem (though not ideal) but IsSquashedAllLayersResolver  is the main problem here.
Converting an existing syft-json SBOM into the memory location would not have any information about IsSquashedLayer on the file.LocationMetadata structs. This incongruity may cause some confusion for us down the line, especially if there is downstream processing (in syft) that depends on these being accurate.
Package filtering is happening during formatting. This is a big one -- it looks like only the syft-json format has this filtering implemented, but porting to the remaining formats is not ideal. Ideally the SBOM object itself would be consistent before any formatters are used, so it hints at this kind of work being done further upstream processing-wise than where it is now. It might be that this could be refactored so that this is happening within the package cataloging task itself instead of downstream in the formatters.
The package collection is aware of the file resolver method used, which is another abstraction leak -- it should only really know about packages, not how the packages were discovered. If there were a more resolver-agnostic definition that was core to what the package collection does then that would be different, but an equivalent configuration name hasn't come to mind yet.

What's the path forward from here? I think there is a chance of modifying this PR to get it to a mergable state, but it would require looking into the following things:

Probably migrate all package filter logic from the formatter to it's own task. Today we have a set of tasks that are run to coordinate how the SBOM is populated. There are some "post tasks" that always run after cataloging (such as the relationship task) that does additional work to what is already in the SBOM. It seems like we could make a new task that would be just after package cataloging that would be responsible for actively removing packages that shouldn't be in the SBOM at all (as well as their relationships). This change should be enough to remove the need for IsSquashedAllLayersResolver on the file.LocationMetadata object.
Directly related to the previous point 1, is there a way to remove the IsSquashedLayer bool on file.LocationMetadata? I don't obviously see a way to do this, but this should be addressed per fundamental problem 2. Should we expose this information to JSON? should these be another location annotation instead? Can we convince ourselves that this is a cataloging/post-cataloging/pre-formatting concern entirely, which would make this a non-point and we don't need to solve for it.

The following changes would additionally be needed:

any []file.Location returned by the new resolver needs to be deduplicated. We have file.LocationSet that should help with this, but it should be noted that the current implementation is noting squashed=true and false for potentially the same layer information, so this needs to be considered.
we need to deduplicate the relationships coming from the several duplicate file parser calls that's happening. I think it would need to occur after we know what the duplicates are, which means there is some interaction with the package cataloger here that is non obvious.

@tomersein shout out if you want to sync on this explicitly, I'd be glad to help. A good default time to chat with us is during our community office hours. Our next one is going to be this thursday at noon ET  . If that doesn't work we can always chat through discourse group topics or DMs to setup a separate zoom call.

Hi @wagoodman
Thanks for the comments. I will not be available to work on it this month, but i will want to develop it after that.
It will be helpful to discuss all open issues so once i am available again i can work on it, i will watch the discussion on youtube but i will not be able to join myself :)
Please let me know if its ok!

Hi @wagoodman ,
I've read again all of the comments, I'll try to fix some of them.
However, some of the requests sounds more complex:

we need to deduplicate the relationships coming from the several duplicate file parser calls that's happening. I think it would need to occur after we know what the duplicates are, which means there is some interaction with the package cataloger here that is non obvious.

so I might need some more details or a direction in the code how to do so.

hi @wagoodman
made some changes according to your comments, please let me know how to proceed further.
let me know if the changes that i've made are going to the right direction so this PR will be merged in the future :)

It looks like these have not been addressed yet

Converting an existing syft-json SBOM into the memory location would not have any information about IsSquashedLayer on the file.LocationMetadata structs. This incongruity may cause some confusion for us down the line, especially if there is downstream processing (in syft) that depends on these being accurate.

Directly related to the previous point 1, is there a way to remove the IsSquashedLayer bool on file.LocationMetadata?...

I haven't done another in-depth review though to see if there are other outstanding issues.

hi @wagoodman ,
I didn't find a way to do so, would like to know if you have any suggestions \ ideas where this logic will fit better.

I will try to elaborate the issue:
In case a file is being deleted, the location will exist in the "all-layers" and not in "squashed". I need a way to filter these packages, so I can from the one hand provide all the location of a given package, but not to include packages which doesn't actually exist.
I can provide some samples of Dockerfiles which demonstrate the issue.
The only way I thought was to add a field to the location struct, which can indicate to the other components (like sbom) which resolver provided a given location.
If I try to build it inside the resolver, I still can't manage to filter out packages that was deleted (and I don't want to change the Interface of the functions of the resolvers).
can we discuss on possible solutions? @wagoodman @popey

hi! @wagoodman
followed the gardening OSS meeting today, noticed we hadn't have enough time to discuss this PR, please let me know if you have any suggestions to alternative way beside using a new field in location :)

@wagoodman delivered a new solution without the new field.
let me know what do you think :)

hi! @wagoodman

removed the field as requested
added UT

I think this PR is ready now for further deep review, let me know how to proceed further :)


UBI bootstrap script unable to setup cross-rs

I'm trying to build for apple silicone, with the following action config
build:
    name: Build
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - name: Build binary
        uses: houseabsolute/actions-rust-cross@v0
        with:
          command: "build"
          target: aarch64-apple-darwin
          toolchain: nightly
          cross-version: "v0.2.5"
          args: "--locked --release"
          strip: true

I'm getting output
...
bootstrap-ubi.sh: ubi has been installed to ..
| bootstrap-ubi.sh: It looks like . is not in your PATH. You may want to add it to use ubi.
|
| + ./ubi --project cross-rs/cross --matching musl --in . --tag v0.2.5
| [ubi][ERROR] HTTP status client error (401 Unauthorized) for url (https://api.github.com/repos/cross-rs/cross/releases/tags/v0.2.5)

That's odd. Can you point me to the project with this config or is it private?

We encountered the same issue when using this action in a workflow on a GitHub Enterprise instance. The problem arises because the action attempts to authenticate with github.com using the token from $GITHUB_TOKEN, which isn't valid because it's only applicable to the instance that issued it.
To resolve this, we generated a PAT for github.com and used it to override the respective environment variable in the workflow.
  - name: Build binary
    uses: houseabsolute/actions-rust-cross@v0
    with:
      GITHUB_TOKEN: ${{secrets.GITHUB_DOT_COM_TOKEN}}

Thanks for the info, @reformat0r. I will add something to do the docs about this.

Added.


Umzug should reject a migration if it can't find the migration method

Note: I created a pull request for this a while back, but it hasn't been merged in yet. I'm not sure what the process is supposed to be, so I created an issue. This is the pull request:
#115
Rationale for change: you will never have a no-op migration. Currently, if the up or down methods can't be found when running a migration, Umzug replaces the method body with Promise.resolve() and tells you that the migration was run correctly. (It wasn't.)

No problem, there is no official process as this project is very small and don't have an active maintainer (as I have been busy for a while).


add VS Code extension to the Data Science category in VS Code extension marketplace

https://marketplace.visualstudio.com/search?target=VSCode&category=Data Science&sortBy=Installs

I think yours is also a good candidate for Visualization & Notebooks categories vscode & marketplace teams added recently:
https://marketplace.visualstudio.com/search?target=VSCode&category=Visualization
https://marketplace.visualstudio.com/search?target=VSCode&category=Notebooks


ollama 模型授权

What is the issue?
我想问一下ollama怎么自定义设置KEY_传参， 每个模型定义不同的key，2.ollama是否支持模型授权，加密模型之类的，
OS
Linux
GPU
Nvidia
CPU
Intel
Ollama version
最新的

Hi there, Ollama doesn't currently supported encrypted models or anything similar at the moment. That said don't hesitate to create a feature request! Thanks for the issue


Close proxy only when the last driver is closed (during test method running)

Close proxy only when the last driver is closed during particular test method running. And also allow to run separate proxy for each driver.

closing as won't fix


Cannot schedule a workflow at a specific date/time

In the existing implementation I cannot see the ability to pass date/ time to schedule the workflow/ activity run as per the below code at : https://github.com/dapr/java-sdk/blob/master/sdk-workflows/src/main/java/io/dapr/workflows/client/DaprWorkflowClient.java
public  String scheduleNewWorkflow(Class clazz) {
return this.innerClient.scheduleNewOrchestrationInstance(clazz.getCanonicalName());
}
/**

Schedules a new workflow using DurableTask client.

@param    any Workflow type
@param clazz Class extending Workflow to start an instance of.
@param input the input to pass to the scheduled orchestration instance. Must be serializable.
@return the randomly-generated instance ID for new Workflow instance.
*/
public  String scheduleNewWorkflow(Class clazz, Object input) {
return this.innerClient.scheduleNewOrchestrationInstance(clazz.getCanonicalName(), input);
}

/**

Schedules a new workflow using DurableTask client.

@param         any Workflow type
@param clazz      Class extending Workflow to start an instance of.
@param input      the input to pass to the scheduled orchestration instance. Must be serializable.
@param instanceId the unique ID of the orchestration instance to schedule
@return the instanceId parameter value.
*/
public  String scheduleNewWorkflow(Class clazz, Object input, String instanceId) {
return this.innerClient.scheduleNewOrchestrationInstance(clazz.getCanonicalName(), input, instanceId);
}

However I can schedule it either with Python/ dotnet;  Refer to dotnet SDK here: https://github.com/dapr/dotnet-sdk/blob/master/src/Dapr.Workflow/DaprWorkflowClient.cs
@skyao - FYA.

Seems we need another wrapper method for this https://github.com/microsoft/durabletask-java/blob/8a74001f64aa4048c1619c14b7657c8b3b8993af/client/src/main/java/com/microsoft/durabletask/DurableTaskClient.java#L78


Getting error InvalidParameter calling waveInOpen

Getting this error every time calling WaveInEvent.StartRecording. Method MMDeviceEnumerator.EnumerateAudioEndPoints(DataFlow.Capture, DeviceState.Active) returns info about my microphone. Method WaveInEvent.GetCapabilities(0) returns 2 channels with many SupportedWaveFormat.
This issue is not direct related to NAudio, tried my code with DllImport - same result. Can anybody help me?
Windows 7 SP1 x64

so what parameters are you calling it with?

var sourceFormat = new WaveFormat(44100, 1);
_waveIn = new WaveInEvent();
_waveIn.WaveFormat = sourceFormat;
_waveIn.DataAvailable += OnSoundDataAvailable;
_waveIn.RecordingStopped += OnRecordingStopped;
_waveIn.StartRecording(); // InvalidParameter

OK, try with 2 channels and also with 48kHz. Maybe the drivers for your sound device are fussy

Same error.
WaveFormat: 16 bit PCM: 48kHz 2 channels
WaveInEvent.GetCapabilities(0): WAVE_FORMAT_48S16 and WAVE_FORMAT_48S08 are supported
Windows microphone default settings: 2 channels, 16 bit, 48000 Hz. Windows SoundRecorder.exe records wma without errors.

Then I have no idea why it won't open for you. Have you tried with other audio devices on your system?

are you in a virtual machine / rdp session by any chance?

This is operator PC with audio registration, not a VM nor RPD. I connecting via TeamViewer, but issue not belongs on user connection type. Will try MCI windows api.

Why this issue is closed? It's solved? What was the solution?

Why this issue is closed? It's solved? What was the solution?

I was looking for an answer too 😄 😆

Nо solution found. In my case the reason was - Kaspersky antivirus on operator PC, so i have added additional message to error handler. Sample code:
catch (Exception ex)
{
    string msg = "Error when starting recording";
    var mmex = ex as NAudio.MmException;
    if (mmex != null && mmex.Result == NAudio.MmResult.InvalidParameter && mmex.Message.IndexOf("waveInOpen") > -1)
        msg += "warning about AV software";
    _logger.Error(ex, msg);
}

Sorry for issue closing without comment.

I am having the same issue

are you in a virtual machine / rdp session by any chance?

And I am in a virtual machine. Does that have to do with the problem?


⚠ Bofrost.be has degraded performance

In c509514, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1384 ms

Resolved: Bofrost.be performance has improved in eefd01c.


wireshark: 2.2.0 -> 2.2.2

Motivation for this change
Things done

[X] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] Linux

[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

See releases announcements:

https://www.wireshark.org/docs/relnotes/wireshark-2.2.1.html
https://www.wireshark.org/docs/relnotes/wireshark-2.2.2.html

wireshark-2.2.1 fixes the following vulnerabilities:

CVE-2016-7957
CVE-2016-7958

wireshard-2.2.2 fixes the following vulnerabilities:

CVE-2016-9372
CVE-2016-9374
CVE-2016-9376
CVE-2016-9373
CVE-2016-9375

Thanks @lsix! If you or the maintainers @bjornfor @fpletz are feeling generous with your time, please also cherry-pick to release-16.09 as there are security fixes here.

I'm backporting this. Just waiting for the build to succeed before pushing. Thanks!

One step ahead (sorry!):<PHONE_NUMBER>95d72879d1d8c74a59c0868cce8f71

Alright. Thanks! :+1: