apache_beam.runners.portability.flink_runner_test.FlinkRunnerTestOptimized.test_flink_metrics is flaky

Sample error:
https://ci-beam.apache.org/job/beam_PreCommit_Python_PVR_Flink_Commit/2869/testReport/junit/apache_beam.runners.portability.flink_runner_test/FlinkRunnerTestOptimized/test_flink_metrics/

Error Message
AssertionError: Items in the second set but not the first: 'stateful).beam.metric:statecache:hit:
11' 'stateful).beam.metric:statecache:put: 1' 'stateful).beam.metric:statecache:miss: 1' 'stateful).beam.metric:statecache:get_total:
120' 'stateful).beam.metric:statecache:size: 10' 'stateful).beam.metric:statecache:get: 12' 'stateful).beam.metric:statecache:evict:
0' 'stateful).beam.metric:statecache:capacity: 123' 'stateful).beam.metric:statecache:put_total: 10'
'stateful).beam.metric:statecache:evict_total: 0' 'counter: 110' 'stateful).beam.metric:statecache:miss_total:
10' 'stateful).beam.metric:statecache:hit_total: 110'
Stacktrace
self = <apache_beam.runners.portability.flink_runner_test.FlinkRunnerTestOptimized
testMethod=test_flink_metrics>

    def test_flink_metrics(self):
      """Run a simple DoFn that
increments a counter and verifies state
      caching metrics. Verifies that its expected value is
written to a
      temporary file by the FileReporter"""

      counter_name = 'elem_counter'

     state_spec = userstate.BagStateSpec('state', VarIntCoder())

      class DoFn(beam.DoFn):

       def __init__(self):
          self.counter = Metrics.counter(self.__class__, counter_name)

         _LOGGER.info('counter: %s' % self.counter.metric_name)

        def process(self, kv,
state=beam.DoFn.StateParam(state_spec)):
          # Trigger materialization
          list(state.read())

         state.add(1)
          self.counter.inc()

      options = self.create_options()

    # Test only supports parallelism of 1
      options._all_options['parallelism'] = 1
      # Create
multiple bundles to test cache metrics
      options._all_options['max_bundle_size'] = 10
      options._all_options['max_bundle_time_millis']
=<PHONE_NUMBER>0
      experiments = options.view_as(DebugOptions).experiments or []
      experiments.append('state_cache_size=123')

     options.view_as(DebugOptions).experiments = experiments
      with Pipeline(self.get_runner(),
options) as p:
        # pylint: disable=expression-not-assigned
        (
            p

     | "create" >> beam.Create(list(range(0, 110)))
            | "mapper" >> beam.Map(lambda x: (x
% 10, 'val'))
            | "stateful" >> beam.ParDo(DoFn()))

      lines_expected = {'counter:
110'}
      if options.view_as(StandardOptions).streaming:
        lines_expected.update([

      # Gauges for the last finished bundle
            'stateful.beam.metric:statecache:capacity:
123',
            'stateful.beam.metric:statecache:size: 10',
            'stateful.beam.metric:statecache:get:
20',
            'stateful.beam.metric:statecache:miss: 0',
            'stateful.beam.metric:statecache:hit:
20',
            'stateful.beam.metric:statecache:put: 0',
            'stateful.beam.metric:statecache:evict:
0',
            # Counters
            'stateful.beam.metric:statecache:get_total: 220',

    'stateful.beam.metric:statecache:miss_total: 10',
            'stateful.beam.metric:statecache:hit_total:
210',
            'stateful.beam.metric:statecache:put_total: 10',
            'stateful.beam.metric:statecache:evict_total:
0',
        ])
      else:
        # Batch has a different processing model. All values for

    # a key are processed at once.
        lines_expected.update([
            # Gauges

   'stateful).beam.metric:statecache:capacity: 123',
            # For the first key, the cache token
will not be set yet.
            # It's lazily initialized after first access in StateRequestHandlers

           'stateful).beam.metric:statecache:size: 10',
            # We have 11 here because there
are 110 / 10 elements per key
            'stateful).beam.metric:statecache:get: 12',

'stateful).beam.metric:statecache:miss: 1',
            'stateful).beam.metric:statecache:hit: 11',

           # State is flushed back once per key
            'stateful).beam.metric:statecache:put:
1',
            'stateful).beam.metric:statecache:evict: 0',
            # Counters
            'stateful).beam.metric:statecache:get_total:
120',
            'stateful).beam.metric:statecache:miss_total: 10',
            'stateful).beam.metric:statecache:hit_total:
110',
            'stateful).beam.metric:statecache:put_total: 10',
            'stateful).beam.metric:statecache:evict_total:
0',
        ])
      lines_actual = set()
      with open(self.test_metrics_path, 'r') as f:

     for line in f:
          for metric_str in lines_expected:
            metric_name = metric_str.split()[0]

           if metric_str in line:
              lines_actual.add(metric_str)
            elif metric_name
in line:
              lines_actual.add(line)
>     self.assertSetEqual(lines_actual, lines_expected)
E
    AssertionError: Items in the second set but not the first:
E     'stateful).beam.metric:statecache:hit:
11'
E     'stateful).beam.metric:statecache:put: 1'
E     'stateful).beam.metric:statecache:miss:
1'
E     'stateful).beam.metric:statecache:get_total: 120'
E     'stateful).beam.metric:statecache:size:
10'
E     'stateful).beam.metric:statecache:get: 12'
E     'stateful).beam.metric:statecache:evict:
0'
E     'stateful).beam.metric:statecache:capacity: 123'
E     'stateful).beam.metric:statecache:put_total:
10'
E     'stateful).beam.metric:statecache:evict_total: 0'
E     'counter: 110'
E     'stateful).beam.metric:statecache:miss_total:
10'
E     'stateful).beam.metric:statecache:hit_total: 110'

apache_beam/runners/portability/flink_runner_test.py:390:
AssertionError

Imported from Jira BEAM-12019. Original Jira may contain additional context.
Reported by: tvalentyn.

I think this is fixed. If not, it should get auto-flagged by our tooling anyways, so this should be safe to close


YAML frontmatter rendered improperly

Exemplary, in a Jekyll project, markdown files have a YAML front matter like this default one in index.md:
---
# Feel free to add content and custom Front Matter to this file.
# To modify the layout, see https://jekyllrb.com/docs/themes/#overriding-theme-defaults

layout: default
---

Gitea tries to render it as if it was regular Markdown:

Instead, it should detect it being the YAML frontmatter and render it properly, e.g. like this (screenshot created by adding four spaces in front of each line in the front matter):

Gitea Version: 4c1f1f9

There is an open pull request for gogs: https://github.com/gogs/gogs/pull/4643

I have the same problem. Would be nice if the front matter just weren't rendered at all.

@zeripath Do you think the change to goldmark makes a difference for this issue, does it have any specific support for it?

@davidsvantesson I haven't checked how it looks now, but Goldmark definitely has support for yaml frontmatter. It is used as the default renderer for Hugo which does also have yaml frontmatter.

@davidsvantesson @dakira we would need to use the https://github.com/yuin/goldmark-meta extension.
I guess it would probably be quite easy to do. The issue is deciding whether to always enable it or not.
I mean yaml front matter is a particular extension to commonmark - it may not be expected.


Call ABAP: stable design code

Call ABAP: Example of object oriented patterns on practical examples

.abapgit.xml missing, plus license missing

.abapgit.xml missing, plus license missing

Done.
I have re-created it and it seems forgot about them.


Extract out code that has only cadence dependencies

Sometimes other projects wants to use parts of overflow that only rely on cadence. Atm that is hard for them since it has many dependencies.
Extract out utilities that only have cadence as a dep from flow into a underflow project.

Also add options on the api to have a terse (current) format and a more verbose mode for the CadenceToValue functions.

This will only be there for v2 since it breaks BC.


openOutputOnDeploy ignoring "false" setting

Hi! First of all, thank you for this wonderful plugin.
I have this issue. Despite setting "openOutputOnDeploy" to false, the output keeps popping up.
I am running Visual Studio Code 1.10.2 under Windows 10 Pro 64-bit. The version of vs-deploy is the lates available (6.1.2).
I already tried closing and restarting VSCode.
This is my settings.json file.
{
    "deploy": {
        "packages": [
            {
                "name": "Version 2.3.4",
                "description": "Package version 2.3.4",
                "exclude": [
                    "_sql/**",
                    ".git/**",
                    "storage/**",
                    ".vscode/**"
                ],
                "deployOnSave": true,
                "openOutputOnDeploy" : false
            }
        ],
        "targets": [
            {
                "type": "ftp",
                "name": "xxx",
                "description": "xxx",
                "dir": "xxx",
                "host": "xxx", "port": 21,
                "user": "xxx", "password": "xxx"
            }
        ]
    }
}

It is a global setting:
{
    "deploy": {
        "openOutputOnDeploy" : false,

        "packages": [
            {
                "name": "Version 2.3.4",
                "description": "Package version 2.3.4",
                "exclude": [
                    "_sql/**",
                    ".git/**",
                    "storage/**",
                    ".vscode/**"
                ],
                "deployOnSave": true
            }
        ],
        "targets": [
            {
                "type": "ftp",
                "name": "xxx",
                "description": "xxx",
                "dir": "xxx",
                "host": "xxx", "port": 21,
                "user": "xxx", "password": "xxx"
            }
        ]
    }
}

Whoops!
Rookie mistake, sorry for wasting your time :)

@bimbo1989
No problem! ;-)


tests: fix flaky migration test by patching node instead of updating

What this PR does / why we need it:
Running Update() on a global object can fail if the object changed since the last Get().
We can either keep retrying to get + update, or just patch. I picked patch.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/cherry-pick release-0.53

Does this relate to #7752?

No.. Indeed it does look similar, but the part I'm fixing doesn't seem to be addressed by #7752.

@jean-edouard Thank you!

Does this relate to #7752?

No.. Indeed it does look similar, but the part I'm fixing doesn't seem to be addressed by #7752.

I think it actually is.
If you disagree we can talk offline :ok_hand:

Does this relate to #7752?

No.. Indeed it does look similar, but the part I'm fixing doesn't seem to be addressed by #7752.

I think it actually is. If you disagree we can talk offline ok_hand

https://github.com/kubevirt/kubevirt/pull/7752/files#diff-432108e71d3780d20244b4303d7b4e6d37151904ead1b9227be9ad87df1df90aR2746


Include chart(s) for personal stats page

On the https://adventofcode.com/2018/leaderboard/self page (and those for other years) we could also show some fun stats. Something based off this codepen perhaps?
The codepen only does something with rank for star 2, but other cool stuff would include:

difference between two ranks
difference in time to star 1 and star 2
score (though for most people that's just 0 :D)

Of course the extension would only be able to see the html page of 1 year at a time (but I guess we can hack our way around it by 'saving' the scraped data for later, when the user switches years?).

Tagging this 'hacktoberfest' although note that this is not really a small thing to add. Still welcome if someone wants to give it a shot.

PS. There's a advent-of-code-charts channel in the contributing.today Discord where I'll be if anyone has hacktoberfest-related questions!

I'm eyeballing this for a 2023 update, but only if there will be a 2023 AoC edition at all 😅... so letting this sit until at least fall, might pick it up after that.

There is a 2023 edition! However, all the updates from Jan/Feb and from this Nov focused on other features. Perhaps in 2024 the Personal Leaderboards will get some love.
PS. Note that there was some inspiration on Reddit too for personal leaderboards improvements.


webmasters V3 API down
googleapiclient.errors.UnknownApiNameOrVersion: name: webmasters version: v3

Environment details
OS macOS: 10.15.4

Python version: python 3.8.1

pip version: pip 19.0.3

google-api-python-client version: 1.12.1
Code example
from googleapiclient.discovery import build
 service = build(
        'webmasters',
        'v3',
        credentials=credentials
    )

Stack trace

googleapiclient.errors.UnknownApiNameOrVersion: name: webmasters version: v3
While trying to get data from Search Console API we get this error UnknownApiNameOrVersion.
URL on web is also down

We are hitting the same issue. Please fix or revert

I'm having the same issue.
FIY it happened once in September 2020.
https://github.com/googleapis/google-api-python-client/issues/1042

googleapiclient.errors.UnknownApiNameOrVersion: name: webmasters  version: v3
I have been looking for a solution in the last few days for this issue too..
Some of our airflow dag runs seems executed successfully for some days but data did not land for those days.. I highly recommend you guys to check out your data for 18th, 19th, 20th and 21st of October 2021.
Please leave a fix here if any of you guys can make it work.. Please let us know what package combination it works with and which version of Python.
Thank you!
Oz.

I encountered the same problem here, the solution given by #1042 seem doesn't work for me. After changing it to build('searchconsole', 'v1', http=http) will get 400 HTTP error.

webmasters v3 is included in the static discovery artifacts that are shipped with google-api-python-client>=2.
Please can you try the following?
from googleapiclient.discovery import build
service = build('webmasters','v3')

We are facing similar issues with google-api-python-client version: 1.7.4. The UnknownApiNameOrVersion started showing up 3 days ago on several calls and now returns for all of our api calls.
from googleapiclient import discovery discovery.build('webmasters','v3','http=http,cache_discovery=False

Facing issue since last 4 days.. Kindly advise.
googleapiclient.errors.UnknownApiNameOrVersion: name: webmasters  version: v3
service = build_from_document(
                content,
                base=discovery_url,
                http=http,
                developerKey=developerKey,
                model=model,
                requestBuilder=requestBuilder,
                credentials=credentials,
                client_options=client_options,
                adc_cert_path=adc_cert_path,
                adc_key_path=adc_key_path,
            )

Facing issue since last 4 days.. Kindly advise.
googleapiclient.errors.UnknownApiNameOrVersion: name: webmasters version: v3
service = build_from_document(
                content,
                base=discovery_url,
                http=http,
                developerKey=developerKey,
                model=model,
                requestBuilder=requestBuilder,
                credentials=credentials,
                client_options=client_options,
                adc_cert_path=adc_cert_path,
                adc_key_path=adc_key_path,
            )

Please update to google-api-python-client version 2.x in order to use static discovery artifacts which are included with the library.
The following should work on google-api-python-client version 2.x

from googleapiclient.discovery import build
service = build('webmasters','v3')

raise UnknownApiNameOrVersion("name: %s  version: %s" % (serviceName, version))
googleapiclient.errors.UnknownApiNameOrVersion: name: webmasters  version: v3
Same issue, who will be able to let us know a fix ?

@parthea google-api-python-client>=2 no longer supports Python2, any solution for legacy systems?

@DanReia You can use https://github.com/googleapis/google-api-python-client/blob/main/googleapiclient/discovery_cache/documents/webmasters.v3.json and build_from_document if you are unable to upgrade to the latest version.
Internal issue 204972401 indicates this API (webmasters V3) is deprecated. I'm checking with that team to see what they recommend as an alternative.

It seems using:
from googleapiclient.discovery import build
 service = build(
        'searchconsole',
        'v1',
        credentials=credentials
    )

Seems to work, but I just notice most documentation on Search Console still references the webmasters V3 API.

Here's the response from the API team:

Hey. So the Python example in our devsite already contains the new API name and version. We also published this blog post a while back with the deprecation announcement and refactor instructions.

It looks like the recommended approach is to use searchconsole v1 instead of webmasters v3.
https://developers.google.com/search/blog/2020/12/search-console-api-updates#discovery-doc-migration indicates the objects are the same so it should be a drop in replacement.

I'm going to close this issue as resolved but please feel free to re-open it or create a new issue if you're still having trouble.

@busunkim96 I will give searchconsole v1 a go, thank you for your help!

Thanks everyone.. It works with searchconsole v1.
Documentation was confusing and made me think searchconsole is older than webmasters.


htmlproofer ignores link to crates.io

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a31b1baa9eccf77d4bbd80e3b0c0fa674a2a5613/


Version 6.1.0 is broken

The action LOCATION_CHANGE is called after componentDidMount of the component, this causes my sagas to be canceled.
I use redux-saga and cancel them with LOCATION_CHANGE.

v6.1.0

v6.0.0

goForward is totally broken.
never enabled

For the LOCATION_CHANGE calling after componentDidMount, this is intended to fix the old implementation by moving the dispatching from constructor to componentDidMount. (see this comment.
For the goForward, can you explain a bit more? Is there any minimal repo to reproduce it?

@supasate Thanks for your reply!
The repo
Use this extension for test the sagas and actions.

Got similar problem here, but backward. The problem is caused by the listeners of react-router's history and the subscriber of redux store.
Router component from react-router will listen to history in componentWillMount. (v 4.3.1 used by latest connected-react-router).
But ConnectedRouter will do that in componentDidMount instead of  constructor.
The order of these listeners are changed in 6.1.0.
Also, ConnectedRouter subscribes to redux store. It will check history path with store path.
Here is an example when browser backward is clicked:
The listener of router component will be triggered first. That will update it's state. Then children components might be updated, and fire some redux actions (from componentDidUpdate or others). Because redux executions are sync, so store could be changed, then subscribers will be triggered first before the history listener of ConnectedRouter. In that case, LOCATION_CHANGE  won't be fired the first time when a history is changed. But according to the subscriber, store path is still the old one. So a new history.push will be fired.  That's really unexpected.

We saw really odd behavior as well in our application when upgrading to the latest version.  We had two pages, both with back buttons and we would somehow get into a circular loop.

Page 0, click a link to Page 1
Page 1, click a link to Page 2
Page 2, click a button that calls (back) and navigate to Page 1
Page 1, click a button that calls (back) and navigate to Page 0

Works fine on version 6.0.0, but on version 6.1.0, step 4 actually gets sent to Page 2 instead of Page 0.  For now, we have reverted to the older stable version.

@ahce @syjstc @ryank311 Can you all try again with connected-react-router@next (6.2.0-beta.1) if it solves the problem?


Not deleting messages

I set up the bot in a channel with:
@AutoDelete set 72h

It gives the following warning and does nothing:
The number of messages in this channel is over 200. Messages may not be reliably deleted. (Saw: 200)

I‘m also wondering if there’s any way to fix/workaround this limit. 200 messages is quite little for most discord instances.
In my particular use-case, I have an auto-delete that deletes after 1 month. That means it only works up to 7 messages per day...
Is it possible to implement this? I’d say it should be, given that I can manually delete the older messages without any issues.


        Data may have also been saved along the way. This forces the
        last of the data to be saved.

        Returns True if there was data to save, False if not.
        """
        if not self._activity():
            return False

        if self.branch:
            if self.packed_arcs:
                # Unpack the line number pairs packed into integers.  See
                # tracer.c:CTracer_record_pair for the C code that creates
                # these packed ints.
                arc_data: Dict[str, List[TArc]] = {}
                packed_data = cast(Dict[str, Set[int]], self.data)
                for fname, packeds in packed_data.items():
                    tuples = []
>                   for packed in packeds:
E                   RuntimeError: Set changed size during iteration

arc_data   = {'/Users/runner/work/tox/tox/.tox/py3.12/lib/python3.12/site-packages/tox/__init__.py': [], '/Users/runner/work/tox/to...thon3.12/site-packages/tox/config/cli/env_var.py': [(43, -14), (-14, 22), (23, 43), (22, 23), (23, 24), (24, 23)], ...}
fname      = '/Users/runner/work/tox/tox/.tox/py3.12/lib/python3.12/site-packages/tox/tox_env/python/virtual_env/package/pyproject.py'
l1         = 128
l2         = 124
packed     = 130023552
packed_data = {'/Users/runner/work/tox/tox/.tox/py3.12/lib/python3.12/site-packages/tox/__init__.py': set(), '/Users/runner/work/tox.../site-packages/tox/config/cli/env_var.py': {24117270, 24117272, 25165847, 45088791,<PHONE_NUMBER>462,<PHONE_NUMBER>659}, ...}
packeds    = {106954853, 108003430, 109052007, 110100584, 111149161, 112197738, ...}
self       = <Collector at 0x10ac527e0: CTracer>
tuples     = [(128, 124)]

.tox/py3.12/lib/python3.12/site-packages/coverage/collector.py:507: RuntimeError

Do you know what has changed in the last few weeks? Are you using a newer version of coverage? Is there a way for me to reproduce it?

I do not sadly, even in the CI happens semi-regularly. I don't have more than what I already put above.

This is fixed in commit 08fc997b6b3d881e8e5082b71ad6d6bcc4e2f752.

This is now released as part of coverage 7.4.3.


Bug with token decimal handling for Trade

Describe the bug
A clear and concise description of what the bug is.
const quoteResponse = await (       await fetch(        ${JUP_API}/quote?+          inputMint=${inputMint.toString()}+          &outputMint=${outputMint.toString()}+          &amount=${inputAmount * LAMPORTS_PER_SOL}+          &slippageBps=${slippageBps}+          &onlyDirectRoutes=true+          &maxAccounts=20,       )     ).json();
This is assuming all input tokes are 9decimals, which is going to cause issues, when trying to swap tokens with decimals other than 9
Expected behavior
The function is supposed to detect, the decimals of the input Token and then multiply that with the inputAmount

Hello @impozzible  A support ticket has been opened for you. Kindly Talk to Support on the Live support page so that your issue can be looked into. CLICK HERE


feat: bump release level to production/stable

Fixes #64  🦕

There is a pending release with new fixes and features. Please merge https://github.com/googleapis/python-functions/pull/61 and reset the timer.

Wait for #78


[all] Add macOS support

From the Firebase iOS SDK readme:

Thanks to contributions from the community, FirebaseABTesting, FirebaseAuth, FirebaseCore, FirebaseDatabase, FirebaseMessaging, FirebaseFirestore, FirebaseFunctions, FirebaseRemoteConfig, and FirebaseStorage now compile, run unit tests, and work on macOS and tvOS.

This should make it quite easy to support most Firebase plugins on macOS. If noone is already working on this I will try to experiment with firebase_core, firebase_auth, cloud_functions and cloud_firestore. Help and guidance very much appreciated.
How do you feel about converting those plugins to Swift at the same time? It's not really needed but I would feel much more comfortable with that language.
/cc @ditman @hterkelsen @collinjackson

PRs for firebase_core, firebase_auth, cloud_functions and cloud_firestore are created. They are all tested in our app but lack unit tests. I will try to add them in the coming days.
They are 99% identical to their iOS siblings. I currently added them as macos folders next to the ios implementation. Federation would be an option but I think it would be ideal if we could find a way to even keep both implementations in the same file to prevent them from drifting apart. What would be the best approach for that?

Federation would be an option but I think it would be ideal if we could find a way to even keep both implementations in the same file to prevent them from drifting apart. What would be the best approach for that?

@cbenhagen What about extracting the common ios and macos parts to a shared package that gets dependend on by both the ios plugin (in the core package) and the macos version (in its own, federated, package)?

how is it going? and how do we add osx support for firebase, is it just like ios? i mean info.plist file.

@abjorck I can't promise anything but I will try and see how far I get. Will add firebase_crashlytics and firebase_messaging for sure as I am also using them.

Is the crashlytics plugging working for iOS? Me and some other can't get it to work following the implementation guid. See issue described:
StackOverflow: flutter-flutter-firebase-crashlytics-not-showing-for-ios

@viktor-morin please stop hijacking other issues.

@viktor-morin please stop hijacking other issues.

I'm not trying yo hiijacking anything, I'm trying to solve an issue. So this isn't related either? So this is just for macOS and not iOS? I was hoping solving macOS would solve iOS as well. My bad.

Fixing your issue for iOS would most likely also fix it for macOS as the code is shared. This issue here was created to track overall progress of macOS implementations of all firebase plugins and to discuss topics which touch them all like sharing code between iOS and macOS.
Please keep the communication about your specific issue in the issue itself unless you have good reasons to believe that another issue is related. If it just mentions iOS as well it does not mean that the issue is in any way connected.

Manage to solve it for MAC, apparently you need in the Firebase Console, for iOS press "Enable SDK"
Step 1: Set up Crashlytics in the Firebase console
Click Crashlytics in the left-hand nav panel of the Firebase console.
If your Firebase project has multiple apps registered in it, select the app you just added from the dropdown next to Crashlytics in the top bar of the console.
Click Add SDK.
https://firebase.google.com/docs/crashlytics/get-started

@cbenhagen do you have any plans to add firebase_analytics support?

This is blocked by https://github.com/firebase/firebase-ios-sdk/issues/1732

Hey all, just an FYI firebase_database MacOS support is landing shortly via #3021

Hey all, another FYI 🙃  firebase_remote_config MacOS support is landing shortly via #3066


Question: Regarding using pyexasol in a docker environment

Hi there,
I don't know if this here is the right place for asking questions, but I have a potentially pretty stupid question so here it is:
If I wanted to use pyexasol in a script that runs in some docker container built from an image like I don't know maybe python:3.9-slim-buster + installing pyexasol via pip would it be possible to connect to an Exasol instance?
Or do I have to make sure and install an ODBC driver inside the container?
Cheers for your help

It should be possible. This page lists all optional dependencies: https://github.com/badoo/pyexasol/blob/master/docs/DEPENDENCIES.md
The core dependencies are implemented in pure Python: websocket-client, rsa. Some other dependencies require compilation and may raise some concerns: pandas, pyopenssl.
But if you do not need pandas or encryption, you may safely skip these dependencies.

You do not need ODBC / JDBC driver. PyEXASOL uses an alternative native WebSocket protocol.

Thanks for your comments! I do believe though that the WebSocket protocol has to be activated on the server side for it to work. I've tried to connect to the Exasol instance at work with no ODBC/JDBC driver installed and it doesn't work. Admins haven't activated the websocket mode.
Anyway, thanks for answering my questions, appreciated!

WebSocket protocol should be available starting from Exasol v6.0+. It is available by default. There is no way to activate or deactivate it explicitly.


Invalid “hours” in range cause cron #next_time loop breaker issue

Issue description
Values outside 0-23 in an hour range cause an infinite loop error.
How to reproduce
require 'fugit'
c = Fugit.parse('* 0-24 * * *')

RuntimeError (too many loops for {:min=>0, :max=>23, :sta=>0, :edn=>24, :sla=>1} #range, breaking, please fill an issue at https://git.io/fjJC9)

Expected behaviour
The “24” being out of range should either result in a parsing error or being treated as 0.
Context
Please replace the content of this section with the output of the following commands:
Darwin Kinzie 18.7.0 Darwin Kernel Version 18.7.0: Thu Jun 20 18:42:21 PDT 2019; root:xnu-4903.270.47~4/RELEASE_X86_64 x86_64
ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-darwin18]
(secs:1565722428.8614998,utc~:"2019-08-13 18:53:48.8614997863769531",ltz~:"PDT")
(etz:nil,tnz:"PDT",tziv:"1.2.5",tzidv:nil,rv:"2.6.2",rp:"x86_64-darwin18",win:false,rorv:nil,astz:nil,eov:"1.2.1",eotnz:#<TZInfo::TimezoneProxy: America/Dawson>,eotnfz:"-0700",eotlzn:"America/Dawson",eotnfZ:"PDT",debian:nil,centos:nil,osx:"zoneinfo/America/Vancouver")

Additional context
Encountered via in-the-wild user input!

Note in passing:
https://crontab.guru/#*_0-24_*_*_* says 24 is not in the allowed range.

Already accepting 24 on its own, https://github.com/floraison/fugit/blob/12a2faabc1d5f66fc8b4c8c3795d6b32c154ac2d/spec/cron_spec.rb#L50 so have to be lenient.

Released as part of fugit 1.3.2.
https://rubygems.org/gems/fugit/versions/1.3.2
Please tell me if there is anything wrong.
Many thanks with this issue report.

Thanks for the quick fix! Looking good 😄


Console Shuts down

Consoles: CECHH04, CECHG04 EvilNAT 4.89CFW + webMAN MOD 1.47.41
Here is what happens on both consoles:
Console starts up alright and works flawlessly.
But after activating fps counter everything shows as it should except cpu/gpu clocks are missing. After ~17 seconds YLOD, console shuts down power led red flashing and beeping. It doesn't matter what I do, browse in XMB, start a game, do nothing, it always happens at ~17 seconds.
Powering the console up again, hdd checking("the unit was not properly shut down the last time is was used") and after that the xmb starts up.
And here is the difference, after activating the fps counter again (L3+R3) everything happens as before except after ~17 seconds the cpu/gpu clocks appear too. No crash.
After shutting down the console and powering up again next day everything happens again from start.
It's like the cpu/gpu clock speed readout crashes the console.
I tried configuring the plugin to only show fps/cpu/gpu temperature/fan speed, but crashed again. It works only after a YLOD/hdd check. I checked the hdd its flawles in both consoles.
Reinstalled cfw, no luck.
I tried version 2.2 and it works flawlessly, it only freezes sometimes when exiting a game, but its a known bug.

Do you use COBRA or MAMBA payload?

I don't know, evilnat cfw comes with cobra 8.3. I don't set anything like that just install webman mod and set the fan speed. I tought at first the console is bad, but the other one does the same. At psx-place.com in the webman mod topic another user had this issue like me.

Both of you mentioned you have a phat ps3 model.
From PSX PLACE
PostalDude__
Member
Joined:Jan 12, 2021
Messages:32
Trophy Points:32
the new FPS plugin and start navigating menus within the XMB, it will eventually YLOD the console with 1601/1701 (enabling the start+select menu speeds up this too). I have no clue if that has been reported so far. I have confirmed this to occur on both of my COK-001 based consoles to rule out the possibility of a hardware issue.
I have only tested on evilnat 4.88.2 so i have no clue if this occurs on any other firmware, i have uploaded a video of the issue, as well as the syscon error log if that is of any help.
The video: https://cdn.discordapp.com/attachments/888130660773003265/980949846787772536/Snapchat-265624386.mp4
and i have uploaded the syscon log the usual way
Attached Files:
syscon log.txt
File size:1.5 KB
Views:2
PostalDude__, Tuesday at 6:17 AM

I have a Slim(CECH-2004A) with EvilNAT 4.88 CFW and a super slim (CECH-4004) with HFW 4.88+HEN 3.1.
I will test it on them in the next few days.

I tested the Slim.
It works, kind of. In XMB no problem, but the games freeze randomly.
I think it's maybe because of the low free memory. In XMB it is around ~1600KB, after a game starts it's only 400-500KB.
Isn't that too low?

try to lower the vsh memory used with webman plugin settings

I can confirm that this exact crash also occurs on CECHCK04 (board DIA-002).

It's like the cpu/gpu clock speed readout crashes the console.
I tried configuring the plugin to only show fps/cpu/gpu temperature/fan speed, but crashed again.

This is indeed true, calling PeekLv1() in clock readout functions seems to be the culprit as it doesn't happen when you recompile without that call. The reason for it happening even though you disabled it in config is because still calls those functions.
Good news is this is preventable by enclosing it in an if statement. Console seems to be 100% stable after testing it for several hours. Bad news is that it doesn't fix the underlying issue, but only bypasses it. Also no clock speeds for those models, at least for now.


Unable to run Jest with Create-React-App: "Not a test file"

Unless you unload your configuration, Create-React-App hides a lot of things in a React.js setup, including Jest. Under node_modules/react_scripts/package.json is where you will find Jest, not in your project root package.json. I was able to get Vim-Test working, but only after hacking the plugin, removing the package check from vim-test for Jest:

autoload/test/javascript/jest.vim

function! test#javascript#jest#test_file(file) abort
    return a:file =~# g:test#javascript#jest#file_pattern
    " \ && test#javascript#has_package('jest')  " <--- It fails here
endfunction

I guess some options are to remove the check, add a flag to be able to remove the check, add an alternate variable for a different package.json to look at (probably the recommended path?), or make the check aware of Create-React-App (not agnostic enough I am sure).
Let me know your thoughts and if you would want a PR.

We plan address with #185 which lets you set the runner when the detection does not work

I don't think it would be a good idea for vim-test to read package.json files from other dependencies, because then it would need to distinguish between dependencies and devDependencies (as in the latter case we shouldn't assume that jest is used in the main project as well, because it's just a development dependency of that package). This would mean we'd need to implement JSON parsing, or at least some smart parsing.
I agree with @codeinabox that https://github.com/janko-m/vim-test/issues/185 would be the correct solution. You could also just add jest to your project's package.json.

With jest there is likely to be a jest key for configuration in the package.json or a jest.config.js file.
https://jestjs.io/docs/en/configuration

Is this still an issue?

This in theory should no longer be an issue because #475 now only checks dependencies and devDependencies if you have Vim 8 or Neovim and #335 added support for React Scripts. Feel free to reopen this if it's still an issue

Hi @codeinabox, maybe there's still an issue with this.
I have a bunch of code exercises in subfolders of a repo. When the working directory is an exercise folder it works as expected but when the working directory is the parent repo directory I'm told "Not a test file".
Of course, I can keep updating the working directory but it's not ideal. Thought I'd raise as a potential vim-test improvement.

For me, I install the jest lib in global and set the runer to jest and it works for me
# terminal
yarn global add jest

# in vimrc
let test#javascript#jest#executable = "yarn test"
let g:test#javascript#runner = 'jest'


drivers: flash: spi_nor: select largest valid erase operation

The spi_nor erase op selection was based on the alignment of the end of the region to be erased. This prevented larger erase operations being selected in many cases
See https://github.com/zephyrproject-rtos/zephyr/issues/60904 for details and impact

Test failure is unrelated? Seems like this https://github.com/zephyrproject-rtos/zephyr/issues/60941

Test failure is unrelated? Seems like #60941

Was it the tlsTransport? That still seems to be somewhat problematic, but I am looking into it.
E.g.
https://github.com/zephyrproject-rtos/zephyr/actions/runs/5697038294/job/15443170454?pr=60942#step:13:282

@Crzyrndm could you add closes #60904 to your commit message.

@Crzyrndm could you add closes #60904 to your commit message.

Done

Test failure again unrelated?


Add support for indices.stats

Description
Describe what this change achieves.
Issues Resolved
Fixes #716
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Leaving open, take a look at integration tests.


chore(deps-dev): bump typescript from 3.9.7 to 4.0.5

👋  Hi, I didn't have any cause other than I bothered checking if there were any compatibility issues with upgrading while I was poking around. I did find one compatibility issue with the new delete checks, for which fixes are provided.
https://devblogs.microsoft.com/typescript/announcing-typescript-4-0-beta/#operands-for-delete-must-be-optional

This would need to follow #68 to avoid duplicating some of the changes in both PRs - rebasing on it should result in passing tests.

Thank you for your PR. There's nothing in TypeScript 4 that this project currently needs, though, so I'm going to close this for now.

Is there a reason you are resistant to keeping up with the current release? Eventually, you may want to use features available in a more recent version than you have currently, and it is likely that new TypeScript features will be adopted by some dependency (either direct or transient).

I'm being conservative with dependencies in general because, as a security-oriented collection of libraries, I want to keep things as predictable and reliable as possible. I'm totally down for the idea of keeping all third-party dependencies as up-to-date as possible, but in the case of SimpleWebAuthn I'm choosing to be more stringent because I want developers who use it to know that their RP's won't suddenly break.
I've also been burned in the past with accidentally publishing a release that broke because of third-party versioning I have no control over. I was fortunate enough to have time to catch it and fix the issue, but my supply of time lately has significantly diminished due to life events and so I'm hesitant to approve updates like this in case something breaks. It'd be on me to make time to fix the issue and I can't guarantee that right now.
I'm totally down for upgrading to TypeScript 4 when a new SimpleWebAuthn feature would benefit from it, but upgrading for the sake of upgrading is less desirable right now.

@jstewmon I changed my mind on this, after all of your other contributions this one seemed like a no-brainer! Thank you again for the push 💪


Add support for moving to sd-card

It would nice if andstatus could be completely moved to sd card to save space on internal memory

"Complete" moving is impossible due to Android limitation: Any application, which has a Widget, cannot be moved to SD card.
In Android 6 notions of "Internal" and "External" storage changed their meaning. "External" storage is no longer necessarily an "SD card".
More on this: https://github.com/andstatus/andstatus/issues/382
So actually for Android 6+ we need to change/extend existing "Use external storage" option to include "Store on external SD card" (or something like this...)


Warden::SessionSerializer - wrong number of arguments (2 for 1)

Error appears because I have two root paths
  authenticated :user do
    root 'application#index', as: :authenticated_root
  end

  root to: redirect('/auth/login'), as: :unauthenticated_root

When I remove path as authenticated_root error go away ( not unauthenticated_root, in this case error persist )

PS
Application path
devise_token_auth version 0.1.32.beta10 07ca81c (fetched from git)
When I installed devise_token_auth, I din't initialize devise, only devise_token_auth
also config.change_headers_on_each_request = false

I change routers.rb to
  root 'application#index'

  get "auth/login", to: "application#login" , as: "login"
  get "auth/facebook", to: "application#login", as: "facebook"
  get "auth/registration", to: "application#login", as: "registration"

and  I found that user_signed_in? raise that error too
Error stack:
ArgumentError - wrong number of arguments (2 for 1):
  devise (3.5.1) lib/devise.rb:457:in `block (2 levels) in configure_warden!'
  warden (1.2.3) lib/warden/session_serializer.rb:34:in `fetch'
  warden (1.2.3) lib/warden/proxy.rb:212:in `user'
  /home/bjorn/.bundler/ruby/2.2.0/devise_token_auth-07ca81c1d352/app/controllers/devise_token_auth/concerns/set_user_by_token.rb:32:in `set_user_by_token'
  /home/bjorn/.bundler/ruby/2.2.0/devise_token_auth-07ca81c1d352/lib/devise_token_auth/controllers/helpers.rb:115:in `current_user'
  /home/bjorn/.bundler/ruby/2.2.0/devise_token_auth-07ca81c1d352/lib/devise_token_auth/controllers/helpers.rb:111:in `user_signed_in?'
  actionpack (4.2.3) lib/abstract_controller/helpers.rb:67:in `user_signed_in?'
  app/views/layouts/_debug.slim:4:in `_app_views_layouts__debug_slim___2147060343315952264_69908902597980'
  actionview (4.2.3) lib/action_view/template.rb:145:in `block in render'
  activesupport (4.2.3) lib/active_support/notifications.rb:166:in `instrument'
  actionview (4.2.3) lib/action_view/template.rb:333:in `instrument'
  actionview (4.2.3) lib/action_view/template.rb:143:in `render'
  actionview (4.2.3) lib/action_view/renderer/partial_renderer.rb:339:in `render_partial'
  actionview (4.2.3) lib/action_view/renderer/partial_renderer.rb:310:in `block in render'
  actionview (4.2.3) lib/action_view/renderer/abstract_renderer.rb:39:in `block in instrument'
  activesupport (4.2.3) lib/active_support/notifications.rb:164:in `block in instrument'
  activesupport (4.2.3) lib/active_support/notifications/instrumenter.rb:20:in `instrument'
  activesupport (4.2.3) lib/active_support/notifications.rb:164:in `instrument'
  actionview (4.2.3) lib/action_view/renderer/abstract_renderer.rb:39:in `instrument'
  actionview (4.2.3) lib/action_view/renderer/partial_renderer.rb:309:in `render'
  actionview (4.2.3) lib/action_view/renderer/renderer.rb:47:in `render_partial'
  actionview (4.2.3) lib/action_view/helpers/rendering_helper.rb:35:in `render'
  app/views/layouts/application.html.slim:15:in `_app_views_layouts_application_html_slim__1088578683254279594_69908896638320'
  actionview (4.2.3) lib/action_view/template.rb:145:in `block in render'
  activesupport (4.2.3) lib/active_support/notifications.rb:166:in `instrument'
  actionview (4.2.3) lib/action_view/template.rb:333:in `instrument'
  actionview (4.2.3) lib/action_view/template.rb:143:in `render'
  actionview (4.2.3) lib/action_view/renderer/template_renderer.rb:66:in `render_with_layout'
  actionview (4.2.3) lib/action_view/renderer/template_renderer.rb:52:in `render_template'
  actionview (4.2.3) lib/action_view/renderer/template_renderer.rb:14:in `render'
  actionview (4.2.3) lib/action_view/renderer/renderer.rb:42:in `render_template'
  actionview (4.2.3) lib/action_view/renderer/renderer.rb:23:in `render'
  actionview (4.2.3) lib/action_view/rendering.rb:100:in `_render_template'
  actionpack (4.2.3) lib/action_controller/metal/streaming.rb:217:in `_render_template'
  actionview (4.2.3) lib/action_view/rendering.rb:83:in `render_to_body'
  actionpack (4.2.3) lib/action_controller/metal/rendering.rb:32:in `render_to_body'
  actionpack (4.2.3) lib/action_controller/metal/renderers.rb:37:in `render_to_body'
  actionpack (4.2.3) lib/abstract_controller/rendering.rb:25:in `render'
  actionpack (4.2.3) lib/action_controller/metal/rendering.rb:16:in `render'
  actionpack (4.2.3) lib/action_controller/metal/instrumentation.rb:44:in `block (2 levels) in render'
  activesupport (4.2.3) lib/active_support/core_ext/benchmark.rb:12:in `block in ms'
  /usr/lib/ruby/2.2.0/benchmark.rb:303:in `realtime'
  activesupport (4.2.3) lib/active_support/core_ext/benchmark.rb:12:in `ms'
  actionpack (4.2.3) lib/action_controller/metal/instrumentation.rb:44:in `block in render'
  actionpack (4.2.3) lib/action_controller/metal/instrumentation.rb:87:in `cleanup_view_runtime'
  activerecord (4.2.3) lib/active_record/railties/controller_runtime.rb:25:in `cleanup_view_runtime'
  actionpack (4.2.3) lib/action_controller/metal/instrumentation.rb:43:in `render'
  actionpack (4.2.3) lib/action_controller/metal/implicit_render.rb:10:in `default_render'
  actionpack (4.2.3) lib/action_controller/metal/implicit_render.rb:5:in `send_action'
  actionpack (4.2.3) lib/abstract_controller/base.rb:198:in `process_action'
  actionpack (4.2.3) lib/action_controller/metal/rendering.rb:10:in `process_action'
  actionpack (4.2.3) lib/abstract_controller/callbacks.rb:20:in `block in process_action'
  activesupport (4.2.3) lib/active_support/callbacks.rb:115:in `call'
  activesupport (4.2.3) lib/active_support/callbacks.rb:553:in `block (2 levels) in compile'
  activesupport (4.2.3) lib/active_support/callbacks.rb:503:in `call'
  activesupport (4.2.3) lib/active_support/callbacks.rb:88:in `run_callbacks'
  actionpack (4.2.3) lib/abstract_controller/callbacks.rb:19:in `process_action'
  actionpack (4.2.3) lib/action_controller/metal/rescue.rb:29:in `process_action'
  actionpack (4.2.3) lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
  activesupport (4.2.3) lib/active_support/notifications.rb:164:in `block in instrument'
  activesupport (4.2.3) lib/active_support/notifications/instrumenter.rb:20:in `instrument'
  activesupport (4.2.3) lib/active_support/notifications.rb:164:in `instrument'
  actionpack (4.2.3) lib/action_controller/metal/instrumentation.rb:30:in `process_action'
  actionpack (4.2.3) lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
  activerecord (4.2.3) lib/active_record/railties/controller_runtime.rb:18:in `process_action'
  actionpack (4.2.3) lib/abstract_controller/base.rb:137:in `process'
  actionview (4.2.3) lib/action_view/rendering.rb:30:in `process'
  actionpack (4.2.3) lib/action_controller/metal.rb:196:in `dispatch'
  actionpack (4.2.3) lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
  actionpack (4.2.3) lib/action_controller/metal.rb:237:in `block in action'
  actionpack (4.2.3) lib/action_dispatch/routing/route_set.rb:76:in `dispatch'
  actionpack (4.2.3) lib/action_dispatch/routing/route_set.rb:45:in `serve'
  actionpack (4.2.3) lib/action_dispatch/journey/router.rb:43:in `block in serve'
  actionpack (4.2.3) lib/action_dispatch/journey/router.rb:30:in `serve'
  actionpack (4.2.3) lib/action_dispatch/routing/route_set.rb:821:in `call'
  omniauth (1.2.2) lib/omniauth/strategy.rb:186:in `call!'
  omniauth (1.2.2) lib/omniauth/strategy.rb:164:in `call'
  omniauth (1.2.2) lib/omniauth/builder.rb:59:in `call'
  warden (1.2.3) lib/warden/manager.rb:35:in `block in call'
  warden (1.2.3) lib/warden/manager.rb:34:in `call'
  rack (1.6.4) lib/rack/etag.rb:24:in `call'
  rack (1.6.4) lib/rack/conditionalget.rb:25:in `call'
  rack (1.6.4) lib/rack/head.rb:13:in `call'
  actionpack (4.2.3) lib/action_dispatch/middleware/params_parser.rb:27:in `call'
  actionpack (4.2.3) lib/action_dispatch/middleware/flash.rb:260:in `call'
  rack (1.6.4) lib/rack/session/abstract/id.rb:225:in `context'
  rack (1.6.4) lib/rack/session/abstract/id.rb:220:in `call'
  actionpack (4.2.3) lib/action_dispatch/middleware/cookies.rb:560:in `call'
  activerecord (4.2.3) lib/active_record/query_cache.rb:36:in `call'
  activerecord (4.2.3) lib/active_record/connection_adapters/abstract/connection_pool.rb:653:in `call'
  activerecord (4.2.3) lib/active_record/migration.rb:377:in `call'
  actionpack (4.2.3) lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
  activesupport (4.2.3) lib/active_support/callbacks.rb:84:in `run_callbacks'
  actionpack (4.2.3) lib/action_dispatch/middleware/callbacks.rb:27:in `call'
  actionpack (4.2.3) lib/action_dispatch/middleware/reloader.rb:73:in `call'
  actionpack (4.2.3) lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
  better_errors (2.1.1) lib/better_errors/middleware.rb:84:in `protected_app_call'
  better_errors (2.1.1) lib/better_errors/middleware.rb:79:in `better_errors_call'
  better_errors (2.1.1) lib/better_errors/middleware.rb:57:in `call'
  actionpack (4.2.3) lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
  web-console (2.2.1) lib/web_console/middleware.rb:39:in `call'
  actionpack (4.2.3) lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
  railties (4.2.3) lib/rails/rack/logger.rb:38:in `call_app'
  railties (4.2.3) lib/rails/rack/logger.rb:20:in `block in call'
  activesupport (4.2.3) lib/active_support/tagged_logging.rb:68:in `block in tagged'
  activesupport (4.2.3) lib/active_support/tagged_logging.rb:26:in `tagged'
  activesupport (4.2.3) lib/active_support/tagged_logging.rb:68:in `tagged'
  railties (4.2.3) lib/rails/rack/logger.rb:20:in `call'
  quiet_assets (1.1.0) lib/quiet_assets.rb:27:in `call_with_quiet_assets'
  actionpack (4.2.3) lib/action_dispatch/middleware/request_id.rb:21:in `call'
  rack (1.6.4) lib/rack/methodoverride.rb:22:in `call'
  rack (1.6.4) lib/rack/runtime.rb:18:in `call'
  activesupport (4.2.3) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
  rack (1.6.4) lib/rack/lock.rb:17:in `call'
  actionpack (4.2.3) lib/action_dispatch/middleware/static.rb:116:in `call'
  rack (1.6.4) lib/rack/sendfile.rb:113:in `call'
  railties (4.2.3) lib/rails/engine.rb:518:in `call'
  railties (4.2.3) lib/rails/application.rb:165:in `call'
  rack (1.6.4) lib/rack/lock.rb:17:in `call'
  rack (1.6.4) lib/rack/content_length.rb:15:in `call'
  rack (1.6.4) lib/rack/handler/webrick.rb:88:in `service'
  /usr/lib/ruby/2.2.0/webrick/httpserver.rb:138:in `service'
  /usr/lib/ruby/2.2.0/webrick/httpserver.rb:94:in `run'
  /usr/lib/ruby/2.2.0/webrick/server.rb:294:in `block in start_thread'

Handle with this by downgrading Rails from 2.2.3 to 2.2.2
But there was another error


Add LSP package name to the readme

The README contains no direct reference to the language server itself. Given past  renames and the legacy Vetur, it's not straightforward to fine the correct package online.
Include the LSP and its package name in the README. This will assist people trying to install the language server.
Additionally, as of 2.0.0, a plug-in is required for TypeScript support. This is mentioned in the changelog, but the name of the plug-in itself is not made evident anywhere. Also add this to the README.

I think you got that backwards? As of 2.0, the plugin is no longer required?


Add .gitignore file to the repo

The pycache directory present in the repo is not necessary. Creating a .gitignore file and adding __pychache__ will do the trick.

Fixed. Thanks!


request prepare route only on cloud5

this route does not exist (yet) in cloud6

@MaximilianMeister should it rather be added to cloud6 ? or is it not needed for the cloud7 update?

should it rather be added to cloud6 ? or is it not needed for the cloud7 update?

I would like to see if it is needed while fixing the cloud6 to 7 upgrade path. for now it would be ok to use it only on cloud5.

+1

prepare was executed in the gating (upgrade 5 to 6)
subsequent gating failure is the same as in the other cloud-mkcloud6-job-upgrade builds

sorry for stressing but this blocks my work on the 6to7 upgrade a bit
@dirk @jdsn @rsalevsky can you please review?

Makes sense. +1

LGTM, but would prefer to have @jdsn give a +1 (to make sure it's the right way forward)

LGTM, but would prefer to have @jdsn give a +1 (to make sure it's the right way forward)

It is more a crowbar question i would say, as we don't have this route (yet) in cloud6. in fact this route only exists on cloud 5 and gets executed for cloud 6 and 7.
but thanks for the input. I will ping @jdsn

I will rather add the route for cloud 6 now in crowbar, and then we will probably not need this anymore. thanks for the hint @dirkmueller

even if it is not tested yet, https://github.com/crowbar/crowbar-core/pull/430 is the favoured way to go here
closing


Search Result Reset

I have a scene in one of our apps that contains (2) tables both having a search field for data each contains.  Lately I've noticed that if I search in table 1 as an example "test1" any and all results are shown.  If I then try a search as an example "test2" in table 2, any and all results are shown.  Now here's the problem, if I hit the "reset" button next to the search field for table 1, it clears the entry (ie test1) and brings table back to normal just like it should but it will also clear the search bar for table 2 within the 10 seconds, which is what I have our auto refresh set to for both views.  The weird thing is, even though the data has been cleared in both search fields by me pressing the reset on table 1's search field, the reset button is still visible on the search field that wasn't pressed, in above example "table 2".
I've never noticed this before and didn't know if there was a change to KTL that is effecting this.
Hoping there is a fix... JON

Hi Jon
We will see if we can recreate this tomorrow.
Craig

Hi Jon
This might be one for @cortexrd. I have replicated this issue (using KTL version 0.19.5).
When we turned off the auto refresh this issue didn't occur.
Do you know when you started to see this issue @jbk68?
Craig

Hey Craig, thanks for taking the time on this issue.  To answer your question, I just noticed it a few days ago but for all I know, it could have been that way for a while.  It's kind of unique for me to be using both search fields on the same view for various searches at the same time.  I do know however in the past I never saw this issue.

Hi guys,
This was a Knack bug.  You can see it by using the Bypass KTL feature from the Version Info Bar and KTL Developer Tools panel:

The bug is still there, without the KTL.
But the good news is that I've found a solution!
It will be in next release.
In the meantime you can test it by clicking Debug this device and OK (from same panel above).  This switches to the latest "dev" version of the KTL, before an official release, for testers.
To go back to normal, click the button again but Cancel this time.
Norm

Hey Norm, I've also noticed another issue when using keyword _ar (my favorite ktl feature) with a view with a table that has multiple columns that requires the lower scroll bar.
When the user is viewing a table that requires the use of the scroll bar, the table view will be reset when the page refreshes.  So if I have auto refresh set to 10 seconds and user is view data to the right side of table, table view resets and user has to scroll to the right again to view data only to be reset again in 10 seconds.
If I remove keyword _ar, user can view data without the table view resetting and move back to the left.
Looking forward to your solution to initial issue with keyword _ar and hoping you have a solution to this issue I just posted.
Thanks... JON

Done - I have fixed this a moment ago.
Will be in next release.
Norm

Thank you sir.  Look forward to the fix... JON

Released just now.  v0.21.2
Enjoy,
Norm

Hey Norm, v021.2 appears to have fixed the scrolling issue using the keyword _ar, but it didn't fix the initial issue of this post of when there is multiple search field on a scene and user "reset" search criteria of one it still is resetting they other search fields and leaving the "reset" button on the second one cleared.
Not sure if this update was supposed to fix that.
Thank you for fixing the scrolling issues... JON

Here it works well.  Just tested again.
Can you give me access to a test page?
It may have something to do with the app style setting somewhere.
Norm

Let me put one together and get back to you.
For security reasons, do you have an email I can sent link and credentials to?

Sure<EMAIL_ADDRESS>Norm


CUDA not available causes SIGSEV

When CUDA is not available at runtime, but cv-rs is built with the "cuda" feature enabled, then the program emits this message: OpenCV(3.4.1) Error: Gpu API call (no CUDA-capable device is detected) in allocate. Then an exception is thrown with that error which is not caught and blows up the stack. We need to catch exceptions for when CUDA is not available and either panic! on the Rust side, or give Result back via the API.

CResutlt has relevant method to catch it. We could just use it. Panic may be a bad thing since GPU may appear after (e.g. dynamic videocard switch on laptop).


Stripe connnect

Does this support stripe connect?

What do you mean?

Tell me more about your exact needs, I'm also interested in leveraging this so I can start implementing the ones that are your priorities, so I'll learn my way in to use it myself afterwards.

I covered what I need in v1 so... if you have ideas feel free!

@Immortalin  What are your interests in connect? I'm building a platform on top of stripe where every user can have their own account. So connect looks like the way to go for that!

@nicrioux I am building an ecommerce marketplace type of service. The usages for stripe connect are pretty broad. I am mainly using it in place of PayPal Adaptive Chained payments. For the latter, it is mainly used for marketplaces such as eBay etc.

@Immortalin Are you more interested in the standalone or the managed connect ?

@nicrioux probably standalone as the risks of a managed account outweighs a standalone one.

Do you have something implemented already? Or is it still in planning stage?

@Immortalin
Do you have something implemented already? Or is it still in planning stage?

@nicrioux working on it right now. We can chat over irc if you want

@Immortalin using this project as the base? or from something else?

I think it could be pretty neat to add this as a feature of stripity

@nicrioux using the this project to implement the payments bit. User sells product-> service gets a percentage, user gets the rest. Something like this

Oh that would be nice!

I was thinking about this. Wouldn't it only involve creating an additional "key" variable on make_request (and all who references it) to provide a path for the stripe key? In a multi-tenant scenario, the key would be provided but can also be omitted to default to the config/env key of the owning tenant. Is your implementation more involved then this?

*a path for the stripe key to flow through ...

All I need is the subs/charge/customer stuff... I don't use the payouts. Happy to add you to commit if you want to give it a go.

Good time to take advantage of elixir's multiple dispatch ;)

https://github.com/robconery/stripity-stripe/pull/12

Almost done on this! The Connect feature simplify the usage of connect by: 1- generating the workflow start button url. Then on workflow end callback from stripe, you call our Stripe.Connect.get_token return_code_from_stripe to perform the oauth callback to stripe. There's also a method to get the full oauth response to store local to the platform. I'll also finish implementing the key flow thru on the rest of the API.

:+1:

Fully resolved. Might need to be iterated on a bit to refine. Standalone and managed supported. All API modules have functions which accepts an api key. A phoenix demo has been created to demonstrate the integration.

@nicrioux thanks! :D


feat: add goreleaser workflow

This PR adds goreleaser workflow and config.

cc @apelisse

(i didn't try it, could have typos in the config 🤞)

@alexzielenski let me know if you want more config, goreleaser can use cosign, build/sign images with ko, publish on brew, etc...

Hi all, thanks for starting this PR. What's required to get this PR merged? It would be very helpful to have released binaries of kubectl-validator.

/approve
/lgtm

OK, let's try it now!

I just pushed v0.0.2 (from the same commit as v0.0.1) and it doesn't look like it's triggering: https://github.com/kubernetes-sigs/kubectl-validate/actions/workflows/release.yaml

Thanks for trying! Our company is using a forked release so we are not blocked. We'll shift to the official release whenever that's ready.
kubectl-validate has caught numerous issues in our dev workflow. Thanks for creating this super useful tool!


Add support for packages that contain their own examples (ex: hand physics) and some script cleanup

This change provides a generic implementation to support packages that contain their own example projects (ex: hand physics service).
The hand physics package.json was updated to create the samples entry and to not include the Examples folder (it would conflict if the example is imported into the project)
While making this change, some script cleanup was performed (we do not need examplefolderpostupm.ps1).

/azp run

/azp run

/azp run


Add more voice model options

Description
Made frontend changes to allow users to select a voice model (male or female) for the TTS. For backend change: https://github.com/PeoplePlusAI/sunva/pull/15
Motivation and Context
This change is required to provide users with the option to choose between male and female voices in TTS, enhancing the user experience by offering customization options.
How Has This Been Tested?
Manually tested the changes by selecting options and checking for any bugs.

Done!


Event stream partitioning.

The current event stream API does not allow specification of a stream within an application. It is assumed that every application has exactly one stream (as is the case with Verity).
We need to support multiple streams per application. This could be done by adding an additional piece of information to the API - a "partition ID" or "stream ID".
Another approach would be to simply rename "application ID" to "stream ID" within the consume request. Verity would simply use the application as the stream ID, whereas Veracity would be free to expose multiple streams with other IDs.
Regardless of the approach taken, the event stream API will need a way to enumerate the available streams.
There may also be a requirement to include "site" information in the API.

A new gRPC API has been added to enginekit. No site related functionality has been added (and may not be necessary in this API, not sure yet).


How use a colunm title different of colunm name

I want use a different name for title and name. That are possible?
Something like:
const column = [
{
name: 'columnName',
title: 'Column Title',
options: {
filter: true,
sort: true,
display: true
}
}
}
]

I have the same issue. Tried customHeadRender, but that's way too much when I simply want to replace the text

Thank you. It worked.

How did you make it work?

this is available by using the label property:
    const columns = [
      {
        name: "name",
        label: "Name",
    ];


Nuxt generate not fetching api client side

Environment

Operating System: Darwin
Node Version:     v18.17.1
Nuxt Version:     3.14.159
CLI Version:      3.15.0
Nitro Version:    2.10.4
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      default
Runtime Modules:  -
Build Modules:    -

Reproduction
https://codesandbox.io/p/devbox/rcx6q6
https://web547client.vermillion.com.tw/test/
Describe the bug
When using "nuxt generate" to generate prerender pages, the api is not called between pages.
https://github.com/user-attachments/assets/27148279-51ee-4c41-abb7-ad05a1313fe1
Additional context
No response
Logs
No response

The following Reproduction uses the previously created 3.11.2 version project to modify it into the same program code structure as above. The generated file can fetch api data on the client side very well, but it will become invalid once nuxt update to the higher version.
https://codesandbox.io/p/devbox/3-11-2-worked-fine-nuxt-generate-not-fetching-api-client-side-kprlxx
https://web547client.vermillion.com.tw/test2/news

I have the same issue. Only 3.11 works. From 3.12 on this doesn't work anymore.

This is a documented feature - and shouldn't have changed in in Nuxt v3.12 - data is not fetched when navigating to a page that was statically generated. Instead, the data that was present at generate time is used.
If you do not want this behaviour, you can set experimental.payloadExtraction to false.

This is a documented feature - and shouldn't have changed in in Nuxt v3.12 - data is not fetched when navigating to a page that was statically generated. Instead, the data that was present at generate time is used.
If you do not want this behaviour, you can set experimental.payloadExtraction to false.

that worked for me, yes. But to me it wasn't clearly documented enough. I didn't understand what this feature really did. Your comment clarified this in a way that isn't in the docs.


chore: Update agentbaker e2e with image on 05202024

What type of PR is this?
/kind test

What this PR does / why we need it:
Updating agentbaker e2e images with latest image  (05/20/2024) as the previous one is quite old. This allows to test e2es with newer components in the VHD.
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3032

Relevant Lines:
3937

💛  - Coveralls

LGTM, any reasons why those number are not the same as the release number are use eternally ?

we're taking directly from the staging gallery in MSFT here - the versions we upload there don't follow our official versioning format


Fix segfault when reading gif with Comment Extension and no Comment Data

Description
The GIFInput::read_gif_extension method segfaults when reading a GIF that has a Comment Extension with no Comment Data. I don't know how the problem GIF was generated and unfortunately I can't share it but it seems valid and can be opened without issue in other applications.
Tests
Prior to the change OpenImageIO was segfaulting as soon as the image was opened, now it opens without issue.
Checklist:

[x] I have read the contribution guidelines.
[ ] If this is more extensive than a small change to existing code, I
have previously submitted a Contributor License Agreement
(individual, and if there is any way my
employers might think my programming belongs to them, then also
corporate).
[ ] I have updated the documentation, if applicable.
[ ] I have ensured that the change is tested somewhere in the testsuite
(adding new test cases if necessary).
[x] My code follows the prevailing code style of this project.

LGTM, good catch!
Merging and also backporting into release branch...


chanjo generates errors instead of help text

$chanjo
Traceback (most recent call last):
  File "/mnt/hds/proj/cust003/develop/modules/miniconda2/envs/mip4.1/bin/chanjo", line 11, in <module>
    load_entry_point('chanjo==4.0.0', 'console_scripts', 'chanjo')()
  File "/mnt/hds/proj/cust003/develop/modules/miniconda2/envs/mip4.1/lib/python2.7/site-packages/click/core.py", line 716, in __call__
    return self.main(*args, **kwargs)
  File "/mnt/hds/proj/cust003/develop/modules/miniconda2/envs/mip4.1/lib/python2.7/site-packages/click/core.py", line 695, in main
    with self.make_context(prog_name, args, **extra) as ctx:
  File "/mnt/hds/proj/cust003/develop/modules/miniconda2/envs/mip4.1/lib/python2.7/site-packages/click/core.py", line 620, in make_context
    self.parse_args(ctx, args)
  File "/mnt/hds/proj/cust003/develop/modules/miniconda2/envs/mip4.1/lib/python2.7/site-packages/click/core.py", line 1009, in parse_args
    echo(ctx.get_help(), color=ctx.color)
  File "/mnt/hds/proj/cust003/develop/modules/miniconda2/envs/mip4.1/lib/python2.7/site-packages/click/core.py", line 495, in get_help
    return self.command.get_help(self)
  File "/mnt/hds/proj/cust003/develop/modules/miniconda2/envs/mip4.1/lib/python2.7/site-packages/click/core.py", line 824, in get_help
    self.format_help(ctx, formatter)
  File "/mnt/hds/proj/cust003/develop/modules/miniconda2/envs/mip4.1/lib/python2.7/site-packages/click/core.py", line 839, in format_help
    self.format_options(ctx, formatter)
  File "/mnt/hds/proj/cust003/develop/modules/miniconda2/envs/mip4.1/lib/python2.7/site-packages/click/core.py", line 950, in format_options
    self.format_commands(ctx, formatter)
  File "/mnt/hds/proj/cust003/develop/modules/miniconda2/envs/mip4.1/lib/python2.7/site-packages/click/core.py", line 995, in format_commands
    cmd = self.get_command(ctx, subcommand)
  File "/mnt/hds/proj/cust003/develop/modules/miniconda2/envs/mip4.1/lib/python2.7/site-packages/chanjo/cli.py", line 42, in get_command
    return commands[name].load()
  File "/mnt/hds/proj/cust003/develop/modules/miniconda2/envs/mip4.1/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2291, in load
    return self.resolve()
  File "/mnt/hds/proj/cust003/develop/modules/miniconda2/envs/mip4.1/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2297, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/mnt/hds/proj/cust003/develop/modules/miniconda2/envs/mip4.1/lib/python2.7/site-packages/chanjo/init/cli.py", line 6, in <module>
    from path import path
ImportError: cannot import name path

This is because path is not installed. Try pip install path and try again.
We should include this in requirements if it is not already done

pip install path
Downloading/unpacking path
  Could not find any downloads that satisfy the requirement path
Cleaning up...
No distributions at all found for path
Storing complete log in /home/henrik.stranneheim/.pip/pip.log

Sorry, it should probably be pip install Path

Nope 😄
$ pip install Path
Downloading/unpacking Path
  Could not find any downloads that satisfy the requirement Path
Cleaning up...
No distributions at all found for Path
Storing complete log in /home/henrik.stranneheim/.pip/pip.log

Ok let's wait for @robinandeer then

yeah it's called path.py but we need to update the code to correct the import


Add pydantic<2 pin

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Notes:

fixes #9 (partially)

@conda-forge-admin please rerender

https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/475 was merged, so this isn't high priority, but:
@conda-forge/copier ready for review


Code stops working on master

Open FCS repo folder
Open TypeChecker.fs file
Tooltips start working almost immediately (wow)
Few seconds after that Code UI stops working completely (no reaction on mouse / keyboard)

Pressing "Reopen" does not help. Something with just merged websockets maybe?

Last thing it outputs:

Nothing happening in plugin should be able to kill whole VSCode (plugins are running in separate processes).
Only time I've seen this, was when someone showed me some super long CodeLenses. Maybe that's the problem? Try turning off CodeLens in settings and then check if error can be reproduced.

No, turning off CodeLens does not help. Code loads 1 CPU core at 100%:

I doubt it's performance related.

The only thing I've noticed when I was trying to reproduce it was noticeable performance problem (on editor side) when FSAC was returning many errors for multiple files. My current theory right now is that crash can be extreme example of it /shrug.

Should be better in 2.9.4


Empty struct init

Fixes https://github.com/hylo-lang/hylo/issues/997
Suspect there is a better way not to leak abstraction and infer without saving state

Weird that this doesn't compile on the CI :thinking: I've successfully recompiled twice now locally and verified I am on the same commit be6d4684. I nuked my .build to ensure I wasn't using a stale cached artefact. Weird. Suspect it may be the CI system's cache...

Will try to build on my system.

I get the same error as CI on my system:
/Developer/hc/Sources/IR/Module.swift:297:7: error: missing argument for parameter 'isEmptyInit' in call
      isSubscript: false,
      ^
      isEmptyInit: <#Bool#>,

Another approach you may consider is to have the emitter insert make_state [initialized] %self before the return instructions of an empty initializer. The instruction will "convince" the borrow checker that self is initialized and it will have no effect if self is initialized explicitly.

This approach seems cleaner. Is there any downsides to emitting the make_state [initialized] %self directive. Perhaps it has some other side effects?
Carving out a special case for empty initializers when doing initialization checking looks a bit hacky. I guess the question is whether it's more hacky than the special case for injserting the make_state [initialized] %self directive. Will check both (already pushed the first option).

This approach seems cleaner. Is there any downsides to emitting the make_state [initialized] %self directive? Perhaps it has some other side effects?

Not really. mark_state is a ghost instruction. It has no operational semantics. The only requirement is that we should use it carefully because it's essentially a way to tell the borrow checker "trust me, I know this think is [un]initialized".

Carving out a special case for empty initializers when doing initialization checking looks a bit hacky.

Unfortunately I think we need to carve out an exception. The rationale is that in other places we do want to track the logical initialization of empty objects.
public fun main() {
  var x: Void
  print(x) // error: 'x' is not initialized
}

Will check both (already pushed the first option).

Okay, let me know if you need any help.

Closed in favour of https://github.com/hylo-lang/hylo/pull/1016


Security Address

Hello!
I may have found a security issue in latest version of Installer. Following responsible disclosure, is there an email or other private channel where I could share the details?
Thank you

This project now has private vulnerability reporting enabled.
Please reach out via the mechanisms described in https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability#privately-reporting-a-security-vulnerability.


tests: Add test to validate that generate_data() is generating the files expected

Provides tests to validate that generate_data() API is generating the files expected. It:

Uses basic Pipeline "simple"
Mocks out the LLMBlock _generate() to return generated output from Model (data captured when generate process run fully)
Tests with taxonomies of compositional skills, and knowledge
Verifies all of the files expected are there, with some basic validation of contents

Closes #208

@hickeyma I went down the pretty miserable rabbit hole of validating the contents of the output files, since my sense is that's where a lot of the brittleness with this code is going to be. What do you think?

went down the pretty miserable rabbit hole of validating the contents of the output files, since my sense is that's where a lot of the brittleness with this code is going to be. What do you think?

Thanks @markmc for pushing the changes. I was between 2 minds about trying to keep the pipeline as true as possible, thereby avoiding as much mocking as possible. Faking v Making argument! Lets go with the mocking of the _generate().
 They tests are a great addition, thanks.

left a few comments, mostly stylistic. Otherwise, everything looks good!

Thanks @khaledsulayman  for the feedback. I'll update your comments shortly.

@markmc This should be ready for merging. What do you think?


feat: add code sprint 2024 blog post

This is the first draft for the geostyler code sprint blog post.
TODOs

add more detailed info about the capabilities of the new ArcGIS parser.

Just a few screenies:

Thanks for the feedback. I applied your suggestions and added a list of the related releases that we will publish throughout the day.
Is there anything else that should be changed?

Looks good @jansule - thanks!
Could you add a mention to @compassinformatics as they paid for some of my time attending the sprint?

Bad timing @geographika :grinning: But sure, I can add this


Move to yiisoft/translator

Maybe simple implementations of translator interfaces (without dependencies) place in yiisoft/translator itself, not separately?

Now simple formatter is really a simply, but when will be a complex? Today it's may be a good idea. After this package may will be split(excluded formatter)

It should not become any more complex but I wonder how to ensure automatic-configuration to use intl one when both packages are required.

When move this package to yiisoft/translator - we will have problem with usaging intl-package after install yiisoft/translator-formatter-intl.
Now formatters automatically configuring with composer require and this be simple


Netbox 2.10 needs manage.py trace_paths run on upgrade

Looking at the upgrade.sh for Netbox 2.10 it needs to run manage.py trace_paths --no-input once to populate the new dcim_cablepath table, the manage.py migrate step doesn't do it.  In addition there are a couple of other commands in the update script to invalidate caches that probably make sense to run on updates.

sorry for the late response, just cleaning up email at end of week
I can git blame the upgrade.sh script
As far as the trace_paths looks like it was introduced in 2.10.0 https://github.com/netbox-community/netbox/commit/f560693748d1f35e79ad9d006a8a9b75ef5ae37b
Looks like the cache invalidation commands were added for Netbox 2.6.13 https://github.com/netbox-community/netbox/commit/685cf50268858c3ea211907ba63a69638c9cef8f
—
Mark Tinberg @.***>
Division of Information Technology-Network Services
University of Wisconsin-Madison

From: Musee Ullah @.***>
Sent: Wednesday, March 24, 2021 4:17 PM
To: lae/ansible-role-netbox
Cc: Mark Tinberg; Author
Subject: Re: [lae/ansible-role-netbox] Netbox 2.10 needs manage.py trace_paths run on upgrade (#119)
@lae approved this pull request.
Overall lgtm. I'll merge in a few days if I don't hear back (and check the things I mentioned in the review).

In tasks/deploy_netbox.ymlhttps://github.com/lae/ansible-role-netbox/pull/119#discussion_r600877616:

@@ -122,6 +122,13 @@
app_path: "{{ netbox_current_path }}/netbox"
virtualenv: "{{ netbox_virtualenv_path }}"

name: Trace missing cable paths for NetBox

 django_manage:

   command: "trace_paths --no-input"

   app_path: "{{ netbox_current_path }}/netbox"

   virtualenv: "{{ netbox_virtualenv_path }}"

 when: "netbox_stable_version is version('2.10.0', '>=')"

Can you also add a check for the git commit hash that introduces this change? You can reference commit 192137bhttps://github.com/lae/ansible-role-netbox/commit/192137b9834ee21e979b6ec4d32da7cc6bd729ea to see how it's been implemented previously.

In tasks/deploy_netbox.ymlhttps://github.com/lae/ansible-role-netbox/pull/119#discussion_r600879229:

@@ -142,5 +149,18 @@
app_path: "{{ netbox_current_path }}/netbox"
virtualenv: "{{ netbox_virtualenv_path }}"

name: Clear stale content types in NetBox

 django_manage:

   command: "remove_stale_contenttypes --no-input"

   app_path: "{{ netbox_current_path }}/netbox"

   virtualenv: "{{ netbox_virtualenv_path }}"

name: Clear cached data in NetBox

 django_manage:

   command: "invalidate all"

   app_path: "{{ netbox_current_path }}/netbox"

   virtualenv: "{{ netbox_virtualenv_path }}"

Will these two commands work for older versions of NetBox/Django (even if they might not do anything)? If they work for like the releases in the past year or two then they're fine, otherwise it might be appropriate to also have a version check here.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/lae/ansible-role-netbox/pull/119#pullrequestreview-620235890, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAS7UM6GBFZ6PIWTHTTEM63TFJJGLANCNFSM4U3OYGVA.

@mtinberg - if you were to add those version/hash checks that @lae mentioned on those two tasks, this PR should be good to go.


Evaluate Palantir Java Format

This PR evaluates the effect of the following Spotless configuration on log4j-api:
<java>
  <palantirJavaFormat>
    <version>2.38.0</version>
  </palantirJavaFormat>
</java>

The log4j-api source code is about 33k LOCs.

Closing since it has been integrated in apache/logging-parent#59


"Loss is nan" errors

Thanks for making your code and models available! I sometimes get "Loss is nan, stopping training" errors during training when I train a model with DINO (I suspect this is due to some kind of runaway dynamics making logits inf). I'm not sure if there's a consistent pattern to when exactly I get this error, but I was wondering if this is a known, common issue and what I can do to avoid it. Thanks!

Closing this as this seems to be a duplicate of #58


Design doc: scikit-learn-dask thoughts

We shouldn't merge this.  These are just some loose thoughts.  Comments welcome.
@ogrisel @amueller @cowlicks

@amueller and I have a working prototype for pipeline.

Prototype lives here https://github.com/mrocklin/dask-learn

Closing in favor of https://github.com/blaze/dask/pull/743


chore: Bump required version of ESLint

The CI / Floating Dependencies test is going to fail until babel/babel#17001 is merged and released.


update spec_version:46

reward_mapping will only use the latest key (https://github.com/deeper-chain/deeper-chain/pull/373[)](https://github.com/deeper-chain/deeper-chain/commit/1d337464f299f810f5d5f40c11ca3f125eb6e880)

Codecov Report
Patch coverage: 18.18% and project coverage change: -0.05 :warning:

Comparison is base (1cdada1) 63.69% compared to head (a9faee8) 63.64%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #374      +/-   ##
==========================================
- Coverage   63.69%   63.64%   -0.05%
==========================================
  Files          75       75
  Lines       21427    21448      +21
==========================================
+ Hits        13647    13650       +3
- Misses       7780     7798      +18

Impacted Files
Coverage Δ

pallets/credit-accumulation/src/lib.rs
38.41% <0.00%> (-4.74%)
:arrow_down:

runtime/src/lib.rs
10.99% <ø> (ø)

pallets/deeper-node/src/lib.rs
93.02% <100.00%> (ø)

primitives/src/lib.rs
76.92% <100.00%> (+6.92%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


The repository need an update with the newer versions of pytorch

There are many libraries deprecated that are used here and cant be used with pytorch 1.11 and higher (as TH/TH.h). The repository "https://github.com/lbin/DCNv2/tree/pytorch_1.11" has been updated with these updates for making this code suitable for newer pytorch versions.

Great Find @Peanpepu!


FaderPort Control broken on FP16

Thanx, will add it to the list

Thank you!  I'll keep you apprised of any FP16 issues I run into, which are really few and far in between besides this and the automation issue!

1.0.1 fixed it!


StaticFile.fromPath allows for very easy directory traversal

For example with this endpoint
case GET -> Root / name  =>
  StaticFile.fromPath(Path(s"./$name")).getOrElseF(NotFound())

One could easily read system files like /etc/passwd see File path traversal.
A simple solution is to employ the strategy explained at the bottom of the article (in Java):
File file = new File(BASE_DIRECTORY, userInput);
if (file.getCanonicalPath().startsWith(BASE_DIRECTORY)) {
    // process file
}

Or in other words StaticFile could receive two more arguments: baseDir: Path, onInvalidPath: Path => F[Response[F]]. If the above check fails then onInvalidPath would be called.

Also FileService attempts to protect from directory traversal with this code:
      val resolvePath: F[Path] =
        if (request.pathInfo.isEmpty) F.pure(rootPath)
        else {
          val segments = request.pathInfo.segments.map(_.decoded(plusIsSpace = true))
          F.catchNonFatal {
            segments.foldLeft(rootPath) {
              case (_, "" | "." | "..") => throw BadTraversal
              case (path, segment) => path.resolve(segment)
            }
          }
        }

      val matchingPath: F[Option[Path]] =
        for {
          path <- resolvePath
          existsPath <- Files[F].exists(path, false)
        } yield
          if (existsPath && path.startsWith(rootPath))
            Some(path.absolute.normalize)
          else None

However if one of the segments is ..%2F..%2F..%2F..%2F..%2F.. then path.resolve will happily resolve it.


Form checkbox group bug

See attached gif.

Can click outside of a checkbox and the first input will be selected
Clicking any checkbox looks also interacts with the first checkbox, though it's selected state is not affected.

https://dl.dropboxusercontent.com/s/yow9zebvlc020d3/FFD7C45E-CAB4-4C6E-9D7B-3094C181B5D8-9068-000032D7533019C0.gif?dl=0

I think this issue has something to do with labels

fixed in commit 81db000


CI Tests fail on pull request

The jest CI tests fail when creating a pull request to the repo, see Actions & pull requests.
They fail because there are no tests to run.
I propose to disable the workflow until there are some tests to run.

Done! We want to refactor this repo to look more like this one. When that happens, we'll also solve this.


[WIP] Team total results for Salmon Run

A user contacts (requests) to me via Twitter.
Add Team total Golden/Power Eggs to shift list.
Add Total results to details view.

Task list

[x] Team total Golden Eggs
[ ] Team total Power Eggs
[x] Total results to details view


chore(main): release 1.266.0

When this PR is merged, a new tagged release will be created with the notes below.
1.266.0 (2024-09-16)
Features

Removing long task (#1153) (304e395)

Bug Fixes

Remove nullish coalescing inside getter (#1180) (e537359)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/newrelic/newrelic-browser-agent/releases/tag/v1.266.0 :sunflower:


Need to update nannyml rich version to support >=13.0.0

Facing compattiblity issues when installing with evidently latest tag release.

@nnansters Can you please help update the dependency?

Should be fixed in our brand new 0.12.0 release!

Great! Thanks @nnansters looking forward to the release.

You can try it right now!


Galaxy Fold 4 - Not able to use the camera to scan receipt

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

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

Tap global create
Tap submit expense
Select scan option
Focus on the receipt and tap on the button to capture picture

Expected Result:
Able to scan and receipt created
Actual Result:

Camera didn't capture receipt and throwing camera error
Apparently receipts were uploaded and in the OldDot showing the created IOUs
nOTE: Seems happening with all fold phones

Workaround:
unknown
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/38435837/2e6fd0d2-beda-4d1b-ad77-a9d73f15646a

View all open jobs on GitHub

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

@mrousavy are you familiar with this issue perhaps?

Heh, good question.
@danieldoglas could you capture device logs while doing this please? So that we can know the specific error.

Asking for a re-test here: https://expensify.slack.com/archives/C9YU7BX5M/p1716230829161089

Issue is not reproducible on Galaxy Fold 4.
https://github.com/Expensify/App/assets/93399543/1b218645-875c-469d-aab1-c90fd7af8480

Ok thanks! Going to close. @danieldoglas feel free to reopen if you're still seeing it.


MySQL recorder stops recording after some time

Home Assistant release (hass --version):
0.52.1
Python release (python3 --version):
Python 3.5.3
Component/platform:
Recorder
Description of problem:
The recorder stops recording new events after some time running. I have the recorder component with MySQL (mysqlclient pip module) and MariaDB as a backend. For example, this run, i started Home Assistant on 2017-08-30 11:32:39 according to the data in the schema_runs table, and the last entry is on 2017-08-30 17:11:33 (in the events table as well as in the states table). There is no associated entry in the log file, but when i stop Home Assistant and start it again, i get the following log entry:
2017-08-31 10:45:42 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=2 from 2017-08-30 11:32:39)   Now the recording starts again until it hangs sometimes again, until i restart HA again...and so on.
Expected:
The recorder component recording stuff as long as Home Assistant is running.
Problem-relevant configuration.yaml entries and steps to reproduce:
recorder:
  purge_days: 30
  db_url<EMAIL_ADDRESS>

Install Home Assistant
Install MariaDB and create database and user
Install mysqlclient pip module
Config HA and start it
Wait...after some time there are no new log entries written any more

Additional info:
I am unsure if it has something to do with the recent database changes. I have completely dropped the database in between because i thought there could be some failed migration. But also with a fresh database (and even with a complete reinstall of MariaDB) this problem occurs as well. Haven't tested it with SQlite, though.

I have seen this before when the Amcrest component was breaking the recorder:

2017-08-31 10:45:42 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=2 from 2017-08-30 11:32:39)

What this means is that something threw an exception in the middle of a recorder run and that session/transaction was never completed or rolled back or something. Typically restarting hass will fix it.
I feel like this is more an issue of the recorder not being able to come back from a problem. Yes the root of this specific issue might be another component failing or otherwise taking the recorder down, but I feel like the recorder needs to better deal with errors and close/rollback sessions on error.

I have tested it with SQlite as a backend, and it seems that this issue is backend-unaware, since the recording stops here after some hours as well.

I am having the same problem. After a few days it just stops recording events. It seems to first stop some types (temperature) and after a bit it drops everything.

I forgot to mention that this happened after upgrading to some version above 0.5, not sure exactly when.

I have the same or similar issue in 0.54
2017-10-07 09:23:02 ERROR (Recorder) [homeassistant.components.recorder.util] Error executing query: Object of type 'function' is not JSON serializable
Interestingly, the timestamp coincides with a failed attempt to get Wunderground data:
2017-10-07 09:23:02 ERROR (SyncWorker_6) [homeassistant.components.sensor.wunderground] Check WUnderground API ('this key does not exist',)


Filter outside the table

I wanna bring the search bar  outside the table. How can I do that?

Once they have been created, you can move the filters freely using standard DOM manipulation.

@tonyng3101 Without feedbacks from you, I am closing this. I have added a quick example to demonstrate how you can move filter elements.
If you still have trouble with this, feel free to re-open this issue.


Use kbd tag when possible and general markdown improvements

The usage of they <kbd> tag would be better than bold or just normal text. Currently, <kbd> is used in a really few articles. Example where it's used is Tutorial: Create a .NET Core solution in macOS using Visual Studio Code.

General markdown improvements:
Make sure that the following points from the current style guide are followed:

This point caused an issue before with some regex being rendered incorrectly. There could be many occurrences where it causes a problem.

Markdown uses special characters such as *, `, and # for formatting. If you wish to include one of these characters in your content, you must do one of two things:

Put a backslash before the special character to "escape" it (for example, * for a *)
Use the HTML entity code for the character (for example, * for a *).

This is less priority but may be taken into consideration at some point of time.

File names use the following rules:

Use action verbs that are specific, such as develop, buy, build, troubleshoot. No -ing words.
No small words - don't include a, and, the, in, or, etc.

This was changed in the guide soon, it was to capitalize the word following a colon, so there are a lot of articles that doesn't follow this current guide.

Use sentence-style capitalization. Always capitalize the first word of a heading, but don't capitalize the word following a colon in a title or heading (for example, "How to: sort an array").

Italics Use for files, folders, paths (for long items, split onto their own line), new terms.
Bold Use for UI elements.
Code Use for inline code, language keywords, NuGet package names, command-line commands, database table and column names, and URLs that you don't want to be clickable.

/cc @mairaw, @rpetrusha, @BillWagner, @Thraka, Thoughts ?

I like it, I always have. KBD is in the whitelist on the contributors guide. So we just need an agreement on using it.

Thanks @Youssef1313 for opening this issue. We really appreciate your passion and contributions so far to the .NET documentation. I discussed this issue with my team.
Given the amount of legacy content we have, we could spend considerable amount of time trying to make all of our content follow the style guide rules, which takes time away for our team to work on new and updated content without much added value. But we do try to follow the guidance when creating or significantly updating an article.
I think that fixing inaccuracies caused by #1 would be a priority for us but I wouldn't use the HTML code for that. I'd suggest that if you find broken content because of the use of special characters, to file an issue or PR for that specific page. The other improvements are OK if they are done on a case by case scenario but not in bulk. That way, we can easily review and merge the PR.
For this reason, I'm closing the issue.

Follow-up on the <kbd> tag

Currently, <kbd> is used in a really few articles.

This is because guidance in our internal Contributor Guide for docs.ms.com currently advises against using any style at all. For example:  Ctrl+Shift+Enter. Unless we change that guidance, it would be better not to add <kbd> to articles as they will be out of sync with the rest of the docs across the docs.ms.com site.


Cleanup2

Couple more files that are using old digest values
https://github.com/IBM/ibm-helm-api-operator/blob/cleanup2/deploy/operator.yaml#L60-L65
https://github.com/IBM/ibm-helm-api-operator/blob/cleanup2/deploy/olm-catalog/ibm-helm-api-operator/3.6.0/ibm-helm-api-operator.v3.6.0.clusterserviceversion.yaml#L260-L265


Grammar (in the documentation) misses definition for ClassBody

While writing an interpreter for TypeScript definition files I noticed that the grammar seems to be a bit incomplete. For several items I'm not sure whether it's just me or whether it is a logic inconsistency, but for the ClassBody a definition is definitely missing.
By comparing with older versions it seems it is identical to AmbientClassBody, but it should be written/marked as such.
I hope to report a few more inconsistencies if I am sure.

The spec grammar augments the ES6 grammar, which defines ClassBody http://www.ecma-international.org/ecma-262/6.0/#sec-class-definitions