[BEAM-11106] small nits to truncate sdf exec unit

Small nits to truncate exec unit. Earlier we were extracting the main input from FullValue. This extraction is not required because the element can be of any type and not FullValue. Having a []byte in process element gave me the error that the extracting value is []uint8 and not FullValue. This PR fixes that.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Can one of the admins verify this patch?

R: @lostluck

Run GoPortable PostCommit


Image.RotateTo inside CompassChanged event crashes the app on Android

Good Day James,
Awesome plugins by yo have made life really easy.
I am calculating the rotation value based on the compass heading and trying to rotate an image inside CompassChanged event. It is a separate view that is invoked from the main view. View works fine but when this view is pushed and popped about 6 to 7 times, the app crashes, only on Android.
Following is the code I am using:
private void Current_CompassChanged(object sender, Plugin.Compass.Abstractions.CompassChangedEventArgs e)
{
var headingTo = {some calculation based on e.Heading};
Device.BeginInvokeOnMainThread(async () =>
await imgCompass.RotateTo(headingTo , 100)
);
}
I also tried rotating image without using Device.BeginInvokeOnMainThread, but the same results.
Please advise.
Thank you.

It is most likely updating too fast for the UI to refresh I would assume. You may want to put some checks before doing your next rotation.

Good day James,
Thank you for replying back. I checked, nothing was wrong with the calculation. But interestingly, what I observed was, even after the view is popped from the stack, the Compass Changed event was still listening the compass heading. So detaching the Compass Changed event in OnDisappearing() of the view, solved the problem altogether.
Please advise.


Feature/markup optimization

@ala-n @julia-murashko @nattallius @Sisha3342

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Event Request] Table 7321 Warehouse Shipment Line - OnBeforeAutofillQtyToHandle / OnAfterAutofillQtyToHandle

Hi Team,
In table 7321 we need possibility to replace standard code with our own. Having event in beginning and at the end of procedure AutofillQtyToHandle, would be perfect solution:

    [IntegrationEvent(false, false)]
    local procedure OnBeforeAutofillQtyToHandle(var WhseShptLine: Record "Warehouse Shipment Line"; var HideValidationDialog: Boolean)

    [IntegrationEvent(false, false)]
    local procedure OnAfterAutofillQtyToHandle(var WhseShptLine: Record "Warehouse Shipment Line"; var HideValidationDialog: Boolean)

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Storing Application Secrets in Azure Vault

This application utilizes many different secrets and also SSL certificate. For streamlining the development and deployment to move away from file-based application settings.
Utilize the following libraries:

Bet.AspNetCore
Bet.AspNetCore.HealthChecks
Bet.AspNetCore.Logging
Bet.Extensions
Bet.Extensions.AzureVault
Bet.Extensions.Logging
https://github.com/kdcllc/Bet.AspNetCore

This is implemented.


masm codegen: identify procedures/interface for use by STARK verifier

We need to clarify the design for the STARK verifier and use that to identify the interface (i.e. what stack and memory should look like) and the procedures that need to be generated in Miden assembly. From there, we can break the Miden assembly codegen down into separate issues.

reference: there is an initial proposal at https://github.com/0xPolygonMiden/air-script/issues/164#issuecomment-1454224293


🐛 BUG: Issue with nodejs_compat + dynamic require of node:events

Which Cloudflare product(s) does this pertain to?
Workers/Other, Wrangler
What version of Wrangler are you using?
2.18.0
What operating system are you using?
Mac
Describe the Bug
Attempting to upload a worker with Wrangler using compatibility_flags = ['nodejs_compat'] or command line --compatibility-flags="nodejs_compat" fails with this error message:
  Uncaught Error: Dynamic require of "node:events" is not supported
    at worker.js:13:11
    at worker.js:13348:28
    at worker.js:13631:3
   [code: 10021]

The package using node:events is this LaunchDarkly SDK: https://github.com/launchdarkly/js-core/tree/main/packages/sdk/cloudflare

Same exact issue for me as well using same package

Having the same issue with trying to use import { Buffer } from "node:buffer"; per the docs:
service core:user:muxworker: Uncaught Error: Dynamic require of "node:buffer" is not supported
  at core:user:muxworker:14:11
  at core:user:muxworker:1749:28
  at core:user:muxworker:2897:3

This was with Wrangler version v.2.20.0 as well as v3.0.0. Also encountering this error with wrangler dev.

Anyone have any luck resolving this?

Right now, the only way to access these compatible libraries is by a static import {Buffer} from "node:buffer"; statement or a dynamic await import("node:Buffer") expression. Not a require() I believe.


New attempt to improve timesyncd support

Hello,
Here is a new attempt (related to #5) to improve timesyncd support. Variouscomments should have been taken into account.
Best regards,

@aanriot, @aboe76 thanks for your work!

You are welcome, thanks @aboe76 , @javierbertoli !


Export external items as interfaces

External Rust items have no special treatment in the frontend.
We need to collect them to produce interface files in the various backends so that one can provide models in the backends for external crates.
For instance, Hacspec_lib is an external crate, and we would like Circus to generate an interface each backend should implement.
TODO:

[ ] the frontend should collect every item signature for every external crate;
[ ] the frontend should mark which external item is used by the exported crate;
[ ] have an interface generation mode for backends.

Progress have been made with PR #743

Still useful


cigien: Watch beseductiv.com

cigien requests the watch of the watch_keyword beseductiv\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

beseductiv\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.

https://m.erwaysoftware.com/posts/uid/stackoverflow/65486143

Approved by tripleee in Charcoal HQ


Broken on Gatsby v4.8.0

Versions

gatsby-source-prismic: 5.2.5
gatsby-plugin-prismic-previews: 5.2.5
node: v16.14.0

Reproduction
Just upgrading Gatsby to v4.8.0 broke existing sites
https://github.com/daangn/websites/pull/511
 ERROR

There was a problem loading plugin "gatsby-source-prismic". Perhaps you need to install its package?
Use --verbose to see actual error.

 ERROR

There was a problem loading plugin "gatsby-plugin-prismic-previews". Perhaps you need to install its package?
Use --verbose to see actual error.

 ERROR

There was a problem loading plugin "gatsby-source-prismic". Perhaps you need to install its package?
Use --verbose to see actual error.

 ERROR #11321  PLUGIN

"gatsby-plugin-prismic-previews" threw an error while running the onPostBootstrap lifecycle:

pluginOptions.writeTypePathsToFilesystem is not a function

  TypeError: pluginOptions.writeTypePathsToFilesystem is not a function

  - on-post-bootstrap.ts:57 Object.onPostBootstrap
    [gatsby-theme-prismic]/[gatsby-plugin-prismic-previews]/src/on-post-bootstrap.ts:57:22

  - api-runner-node.js:462 runAPI
    [websites]/[gatsby]/src/utils/api-runner-node.js:462:22

  - api-runner-node.js:613 Promise.catch.decorateEvent.pluginName
    [websites]/[gatsby]/src/utils/api-runner-node.js:613:13

  - debuggability.js:384 Promise._execute
    [websites]/[bluebird]/js/release/debuggability.js:384:9

  - promise.js:518 Promise._resolveFromExecutor
    [websites]/[bluebird]/js/release/promise.js:518:18

  - promise.js:103 new Promise
    [websites]/[bluebird]/js/release/promise.js:103:10

  - api-runner-node.js:611
    [websites]/[gatsby]/src/utils/api-runner-node.js:611:16

  - util.js:16 tryCatcher
    [websites]/[bluebird]/js/release/util.js:16:23

  - reduce.js:166 Object.gotValue
    [websites]/[bluebird]/js/release/reduce.js:166:18

  - reduce.js:155 Object.gotAccum
    [websites]/[bluebird]/js/release/reduce.js:155:25

  - util.js:16 Object.tryCatcher
    [websites]/[bluebird]/js/release/util.js:16:23

  - promise.js:547 Promise._settlePromiseFromHandler
    [websites]/[bluebird]/js/release/promise.js:547:31

  - promise.js:604 Promise._settlePromise
    [websites]/[bluebird]/js/release/promise.js:604:18

  - promise.js:649 Promise._settlePromise0
    [websites]/[bluebird]/js/release/promise.js:649:10

  - promise.js:729 Promise._settlePromises
    [websites]/[bluebird]/js/release/promise.js:729:18

  - async.js:93 _drainQueueStep
    [websites]/[bluebird]/js/release/async.js:93:12

success onPostBootstrap - 0.899s
info bootstrap finished - 23.450s
success onPreExtractQueries - 0.002s

@cometkim Thanks for the report. I have been able to use gatsby-source-prismic and gatsby-plugin-prismic-previews successfully in Gatsby v4.10.3.
It's possible you are seeing those error due to Gatsby's new support of native TypeScript gatsby-*.js files. If I remember correctly, your monorepo includes support for TypeScript files by transpiling them before building. You could try removing that step and using the new native TypeScript support.
If this is still an issue for you, are you able to create a reproduction of the issue in a minimal repository?


Google

GoogleLegacy was here!

Stop posting that you were here please. At least give some form of useful message


Regression for "scan-and-fix-repos" in Azure DevOps server since version 2.11.5

Describe the bug
Since frogbot version 2.11.5 and newer, the "scan-and-fix-repos" command fails with the following error:
failed to checkout to master branch before scanning. The following error has been received:
'git checkout master' failed with error: reference not found

NOTE: our git provider is Azure DevOps Server. It is not available in the issue's dropdown menu
Current behavior
With Frogbot version 2.11.7
It seems that now frogbot tries to checkout a branch. However, the zip archive that is downloaded does not contain the .git folder
Frogbot downloaded successfully!
10:56:50 [Info] Frogbot version: 2.11.7
10:56:50 [Debug] Reading config from file system. Looking for .frogbot/frogbot-config.yml
10:56:50 [Debug] frogbot-config.yml found in /opt/agt/_work/1/s/.frogbot/frogbot-config.yml
10:56:50 [Debug] Locking config file to run config AddOrEdit command.
10:56:50 [Debug] Creating lock in: /tmp/jfrog.cli.temp.-1692003410-986446427/locks/config
10:56:50 [Debug] Releasing lock: /tmp/jfrog.cli.temp.-1692003410-986446427/locks/config/jfrog-cli.conf.lck.324.1692003410241201455
10:56:50 [Debug] Config AddOrEdit command completed successfully. config file is released.
10:56:50 [Info] Running Frogbot "scan-multiple-repositories" command
10:56:50 [Debug] Downloading <Global/CockpIT-back/master> to: '/tmp/jfrog.cli.temp.-1692003410-2257876789'
10:56:50 [Debug] Download url: https://<AZURE_SERVER_HOST>/global/CockpIT/_apis/git/repositories/CockpIT-back/items/items?path=/&versionDescriptor[version]=master&$format=zip
10:56:50 [Debug] Usage Report:  Sending info...
10:56:50 [Debug] Sending HTTP GET request to: https://artifactory.prd.apps.bdl/artifactory/api/system/version
10:56:50 [Debug] Artifactory response: 200
10:56:50 [Debug] JFrog Artifactory version is: 7.55.10
10:56:50 [Debug] Sending HTTP POST request to: https://artifactory.prd.apps.bdl/artifactory/api/system/usage
10:56:50 [Debug] Usage Report: Usage info sent successfully. Artifactory response: 200
10:56:50 [Info] CockpIT-back repository downloaded successfully. Starting with repository extraction...
10:56:50 [Info] Extracted repository successfully
10:56:50 [Debug] Repository download completed
10:56:50 [Debug] Setting timeout for go-git to 120 seconds ...
10:56:50 [Debug] Running git checkout to branch: master
10:56:50 [Debug] Downloading <Global/CockpIT-front/master> to: '/tmp/jfrog.cli.temp.-1692003410-2588085699'
10:56:50 [Debug] Download url: https://<AZURE_SERVER_HOST>/global/CockpIT/_apis/git/repositories/CockpIT-front/items/items?path=/&versionDescriptor[version]=master&$format=zip
10:56:50 [Info] CockpIT-front repository downloaded successfully. Starting with repository extraction...
10:56:50 [Info] Extracted repository successfully
10:56:50 [Debug] Repository download completed
10:56:50 [Debug] Setting timeout for go-git to 120 seconds ...
10:56:50 [Debug] Running git checkout to branch: master
10:56:50 [Error] failed to checkout to master branch before scanning. The following error has been received:
'git checkout master' failed with error: reference not found
##[error]Bash exited with code '1'.
Finishing: Run Frogbot

Reproduction steps
frogbot-config.yml
- params:
    git:
      repoName: CockpIT-back
      branches:
        - master
    scan:
      projects:

- params:
    git:
      repoName: CockpIT-front
      branches:
        - master

pipeline.yml
[...]
      - task: CmdLine@2
        displayName: 'Run Frogbot'
        env:
          JF_GIT_TOKEN: $(System.AccessToken)
          JF_URL: https://<ARTIFACTORY_HOST>
          JF_USER: $(artifactory_username)
          JF_PASSWORD: $(artifactory_password)
          JF_GIT_OWNER: "Global"
          JF_RELEASES_REPO: "jfroginsight-generic-external"
          JF_GIT_PROJECT: $(System.TeamProject)
          JF_GIT_API_ENDPOINT: $(System.CollectionUri)
          JF_GIT_PROVIDER: 'azureRepos'
          JFROG_CLI_LOG_LEVEL: "DEBUG"
          JAVA_HOME: $(JAVA_HOME_17_X64)
          MAVEN_OPTS: "-Dmaven.gitcommitid.skip=true -Dcodegen.skip=true"
        inputs:
          script: |
            sh getFrogbot.sh ${{ parameters.frogbotVersion }}
            ./frogbot scan-and-fix-repos

Expected behavior
With Frogbot version 2.11.4
Frogbot downloaded successfully!
10:55:11 [Info] Frogbot version: 2.11.4
10:55:11 [Debug] Reading config from file system. Looking for .frogbot/frogbot-config.yml
10:55:11 [Debug] frogbot-config.yml found in /opt/agt/_work/1/s/.frogbot/frogbot-config.yml
10:55:11 [Debug] Locking config file to run config AddOrEdit command.
10:55:11 [Debug] Creating lock in: /tmp/jfrog.cli.temp.-1692003311-2952632449/locks/config
10:55:11 [Debug] Releasing lock: /tmp/jfrog.cli.temp.-1692003311-2952632449/locks/config/jfrog-cli.conf.lck.334.1692003311253930784
10:55:11 [Debug] Config AddOrEdit command completed successfully. config file is released.
10:55:11 [Info] Running Frogbot "scan-and-fix-repos" command
10:55:11 [Debug] Created temp working directory:  /tmp/jfrog.cli.temp.-1692003311-3426455115
10:55:11 [Debug] Usage Report: Sending info...
10:55:11 [Debug] Downloading Global/CockpIT-back , branch: master to: /tmp/jfrog.cli.temp.-1692003311-3426455115
10:55:11 [Debug] Download url: https://<AZURE_SERVER_HOST>/global/CockpIT/_apis/git/repositories/CockpIT-back/items/items?path=/&versionDescriptor[version]=master&$format=zip
10:55:11 [Debug] Sending HTTP GET request to: https://<ARTIFACTORY_HOST>/artifactory/api/system/version
10:55:11 [Debug] Artifactory response: 200
10:55:11 [Debug] JFrog Artifactory version is: 7.55.10
10:55:11 [Debug] Sending HTTP POST request to: https://<ARTIFACTORY_HOST>/artifactory/api/system/usage
10:55:11 [Debug] Usage Report: Usage info sent successfully. Artifactory response: 200
10:55:11 [Info] CockpIT-back repository downloaded successfully. Starting with repository extraction...
10:55:11 [Info] Extracted repository successfully
10:55:11 [Debug] Repository download completed
10:55:11 [Debug] Sending HTTP GET request to: https://<ARTIFACTORY_HOST>/xray/api/v1/system/version
10:55:11 [Debug] Sending HTTP GET request to: https://<ARTIFACTORY_HOST>/xray/api/v1/entitlements/feature/contextual_analysis
10:55:11 [Info] JFrog Xray version is: 3.71.6
10:55:11 [Info] Scanning for vulnerable dependencies...
10:55:11 [Info] Scanning directory: /tmp/jfrog.cli.temp.-1692003311-3426455115 ...
10:55:11 [Info] Detected: maven.
10:55:11 [Debug] mvn command goals: [-B compile test-compile -Dcheckstyle.skip -Denforcer.skip]
10:55:11 [Debug] Saving build general details at: /tmp/jfrog/builds/59f364334d4e91c932925a84bc065ab92684eacab478706736a678566aad4b9b/partials
[...]

JFrog Frogbot version
2.11.7
Package manager info
N/A
Git provider
GitHub
JFrog Frogbot configuration yaml file

params:
git:
repoName: CockpIT-back
branches:
- master
scan:
projects:

params:
git:
repoName: CockpIT-front
branches:
- master

Operating system type and version
RHEL 8
JFrog Xray version
3.71.6

Hello @anael-l,
Thank you for reporting this issue, we sincerely apologize for any inconvenience this bug may have resulted in. We are committed to resolving it promptly and will keep you informed of our progress.
Warm regards,
Eyal Delarea

Hello @EyalDelarea,
The new version does fix the issue I was having.
Thank you for the quick fix !
Best regards


Changed handling of JedisException in RedisShardSubscription::stop

fixes #1838
If a call to stop() is made before any connection is established, the resulting JedisException will be thrown.
Previously this exception was caught and swallowed, but this caused an issue where subscribe would never complete and the user would not be notified. Because the stopped Atomic Boolean is set at the beginning of the stop() method, the mainLoop() method would stop regardless of wether or not unsubscribe() could complete gracefully.
This change will throw an error in that case, to alert the user that the RedisSubscription object is now in "stopped" state and cannot accept connections.
The attached image shows how the race condition happens - by the time the initial call to run() progresses to the mainLoop() method, stopped is already set to true, and so iterate() is never called and the subscription is never connected.

Based on previous drafts, I'm not understanding this change - wasn't there a restructure to 'first'? How does just swallowing on stop accomplish the goal here?

Not swallowing the JedisException on stop accomplishes the goal because it alerts the user that their object is now in the "stopped" state and that it failed to connect.
There's no need to restructure "first". In the "onReset..." test, when the initial subscribe happens, first is set to false. Then after that fails, the second attempt triggers the onReset method because iterate and subscribe get called with isReset == !first == true

Please have a closer look at the issue description: we're not trying to solve for a "stop()" hang, we're solving for the fact that if we stop between the stopped check and the subscribe, that the subscription thread (on this line) will hang (and is what was observed to hang).
The relation to the test is only tangential - the core of the issue is that at any point in the subscription process, a stop can be called, and the subscription should never hang or block afterwards. That behavior hasn't changed here.
This is why the subscribed future should be irrelevant or reassociated - since the first response of the server is to break the connection, all we determine in that test is whether the onReset is called. The onReset callback can be the future::set, particularly because we could actually race the subscribe -> onReset -> subscribe loop as well, and the only implementation detail the test should depend upon is the onReset call.


microTVM or zephyr bugs, No SOURCES given to Zephyr library

After the configuration of microTVM in TVM and zephyr in my local environment, I run the "python micro_aot.py" in tvm/gallery/how_to/work_with_microtvm subdirectory. The following errors occur.
zephyrproject/zephyr/subsys/random/CMakeLists.txt:11 (message):

      Warning: CONFIG_TEST_RANDOM_GENERATOR is not a truly random generator.
      This capability is not secure and it is provided for testing purposes only.
      Use it carefully.

CMake Warning at /home/sdc/wangpeng/dlc/zephyr/zephyrproject/zephyr/CMakeLists.txt:824 (message):
  No SOURCES given to Zephyr library: drivers__console

  Excluding target from build.

tmp/tmp7tvfh3o8/project/src/main.c:31:10: fatal error: drivers/gpio.h: No such file or directory
   31 | #include <drivers/gpio.h>
      |          ^~~~~~~~~~~~~~~~
compilation terminated.

Same as #13303 in TVM


update init process for coinbase demo

make the demo simple to run by

moving DDL to proton init process
create pipeline with a init container

(Jove Github Bot) added it to the current sprint.

(Jove Github Bot) moved this ticket out of the GitHub project(up to 1200 tickets for one project).


how to emulate save_and_open_page

Great work. How can we not only have it save the HTML on an error, but automatically open it, just like Capybara's save_and_open_page method?

Thanks for the great gem. It would be awesome to have this functionality. I currently hacked it into my rspec setup in the following way:
Capybara::Screenshot.autosave_on_failure = false

RSpec.configure do |config|
  config.after do |example|
    if example.metadata[:type] == :feature && example.exception.present?
      save_and_open_page
    end
  end
end

@swrobel fancy doing a PR to add this functionality?


Save memory when resizing images

Fix to help (partially) deal with issue 5852 concerning out of memory problems when resizing big images.
This pull request implements this idea: https://github.com/concrete5/concrete5/issues/5852#issuecomment-330610689

This looks good to me other than the missing newline.
I would've either made a subclass of the resize processor or wrapped the image in order to keep method length and cyclomatic complexity low.

Still looks like there are missing newlines, no? PSR-2 requires that files end in a blank line

I made sure there was one in each file now. Should be ok

Running php-cs-fixer would fix automatically the coding style rules (and if/when https://github.com/concrete5/concrete5/pull/5971 will get merged, we'll have a TravisCI job that will automatically check the coding styles)

Yes, @KorvinSzanto said I should do it that way, one commit for modifications and one commit for cs fixer

@mnakalay Any reason to set ConstrainImageProcessor::$resizeInPlace to false?
Since the process method loads the image when it's called (\Image::load($version->getFileResource()->read());), there's no problem in working directly on the ImageInterface image, isn't it?
If so, what about removing the resizeInPlace concept (assuming it's always true)?

@mlocati, I know there was a reason for this but I can't remember right now. I kind of remember the process method is used elsewhere and will require the copy but I don't remember the specifics.
Give me a few days to go back to what I did and try to remember.

@mlocati I checked and I did it like that as a just-in-case safety device really.
As far as the core is concerned, that boolean is always set to true. But I didn't want to totally remove Imagine's original thumbnailing system from the equation. My thinking was that if they think it's wise to make a copy before resizing, there might be a reason that I don't know about and I should allow for that possibility.
By always using my custom thumbnailing function, that ConstrainImageProcessor class will be cut from the original Imagine thumbnailer so that's one option less.
With that in mind, maybe making that boolean true by default instead of false by default would be a good idea. But someone who understands the implications better than I do would have to decide whether it should be removed or not.

My thinking was that if they think it's wise to make a copy before resizing, there might be a reason that I don't know about and I should allow for that possibility.

It is totally useless to keep in memory two images. I'm going to deprecate the resize-in-place approach, assuming it's always true.

sounds good to me

Maybe resizing in place is slower for some images? Perhaps there is a trade off between processing and memory use?
Just speculating. Nothing I actually have data for.

The resize-in-place approach resizes the loaded image resource directly.
The not-resize-in-place approach makes a copy of the image resource and performs the same operations of the resize-in-place approach on that copy. So, this second approach is slower and more memory hungry.


Getting started for lib

:tada: This issue has been resolved in version 7.26.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Kysely Converts Int8Array to object (not array) after query

I'm having an issue pulling an Int8Array out of the database using Kysely.
At some point after my custom dialect's executeQuery method, an Int8Array coming from the DB (this is how wa-sqlite does blobs) is being converted to an object (the keys being the indexes of the former array). I've checked what I'm returning from executeQuery and it's still an Int8Array at that point. Just for kicks, I modified the driver to change the field to some other byte array types, Uint8Array, Uint32Array, and it has the same issue there. If I convert it to a regular Array (Array.from(int8arraydata)) on the other hand, it works fine.
So it seems that something in Kysely, after the driver returns the data, but before the query results are returned, is turning Int8Array and similar types into to an object. Is there a workaround for this besides just converting the object back and forth, or modifying the DB calls/driver, or is this something that can be changed? Checked the docs but could not find much of anything on how blobs / byte arrays are handled.
const localFile = await this.db.kysely.selectFrom("localFiles").where("id", "=", upload.id).select("myint8arrayfield").executeTakeFirst()
//this is an object ^

      async executeQuery<O>(compiledQuery: CompiledQuery) {
        const results = await dialect.sqlite.exec(compiledQuery.sql, compiledQuery.parameters.map(_ => dialect.convert(_)) as SQLiteType[])
        const rows = results.map(result => result.values.map(_ => zipObject(result.columns, _) as unknown as O))[0] ?? []
        const numUpdatedOrDeletedRows = BigInt(await dialect.sqlite.changes())
        return {
          rows: rows.map(row => {
            // if (isInt)
            return Object.fromEntries(Object.entries(row as any).map(([k, v]) => {
              if (k === "myint8arrayfield") {
                const i: Int8Array = v as Int8Array
                // if i console.log the value here, it's still an Int8Array
                // does not work return [k, i] as const
                // DOES work return [k, Array.from(i)] as const
                // does not work return [k, new Uint8Array(i)] as const
              }
              return [k, v] as const
            }))
          }) as any,
          numUpdatedOrDeletedRows
        }
      }

Kysely does no conversions. See the db driver's docs.

Kysely doesn't touch the data in any way whatsoever. It just passes it through.
If you use the debugger to step through the code, you'd immediately see where the conversion happens. Definitely faster than writing this issue.
My guess: you have a pair of JSON.stringify and JSON.parse somewhere.
Maybe you are using some plugin?

Strange. No plugins, I thought maybe Kysely was serializing somewhere because the driver was giving me the right type. I'll go through and debug. Thanks.

@koskimas I figured it out - it is Kysely, but, it's also a plugin (the built in CamelCasePlugin - thought I had tested without it).
function canMap(obj) {
    return (0, object_utils_js_1.isObject)(obj) && !(0, object_utils_js_1.isDate)(obj) && !(0, object_utils_js_1.isBuffer))(obj);
}

Since Int8Array/Uint8Array/etc passes the isObject test it tries to map the keys.
Might make sense to add another negative condition here. ArrayBuffer.isView? Not sure what's most compatible.


Improved similarity measure

https://github.com/kwikteam/phy/blob/master/phy/cluster/manual/session.py#L654

@nippoo can you remind me what was the new algo discussed over skype?

session:346
            mu_0 = self.cluster_store.mean_features(target)
            mu_1 = self.cluster_store.mean_features(candidate)

            omeg_0 = self.cluster_store.mean_masks(target)
            omeg_1 = self.cluster_store.mean_masks(candidate)

            omeg_0 = np.repeat(omeg_0, self.model.n_features_per_channel)
            omeg_1 = np.repeat(omeg_1, self.model.n_features_per_channel)

            d_0 = np.dot(mu_0, omeg_0)
            d_1 = np.dot(mu_1, omeg_1)

            return (d_0 - d_1) ** 2

just tried: weird results. TBI...

Ah okay, we want:
   d_0 = np.dot(mu_0, omeg_0)
   d_1 = np.dot(mu_1, omeg_1)

   return np.linalg.norm(d_0 - d_1)

np.multiply is the Hadamard product.

you can also just use mu_0 * omeg_0

ugh I'd always assumed that was the dot-product. This all makes sense now...

yeah in matlab that's the case! (i think...)

seems to work fine with your suggestion @nippoo ! will be closed in the next PR

For most clusters it looks like I get good results for closest match. But for this one cluster I had to scroll through something like 100 (not exaggerating) "closest match"es that looked like these:

before finally getting to this:

which isn't an exact match but it's way closer than anything else. Any ideas why this would happen? The cluster doesn't look unique to me; other ones on the same channels do fine. Anyway, I don't think this is worth acting on if you don't have any ideas, since it seems to work fine for the rest of the clusters. But it can be logged here, anyway, in case we start to observe other ones in the future...

the second cluster looks quite noisy no? in any case, yes please put the filename and cluster numbers here so that I (or @nippoo) can take a look

Data in \zserver\multichanspikes\M141003_NS2ROSS\20141112\20141112_all.kwik, cluster #17.
I don't think it is particularly noisier than any other cluster. These channels are a little raggedy-looking mostly because that section of the probe was very highly active.

I won't have time to check this right now -- let me know if you do @nippoo

@nsteinme is this bug critical, or can we set it to the v0.3.0 milestone?

Not critical, or especially not until/unless I see it again in another
example.
On Tue, Jun 23, 2015 at 6:09 PM, Cyrille Rossant<EMAIL_ADDRESS>wrote:

@nsteinme https://github.com/nsteinme is this bug critical, or can we
set it to the v0.3.0 milestone?
—
Reply to this email directly or view it on GitHub
https://github.com/kwikteam/phy/issues/273#issuecomment-114574742.

Ok, I would like to "re-up" this issue. I have now observed more examples of this. Somehow it prefers to give you a "most similar" cluster that has nothing on the channels that the "best unsorted" cluster inhabits, rather than give you ones that are on the same channels but are a bit different. It may to do with the fact that there is no normalization - so a unit with big overlapping features looks potentially "more distant" than one with zero overlapping features.
Can we move this back to 0.3.0? I think it is a big problem.

Can you try custom measures and propose one that works better for you?
Le dimanche 4 octobre 2015, nsteinme<EMAIL_ADDRESS>a écrit :

Ok, I would like to "re-up" this issue. I have now observed more examples
of this. Somehow it prefers to give you a "most similar" cluster that has
nothing on the channels that the "best unsorted" cluster inhabits,
rather than give you ones that are on the same channels but are a bit
different. It may to do with the fact that there is no normalization - so a
unit with big overlapping features looks potentially "more distant" than
one with zero overlapping features.
Can we move this back to 0.3.0? I think it is a big problem.
—
Reply to this email directly or view it on GitHub
https://github.com/kwikteam/phy/issues/273#issuecomment-145348854.

You think it will work? custom quality function doesn't work.
https://github.com/kwikteam/phy/issues/627
On Sun, Oct 4, 2015 at 2:06 PM, Cyrille Rossant<EMAIL_ADDRESS>wrote:

Can you try custom measures and propose one that works better for you?
Le dimanche 4 octobre 2015, nsteinme<EMAIL_ADDRESS>a écrit :

Ok, I would like to "re-up" this issue. I have now observed more examples
of this. Somehow it prefers to give you a "most similar" cluster that has
nothing on the channels that the "best unsorted" cluster inhabits,
rather than give you ones that are on the same channels but are a bit
different. It may to do with the fact that there is no normalization -
so a
unit with big overlapping features looks potentially "more distant" than
one with zero overlapping features.
Can we move this back to 0.3.0? I think it is a big problem.
—
Reply to this email directly or view it on GitHub
https://github.com/kwikteam/phy/issues/273#issuecomment-145348854.

—
Reply to this email directly or view it on GitHub
https://github.com/kwikteam/phy/issues/273#issuecomment-145349051.

I will have a look, in the meantime maybe you can try to change the code
directly in the source?
Le dimanche 4 octobre 2015, nsteinme<EMAIL_ADDRESS>a écrit :

You think it will work? custom quality function doesn't work.
https://github.com/kwikteam/phy/issues/627
On Sun, Oct 4, 2015 at 2:06 PM, Cyrille Rossant<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>>
wrote:

Can you try custom measures and propose one that works better for you?
Le dimanche 4 octobre 2015, nsteinme<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> a écrit :

Ok, I would like to "re-up" this issue. I have now observed more
examples
of this. Somehow it prefers to give you a "most similar" cluster that
has
nothing on the channels that the "best unsorted" cluster inhabits,
rather than give you ones that are on the same channels but are a bit
different. It may to do with the fact that there is no normalization -
so a
unit with big overlapping features looks potentially "more distant"
than
one with zero overlapping features.
Can we move this back to 0.3.0? I think it is a big problem.
—
Reply to this email directly or view it on GitHub
https://github.com/kwikteam/phy/issues/273#issuecomment-145348854.

—
Reply to this email directly or view it on GitHub
https://github.com/kwikteam/phy/issues/273#issuecomment-145349051.

—
Reply to this email directly or view it on GitHub
https://github.com/kwikteam/phy/issues/273#issuecomment-145349277.

K, I will talk with Kenneth then try something.
On Sun, Oct 4, 2015 at 2:13 PM, Cyrille Rossant<EMAIL_ADDRESS>wrote:

I will have a look, in the meantime maybe you can try to change the code
directly in the source?
Le dimanche 4 octobre 2015, nsteinme<EMAIL_ADDRESS>a écrit :

You think it will work? custom quality function doesn't work.
https://github.com/kwikteam/phy/issues/627
On Sun, Oct 4, 2015 at 2:06 PM, Cyrille Rossant <
<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>>
wrote:

Can you try custom measures and propose one that works better for you?
Le dimanche 4 octobre 2015, nsteinme<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> a écrit :

Ok, I would like to "re-up" this issue. I have now observed more
examples
of this. Somehow it prefers to give you a "most similar" cluster that
has
nothing on the channels that the "best unsorted" cluster inhabits,
rather than give you ones that are on the same channels but are a bit
different. It may to do with the fact that there is no normalization

so a

unit with big overlapping features looks potentially "more distant"
than
one with zero overlapping features.
Can we move this back to 0.3.0? I think it is a big problem.
—
Reply to this email directly or view it on GitHub
https://github.com/kwikteam/phy/issues/273#issuecomment-145348854.

—
Reply to this email directly or view it on GitHub
https://github.com/kwikteam/phy/issues/273#issuecomment-145349051.

—
Reply to this email directly or view it on GitHub
https://github.com/kwikteam/phy/issues/273#issuecomment-145349277.

—
Reply to this email directly or view it on GitHub
https://github.com/kwikteam/phy/issues/273#issuecomment-145349380.

Hey, I talked with Kenneth and we came up with some things to try. It may take a while for me to try them though because I have to find good test cases. Could you assign this issue to me, though? I can do it.


Define and Expose a CDS-Based Travel Data Model

Tutorials: https://developers.sap.com/tutorials/abap-environment-data-model.html
In Step 5 the answers should accept both values: Service Binding OR Service binding (OR service binding).
Many thanks! Great tutorial!

Hi @Klickerlebnis,
thank you for your feedback. We'll update this as soon as possible.
Best regards,
Merve

Hi @MichaelCzcz  ,
I created following pull request: #6834. Can you merge my pull request?
Thank you in advance.
Best regards,
Merve


Fix completion of incomplete

When class Foo have getMessage, completion on new Foo().ge| fail.
Because javacomplete2 plugin detect ge as class name incomplete. then finding class ge*.
I moved this part at last of case which checking completion-method.

Looks like it breaks class name compeltion. Will look further.

Now should work both completions in right way.


weird result of isValid()

Description of the Issue and Steps to Reproduce:
i want to detinmine if the date format is 'D/M/YYYY' using moment("1991-10-10T00:00:00", 'D/M/YYYY').isValid()
but i got wrong result for different year
Environment:
Chrome,IE
moment("1991-10-10T00:00:00", 'D/M/YYYY').isValid()
false
moment("2001-10-10T00:00:00", 'D/M/YYYY').isValid()
true
moment("2000-10-10T00:00:00", 'D/M/YYYY').isValid()
false

By default, Moment is very aggressive about finding a way to parse your string. You can see how it tries to handle each string with moment("1991-10-10T00:00:00", 'D/M/YYYY').parsingFlags() . What you probably want to do is to parse in strict mode:
moment("2001-10-10T00:00:00", 'D/M/YYYY', true).isValid() //=> false


[FEATURE REQ] Add Priority Property to CloudTask Class

Library name
Microsoft.Azure.Batch
Please describe the feature.
Add Priority Property to CloudTask Class.
Tasks with Higher priority would all run before tasks with lower priority get scheduled and run.
DependsOn would be followed as it currently is.
Currently, we see no way to specify some tasks should be run before others without the dependson property.
We are try to get the most efficient use of all the nodes and cores by letting tasks that finish quickly grab another smaller slice of work to do. With a priority property, we could mark a set of smaller job slices as low priority so they do not get run before the large ones.

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Core:0.19363692,Event Hubs:0.09095503,Storage:0.0798744'

@scottbright22 We are looking into it and get back to you for any additional information.

This is not a feature that we plan to provide at this time. We hope to in the future, but at the moment Task Dependencies are the only available option.


translate attribute

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Feature request
[X ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

Can we get documentation on how to translate an attribute?
Example from angular docs:

Added to the docs:
Attribute
Property


Snmp-set with 0 on number field does not work

Describe the bug
I am trying to set the snmp-value of an oid by doing a write via the iobroker-objects view.
This is working fine for all values, except the 0.
By looking into a wireshark trace it seems that "null" is transmitted instead.
I tried this manually via snmpset and it is working as expected.
snmpset -v1 -c xxxxxx  <IP_ADDRESS> .<IP_ADDRESS>.4.1.137<IP_ADDRESS>.<IP_ADDRESS>.4 i 0
Expected behavior
I would expect, that a "0" is written.
Versions:
Platform: linux
operating system: linux
Architecture: x64
CPUs: 2
Speed: 2903 MHz
Model: Common KVM processor
RAM: 7.5 GB
System uptime: 2 d. 04:25:44
Node.js: v16.19.1
time:<PHONE_NUMBER>243
timeOffset: -120
adapters count: 561
NPM: 8.19.3
Disk size: 14.7 GB
Disk free: 9.2 GB
Uptime: 2 d. 03:59:26
Active instances: 14
Path: /opt/iobroker/

SNMP-Adapter version: 2.4.5
JS-Controller: 4.0.24

Additional context
Add any other context about the problem here.

@JM2014 Thanks for the very complet information provided with this issue.
A first review of the relevant ciode part did not show a problem.
I would ask to do the following things:
a) You seem to have three states with identical oid. I would ask to disable two of them. I'm not sure whether sending the same oid multiple times could cause troubles. (I do not really think this is the problem, as this ist not realted to 0 / non zero values, but trying this is not a big effort).
b) The decoded smnp data shown seems to be related to the get request which is issued after the set operation. Could you please check the iobroker logs and post the related liones? I think there should be en entry with either (or both) of session.set or session.get. In addition you write that snmpset worked. Did you check that a snmp read operation immediatly after the set works too? I only would like to double check that you device can handle the zero.
c) Is the decoded data from wireshark? As it seems to be a get(read) request could you try to capture the write (set) request too ?
d) Please activate the option "add raw states at tab Options

You should get a new state names *-raw after a normal successful read. Please provide the json stored within this data. (Please check for sensitive data - but I do not think there should be anys passwords or tokens within).
I'll try to reproduce the problem but I must first search for some snmp device which accepts numeric data for write.
Sorry that I cannot prpvide a fast fix.

Hi, first of all, thank you that you are looking for this problem!!!
a. I removed all, except one.
b. + c.: I will add a wireshark. In this wireshark I tried the values: 5,0,6,0,7,8,0
Of course these values are not defined at the destination-device, but they should be send out.
When looking at the trace it seems, that there are no SNMP-Sets with "0" send out. Do you have an idea here?
d: {"oid":"<IP_ADDRESS>.4.1.137<IP_ADDRESS>.<IP_ADDRESS>.4","type":2,"value":1}
Greetings
Juergen

OK,
a) duplicate OIDS can be skipped ass source of problem for sure now.
d) json looks like expected - no surprise
Please check wireshark traces. They seem to have been lost somewhere. At least I do not see any of them.
I do not have any idea why 0 should not be sent - but I will investigate further

I am doing the traces on a firewall between. But I can not see any reason, why it should drop the snmp-sets with "0".
I will try to do a tcpdump tomorrow on the iobroker itself...But I would bet, that I will not see them there....that would mean, that the packets are not send out...,-)

Please could you tray to capture debug logging
-) temporary disable all unrelated snmp devices to reduce the number of traceinfos written
-) disable all unrelated oids to reduce the number of traceinfos written
-) start adapter with debug logging
-) perform a write with "0" value
There should be a debug logged like
onStateChange triggered - id ${pFullId} - with the id of the OID written
Please provide this trace and the following traces wi#hcih will log the processing of the value and teh called functions.
Thanks in advance

I think I located the bug. Please do not set any further effrot at your side until I come back with more infos

@JM2014
Please retry new verion 2.4.6 available at github now and at latest at least tomorrow.
Please let me know if the problem is solved with the changes.

The new 2.4.6 is working fine.
You solved the problem! Thankyou very much! Great!

Fixed with 2.4.6
Problem prohibited setting of boolean false and empty string too.


Add support for postgres aliases with double quotes

This PR implements https://github.com/DerekStride/tree-sitter-sql/issues/46
Let me know if I missed something/

Off topic suggestion: What do you think about running tests on PRs? I see currently they are set only any branch push, but forks doesn't fall into that category.


Some controls have only NullEvents

Might be worth if you fill in some more details about platform, what NameTextBox is etc.

OC: Windows 10
.Net: net5.0
Avalonia: 0.10.6
ObservableEvents: 1.0.10
NameTextBox  it's Avalonia.Controls.TextBox

Thanks.

I just stumbled across the same issue.
My theorie is, that it is because of chaining the ObservableEvents-Source-Generator and the Avalonia-Source-Generator.
Because it works when the generated field is explicitly casted to a type like this:
((Button)Button0).Events().Click.Select(_ => "0")


Update flesh, mtc, ashib, add fleshFetcher

Update flesh, mtc, ashib, add fleshFetcher

Checks failed on testing fleshFetcher (unknown why it doesn't like this one)
● supply fetchers › test fetcher for token a1ce0414d79b040f986f3bcd187a7563fd26662390dece6b12262b52464c45534820544f4b454e
BlockfrostServerError: The requested component has not been found.


PullAsync returns 500, PushAsync works just fine

I have windows phone app that's trying to connect to its .Net backend. Everything was working fine before I started using Offline scenario.
Adding new rows to the database works as expected but pulling the data returns a 500.
The request could not be completed.  (Internal Server Error)
Here is the stack trace for the client side:
at Microsoft.WindowsAzure.MobileServices.MobileServiceHttpClient.d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Microsoft.WindowsAzure.MobileServices.MobileServiceHttpClient.d__1d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()    at Microsoft.WindowsAzure.MobileServices.MobileServiceHttpClient.<RequestAsync>d__4.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()
at Microsoft.WindowsAzure.MobileServices.MobileServiceTable.d__f.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()    at Microsoft.WindowsAzure.MobileServices.MobileServiceTable.<ReadAsync>d__7.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()
at Microsoft.WindowsAzure.MobileServices.Sync.PullAction.d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Microsoft.WindowsAzure.MobileServices.Sync.TableAction.d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Microsoft.WindowsAzure.MobileServices.Sync.MobileServiceSyncContext.d__3b.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Microsoft.WindowsAzure.MobileServices.Sync.MobileServiceSyncContext.d__27.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at MyApp.Cloud.MyAppCloud.d__4.MoveNext()

You may be requesting system properties that are not present in your backend. I recommend using Fiddler to see the actual request that is being sent.
I'm going to close this issue for now--this is the kind of question that is better suited for the forums, since it is not a reproducible bug.


Update to Azure runtime 3 and .net core 3.1

Update Dedicated Host Manager to Azure Runtime v3
Update all projects and dependencies to .Net Core 3.1
Additional Notes:

VS2019 used for development and testing
Tests executed and validated Cloud deployment with updated Runtime

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


Raising error when incompatible inputs are passed to mitigation

This PR addresses #308 which arose from wrong initialization of the calibration circuits which did not raise a meaningful error. There may be additional changes that can be done (e.g. passing the circuit to the calibration circuits method and letting it decide what the quantum register is by itself).

@gadial could you add a bug fix release note?

@gadial could you add a bug fix release note?

Done


Keep input roots during simplification

The tests are failing at least in part b/c we are "too clever" in how we treat our temporary table states during simplification.

The tests fail because not all input nodes with ancestry and null output IDs are input roots.
There are two paths forward:

Recognize that an input root must have time 0 (by definition, given what we are doing), so we can filter accordingly.
Figure out a more general approach...

Putting this aside--a distraction at the moment...


Error event not triggered when model destroy fails on ajax call

Hi,
I'm trying to figure out, what is the actual flow of events, when destroying model.
I think I see at least two issue related to model destroy.

error event is not triggered when ajax call fails (this is different from model save method, where error event is always triggered in case of ajax failure)
model collection removal should be delayed after successful ajax call, meaning that model is only removed from collection when ajax DELETE was successful

Here is the basic test:
Jsfiddle: http://jsfiddle.net/mauron85/115q8vsu/3/
var MyCollection = Backbone.Collection.extend({
  url: '/collection'
});

// 1. create instance of collection and model
var collection = new MyCollection;
var model = new Backbone.Model({
    id: '1'
});

// 2. add model to collection
collection.add(model);

// 3. this will be fired first after model.destroy() - EXPECTED
collection.on("request", function (model) {
  console.log('request');
});

// 4. this will be never fired as ajax call fails - EXPECTED
collection.on("sync", function (model) {
  console.log('sync');
});

// 5. this will be never fired, I was expecting this one to be triggered when ajax fails (same as for model save ...)
collection.on("error", function (model) {
  console.log('error');
});

// 6. this is fired last - at least confusing, as destroy ajax call failed
collection.on("destroy", function (model) {
  console.log('destroy');
});

// 7. this is fired right after 4. - at least confusing, as destroy ajax call failed
model.on('destroy', function () {
  console.log('model destroyed');
});

// 8. UNEXPECTED (removing model from collection,
// IMHO should be delayed and done after sucessfull ajax call)
collection.on("remove", function (model) {
  console.log('model removed');
});

model.destroy().always(function () {
  // Expecting collection length to be 1, as destroy was not succesfull,
  // but it's 0 - model was removed from collection.
  // Should I add model back on ajax failure?
  console.log(collection.length);
});

Let's compare it with model save. No issue here. Events are tiggered as expected according to docs.
var MyCollection = Backbone.Collection.extend({
  url: '/collection'
});

// 1. create instance of collection and model
var collection = new MyCollection;
var model = new Backbone.Model({
    id: '1'
});

// 2. add model to collection
collection.add(model);

// 3. this will be fired first - EXPECTED
collection.on("request", function (model) {
  console.log('request');
});

// 4. this will be never fired as ajax call fails - EXPECTED
collection.on("sync", function (model) {
  console.log('sync');
});

// 5. this will be fired - EXPECTED
collection.on("error", function (model) {
  console.log('error');
});

model.save().always(function () {
  console.log(collection.length);
});

I think you're looking for model.destroy({ wait: true }). That'l make it wait until a successful ajax delete returns before triggering events and before removing the model from the collection.

Will you at least think about it for second? Or you like closing my issues at sight?
Please, read and reconsider at least this one:
error event is not triggered when ajax call fails (this is different from model save method, where error event is always triggered in case of ajax failure)

error event is not triggered when ajax call fails

The error event will be triggered on the model, but since the model is no longer a part of the collection it won't trigger an error event on the collection. Backbone's optimistic about any server requests it makes, so it's proceeded as if the request will pass. If you'd like for it to wait for the response instead, { wait: true}.
http://jsfiddle.net/115q8vsu/4/

But this is inconsistent with save method, which is also optimistic.

Because #save optimistically adds the model to the collection, hence the events being triggered on the collection. #destroy optimistically removes the model from the collection, preventing events from triggering there.


Removed namingstrategy for doctrine

Q
A

Bug fix?
yes (poosible bug for extended sulus)

New feature?
no

BC breaks?
no

Deprecations?
no

Fixed tickets
none

Related issues/PRs
https://github.com/sulu/sulu/pull/2380

License
MIT

Documentation PR
none

What's in this PR?
This PR removes the naming-strategy for doctrine.
Why?
Doctrine drops columns which name is generated and recreate it if the naming-strategy was changed (was done before 1.2 in https://github.com/sulu/sulu-standard/commit/b712c39ff27050107e1328677213d97d63089cea).

@chirimoya I think we said that we stick with the symfony-standard configuration, right? Then we should close this one. @wachterjohannes already knows about that.

Closed it for now, I think we already agreed on it. Can be reopened otherwise.


Bug: clicking on up arrow does not increase the hour

Selecting the hour input and then clicking on the up arrow does not increase the hour, it throws an error instead: ReferenceError: optionsdate is not defined

see #12 , I link the fix commits with another issue.  : (


CCACHE_DIR environment variable is ignored by action

If the CCACHE_DIR environment variable is set ccache will use that for its cache location but ccache-action is hardcoded to use .${ccacheVariant}. The action should either honor CCACHE_DIR or set it to the hard coded path.

I agree. Do you want to send a PR?

Maybe we can even stop overriding the cache dir. I’m not sure why we do it.

Maybe we can even stop overriding the cache dir. I’m not sure why we do it.

Without any context my guess is this is done to keep all files generated during the action in the workspace directory. It might be good to keep this behavior and override the environment variable by using the --dir argument to specify the directory in all calls to ccache.
Even though the cache_dir is set in the config that is overriden by the environment variable. https://ccache.dev/manual/latest.html#_configuration

@n3world Whats the use case of overriding CCACHE_DIR? Was it set accidentally?

@n3world Whats the use case of overriding CCACHE_DIR? Was it set accidentally?

I do not think I know exactly what you are asking so I'll just explain the situation a bit more.
CCACHE_DIR is currently set in the environment in which this action runs. This action does not check the setting of that variable and always tries to use <workdir>/.ccache. ccache prefers environment variables over settings in the configuration file so when the variable is set ccache does not use the directory this action expects and this action does not work.
Two ways to resolve this would be this action honors the environment variable and puts everything there or it overrides it and uses the directory it wants to. I was suggesting to go with the later fix since that provides more isolation and less likely to have issues if multiple compilations are using the same filesystem, fighting over setting configuration values in the configuration file and cache bloat.
If you were actually asking why the environment variable is set in the first place I don't think that it is too important but for me it is part of the docker container environment. The container is used for development and there it is convenient to have one volume location for the ccache just for consistency in scripts across all users.

Thanks @n3world, that makes it more clear to me. You explained it is a side effect of re-using a docker container for development and CI. That's what I meant with "accidental". I understand you are not asking for implementing the possibility to override CCACHE_DIR, but to fix the unexpected behavior you see. So there isn't a use case, there is "just" developer pain, spending time debugging why the actions isn't working the way it should.
However this is harder to fix than it seems. Afaik steps in a workflow are isolated. Removing CCACHE_DIR from the environment won't work, because it is only unset in the setup action step, compilation runs in its own step and CCACHE_DIR might just be there again. I guess you introduce it in your build scripts. At the moment I can only think of checking if CCACHE_DIR is set and either log a warning or even fail the action. But if CCACHE_DIR is set in build scripts I wonder if we are even able to detect it at all. Again the action finalizer runs in its own step and likely doesn't have CCACHE_DIR set. With other words: I am not sure the action can honor CCACHE_DIR even if we would want to implement it.
@n3world Can you tell me where CCACHE_DIR is set in your case?
I suggest to add a troubleshooting section in the Readme.

However this is harder to fix than it seems.

I know in steps you can write to $GITHUB_ENV  file to set an environment variable that are seen by subsequent steps. The same could be done in the setup action

But if CCACHE_DIR is set in build scripts I wonder if we are even able to detect it at all. Again the action finalizer runs in its own step and likely doesn't have CCACHE_DIR set. With other words: I am not sure the action can honor CCACHE_DIR even if we want to implement support.

If it is just set in the build script and not global this action couldn't do anything about that, other than just documenting that CCACHE_DIR being set breaks this action

@n3world Can you tell me where CCACHE_DIR is set in your case?

It is in the environment for the docker image so it is there for anything using that image.

Getting back to the question raised in https://github.com/hendrikmuhs/ccache-action/issues/96#issuecomment-1225258352: why do we need to override the cache directory?
In particular, storing it inside the worktree causes unintended consequences for actions that push back to the Git repository. If we must override, I propose to store it alongside the worktree.


Passing writer_options with generate()

I'm calling generate() function to create a code128 barcode, and I need to pass custom writer_options payload. Here is the code fragment:
writer_options = {
    'module_width': 0.3,
    'module_height': 25.0,
    'quiet_zone': 1,
    'font_size': 10,
    'text_distance': 0,
    'background': 'white',
    'foreground': 'black',
    'write_text': True,
    'text': '',
}
name = generate('code128', foo, output=f"barcode_{foo}", text=' ', writer=ImageWriter(), writer_options=writer_options)

This code gives me the following error message:
Traceback (most recent call last):
  File "gen_barcode_foreign.py", line 55, in <module>
    name = generate('code128', tracking, output=f"barcode_{tracking}", text=' ', writer=ImageWriter(), writer_options=writer_options)
  File "d:\python_test\barcodes\venv\lib\site-packages\barcode\__init__.py", line 73, in generate
    barcode = get(name, code, writer, options)
  File "d:\python_test\barcodes\venv\lib\site-packages\barcode\__init__.py", line 61, in get
    return barcode(code, writer, **options)
TypeError: __init__() got an unexpected keyword argument 'module_width'

I tried to edit __init__.py, changing the line #61 from return barcode(code, writer, **options) to return barcode(code, writer), and it helped, generate() now works fine.
Not sure if this is the correct way to solve this issue though.

I found that error too and I realized the init of Code128 is missing **kwargs param (file codex.py line 139)

Better solution:
With this solution you can set up options for writer and code at the same time
def generate(name, code, writer=None, output=None, writer_options=None, code_options=None,              text=None, pil=False):     barcode = get(name, code, writer, code_options)     if pil:         return barcode.render(writer_options, text)     if isinstance(output, _strbase):         fullname = barcode.save(output, code_options, text)         return fullname     else:         barcode.write(output, code_options, text)
Usage:
from barcode.writer import ImageWriter
from barcode import generate
generate(
'CODE39',
'130000123',
pil=True,
writer=ImageWriter(),
writer_options={'module_height': 5.0, 'text_distance': 1.0},
code_options={'add_checksum': False}
)

This is now fixed by @987da3b696050e04a9a3555693cf421a0c3ee146.


Using outdir name starting with dot doesn't seem to work

Description
When using dot as the starting character for outdir name (e.g. .panda) files don't get generated despite logged as generated.

Link to Reproduction
https://stackblitz.com/edit/vitejs-vite-ge2r6zsu?file=panda.config.ts
Steps to reproduce
No response
JS Framework
No response
Panda CSS Version
latest
Browser
No response
Operating System

[ ] macOS
[ ] Windows
[ ] Linux

Additional Information
No response

It works as expected on my machine. This is probably happening because Stackblitz hides folders that start with .*
Try it locally, and it should work.


Exercise <IP_ADDRESS> honour comment

@winitzki commented [...]
In chapter02/worksheets/solution<IP_ADDRESS>_AR.scala:

@@ -0,0 +1,17 @@
[...]
+Exercise <IP_ADDRESS>

Find all integer pairs 𝑖, 𝑗 where 0 ≤ 𝑖 ≤ 9 and 0 ≤ 𝑗 ≤ 9 and 𝑖 + 4 ∗ 𝑗 > 𝑖 ∗ 𝑗.
Hint: use flatMap and filter.
*/

+val a = (0 to 9).flatMap(x => (0 to 9).map { y => (x, y) } )
+val b = a.map{ case x => x._1 + 4 * x._2 }
I would suggest to use case (x, y) => here as well.

BTW will do that as exercise, however, not convinced WRT rationale behind. Because using simply case  seems more generic, that way losing information of the current type in question.

The reason is that { case (x, y) => ...} will fail to match (and fail to compile) unless the type is actually a tuple.  { case x => ...} will never fail to match.
Suppose you are writing x.map { case x => x._1 + 4 * x._2 } where you expect x to have type Seq[(Int, Int)].  But, by mistake, x has type Seq[(Int, Int, Int)]. Your code with case x will still match and compile but {case (x, y) => ...} will fail to compile and will tell you that the types don't match.
So, writing {case (x, y) =>  is actually more specific and less generic.

Okay, did a little check with List:
scala> val x = List(9, 3)
x: List[Int] = List(9, 3)

scala> val y = List(5, 6)
y: List[Int] = List(5, 6)

scala> val z = List(x) ++ List(y)
z: List[List[Int]] = List(List(9, 3), List(5, 6))

scala> z.map{ case (i, j) => }
<console>:13: error: constructor cannot be instantiated to expected type;
 found   : (T1, T2)
 required: List[Int]
       z.map{ case (i, j) => }

scala> z.map{ case i => i }
res13: List[List[Int]] = List(List(9, 3), List(5, 6))

scala> z.map{ case List(i, j) => i }
res14: List[Int] = List(9, 5)


Added Taskade

Just added Taskade's mobile app to the list. I think it fits under the writing section as every document inside Taskade is an outline, tree structured database. https://itunes.apple.com/app/taskade/id1264713923

Oh wait.

You should PR it to this list.
This is my personal list and I am not using Taskade so I reverse this change.

@nikitavoloboev oops, got it, thank you!


message_scroll: Convert module to TypeScript

Apparently something is broken preventing me from approving this in the UI, but approved.


[RDK-52502] added new mount/unmount APIs

initial implementation of mount & unmount operations
Description
What does this PR change/fix and why?
Adds new mount & unmount API calls to support dynamic mounting/unmounting of USB mass storage devices
Test Procedure
Use the following commands to mount and unmount directories in already running containers:
DobbyTool mount com.sky.as.apps_com.bskyb.epgui  /mnt/usb /tmp/newmount 0
DobbyTool unmount com.sky.as.apps_com.bskyb.epgui /tmp/newmount

Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Other (doesn't fit into the above categories - e.g. documentation updates)

Requires Bitbake Recipe changes?

[x] The base Bitbake recipe (meta-rdk-ext/recipes-containers/dobby/dobby.bb) must be modified to support the changes in this PR (beyond updating SRC_REV)

requires kernels 4.18 or higher since this implementation requires SYS_open_tree and SYS_move_mount syscalls.

need to add L1/L2 tests

replaced with #336


[Rust] unsafe transmute cause runtime error

The impl From<ByteArray> for ArgValue<'static> is unsound and cause runtime error:
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

Here is a reproducible example:
https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=79b8e8c9abda957d250b0c780582f014
miri catch this UB:
error: Undefined Behavior: type validation failed: encountered a dangling reference (use-after-free) at .0

There is another error:
In ArgValue 's to_tvm_value() ( inside TVMPODValue! macro).
    match &self {
        Bytes(val) => {
            (TVMValue { v_handle: val as *const _ as *mut c_void }, TVMArgTypeCode_kTVMBytes)
        }
        Str(val) => { (TVMValue { v_handle: val.as_ptr() as *mut c_void }, TVMArgTypeCode_kTVMStr) }
    }

The type of val is &&ffi::TVMByteArray, so the pointer return is a invalid dangling pointer.

Thanks for the issue, I have another open issue #6098 that is worried about these kinds of things. I believe the old TVMArgValue and TVMRetValue's implementations were previously unsound, and now more unsound after migrating things to object system. I believe we need to remove all non-owned variants but I haven't got around to doing this yet. If you have the cycles happy to accept a PR on this. cc @mwillsey


Doc: updated TAOS-CI installation manual

This commit is to update the existing TAOS-CI installation manual to help users that do not have CI experience enough.
Changes proposed in this PR:

Updated installation manual of TAOS-CI for user convenience
Removed unnecessary explanations

Signed-off-by: Geunsik Lim<EMAIL_ADDRESS>
[Template] PR Description
In general, github system automatically copies your commit message for your convenience.
Please remove unused part of the template after writing your own PR description with this template.
$ git commit -s filename1 filename2 ... [enter]

Summarize changes in around 50 characters or less

More detailed explanatory text, if necessary. Wrap it to about 72
characters or so. In some contexts, the first line is treated as the
subject of the commit and the rest of the text as the body. The
blank line separating the summary from the body is critical;
various tools like `log`, `shortlog` and `rebase` can get confused
if you run the two together.

Further paragraphs come after blank lines.

**Changes proposed in this PR:**
- Bullet points are okay, too
- Typically a hyphen or asterisk is used for the bullet, preceded
  by a single space, with blank lines in between, but conventions vary here.

Resolves: #123
See also: #456, #789

**Self evaluation:**
1. Build test: [ ]Passed [ ]Failed [*]Skipped
2. Run test: [ ]Passed [ ]Failed [* ]Skipped

**How to evaluate:**
1. Describe how to evaluate in order to be reproduced by reviewer(s).

Add signed-off message automatically by running **$git commit -s ...** command.

$ git push origin <your_branch_name>

:memo: Version: 1.20180811. Thank you for submitting PR #183. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://invain.mooo.com/.


West should default to no-tags and initial shallow fetch

Introduction
West defaults to fetching full history and tags for all modules, which is slow and results in a big repository. The proposal is to change the default to do a shallow fetch with no tags.
Problem description
A default upstream Zephyr checkout (west init; west update) at this point in time is about 5GB, and includes all history of all modules. Practically though, I suspect that a random user does not need the full module history, someone working on a module project or vendor may only need the history for some selected modules, and only people working on the core OS may want a full repository.
The difference between doing a shallow or full fetch on a not too powerful machine is significant, especially for the fetch time, for example on my laptop:

west update takes about 4 minutes and results in a 5GB repository
west update -o=--depth=1 -n takes 2 minutes and results in a 4.2GB repository

Note that this is just the time for fetching the modules, the main upstream zephyr repo is already in place, and it takes about 920MB, but this also means that there would be even more time saved if west was running on a project and doing a shallow fetch of the main zephyr repo as well.
Proposed change
Change west to:

do not fetch tags by default (right now it always does it, which does not quite make sense with shallow fetches).
detect if the module is being fetched for the first time, and default to do a shallow fetch, unless it's requested to initialize new modules with full history (currently fetch uses the same flag regardless, clone is not used).
if the module has been fetched already, do a normal fetch, so one could just un-shallow a repository using the standard git tooling (git fetch --unshallow) and then west would not create any more grafted commits, this also means that updates of all modules are always going to have history from the initial fetch.

Concerns and Unresolved Questions

Why does west default to always request tags right now? git default is to only fetch them if they are part of the history, I'm suspecting that changing the default may break some use case
Is this even worth it? Changing the default behavior may be confusing for some users, break some use case. The difference in space is not as big as I hoped, the difference in time is significant so it may help the perception of project being heavy, but I'm not too sure it's worth the change in behavior.

cc @mbolivar-ampere @henrikbrixandersen @nashif @carlescufi

do not fetch tags by default (right now it always does it, which does not quite make sense with shallow fetches).

Not so sure on this, there are manifests that use tags for revisions which should not be broken, and the tag can also be used for versioning i.e. zephyr boot messages

Not so sure on this, there are manifests that use tags for revisions which should not be broken, and the tag can also be used for versioning i.e. zephyr boot messages

Fetching by tag seems to work regardless (changed a project revision to a tag, deleted the module, fetched with west update -n, works fine), guess it's resolved by the remote, git describe would definitely break though, good point.


Changelog page + update notification

A separate page detailing the latest changes/a full changelog should be added, informing users about any recent feature additions or bugfixes. Admins should have edit access on that page, allowing for new entries to be quickly created using the frontend only.
To increase the visibility of updates, a new notification type could be added, being automatically sent to every user upon button-click by an admin.

Tasks

[x] Add Changelog display page
[x] Add Changelog modify modals for admins
[x] Add display of new notification

While completed on the frontend side, we currently have the problem of no localization being available on the backend - thus not being able to serve appropriately translated changelog content to the user.
This requires the introduction of user language settings for the backend and will thus be postponed until the language task has been completed.


Proguard sees duplicate CustomType.class entries in multi-module project

Summary
Proguard sees duplicate CustomType.class entries in multi-module project
Description
I have a multi-module project. Module0 is the main module. Module1 has apollo lib and plugin. Module1 also has a custom type with one custom mapping. Everything works great! Now, we also have Module2 which also has apollo lib and plugin. It does not have a custom type. Module2 also works great as part of a sample app. Problem happens when adding Module2 to project with Module0 and Module1. Debug builds and runs okay, but we run Proguard on release builds, and it fails on duplicate CustomType class on the final pass when it gets to Module2.
Execution failed for task ':module0:transformClassesAndResourcesWithProguardForGoogleRelease'.
java.io.IOException: Can't write [/Users/me/multiModuleProject/module0/build/intermediates/transforms/proguard/google/release/0.jar] (Can't read [/Users/me/module2Project/module2/build/intermediates/runtime_library_classes/googleRelease/classes.jar(;;;;;;;**.class)] (Duplicate jar entry [type/CustomType.class]))
Version
1.2.0

Unfortunately having multiple modules can lead to clash of class generation, the only recommendation is to provide different package names for different modules. Otherwise I can think of 2 places where model generated by Apollo can clash, one is this class you mentioned used for custom sclar type adapters CustomType another case is when both modules use the same enum.
@martinbonnin , @tasomaniac  do you folks have any suggestions on this?

My recommended solution would also be to put them into packages. That's how jvm languages work. Since Apollo generates Java/Kotlin code, that makes sense to me.
Another thing that you can try is to put this as a Proguard rule
-dontwarn **.CustomType

I'm actually surprised that the debug build runs since you can't have 2 different versions of CustomType in the classpath at the same time (well...unless you do some ClassLoader magic but you usually don't want to do that).
My guess is that it's either a very lucky coincidence that CustomTypes are binary compatible or that you'll have runtime crashes at some point.
All in all, agree with @sav007 and @tasomaniac, you can use packages, either by adding subfolders under src/main, e.g. src/main/graphql/com/example/schema.json or with the rootPackageName option in gradle.

Thanks for the suggestions. Moving schema.json  in the library module to a new package resolved the problem for.


Global S3 configuration

When I move my S3 credentials to config.rb I receive the following error when kicking off a backup.
Missing required arguments: aws_access_key_id, aws_secret_access_key
It seems that these params are not passed to the fog gem.
(Using 3.0.23)

@meskyanichi @pat

Have you added it like this into the config.rb file?
Backup::Configuration::Storage::S3.defaults do |s3|
  s3.access_key_id     = "123"
  s3.secret_access_key = "123"
end

Yes. When I run the model it says that the aws access key and secret are missing.
Which I think is fog exploding from the missing param.
On 06/03/2012, at 7:44 AM, Dean Perry wrote:

Have you added it like this into the config.rb file?
Backup::Configuration::Storage::S3.defaults do |s3|
 s3.access_key_id     = "123"
 s3.secret_access_key = "123"
end

Reply to this email directly or view it on GitHub:
https://github.com/meskyanichi/backup/issues/291#issuecomment-4331361

How are you triggering the backup because it sounds as though you're running it a different way? Also, what version of fog do you have?


2-class problem

Is 2-class the following code in fairseq/data/raw_audio_text_video_dataset.py?
If so, why are the sentiment_score 0 and 1?
            self.emotion_dictionary = {   #modei senti 2 class

                '0': 0,
                '1':1
            }

It is just assigning a class label in two class cases. In MOSEI and MOSI ,
same script used to assign the real score.
On Wed, Apr 7, 2021, 13:22 Chenpuh @.***> wrote:

Is 2-class the following code in
fairseq/data/raw_audio_text_video_dataset.py?
If so, why are the sentiment_score 0 and 1?
        self.emotion_dictionary = {   #modei senti 2 class

            '0': 0,
            '1':1
        }

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/shamanez/Self-Supervised-Embedding-Fusion-Transformer/issues/2,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEA4FGQD2N7YAFCY2XYLUZTTHOXV5ANCNFSM42PZJBVA
.

Sorry, I don't understand what you mean.
in the paper MSAF Multimodal Split Attention Fusion:
For binary classification, we consider [-3, 0) labels as negative and (0, 3] as positive.
I want to know what 0 and 1 stand for in your repository?

It is for the binary sentiment classification. 0 for negative and 1 for
positive.
On Wed, Apr 7, 2021 at 1:33 PM Chenpuh @.***> wrote:

Sorry, I don't understand what you mean.
in the paper MSAF Multimodal Split Attention Fusion:
For binary classification, we consider [-3, 0) labels as negative and (0,
3] as positive.
I want to know what 0 and 1 stand for in your repository?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/shamanez/Self-Supervised-Embedding-Fusion-Transformer/issues/2#issuecomment-814537004,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEA4FGRL3W3IOLW3NPF3FZTTHOY43ANCNFSM42PZJBVA
.

--
[image: Augmented Human Lab] http://www.ahlab.org/ [image: uni]
https://www.auckland.ac.nz/en/abi.html
Gayal Shamane
Ph.D. Candidate
Augmented Human Lab
Auckland Bioengineering Institute | The University of Auckland

In *.csv, the format is as follows:
FileName,sentiment_score
03bSnISJMiM_1,2.400000095367432
03bSnISJMiM_3,-1.0
03bSnISJMiM_4,-1.75
03bSnISJMiM_5,0.0
03bSnISJMiM_6,0.0
03bSnISJMiM_7,0.8000000119209291
03bSnISJMiM_9,0.20000000298023224
03bSnISJMiM_11,-0.5
03bSnISJMiM_12,2.200000047683716
0h-zjBukYpk_1,-0.4000000059604645
0h-zjBukYpk_2,-2.799999952316284
0h-zjBukYpk_3,-0.20000000298023224
0h-zjBukYpk_4,-1.399999976158142
0h-zjBukYpk_5,0.8000000119209291
0h-zjBukYpk_6,-1.399999976158142
0h-zjBukYpk_8,0.8000000119209291

They are all floating point numbers. How can we make them 0 or 1?

no no in MOSEI and MOSI you need to predict sentiment scores. So itis
basically a regression task. In the paper, I have cited CMU-MOSI and MOSEI.
I know it is bit different :).
On Wed, Apr 7, 2021 at 2:08 PM Chenpuh @.***> wrote:

In *.csv, the format is as follows:
FileName,sentiment_score
03bSnISJMiM_1,2.400000095367432
03bSnISJMiM_3,-1.0
03bSnISJMiM_4,-1.75
03bSnISJMiM_5,0.0
03bSnISJMiM_6,0.0
03bSnISJMiM_7,0.8000000119209291
03bSnISJMiM_9,0.20000000298023224
03bSnISJMiM_11,-0.5
03bSnISJMiM_12,2.200000047683716
0h-zjBukYpk_1,-0.4000000059604645
0h-zjBukYpk_2,-2.799999952316284
0h-zjBukYpk_3,-0.20000000298023224
0h-zjBukYpk_4,-1.399999976158142
0h-zjBukYpk_5,0.8000000119209291
0h-zjBukYpk_6,-1.399999976158142
0h-zjBukYpk_8,0.8000000119209291
They are all floating point numbers. How can we make them 0 or 1?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/shamanez/Self-Supervised-Embedding-Fusion-Transformer/issues/2#issuecomment-814548418,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEA4FGT4JQRTSEIP6IUKTHDTHO5AHANCNFSM42PZJBVA
.

--
[image: Augmented Human Lab] http://www.ahlab.org/ [image: uni]
https://www.auckland.ac.nz/en/abi.html
Gayal Shamane
Ph.D. Candidate
Augmented Human Lab
Auckland Bioengineering Institute | The University of Auckland

In mosei/BA senti/label_file_*.csv, the format is as follows:
FileName,SEVEN,TWO
5Fs_7A_V2kA_0,1,1
5Fs_7A_V2kA_1,1,1
5Fs_7A_V2kA_2,1,1
5Fs_7A_V2kA_3,1,1
5Fs_7A_V2kA_4,1,1
Wfn7XvSEwUA_0,-2,0
Wfn7XvSEwUA_1,0,non
Wfn7XvSEwUA_2,2,1
Wfn7XvSEwUA_3,1,1
Wfn7XvSEwUA_4,0,non
Wfn7XvSEwUA_5,1,1
Wfn7XvSEwUA_6,1,1
Wfn7XvSEwUA_7,1,1
47472_0,-2,0
47472_1,0,non
47472_2,-1,0
47472_3,-2,0
47472_4,-2,0

How are they generated? Ceiling function?

Yes, it is.
On Wed, Apr 7, 2021, 14:50 Chenpuh @.***> wrote:

In mosei/BA senti/label_file_.csv*, the format is as follows:
FileName,SEVEN,TWO
5Fs_7A_V2kA_0,1,1
5Fs_7A_V2kA_1,1,1
5Fs_7A_V2kA_2,1,1
5Fs_7A_V2kA_3,1,1
5Fs_7A_V2kA_4,1,1
Wfn7XvSEwUA_0,-2,0
Wfn7XvSEwUA_1,0,non
Wfn7XvSEwUA_2,2,1
Wfn7XvSEwUA_3,1,1
Wfn7XvSEwUA_4,0,non
Wfn7XvSEwUA_5,1,1
Wfn7XvSEwUA_6,1,1
Wfn7XvSEwUA_7,1,1
47472_0,-2,0
47472_1,0,non
47472_2,-1,0
47472_3,-2,0
47472_4,-2,0
How are they generated? Ceiling function?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/shamanez/Self-Supervised-Embedding-Fusion-Transformer/issues/2#issuecomment-814561926,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEA4FGUWX7ACFBEUUF4LZ4LTHPCADANCNFSM42PZJBVA
.

Both sentiment_score or BA senti can be used in this repository, right?
Or  need to modify some code to use it?

Just the score. Later u need to ceil the scores inorder to calculate the
BA. During the training we do not use any classes.
On Wed, Apr 7, 2021, 14:59 Chenpuh @.***> wrote:

Both sentiment_score or BA senti can be used in this repository,
right?
Or need to modify some code to use it?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/shamanez/Self-Supervised-Embedding-Fusion-Transformer/issues/2#issuecomment-814564863,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEA4FGVELQPJAJAXF67HY4TTHPDB3ANCNFSM42PZJBVA
.

In other words, 7-classes and 2-classes are the same, but the evaluation criteria are different. Is 7-classes more detailed?

Exactly. I also faced the same problem when I just started this. So I
really understand how you feel  :). But for some reason this is how they
have evaluated. But I have seen recent work which just devices the score in
to clases prior to the training. You can use that way. So think this as a
regression task. Then after the training predict the score for test set.
Finally use the predicted score to assign them to classes  -3 to + 3.
On Wed, Apr 7, 2021, 15:10 Chenpuh @.***> wrote:

In other words, 7-classes and 2-classes are the same, but the evaluation
criteria are different. Is 7-classes more detailed?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/shamanez/Self-Supervised-Embedding-Fusion-Transformer/issues/2#issuecomment-814568158,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEA4FGW4OP7M7IEAHINB7ITTHPEKZANCNFSM42PZJBVA
.

Thank you very much for your help.


'jf rt ping' returns OK if you send empty credentials

Describe the bug
If you run jf c add with empty credentials and then run jf rt ping, the server returns OK.
Current behavior
No debug output.
Reproduction steps

Run jf c rm --quiet
Run jf c add add submit empty credentials.
Run jf rt ping and see that it returns OK

Not sure if this is intended or not. If this is intentional, please explain.
Obviously cannot login to Artifactory GUI with empty credentials.
Expected behavior
I am expecting that, since there is no user with the username "" and password "", the server will return 401 for bad credentials.
JFrog CLI version
2.21.4
Operating system type and version
Windows 10
JFrog Artifactory version
7
JFrog Xray version
No response

I was recently trying to rely on CT=1 jf rt ping to validate access to an Artifactory instance. I also realized that it was returning a success code for a configuration with no credentials set. My assumption from this was it was designed this way for the use case where one may be using the CLI for read-only access scenarios (i.e. files that can be downloaded without credentials; if a repository was configured to support this). So this might be working as expected.
I have updated my scripts to use a crude method to provide a somewhat better chance that a working state has access. First, I check if the default configuration has a password value configured (jf c show | grep Pass) -- and if so, then check if I can ping (CT=1 jf rt ping). For sure does not guarantee the client will have access to the specific repository planned for use, but I will at least know I'm checking accessibility with an authenticated user.
It would be nice to be able to explicitly check access to a specific repository, and more so even if a client has access to write to a repository. For example:
(note: this does not exist)
jf rt ping <my-repo> --access=write

Although this would fall under an enhancement over a bug, and no idea if the above CLI example is the "right" way to approach this.


Update PBK Token

TOKEN INFORMATION
Total number of tokens 500 million
Total number of tokens for ico 400 million
Token for Lucky 100 million
Token per phase 1 & 2 100 million each
Token per phase 3 & 4 50M each
Decimal 7
Platform ERC 20
Smart contract:0x077DC3c0c9543df1cdD78386DF3204E69E0DD274
Telegram = t.me/powerbankofficial
Cost of token in each phase
1ETH = 6000BK (1PBK =0.0002ETH)
(lucky ico for 1st 100 person only (1ETH for 1M PBK)
1st phase = 0.00002/PBK/with 40℅ bonus
2nd phase= 0.0002/PBK/ with 20% bonus
3rd phase = 0.0002/PBK/ with 10℅ bonus
4th please= 0.0002/PBK/with 2% bonus
Currencies accept in ico
ETHERIUM
Min contribution 0.5ETH
Max contribution 100ETH
White paper ,:https://drive.google.com/file/d/1b0mrfLCip6UGvyE4KpdDAImB-gAzH9Lc/view?usp=drivesdk
Website:http://www.powerbankcoin.com

The submitted content is in conflict
Please check it out


FIX to account for different versions of sphinx_gallery

See: http://sphinx-gallery.readthedocs.org/en/latest/getting_started.html. It's called sphinx_gallery now

comments addressed

merge when travis is happy
thx

thx @jasmainak


Fix files path "evaluate.py"

remove 'modals/' from open('modals/tfidf') and open('modals/modal')

Done !
Thanks :)


Add transpilation to ES5 for cicero-core

As raised in #243, some tools and environments require ES5.
This PR uses Babel to transpile the ES6 source for cicero-core, now in packages/cicero-core/src to ES5 in packages/cicero-core/lib. The build output is used for tests and webpacking.

Coverage decreased (-0.03%) to 91.065% when pulling 2fa533ad64d7f13bd8882d615f09f32dfd8a6ecd on mttrbrts:mr-ecma6-cicero-core into e9e467cc4adc19ef02b8561d70da42f681923079 on accordproject:master.


Update docstrings, codecov, readthedocs, pypi release

The aiida-workgraph repository has been transferred to the aiidateam organization, but the following setting still uses the old superstar54 account.

docstrings: Move to Sphinx docstring format (from Google)
codecov (this does not work anymore)
readthedocs
pypi release

We should at least fix the codecov.

It turned out that the readthedocs, pypi and codecov work correctly. The format of the docstring is reported in this issue #322 .
So, I closed this issue.