Bug report: little-snitch 3.6.2 download location 404's (newer version available?)

Description of issue
Attempting to force a reinstall of little-snitch (via brew cask install little-snitch --force), the download location https://www.obdev.at/downloads/littlesnitch/LittleSnitch-3.6.2.dmg returns 404. See output below.
FWIW, it appears Little Snitch 3.6.3 is the latest version.
Output of brew cask install little-snitch --force --verbose
/opt/boxen/homebrew/bin/brew tap caskroom/cask
==> Tapping caskroom/cask
Cloning into '/opt/boxen/homebrew/Library/Taps/caskroom/homebrew-cask'...
remote: Counting objects: 3452, done.
remote: Compressing objects: 100% (3407/3407), done.
remote: Total 3452 (delta 66), reused 250 (delta 23), pack-reused 0
Receiving objects: 100% (3452/3452), 5.88 MiB | 2.27 MiB/s, done.
Resolving deltas: 100% (66/66), done.
Checking connectivity... done.
Tapped 1 formula (3,418 files, 13.3M)
==> Downloading https://www.obdev.at/downloads/littlesnitch/LittleSnitch-3.6.2.dmg
/usr/bin/curl -fLA Homebrew-cask v0.51+ (Ruby 2.0.0-645) https://www.obdev.at/downloads/littlesnitch/LittleSnitch-3.6.2.dmg -C 0 -o /opt/boxen/cache/homebrew/little-snitch-3.6.2.dmg.incomplete
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (22) The requested URL returned error: 404 Not Found
Error: Download failed on Cask 'little-snitch' with message: Download failed: https://www.obdev.at/downloads/littlesnitch/LittleSnitch-3.6.2.dmg
Error: Kernel.exit

Output of brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!

Warning: Python is installed at /Library/Frameworks/Python.framework

Homebrew only supports building against the System-provided Python or a
brewed Python. In particular, Pythons installed to /Library can interfere
with other software installs.

Warning: Your Homebrew is not installed to /usr/local
You can install Homebrew anywhere you want, but some brews may only build
correctly if you install in /usr/local. Sorry!

Output of brew cask doctor
==> OS X Release:
10.11
==> OS X Release with Patchlevel:
10.11.3
==> Hardware Architecture:
intel-64
==> Ruby Version:
2.0.0-p645
==> Ruby Path:
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby
==> Homebrew Version:
Homebrew 0.9.5 (git revision 4b1da8; last commit 2016-01-30)
==> Homebrew Executable Path:
/opt/boxen/homebrew/bin/brew
==> Homebrew Cellar Path:
/opt/boxen/homebrew/Cellar
==> Homebrew Repository Path:
/opt/boxen/homebrew
==> Homebrew Origin:
https://github.com/Homebrew/homebrew
==> Homebrew-cask Version:
0.60.0 (git revision 8f7b; last commit 2 hours ago)
==> Homebrew-cask Install Location:
<NONE>
==> Homebrew-cask Staging Location:
/opt/homebrew-cask/Caskroom
==> Homebrew-cask Cached Downloads:
/opt/boxen/cache/homebrew
/opt/boxen/cache/homebrew/Casks
14 files, 545.2M (warning: run "brew cask cleanup")
==> Homebrew-cask Default Tap Path:
/opt/boxen/homebrew/Library/Taps/caskroom/homebrew-cask
==> Homebrew-cask Alternate Cask Taps:
/opt/boxen/homebrew/Library/Taps/caskroom/homebrew-versions
==> Homebrew-cask Default Tap Cask Count:
2958
==> Contents of $LOAD_PATH:
/opt/boxen/homebrew/Library/Taps/caskroom/homebrew-cask/lib
/opt/boxen/homebrew/Library/Homebrew
/Library/Ruby/Site/2.0.0
/Library/Ruby/Site/2.0.0/x86_64-darwin15
/Library/Ruby/Site/2.0.0/universal-darwin15
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/x86_64-darwin15
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/universal-darwin15
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/x86_64-darwin15
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/universal-darwin15
==> Contents of $RUBYLIB Environment Variable:
<NONE>
==> Contents of $RUBYOPT Environment Variable:
<NONE>
==> Contents of $RUBYPATH Environment Variable:
<NONE>
==> Contents of $RBENV_VERSION Environment Variable:
<NONE>
==> Contents of $CHRUBY_VERSION Environment Variable:
<NONE>
==> Contents of $GEM_HOME Environment Variable:
<NONE>
==> Contents of $GEM_PATH Environment Variable:
<NONE>
==> Contents of $BUNDLE_PATH Environment Variable:
<NONE>
==> Contents of $PATH Environment Variable:
PATH="bin:/opt/boxen/rbenv/shims:/opt/boxen/rbenv/bin:/opt/boxen/ruby-build/bin:/opt/boxen/nodenv/shims:/opt/boxen/nodenv/bin:/opt/boxen/node-build/bin:/opt/boxen/homebrew/bin:/opt/boxen/homebrew/sbin:/opt/boxen/bin:/opt/boxen/rbenv/shims:/opt/boxen/rbenv/bin:/opt/boxen/rbenv/plugins/ruby-build/bin:/opt/boxen/homebrew/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/boxen/homebrew/Library/Taps/boxen/homebrew-brews/cmd:/opt/boxen/homebrew/Library/Taps/caskroom/homebrew-cask/cmd:/opt/boxen/homebrew/Library/ENV/scm"
==> Contents of $SHELL Environment Variable:
SHELL="/opt/boxen/homebrew/bin/zsh"
==> Contents of Locale Environment Variables:
LANG="en_US.UTF-8"
LC_CTYPE="en_US.UTF-8"
==> Running As Privileged User:
No

Thank you for the report. Will be fixed in https://github.com/caskroom/homebrew-cask/pull/17893.


chore: Oracle: add JUnit TCs

Description

Add JUnit TCs

Please note that more test cases could be added here, however, in the interest of time, I would request that we move forward with the coverage that we have with this PR. I am fairly confident that the test cases introduced here cover all the important code flows and should cover more than 80% of the use cases.

Minor improvement to reading of data types: timestamp, raw, blob

Fixes #20535
Type of change

Chore (housekeeping or task changes that don't impact user perception)

How Has This Been Tested?

Manual
JUnit TC

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

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

QA activity:

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

/ok-to-test

/build-deploy-preview skip-tests=true

/ok-to-test

/build-deploy-preview skip-tests=true

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test


Local Manifest

Create a manifest file of media asset urls instead of downloading the manifest. Inspired by @glouel https://github.com/JohnCoates/Aerial/issues/463#issuecomment-424744678 and https://github.com/JohnCoates/Aerial/issues/494#issuecomment-425480512
The goal would be to reconcile all available 1080p and 4k assets into a single manifest so that we don't need to lose out on videos which are no longer available in newer manifest urls.

Just to clarify, I think we should pull each JSON exactly once (or use already downloaded file, which will give us offline mode). Maybe put them in a subfolder for each "json" (there are 3 that we know of tvOS12, 11, 10)
In case of the tvOS12 .tar file we are using right now, inside there's also a bundle of localized strings. On tvOS 12, those includes extra descriptions as the video progresses forward, those are linked to timestamps/keys in the JSON.
So having those is pretty important too as we can use them to display those descriptions.

@glouel what's the specific advantage of downloading the content vs. just creating our own list and storing it in the repo? It seems easier and less fragile to just create our own manifest than to rely on merging multiple downloads (which might disappear at any time).

Considering the JSON is what is used by tvOS, I'm not convinced it's more fragile. Should Apple deprecate old version of tvOS, they'll probably pull the plug on the videos and JSON.
But it's just a LOT of contents with the bundle strings included in the tar. If you can, check the TVIdleScreenStrings.bundle file (1.4 MB).
I'm also not convinced that bundling that file with the project is a good idea in terms of copyright (it's definitely a step further than including URLs as we currently do).

Agreed on all this.
Here's how I see it :

Fix AerialVideo to allow having videos that aren't available in every format
At first startup, pull each json, save locally (and we can try loading that instead of pulling first to get offline mode)
Also provide our extra info (based on id, we add data for space/land day/night etc)
We then can reconcile everything in a local manifest that will then be used from now on

I think in order to get that to work, we can make the list much larger and put icons on the right side showing day/night etc, and maybe if available in 4K, etc.
One other change that will be needed in that merged list, the ability to play "best available format". Let's say I have 4K HEVC as a setting, but I want to add an old 1080p video, we should then play that.

@esetnik I made a small patch to stop redownloading the tar file at every opportunity, following our discussion. I think it's a good first step towards better manifest loading but there's a lot to be improved.

Closing as fixed in release 1.4


Added login service

Added a login service - #8

This change is

I had to do a bit of merging to fit it in with the latest but it looks like it is fine.


Move toTableResponse() off the TableSchemaObject

We should not be creating the response here, this should be part of the operation

had been refactored out


Test cases

In order to make implementations easier to verify, we should provide, along with the specification, a serie of test cases with the expected result.
To test a token, we will need:

its serialized version (if we store the test cases as text, the base64 encoded version)
root public key
verifier facts (if any)
verifier queries (if any)
result:

if failed: error code(s) and message(s) (we should probably specify the errors returned by the verifier)

text explanation of the issue

Here's a temporary list of test cases we should provide:

format and signature errors:

a serie of random bytes: parse error
a correctly serialized structure with invalid crypto (wrong size): parse error
a correctly serialized structure with invalid crypto (right size, random bytes): signature verification error
a correctly serialized structure with valid crypto, but wrong root key: signature verification error
correctly serialized, valid crypto and root, random bytes in blocks: parse error
correctly serialized, valid crypto and root, valid blocks but wrong order: parse error

correct format and signature, logic language serialization errors:

how to test invalid symbol table? symbols not present in the table, or blocks refer to symbols defined by later blocks, symbols redefined by later blocks
authority block has fact without authority tag: validation error
ambient facts without ambient tag: validation error
block facts with authority or ambient tag: validation error
authority or ambient blocks contain variable type: validation error
block at index 0 is not the authority block: validation error

caveat verification:

block 1 defines fact X, block 2 has a caveat requiring fact X: validation error (the fact X should only be valid when evaluating block 1)
?

most of those test case ideas are now generated by https://github.com/CleverCloud/biscuit-rust/blob/master/examples/testcases.rs
Some of them are already tested by the Java version


Serve all CSS assets and fonts locally

Keeps the application self-contained.

Coverage remained the same at 98.115% when pulling 88c80cd4d5f8124af592faa3522d9a56a8299e62 on local-assets into 19ef75d5cefda512bcc9e4c8fc57701559fcc335 on master.


feat(tag): Workspace variable resolution

Pull Request
🤨 Rationale
https://ni.visualstudio.com/DevCentral/_workitems/edit/2527392
👩💻 Implementation
Prepend dashboard variables to list of workspaces and attempt to resolve variables populated in the workspace field prior to querying.
🧪 Testing

Validated functionality locally
Add new test and existing tests continue to pass

✅ Checklist

[X] This PR has a title that follows the commit message format.

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

v3.5.0
GitHub release

Your semantic-release bot :package::rocket:


Fixed project to work xcode 6.3

Fixed to use the xcode version 6.3
It has been fixed syntax differences and added some codes more

nice didn't have the time to update it. thx :-)


teleport should be reactive

What problem does this feature solve?
One of the main features of Vue is to control, what components are displayed.
Teleport however requires that an element is mounted before the teleport tag is mounted.
If for some reason the teleport target is removed but mounted again, the teleport does not work.
What I want is:
If teleport is enabled (:disable="false"), then look for the element to be teleported to.
return error or warning if not found.
teleport if found.
This feature would make teleport a lot more easy to use, because it fits better into an Vue environment where everything is reactive.
As for a use-case:
I currently want to teleport an input-field to a sidebar (https://www.primefaces.org/primevue/sidebar) that is displayed on small displays. The sidebar is displayed when I click on the inputfield. Even if I make sure that the teleport is enabled after (up to 10sec) the sidebar is displayed, the teleport fails silently.
What does the proposed API look like?
If teleport is enabled (:disable="false"), then look for the element to be teleported to.
return error or warning if not found.
teleport if found.

You should be able to use a key to force the recreation of the teleport

It has a wierd workaround, that I found seconds before giving up:
    <Sidebar v-model:visible="showMobile" position="top">

    </Sidebar>
    <teleport
      v-if="ready"
      to="#mobileTarget"
      :disabled="disableTeleport"
    >
    ....
    @focus="switchToMobile"
    ....
</teleport>

 data() {
    return {
      showMobile: true,            //Initially the teleporttarget is present
      ready: false,                     // Initially teleport is not created.
      disableTeleport: true,
    };
  },
mounted() {
    this.ready = true;                 //Delays the mount, therefore teleport will not throw an error, because teleporttarget is still present
    this.showMobile = false;     //removes teleporttarget, so its not displayed
  },
methods:{
allowTeleportToMobile(): boolean {
      return this.breakpoint === "xs" || this.breakpoint === "sm";
      },
 switchToMobile() {
      if (this.allowTeleportToMobile && !this.showMobile) {
        this.showMobile = true;              // first make the teleporttarget available
        this.ready = false;                       // remove the teleport
        setTimeout(() => {                      //wait a little (it doesn't work without setTimeout
          this.disableTeleport = false;     //enable the teleport
          this.ready = true;                     // render it ==> now it teleports properly.
        }, 1);
      }
    },
}

But its a very verbose and ugly workaround if you ask me.
The teleport should check for the existence of the target, when activated. I would even propose that the target can be a vue component it self, but it would certainly help if that mounted requirement is gone.
Don't know what exactly you were proposing with the key. I only know it from lists (v-for), which isn't my current use-case.

@telion2  the work around with key would be adding the :key attribute to the component (or teleport, not sure exactly which is most appropriate @posva). If you change the key, vue will see this and force a re-render.
Its not a feature that has to be exclusively used with v-for or iteration over data. It can be used in any situation.

Have a very similar usecase — using portal-vue to make it work — but would be nice if Teleport supported these scenarios.


pylint clean

Tidying up some linting issues while learning the project.

Thanks for making those fixes, just waiting for CI to pass and then we can get these changes merged in.


ci: specify semrel branches

Summary of change
Add missing branches values in array in releaserc
Related issue
#12

:tada: This PR is included in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add integration test for file name normalization

This test ensures the client does not perform file name normalization. But it looks like the current ruby client (google-api-client?) does that. So the test fails.

@swcloud This PR looks to be the opposite of #1097, which attempts to show that the upload should match regardless of unicode normalization. @sqrrrl says that an internal GCS bug has been created for the file name normalization. Is that bug still open? What can you tell us about this?

@swcloud I doubt that google-api-client will remove its dependency on the addressable gem, which implements the RFC 6570 URI Template spec faithfully. So the only way to accept this PR is to remove the dependency on google-api-client, similar to how we have done that for google-cloud-translate. Is that what you are asking with this PR?

For more about the gems and the spec, see this comment.

The internal bug is still open. The service side fix is tricky. Currently
we want to make sure the client does not do normalization.
On Mon, Mar 27, 2017, 8:55 AM Mike Moore<EMAIL_ADDRESS>wrote:

@swcloud https://github.com/swcloud This PR looks to be the opposite of
#1097 https://github.com/GoogleCloudPlatform/google-cloud-ruby/pull/1097,
which attempts to show that the upload should match regardless of unicode
normalization. @sqrrrl https://github.com/sqrrrl says that an internal
GCS bug has been created for the file name normalization. Is that bug still
open? What can you tell us about this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-ruby/pull/1364#issuecomment-289497699,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT0hCacaxt26deQevsUSVUl8IMmAH404ks5rp9vjgaJpZM4MqdWY
.

My understanding is that different API had their different way to define
resource name semantics either byte semantics or text semantics, GCS is
byte semantics, so there should not be any normalization.
On Mon, Mar 27, 2017, 9:20 AM Song Wang<EMAIL_ADDRESS>wrote:
The internal bug is still open. The service side fix is tricky. Currently
we want to make sure the client does not do normalization.
On Mon, Mar 27, 2017, 8:55 AM Mike Moore<EMAIL_ADDRESS>wrote:
@swcloud https://github.com/swcloud This PR looks to be the opposite of
#1097 https://github.com/GoogleCloudPlatform/google-cloud-ruby/pull/1097,
which attempts to show that the upload should match regardless of unicode
normalization. @sqrrrl https://github.com/sqrrrl says that an internal
GCS bug has been created for the file name normalization. Is that bug still
open? What can you tell us about this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-ruby/pull/1364#issuecomment-289497699,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT0hCacaxt26deQevsUSVUl8IMmAH404ks5rp9vjgaJpZM4MqdWY
.

@swcloud Would you prefer we push a fix to google-api-client or would you prefer we remove google-api-client?

Sounds like you already have code to replace google-api-client
functionality? I would prefer to remove google-api-client to be consistent
with Translation.
On Mon, Mar 27, 2017, 10:02 AM Mike Moore<EMAIL_ADDRESS>wrote:

@swcloud https://github.com/swcloud Would you prefer we push a fix to
google-api-client or would you prefer we remove google-api-client?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-ruby/pull/1364#issuecomment-289517182,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT0hCawexuw-sLT_awXn2c9zCJtXcFmWks5rp-uxgaJpZM4MqdWY
.

Sounds like you already have code to replace google-api-client functionality?

Not really.

I would prefer to remove google-api-client to be consistent with Translation.

Translation is a very simple library using a single API call with HTTP GET, so it was much easier to replace. Storage has dozens of API calls, both downloading and uploading files. This will be a significant effort to implement and verify this change.

I see. What about another option? Maybe you can add a configable parameter
to enable/disable normalization?
On Mon, Mar 27, 2017, 10:19 AM Mike Moore<EMAIL_ADDRESS>wrote:

Sounds like you already have code to replace google-api-client
functionality?
Not really.
I would prefer to remove google-api-client to be consistent with
Translation.
Translation is a very simple library using a single API call with HTTP
GET, so it was much easier to replace. Storage has dozens of API calls,
both downloading and uploading files. This will be a significant effort to
implement and verify this change.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-ruby/pull/1364#issuecomment-289521977,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT0hCWXETo2MrdHbMYE0Dwsey2X3FJP7ks5rp--fgaJpZM4MqdWY
.

I see. What about another option? Maybe you can add a configable parameter to enable/disable normalization?

I've been looking into that as well. By reading the closed issues for the addressable gem, I doubt that any configuration to change the normalization behavior will be accepted. I see the following options:

Fork the addressable gem, add configuration to control normalization behavior, make google-api-client switch to use this newly forked gem.
Fork the relevant parts of the google-api-client gem, replace the dependency on addressable, switch google-cloud-storage to use this newly forked gem.
Move google-cloud-storage off of google-api-client in the manner of google-cloud-translate.

The least complicated option seems to be option 3. If byte semantics for GCS API calls is a hard requirement, and we cannot wait for GCS to support text semantics, then I think option 3 is the way to go. Since all changes would be under our control this would also be the quickest to complete.
But that doesn't mean this is an easy or quick change.

Agreed with option 3. Do you have ETA?
On Mon, Mar 27, 2017, 11:09 AM Mike Moore<EMAIL_ADDRESS>wrote:

I see. What about another option? Maybe you can add a configable parameter
to enable/disable normalization?
I've been looking into that as well. By reading the closed issues for the
addressable gem, I doubt that any configuration to change the
normalization behavior will be accepted. I see the following options:

Fork the addressable gem, add configuration to control
normalization behavior, make google-api-client switch to use this
newly forked gem.
Fork the relevant parts of the google-api-client gem, replace the
dependency on addressable, switch google-cloud-storage to use this
newly forked gem.
Move google-cloud-storage off of google-api-client in the manner of
google-cloud-translate.

The least complicated option seems to be option 3. If byte semantics
for GCS API calls is a hard requirement, and we cannot wait for GCS to
support text semantics, then I think option 3 is the way to go. Since all
changes would be under our control this would also be the quickest to
complete.
But that doesn't mean this is an easy or quick change.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-ruby/pull/1364#issuecomment-289536675,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT0hCYIifP0vTt50HpXZgmBYcckTGrYrks5rp_t1gaJpZM4MqdWY
.

Do you have ETA?

Maybe the end of the week? Depending on other priorities?

FWIW, I'm working on submitting a PR for addressable to make unicode normalization optional. Should have that done shortly.

@sqrrrl Wonderful news!
@swcloud Does this change our plans? We unfortunately don't have control over if the change is accepted, and when it would be released.

I am fully onboard w/ unicode normalization being optional for URI templates. The default should be whatever the RFC says, however, on principle, I don't like library code that thinks it knows better than the developer just because the "RFC said so".
That said, while the RFC didn't say you MUST normalize, it does say you SHOULD normalize. Anybody that's trying to push raw bytes in a URI should probably seriously consider url-safe base64 encoding as a first pass for representing raw byte data that's not subject to the vagaries of unicode, NFKC, and percent-encoding. That goes double for URI templates, where the data is guaranteed to be messed with by any conformant processor. Even after Addressable makes it possible to disable normalization, it seems to me that you're still firmly in "this is unwise" territory here. I would recommend deprecating raw bytes as values expanded within URI templates and suggest phasing them out entirely. It's simply a bad idea and you shouldn't be doing it.

As for release schedule, adding an extra parameter shouldn't be a breaking change, so it can be a patch release. All the commits between now and the last release have been changes to the tests, so there's no obstacle to releasing immediately after merge.

2.5.1 released. You should be all set to update dependency and use the new option. My commentary above still applies but at least you have better options now.

Thanks Bob. FWIW, agree with the general sentiment -- not great that resource names are sensitive here.
I'll update google-api-client in the next day or two. Version will be bumped to 0.11.0

@sqrrrl How long do you think it will take to see a release that makes use of addressable 2.5.1?

Aiming for end of week, earlier if I can. There are some other changes that need to be dusted off and merged in, but shouldn't take too long to do.

Man, I missed your earlier comment again. That all sounds great. Please let me know how I can help. My email is<EMAIL_ADDRESS>

@sqrrrl @sporkmonger Thanks a lot for pushing the changes in Addressable so quickly! @blowmage  Yes, it makes sense to change the plan and stick with the google-api-client once @sqrrrl released a new version. This path is less risky.

@blowmage @swcloud -- ruby client 0.11 just pushed, please give it a try. LMK if you run in to any issues.


varargs for tab -w

This might be a bit difficult, as the autocomplete scripts would need to support the vararg.

Fish doesn't even support `-w foo bar baz' completions.  This was easy to implement with Clap, but fish and zsh do not support dynamic vararg completions (which honestly makes sense).  Not even with '-w foo -w bar'.

Closing, released in v0.4.0!


Exclude not working for apostrofs

w = "L’Unesco a perdu tout crédit et Donald Trump en tire les conséquences"
tokeniser = WordsCounted::Tokeniser.new(w).tokenise(exclude: "’")
[     [ 0] "l",     [ 1] "unesco",     [ 2] "a",     [ 3] "perdu",     [ 4] "tout",     [ 5] "crédit",     [ 6] "et",     [ 7] "donald",     [ 8] "trump",     [ 9] "en",     [10] "tire",     [11] "les",     [12] "conséquences"

@drummerroma interesting. Are you sure it's the same character in the text and exclude clause?

I used cut and paste in the rails console. So I am sure.
I have a french (or italian) text pasted from Word (or any other processor) and would like to have treated apostrofated frases counted as songle token. Example:
l'appartamento
l'Unesco
l’abandon
Maybe there is a difference between "'" and "’"?

@drummerroma yes, there is. These are different characters. The apostrophe,  code is ’, while the single quote is '. The trouble is, many people don't use the right chars. For example, they use double quotes " instead “ and ”, the proper quoting chars. For this type of use case, I would exclude both because you can never be certain what the originally typed text contains, or whether it was transformed by an editor.

Yes, I agree. But the exclude instruction should work anyway.

I just confirmed that this doesn't exclude the apostrophe but does exclude the single quote. Strange. I'll have to investigate why.


Fix library path bugs following tests

Better handling of the install destination for Python, and adds the path of the python library to the rpath of pyncpp.

I'm merging this but it doesn't work on Windows yet. We are fixing that on a different branch.


Writing an h5 results in seg-fault if annotations are present on morphology

Example (swc works but annotations are not written to file, h5 throws seg-fault error)
import morphio
m = morphio.mut.Morphology()
m.annotations.append('{"Apical point": (0, 1, 0)}')

m.write('Test annot.swc')
Warning: writing file without a soma

m.write('Test annot.h5')
Warning: writing file without a soma
Segmentation fault

Annotations are not designed to be writable, it's a read-only object.
They just contain details about what happened when the files was opened (like single children, duplicates...).
And the segfault comes from the fact you are trying to write an empty morphology.

And the segfault comes from the fact you are trying to write an empty morphology.

IMHO the library should not punish the user with a segfault.

IMHO the library should not punish the user with a segfault.
Yep. This has been fixed.


[FEATURE] Run jupyter doc notebooks in headless mode to notice outdatedness

Is your feature request related to a problem
When we push updates to the dataquality client's interface we may forget that downstream our docs and notebooks will break. At least in this repo we have a notebook or two that should be kept updated with the code syntax so we have some source of truth on client usage.
The solution you would like
Run the jupyter notebook in a headless mode to check it still is able to successfully complete. We could also add maybe some assertions to the bottom to actually turn it into a real test

we do this for our colab notebooks now


Cannot use interface to declare emits

Vue version
3.3.4
Link to minimal reproduction
https://github.com/vuejs/language-tools/issues/3223
Steps to reproduce
See the example
What is expected?
No type errors
What is actually happening?
Type errors
System Info
No response
Any additional comments?
Well that's a typescript limitation: microsoft/TypeScript#42825 but I think we can avoid it.

Same issue here

Ugh. After some thoughts, I think the error is correct, see the example:
interface Emits {
  foo: []
}
interface Emits {
  bar: 1 // !!!!
}


support HTTP Bearer authentication (fix #324)

This adds support for Bearer type authorization header. Incorporated suggestions by @catenacyber at https://github.com/OISF/libhtp/pull/325#pullrequestreview-620194346:

defined HTP_AUTH_BEARER constant,
added test file and TEST_F(ConnectionParsing, AuthBearer) using example from RFC6750.

Fixes #324.

Do you want this for Suricata or for another use case ?

Do you want this for Suricata or for another use case ?

For Suricata

Ok thanks.
Could you create a redmine ticket for this ?
https://redmine.openinfosecfoundation.org
And could you create a Suricata-verify test to check that this libhtp change brings the wanted behavior in Suricata ?

Friendly ping @kevinreddot do you plan to work further on this ?

Replaced by https://github.com/OISF/libhtp/pull/393


oci_database_db_system version is null

Describe the bug
A query from oci_database_db_system on columns version returns null:
steampipe query "select
display_name,
database_edition,
version
from
oci_database_db_system;"
+--------------------+--------------------+---------+
| display_name       | database_edition   | version |
+--------------------+--------------------+---------+
| dbsys-ivz-db-01    | ENTERPRISE_EDITION |   |
| just-4-calculation | STANDARD_EDITION   |   |
| DBSystem-PAGDB     | STANDARD_EDITION   |   |
+--------------------+--------------------+---------+
Steampipe version (steampipe -v)
steampipe version 0.7.1
Plugin version (steampipe plugin list)
+--------------------------------------------+---------+---------------------------+
| Name                                       | Version | Connections               |
+--------------------------------------------+---------+---------------------------+
| hub.steampipe.io/plugins/turbot/oci@latest | 0.2.0   | oci_tenant_xxxxxxxx     |
+--------------------------------------------+---------+---------------------------+
To reproduce
Just do a query.
Expected behavior
Version from db-home should be shown - example command in OCI CLI where ORACLE_HOME version is shown:
oci db db-home list --compartment-id $COMPARTMENT_ID
{
"data": [
{
"compartment-id": "ocid1.compartment.oc1..aaaaaaaaaql7z6vtbjjjz24lnyxxxf2xxxxxxxxx",
"database-software-image-id": null,
"db-home-location": null,
"db-system-id": "ocid1.dbsystem.oc1.eu-zurich-1.ab5heljriwkcxaxdahcelyjdugsgibwmhxxxxxxxxxx",
"db-version": "<IP_ADDRESS>.0",
"defined-tags": null,
"display-name": "dbhome20210607111507",
"freeform-tags": null,
"id": "ocid1.dbhome.oc1.eu-zurich-1.ab5heljrtgh5x4fjji75eialxcxe3bu7xwdtxxxxxxx",
"last-patch-history-entry-id": null,
"lifecycle-details": null,
"lifecycle-state": "AVAILABLE",
"one-off-patches": null,
"time-created": "2021-06-07T11:15:07.191000+00:00",
"vm-cluster-id": null
}
]
}
Additional context
Please add version here.

@martinberger-ch thanks for the continuous feedback, the API call for oci_database_db_system contains the version as an attribute, and it's returning null. We have the db_version column in oci_database_db_home table, which renders the outcome. We will investigate further and raise this OCI team as well before taking any customization.
`

@rajlearner17 Have you received any updates from the OCI team yet?

@cbruno10 the raised issue 3-26892148051 [CLI returns "version": null, in oci db system list,] got closed with a few rounds of conversation and experiment, we were supposed to provide more details, and it was consuming time. The behaviour remains the same in CLI. We have to re-open the case and experiment further. However oci_database_db_home renders expected data. I suggest we close and wait further for any usage & ask for it in future.

We will track the OCI SR and take action in future.


[BUG]: WASM/Rust layer panics and cannot catch it.

Describe the bug
When you have a large import/export file the WASM runtime can panic due to some internal issue happening in rust. This will brick the TS workflow because the promise never returns and the logic of the system will not cleanup properly.
This prevents you from executing future KCL files so you cannot switch files or rerun your code.
Steps to Reproduce

Make a massive file to export
Import it into a main.kcl file
Wait for the WASM runtime to brick

Expected Behavior
We should be able to gracefully recover from a crashed WASM/Rust run of the AST.
this.isExecuting and some other cleanup calls need to be invoked to properly restore the TS state in the application after the promise for executeAST dies.
Screenshots and Recordings

Desktop OS
Linux
Browser
No response
Version
v0.34.0
Additional Context
It has at least been a bug since v0.30.0
https://github.com/rustwasm/wasm-bindgen/issues/2392
We will be using window.addEventListener('error', (event) => { ... }) to catch a global error since we cannot try catch the error from the executeAST promise it completely dies in that context.
We will need a global error handler that can map some of those runtime errors across the entire application state. It isn't amazing but after pairing with a few devs this is the only thing we could find. When rust panics we cannot catch that error in TS.
Sample error that is being caught with the global handler

Yes it is the same one in that post above.


Docs: Put back the 'Set Up and Run a Cluster Node' page, for now

I had removed this page but I realized it's probably a good idea to keep it around for now. It can be removed in the future, once the new section on production node setup & management is more complete.

Current coverage is 92.27% (diff: 100%)

Merging #582 into master will not change coverage

@@             master       #582   diff @@
==========================================
  Files            22         22
  Lines          1178       1178
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1087       1087
  Misses           91         91
  Partials          0          0

Powered by Codecov. Last update 1797960...20964fd

:+1:


[$500]  Workspace - After BA has been added on OD, it does not appear on ND

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

Version Number: 1.4.28-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Pre-requisite: user must have created a collect workspace and have created a request from an employee account

As the admin on OD, go to workspace setting and click on "Reimbursements"
Click on Direct
Add a fully verified VBA
As the admin on ND, navigate to workspace chat with an employee that have submitted a request
Click on "Pay with Expensify" button

Expected Result:
The user should be able to pay the request if the BA was added on OD
Actual Result:
The add BA modal opens
Workaround:
Unknown
Platforms:

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

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

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/fbdae518-42ac-47a9-9879-2b3535c7fb89
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0151fb7e11e7787a66
Upwork Job ID:<PHONE_NUMBER>983385600
Last Price Increase: 2024-01-20

We think that this bug might be related to #wave8.
CC @zanyrenney

Hm, @luacmartins @mountiny @JmillsExpensify I can't find the issue, but is this related to how VBBAs were implemented on NewDot and are awaiting a refactor?

Yes, we're likely not setting the expensify_freePlanBankAccountID NVP. This is the issue to fix it.

I think we should make that issue higher priority just to clear this debt out of the way

Okay, so we don't need this dupe issue, so I'll close it. Vit, that's probably better discussed over there!


Add support for 'Bose QC35 II'

My Bose QC35 II have a different ProductId to the ID hardcoded in this App, so this tool isn't compatible.
This PR will add support for this additional ProductID & appears to work locally.
(This app is awesome by the way, thank you)

Nice one, thanks for the contribution! Glad to see this being useful to someone besides myself, might motivate me to fix some of the bugs lol


Grouping commuting Pauli strings in quantum_info

Summary
This PR is the first step in implementing #6624. This implements grouping commuting Pauli strings in quantum_info. The second step, which will be addressed in another PR, is to rewrite the abelian-grouping code in opflow to call the code in the present PR.
Details and comments
Here is an example of the function created:

from qiskit.quantum_info import PauliList,Pauli
pauli_list=PauliList([Pauli("II"),Pauli("IX"), Pauli("IY"), Pauli("XX"),Pauli("YY"),Pauli("YX")])

pauli_list.group_subops_pauli_list()
#returns [PauliList(['YX']), PauliList(['XX', 'IX']), PauliList(['IY', 'II', 'YY'])]

Can you add 1) tests and 2) a release note?


network: refactor some network functionality

Related-to https://github.com/system-transparency/stboot/issues/66
Signed-off-by: Morten Linderud<EMAIL_ADDRESS>

Yes, that's ok for now, since I'd like to get your opinion on error handling / wrapping / sterror pkg.

The stlog error handling is a tiny bit weird. I'm not super sure when you want to make a new error, forward them or not :upside_down_face: I settled on a hybrid for this.

@Foxboron, is this still relevant?

Partially, but it can be deferred until later I think. It's not a complicated change.

I see, "relevant" was not the right term. It's not urgent, right?
I'll take that into account while refactoring once we are on GitLab.

Not urgent at all. It was me looking around the stboot code the first month :)

https://git.glasklar.is/system-transparency/core/stboot/-/tree/main/


Dynamic type

change all the text in the variable modals to be dynamic type.
Also, just check over the entire storyboard to make sure all text is dynamic type

I changed all the variable modals to use dynamic type and checked over the other modal screens to make sure they have it. I ended up having to change the format of the look left/right and up/down modal screens because there were too many characters to fit on one line when it was on the same line as the back button.


eddi temp sensors as long-term statistics

I have been able to use the two eddi temp sensor entities with HA Sensor cards but it doesn't seem to be possible to select the entities when configuring an HA Statistics Graph card.
In the HA configuration UI for the Statistics Graph card (screenshot below) it suggests referring the author of the integration to this page: https://developers.home-assistant.io/docs/core/entity/sensor/#long-term-statistics
As you can hopefully see from the screenshot, I am offered other temperature unit entities when configuring the card.
Apologies if I have misunderstood how this all works and it's due to me not configuring something in my Home Assistance instance for the two entities you have already included.


Download Sources

Is your feature request related to a problem? Please describe.
I might be missing something, but I can't find a way to download sources of dependencies. A feature I've used a lot in other IDEs
Describe the solution you'd like
Have the ability to globally enable the downloading of sources for all dependencies.
Describe alternatives you've considered
Not found any practice work-arounds.
Additional context

could you paste your output log in "Gradle for Java" channel? is your PC using proxy?

This is a must have feature.
When jump into method in dependency jar. vscode-gradle just decompile the class file to show the source code. No document present in the decompiled source code which is very inconvenient.
In IDEA, it will show a button to promopt to download source jars and jump into source file. This is a great feature

Or at least make 'Attach Sources...' work when using Gradle.

Hi @jdneo, I was wondering is the amount of work for this enhancemnet somewhat reasonable and in scope for this project? If that is the case, could you give me some hints where to start?

@mamilic could you reproduce this issue?

@jdneo , it seems that I can not. As I can tell, at least on my PC it downloads the sources always. Is that default behavior?

@mamilic It's a little complex to explain. I'll try to explain it clear.
So for the gradle project we have two importer, gradle build serverand buildship:
// If project is imported by gradle build server, the container name is displayed as Referenced Libraries
// If project is imported by buildship, the container name is displayed as Project and External Dependencies
The source jars are always downloaded by gradle build server, in this case, users do not need to do anything and will see the sources.
If it's buildship, It's lazy-load approach. Which means, when user opens a class file and the source jar is not downloaded locally, a download task will be kicked. Once it's downloaded, next time user opens that file, he should be able to see the sources.

I tend to close this issue right now. But if anyone finds that my understanding is incorrect, please leave comment here.


Automated smoke test data migration test fails on Linux

#27456
OS: Linux
Command: npm test -- --latest /usr/share/code-insiders/bin/code-insiders --stable /usr/share/code/bin/code
  Smoke Test Suite

    Data Migration

      ✓ checks if the Untitled file is restored migrating from stable to latest (25176ms)

      1) checks if the newly created dirty file is restored migrating from stable to latest

...

  1) Smoke Test Suite Data Migration checks if the newly created dirty file is restored migrating from stable to latest:
     Error: unknown error: Element
...
 is not clickable at point (314, 17). Other element would receive the click: This workspace has extension recommendations.

Removing 'bug', I don't think a test failure needs verification.

@roblourens This test failure was caused due to missing implementation in smoke test to tackle the problem @Tyriar faced, not because it failed due to a bug in VS Code. It would be still great to verify it.

It now passes on the same machine :+1:


Route Diagram on Wildfly 8.2.0 throws RuntimeErrorException because of dumpRoutesAsXml

I was sent here to ask for help from this issue:
https://github.com/hawtio/hawtio/issues/1915
I doubt this is the right place for me to ask for help, since I do not use wildfly-camel but instead use:
        <dependency>
            <groupId>io.astefanutti.camel.cdi</groupId> (I read it is being actively integrated into apache camel since december to replace the existing camel-cdi)
            <artifactId>camel-cdi</artifactId>
            <version>1.1.0</version>
        </dependency>
        <dependency>
            <groupId>org.apache.camel</groupId>
            <artifactId>camel-sjms</artifactId>
            <version>2.14.1</version>
        </dependency>
        <dependency>
            <groupId>org.apache.camel</groupId>
            <artifactId>camel-mongodb</artifactId>
            <version>2.14.1</version>
            <exclusions>
                <exclusion>
                    <artifactId>mongo-java-driver</artifactId>
                    <groupId>org.mongodb</groupId>
                </exclusion>
            </exclusions>
        </dependency>
        <dependency>
            <groupId>org.apache.camel</groupId>
            <artifactId>camel-core</artifactId>
            <version>2.14.1</version>
            <exclusions>
                <exclusion>
                    <artifactId>slf4j-api</artifactId>
                    <groupId>org.slf4j</groupId>
                </exclusion>
            </exclusions>
        </dependency>

and  hawtio-web-1.4.45.war.
But maybe somebody might be so kind to help me, anyway?

Using wildfly-camel instead of trying to provide your own integration layer has many benefits. We gladly help with making this use case work on top of wildfly-camel

@tdiesler I think widlfy has a general problem, what if people deploy .war files with a camel-core app. Then I suspect wildfly has that same problem reported here. That invoking dump routes as xml operation on the camel context mbean over JMX will fail. You can verify by just installing any camel .war app in widlfly, and connect using jconsole, and invoke that mbean operation.

The goal of this project is that wildfly/eap provides camel functionality out of the box. Replacing the provided camel (core) components with something else cannot be supported


Interplay of slicing and flattening

When implementing Numba-based algorithms for process_tile(), both input data and result buffers are often flattened for working in the signal direction since it makes it easier to implement routines independent of the dataset shape. StdDevUDF would be an example.
If the tile or result buffer views are not contiguous, they can't produce a flattened view: https://docs.scipy.org/doc/numpy/reference/generated/numpy.reshape.html
If reshape()is used with an assumption that it creates a view, it can introduce hard-to-find errors that are only triggered if the tile is slicing not only the left-most, but also other dimensions. K2 IS is a prime example of a dataset that slices result buffers this way because of it's native data layout. Assigning to the shape attribute would trigger an AttributeError instead, which isn't a solution as well. Refs #738
Furthermore, this case might be triggered if a partition is memory-mapped, and non-contiguous tiles are sliced out of it. That might include cases where frame headers are masked out with a view. In these cases, reshaping might introduce a hidden copy in the main data flow, which can introduce a significant performance penalty.
Possible components of a solution:

Implement routines with the assumption that reshaping buffers or tiles generates a copy.
Change process_tile() in such a way that both signal and navigation dimension are always flat, and leave it to the back-end to supply efficient buffers.
Change the back-end to always supply buffers and tiles as contiguous memory reshaped into the same signal shape as now, and leave it to the back-end to implement this efficiently. The result buffers could be rearranged to be contiguous between preprocess() and process_tile(), and again before postprocess().
Switch the reading back-end to L3 cache friendly tile sizes if it detects a case where flattening the signal dimension would create a copy of a tile -- possibly together with an UDF flag?
Make sure that the tile shape negotiation gives contiguous tiles if at all possible, for example in raw files.

As a remark, we should make sure that all UDFs are tested against odd datasets and tiling schemes as soon as #706 is merged.

DIscussion with @sk1p : We are favoring a solution where kind="sig" buffers get a cached contiguous copy in case the signal dimension of a slice can't be flattened in or around https://github.com/LiberTEM/LiberTEM/blob/9557ff6ecc384552c757f1becb48e16766270fd0/src/libertem/udf/base.py#L183-L185. The copy can be merged back after the process_tile() loop is finished. Since slices don't overlap and the same slicing scheme is used within a partition, this is manageable.

In summary, we can guarantee from DataSet side that tiles are contiguous, in the worst case by reducing tile size and creating a copy in L3 cache. For kind="sig" buffers, we can create copies and merge them back with acceptable efficiency.

Closing here since mostly resolved in #738:

Transparent mechanism to make result buffer views contiguous
libertem.common.buffers.reshaped_view() as an alternative to numpy.ndarray.reshape()
Test cases for new dataset implementation added as a TODO item in #706


docs(changelog): capture all PRs

Fixes #2602
The changelog tool was missing some PRs in the generation.  Our repo is quite large.  I've dialed back some of the settings to ensure we aren't missing critical PRs due to Github rate limits.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #2659   +/-   ##
=======================================
  Coverage   99.74%   99.74%
=======================================
  Files         160      160
  Lines        2751     2751
=======================================
  Hits         2744     2744
  Misses          7        7

Continue to review full report at Codecov.

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

Released in<EMAIL_ADDRESS>


Error: Can not serialize input for SGX io error: Broken pipe (os error 32)

Describe the bug
@liray-unendlich also faced the same error. We both reinstalled each server.
raiko  | 2024-05-13T07:30:11.256029Z  INFO raiko_host::execution: Verifying final state using provider data ...
raiko  | 2024-05-13T07:30:11.256043Z  INFO raiko_host::execution: Final block hash derived successfully. 0xf00f207b7ccf031bf7ee787f9ae7b856201a0df9b309cd729002229ef6b3ab08
raiko  | 2024-05-13T07:30:11.256045Z  INFO raiko_host::execution: Final block header derived successfully. Header { parent_hash: 0x96aea128aaaa20cdce520f916238b213f51cbd4d0107823fafc73d39e0aa2b1f, ommers_hash: 0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347, beneficiary: 0xc16b9a2dfda0aa8281054feee3270665da2f7662, state_root: 0x10f77c0ddf60494ca09f7f3b23089cfb8461fde38d767dc0fb8b5336a3915fdc, transactions_root: 0xacf0f0d1489a7ad5b83c7350472f1a807fb5b709da5e09459106f5984e06c781, receipts_root: 0xdf28f7f2768c28b553d7e4beca36b7ba067b877c2463595dfb838c3d0e27ff08, withdrawals_root: Some(0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421), logs_bloom: 0x00000000000080010014000000000020000000000018000000800000020000c00000000100040000000040000010004000000080000020000000000000003140000000000000002900000008000000000001000200400000000050020004001000000080060000000040008080000800000000000000140001000010000800400004010102000400000000000000204000000000000000000000000000000400002000000001000000000000004000204000100000001104300000080000000000020002800000000200000000000000000410000000002008040002800020000000000000000020000000000000000004000000000000000000000000400000, difficulty: 0x0_U256, number: 137631, gas_limit: 240250000, gas_used: 726723, timestamp:<PHONE_NUMBER>, mix_hash: 0xc29f37337bcc95e770f6e4edb01125e07cef1ea78bbb0b05fc3971363e74a6f8, nonce: 0, base_fee_per_gas: Some(1), blob_gas_used: None, excess_blob_gas: None, parent_beacon_block_root: None, extra_data: 0x302e31382e302d64657600000000000000000000000000000000000000000000 }
raiko  | kzg check enabled!
raiko  | Guest program peak memory used: 4.235377 MB
raiko  | Generating proof...
raiko  | WARNING: running SGX in hardware mode!
raiko  | Current directory: "/opt/raiko/bin"
raiko  |
raiko  | Error: Can not serialize input for SGX io error: Broken pipe (os error 32), output is Ok(Output { status: ExitStatus(unix_wait_status(25856)), stdout: "Starting one shot mode\nthread 'main' panicked at provers/sgx/guest/src/one_shot.rs:117:10:\ncalled `Result::unwrap()` on an `Err` value: Application was not bootstrapped or has a deprecated bootstrap.\nnote: run with `RUST_BACKTRACE=1` environment variable to display a backtrace\n", stderr: "Gramine is starting. Parsing TOML manifest file, this may take some time...\n-----------------------------------------------------------------------------------------------------------------------\nGramine detected the following insecure configurations:\n\n  - loader.insecure__use_cmdline_argv = true   (forwarding command-line args from untrusted host to the app)\n  - sys.insecure__allow_eventfd = true         (host-based eventfd is enabled)\n  - sgx.allowed_files = [ ... ]                (some files are passed through from untrusted host without verification)\n\nGramine will continue application execution, but this configuration must not be used in production!\n-----------------------------------------------------------------------------------------------------------------------\n\n" })

Steps to reproduce
Steps to reproduce here.
Spam policy

[X] I verify that this issue is NOT SPAM and understand SPAM issues will be closed and reported to GitHub, resulting in ACCOUNT TERMINATION.

Application was not bootstrapped or has a deprecated bootstrap.

That normally means you need to bootstrap & register again, normally because you change config after the 1st init. Please try removing the old secrets/priv.key & do init again.

Thanks. I registered again and the error no longer occurs. Closing.


Fix typo in Mint.WebSocket.new() function doc

Scheme is passed to upgrade/5, not new/5.

Pull Request Test Coverage Report for Build 970178439a38cf5011711ff5d69ff6797907cb6f-PR-28

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

Totals

Change from base Build e76205eefd9227aa9d10a1a808025024f5144a6c:
0.0%

Covered Lines:
313

Relevant Lines:
351

💛  - Coveralls

Thank you!


Add IIPEndPointConnectionFeature

Right now the only way to get IP information is to go through the IHttpConnectionFeature which is a bit unfortunate:
public interface IIPEndPointConnectionFeature
{
    IPEndPoint RemoteEndPoint { get; set; }
    IPEndPoint LocalEndPoint { get; set; }
}

Let's take a quick look since this may be something we want to take a breaking change for (to rename the shared feature)

We fixed this differently with a more generic feature as part of https://github.com/aspnet/AspNetCore/commit/04bf1bf32e13d35d4d7f61f9cbeb9bfa22e0c617

Acceptance checklist (check one item)

[ ] We decided not to take this fix.
[ ] The fix is tests-only.
[x] The fix contains product changes (check all items below).

[ ] Relevant XML documentation comments for new public APIs are present.
[ ] Narrative docs (docs.microsoft.com) are updated. (check one item below)

[ ] The change requires a new article. An issue with an outline has been filed here: [ISSUE LINK]
[ ] The change requires a change to an existing article. A docs PR with these changes is linked here: [PR LINK]
[ ] The change requires no docs changes.

[x] Verification has been completed. (check one item below)

[x] The change is in the shared framework and was verified against the following versions

SDK installer: [VERSION]
ASP.NET Core Runtime: [VERSION]
.NET Core Runtime: [VERSION]

[ ] The change is in an OOB NuGet/NPM/JAR package and was verified against the following version of that package: [PACKAGE ID] [VERSION]


Upgrade to pulumi-terraform-bridge v1.4.3

@mikhailshilkov please approve this - i just need to bump the version of the azure package for the codegen - it's unrelated to this change


ERROR: "msg": "Failed to import the required Python library (pyrfc) on HOST

Summary
I have a Ansible CONTROL Node with:
python version: Python 3.8.10
pyrfc version: 2.7.0
And a ansible "SAP NW" Node with:
OS: SLES 15 SP2
Python 3.6.15
pyrfc: missing
When  try to use the module "community.sap_libs.sap_user" to create a new USER I have the error:
"msg": "Failed to import the required Python library (pyrfc) on myhostname's Python /usr/bin/python3. Please read the module documentation and install it in the appropriate location. If the required library is installed, but Ansible is using the wrong Python interpreter, please consult the documentation on ansible_python_interpreter"
Question1: Do I need to install the pyrfc even on SAP NW host ? (because this is not possible now)
QUestion2: How to correct the error ?
THX
Issue Type
Bug Report
Component Name
sap_user
Ansible Version
$ ansible --version
ansible [core 2.13.1]
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/ubuntu/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/ubuntu/.local/lib/python3.8/site-packages/ansible
  ansible collection location = /home/ubuntu/.ansible/collections:/usr/share/ansible/collections
  executable location = /home/ubuntu/.local/bin/ansible
  python version = 3.8.10 (default, Nov 14 2022, 12:59:47) [GCC 9.4.0]
  jinja version = 3.1.2
  libyaml = True

community.sap_libs Version
$ ansible-galaxy collection list community.sap_libs
Collection         Version
------------------ -------
community.sap_libs 1.1.0

# /home/ubuntu/.ansible/collections/ansible_collections
Collection         Version
------------------ -------
community.sap_libs 1.4.0

Configuration
$ ansible-config dump --only-changed
DEFAULT_HOST_LIST(/etc/ansible/ansible.cfg) = ['/etc/ansible/hosts']
INTERPRETER_PYTHON(/etc/ansible/ansible.cfg) = auto

OS / Environment
Source OS (Ansible Control Node): Ubuntu 20.04.5 LTS
Target OS (SAP NW): SLES 15 SP2
Steps to Reproduce

---
  - name: SAP_USER
    hosts: SAP_S4HANA
    tasks:
        - name: Create SAP User
          community.sap_libs.sap_user:
            conn_username: 'ADMIN'
            conn_password: 'MyAdminPSWD'
            host: myhostname
            sysnr: '00'
            client: '200'
            state: present
            username: ANSIBLE
            firstname: first_admin
            lastname: last_admin
            email<EMAIL_ADDRESS>            password: Test123456
            useralias: ANSIBLE-ADMIN
            company: DEFAULT_COMPANY
            roles:
              - "SAP_ALL"

Expected Results
Error
NA
Actual Results

NA

Code of Conduct

[X] I agree to follow the Ansible Code of Conduct

Hi @picoroma, thank you for open this Issue. It is not necessary to install pyrfc on the nw host because we always do rfc calls.
Ansible always execute modules on the host defined on top of the playbook.
Therefore you have two possible solution and depends on the tasks which should be executed:

Execute your playbook on localhost like:
(Only a good approach if you execute tasks which must not executed on the NW host for example)
 - name: SAP_USER
   hosts: localhost
   tasks:
     -

use delegation:
    - name: Create SAP User
      community.sap_libs.sap_user:
        conn_username: 'ADMIN'
        conn_password: 'MyAdminPSWD'
        host: myhostname
        sysnr: '00'
        client: '200'
        state: present
        username: ANSIBLE
        firstname: first_admin
        lastname: last_admin
        email<EMAIL_ADDRESS>        password: Test123456
        useralias: ANSIBLE-ADMIN
        company: DEFAULT_COMPANY
        roles:
          - "SAP_ALL"
     delegate_to: localhost

The delegation could also a other foreign host.
Both approaches needs the installation of pyrfc and sdk on the control node or delegate host.
If you want to use AAP or AWX you have to build a custom ee which contains pyrfc.
Please let me know if this will solve your problem.
If you have any question feel free to reach out to me.

Hi @rainerleber !
THX to you for answer me!.
I'm quite new to ANSIBLE and i have a lot of GAP on this.
Anyway I have tested successfully both method you give me.
One question - regarding for example "community.sap_libs.sap_user"
How can I use the ANSIBLE methot to create user MASSIVELY ?
Assigning each one for example different SAP Profile ?
THX

It depends on what you want to achieve exactly a possible solution:
defining a var like:
user_groups: ''
  - { firstname: "admin_user", username: "test_admin", role: "SAP_ALL" }
  - { firstname: "monitoring_user", username: "test_mon", role: "SAP_ADMIN" }

and the task like:
    - name: Create SAP User
      community.sap_libs.sap_user:
        conn_username: 'ADMIN'
        conn_password: 'MyAdminPSWD'
        host: myhostname
        sysnr: '00'
        client: '200'
        state: present
        username: "{{ item.username }}"
        firstname: "{{ item.firstname }}"
        lastname: last_admin
        email<EMAIL_ADDRESS>        password: Test123456
        useralias: ANSIBLE-ADMIN
        company: DEFAULT_COMPANY
        roles:
          - "{{ item.role}}"
    loop:
      - user_groups

You can also develop a solution reading AD user write them to a set_fact var and iterate over it for example.

Thank for the hint i will correct it :-)

Solved


OSX High Sierra

High Sierra version of the box would be nice now that it's released.

Agreed, High Sierra brings Xcode 9.x which is the version officially supported by e.g. https://github.com/flutter/flutter.
Updating via softwareupdate -a -i --verbose gets stuck after downloading and unpacking files. Updating via UI also gets stuck a few minutes after reboot.

I've been able to upgrade the box to High Sierra. Usually when you upgrade after the restart nothing happens. You need to perform a workaround described here:
https://raimue.blog/2017/06/09/upgrading-a-vm-from-macos-10-12-sierra-to-macos-10-13-high-sierra-in-virtualbox/
This workaround have been working with all updates so far. (virtualbox 5.2)

monsenso appears to have one https://app.vagrantup.com/monsenso/boxes/macos-10.13; although I couldn't get it to start. That's because I can't get a VirtualBox more recent than 5.1.18 to actually work on my MacBook Pro though...

How to get latest macOS High Sierra? Will this repo be updated?

Can confirm that the Vagrant box linked by @chaospixel works correctly, though it has the usual performance issues of OSX in a VM. It requires at least VirtualBox 5.2 (5.2.2 and above for the resolution fix below), with the extensions pack installed.
I can't find a Github/FOSS repo for the box, so I can't submit this there, but if you're using it and have problems with screen resolution, you can override them in the Vagrantfile:
config.vm.provider "virtualbox" do |vb|

  ... Existing config here ...

  # Set the screen resolution inside the machine
  vb.customize ["setextradata", :id, "VBoxInternal2/EfiGraphicsResolution", "1920x1080"]

end

Replace 1920x1080 with whatever screen resolution you desire, obviously.


amended deprecated syntax

Amended deprecated syntax
From
networks:
  dhcp:
      external:
          name: "staff-device-dhcp-server_default"

To
`networks:
  dhcp:
    name: "staff-device-dhcp-server_default"
    external: True`

Source for new syntax:
https://docs.docker.com/compose/networking/#use-a-pre-existing-network


Support Exporter in core

Provide the core bridge to support exporter module. I will add implementations later.

OC Metric API integration
gRPC service our own formats

Coverage decreased (-0.006%) to 14.107% when pulling 076be13d82844ad2221f1c6995c2706d00669001 on exporter into 14db2ede7f36a93c1342c403f6daa96b55946caa on master.


refactor: Remove custom hit testing in usePress

Related to #1720, #2506, #5290
Back in #62 we implemented our own hit testing in usePress in order to work around a bug in pointer events in iOS 13. Now that this version is long gone, we can probably remove this and use the onPointerLeave and onPointerEnter events instead. This depends on releasePointerCapture being called during onPointerDown on touch devices, so that the original target doesn't capture the pointer and cause the browser to retarget all events to it even outside the hit area.

Updated to address two issues found in testing:

On touch (ipad), open any sub menu and press down on a submenu item, without lifting, slide off the submenu and release. Menus all close now. The close behavior exists already with mouse.

This only happens in RSP v3, not in RAC, because we recently changed the DOM structure to no longer be nested there. In RSP we have an extra useInteractOutside in Menu, but it only checks if the interaction was outside the menu itself not any submenus. It checks that during onInteractOutside but not in the pointer down event. I moved this to the root menu trigger instead so submenus should be included.

On ipad, starting a touch event on one item and then dragging and releasing of a different item selects that item. Doesn't happen on Android and doesn't happen if the dropdown is scrollable. Didn't happen on main previously, same issue as row 7. Also occurs for Menu (DL)

This works as intended with mouse (matching native behavior), but it is weird with touch since the user might be trying to scroll. Updated this logic to only select during onPressUp if pointerType is mouse, otherwise wait for onPress which requires pressing down on the same target your release over.


Dockerisation of the project

I can work on dockerisation of this entire project.

@ShivanshPlays someone else also raised the same issue, so do you preferably want to work on this or shall I assign him?

Yes, I want to work on this issue, but as discussed with @rahulsainlll this issue shall be addressed during the later half of the program.
Although I would be more than happy to work on it, whenever it is assigned to me

@ShivanshPlays someone else also raised the same issue, so do you preferably want to work on this or shall I assign him?

it will be good if we do this after we merge other PRs first it can be done 1-2 week before gssoc end do remind me @ShivanshPlays before it ends i'll assign with other this under level3

Ok , I'll do it in the later half of the program

@ShivanshPlays are you working on this issue?

@unknown91tech bro, the project admin has told me to work on this in the last week

@ShivanshPlays okay no problem


Workspace

Hello,
This is realy nice thing for Vault users and CAD administrator.
This solution get file to user workspace, what is litle bit dangerous, because user can had some old version of file on his local drive. It will be good if file and workspace can be at some temp folder.
There is also some problem on polish version with loging. Extension working for me if i comment this line:  //      mLogCtrl.SaveLogAs(mILogicLogFileFullName);

In another case I'm geting exception:"
Job failed by unhandled exception: System.InvalidOperationException: Brak aktualnego pliku dziennika.
w System.Dynamic.ComRuntimeHelpers.CheckThrowException(Int32 hresult, ExcepInfo& excepInfo, UInt32 argErr, String message)
w CallSite.Target(Closure , CallSite , ComObject , String )
w System.Dynamic.UpdateDelegates.UpdateAndExecute2[T0,T1,TRet](CallSite site, T0 arg0, T1 arg1)
w System.Dynamic.UpdateDelegates.UpdateAndExecuteVoid2[T0,T1](CallSite site, T0 arg0, T1 arg1)
w Autodesk.VltInvSrv.iLogicSampleJob.JobExtension.Execute(IJobProcessorServices context, IJob job) w C:\Users\koechlm\source\Autodesk.VltInvSrv.iLogicSampleJob\Autodesk.VltInvSrv.iLogicSampleJob\JobExtension.cs:wiersz 471
"

Hello Dariusz,
thank you for the feedback. As it relates to the Job for the iLogic Support project, let's move the conversation there.
Thanks,
Markus


Edit the information panel for the CohortCharacteristics functions

This can be edited here:
https://github.com/oxford-pharmacoepi/omopViewer/blob/123b8a561cc4ecc113a0cf2cc41021c4ce8bac51/data-raw/internalData.R#L7-L15


BEF/BJLS: support target scoped classapaths

Sample project:
https://github.com/salesforce/bazel-jdt-java-toolchain
//builder/src/main/java
java_library(
    name = "jdt_java_builder_lib",
    srcs = [
        "com/salesforce/bazel/jdt/toolchain/builder/InvalidCommandLineException.java",
        "com/salesforce/bazel/jdt/toolchain/builder/JdtJavaBuilder.java",
        "com/salesforce/bazel/jdt/toolchain/builder/SimpleOptionsParser.java",
    ],
    deps = [
        "//builder/src/main/java/com/salesforce/bazel/jdt/toolchain/builder/jarhelper",
        "//builder/src/main/protobuf:deps_java_proto",
        "//builder/src/main/protobuf:java_compilation_java_proto",
        "//builder/src/main/protobuf:worker_protocol_java_proto",
        "@rules_jdt_guava",
        "//builder/third_party/ecj",
    ],
    visibility = ["//visibility:public"],
)

//builder/src/main/com/salesforce/bazel/jdt/toolchain/builder/jarhelper
java_library(
    name = "jarhelper",
    srcs = [
        "JarCreator.java",
        "JarHelper.java",
    ],
    visibility = ["//visibility:public"],
)

Coming up with project names and representation is not easy.
Should we use target names?
Should we use project names inherited from the full folder structure?
Can we do something else?

@plaird Can you share some context why the current logic is implemented this way:
https://github.com/salesforce/bazel-eclipse/blob/master/bundles/com.salesforce.bazel.eclipse.common/src/main/java/com/salesforce/bazel/eclipse/project/EclipseProjectUtils.java#L82-L87
Given that there can be multiple java targets in a single package - each with entirely different classpaths - shouldn't the target name become a qualifier for the project name (if not a dominator)?
To follow the example above: two projects will be created in Eclipse: jdt_java_builder_lib and jarhelper
Alternatively I can think of:

builder - jdt_java_builder_lib
java - jdt_java_builder_lib
builder-src-main-java (jdt_java_builder_lib)
jdt_java_builder_lib (builder-src-main-java)

Or other variations of it.
3+4 will have the benefit of being unique in the Eclipse workspace. The number suffix would disappear. However, they are very verbose and there could be special cases with overlap (eg., //package-special/somedir vs. //package/special/somedir). One could argue those should be clean-ed up in the Bazel workspace, though.

Good question, this is a design decision that I should document somewhere. It is discussed in docs here and there and discussed in some Issues. Remember that we map the whole Bazel package into JDT main/test classpath construct using a union classpath of all java targets in the package:
https://github.com/salesforce/bazel-eclipse/blob/master/docs/bef/using_the_feature_classpath.md#classpaths-are-scoped-to-each-eclipse-project
There are a few reasons for this...

With target scoped projects there would be an explosion of Eclipse projects inside the IDE. Personally, I don't like to have more than 10-20 projects open in Eclipse at any time. I typically develop with about 10 Bazel packages at a time in our monorepo (use case dependent, but for what I work on this is normal). If you import packages with 5 targets each, the experience gets bloated really quickly.

Even if we implemented this, JDT would be awkward anyway because a single java source file can be consumed by multiple java targets within the package...with different classpaths. Right now if you do this in BEF you can add an import that is valid in the Java editor but breaks the command line build, which isn't great. If we had target scoped classpaths, this would appear in JDT as the same source file being linked to multiple Eclipse projects. But then code completion would be context sensitive - how did you open the file? Not only is this confusing, but again you could add something that broke the command line build for another target. I don't think this is great user experience either. If we did all this work to implement this, I would expect a better experience.

In Bazel, each test class has its own classpath. So to be correct, every test would need to be a distinct Eclipse project as well. With some of our packages having 200 test classes, this is nasty.

Level of effort and complexity of the BEF code. This would be a major change and require quite a bit of work to get right. Test coverage of this would be a big project by itself. Just consider all the variations of the above (test classpaths, launchers, etc).

Given what else we need to work on to make BEF better, it just hasn't been a priority for me to provide a finer grained classpath.  The package scope of classpath is a compromise between usability and correctness, and requires a lower level of effort and testing. As a user myself, I personally would not welcome having target scoped Eclipse projects, as for our monorepo that would be a step backwards in usability.
As a comparison, the IJ plugin puts the entire Bazel workspace into a single project and classpath. So BEF is far better than that with package scoped classpaths. If your team wanted to do this, we could make it an import option for users that want that level of granularity. But I honestly don't think most users would prefer it.
So back to the above computeEclipseProjectNameForBazelPackage() method, appending a target name would actually be confusing, because that would imply the classpath was scoped to the target in the IDE.
Other things:

We do plan to support selective target import, that is in fact the theme of the next minor release: https://github.com/salesforce/bazel-eclipse/projects/12. Having that would allow the user to reduce the project explosion problem. But this feature makes most sense if users exclude entire types of targets (springboot) as hand picking packages for import is tedious already. Project Views help with this, but....
Having target scoped classpaths would solve the circular reference problem in #197 which is nice. But in practice has been easily solved by just changing the BUILD files so hasn't been a priority for us.

@plaird Thanks for sharing. I have a few follow up question/comments.

Why is "Bazel Workspace (name)" mostly empty, i.e. only links? Wouldn't it be better if the full workspace is made accessible from a file browsing perspective? It could be a simple project without any Java.

Problem for shared sources between targets is a valid concern. Would it work to exclude that case and ask developers to restructure their projects for better granularity and dependency management? How does IntelliJ deals with this?

In our mono-repo, developers would need to work with 50-150 targets at a time. They are used to have this as projects. I'm not sure if this is the best approach, though.

I'm not a big fan of linking. It takes away the ability to use Eclipse tools such as EGit for Git management. Have there been experiments with creating projects inside the source tree and using filtering capabilities?

@guw good questions, responses....

Why is "Bazel Workspace (name)" mostly empty, i.e. only links? Wouldn't it be better if the full workspace is made accessible from a file browsing perspective? It could be a simple project without any Java.

I am open to this. I last worked on this in #180 but in a limited way. BTW, this is changing for some use cases due to the work in #404

Problem for shared sources between targets is a valid concern. Would it work to exclude that case and ask developers to restructure their projects for better granularity and dependency management?

Yes, but this is why I get worried about the mental complexity of target scoped Eclipse projects. It just feels like it will be hard to convey the sharp edges to users. This is why I wouldn't want it to be the default option, if we do it. "I just tried to import this workspace, and BEF vomited up all these weird complaints. I just want to edit some Java code".

How does IntelliJ deals with this?

IJ builds a single union classpath for the entire Bazel workspace. They talked about fixing this at one point.

In our mono-repo, developers would need to work with 50-150 targets at a time. They are used to have this as projects. I'm not sure if this is the best approach, though.

OK. That is why I think target scoped projects is still worthwhile option for some use cases. Just don't like it as the default behavior. BTW, the way I see users working with your monorepo is your team adds a Project View creator to your setup CLI (obfuscating internal SFDC details here, that you and I both know). So you will ask the users what packages they will work with up-front, and it generates a Project View file. The Project View file would need to signal that the Eclipse projects should use target scoped import.

I'm not a big fan of linking. It takes away the ability to use Eclipse tools such as EGit for Git management. Have there been experiments with creating projects inside the source tree and using filtering capabilities?

Agreed, this would be good to support. No, we haven't investigated it.


[ENG-475] Meeting detail header

Purpose
Add meeting detail page header.
Summary of Changes
New meeting-detail-header component and some tests.
Ticket
https://openscience.atlassian.net/browse/ENG-475
Reviewer Checklist

[ ] meets requirements
[ ] easy to understand
[ ] DRY
[ ] testable and includes test(s)
[ ] changes described in CHANGELOG.md

Pull Request Test Coverage Report for Build 2944

81 of 101 (80.2%)  changed or added relevant lines in 6 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.03%) to 72.005%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

app/adapters/meeting-submission.ts
6
10
60.0%

app/meetings/detail/-components/meeting-detail-header/component.ts
42
46
91.3%

app/meetings/detail/-components/meeting-submissions-list/component.ts
14
18
77.78%

app/meetings/detail/route.ts
1
9
11.11%

Files with Coverage Reduction
New Missed Lines
%

app/meetings/detail/route.ts
1
58.97%

Totals

Change from base Build 2935:
0.03%

Covered Lines:
6230

Relevant Lines:
7797

💛  - Coveralls

Also, please update with the latest develop.


Az Powershell documentation is old and misleading

Please update documentation  with a latest image of Az Powershell task. As of now the Az modules cmdlets are specific for Task version 4.* .The image still shows 2.* . Also in 4.* the inline scripts  arguments are gone.
This results in failure of Devops  pipelines

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1e22e4d6-366f-fbf8-e141-8905ca7ab7ae
Version Independent ID: 5be2acf2-66e7-cadf-6666-5a85a65b9771
Content: Continuous integration and delivery in Azure Data Factory
Content Source: articles/data-factory/continuous-integration-deployment.md
Service: data-factory
GitHub Login: @djpmsft
Microsoft Alias: daperlov

Hello @Viswa-Ranjan-Sahu .  We will review the document and provide an update as appropriate.

@Viswa-Ranjan-Sahu  I have assigned this issue to the author to update as appropriate.
@djpmsft This one requires an image update due to breaking changes in Az.

@Viswa-Ranjan-Sahu , this is in reference to the Update Active Triggers section, correct?

Hi @Viswa-Ranjan-Sahu ,
Apologies for the delay in response. I have updated the documentation to account for this, you should see it public by end of day today.
Thanks,
Daniel

#please-close


Service Plan should be free by default

Following service broker api documentation, service plan  should be free by default.
Actual implementation makes service plan not free by default
	/**
	 * Indicates whether the plan can be limited by the non_basic_services_allowed field in a Cloud Foundry Quota.
	 */
	@JsonSerialize
	@JsonProperty("free")
	private boolean free;

Completed via https://github.com/orange-cloudfoundry/spring-cloud-cloudfoundry-service-broker/commit/d2246ed6439dbd2627ad44c93f4f2cedfbe2c28a


Save as netcdf

Detailed Description
Save joined files at netcdf (instead of zarr). Think this is slightly better as zarr file is a lots of small files.

Think this is slightly better as zarr file is a lots of small files.

Just to clarify:
NetCDF is probably better when you know you'll always want to load the entire dataset into memory (which is probably true when we only have a few hours of NWP data. But probably isn't true when we have days (or more) of NWP data).
Zarr is better when you might be on the cloud, and when you often want to load only part of the dataset into memory.  (Because, on the cloud, you can't really seek into objects in cloud storage. So if you use a single large NetCDF file then you have to load the entire NetCDF file from the cloud bucket, even if you only want a small subset of the data).


Refresh captcha.

Hi,
I'm trying to refresh the captcha but always I'm getting the same image.
I can't see any way te regenerate the phrase. How can I do it?
Regards.!

Hi. I think it's a browser issue.
As temporary workaround, you can generate an unique url to prevent caching.
For example:
<img src="<?= $this->url('captcha') ?>?<?= rand(0, 9999) ?>" />

A more correct solution is to specify the following headers:
Cache-Control: no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: 0

I will do it as soon as possible.
Thanks for your report!

I tried to add the no cache but the response is still the same.
$response = new Response($image, 200, array('Content-Type' => 'image/jpeg'));
$response->setPrivate();
$response->setMaxAge(0);
$response->setSharedMaxAge(0);
$response->headers->addCacheControlDirective('must-revalidate', true);
$response->headers->addCacheControlDirective('no-store', true);
return $response;

The only thing that changes it is doing:
$app['captcha.image_url'] = $app->protect(
            function () use ($app) {
                /** @var $urlGenerator UrlGenerator */
                $urlGenerator = $app['url_generator'];

                return $urlGenerator->generate($app['captcha.route_name'], array(), UrlGenerator::ABSOLUTE_URL). "?".  rand(0, 1000000);
            }
        );

But is not a really nice solution. If you want I can make the fork/fix and send the merge?
Regards

But is not a really nice solution. If you want I can make the fork/fix and send the merge?
I'm against on this because it is a dirty hack.

Nevertheless, I will try to find a nice solution.

Kilte any news for this?
Regards.

@rsantellan, I've tried to reproduce this bug, but I couldn't. It seems to me, this is a server configuration issue.
Unfortunately I can't  to help you. But it would be nice if you will show your host configuration. Maybe I'm still able to help.
Finally, you can use a workaround, described above.

I'm using basic ubuntu configuration:
<VirtualHost *:80>
	# The ServerName directive sets the request scheme, hostname and port that
	# the server uses to identify itself. This is used when creating
	# redirection URLs. In the context of virtual hosts, the ServerName
	# specifies what hostname must appear in the request's Host: header to
	# match this virtual host. For the default virtual host (this file) this
	# value is not decisive as it is used as a last resort host regardless.
	# However, you must set it for any further virtual host explicitly.
	#ServerName www.example.com

	ServerAdmin webmaster@localhost
	DocumentRoot /var/www

	# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
	# error, crit, alert, emerg.
	# It is also possible to configure the loglevel for particular
	# modules, e.g.
	#LogLevel info ssl:warn

	ErrorLog ${APACHE_LOG_DIR}/error.log
	CustomLog ${APACHE_LOG_DIR}/access.log combined

	# For most configuration files from conf-available/, which are
	# enabled or disabled at a global level, it is possible to
	# include a line for only one particular virtual host. For example the
	# following line enables the CGI configuration for this host only
	# after it has been globally disabled with "a2disconf".
	#Include conf-available/serve-cgi-bin.conf
</VirtualHost>

I tried to add a reload captcha button with the following jquery.
function reloadCaptcha()
{
  $.ajax({
      url: $('#reload-captcha-url').val(),
      type: 'get',
      dataType: 'json',
      success: function(data){
        if(data.result == "OK")
        {
            $("#catpcha-img").attr('src', data.captchaUrl);
        }
      },
      complete: function()
      {

      }
  });
}

Adding the url on the twig template:
<input type='hidden' value="{{ path('captcha-reload') }}" id="reload-captcha-url" />

And passing it from the app:
return $app['twig']->render('users/login.html.twig', array(
          'error'         => $error,
          'last_username' => $lastUser,
          'captchaUrl' => $app['captcha.image_url'](),
          'showCaptcha' => $showCaptcha,
          'askOtp' => $askOtp,
          'changePasswordMessage' => $changePasswordMessage,
      ));

Why so hard? Keep it simple.
<!DOCTYPE html>

        <title>Refresh image</title>

That fix it! And is not soo bad.
I was doing it with a line like this:
return $urlGenerator->generate($app['captcha.route_name'], array(), UrlGenerator::ABSOLUTE_URL). "?".  rand(0, 1000000);

On vendor/kilte/silex-captcha/source/CaptchaServiceProvider.php
So I don't have to worry of doing it on the url.
Thanks.


Ensure that userns is created for stopped rootless pods

When starting a container in a stopped pod, we attempt to recursively start dependencies. Unfortunately, this presently causes an error when we try and join an appropriate user namespace, as we weren't checking whether the PID of the container we're joining was not 0. Fix that here.

LGTM

LGTM

/test images
/lgtm

Changes LGTM, but test aren't buying it.

Tests ought to be fixed

/lgtm


[google_maps_flutter] Possibility to Remove Directions Icon

Use case
When I tap on a marker in the GoogleMap view for my application it shows the Marker InfoWindow, centralizes the map on the marker and shows two icons in the right bottom of the map: "Directions" and "Open GoogleMaps App".
I would like to take off these icons on the right bottom and create my own icons to provide these kinds of functions. I can make the marker consume the tap event and not show these icons but it would cancel the other events too. I want to keep showing the InfoWindow and centralizing the map on the market without having to handle it manually. This icons only appearrs in the Android
Proposal
When creating a GoogleMap() adds an optional parameter that cancels the appearing of these bottom right icons when a market is tapped

Me too. I am showing a FAB in the bottom right where the direction / google maps icon are. Is there a flag to remove these icons?

This is important and also mentioned here: https://github.com/flutter/flutter/issues/25660

Already fixed
https://github.com/flutter/plugins/pull/1808

@felpsio so is it safe to close the issue?

Yes :).


(3) refactor: hardcoded explorer link to networkSettings explorerUrl

Acceptance Criteria

Use the networkSettings.explorerUrl as the link to the explorer button.

Security Checklist

[ ] Make sure you do not include new dependencies in the project unless strictly necessary and do not include dev-dependencies as production ones. More dependencies increase the possibility of one of them being hijacked and affecting us.

I rebased with the previous PR to resolve conflicts.


[BUG] Capitalize the h in the GitHub word

Description of the bug
The h should be capitalized as the word itself should be GitHub. Go to the src/_includes/partials/footer.html file.
In line 96, change the word to GitHub, as currently the h is not capitalized.
Please add screenshots (if applicable)

Add any other context about the problem here
No response
Code of Conduct

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

can i work on this?

Done

check it

 check it

You must fork this repository, implement your changes, make a PR, and then we will review it to see if it's good. 🙂

can i work on this?

Feel free to work on this if you want. I'm just not sure if @Ashwani132003 wants to work on that, though.

I can do it?

@Panquesito7 I do not think we should add the hacktoberfest label. It's just changing a letter

I can do it?

A PR was already made, sorry. 😅


Event spaces disappearing after patching ROM

I placed an event space next to Boo and then patched the ROM. After I loaded up this ROM in PP64, I found that the event that was attached to the space was gone. I did use the space that is used for junctions (not sure what to call this space). This combined with other issues is making my board nearly impossible to create properly.

It is a bug that sometimes PP64 is not able to parse events that it wrote when loading a ROM back in again. It has been lower priority because I don't think it is common that a patched ROM is opened again in PP64.
I'm not sure why this is causing you so much trouble? You can always load a fresh ROM and re-apply your board while making changes. If the board is really large and the browser is not willing to save it to local storage, you should use the "Export Board" option to save the board file, and then import it again when you use PP64 next time. There are no issues like this with reading board files, so all the events will be fine through an export/import.

Thanks for the quick response. I only posted this issue because I assumed that because PP64 was not showing these events, they were not in game either. This was my fault, as I should have tested it before so quickly reporting the bug. Thanks again for the quick response and thank you for working so hard on this project!

Closing this issue, as the board file is now stored in the ROM, which allows for the custom boards to be retrieved completely.


User as an object of [Getter/Setter]

I do not know why GoogleSignIn.signIn always returns an object of [Getter/Setter]
11-28 21:20:46.496  4879  5182 I ReactNativeJS: { serverAuthCode: [Getter/Setter],
11-28 21:20:46.496  4879  5182 I ReactNativeJS:   idToken: [Getter/Setter],
11-28 21:20:46.496  4879  5182 I ReactNativeJS:   photo: [Getter/Setter],
11-28 21:20:46.496  4879  5182 I ReactNativeJS:   scopes: [Getter/Setter],
11-28 21:20:46.496  4879  5182 I ReactNativeJS:   email: [Getter/Setter],
11-28 21:20:46.496  4879  5182 I ReactNativeJS:   name: [Getter/Setter],
11-28 21:20:46.496  4879  5182 I ReactNativeJS:   id: [Getter/Setter] }
Anyone got the same problem?

Nevermind. I got it.


H5151 Gateway and H5100 Therm/Hygrometers

I see that bluetooth devices are not supported but the Gateway uses wifi. Can support be added for these sensors/gateway? Right now in the logs I am getting "bluetooth sensor not supported by this plugin, see " but these operate over Wifi.

Hi @rmaes4
Apologies I'm a bit behind on all these govee issues right now! Getting through them slowly.
I never realised that a wifi gateway existed for these sensors.
When you start the plugin, does it show any info about the H5151 being not supported?

@bwp91
No worries, I understand being busy completely.
These are the logs I get when starting the plugin.
[17/04/2022, 21:24:42] [Govee] [Bed Therm. (3)] bluetooth sensor not supported by this plugin, see https://bit.ly/hb-plugin-govee
[17/04/2022, 21:24:42] [Govee] [Window Therm. (2)] bluetooth sensor not supported by this plugin, see https://bit.ly/hb-plugin-govee
[17/04/2022, 21:24:42] [Govee] [Dresser Therm. (1)] bluetooth sensor not supported by this plugin, see https://bit.ly/hb-plugin-govee

It doesn't seem there are any logs pertaining to the H5151 gateway, only the H5100 sensors.

Looks like there is a new API at https://app2.govee.com/app/v1/gateways to get the gateway H5151
Then from there, will likely need a new thermo class for gateway, so something like ThermoGateway and when you discover H5100, have to look and see if its part of the gateway or not.  I've only glanced at your code, but, I think because the H5100 is tagged as BLE, it now is BLE over gateway.  Should be fun to handle.

Upvote on this. Would be nice to have!

Looking forward to this myself. I just picked this H5151 up and thought it would work. lol. Glad to see someone supporting this though. Thanks for your hard work!

Can anyone update to the new beta 5.2.1-beta.3 of the plugin? I have re-enabled these bluetooth sensors to show.
Maybe their current temperature/humidity values that the plugin collects about these devices is automatically updated by the gateway. This is what I am hoping!
Instructions for beta installation if needed:
https://github.com/bwp91/homebridge-govee/wiki/Beta-Version

Can anyone update to the new beta 5.2.1-beta.3 of the plugin? I have re-enabled these bluetooth sensors to show.
Maybe their current temperature/humidity values that the plugin collects about these devices is automatically updated by the gateway. This is what I am hoping!
Instructions for beta installation if needed: https://github.com/bwp91/homebridge-govee/wiki/Beta-Version

Awesome!! Working! I have my temps and humidity showing up now! Thanks dude!

Do the values update over time if you don’t connect your phone to the sensors within the govee app?

Do the values update over time if you don’t connect your phone to the sensors within the govee app?

I’ll check throughout the day today. At the moment the values in the app and HomeKit are the same (rounded up and down to the nearest tenth - I assume that’s by design or HomeKit doing it).

Is there any way to change the temperature from C to F?

Do the values update over time if you don’t connect your phone to the sensors within the govee app?

I’ll check throughout the day today. At the moment the values in the app and HomeKit are the same (rounded up and down to the nearest tenth - I assume that’s by design or HomeKit doing it).

Looks good on my end, values are updating.

Is there any way to change the temperature from C to F?

In the settings app on your iphone, go to Language & Region -> Temperature Unit -> and choose F.
This should show the values in the home app as fahrenheit

Closing this as a bit overwhelmed with issues.
Please update to the beta version of the plugin, and if you are still having issues, do reopen this ticket!
Thanks and apologies if closing prematurely.


TCL: Remove MgmtHashTable.h

This library is obsolete and not being used anywhere.
It shows up when I'm cleaning up the TCL dependency.

Cherry picked to 8.1.0


Cannot find module '@babel/preset-typescript' 🐛

What were you trying to do?
I am setting up my project to use react-native-vision-camera
Reproduceable Code
No response
What happened instead?
The app bundle is not able to be built through the metro bundler:
error: node_modules/react-native-vision-camera/src/hooks/useFrameProcessor.ts: /node_modules/react-native-vision-camera/src/hooks/useFrameProcessor.ts: Cannot find module '@babel/preset-typescript'

I had to install a few other babel plugins just to get this far.
I received the same error for the follow plugins:
    '@babel/plugin-transform-shorthand-properties',
    '@babel/plugin-transform-arrow-functions',
    '@babel/plugin-transform-template-literals',

My project is not TypeScript and I should not be required to install these plugins to get this module working.
Relevant log output
No response
Device
Pixel 4 XL
VisionCamera Version
2.9.3
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

I'm also encountering this issue.
error: FaceDetection.tsx: FaceDetection.tsx: Cannot find module '@babel/preset-typescript'
Require stack:

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>\react-native\node_modules\metro-transform-worker\src\index.js
\react-native\node_modules\metro\src\DeltaBundler\Worker.js
\react-native\node_modules\jest-worker\build\workers\processChild.js
BUNDLE  ./index.js

Did you try cleaning your cache as mentioned in the Troubleshooting Guide?
npx react-native start --reset-cache

Also, is babel installed correctly?

So weird, I got this same issue after upgrading Reanimated to 2.3.0.
Clearing the cache didn't help for me. Can't seem to figure out why Reanimated is causing this, but maybe it's a similar reason to vision camera?

Closed due to inactivity

I'm facing the same issue with `react-native-gesture-handler. have you found a solution?

yarn add @babel/preset-typescript fixed it for me with reanimated.

@nandorojo thanks, it worked for me with react-native-gesture-handler

I had to pod install after doing yarn add @babel/preset-typescript