Filesystem type detection

Opening this issue to discuss filesystem detection
In reference to https://github.com/Storj/driveshare-gui/issues/57 for dataserv-gui
In the Dataserv-client cli -help, I'm seeing
--use_folder_tree     Use folder tree to store files (always on for fat32 store_path).

I'm not certain that the GUI should be passing the use_folder_tree option here; to me, it seems like the dataserv-client should be determining the file system type to eliminate the need for client applications to implement various cross-platform file system detection or worse, a checkbox for a user to tell a machine about itself. I wanted to gather thoughts concerning this addition, thanks.

Storjnode implements this in utils: https://github.com/Storj/storjnode/blob/master/storjnode/util.py
Cake.

The fat32 detection moves from dataserv-client to storjnode. https://github.com/Storj/dataserv-client/blob/master/dataserv_client/api.py#L66
At the moment we can't detect fat32 drives for sure. One of the problems is: https://code.google.com/p/psutil/issues/detail?id=434

From what I understand this is already implemented, just detection remains spotty.


feat: use url from annotation value for webhook-notification

This feature is enabling to set an Webhook-URL within the annotation. The value is already written into Destination.Recipient and now used when it's an valid URL.
Can therefore be set from ArgoCD UI.

@jimtoniq
Would you add docs for this features?

@ryota-sakamoto
Sure! hope that one is enough

Hi Alex,
thanks for looking into my PR.
With our webhook-service configuration, we have something like this
  service.webhook.mattermost_webhook: |
    url: https://{mattermost-host}/hooks/{hook-id}
    headers:
    - name: Content-Type
      value: application/json

We want our users to configure their webook-url on their own (via UI with app-annotations), but with the above configuration, we would need to create several webhook-service-configs for each new webhook on many mattermost-channel.
The url above shouldn't be optional but a fallback.
With the email-service, its possible (or even required) to set the recipient from annotation, as its read from dest.Recipient
https://github.com/argoproj/notifications-engine/blob/0e1f1eda5f52843e21f5b8fb50e4b0ef81bcab2a/pkg/services/email.go#L84
Thats why I tried making use of the dest.Recipient in the webhook-service, as its already read from the annotation and consider it as a overwrite.
I see it as a flexible solution to have the notification-template be the same, with less manual yaml-configuration but custom webhook-urls.
Do you think we would need to make changes to not break other usages? Let me know

@jimtoniq , in your use case, is it required to override mattermost host for each recipient? If not then you already can use {{recipient}} in template:
  service.webhook.mattermost_webhook: |
    url: https://{mattermost-host}/hooks/
    headers:
    - name: Content-Type
      value: application/json

  template.<templateName>: |
    webhook:
      <webhook-name>:
        method: POST
        path: /{{recipient}}
        body: |
          <optional-body-template>

So the request will be sent to https://{mattermost-host}/hooks/{{recipient}}
If you need to override whole URL then we need to make a code change. I just realized we can support url field in  template  - probably this is the cleanest solution and won't break existing behavior

We would like to set the entire url from the annotation.
So that we could have one service and one template for each webhook-service.
Then annotations on the Application can be
notifications.argoproj.io/subscribe.app-health-degraded.mattermost_webhook: https://mymattermost.domain.tld/hooks/abcd1234
for one app,
for another one
notifications.argoproj.io/subscribe.app-health-degraded.mattermost_webhook: https://anothermattermost.domain.tld/hooks/bcd0123
without having to configure multiple services or templates in our argocd-notifications configuration.
With the current state, we would create two services for the upper example:
service.webhook.mymattermost_webhook: |
    url: https://mymattermost.domain.tld/hooks/abcd1234
    headers:
    - name: Content-Type
      value: application/json

service.webhook.anothermattermost_webhook: |
    url: https://anothermattermost.domain.tld/hooks/bcd0123
    headers:
    - name: Content-Type
      value: application/json

and two redundant webhook-templates
   template.app-health-degraded: |
     email:
       subject: Application {{.app.metadata.name}} has degraded.
     message: |
       {{if eq .serviceType "slack"}}:exclamation:{{end}} Application {{.app.metadata.name}} has degraded.
       Application details: {{.context.argocdUrl}}/applications/{{.app.metadata.name}}.
     webhook:
      mymattermost_webhook:
        method: POST
        body: |
          {
            "attachments": [{
              "title": "{{.app.metadata.name}}",
              "title_link": "{{.context.argocdUrl}}/applications/{{.app.metadata.name}}",
              "color": "#18be52",
              "fields": [{
                "title": "Sync Status",
                "value": "{{.app.status.sync.status}}",
                "short": true
              }, {
                "title": "Repository",
                "value": "{{.app.spec.source.repoURL}}",
                "short": true
              }]
            }]
          }
      anothermattermost_webhook:
        method: POST
        body: |
          {
            "attachments": [{
              "title": "{{.app.metadata.name}}",
              "title_link": "{{.context.argocdUrl}}/applications/{{.app.metadata.name}}",
              "color": "#18be52",
              "fields": [{
                "title": "Sync Status",
                "value": "{{.app.status.sync.status}}",
                "short": true
              }, {
                "title": "Repository",
                "value": "{{.app.spec.source.repoURL}}",
                "short": true
              }]
            }]
          }

Sorry for the long response @jimtoniq .
Got it . In this case I would recommend adding the url field in webhook template. So you could define mattermost service once and use  url: "{{recipient}}" in template to support customizing the full URL.
  service.webhook.mymattermost_webhook: |
    headers:
    - name: Content-Type
      value: application/json
   template.app-health-degraded: |
     webhook:
      mymattermost_webhook:
        method: POST
        url: "{{recipient}}"
        body: |
          {
            "attachments": [{
              "title": "{{.app.metadata.name}}",
              "title_link": "{{.context.argocdUrl}}/applications/{{.app.metadata.name}}",
              "color": "#18be52",
              "fields": [{
                "title": "Sync Status",
                "value": "{{.app.status.sync.status}}",
                "short": true
              }, {
                "title": "Repository",
                "value": "{{.app.spec.source.repoURL}}",
                "short": true
              }]
            }]
          }

Does it sounds good?


[3.9] pm updated license behaviour

Scope & Purpose
Updated license timing behaviour to final PM decision

[ ] :hankey: Bugfix (requires CHANGELOG entry)
[X] :pizza: New feature (requires CHANGELOG entry, feature documentation and release notes)
[ ] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification
[ ] :book: CHANGELOG entry made

Backports:

[ ] Backport for 3.9: (Please link PR)
[ ] Backport for 3.8: (Please link PR)
[ ] Backport for 3.7: (Please link PR)

Related Information
(Please reference tickets / specification / other PRs etc)

[x] Docs PR: https://github.com/arangodb/docs/pull/831
[ ] Enterprise PR:
[ ] GitHub issue / Jira ticket number:
[ ] Design document:

Testing & Verification
(Please pick either of the following options)

[ ] This change is a trivial rework / code cleanup without any test coverage.
[X] The behavior in this PR was manually tested
[X] This change is already covered by existing tests, such as unittests, shell_client.
[ ] This PR adds tests that were used to verify all changes:

[ ] Added new C++ Unit tests
[ ] Added new integration tests (e.g. in shell_server / shell_server_aql)
[ ] Added new resilience tests (only if the feature is impacted by failovers)

[ ] There are tests in an external testing repository:
[ ] I ensured this code runs with ASan / TSan or other static verification tools

Link to Jenkins PR run:
https://jenkins.arangodb.biz/job/arangodb-matrix-pr/18569/
Documentation

All new features should be accompanied by corresponding documentation.
Bugs and features should furthermore be documented in the CHANGELOG so that
support, end users, and other developers have a concise overview.

[ ] Added entry to Release Notes
[ ] Added a new section in the Manual
[ ] Added a new section in the HTTP API
[ ] Added Swagger examples for the HTTP API
[ ] Updated license information in LICENSES-OTHER-COMPONENTS.md for 3rd party libraries

External contributors / CLA Note
Please note that for legal reasons we require you to sign the Contributor Agreement
before we can accept your pull requests.

[ ] https://jenkins.arangodb.biz/job/arangodb-ANY-components-and-drivers/18/
[ ] https://jenkins.arangodb.biz/job/arangodb-ANY-mac-matrix/2648/

[ ] https://jenkins.arangodb.biz/job/arangodb-ANY-matrix/77/
[ ] https://jenkins.arangodb.biz/job/arangodb-ANY-components-and-drivers/22/

[ ] https://jenkins.arangodb.biz/job/arangodb-ANY-matrix/79/
[ ] https://jenkins.arangodb.biz/job/arangodb-ANY-components-and-drivers/23/


GULAppDelegateSwizzler - remote notifications methods and tvOS support

Changes required for #2591.

GULAppDelegateSwizzler - remote notifications methods support
GULAppDelegateSwizzler tvOS support

This is a part of PR #2683. I have to merge the changes first to make sure macOS support is available for FirebaseMessaging

Consider targeting the PR to  mm/messaging-swizzling instead of master to make it easier to review.

@paulb777 This PR is just a part of mm/messaging-swizzling that has to be merged earlier to allow Cocoapods lint to pass. From that prospective, the diff between this branch and mm/messaging-swizzling does not make sense.


[Question] How to render dynamically?

Hi, I am trying to render flag dynamically, but can't figure out.
How can I do something like this this?
{#each users as user}
    <Flag.{user.country} />
{/each}

Can you show how you did for other developers?

Thanks to https://stackoverflow.com/a/40564242/2277053
<script>
    import * as Flag from "svelte-flag-icons";
</script>

{#each users as user}
    <svelte:component this={Flag[user.country]} size="20" />
{/each}


client.rb contains incorrect chef_server_url

I am using v1.1.1 in local mode to setup a machine that should then be managed by a server specified in chef_server_url. My problem is that the created /etc/chef/client.rb points to http://localhost:8889 and not what I specified, even though the node is registered with the server and gets recipes from it during the provisioning run.
I've tried this with ssh and vagrant provisioners, and using 'with_chef_server' or specifying chef_server on the machine resource.
For example:
machine "test2" do
  chef_server( :chef_server_url => "http://<IP_ADDRESS>:8889")
end

What revision of Chef itself are you using?  chef-client -v I mean.

Hmm, I have suspicions.  I'm seeing this: chefzero://localhost:8889/nodes/ as the URL.  I bet we don't detect it.

Oh, right.  That shouldn't matter, because the chef server should be pointable regardless.  Testing.

Retrying this now, with chef-client 12.3 on the workstation and target VM, it looks like it's not putting anything in client.rb at all.

Just reran this with chef-client 12.3 on both workstation and target; same result. I think I had 12.2 on workstation and 12.3 on client originally.

Were you able to reproduce this?

fwiw, I still see this on current dev driver (1.3.0.dev.0)

I was looking at this during office hours and it was taking too long to troubleshoot, but it looks like this is definitely a bug.  The first weird thing I see is that chef_server is indeed a machine attribute, but I don't know where that is coming from.
We should also update our documentation so it is super clear how you specify which chef-server a machine should register itself with for convergence.
@christinedraper said that when doing this the machine initially converges correctly, but its only the client.rb content which contains the wrong URL for a chef server.  I hypothesize that https://github.com/chef/chef-provisioning/blob/master/lib/chef/provisioning/convergence_strategy/precreate_chef_objects.rb#L11 is getting the chef-server URL incorrectly.

As a workaround you should be able to specify
machine "test2" do
  chef_config :chef_server_url => "http://<IP_ADDRESS>:8889"
end

I did a bit of debug on this. Turns out it is significant that the 'chef server' I am pointing at is chef-zero running on localhost.
So for example, with the above I'm doing:
chef-zero -H <IP_ADDRESS>
where <IP_ADDRESS> is the IP address of localhost. Another scenario is where I'm using vagrant VMs running on a private network on localhost with IP addresses 10.0.1.x and I'm running chef-zero -H <IP_ADDRESS>
Anyway, what's happening is that setup_convergence does:
chef_server_url = make_url_available_to_remote(chef_server_url)
make_url_available_to_remote calls is_local_machine() and gets the answer 'true'. It then proceeds to call forward_port() which constructs a URL with the host set to 'localhost', overriding the host information in the chef_server_url that was set.
https://github.com/chef/chef-provisioning/blob/master/lib/chef/provisioning/transport/ssh.rb#L146-L162

I found a workaround to this issue for the time being:
with_chef_server Chef::Config[:chef_server_url],
                       :client_name => Chef::Config[:node_name],
                       :signing_key_filename => Chef::Config[:client_key]

machine 'target-machine' do
  action :converge
  machine_options( {
    bootstrap_options: {
      key_name: 'id_rsa'
    },
    ssh_username: 'root',
    transport_options: {
      host: 'nep-infrastructure-1',
      username: 'root',
      ssh_options: {
        keys: ['/root/.ssh/id_rsa']
      }
    },
    convergence_options: {
      ssl_verify_mode: :verify_none,
      chef_version: '12.17.44',
      chef_config: "chef_server_url '#{Chef::Config[:chef_server_url]}'\n",
      install_url: ''
    }
  })
  recipe 'some::recipe'
end

I got bit by this issue when trying to chef-provisioning-ssh from the Chef Server.  Port forwarding wasn't working for me in that environment.


Proposal: Use the net/http/httptrace package

Would you consider a PR that uses the golang 1.7 httptrace package to retrieve request metrics?
No changes on the current features just on the implementation.
I also asked myself if the idea of fine-grained information about the lifecycle of the requests (as an option), won't break the tool's simplicity.

Can you elaborate on the proposal? How would the end result of using that package look like?

@jcorral: Ping?

sorry for the delay, busy days prior to dotGO.
The idea that i had on mind was to create a customized Transport struct pretty much like the second example with the title Tracing with http.Client on the original Golang blog, the tracking the Roundtrip time would be there instead of the hit func, but the Latency would be still copied on the hit func.
Personally i'm not totally happy with that approach as the Transport gets reused, but  i'm not yet proficiency enough with your lib to get a better one.
I think that i would do it just for hacking so feel free to close this issue as a PR would come, but any concern that you may have will be welcome.

@jcorral: Find if there's a tangible and obvious benefit in leveraging this new package and come back to me with your proposal :-)


chore: Renaming Cortex Engines to use semantic naming

@dan-homebrew can you elaborate

dupe of #1168


FSA page Trainsylvania activity refers to City Mall and Suburbopolis

The FSA page Trainsylvania activity refers to City Mall as the start point, and Suburbopolis as the target. These places don't exist on the map (guessing they were from a previous version)

Fixed in a018950e69dd03a41eeca44ade10a6cf050add1d
Thanks Steve for pointing that out, the fix will be pushed to the production website soon.


python311Packages.google-cloud-speech: 2.19.0 -> 2.20.0

Changelog: https://github.com/googleapis/python-speech/blob/v2.20.0/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 235782 run on x86_64-linux 1

4 packages built:

python310Packages.google-cloud-speech
python310Packages.google-cloud-speech.dist
python311Packages.google-cloud-speech
python311Packages.google-cloud-speech.dist


Flickering when row height changes

Describe the bug
When row heights change soon after the component mounts, it can cause on-screen rows to flicker.

Video demo: https://cloudup.com/cm6OIUfnGhP
Reduced test case: https://github.com/inokawa/virtua/compare/main...mattwondra:virtua:bug/flicker-when-height-changes

To Reproduce
Generate components that change their height very soon after mount (e.g. they make a network request and render something based on it). As you scroll them into the overscan, you will often notice rows already rendered on the screen flickering (disappearing and then reappearing).
I've set up a reduced test cases in a branch on my fork, load Storybook and scroll around in the Default story to trigger.
Expected behavior
Components that are already rendered to screen should not flicker at all, even if their height or other components' height changes.
Platform:

OS: MacOS
Browser: Chrome, Firefox, Electron
Version of react: 18.2.0
Version of this package: 0.16.4

Additional context
Thanks for all your work on this package! Let me know if I missed something obvious here or if there's more I can do to help debug.

It's strange that increasing overscan makes the situation worse!
I haven't figured out the reason yet, but in theory, this lib absorbs resizes outside of the viewport with shifting scroll position so huge shift might cause something bad.
Setting min-height to img or item div may suppress the glitch.

I hope it was fixed in 0.17.0.
Thank you for reporting it!

Thank you for your work to address this @inokawa! Unfortunately the changes made in 0.17.0 didn't fix it... I've rebased my forked branch on main so you can verify in Storybook.
I did a little more sleuthing and here's some more clues that will hopefully lead us to a solution:
1. Deferring scroll position jumping fixes this problem (but causes others)
If I update applyJump so all browsers use pendingJump, the problem is solved!
const applyJump = (j: ScrollJump) => {
  pendingJump += j;
};

However it creates at least one regression, with scrolling to the end of the list. You can see this in the "Reverse" story — it gets scrolled past the last item. This happens even without the reverse prop.
2. Safari does not have this bug
I tested in Safari, and both my original branch on 0.16.4 and the current version on 0.17.0 do not have this bug! I noticed that on item resize, diff is always 0 so applyJump never seems to be called.
3. onScrollStop is called twice when the bug happens
I stumbled on this while console.log debugging. When scrolling down and the bug gets triggered, onScrollStop gets called twice. When I dug a little deeper, it's because when scrolling stops for some reason scrollDirection goes from SCROLL_DOWN to SCROLL_IDLE (expected) and then to SCROLL_UP and then SCROLL_IDLE again.
So for some reason it thinks I scrolled back up again, when I didn't.
4. Items outside the viewport are remounted without range changes
This may be unrelated and should be filed as a separate bug, but — on very small scrolls that don't change which items are visible (onRangeChange doesn't fire), a bunch of the off-screen overscan items are re-mounted. This seems like a bug, those components are already mounted and there shouldn't be any need for them to be destroyed and re-mounted when the range hasn't changed.

I didn't notice that. As far as I've tested it again, feels less often but certainly it still happens.
And thank you for your investigation! It may be better to publish a build for debug like react-virtuoso...
I'm not sure it is solvable problem but I try to fix it as much as possible. What I can say for now is:

1 will defer adjusting scroll position so the adjusting itself may be the cause. That mode is a workaround for iOS Safari, which cause serious junk if we didn't defer it.
2 sounds strange... 🤔
3, 4 are expected behavior but it seems that it has side effects for this issue.

If resize happens, virtua adjust scroll position to suppress it. Scroll direction is determined based on scroll events, but adjusted scroll position also included in the scroll events so it's difficult to distinguish between them.
onRangeChange returns range of visible items so it can be different from actually mounted range. The overscaned items opposite to the scroll direction will be unmounted during scrolling to reduce cost. That's similar behavior to react-window.

@mattwondra
Could you try #255 to see if it makes your situation better? Thanks.

@inokawa Eureka! That completely fixes the content flickering on Mac Chrome / Firefox, and confirming Safari still works too! The scrollbar still jitters (see videos below) but that isn't nearly as noticeable. Before/after videos:
main (at ae98ff71514d73d745648e0fa5cd6be2082ced10)
Notice content and scrollbar flickering:
https://github.com/inokawa/virtua/assets/518059/6ddab0ba-11fc-4120-94ab-3fb7fec0e9aa
ignore-scroll-jump
Content is smooth! Just scrollbar flickering:
https://github.com/inokawa/virtua/assets/518059/2a02d2c2-8703-482e-99ab-23699325e29c

Thank you for confirmation! I'll publish this fix in the next release.

Released in 0.17.2.


Add authentication token to Buf actions

Description
Closes #1710.
Uses a token (that we already have set up in a secret) to authenticate requests to Buf.
Run without token: https://github.com/ConduitIO/conduit/actions/runs/10201954995/job/28225018275?pr=1739 (if you check the logs, you'll see warnings about the token)
Run with token: https://github.com/ConduitIO/conduit/actions/runs/10202188145/job/28225742398?pr=1739
Quick checks

[ ] I have followed the Code Guidelines.
[ ] There is no other pull request for the same update/change.
[ ] I have written unit tests.
[ ] I have made sure that the PR is of reasonable size and can be easily reviewed.

Looks like Buf released a new action that unifies all of these actions. I'll convert this PR to a draft.

Also keep in mind that we need the token specifically when generating the proto code in validate-generated-files.yml because we're using remote code generation.

Also keep in mind that we need the token specifically when generating the proto code in validate-generated-files.yml because we're using remote code generation.

I was looking at that too, but interestingly, buf isn't complaining about the token there. I plan to take a closer at that (I mean, it doesn't hurt just giving it the token, but still).


ncdump from the netcdf package does not work

When I try to run ncdump netcdf-file I get the following error message:
*** ncdump: ncopen failed on ioda/test/testoutput/amsua_n19_obs_2018041500_m_put_db_0000.nc4

This appears to happen with any netcdf file including ones known to be readable by ncdump on other platforms.
I am seeing this on AWS RedHat 8 and on MacOS.

@kgerheiser, @climbfuji I just added this issue, and I can't seem to add an estimate nor the epic it belongs to. Am I doing this wrong, or missing permissions somewhere? Thanks!

@kgerheiser, @climbfuji I just added this issue, and I can't seem to add an estimate nor the epic it belongs to. Am I doing this wrong, or missing permissions somewhere? Thanks!

I figured out what the problem is. The hdf4-4.2.15 install also creates a binary called ncdump, and because of the order of how the modules are loaded it finds that one:
heinzell@JCSDA-L-18146:~/scratch/ufs-run/control_c48 [brew-x86_64]> which ncdump
/Users/heinzell/work/spack-stack/spack-stack-1.0.0-rc1/envs/skylab-1.0.0/install/apple-clang/13.1.6/hdf-4.2.15-rpy26yf/bin/ncdump

The netcdf-c install is pretty much complete:
heinzell@JCSDA-L-18146:~/scratch/ufs-run/control_c48 [brew-x86_64]> nc-config --all

This netCDF 4.8.1 has been built with the following features:

  --cc            -> /Users/heinzell/work/spack-stack/spack-stack-1.0.0-rc1/envs/skylab-1.0.0/install/apple-clang/13.1.6/openmpi-4.1.3-hldiips/bin/mpicc
  --cflags        -> -I/Users/heinzell/work/spack-stack/spack-stack-1.0.0-rc1/envs/skylab-1.0.0/install/apple-clang/13.1.6/netcdf-c-4.8.1-ygcbmzc/include -I/usr/local/Cellar/curl/7.83.0/include -I/Users/heinzell/work/spack-stack/spack-stack-1.0.0-rc1/envs/skylab-1.0.0/install/apple-clang/13.1.6/hdf5-1.12.1-jn7p2sk/include -I/Users/heinzell/work/spack-stack/spack-stack-1.0.0-rc1/envs/skylab-1.0.0/install/apple-clang/13.1.6/parallel-netcdf-1.12.2-zworqap/include
  --libs          -> -L/Users/heinzell/work/spack-stack/spack-stack-1.0.0-rc1/envs/skylab-1.0.0/install/apple-clang/13.1.6/netcdf-c-4.8.1-ygcbmzc/lib -lnetcdf
  --static        -> -lpnetcdf -lhdf5_hl -lhdf5 -lm -lz -lcurl

  --has-c++       -> no
  --cxx           ->

  --has-c++4      -> yes
  --cxx4          -> /Users/heinzell/work/spack-stack/spack-stack-1.0.0-rc1/spack/lib/spack/env/clang/clang++
  --cxx4flags     -> -I/Users/heinzell/work/spack-stack/spack-stack-1.0.0-rc1/envs/skylab-1.0.0/install/apple-clang/13.1.6/netcdf-cxx4-4.3.1-jxyenvz/include
  --cxx4libs      -> -L/Users/heinzell/work/spack-stack/spack-stack-1.0.0-rc1/envs/skylab-1.0.0/install/apple-clang/13.1.6/netcdf-cxx4-4.3.1-jxyenvz/lib -lnetcdf_c++4 -lnetcdf

  --has-fortran   -> yes
  --fc            -> /Users/heinzell/work/spack-stack/spack-stack-1.0.0-rc1/spack/lib/spack/env/clang/gfortran
  --fflags        -> -I/Users/heinzell/work/spack-stack/spack-stack-1.0.0-rc1/envs/skylab-1.0.0/install/apple-clang/13.1.6/netcdf-fortran-4.5.4-5cv747y/include -I/Users/heinzell/work/spack-stack/spack-stack-1.0.0-rc1/envs/skylab-1.0.0/install/apple-clang/13.1.6/netcdf-fortran-4.5.4-5cv747y/include
  --flibs         -> -L/Users/heinzell/work/spack-stack/spack-stack-1.0.0-rc1/envs/skylab-1.0.0/install/apple-clang/13.1.6/netcdf-fortran-4.5.4-5cv747y/lib -lnetcdff -lnetcdf -lnetcdf -lm
  --has-f90       ->
  --has-f03       -> yes

  --has-dap       -> yes
  --has-dap2      -> yes
  --has-dap4      -> yes
  --has-nc2       -> yes
  --has-nc4       -> yes
  --has-hdf5      -> yes
  --has-hdf4      -> no
  --has-logging   -> no
  --has-pnetcdf   -> yes
  --has-szlib     -> no
  --has-cdf5      -> yes
  --has-parallel4 -> yes
  --has-parallel  -> yes
  --has-nczarr    -> yes

  --prefix        -> /Users/heinzell/work/spack-stack/spack-stack-1.0.0-rc1/envs/skylab-1.0.0/install/apple-clang/13.1.6/netcdf-c-4.8.1-ygcbmzc
  --includedir    -> /Users/heinzell/work/spack-stack/spack-stack-1.0.0-rc1/envs/skylab-1.0.0/install/apple-clang/13.1.6/netcdf-c-4.8.1-ygcbmzc/include
  --libdir        -> /Users/heinzell/work/spack-stack/spack-stack-1.0.0-rc1/envs/skylab-1.0.0/install/apple-clang/13.1.6/netcdf-c-4.8.1-ygcbmzc/lib
  --version       -> netCDF 4.8.1

This means that you probably want to provide more info in the description and title that this has to do with a conflict with hdf4 binaries. Definitely needs to be fixed in the release, I'll add the corresponding labels. Thinking about a solution ...

@srherbener The same problem for ncgen:
heinzell@JCSDA-L-18146:~/scratch/ufs-run/control_c48 [brew-x86_64]> ls -1 /Users/heinzell/work/spack-stack/spack-stack-1.0.0-rc1/envs/skylab-1.0.0/install/apple-clang/13.1.6/hdf-4.2.15-rpy26yf/bin/
gif2hdf
h4cc
h4redeploy
hdf24to8
hdf2gif
hdf2jpeg
hdf8to24
hdfcomp
hdfed
hdfimport
hdfls
hdfpack
hdftopal
hdftor8
hdfunpac
hdiff
hdp
hrepack
jpeg2hdf
ncdump
ncgen
paltohdf
r8tohdf
ristosds
vmake
vshow

Ok this is a tricky one actually. Lots of installers have tripped over this.
HDF4 made the unwise decision to include their own copy of the netcdf API and tools.
Problem is, it's a very old version of netCDF (long before netcdf4). And it's never been updated. So it will only work on netcdf classic files.
The answer is that HDF4 must be built with --disable-netcdf. This should be done by spack always.
Ironically the opposite situation works well - netCDF has a --enable-hdf4 option which works well for HDF4 SD files. This works because instead of reimplementing HDF4, netCDF uses the HDF4 library and just calls it.

Well, that is a perfect solution, @edwardhartnett - thanks. We'll make this change in release candidate 2.

Closed via https://github.com/NOAA-EMC/spack-stack/pull/208


Remove tab characters from README.md

This PR aims to tidy up README.md by removing tab characters. For example, the alignment looks better in GitHub.
Before
https://github.com/apache/incubator-ranger/blob/master/README.txt
After
https://github.com/dongjoon-hyun/incubator-ranger/blob/14cff7000cdea33eaff211ec51cf5a99d3b36267/README.txt

Hi, @gautamborad
Could you review this PR when you have sometime?
At least, this make GitHub page look better.

Hi Dongjoon,
We generally follow the Raise Apace Jira
https://issues.apache.org/jira/browse/RANGER -> Create RR
https://reviews.apache.org/ flow for contributions to Apache Ranger.
Please create a jira and submit the patch, I would be happy to commit it.
Thanks.
On Fri, Dec 2, 2016 at 4:03 AM, Dongjoon Hyun<EMAIL_ADDRESS>wrote:

Hi, @gautamborad https://github.com/gautamborad
Could you review this PR when you have sometime?
At least, this make GitHub page look better.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-ranger/pull/11#issuecomment-264316516,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJ4DXmSctewnVs2ktlOilKap_plfoVbks5rD0szgaJpZM4K0Vq_
.

--
Regards,
Gautam.

Thank you for review, @gautamborad !
I'll do like that.

Thank you for review and merging.


Error Test Case

Created test cases for errors.go that will show an error message if the test does not pass.

Assigned @LuanTa-CSUN


feat: add ansible-lint

@mason-org/triage notify(Reason::NewPullRequest)
This comment ensures a notification is delivered to maintainers.
 🤖 This is an automated comment.    📖 Source code


gtk 3.16

Add gtk 3.16 support

This would be great! I just tried the install on mac with brew install gtk+3 and got
==> Downloading https://homebrew.bintray.com/bottles/gtk+3-3.16.6.yosemite.bottle.tar.gz
Already downloaded: /Library/Caches/Homebrew/gtk+3-3.16.6.yosemite.bottle.tar.gz
==> Pouring gtk+3-3.16.6.yosemite.bottle.tar.gz
==> /usr/local/opt/glib/bin/glib-compile-schemas /usr/local/share/glib-2.0/schemas
🍺  /usr/local/Cellar/gtk+3/3.16.6: 1298 files, 79M

This issue doesn't describe any specific problem currently. I believe the library should just work with GTK 3.16 and higher.

It just won't have the specific functions from 3.16 and higher versions

The bindings for functions and classes from various versions might be missing, simply saying "3.16" is not useful.

Sorry I was referring to adding the new functions from 3.16


instrumentation-pg loses its scope

What version of OpenTelemetry are you using?
 "dependencies": {
    "@opentelemetry/api": "^1.0.0-rc.0",
    "@opentelemetry/exporter-zipkin": "^0.19.0",
    "@opentelemetry/instrumentation": "^0.19.0",
    "@opentelemetry/instrumentation-express": "^0.15.0",
    "@opentelemetry/instrumentation-http": "^0.19.0",
    "@opentelemetry/instrumentation-pg": "^0.16.0",
    "@opentelemetry/node": "^0.19.0",
    "@opentelemetry/tracing": "^0.19.0"
  },

What version of Node are you using?
v12.22.1

What did you do?
Calling request from 1st server to 2nd server then to query data from DB (postgres)
What did you expect to see?
Expect to see a single span from 1st server to 2nd server then to PG
What did you see instead?
PG trace is in different span altogether

Additional context
I have example repository to reproduce this

instrumentation-express ver 0.15 is not compatible with 0.19 of core and 0.16 of contrib, please use ver. 016

I have the same problem, it's probably a problem with the async_hooks for the node version.
We got the tracing working updating the node version to 14

instrumentation-express ver 0.15 is not compatible with 0.19 of core and 0.16 of contrib, please use ver. 016

Let me try this today and report back. I will also give it a try on node version.

Updating instrumentation-express to ver 0.15 does not resolve the issue, however updating node version from v12 ~ to v14.17.0 does


Native course catalog

JIRA: https://openedx.atlassian.net/browse/MA-1631

@mikekatz please review

@BenjiLee please review

:+1: I'm happy with my glance.


add an inferSchema npm tasks to the API

the default schema will not be compatible with existing databases
(should probably check that, or that the db is empty)
an npm run inferSchema that updates the schema file would be good

Initially addressed in dbde3042e9b7c2dd7cf4dd4f43eea620da2a90f8
Leaving this issue open as we need to add encrypted flag and optional database


Add option to randomise MCQ answer order

Possibly also for quiz... questions get randomised but don't think answers do.

For quiz, mcq and media lesson


Fix travis CI it never builds in it.

Showing linker error right now.
libstmp_process.a(stmp_process.c.o): In function `process_source':
/home/travis/build/ParadoxZero/stmp/stmp/src/stmp_process.c:(.text+0x357): undefined reference to `get_all_lines'
/home/travis/build/ParadoxZero/stmp/stmp/src/stmp_process.c:(.text+0x45d): undefined reference to `get_all_words'
libstmp_process.a(stmp_process.c.o): In function `parse_macro_definitions':
/home/travis/build/ParadoxZero/stmp/stmp/src/stmp_process.c:(.text+0x8e4): undefined reference to `get_all_words'
/home/travis/build/ParadoxZero/stmp/stmp/src/stmp_process.c:(.text+0xb0f): undefined reference to `get_all_words'
libstmp_process.a(stmp_process.c.o): In function `expand_macro':
/home/travis/build/ParadoxZero/stmp/stmp/src/stmp_process.c:(.text+0xdfc): undefined reference to `get_all_words'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [stmp/src/stmp] Error 1
make[1]: *** [stmp/src/CMakeFiles/stmp.dir/all] Error 2
make: *** [all] Error

Works totally fine in my local machine. :(

@gautamkrishnar @jophab Any idea how to fix this? I am stuck here

See the result of a google search
Use a cmake like this: https://github.com/jovial/NNet/blob/master/CMakeLists.txt

The problem was older CMake version for travis. I had reduced the min required to 3.0 from 3.6, so had to put an explicit linking of stmp_process and stmp_utility.


Can't withdraw from metaplex, or import my SOL address to Phantom Wallet

Hi all, summarizing my issue below:

A few weeks ago I placed a bid on an NFT auction paying with SOL on: https://metaplex.helium.com/#/. My wallet setup is Sollet + Ledger Nano S

I lost two auctions so need to return the same site to redeem my bid SOL

When clicking redeem, the tx prompts in sollet, I click approve, but it never makes its way to my ledger. Upon speaking with the Metaplex team, they inspected the console, and determined the issue to be with Sollet. The team suggested I import the same SOL address into Phantom and attempt to redeem that way

Upon trying to import the same wallet address into Phantom, my address aren't showing. The derivable addresses (including the ones I use) in Sollet at m/44'/501'/0'/0' are not showing in Phantom import screen and don't match what is shown in sollet.

Upon speaking with the Phantom team (link) they recommend simply creating a new account, but that wont' solve my problem of redeeming my bid SOL

Any guidance here, on either front? Thank you for your time

For the address, issue, I would expect the addresses shown by phantom and sollet to be the same. When you import to sollet and phantom, double check your derivation path is correct.
For using sollet with metaplex, have you tried recently? Recently chrome broke web usb so sollet had to be updated to work with ledger again. It should work now. Also, double check you are connecting you hardware wallet before connecting to metaplex. I.e., click "Import hardware wallet" on the sollet popup, which shows after you click "Connect".

Hi Armani, thanks so much for the quick reply!
Issue resolved -- I had last tried on Friday morning but the recent update appears to have fixed the issue! Thank you.


I can't slow down, I'm aiming too fast, sometimes I get lost where do I adjust it?

I can't slow down, I'm aiming too fast, sometimes I get lost where do I adjust it?

Updated, try to play with mouse_sensitivity in options.


[Lona Studio] Display SVG files when selected within the file navigator

Summary
Currently Lona Studio displays some image files, e.g. PNG files, when selected in the file navigator. However, it doesn't display SVG files, which it really should, since it handles them elsewhere correctly.
Here's what the image viewer looks like for PNG files:

And here's what it currently looks like for SVG files:

We want to use the same viewer as the PNG for SVG also.
Proposed Implementation
I think we want to add svg to the list of supported file types:

Then when we read the data for the ImageDocument
https://github.com/airbnb/Lona/blob/0571d6aa7c7796073eece13aa6a43acdb15840c7/studio/LonaStudio/Documents/ImageDocument.swift#L45 we should render the SVG file to an image
https://github.com/airbnb/Lona/blob/0571d6aa7c7796073eece13aa6a43acdb15840c7/studio/LonaStudio/Models/SVG.swift#L416
We might need to choose an arbitrary size for the image. We could use the viewBox of the svg to attempt to determine an "intrinsic" size of some kind, but that isn't really reliable. SVGs are designed to scale to any size, so they don't really have an intrinsic size, although viewBox is sometimes used like that. Maybe play around with it and see what looks best?

If you want to try using the viewBox, it's a little more effort, but you can access it by first generating an SVG.Node before rendering an image, e.g. here https://github.com/airbnb/Lona/blob/0571d6aa7c7796073eece13aa6a43acdb15840c7/studio/LonaStudio/Models/SVG.swift#L241

I want to take this issue as well.

I'm not sure, but those SVGs most likely use features that Lona's very primitive SVG renderer doesn't support yet. E.g. the firefox one might have gradients, but we can only draw solid colors for now. So I think what you have looks good.


Missing Declared

Type: Missing
Summary:
Missing Declared
Details:
GitHub POM indicates license is Apache v2
Resolution:
https://github.com/codehaus/jettison/blob/master/pom.xml
Affected definitions:

jettison 1.1

:+1:  and FWIW, this would also would be a "declared" license in my book as it was also at the time
https://github.com/codehaus/jettison/blob/jettison-1.1/src/main/resources/META-INF/LICENSE


Question: v1.7 with Reanimated 3

Hi there @Skipperlla !
Just wondering if you've encountered the following problem while you were migrating to v2: from Reanimated 2.14 to Reanimated 3. My issue is that after updating to Reanimated 3, if I use your lib on 1.x there is a little bit of flickering / lagging (with 10-20% chance) when I start to drag a card. The whole card jumps from the current dragged position back to a couple of millisec before and then back to the recent/valid dragged position, then continous its journey properly...
This is 100% due to the reason I updated to Reanimated 3 (to get rid of useAnimatedStyle which caused memory leak), I made no other changes. I also tried to update react-native-gesture-handler and mimic your recent code from v2, but this flickering / lagging is still there.
 I am just wondering how can I solve that without restructuring my codebase to be able to use v2 if that's possible.

Turns out the issue is that recent Reanimated versions are just laggy by default. When I rolled back to 3.6.3, the problem has gone. On latest version(s) work on the JS thread could lock up the animation causing flickering.
These seem to be relatated:
https://github.com/software-mansion/react-native-reanimated/issues/6102 with https://github.com/software-mansion/react-native-reanimated/issues/6102#issuecomment-2163825540
https://github.com/software-mansion/react-native-reanimated/issues/5816
I have seen that @Skipperlla made amazing optimizations recently with rn-swiper-list on v2 much work on the UI thread / with sharedValues. I'd be curious if that was necessary because of the weird new laggyness or it was an independent improvement. Anyway, my problem is that even with these optimizations the JS part could cause problems, if so, revert back to older Reanimated 3 versions until they fix it.


Add german translation

Hey @coavins, figured I'd help you out a bit since I want to see this mod grow and expand. If you need help with anything, let me know.

Awesome, thanks! I look forward to merging it.

I'd say it's ready for merging. I'm gonna read up on how to define a new model, then perhaps try add either the G36C or a FN SCAR.

Thank you for your contribution!
FYI, it looks like you might want to make sure that the email address on your commits is added to your Github account to ensure that your contributions are properly attributed to you.


Fixed for DragonFly

Running libc-test: PASSED 3426 tests
Squashed commit of the following:
commit 1a7ee714db34f17abd33dc9262d3e10275eec68d
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 13:30:56 2016 +0100
Fix RLIM_POSIXLOCKS ->  RLIMIT_POSIXLOCKS

commit 09c49a97ebebf087486659ef8277610d99e5c7b3
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 13:29:24 2016 +0100
Ignore signedness check for uuid_t on DragonFly

commit aab4d11f59917686280c271683bf00ff34c8040d
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 13:23:21 2016 +0100
Move FreeBSD-only function into freebsd/mod.rs

commit 9921f030b103dbccb37930ab1d64cf1dd587bd48
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 13:21:42 2016 +0100
Move POSIX_FADV_* to freebsd/mod.rs

commit 2921c2db1e3d0314375aa371936bd227cc6c6e2a
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 13:20:11 2016 +0100
Fix signedness of blksize_t for DragonFly

commit 65e817baee9e01d2d7c86c6202c63ee46d218914
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 13:19:02 2016 +0100
Fix Q_{GET,SET}QUOTA for DragonFly

commit a0d2d63ef88206d321222140ae6b3d92c93b51bd
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 13:17:27 2016 +0100
Fix RLIMIT_* for DragonFly

commit d04a1600a7c66a792a481e1524a1652234a69939
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 13:12:09 2016 +0100
Fix ELAST for DragonFly

commit d120b9278426a76ee106e91e6c999885c1f5c7f4
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 13:10:28 2016 +0100
Fix F_GETLK, F_SETLK, F_SETLKW for DragonFly

commit 963f7da270a14f4d12ea1a52301e363ce745c897
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 13:08:51 2016 +0100
Fix O_CLOEXEC for DragonFly

commit f4d6c9d5991d690c7cb4460790a8e37e713bc034
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 13:07:18 2016 +0100
Fix RAND_MAX for DragonFly

commit ba48336da7be613a49702ad9de445ab3850ebb7c
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 13:04:48 2016 +0100
Fix statvfs for DragonFly

commit 9ae480c60a7d77b31a17d34320464f4179e40a4a
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 12:51:47 2016 +0100
Fix fd_set for DragonFly

commit a15e027838288c4980371c503252cca7e32356c0
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 12:42:24 2016 +0100
Fix all remaining issues on DragonFly

Missing functions and missing constats.

commit 3966e4fce0cb81bd0b3ed8cdf50611e6982f7767
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 12:27:14 2016 +0100
Use a macro instead of a constant.

When using a constant, the libc-test thinks this constant
exists as an C equivalent.

commit 9b5659aaf54419f317250cb3a4692a1c14fdbc33
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 12:21:01 2016 +0100
Use a constant in utsname

commit 50484eda3c978a9c0a9652f6fc619c41ad349c2d
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 12:17:55 2016 +0100
Fix struct utsname

commit 832e94248fabc91574d6d42630168da3542c153f
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 12:07:08 2016 +0100
DragonFly has different stat, dirent, clock_t, ino_t, nlink_t, blksize_t

commit f3152a369d75ae8c1558afa5a59aa55e33b33ec6
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 11:52:54 2016 +0100
Move DragonFly related stuff into dragonfly/*

Replicate x86_64.rs from FreeBSD. Need some twists.

commit 9fe35124064aa92303171d019004df119f948223
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 11:49:38 2016 +0100
Move FreeBSD code under freebsd/*.

Next commit will replicate some of the architecture dependent stuff
for DragonFly.

commit e91983df8deb14004f7a0fe47878f0e4eb31198d
Author: Michael Neumann<EMAIL_ADDRESS>Date:   Sat Feb 20 11:44:25 2016 +0100
struct utsname has a different size on DragonFly

Nice! Thanks @mneumann! Looks like there's some CI failures as well?
If you're interested, I'd be totally fine adding a dragonfly builder on Travis via QEMU (there's some instructions in the ci folder) as well!

@alexcrichton : Thanks for the suggestions! Regarding CI, I am pretty busy with my thesis atm, but once I finish, I will take a look. This is definitively something we want to have!


need the default port stuff at the top of web console install, too

fixed with new installation guidelines page.


Support building for Catalyst on the Mac

When building for Catalyst on the Mac, canImport(AppKit) is true, so you also need to check for !targetEnvironment(macCatalyst).

Don't ask my why canImport(AppKit) evaluates to true in this situation - seems wrong to me - but currently it does!


Update build.gradle (API levelled up to Android 10 and SDK version 30 )

This PR closes #83 on merging

@Thesmader
Approve, when free.


[core] Remove notify pattern for checkpoint state accumulation

Description
When calling StateAccumulator::accumulate_epoch, there should never be a case where a previous checkpoint has not already been accumulated. This is because we accumulate the epoch only in 2 places:

Checkpoint builder, as needed to generate the root state hash in order to craft the final checkpoint summary. Checkpoint builder, in order to have sent a proposal for this checkpoint, must have locally executed all previous checkpoints. Since checkpoint accumulation blocks completion of checkpoint execution, we must have accumulated all previous epochs.
Checkpoint executor, for the final checkpoint of the epoch. Since executed checkpoints are processed sequentially, and checkpoint accumulation blocks the full processing, we must have executed and accumulated all previous checkpoints before this call.

Due to the above, we can remove the notify pattern here and instead panic to fail loudly if this invariant is ever violated.
Test Plan
Existing simtests should cover this

If your changes are not user-facing and do not break anything, you can skip the following section. Otherwise, please briefly describe what has changed under the Release Notes section.
Type of Change (Check all that apply)

[ ] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

Invalid assumptions here


port http-client widl interface to smithy

fixed - now in wasmcloud/interfaces/httpclient
commit #dbe5f6724455a4402c6cd745a3889e38c8ea861d


Added API-keys to NIBittensorLLM

Description: Adding Individual level access in NIBittensorLLM
Tag maintainer: @Kunj-2206
Maintainer responsibilities:
Models / Prompts: @hwchase17, @baskaryan

Maintainer responsibilities:
Models / Prompts: @hwchase17, @baskaryan
Can you please merge this PR since its passed all the checks.


build: update to use go1.18 and upgrade actions

upgrade the actions and use go1.18 for build

Hi @chenrui333 , Can you pls reopen the issue against dev branch?

Done.


Break up deployment files and into pods

This PR updates the overall structure of how deployments work. Previously there was a single deployment file with one kustomize directory and all containers in a single pod.

Breaks up into three pods for celestia, sequencing, and geth
Alters directory structure and deployment files to match the pod structure
just commands updated to reflect new structure
Created a new account for testing in geth, added private key to repo, and documentation on how to change
Added note that docker must to running to start running containers

Note: before merge need to update conductor and sequencer-relayer to new tagged releases.

@joroshiba nit: lots of files w/o newline endings


Ethan/close modal fix

Made it so that if you click outside the modal it will close the modal for task-pop-up on calendar.

Closed as addressed in https://github.com/cse110-sp24-group35/journal/commit/f57e117fa42237a8230bae50a0b97b3add76bc54


Add TM Dashboard URL to slack summary

What this PR does / why we need it:
Adds a URL pointing to the TM Dashboard UI to the slack summary.

Fixed, please review/approve


[Job Launcher] Create an e2e tutorial for hCaptcha job types

Description
Create an e2e tutorial for hCaptcha job types in notion.
Motivation
Anyone should be able to launch hCaptcha job types from scratch.
Implementation details

[ ] How to create hCaptcha <JOB_TYPE_NAME> job type via JL
[ ] How to create bucket on GCS
[ ] How to upload images to bucket
[ ] How to create ground truth file and upload it to the bucket
[ ] How to create a job via UI
[ ] How to create a job via API
[ ] How to topup JL balance with crypto

Launch Jobs
Useful tutorials


Replace discontinued ArcGIS sample Feature Service with open data service

Replaces the discontinued sampleserver1 service used in the ArcGIS REST Feature Service example with an open data service.
https://deploy-preview-14253--ol-site.netlify.app/en/latest/examples/vector-esri.html

As with the original example the styles are copied from the Arcgis layer Drawing Info.  It might be better to fetch the layer definition json and create the styles dynamically.

Was there a historical reason for using a loader function and jquery?  It would work with just a url function and format.

Was there a historical reason for using a loader function and jquery? It would work with just a url function and format.

Yes, that example was there before the url function. Please update to use a url function.

Replaced by #14296.


[Create New Issue]: HTML Lists

Description
About Lists in HTML
Domain
Frontend Dev HTML/CSS/JS
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

/assign

@shubh045 I wanted to contribute to this issue if it is not assigned to anyone else.

@Rutumbhara if you want to contribute to this topic in other format than document then maybe you can do, as somebody else's work for this topic in document format has already been merged, and maybe that is why they are not merging my pull request

Ok


Fix push comment url

Signed-off-by: Gong Su<EMAIL_ADDRESS>

Jenkins Linux s390x Build #284 [push] Merge pull request #25 f... started at 03:18

Jenkins Linux amd64 Build #53 [push] Merge pull request #25 f... started at 02:18

Jenkins Linux s390x Build #284 [push] Merge pull request #25 f... passed after 38 min

Jenkins Linux amd64 Build #53 [push] Merge pull request #25 f... passed after 42 min


Android - Chat - New chat shows time zone.

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: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4434326
Issue reported by: Applause - Internal Team
Action Performed:

Launch app (used gmail)
Tap fab --- start chat
Enter<PHONE_NUMBER>/+19894706461 (use non-existing local number
From suggestions, select the contact
Tap on the header

Expected Result:
New chat must not show time zone.
Actual Result:
User is not part of same private workspace/domain nor had sent a DM, yet time zone showing in details page.
New chat shows time zone.
Workaround:
n/a
Platforms:

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

[x] 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/93399543/b69ca6fb-420b-49b0-9a3a-9e0a51986716
View all open jobs on GitHub

We think that this bug might be related to #vip-vsb

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

@kbecciv This is not a bug. We show timezones by default so people are aware of what time it is for the person they attempt to message. This is not personal information, and only provides a very broad location of where that person is at the moment the message is sent.
Going to close this 👍

@Krishna2323 can you clarify what you mean by "the composer"? Sorry for the confusion on my part!

@Krishna2323 I did some additional testing on this, and realized the "composer" refers to the text box — so all good there.
However, I am surprised that we would hide that information, as it is not private by any means. I'm going to bring this to the room to discuss further and will follow up 👍

Post in #VIP-VSB is here

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/piyushdesai

Thanks for your patience! So after a deeper discussion with @puneetlath and @quinthar, we found that the scope of the issue is different that we originally thought.
We're showing timezones for unvalidated accounts per this:

I've adjusted the main comment above (just a heads up @kbecciv) and changed this to reflect that it also shows in iOS, as well as Android 👍
We would like to hide the timezone for unvalidated accounts to maintain consistency, as we do above the compose tool.
@Krishna2323 feel free to adjust your proposal to reflect this (if needed) and we can get this reviewed. Thank you!

@GandalfGwaihir of course!

@mollfpr any feedback for the proposals above? Thanks!

Thanks, @tienifr for another perspective on how our data could be exploited. However, we should run through all our implementations if we try to avoid that. So I try to make it simple and work for now.
I like the proposal from @Krishna2323 when we do the same things as the composer on how to show the timezone on the composer. So it looks good to me!
🎀 👀 🎀 C+ reviewed!

@GandalfGwaihir Do you mind explaining the issue for that?

@GandalfGwaihir I don't think it will be any different from the current function. Do you have any issue in mind with canShowReportRecipientLocalTime?

@mollfpr @tienifr @Krishna2323 — do we have an update on the proposals? I see side conversation happening around the best avenue forward, and wanted to get clarification on where we're at in that process. Thanks!

From looking at the slack thread https://expensify.slack.com/archives/C066HJM2CAZ/p1710859087413049 (thanks @CortneyOfstad for starting that!), I understand that is by design:

Starting a new chat with an account that doesn't exist (unvalidated account), make it consider that account as "known", which means we will get personal details like "timezone" from the backend.
Seems like there is a front-end decision about not showing the timezone for unvalidated accounts

About @tienifr concern, since apparently returning the timezone is not a "leak of personal details" but it is by design, we end up having to decide if:

We want to stop sending timezone from the backend for unvalidated accounts because it is not used anyway, or
We want to make the decision in the frontend based on the account being validated/unvalidated

I don't think one option is better than the other, so I'll go with lets fix it in the frontend because we are already doing that in one place, we have a proposal, and investigating what needs to be done instead in the backend may be costly and not worth it.

@mollfpr , I think what @GandalfGwaihir is saying here does sound like a problem and canShowReportRecipientLocalTime may not be the right place for checking this.
For the composer case we use canShowReportRecipientLocalTime because the report type plays a role on deciding if we want to show or not the timezone, but in the profile page, we always want to show it unless it is unvalidated. It feels like we shouldn't use that function.

@GandalfGwaihir why are you proposing ReportUtils.getReportRecipientAccountIDs(report, accountID); to get an accountID instead of just using the accountID that we have in the variable const accountID = Number(route.params?.accountID ?? 0);

I might have overlooked the issue of using canShowReportRecipientLocalTime; the function seems intended for the chat report only and used over the composer.
@aldo-expensify We can go with @GandalfGwaihir's proposal for simplicity.

@Krishna2323 I don’t have any case in mind, but since the issue is on the profile detail page, it is not necessary to have a check for a report.

Thanks @Krishna2323 for checking, and sorry for the slow replies, I'm quite busy with other high priority stuff for the moment. I'll assign @GandalfGwaihir then.

@GandalfGwaihir any update on the PR progress? Thanks!

@mollfpr — PR is ready for your review — thanks!

Payment is set for tomorrow, so not overdue!

[@mollfpr] The PR that introduced the bug has been identified. Link to the PR:
[@mollfpr] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:

No offending PR.

[@mollfpr] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:

The regression step should be enough.

[@mollfpr] Determine if we should create a regression test for this bug.
[@mollfpr] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Start a new chat with the invalidated account (e.g.,<PHONE_NUMBER>/+19894706461)
Open the profile of the account
Verify the local time of the account is not showing
Open a chat that already had a conversation
Open the profile of the account
Verify the local time is showing
👍 or 👎

@CortneyOfstad Could you create the payment summary? Thank you!

Payment Summary
@GandalfGwaihir — paid $500 via Upwork
@mollfpr — to be paid $500 via NewDot

$500 approved for @mollfpr


Fix Spring Data connector to set multiGet (MGET) commands to slave in…

…stead of master when configured to do so #2656

Thanks for the contribution!


mysql error in creating table "room"

OS: Mac OS
mysql version: mysql  Ver 8.0.14 for macos10.14 on x86_64 (MySQL Community Server - GPL)

Create room command fails with error :

ERROR 1064 (42000): You have an error in your SQL syntax

Tip: Providing an sql dump is easy and convenient.

Screenshot:

Can you please try below command
CREATE TABLE rooms
(
id              INT unsigned NOT NULL AUTO_INCREMENT,
location            VARCHAR(150) NOT NULL,
owneremail           VARCHAR(150) NOT NULL,
guests           INT NOT NULL,
available           TINYINT NOT NULL,
price           INT NOT NULL,
description           VARCHAR(150) NULL,
wifi           TINYINT NOT NULL,
microwave           TINYINT NOT NULL,
safeCloset           TINYINT NOT NULL,
PRIMARY KEY     (id));

Thanks @ameyarangal , it worked.


Getting issues with 0.3.8

Seeing build issues with latest version
ReferenceError: document is not defined
        at Object.<anonymous> (/home/cat/ecapp/node_modules/react-dnd-touch-backend/dist/Touch.js:72:4)
        at Module._compile (module.js:570:32)
        at Module._extensions..js (module.js:579:10)
        at Object.require.extensions.(anonymous function) [as .js] (/home/cat/ecapp/node_modules/babel-register/lib/node.js:152:7)
        at Module.load (module.js:487:32)
        at tryModuleLoad (module.js:446:12)
        at Function.Module._load (module.js:438:3)
        at Module.require (module.js:497:17)
        at require (internal/module.js:20:19)
        at Object.<anonymous> (/home/cat/ecapp/components/toolbar/CustomColumns/ReorderColumns.jsx:8:1)
        at Module._compile (module.js:570:32)
        at loader (/home/cat/ecapp/node_modules/babel-register/lib/node.js:144:5)
        at Object.require.extensions.(anonymous function) [as .jsx] (/home/cat/ecapp/node_modules/babel-register/lib/node.js:154:7)
        at Module.load (module.js:487:32)
        at tryModuleLoad (module.js:446:12)
        at Function.Module._load (module.js:438:3)
    Waiting for the debugger to disconnect...

this is only meant for client side

Same code works fine with 0.3.7 though. Need to dig a little more.

Can you tell us what is the use case? It shouldn't be throwing this error.

Ok, I got it. document is being called at the library instantiation. I'll do a PR fixing it.

Thanks @JoaoMosmann 👍

0.3.9 published, should address this issue


[SR-1528] Swift compiler requires closures without parameter lists to reference all arguments

Previous ID
SR-1528

Radar
rdar://problem/13254540

Original Reporter
erica (JIRA User)

Type
Bug

Environment
Swift 2.2

Additional Detail from JIRA

Votes
10

Component/s
Compiler

Labels
Bug

Assignee
None

Priority
Medium

md5: 2ed8141c3cd057578dc20e6b58317765

is duplicated by:

SR-5695 Error defining closure with more than 3 parameters
SR-6612 Contextual closure type expects N arguments, but <N was used in closure body.

relates to:

SR-3639 Surprising meaning of anonymous closure parameters if not all are used
SR-11389 Confusing error message when missing an overload

Issue Description:
Swift closures that do not explicitly declare an internal parameter list must reference all arguments using implicit $n shorthand names. If they do not, Swift complains that the contextual type for the closure argument "expects n arguments, which cannot be implicitly ignored." This requirement diminishes the efficacy of Swift's $n syntactic sugar. Eliminating the requirement means:

{} becomes a valid 'noop' closure in any context requiring a Void-returning closure.

Implementations can discard unnecessary code cruft and streamline their minimum implementation from { _(, _)* in } to {}.

{ expression } becomes a valid closure in any context requiring a return value. The expression can offer a simple expression or literal, such as { 42 }.

The closure can mention some of its parameters without having to mention all of its parameters.

All the following closures should be valid and compile without error or warning:
{{let _: () -> Void = {}
let _: (Int) -> Void = {}
let _: (Int, Int) -> Int = { 5 }
let _: (Int, Int) -> Int = { $0 }
let _: (Int, Int) -> Int = { $1 }
doThing(withCompletion: {})
let x: (T) -> Void = {}}}
Chris L writes: "I consider this to be an obvious bug in the compiler. I don’t think it requires a proposal. Unfortunately it is non-trivial to fix…"

Just found an even sillier part of this.
If you write:
func doSomething((T, Int) -> Int) {}
You've gotta use both params to use that closure
But if you write it as:
func doSomething(((T, Int)) -> Int) {}
You now have a tuple (note the extra pair of parenthesis). Code that uses both arguments will keep working as swift will transparently turn that tuple into the arguments of the closure, no problem. If you then want to use only the first argument, you can refer to it as $0.0, treating the tuple as a tuple, and it'll work too, and won't complain.
 Can we fix this please?


JsonInputFormatter and JsonOutputFormatter consistancy

JsonInputFormatter
JsonOutputFormatter

On JsonInputFormatter the CreateJsonReader and CreateJsonSerializer method are public and virtual.
On JsonOutputFormatter the CreateJsonWriter and CreateJsonSerializer methods are private.

Should these methods be consistent between input and output formatters?

JsonOutputFormatter implements IJsonOutputFormatter
JsonInputFormatter doesn't implement an interface.

Is IJsonOutputFormatter required? It doesn't have any methods and is only used in one place.

Let's deal with the IJsonOutputFormatter issue separately: https://github.com/aspnet/Mvc/issues/2715.
We should go ahead and make CreateJsonWriter and CreateJsonSerializer public.

4a4b8ec87e56db88c1192f33dc755ecd67d85cd4


Allow Adjusting Default Service Type for Application Services

When deploying clusters in GKE, services that sit behind a GCP LB for the Ingress object require a non-ClusterIP type Service. Are there plans to allow the CRD for the Applications to support a custom Service Type rather than a hard coded ClusterIP type? If not can we issue PR's to address this?
This is the related issue on the helm chart that deploys the operator.
https://github.com/VictoriaMetrics/helm-charts/issues/163#issuecomment-1989707794

Hello!
What about using the serviceSpec? It allows having an extra customized service.

I was thinking of new boolean flag, which could be added to the serviceSpec - useAsDefaultService: true.
In this case, additional service must be deleted and all properties of it applied to the default service.
This change may require service recreation - if any immutable fields for it changes.

Must be fixed at v0.43.0 release.
Operator allows to modify exist service with serviceSpec if useAsDefault option is set to true
---
apiVersion: operator.victoriametrics.com/v1beta1
kind: VMCluster
metadata:
  name: example-service-change
spec:
  retentionPeriod: "4"
  replicationFactor: 2
  vmstorage:
    replicaCount: 2
    containers:
    - name: my-side-car
      ports:
      - name: extra-port
        containerPort: 8055
    serviceSpec:
      # expose additional port with default service
      userAsDefault: true
      spec:
         ports:
         - name: extra-port
           port: 8055
    storageDataPath: "/vm-data"
    storage:
      volumeClaimTemplate:
        spec:
          resources:
            requests:
              storage: 10Gi
  vmselect:
    replicaCount: 2
    cacheMountPath: "/select-cache"
  vminsert:
    replicaCount: 2
    serviceSpec:
      metadata:
        annotations:
          my-cloud-provide-annotation: value
      userAsDefault: true
      spec:
       type: LoadBalancer


I can't log in AssertionError

I also had a ClientError with the same response, but it was resolved when I replaced the proxy. Could it be that it's about the account?
During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python311\Lib\site-
packages\instagrapi\mixins\private.py", line 313, in _send_private_request
    response.raise_for_status()
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python311\Lib\site-
packages\requests\models.py", line 1021, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://i.
instagram.com/api/v1/challenge/

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python311\Lib\site-
packages\instagrapi\mixins\challenge.py", line 76, in challenge_resolve
    self._send_private_request(challenge_url[1:], params=params)
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python311\Lib\site-
packages\instagrapi\mixins\private.py", line 344, in _send_private_request
    raise ChallengeRequired(**last_json)
instagrapi.exceptions.ChallengeRequired: challenge_required

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\Users\Administrator\Desktop\inst\script\insta_bot.py", line 132, in m
ain
    cl = auth(login, password, proxy)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Administrator\Desktop\inst\script\insta_bot.py", line 35, in au
th
    cl.login(username=login, password=password)
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python311\Lib\site-
packages\instagrapi\mixins\auth.py", line 434, in login
    self.login_flow()
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python311\Lib\site-
packages\instagrapi\mixins\auth.py", line 170, in login_flow
    check_flow.append(self.get_reels_tray_feed("cold_start"))
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python311\Lib\site-
packages\instagrapi\mixins\auth.py", line 247, in get_reels_tray_feed
    return self.private_request("feed/reels_tray/", data)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python311\Lib\site-
packages\instagrapi\mixins\private.py", line 459, in private_request
    self.challenge_resolve(self.last_json)
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python311\Lib\site-
packages\instagrapi\mixins\challenge.py", line 79, in challenge_resolve
    return self.challenge_resolve_contact_form(challenge_url)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\Administrator\AppData\Local\Programs\Python\Python311\Lib\site-
packages\instagrapi\mixins\challenge.py", line 184, in challenge_resolve_contact
_form
    assert result.get("challengeType") in (
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: {'message': 'Please wait a few minutes before you try again.', '
require_login': True, 'status': 'fail'}

same here

any1 solved it?

@adw0rd give us a hint, please

@adw0rd give us a hint, please

time.sleep(600)

time.sleep(600)

So i tried this and earlier even 1 week+ of pause, but it doesn't helps — i constantly get "AssertionError: {'message': 'Please wait a few minutes before you try again.', 'require_login': True, 'status': 'fail'}" when trying to get timeline feed. To be more precise, at first i get default 'login_required', my script does cl.relogin() and fails it with this AssertionError message. If i then try to relogin again and again, i'm only get this AssertionError.
I have two theories:

something wrong with my saved session file
my proxy

Сould any of this be the reason?

Instagram asks you to wait "Please wait a few minutes before you try again", wait exponentially and after a while it will unblock you


Add expo support

Feature request
Add expo support.
Followed install instructions on README (except linking) to install it on a sample app, and I got this error:

cc @EvanBacon

It would be good it this would add rn-web compatibility

@renanmav have you managed to make this library work with an expo project?

@brunoaduarte nop :(

Use expo-blur https://docs.expo.io/versions/latest/sdk/blur-view/ it has web support


[Issue]: WG not sending query params when statusCodeUnions is true

Description
We noticed an issue where WunderGraph (WG) does not send query parameters to the API server when statusCodeUnions config is enabled in openApi().
For a more detailed explanation with steps to reproduce please take a look at this repo's README: https://github.com/znikola/wg-query-params-problem
Reproduction

git clone git@github.com:znikola/wg-query-params-problem.git
npm ci - install dependencies
npm run build - cleans and generates wundergraph files
npm run start - starts the WG server in debug mode
npx ts-node good.ts - runs a script which demonstrates WG was able to successfully send the query parameters and resolve the API server's response. In the WG's logs, we can see GET /Wizards?FirstName=Tom&LastName=Riddle HTTP/1.1 confirming the query params have been sent.
npx ts-node bad.ts - runs a script and demonstrates a case where WG was not able to send query params. This can be confirmed in the WG's logs where we can see GET /Wizards HTTP/1.1 w/o query params. Because there are no query params, API server responded with all wizards, which can be seen in the WG's logs.

Thanks a lot for the reproduction.
We will no longer support openapi v1 in the future and recommend switch to introspect.openApiV2 which will most likely also resolve this issue.


Automatically install tools when cd to a folder with config files

Is there a way to automatically install tools (node, ruby, python, etc) when cd to a folder with .rtx.toml or .nvmrc or other configuration files? something like this in nvm.
If it's not possible to do it now, do you think it's a good idea to add such a feature?

I believe you can set RTX_MISSING_RUNTIME_BEHAVIOR=autoinstall, however I've removed this from the documentation and I'm unsure if it's something I want to continue supporting forever.

thanks @jdx!

I'm unsure if it's something I want to continue supporting forever

is there a reason for this? seems like a useful feature 🤔

--yes is a more elegant solution to most of what RTX_MISSING_RUNTIME_BEHAVIOR did—though it doesn't handle this exact use-case.

RTX_MISSING_RUNTIME_BEHAVIOR just adds a lot of complexity to the codebase for little benefit when --yes is available

with the new not_found handler I feel this probably isn't necessary anymore


Add ability to update and delete notes

Currently Deer doesn't allow to edit/delete notes. Add ability to edit/update notes.

Closed for awhile since current development is not at this stage


Natural Selection 2

Project link: https://store.steampowered.com/app/4920/Natural_Selection_2/
Project license: Proprietary
Does it work on 64-bit only Linux: YES
Is source code available?: NO
Is source code stored in Git?: NO
List of Steam AppIds of supported games:

https://steamdb.info/app/4920/

Additional information
Natural Selection 2 is an Aliens vs Marines themed FPS/RTS game. Its Linux support was dropped in 2019;
https://unknownworlds.com/ns2/a-note-to-our-linux-users/
Later on, due to user request developer put an obsolete [Linux] branch for those want to play outdated version.
https://steamcommunity.com/app/4920/discussions/0/2692512878719460182/?tscn=1568973412#c1628538005512564029
It looks like recent launch config update has broken the Linux launch option that looks for ns2.exe.
https://steamcommunity.com/app/4920/discussions/1/2994296961836681550/
https://steamdb.info/app/4920/history/?changeid=10234342
I wonder if Luxtorpeda utilized to launch the outdated Linux version?

The way Luxtorpeda interacts with Steam is by setting itself up as a compatibility tool. Because of that, it downloads whatever the Windows branch of the game is.
Because of that, unless Natural Selection 2 provides the Linux binaries in the Windows depot as well, then luxtorpeda wont work for it. You might be able to do something to make it work by changing the Steam launch options to point it in the right direction.

The way Luxtorpeda interacts with Steam is by setting itself up as a compatibility tool. Because of that, it downloads whatever the Windows branch of the game is.
Because of that, unless Natural Selection 2 provides the Linux binaries in the Windows depot as well, then luxtorpeda wont work for it. You might be able to do something to make it work by changing the Steam launch options to point it in the right direction.

Please feel free to comment if there's something else you feel luxtorpeda can do here. Closing for now.

Please feel free to comment if there's something else you feel luxtorpeda can do here. Closing for now.


Datagrid: Single row action is not visible when data is loaded asynchronously

Select one ...  (check one with "x")
[ x ] bug
[ ] feature request
[ ] enhancement

Expected behavior
When the data for the Datagrid is loaded asynchronously (i.e. Observable), single row action should be visible on each row
Actual behavior
When the data for the Datagrid is loaded asynchronously (i.e. Observable), single row action is hidden on each row (action column is not rendered).
When you click on any of the Datagrid column header, then the single row action is rendered for each row.
Reproduction of behavior

Include a link to the reproduction scenario you created by forking one of the Clarity Plunker Templates:

You can reproduce the behavior here:
https://plnkr.co/edit/Lb2VilKWu08GEZ6r4B2k?p=preview
(Note: it's reproducible on Safari ; on Chrome, the Datagrid content does not render)
Environment details

Angular version: 4.x

Clarity version: 0.9.12

OS and version:

Browser: Chrome 59 | Safari 10.1.1

Duplicate of #744, the fix is coming in any time now!


Plot background colour

Hey, how can we change the black background colour of the plot to white?

Line 103 k to w


Migrate-Aadds does not work with classic virtual network

Hi
I used the script Migrate-Aadds to upgrade Azure Domain Service from Classic to ARM.
The issue is that script does not work with Classic virtual network as the command used in the script is for ARM.
the command in the script is
 $vnet = Get-AzVirtualNetwork -Name  $VirtualNetworkName -ResourceGroupName $VirtualNetworkResourceGroupName -ErrorAction SilentlyContinue
This will never return the classic virtual network .A command like this should be used
$vnet = Get-AzResource -ResourceName  $VirtualNetworkName
The same issue is then for the Subnet
$subnet = Get-AzVirtualNetworkSubnetConfig -Name $VirtualSubnetName -VirtualNetwork $vnet -ErrorAction SilentlyContinue
as this will never return the subnet for classic virtual netwrork.
The only way to upgrade Azure Domain Service from Classic to ARM with classic virtual network was
1/ Run the Migrate-Aadds in preparation mode.
2/ run migration of classic virtual network to ARM
3/ run the Migrate-Aadds  with commit.
The only cavity with this is that you cannot rollback, if there are issues.
Kind regards,
Ivan

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

ID: 39deaffe-a3b4-7909-0e9e-10e14f766bf4
Version Independent ID: edb0ea30-964d-54c6-9589-f233286a8816
Content: Migrate Azure AD Domain Services from a Classic virtual network
Content Source: articles/active-directory-domain-services/migrate-from-classic-vnet.md
Service: active-directory
Sub-service: domain-services
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@vremeni4 Please help with the link of document on which above document feedback request is created.
Under this repository we want to make sure any issue is linked to a doc so we can help others that may be having the same issue.

Sure this is the link
https://docs.microsoft.com/en-us/azure/active-directory-domain-services/migrate-from-classic-vnet

@vremeni4 This script has been updated by the product group now and the errors should not be seen. In case you still see any error , please send open a ticket with Microsoft support . In case you do not have any support plan , please send us an email on azcommunity [at] microsoft [dot] com and we will help you with alternative support options.

@vremeni4 This script has been updated by the product group now and the errors should not be seen. In case you still see any error , please send open a ticket with Microsoft support . In case you do not have any support plan , please send us an email on azcommunity [at] microsoft [dot] com and we will help you with alternative support options.


Support for "silent login" of existing users with Firebase Auth

Our current customer is asking for "Silent login of existing users (awaiting a call to FirebaseAuth.instance.currentUser)"

From a customer:
We want our users to be able to login with email and password and we want to retrieve this authentication from cache when the app is restarted.
We found that it takes a few moment for firebase auth to verify authentication status with the server, even when retrieving it from cache.
When trying to log an existing user in automatically, we found that auth.currentUser sometimes returns null because the login process is still ongoing.
In fact, firebase_auth.dart describes the currentUser getter this way: “Synchronously gets the cached current user, or null if there is none.”
We essentially need a variant of FirebaseUser.currentUser that we can await so that we can be sure that no firebase auth login is still pending
(if I got any part of the login process wrong, please let me know)

cc @kroikie for thoughts on if this is "normal" behavior, or what the API should look like here.

If I understand the request correctly this is a request for the implementation of getting the cached user, which is available via the onAuthStateChanged callback.
Something along the lines of this PR could be the solution.

Thanks @kroikie . If you can help us land the PR, that would be excellent.

I believe that this was fixed by #180

@sethladd
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/974. Any further collaboration will be done there.


How can I change the width of code block?

When I place a code block in post.
It look like this:

I don't want to see this scroll bar.

@AurevoirXavier The scrollbar is there to show overflowing code. You could make Chalk grid bigger in the _variables.scss file.


Remove NangoConnectionId from Gdrive workflow state

Yes - two more commits are coming.
On Mon, Nov 6, 2023 at 10:54 AM Stanislas Polu @.***>
wrote:

@.**** commented on this pull request.
Don't we need to bump the queue version since we're touching the workflows?
—
Reply to this email directly, view it on GitHub
https://github.com/dust-tt/dust/pull/2389#pullrequestreview-1714685236,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACXUNMF3WCVZIRBDFNZG4LYDCXUDAVCNFSM6AAAAAA67G5JVWVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTOMJUGY4DKMRTGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Don't we need to bump the queue version since we're touching the workflows?

I am actually not sure what to do here.
Since we don't have very long running workflows (except for full sync), bumping the queue or not is exposing us at the same risk of failing workflows.
If we bump: we will stop processing some existing workflows, but get no error.
If we don't bump, we'll get non deterministic errors.
Ideally we would have one commit with a worker for the old queue and the new queue.
Since we don't have that today, I would be in favor on not bumping the queue version, get an error for the non deterministic workflows and restart them manually.

But this means some workflow will old task to new code which is not the safest thing to do
I would bump the queue and manually kill the workflows + restart them (the fullSync ones if any)

But this means some workflow will old task to new code which is not the safest thing to do no?

Gdrive and Slack were designed around webhooks with short lived workflows. So we never had that problem too much (compared to notion which has no webhook and have long lived workflows).
If we end up having an old workflow running on new code, we'll get an error and restart it manually.
It's easier to react on error I think. We have always deployed Slack and Gdrive like that with a very little error rate (their queue name is still v1).

Are you sure you'll get an error? How temporal knows there is a mismatch of code ?

I see them in dev and I saw a few in production when deploying new versions of Slack and Gdrive. I will double check this specific case locally and report back here.

@spolu @philipperolet so after testing, we need to bump the version.
I thought changing workflow level code would trigger an error, but errors are not triggered when you only change the list of arguments to a function.
SInce workflows are compiled, I thought it would do a checksum version of the compiled workflows, but it actually looks at the activities order and throws a non deterministic error if the workflows calls activity in a new order.

Ack, GFM to merge after the bump (followed up by cleaning workflows)
PS: related slack discussion that triggered the PR


Change uffizzi connect to update existing credentials

From Adam:
What's the behavior of uffizzi connect if you specify environment variables but there are already credentials on the account? How does that behavior change with the --skip-raise-existence-error flag? I see this option demonstrated within the entrypoint script (good) but I do not see it documented anywhere.
Is there a way to change existing credentials without doing uffizzi disconnect? For execution in CD pipelines, we need a way to do this. With a flag is fine; I think overwriting as the default behavior is probably fine too?

Let's add --update-credential-if-exists flag. If this flag is passed, we need to update the credential if it exists in the database.

Usage example
DOCKERHUB_USERNAME=name DOCKERHUB_PASSWORD=password uffizzi connect docker-hub --update-credentials-if-exist

TESTED - OK
bash-5.1# bundle exec uffizzi connect docker-hub --update-credentials-if-exist
Updating existing credentials
Successfully connected to Docker Hub

👉 2.

Connect docker-hub (or another) credential
Add in docker-hub invalid docker-hub credentials
Run uffizzi connect docker-hub --update-credentials-if-exist

Result:
bash-5.1# bundle exec uffizzi connect docker-hub --update-credentials-if-exist
Updating existing credentials
undefined method `values' for [{:base=>{:account_id=>1, :id=>8, :username=>"uffizzitest1", :password=>"mYYN8P_gJp.H*jRNdz*ZHRU", :project_id=>nil, :created_at=>"2022-07-26T14:26:41.626Z", :updated_at=>"2022-07-26T14:26:41.626Z", :provider_ref=>nil, :state=>"active", :registry_url=>"https://index.docker.io/v1/"}, :attribute=>"username", :raw_type=>"incorrect", :type=>"incorrect", :options=>{}}, {:base=>{:account_id=>1, :id=>8, :username=>"uffizzitest1", :password=>"mYYN8P_gJp.H*jRNdz*ZHRU", :project_id=>nil, :created_at=>"2022-07-26T14:26:41.626Z", :updated_at=>"2022-07-26T14:26:41.626Z", :provider_ref=>nil, :state=>"active", :registry_url=>"https://index.docker.io/v1/"}, :attribute=>"username", :raw_type=>"incorrect", :type=>"incorrect", :options=>{}}]:Array
Did you mean?  values_at

Expected result:
bundle exec uffizzi connect docker-hub --update-credentials-if-exist
Updating existing credentials
We were unable to log you in to docker registry. Please verify that your username and password are correct.

👉 3.
Add dot . at the end of the sentence  Updating existing credentials

👉 4.

Connect docker-hub account 1 (e.g. uffizzitest)
Deploy private image from this account (deployment-1 should be created)
Update credentials and connect docker-hub account 2 (e.g. your own account)
Update deployment-1. Try to update the preview deployment-1 with the private image from your own account.

Result: Deployment failed.
If then start to deploy (not update) private repo from your own account it will be successfully deployed.
bash-5.1# bundle exec uffizzi preview create -o=json test-compose/uffizzi-compose-webhook-docker-private.yml
[✔] Creating containers...
[✔] Deploying preview...
  [✔] test-private-repo
{"id":"deployment-14","url":"https://deployment-14-default.app.qa-gke.uffizzi.com"}

bash-5.1# bundle exec uffizzi connect docker-hub --update-credentials-if-exist
Updating existing credentials.
Successfully connected to Docker Hub.

bash-5.1# bundle exec uffizzi preview update deployment-14 test-compose/uffizzi-compose-webhook-docker-neal.yml
Preview with ID deployment-14 was successfully updated.
[✔] Creating containers...
Done
[✖] Deploying preview...
  [✖] webhook-test-app
Deployment Not Found

bash-5.1# bundle exec uffizzi preview create test-compose/uffizzi-compose-webhook-docker-neal.yml
Preview created with name deployment-15
[✔] Creating containers...
Done
[✔] Deploying preview...
  [✔] webhook-test-app
Done
https://deployment-15-default.app.qa-gke.uffizzi.com

Next compose files were used:
uffizzi-compose-webhook-docker-private.yml
services:
  webhooks-test-app:
    image: uffizzitest/test-private-repo:latest
    environment:
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: postgres

x-uffizzi-ingress:
  service: webhooks-test-app
  port: 80

x-uffizzi-continuous-preview:
  share_to_github: true
  delete_preview_after: 1h
  tag_pattern: uffizzi_request_*
  delete_preview_when_image_tag_is_updated: true
  deploy_preview_when_image_tag_is_created: true
  delete_preview_when_pull_request_is_closed: true
  deploy_preview_when_pull_request_is_opened: true

uffizzi-compose-webhook-docker-neal.yml
services:
  webhooks_test_app:
    image: nealarw/webhook-test-app:latest
    environment:
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: postgres

x-uffizzi-ingress:
  service: webhooks_test_app
  port: 80

x-uffizzi-continuous-preview:
  delete_preview_after: 1h
  delete_preview_when_image_tag_is_updated: true
  deploy_preview_when_image_tag_is_created: true

TESTED - OK
bash-5.1# bundle exec uffizzi connect docker-hub --update-credentials-if-exist
Updating existing credentials.
Username: uffizzitest
Password:
Successfully connected to Docker Hub.

TESTED - OK
bash-5.1# bundle exec uffizzi connect docker-hub --update-credential-if-exists
Updating existing credential.
Successfully connected to Docker Hub.

TESTED on prod:
CLI connect into APP - OK
# uffizzi connect docker-hub
Username: nealarw
Password:
Successfully connected to Docker Hub.

# uffizzi preview create -o=json compose_1.yml
[✔] Creating containers...
[✔] Deploying preview...
  [✔] webhook-test-app
{"id":"deployment-3","url":"https://deployment-3-default.app.qa-gke.uffizzi.com"}

# uffizzi connect docker-hub --update-credential-if-exists
Updating existing credential.
Username: uffizzitest
Password:
Successfully connected to Docker Hub.

# uffizzi preview update -o=json deployment-3 ccompose_2.yml
[✔] Creating containers...
[✔] Deploying preview...
  [✔] test-private-repo
{"id":"deployment-3","url":"https://deployment-3-default.app.qa-gke.uffizzi.com"}

TESTED on prod - OK
CLI + Platform


Enable RTL and pseudo-locales in debug builds

As the title says. I'm getting tired of toggling these on-and-off :wink:

For testing, you'll need to set your language to "ar_XB". In the Android emulator you can use the "Custom Locale" app to do that. On real devices, you can get a similar app from the Play Store (https://play.google.com/store/apps/details?id=br.testing.locale)

@miankhalid This will allow us to fully test RTL support. Will this work for you?

Great work :+1:
You just made my and QA's life easy, thanks :smile:

@miankhalid Cool, glad to hear it :smiley:


Remove unneeded check in CFRelease and CFRetain.

If they were NULL, the program would just exit so this check is not needed.

@etcwilde any updates?

This should be okay given that the definition of __CFGenericAssertIsCF checks the input over in CFRuntime.c.
That said, I'm going to defer to @millenomi since they're more familiar with this repo.

@swift-ci please test

OK I think it will work now. I just had to rebase

@etcwilde can we try one more time?

@swift-ci please test

Please test with following PRs:
apple/swift#41115
@swift-ci please test macOS platform

The macOS Platform failing seems to be a bug by others which should be fixed by this PR apple/swift#41115

@swift-ci test

@parkera Thank you!


xmas_elf OOB access in Kernel ELF loader

This memory corruption only occurs while loading vi and can be reproduced on PR #360 .

https://github.com/sunriseos/SunriseOS/pull/360/commits/d9c80bfecae0080b0bd3f69b5a2763a34ceaec06 is the commit that's affected (in case PR gets force pushed)

Can you give a description of the problem ?

This bug is definitely present on master.
Haven't bisect yet, but reverting last xmas_elf update fixes the problem: 014dc189 (Jun 15 !)
I would like to investigate and report the bug to xmas_elf, but in the mean time I'm going to make a PR doing the revert.

I was wrong, reverting xmas_elf update does no solve the problem. On some branches it seems to sometime disappear when doing a full rebuild of sunrise, hinting toward an incremental compilation problem.
For now I still believe this is a xmas_elf bug, and sunrise is not responsible for it. To prove my theory I'm going to try to replicate the OOB in a std crate that just tries to parse the "faulty" vi elf with xmas_elf.

@Thog found the problem: it's in mkiso-rs.
Once the bug is found, we should add a test to the CI that the generated ISO is correct by mounting the ISO and checking all the files.

GRUB2 seems to not like the way my files were allocated, this should be fixed by the last release of mkisofs-rs. Please make sure to update it.

Updated mkisofs-rs, diffed every module loaded by grub against their original elf, everything seems to be in order now.
I'm closing the issue.


Installation of exodus through pip is not covered in the readme

One can install exodus by doing pip install sinabs-exodus. This can be mentioned in the readme of the repo as well.

Thanks for pointing this out!


Backspace = CTRL+Backspace?

Your Windows build number:  (Type ver at a Windows Command Prompt)

Microsoft Windows [Version 10.0.16299.19]

What you're doing and what's happening:  (Copy&paste specific commands and their output, or include screen shots)

I am running zshell on WSL where I bind widgets to key combinations with bindkey <combination> <function>. All kinds of [CTRL, ALT]+[anykey] combinations work fine but for anykey = Backspace. I tried to find the escape sequence but

Using CTRL+v to check what they are bound to shows no output for it
Using sed -n l shows nothing as well, except that it deletes one char of any other previously tried combination, just as one would naively expect from a backspace stroke.

Using bindkey '^?' backward-delete-word I manage to bind the regular Backspace stroke to deleting a full word, but this is of course not what I want since I loose the single char deletion this way. The usual shell way of hitting CTRL+w to delete backwars-delete a full word works, but I would like to bind it to CTRL+Backspace since this is what I'm used to in most other editors. Is there any way how I can achieve this? Could I somehow map the CTRL+W key to CTRL+Backspace?

What's wrong / what should be happening instead:

I would have expected to be able to bind the backspace key in a similar fashion as all the other keys

Oh this is related to #2350.
On the backlog for this next release :)

Oh this is related to #2350.
Thanks for spotting this and sorry for the dup! Looking forward to seeing this solved! Keep up the good work!