Refactor mx_math files to remove __DECL_GL_MATH_FUNCTIONS__ guard

Refactor mx_math.glsl and mx_math.metal to remove the __DECL_GL_MATH_FUNCTIONS__ guard, and prefix any necessary functions to ensure isolation from other shader generators, such as HdStorm

@jstone-lucasfilm I totally understand your perspective, and I do concede that it does feel like an additional layer of complexity here.
The first observation I would make is that the problem this PR is trying to address is not unique to storm, but applies to any downstream custom shader generator, some of which may not be publicly known, or open source.  I think the project should be trying to provide a positive experience not only for shader writers but integrators of the project.
At a higher level, this problem is really a manifestation of the fact that we don't have  documentation (or even better specification) of the requirements for implementing a custom shader generation target. Trying to solve this shortfall in a complete way seems like a significant undertaking, which is why this current PR feels like a more pragmatic approach to me.
I will note that this does not require a GLSL shader author to use mx_atan() if they are only writing GLSL code.  The standard function call will still be available if the shader author is working solely in a GLSL environment, the point at which mx_atan() would be necessary only when the shader author is trying to write code that would target both GLSL and MSL. If there existed a new unit test for whatever the new functionality is, then I believe this would be caught as soon as. they were run, and easily changed.
Maybe a different perspective is that the current __DECL_GL_MATH_FUNCTIONS__ guard technique is a way to try and make MSL simulate GLSL. My approach is is a bit more egalitarian and tries to provide a small math API that allows both GLSL and MSL to use a common API, without favoring GLSL over MSL.  This feels more scalable in a potential future that we might add other languages that want to share this code.

@ld-kerley Just to consider the alternative approach, what if we were to remove the __DECL_GL_MATH_FUNCTIONS__ guard from MSL and make no other changes?  Could we rely upon GLSL methods such as atan and inverse being consistently unavailable in MSL, allowing the MaterialX-provided methods to be added without any conflict?

@ld-kerley There's a recent discussion on the ASWF Slack about extending shader generation to support HLSL in addition to the existing support for GLSL and MSL, and I think this provides another useful perspective on this proposal.
Following the current approach in MaterialX, developers would continue to author hardware shading nodes using native GLSL, and MaterialX would convert these features to their HLSL and MSL equivalents during shader generation.
In contrast, this proposal would take us along the path of providing mx_ wrappers around a growing set of native GLSL functions, and developers would be required to use these when writing hardware shading nodes (otherwise their code would work only on a single platform).  In a sense, we would be defining a new shading language in MaterialX, and hardware shading nodes would be expressed in this language rather than an existing open shading language such as GLSL, HLSL, or MSL.
Although that's a valid path forward, to my mind it would make the authoring of hardware shading nodes more complex for developers (especially those working on new BSDF nodes with complex logic), without providing any benefits for artists authoring assets using MaterialX.
Given that context, perhaps it's preferable to follow our current approach, where GLSL is treated as the "neutral" hardware shading language in which our nodes are defined, and this code is converted to all other hardware shading languages during the shader generation process?

I want to preface these thoughts with the caveat that most of my shader writing experience is offline (OSL) and not realtime....
I saw the HLSL discussion, and it made me think of this PR again too.... though I think it made me think this PR was even more valid :).  As I feel you've said before in previous meetings its good for MaterialX not to "pick favorites" when it comes to shading languages, and opting for native GLSL as the defacto language and requiring MSL and potentially now HLSL to conform to GLSL feels potentially a little inhibiting.  I feel this PR proposes a somewhat more democratic approach.
There may well be concepts/features in MSL/HLSL that we want to leverage that do not have natural correspondences in GLSL.
Also the original intent of this PR was to make things more robust and stable for downstream integrators creating their own subclasses of these shader generators.  HdStorm being the most commonly known of these, but I expect there are others.  We don't control what additional code these code generators are creating, and we also do not have any documentation to declare or describe what the constraints these code generators need to conform to (I think such documentation would potentially impose harder restrictions on MaterialX once it was written than we might be happy with).  There were one or two issues that needed to be resolved, with the interplay between MaterialX and HdStorm recently, and given the two projects have very different development velocities and release schedules, it seemed like a good idea to me to try and fix a robust solution moving forwards.
If we don't move forward with something similar to what is proposed in this PR, do you have any alternate ideas on how we can make the development landscape more robust for these downstream code generator integrations of MaterialX ?

These are great points, @ld-kerley, and I fully agree that there are two valid paths forward, each of which provides a sufficient set of tools to build and maintain hardware shading code across languages.
Here are the two paths forward that I see:

Following the approach started by @Morteeza in his original MSL implementation, we would continue using GLSL as our canonical hardware shading language, with cross-compilation techniques used to generate shaders in HLSL, MSL, and other hardware languages in the future.  This set of cross-compilation techniques would include preprocessor definitions, string replacement, and other future improvements that are needed to generate robust shading code in each target language.
Following the approach that you propose here, we would create mx-prefixed macros around each concept that differs across hardware shading languages, and authors of hardware shading nodes would write in our "meta-language" rather than in a common language such as GLSL.  Over time, our set of macros would likely include vector and matrix data types (e.g. mx_float3, mx_matrix44), trigonometric functions (e.g. mx_cos, mx_atan), and potentially even a common syntax for data structures and argument passing.  This approach is similar in spirit to the Three.js Shading Language, which hides the differences between popular web shading languages such as GLSL and WGSL.

Each of these paths forward has its own strengths and weaknesses, with option (1) potentially being the clearest for readers and writers of MaterialX shading code, and option (2) potentially providing the greatest degree of future flexibility.
Perhaps this would make a good topic for an upcoming MaterialX TSC meeting?

In preparation for upcoming discussions, I wanted to suggest a third option for us to consider:

Rather than designing our own meta-shading language using mx-prefixed macros, we would adopt a standard meta-shading language such as Slang (https://github.com/shader-slang/slang).  This would allow us to author our hardware shaders using an established open standard, independent of the growing set of hardware shading languages that we support, leveraging the existing cross-compilation functionality in the meta-language that we have selected.

Slack conversation pertaining to this work is here.


WAPP-15105: Fix for default grid 'set' floating filter

See details at https://nuorder-inc.atlassian.net/browse/WAPP-15105
Issue is reproduced on official demo page https://www.ag-grid.com/javascript-grid-filter-set/

@artiz Can you submit the changes here


DATAJDBC-130 - Support entities with List valued properties.

Resolved via https://github.com/spring-projects/spring-data-jdbc/commit/f5de195768fd0626cfd0d8f123bafe3d683fc8e5.


fix: move vue server plugin out of server/ directory

We currently apply some protections to help users avoid importing nitro in the vue part of the app and vice versa.
With https://github.com/nuxt/nuxt/pull/25162 we expanded the test cases (and now test for server\/(api|routes|middleware|plugins)\/).
We might relax this regexp (cc: @pi0) as it wasn't originally intended to catch module usage (it might be helpful to keep anyway!) but I spotted that your Nuxt server plugin was in the server/ directory when I think it would more helpfully belong in the plugins/ directory, mirroring a normal Nuxt project.
Checklist:

[ ] issue number linked above after pound (#)

replace "Closes " with "Contributes to" or other if this PR does not close the issue

[ ] manually checked my feature / checking not applicable
[ ] wrote tests / testing not applicable
[ ] attached screenshots / screenshot not applicable

We might relax some rules to "warning only" for import protections also reducing chance of breaking Nuxt users by upstream change. but definitely makes sense to refactor this way 👍🏼

with this fix, it is now possible to build the app without crashing it or silently failed it once in production. A quick patch release would be welcome @zoey-kaiser 😍

with this fix, it is now possible to build the app without crashing it or silently failed it once in production. A quick patch release would be welcome @zoey-kaiser 😍

Released in https://github.com/sidebase/nuxt-auth/releases/tag/0.6.5! Sorry for the wait, I was coming home from a trip ❤


Prototype Pollution in Chartkick.js 3.1.x

Under certain conditions, the 3.1.x series of Chartkick.js is vulnerable to prototype pollution. This is same type of issue that was announced for jQuery and other popular libraries earlier this year. jQuery rated this a "minor vulnerability". It's certainly unintended behavior, but since Chartkick.js is a client-side only library, its impact is likely limited. This vulnerability has been assigned the CVE identifier CVE-2019-18841.
Versions Affected:  3.1.0 to 3.1.3
Fixed Versions:     3.2.0
Versions Unaffected: < 3.1.0
Impact
Passing untrusted input to JSON.parse and the result to Chartkick.js can pollute Object.prototype.
var badOptions = JSON.parse('{"__proto__": {"test": true}}')
new Chartkick.LineChart("chart", data, badOptions)
console.log("test" in {})

A specially crafted response in data loaded via URL can cause pollution well.
new Chartkick.LineChart("chart", "https://evil.com/data")

All users running an affected release should upgrade immediately.

Hi, are you sure this vulnerability does not exists before ? In 2.1.0, I saw some lines that looks like those fixed.
Cheers,

Hey @guimard, I didn't find any other affected versions in my testing, but please follow up with the email address in my profile if you can demonstrate the issue in other versions, and I'll update the CVE accordingly.


Improve performance of Gui.update_screen()

This function gets called all the time, so we should optimize it.
It's mainly dependent on how fast the draw layers finish updating on a full screen refresh. Here is a quick benchmark:
[debug][api.Stopwatch] [update_draw_pos]	0.02408ms	(0.00 frames)
[debug][api.Stopwatch] [calc_screen_sight]	2.45786ms	(0.15 frames)
[debug][api.Stopwatch] [update_input]	0.63419ms	(0.04 frames)
[debug][api.Stopwatch] [update_renderer]	4.18282ms	(0.25 frames)
[debug][api.Stopwatch] [update_hud]	36.02600ms	(2.16 frames)

[debug][api.Stopwatch] [screen update]	52.80805ms	(3.17 frames)

So the HUD probably needs some work.
[debug][api.Stopwatch] [hud_hp_bar]	0.01597ms	(0.00 frames)
[debug][api.Stopwatch] [hud_mp_bar]	1.06812ms	(0.06 frames)
[debug][api.Stopwatch] [hud_hud_level]	0.42892ms	(0.03 frames)
[debug][api.Stopwatch] [hud_status_effects]	0.44608ms	(0.03 frames)
[debug][api.Stopwatch] [hud_stats_bar]	0.47994ms	(0.03 frames)
[debug][api.Stopwatch] [hud_clock]	0.37408ms	(0.02 frames)
[debug][api.Stopwatch] [hud_minimap]	9.08399ms	(0.55 frames)
[debug][api.Stopwatch] [hud_skill_tracker]	0.45085ms	(0.03 frames)
[debug][api.Stopwatch] [hud_buffs]	0.35095ms	(0.02 frames)

Also, we really need profiling tools that are trivial to use, so we don't have to keep inserting calls to Stopwatch:p() everywhere.

The HUD is full of allocations, apparently. Commenting out MainHud:draw() decreases the allocations per frame from 181KB to 25KB.

I think is greatly alleviated by 75a141c24fe4ce2b99990814401fcf10dbb95e86 and 47b98393e34d9a656b46e1057b3113e69d9e888b.


added --exec option to configure see ticket #59

Changing the file name in this manner works for me

Perfect! Thanks for the PR :D


How to I extract embeddings from Bert code (tf v1.13)

I started off by leveraging the following kernel:

https://www.kaggle.com/taindow/bert-a-fine-tuning-example

While this kernel is a great introduction, I still find myself confused as to how to break apart this end-to-end pipeline to just extract the embeddings. I've adjusted his code and leveraged the convert_examples_to_features function within the run_classifier.py file.
bert_config = modeling.BertConfig.from_json_file(bert_config_file)

processor = ColaProcessor()
label_list = processor.get_labels()

tokenizer = tokenization.FullTokenizer(vocab_file=vocab_file, do_lower_case=do_lower_case)

tpu_cluster_resolver = None
is_per_host = tf.contrib.tpu.InputPipelineConfig.PER_HOST_V2

train_examples = processor.get_train_examples(data_dir)
num_train_steps = int(len(train_examples) / train_batch_size * num_train_epochs)
num_warmup_steps = int(num_train_steps * warmup_proportion)

print("Feature Test")
features = convert_examples_to_features(examples=train_examples, label_list=label_list, max_seq_length=max_seq_length, tokenizer=tokenizer)
print("Feature Test Completed")

Now, after I do this, I get the following output when I print my features variable:
 <run_classifier.InputFeatures at 0x7f798eece780>,
 <run_classifier.InputFeatures at 0x7f798eefd7b8>,
 <run_classifier.InputFeatures at 0x7f798eece5c0>,
 <run_classifier.InputFeatures at 0x7f798eecec18>,

I have two main questions:

Is this the proper way to extract embeddings
If it is, how do I convert the InputFeatures to arrays

Hi, Did you get the solution?


Change background color with the theme

It should be automatic that depending on the theme, it's easy to set the background color of the story. Currently the only way I've found is adding a div wrapper in the providerFn, but it's a limited solution because it shows some  ugly unthemed borders.

Hey @edulix
This addon intends to manage components theme but not Storybook itselfs. Usually you don't want to keep storybook background in your app's theme? But I understand your needs.
Storybook has an API for managing own theme
https://storybook.js.org/docs/react/configure/theming#create-a-theme-quickstart
Also there is a background addon for changing preview area color
https://storybook.js.org/docs/react/essentials/backgrounds
Will this work for you?

For now I'm using just the backgrounds addon. I'm not sure I follow your logic. I don't want to keep storybook background i my app's theme. I'm trying to easily change the theme of the app and see the widget in a context similar to the one it will be used on.
So for example if I'm doing a component with some paragraphs of text, it makes sense to try the component with the dark theme and see how it responds. But it makes sense that in the dark theme the text will be whitish, so if the background is not changed it will be unreadable. I think it pretty much makes sense to, at least optionally, be able to link the background color of the story together with the theme.

Thanks Eduardo :)
Yes I really understand this inconvenience. I've faced this as well. Currently we don't have any way to switch Storybook theme or integrate with background addon. Maybe it's worth to add such option :thinking:
For a while why wrapping into a custom div doesn't work for you? It's common to wrap components with some providers in general. You could have a single global decorator for that. What do you think?

To be honest, I don't want to have a half-baked visual result, that's why I prefer not using a div wrapper that looks bad and makes the visual result of a widget confusing because it doesn't change the whole background, leaving some borders in other colors.
What I've seen other plugin do is to directly change the CSS style of the iframe:
https://github.com/semoal/themeprovider-storybook/blob/master/src/Themes.tsx#L69
But that cannot be done within the providerFn because it's being executed within the iframe and no on the top frame. I also looked at the backgrounds addon (see https://github.com/storybookjs/storybook/blob/next/addons/backgrounds/src/containers/BackgroundSelector.tsx#L100 ) and tried to use the useGlobals hook inside the providerFn to change the background color, but the same thing happens. You cannot call that within the iframe. So the solution must happen outside the providerFn, but I haven't explored how..

A bit of poking around and I might have a simpler fix.
I'm using material ui, I have my two themes imported and I set parameters to include:
  backgrounds: {
    default: lightThemeOptions.themeName,
    values: [
      {
        name: darkThemeOptions.themeName,
        value: darkThemeOptions.palette.background.default,
      },
      {
        name: lightThemeOptions.themeName,
        value: lightThemeOptions.palette.background.default,
      },
    ],
  },

then I changed https://github.com/react-theming/storybook-addon/blob/master/src/preview/onThemeSwitch.js#L40 to simply set the default background to the theme name and not a color.
  const parameters = {
    backgrounds: {
      default: theme.name
    }
  };

It's a hack right now, but I'll probably use patch-package to try it longer term.
Whenever I change the theme, the default background changes in sync with it.

Now this can be achieved via onThemeSwitch option


Crash when teleporting to a reciever that has been moved by Funky Locomotion.

I've tried this several ways to make sure that I've dialed AFTER they moved, and still no luck.  I have like four crash logs as a result, but they all seem to be identical beyond the time of the event-- I can include them as well if you have reason to believe they'll have more info, but for now I'll just submit the one.
http://pastebin.com/PpfREjkt
Admittedly, I've never submitted a mod error before, so I could be doing this completely wrong.  If there's something else I need to give you or I need to talk to someone else, just say so.

Just experienced the same crash while attempting to walk to the frame miner.  I'm going to tentatively assume the crash is unrelated to the RFtools teleporter and close this.


NetworkFirst wrong exception thrown

Summary
While using cache policy NetworkFirst instead of network failure reason, Cache Miss : no snapshot is thrown
Version
v3.0.0
Description
In NetwokFirst cache policy networkMightThrow is wrapped in try/catch which in case of a very first network call failed due to 300..500 error code will result in bloating firebase with wrong stack trace by provide HttpCacheMissException.
CACHE_FIRST -> {
        try {
          return cacheMightThrow(request, cacheKey)
        } catch (e: ApolloException) {
          //
        }

        return networkMightThrow(request, chain, cacheKey)
      }
      CACHE_ONLY -> {
        return cacheMightThrow(request, cacheKey)
      }
      NETWORK_ONLY -> {
        return networkMightThrow(request, chain, cacheKey)
      }
      NETWORK_FIRST -> {
        try {
          val response = networkMightThrow(request, chain, cacheKey)
          if (response.statusCode in 200..299) {
            //  let HTTP errors through
            return response
          }
        } catch (e: ApolloException) {

        }

        return cacheMightThrow(request, cacheKey)
      }

Can we re throw the network error in case of there is no cache

Hi 👋 . Thanks for sending this. Can you try with version 3.1.0? There have been some important changes to the cache interceptors. Not 100% sure it's related but it's worth checking out.

Hi martin, in v3.1.0 also while configuring persistent LRU httpCache using
fun ApolloClient.Builder.httpCache(
    directory: File,
    maxSize: Long,
): ApolloClient.Builder {

  return addHttpInterceptor(
      CachingHttpInterceptor(
          directory = directory,
          maxSize = maxSize,
      )
  )

Which adds CachingHttpInterceptor and results in same issue.

Thanks for double checking this 🙏 .
We could return an ApolloCompositeException if you're using NETWORK_FIRST and you get both a cache and a network error:
        var networkException: ApolloException? = null
        try {
          val response = networkMightThrow(request, chain, cacheKey)
          if (response.statusCode in 200..299) {
            //  let HTTP errors through
            return response
          }
        } catch (e: ApolloException) {
          networkException = e
        }

        try {
          return cacheMightThrow(request, cacheKey)
        } catch (e: ApolloException) {
          throw ApolloCompositeException(networkException, e)
        }

This way you would get access to the networkException through ApolloCompositeException.first. But I don't think it'll change anything to your Firebase errors since it will still throw?

Correct, but by this we can check what was the actual failure for API which was masked by HttpCacheMissException

Gotcha 👍 . Do you want to open a pull request?

sure

PR raised - https://github.com/apollographql/apollo-kotlin/pull/3957


Change header to year 2021

replace 2004-2020 to 2004-2021

Sure this is not going to be merge nightmare. Maybe wait until NLog 5 ?

I will fix the merge to dev. It's not that a problem


Strip out all unhelpful offline related code

Leaving the public connection check, cause an error is better than a crash.

Done.


Fix code scanning alert - Use of a broken or weak cryptographic hashing algorithm on sensitive data

Tracking issue for:

[ ] https://github.com/canonical/pgbouncer-k8s-operator/security/code-scanning/1

WIP in https://github.com/canonical/pgbouncer-k8s-operator/pull/313


CDA.PL

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting that yt-dlp is broken on a supported site
[X] I've verified that I'm running yt-dlp version 2023.07.06 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
Poland
Provide a description that is worded well enough to be understood
Can't download any videos.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[b532a3481] (zip)
[debug] Python 3.9.2 (CPython x86_64 64bit) - Linux-5.10.0-23-amd64-x86_64-with-glibc2.31 (OpenSSL 1.1.1n  15 Mar 2022, glibc 2.31)
[debug] exe versions: ffmpeg 4.3.6-0, ffprobe 4.3.6-0, rtmpdump 2.4
[debug] Optional libraries: Cryptodome-3.9.7, brotli-1.0.9, certifi-2020.06.20, mutagen-1.45.1, pyxattr-0.7.2, sqlite3-2.6.0, websockets-8.1
[debug] Proxy map: {}
[debug] Loaded 1855 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Available version<EMAIL_ADDRESS>Current version<EMAIL_ADDRESS>Current Build Hash: cedf44a9cf3c241520a692c1006d276e6f434d4d945727c47cb1a70d32953f4a
yt-dlp is up to date<EMAIL_ADDRESS>

post actual verbose log of download attempt

WARNING: [CDA] unable to extract default player_json; please report this issue o  n  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issu  e template. Confirm you are on the latest version using  yt-dlp -U
ERROR: [CDA] 10997593ce: No video formats found!; please report this issue on  h  ttps://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue te  mplate. Confirm you are on the latest version using  yt-dlp -U

See also https://github.com/ytdl-org/youtube-dl/issues/30873 (not apparently the same issue though).

This is an age-confirm page but with a different structure from that expected:
$ yt-dlp -v -F 'https://www.cda.pl/video/1553664551'
[debug] Command-line config: ['-v', '-F', 'https://www.cda.pl/video/1553664551']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[812cdfa06] (source)
[debug] Lazy loading extractors is disabled
[debug] Git HEAD: de4cf77ec
[debug] Python 3.9.16 (CPython i686 32bit) - Linux-4.4.0-210-generic-i686-with-glibc2.23 (OpenSSL 1.1.1u  30 May 2023, glibc 2.23)
[debug] exe versions: ffmpeg 4.3, ffprobe 4.3
[debug] Optional libraries: Cryptodome-3.11.0, certifi-2019.11.28, secretstorage-3.2.0, sqlite3-2.6.0
[debug] Proxy map: {}
[debug] Loaded 1851 extractors
[CDA] Extracting URL: https://www.cda.pl/video/1553664551
[CDA]<PHONE_NUMBER>: Downloading webpage
WARNING: [CDA] unable to extract default player_json; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
ERROR: [CDA]<PHONE_NUMBER>: No video formats found!; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
Traceback (most recent call last):
  File "/home/df/Documents/src/yt-dlp/yt_dlp/YoutubeDL.py", line 1555, in wrapper
    return func(self, *args, **kwargs)
  File "/home/df/Documents/src/yt-dlp/yt_dlp/YoutubeDL.py", line 1652, in __extract_info
    return self.process_ie_result(ie_result, download, extra_info)
  File "/home/df/Documents/src/yt-dlp/yt_dlp/YoutubeDL.py", line 1711, in process_ie_result
    ie_result = self.process_video_result(ie_result, download=download)
  File "/home/df/Documents/src/yt-dlp/yt_dlp/YoutubeDL.py", line 2653, in process_video_result
    self.raise_no_formats(info_dict)
  File "/home/df/Documents/src/yt-dlp/yt_dlp/YoutubeDL.py", line 1067, in raise_no_formats
    raise ExtractorError(msg, video_id=info['id'], ie=info['extractor'],
yt_dlp.utils.ExtractorError: [CDA]<PHONE_NUMBER>: No video formats found!; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U

$

Page JS sets cookie adult=1 but doing that and refetching doesn't help.
A single resolution is available by fetching the embedUrl from the ld+json and decoding an attribute of the player element there.
Of the 3 extractor tests 1 and 2 don't show this problem. There's no view_count in test 2. Test 3 is 410, but a page like the above could replace it once the extraction works.

Hi.
That you for the reply.
The problem is with age confirmation in modal window.
I had to add credentials to my free account to be able to bypass this window.

Duplicate of #5980
Will be fixed by #6638


Update Tesseract source code documentation

Update http://tesseract-ocr.github.io/.
https://digi.bib.uni-mannheim.de/tesseract/doc/tesseract-ocr.github.io/ shows a preview.

Doxygen reported some warnings: https://digi.bib.uni-mannheim.de/tesseract/doc/DoxyWarn.txt. Maybe we can fix them for the final 4.0.0. And some important interfaces still have no documentation at all.


install: Refactor installation instructions

Refactor installation instruction to minimize duplicate content,
to document package source verification process, and to remove
some of the typos.
Fixes: #263
Signed-off-by: Marco Vedovati<EMAIL_ADDRESS>

I still need to figure out where to upload the signing public key.
I was thinking on the tests repo, so that the CI jobs can import it during installation with:
rpm import "$(curl -fsSL \
https://raw.githubusercontent.com/kata-containers/tests/master/key/kata-containers.pub)

This can be added in the install instruction code block, and --no-gpg-checks should be removed...

/cc @jodh-intel @grahamwhaley @jcvenegas

Ok, I pushed a new version based on @jodh-intel suggestions. I can see some improvements but feel free to give some more feedbacks :)

I hope this is getting closer to a final version.
I thought that the reference packages signing key can be uploaded at this location, given that that it will be used to automate packages installation when running CI tests: https://github.com/kata-containers/tests/data/rpm-signkey.pub

lgtm
ping @kata-containers/documentation.

Thanks @klynnrif, I integrated all your suggestions.

Re-ping @kata-containers/documentation - it would be great to get this landed today... :smile:

lgtm


Failed to launch C# gRPC with x64 arch on Windows

the underlying issue is that latest Grpc NuGet package (0.7.1) is shipped without 64-bit version of grpc_csharp_ext.dll
not sure why - maybe due to this reason: https://github.com/grpc/grpc/issues/1082#issuecomment-84752606
i was tried to compile grpc_csharp_ext.dll for x64 arch manually
and everything is working fine for my x64 C# gRPC Client
unfortunately my very simple x64 C# gRPC Server is failed to start with the following error:
..\..\..\src\core\support\stack_lockfree.c:132: assertion failed: (old_val & (1UL << pushed_bit)) == 0

NB: x86 version of gRPC Server is started without problem
does anybody know how to fix this issue?
any help is appreciated...

I have also seen this problem for my C++ Windows x64 gRPC server code. Even after I applied the patch of #1082, the problem still exists.

Closing this as obsolete.
In the next release, we will publish nuget packages that will fully support Win 32bit and Win 64bit (including autodetection). See #4820 for details.


[BUG] in crashlytics/*: Crashlytics functions are deprecated and need to be removed

Crashlytics functions are no longer available, we should remove the samples that reference them.

Calling @jhuleatt the Great Deleter of Samples

@mbleigh

Crashlytics functions are no longer available

My company relied on this trigger. Was this announced somewhere in advance? Also, will there be any new ways of getting alerts, or is it limited to the current options?


How should users debug subscription timeouts?

I often see this error message when my one of my replicated services is trying to acquire a distributed lock from our AWS Elasticache Cluster.

Subscribe timeout: (7500ms). Increase 'subscriptionsPerConnection' and/or 'subscriptionConnectionPoolSize' parameters.

I followed the suggestion of the message and increased my subscriptionsPerConnection from the default to 500. I still see the error message. I looked at the CPU/Memory usage of the AWS Elasticache cluster and it is below 5%.
I have looked into other issues about this topic and I have not found a good way to root cause what is actually going on.
Is there a way that we can validate that we are indeed exceeding the subscriptions per connection or are running out of subscription connections?
If we are indeed running out of connections is there a way we can dump what subscriptions our connections are using?
I have enabled DEBUG level logging and I see the following messages.

connection released for command null and params null from slot NodeSource [slot=null, addr=null, redisClient=null, redirect=null, entry=MasterSlaveEntry [masterEntry=[freeSubscribeConnectionsAmount=0, freeSubscribeConnectionsCounter=value:49:queue:0, freeConnectionsAmount=24, freeConnectionsCounter=value:92:queue:0, freezeReason=null, client=[addr=], nodeType=MASTER, firstFail=0]]] using connection RedisConnection@1767476324 [redisClient=[addr=r], channel=[id: 0x7d4b874f, L:/ - R:], currentCommand=null]

What is the difference between the freeSubscribeConnectionsAmount and freeSubscribeConnectionsCounter ?

I followed the suggestion of the message and increased my subscriptionsPerConnection from the default to 500. I still see the error message. I looked at the CPU/Memory usage of the AWS Elasticache cluster and it is below 5%.

Can this relate to this issue related https://github.com/redisson/redisson/issues/3577 ?

Is there a way that we can validate that we are indeed exceeding the subscriptions per connection or are running out of subscription connections?

There is no such way except statistics monitoring. https://github.com/redisson/redisson/wiki/14.-Integration-with-frameworks#1414-statistics-monitoring-jmx-and-other-systems

If we are indeed running out of connections is there a way we can dump what subscriptions our connections are using?

All subscriptions share the same pool of subscription connections.

Can this relate to this issue related #3577 ?

I don't believe so considering we are reproducing this issue on Redis 3.15.5.

There is no such way except statistics monitoring. https://github.com/redisson/redisson/wiki/14.-Integration-with-frameworks#1414-statistics-monitoring-jmx-and-other-systems

I'm not sure I'm going to go through the effort to convince my company to purchase PRO. Will fork and add my own logs/instrumentation I guess to see what is going on.

What is the difference between the freeSubscribeConnectionsAmount and freeSubscribeConnectionsCounter ?

freeSubscribeConnectionsAmount - amount of pubsub connections in pool, freeSubscribeConnectionsCounter  - current amount of available connections for getting from pool or creating.

I'll add type of connection in logs. So you can count amount of acquired in released connections by log records.

I spent several hours yesterday digging into the code to try and understand what might be going on. As you mentioned, the freeSubscribeConnectionsCounter indicates how many connections remaining connections can be created in order to service requests. Given that I am seeing freeSubscribeConnectionsCounter set to 49 we know that there is only one actual connection being used for pub/sub.
From my testing it appears that if pub/sub channels are added slowly enough they will just be added to an existing connection until the number of subscriptions allowed per connection reaches the maximum, at which point a new connection will be created.
There may be a bug or there may be a legitimate issue with our environment that does not make it possible to acquire a new connection with the Redis cluster. It should not be an environmental issue given that we've seen our Redis Cluster scale up to 40,000 connections and we typically only use 1,200 at a time. I will admit that the environment we are using is quite complex so it is possible there is some infrastructure or network layer playing a part here.
An issue I see with the code is that the logic to retrieve a new connection is encapsulated in a future, and there are codepaths that will finish, but never complete the future. For instance, in my testing when I maxed out the possible pub/sub connections new requests will try to create a connection but timeout. What actually happens is the AsyncSempahore that allows new connections to be created silently doesn't execute some codepath that would complete the future in some way.
Given that I've spent some time looking at the code I would be willing to open a PR to add some additional logging and potentially document/cleanup some minor things.

Given that I've spent some time looking at the code I would be willing to open a PR to add some additional logging and potentially document/cleanup some minor things.

I would be glad to consider it.

What actually happens is the AsyncSempahore that allows new connections to be created silently doesn't execute some codepath that would complete the future in some way.

Fixed in https://github.com/redisson/redisson/issues/3703


Add example IFTTT in readme

README should detail the webhook dependency, and include an example IFTTT applet. Tutorial is ideal but maybe unneeded.

README created but example applet still needs to be linked.

https://platform.ifttt.com/ is down

https://github.com/teamshortcut/Discord-Maths-Bot/commit/44b7fbbd543213cb6ccbc055af153243b43e7b9f


Build Fails to Auto-Generate Password with Latest Plugin

Packer Version

packer --version
1.9.1

Packer Configuration Files

The plugin File (used for INIT) needs to be updated to replicate the issue.
Results in failure
packer {
    required_plugins {
        outscale = {
            version = ">= 1.0.5"
            source  = "github.com/outscale/outscale"
        }
    }
}

Not having issue
packer {
    required_plugins {
        outscale = {
            version = "1.0.5"
            source  = "github.com/outscale/outscale"
        }
    }
}

Debug Output

Issue occurs during Build when the process attempts to create the 'auto-generated' password. Initialization and Validation step included to show that these were performed before attempting the build.
packer init .\plugins\outscale_plugins.pkr.hcl
Installed plugin github.com/outscale/outscale v1.1.0 in "C:/Users/christian.vedia/AppData/Roaming/packer.d/plugins/github.com/outscale/outscale/packer-plugin-outscale_v1.1.0_x5.0_windows_amd64.exe"

packer validate --var-file=".\win_app.pkrvars.hcl" .\win_omi.pkr.hcl
The configuration is valid.

packer build --timestamp-ui --var-file=".\win_app.pkrvars.hcl" .\win_omi.pkr.hcl
outscale-bsu.windows: output will be in this color.

2023-06-22T16:17:15Z: ==> outscale-bsu.windows: Prevalidating OMI Name: packer_win_app_1687450635
2023-06-22T16:17:16Z:     outscale-bsu.windows: Found Image ID: ami-e7ce4bb1
2023-06-22T16:17:16Z: ==> outscale-bsu.windows: Creating temporary keypair: packer_6494740b-5086-adc9-a7a2-7f0c889f2105
2023-06-22T16:17:16Z: ==> outscale-bsu.windows: Launching a source OUTSCALE vm...
2023-06-22T16:17:16Z: ==> outscale-bsu.windows: Adding tags to source vm
2023-06-22T16:17:18Z:     outscale-bsu.windows: Vm ID: i-5d41c002
2023-06-22T16:17:18Z: ==> outscale-bsu.windows: Waiting for vm (i-5d41c002) to become ready...
2023-06-22T16:17:33Z:     outscale-bsu.windows: Adding tag: "Name": "Packer Builder"
2023-06-22T16:17:33Z: ==> outscale-bsu.windows: Waiting for auto-generated password for vm...
2023-06-22T16:17:33Z:     outscale-bsu.windows: It is normal for this process to take up to 15 minutes,
    outscale-bsu.windows: but it usually takes around 5. Please wait.
2023-06-22T16:17:48Z: ==> outscale-bsu.windows: Error waiting for password: Error decrypting auto-generated vm password: crypto/rsa: decryption error
2023-06-22T16:17:48Z: ==> outscale-bsu.windows: Terminating the source OUTSCALE vm...
2023-06-22T16:18:13Z: ==> outscale-bsu.windows: Cleaning up any extra volumes...
2023-06-22T16:18:13Z: ==> outscale-bsu.windows: Deleting temporary keypair...
2023-06-22T16:18:13Z: Build 'outscale-bsu.windows' errored after 58 seconds 163 milliseconds: Error decrypting auto-generated vm password: crypto/rsa: decryption error

Expected Behavior

The auto-generated password step should wait for about 15min to get a response from the VM but instead fails within the 1st minute. Below shows the process working with the same configuration when using an older Plugin version. Initialization and Validation step included to show that these were performed before attempting the build.
packer init .\plugins\outscale_plugins.pkr.hcl
Installed plugin github.com/outscale/outscale v1.0.5 in "C:/Users/christian.vedia/AppData/Roaming/packer.d/plugins/github.com/outscale/outscale/packer-plugin-outscale_v1.0.5_x5.0_windows_amd64.exe"

packer validate --var-file=".\win_app.pkrvars.hcl" .\win_omi.pkr.hcl
The configuration is valid.

packer build --timestamp-ui --var-file=".\win_app.pkrvars.hcl" .\win_omi.pkr.hcl
outscale-bsu.windows: output will be in this color.

2023-06-22T16:05:47Z: ==> outscale-bsu.windows: Prevalidating OMI Name: packer_win_app_1687449947
2023-06-22T16:05:47Z:     outscale-bsu.windows: Found Image ID: ami-e7ce4bb1
2023-06-22T16:05:48Z: ==> outscale-bsu.windows: Creating temporary keypair: packer_6494715b-1424-db7e-5ebc-c0027326a3a6
2023-06-22T16:05:48Z: ==> outscale-bsu.windows: Launching a source OUTSCALE vm...
2023-06-22T16:05:48Z: ==> outscale-bsu.windows: Adding tags to source vm
2023-06-22T16:05:50Z:     outscale-bsu.windows: Vm ID: i-0c41efa1
2023-06-22T16:05:50Z: ==> outscale-bsu.windows: Waiting for vm (i-0c41efa1) to become ready...
2023-06-22T16:06:04Z:     outscale-bsu.windows: Adding tag: "Name": "Packer Builder"
2023-06-22T16:06:04Z: ==> outscale-bsu.windows: Waiting for auto-generated password for vm...
2023-06-22T16:06:04Z:     outscale-bsu.windows: It is normal for this process to take up to 15 minutes,
    outscale-bsu.windows: but it usually takes around 5. Please wait.
2023-06-22T16:12:18Z:     outscale-bsu.windows:
    outscale-bsu.windows: Password retrieved!
2023-06-22T16:12:18Z: ==> outscale-bsu.windows: Using WinRM communicator to connect: <IP_ADDRESS>
2023-06-22T16:12:18Z: ==> outscale-bsu.windows: Waiting for WinRM to become available...
2023-06-22T16:12:25Z:     outscale-bsu.windows: WinRM connected.
2023-06-22T16:12:25Z: ==> outscale-bsu.windows: Connected to WinRM!
2023-06-22T16:12:25Z: ==> outscale-bsu.windows: Provisioning with Powershell...

Actual Behavior

Packer attempts to create the VM with an auto-generated password but quickly fails on its attempt. Switching to an older plugin does not show the same issue.
Steps to Reproduce

Update your plugin file to reference a version later than 1.0.5; we used ">= 1.0.5".
Run packer init referencing the same plugin file
Run packer validate to re-confirm your configuration
Run packer build with the same configuration. The process should go through until the 'auto-generated password' process starts; should fail shortly after.

Additional Context

Your configuration can include a timeout override using "windows_password_timeout" under source "outscale-bsu" but this value does not appear to be passed when the issue is occuring with the updated plugin.
References

none

Hello
Thanks for reporting this, the issue is related to the upgrade of sdk go.
We will fix this soon.
Thanks.

Hello
New release is available, can you please tell us if it is fixed for you ?

Hi Team,
Fix confirmed. Thank you. Pointed to (plugin version 1.1.1) and looks like the issue is no longer occurring. No other updates were made.
Confirmed as well that 'packer-plugin-outscale_v1.1.1_x5.0_windows_amd64.exe' downloaded to (..\packer.d\plugins\github.com\outscale\outscale).
Update in Plugin reference
        outscale = {             version = "1.1.1"             source  = "github.com/outscale/outscale"         }
Results from Pack Build
        2023-08-01T18:43:39Z: ==> outscale-bsu.windows: Waiting for vm (i-abc123defg) to become ready... 2023-08-01T18:43:54Z:     outscale-bsu.windows: Adding tag: "Name": "Packer Builder" 2023-08-01T18:43:54Z: ==> outscale-bsu.windows: Waiting for auto-generated password for vm... 2023-08-01T18:43:54Z:     outscale-bsu.windows: It is normal for this process to take up to 15 minutes,     outscale-bsu.windows: but it usually takes around 5. Please wait. 2023-08-01T18:49:10Z:     outscale-bsu.windows:     outscale-bsu.windows: Password retrieved! 2023-08-01T18:49:10Z: ==> outscale-bsu.windows: Using WinRM communicator to connect:


Multiplexing RTCP required in Chrome Canary

Per this announcement:

As of the most recent Chrome Canary build, the default RTCP multiplexing policy is "require", instead of "negotiate". This will affect the next Chrome release, M57.

For any application that doesn't yet support RTCP multiplexing, you can get the old behavior by explicitly setting the RTCRtpMuxPolicy to "negotiate" in the RTCConfiguration.

Some endpoints (Asterisk, for example) do not yet support rtcp-mux and will therefore stop working after the next Chrome release.

This is not something we can do anything about in SIP.js. If you would like to discuss this further, I would recommend reaching out to Asterisk or you can discuss with other SIP.js users on our mailing list. Thanks.

Sorry? You could add a flag (similar to the hack* options) to pass {rtcpMuxPolicy: "negotiate"} when creating an RTCPeerConnection? Or is that out of scope?

I'm sorry. You are correct. I did not read the announcement before replying and just used your summary as a basis for my reply. Yes, we should add yet another hack. Re-opening this issue.

It should be noted that I tested this with FreeSWITCH 1.6.14 and RTPEngine and neither had issues with multiplexing RTCP with RTP. It appears that Asterisk is the lone issue here.


Mountrail County, ND Parcel Data

https://www.dropbox.com/sh/u2pp1z9aryx3cvs/AABWar2BjcO5qIJo_CYFeQO4a?dl=0
Data is in a few places - excel file, and in an ESRI FGDB - if anyone wants to put together

Do you have excel to export "Nov212016 Landowner Info.xls" to a CSV file?  I can't get it to import into google docs.  The GDB doesn't appear to have address info anywhere.

@trescube I've opened in Excel and saved as CSV for you:

https://s3.amazonaws.com/data.openaddresses.io/cache/uploads/nvkelso/602219/Nov212016-Landowner-Info.csv

But caution it has funny column headings like "column1" thru "column33", lol. My guess is the 1st column is a parcel identifier.


[3.x] Allow for mapping scancodes to current layout

Backport of #52684 for 3.x
Adds OS.keyboard_get_scancode_from_physical(scancode) function.
Implements https://github.com/godotengine/godot-proposals/issues/3571 for 3.x
Test project: phy_conv3.zip

Thanks!

Sweet!  Seems to work.  Just in time for Steam Next Fest!

Was this ever ported to 4.x ?
I can't seem to find a way to convert physical keycode to a regular one

Haha, I just got the documentation for that fixed: https://github.com/godotengine/godot/pull/82092/files
		    if event is InputEventKey:
			        var keycode = DisplayServer.keyboard_get_keycode_from_physical(event.physical_keycode)
			        print(OS.get_keycode_string(keycode))

Was this ever ported to 4.x ?

This was from 4.x, it already existed in 4.x and was backported to 3.x, see the description


ValueError: creating distributed tf.Variable with aggregation=MEAN and a non-floating dtype is not supported, please use a different aggregation or dtype

It happens while using keras-models in kaggle tpu.

It happened to me too and I have no idea how to fix it.

I downgraded keras to 3.6.0 and it seems to fix the issue (althought something else popped up)


Feedback from LinkedIn

I have been reaching out to the community to get feedback on our Miami As a Platform project.
Here is a link to feedback I have received : https://www.linkedin.com/grp/post/6727205-6037314167151558657?trk=groups-post-b-title
Feedback Topics via LinkedIn Miami Tech Community

Historic Budget Data
Real Estate Prices (Residency)
-Traffic Data (Ex. vehicle traffic on the highways (by hour, day, season)?)
New Developments
Neighborhood (Demographic Ex. Kids, Pets, Age)
Park Budget Policy (Compare Rich & Poor Zipcodes; Tax Money Allocation)

Here are the mentioned ideas we can implement:

Justin Gottlieb - How about real estate prices by neighborhood/growth of residency from various other states/countries, traffic data, and new developments?
Patricia Kack - Demographics per neighborhood - age range percentages, kids, and pets so you could get at a glance how young or old an area is when looking for housing.
Michael Neel - How about vehicle traffic on the highways (by hour, day, season)?

I believe I've seen a UM Data Web App that takes care of the first two. I'm looking for the link.
Maybe transportation would want to take on the 3rd suggestion

turned this into a trello card: https://trello.com/c/RWctTaUH/33-linkedin-feedback


Non intuitive insight function

Problem
Now when insights function is rendered if getting data from insight is done. It will pop on insights function section suddenly
Solution
Maybe we can predefine tab before, and gives spinner when getting data from insights?

Good idea, let's implement

Implemented on the new layout


the time to release the code

Thanks for your work! when will the code be released?

Thank you for your attention. The paper is under review, and we will release the code as soon as possible.

Hi, its beautiful! Is here are any way to try it myself? Mb deployed on site or smth?

do you have any estimation for code release?

+1 on this, do you know when are you expecting to release code?

Honestly I can't wait to try this GAN

Thanks for the good paper.
When will I be able to use the code? Thank you!

Hello ZPdesu, the paper is released , can you public your code now. I very interested <3

I think they used StyleGan2 with image mapping on it vector space, then somehow remove face and hair parts from embedding vector and then just add hair embedding to the target image

also here is the same solution https://www.youtube.com/watch?v=0Vbj9xFgoUw

Thanks for your work! when will the code be released?

Look forward

Our code has been released, please git pull the newest repo for improvements and new features.


fix: pause the endpoint request when upgrading to ensure not to miss connection frame sent by socket.io server

Issue
https://gravitee.atlassian.net/browse/APIM-5257
Description
with the current implementation we miss the first “connection” frame sent by socket.io server, the solution is to pause the endpoint request when upgrading the client request, link them together then resume the endpoint websocket.
Additional context

Gravitee.io Automatic Deployment
🚀 A prerelease version of this package has been published on Gravitee's private artifactory, you can:

use it directly by updating your project with version: 3.1.2-APIM-5257-socketio-SNAPSHOT
download it from Artifactory here

Do you think it's possible to add a unit test for this or not ?


Update rank-transact-sql.md

Clarify example; products 494 and 495 only have the same rank within one group, not the other.

#sign-off

This PR is ready for merge. Due to the upcoming Ignite conference, all merging and publishing is on hold until the morning of the keynote address.
The PR review team will resume merging on the morning of the keynote address for the regularly scheduled daily publish cycles. You don't need to take further action on this PR; we'll merge it on the day of the keynote address.
Don't add more commits to this reviewed PR. If you need to make additional changes to these files, email techdocprs for guidance about how to proceed.
#label:"missed-content-complete","event-triaged-to-10AM"


TabHandleView: Add sub view to close-tab icon.

/cc @gokmen @sinan @fatihacet @szkl

@sinan this is kd core level change and would be better if it's review and merged by you.

@sinan could you check again this pr? I've pushed something according to your feedbacks. But I didn't check the view because the target gives me what I want.

@GokhanTurunc this can be a breaking change and we have to be sure there won't be a side effect of this PR. Could you test it more? We can discuss about it more. Ping me on slack.

ping

ping

ping

LGTM :+1:
waiting for @sinan to merge it.

bump up version, and we'll be good.

ready.

@GokhanTurunc please apply the same thing to the master branch as well.

I've created a pull request for this:
The pull request: https://github.com/koding/koding/pull/5222

@sinan i'll do it.


VolumePolicy should support resource allocation to openebs volume pods

VolumePolicy should have some policies that support resource allocation i.e. CPU, RAM to openebs controller & replica pods.

https://github.com/openebs/maya/pull/496 : added Replica and Target ResourceRequest and ResourceLimit related policies


feat: fix shell alias on readme

I don't understand, it's the same thing twice

If I use the original command in readme on windows, which is py3 -m pip install -e .. I was prompted error:
cannot find py3 as cmdlet, function or shell scripts

I think you may set alias py3=python3 on windows. But for people who have not set these alias, they should use python3 instead of py3.

I may have confused py3 for py when I wrote this, haven't used windows in a while. I had the alternate command for windows cuz on windows python3 might not be in path depending on the install method, which if a user just clicks through the python installer the default is to not put python3 in the path and only put the python launcher (https://docs.python.org/3/using/windows.html#launcher)

I am using windows. I found py can be found but not py3.
According to Python official docs, python windows launcher should be called py and "The launcher is compatible with all available versions of Python, so it does not matter which version is installed." https://docs.python.org/3.11/using/windows.html#launcher
However, from Pytorch's installation guide, the way to verify whether python is installed correctly is to type python on command line. https://pytorch.org/get-started/locally/. Even it is installed on windows and user should add python to PATH variable.

Also, I did a global GitHub search for py3 on markdown files in sourcegraph, I found very few use cases.
https://sourcegraph.com/search?q=context%3Aglobal+lang%3AMarkdown+"py3+"+&patternType=standard&sm=1&groupBy=repo
So, I believe py or python3 is appropriate here. If a windows user have only installed Python3 and , python would also be correct.

Yea it was a mistype on my end for py3 its supposed to be py.
If you look at the install guide for python on windows (https://docs.python.org/3/using/windows.html#installation-steps), the add to path option is not checked by default, which means that python3 may not exist for all users depending on how they installed python.

Yes. Fully agree. python3 may not exit for all users, but most popular python package kind of assume people put it on PATH variable. And Python official doc specifially instructed people mannually put it in PATH variable. https://docs.python.org/3/using/windows.html#configuring-python
IMHO, using python3 is appropriate here. For folks who have not put python in PATH, they can easily google or ask ChatGPT  to figure out the solution.

Yea, I agree with that, I think just having python3 should be fine.


Fix the version of mach2 in Cargo.toml

The toml file specifies version 0.4.1 instead of 0.4.2.
Using version 0.4.1 produces a compile error:
error[E0432]: unresolved import `mach2::ndr`
  --> external/crate_index__wasmtime-runtime-20.0.2/src/sys/unix/machports.rs:44:12
   |
44 | use mach2::ndr::*;
   |            ^^^ could not find `ndr` in `mach2`

That's because ndr was added in version 0.4.2.
Note that the lock file specifies version 0.4.2 which explains why this error doesn't happen normally.

@cfallin: here is the cherrypick onto 21 ^ (I cannot edit the reviewer and the system autoassigned @abrown).


add prometheus observability driver

[x] I have read and agree to the contributing guidelines for submitting new pull requests.

Describe your changes
Adds tests, and driver for prometheus observability
Issue ticket number and link
NA
Example usage:
    observability_driver = PrometheusObservabilityDriver(
        service_name="get_experts", span_processor=BatchSpanProcessor(ConsoleSpanExporter())
    )

    with Observability(observability_driver=observability_driver):
        # Build the workflow
        workflow = Workflow(...)
        # add tasks
        workflow.run()

Thanks for the PR @jm-nab! Our guidelines on integrations have changed slightly, please create this as a Griptape Extension.
Once that is working we can discuss upstreaming into griptape core.

@collindutter Thanks! I'll take a look at that.


AngularJS renders too slowly or not at all without $scope.$apply in cs-wizard

The task is to figure out what AngularJS does in the 2-3 seconds between the end of the execution of our code and the html rendering.

The problem can be found on the branch unLoadRouter and from the commit 6439eab6691a6b59d5b9757cfbf2f7dc42c9dfac, under the link http://localhost:8000/sample.html#!/planets/37

The time is lost between the csWizard and csWizardPanel.

Please merge the latest master into your branch, as it contains a modification that removes the unnecessary scope.apply()

If instantly the url (i.e.  http://localhost:8000/sample.html#!/planets/37) is called, then the form is loaded, but if a link is clicked on the index page then the form is not loaded.
Log:

[15.51 s] csWizard singlePage branch
[0.108 s] csWizard finish

And the application loads neither the csWizardPanel, nor the csForm.


Add SUPPORT.md

Adding this file to the root of the project will make a note appear when
opening a new issue, asking the user to first read this document.
As proposed in #802

Anything holding us back from merging this?

No, not really


Add auto apply labels workflow for PRs

This workflow will automatically apply labels to PRs based on the branch name whenever a new PR is opened.

This will help us to filter out PRs intended for a specific branch e.g PG11, PG12, PG13, PG14, PG15, master and any PR for other ongoing project branches.

Currently it supports only PG11, PG12, PG13, PG14, PG15 and master. We can add more by adding a new entry(as shown below) in the .github/labeler.yml file.

tag_name:
- base-branch: 'branch_name'

Looks Good


Dialog doesn't run during remote installation

debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline

This error message comes up when running ./setup_new_pi from a fresh Ubuntu vm. Installing the dialog utility doesn't help. I think that it is stopping some parts of CATAN from installing.
Something along these lines:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/130519

Installing dependencies . . .
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Requirement already satisfied (use --upgrade to upgrade): requests in /usr/lib/python2.7/dist-packages
Cleaning up...
Configuring network interfaces...
sed: -e expression #1, char 7: extra characters after command
bash: line 45: -e: command not found
bash: line 46: -e: command not found
Configuring front end Wi-Fi...
Configuring /etc/default/ifplugd...
cp: cannot stat ‘/etc/default/ifplugd’: No such file or directory
sed: can't read /etc/default/ifplugd: No such file or directory
sed: can't read /etc/default/ifplugd: No such file or directory
Configuring /etc/default/isc-dhcp-server...
Configuring /etc/dhcp/dhcpd.conf
More worrying output from the install script over ssh

Pretty sure the install still goes fine with this messages.  Tested it a few times on my end.  The ifplugd ones should have been corrected.


Beta updates not pushing to phone

I have been part of the beta for some time. I recently purchased a Pixel XL from the Google store. The beta version of this app does not push to the phone and it is not listed in my "beta" tab in the Play app store. Any ideas how I can trigger this? I thought about manually downloading the APK from here, but not sure if that will be seen as a different approach and consequently not get future beta releases pushed to my phone.

I've neglected the beta channel a bit, just added an update there, should show up soon.

Perfect. Thanks. Is there a preferred method to the beta channel?
On Fri, Nov 11, 2016, 12:00 AM Jan Berkel<EMAIL_ADDRESS>wrote:

I've neglected the beta channel a bit, just added an update there, should
show up soon.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jberkel/sms-backup-plus/issues/697#issuecomment-259902248,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABOCZyc-uT3c6MiPYXh5bEpjibYzFvXfks5q9CCvgaJpZM4KvVlZ
.

i've updated the instructions: https://github.com/jberkel/sms-backup-plus#beta.
please reopen if you have trouble getting it installed.


feature: add scenario?

Any plans about adding OpenScenario?  like playing Scenarios according to the .xodr and .xosc files and make web  animation.

This would fit well together with #8 . I have more time to work on this project soon and will check it out.

esmini https://github.com/esmini/esmini is a good example, which is referenced a lot in OpenScenario documentation


I am try to fetch data from firebase firestore on client side.

import { getApp, getApps, initializeApp } from "firebase/app";
import {
  connectAuthEmulator,
  getAuth,
  inMemoryPersistence,
  setPersistence,
  signInWithCustomToken,
} from "firebase/auth";
import { clientConfig } from "@/config/client-config";
import { getOrInitializeAppCheck } from "@/app-check";
import { doc, getDoc, getFirestore, onSnapshot } from "firebase/firestore";
import { useAuth } from "@/authContext/AuthContext";

export const app = !getApps().length ? initializeApp(clientConfig) : getApp();
export const getFirebaseApp = () => {
  if (getApps().length) {
    return getApp();
  }

  const app = initializeApp(clientConfig);

  if (process.env.NEXT_PUBLIC_FIREBASE_APP_CHECK_KEY) {
    getOrInitializeAppCheck(app);
  }

  return app;
};

export function getFirebaseAuth() {
  const auth = getAuth(getFirebaseApp());

  // App relies only on server token. We make sure Firebase does not store credentials in the browser.
  // See: https://github.com/awinogrodzki/next-firebase-auth-edge/issues/143
  setPersistence(auth, inMemoryPersistence);

  if (process.env.NEXT_PUBLIC_EMULATOR_HOST) {
    // https://stackoverflow.com/questions/73605307/firebase-auth-emulator-fails-intermittently-with-auth-emulator-config-failed
    (auth as unknown as any)._canInitEmulator = true;
    connectAuthEmulator(auth, process.env.NEXT_PUBLIC_EMULATOR_HOST, {
      disableWarnings: true,
    });
  }

  return auth;
}

export async function userDb(refName: string) {
  const { user }: any = useAuth();
  if (!user) {
    return;
  }
  const auth =  getFirebaseAuth();
  const { user: firebaseUser } = await signInWithCustomToken(
    auth,
    user.customToken
  );
  const db =  getFirestore(getFirebaseApp());
  const docRef = doc(db, refName, firebaseUser.uid);
  const docSnap = await getDoc(docRef);
  if (docSnap.exists()) {
    console.log("Document data:", docSnap.data());
  } else {
    // docSnap.data() will be undefined in this case
    console.log("No such document!");
  }
}

Hey @Henex1!
Client-side firestore requires to be called in authenticated environment.
You are using setPersistence(auth, inMemoryPersistence); as in starter example, which causes firebase client authentication to reset on page refresh.
You basically have two options here:

You remove setPersistence(auth, inMemoryPersistence); and keep both server and client session active. You will have to keep those two session synchronised, otherwise you will run into consistency issues

You can use signInWithCustomToken from firebase/auth before you use client-side firestore. You can pass server token to signInWithCustomToken and it should enable authenticated firebase environment until next page refresh

See https://firebase.google.com/docs/auth/web/custom-auth#authenticate-with-firebase for more information on how to use  signInWithCustomToken

Please can you give me a sample code using the first option. I am still confused

This one is still not working.
"use client";
import { getFirebaseApp, getFirebaseAuth } from "../../lib/utils/auth/Firebase";
import { doc, getDoc, getFirestore } from "firebase/firestore";
import { useAuth } from "@/authContext/AuthContext";
import { signInWithCustomToken } from "firebase/auth";

const AuthUser = () => {
  const { user }: any = useAuth();
  if (!user) {
    return <>Loading</>;
  }
  console.log(user)
  const auth = getFirebaseAuth();
  const dataFetecher = async () => {
    try {
      const { user: authUser } = await signInWithCustomToken(
        auth,
        user.customToken
      );
      // Signed in
      // Handle the signed-in user information
      const db = getFirestore(getFirebaseApp());
      const docRef = doc(db, "umu-uzongwa-members", authUser.uid);
      const docSnap = await getDoc(docRef);
      if (docSnap.exists()) {
        console.log("Document data:", docSnap.data());
      } else {
        // docSnap.data() will be undefined in this case
        console.log("No such document!");
      }
    } catch (error) {
      // const errorCode = (error as { code: string }).code;
      const errorMessage = (error as { message: string }).message;

      // Handle the error
      console.log(errorMessage);
    }
  };
  dataFetecher();
  return (

          Data information, please check

  );
};

export default AuthUser;

Hey, I just tested signInWithCustomToken and can confirm that it does not work with server token. I am investigating the issue and will get back to you shortly

In the meantime, you can just remove following lines to make firestore work on the client-side:
  // App relies only on server token. We make sure Firebase does not store credentials in the browser.
  // See: https://github.com/awinogrodzki/next-firebase-auth-edge/issues/143
  setPersistence(auth, inMemoryPersistence);

I created a pull-request that exposes customToken in handleValidToken and getTokens. This customToken can be used together with signInWithCustomToken to authenticate Firebase Client-side SDKs.
https://github.com/awinogrodzki/next-firebase-auth-edge/pull/206
I will be releasing canary version with those changes soon. I'll keep you updated here.

Thank you so much for your effort, I have updated the npm version to 1.5.3. I have removed this line
  setPersistence(auth, inMemoryPersistence);

But I am still getting this error from the console on the browser.
Cannot read properties of undefined (reading 'customToken') AuthUser.tsx:  undefined
Is there anything I am suppose to modify on the middleware?

I think you are getting this error by trying to access user.customToken value and user is undefined in this case

@Henex1 you can now install<EMAIL_ADDRESS>In this version, getTokens and handleValidToken exposes customToken string, which you can use together with signInWithCustomToken

Ok @awinogrodzki please any code sample on how to use it to read data from firebase firestore client db? Thank you so much.

Hey @Vicidevs @Henex1! Thank you for you patience.
I have improved starter example and added example to update Firestore using Client SDK

Here's the function where we call signInWithCustomToken and Firestore Client SDK methods: https://github.com/awinogrodzki/next-firebase-auth-edge/blob/main/examples/next-typescript-starter/app/profile/UserProfile/user-counters.ts
Don't forget to pass custom token to user object, as in here: https://github.com/awinogrodzki/next-firebase-auth-edge/blob/main/examples/next-typescript-starter/app/shared/user.ts#L28
In case you plan to setup starter example, please remember to setup Firestore Database rules as mentioned in starter readme: https://github.com/awinogrodzki/next-firebase-auth-edge/tree/main/examples/next-typescript-starter#configuring-firestore-rules
I also added documentation on how to use client-side APIs: https://next-firebase-auth-edge-docs.vercel.app/docs/usage/client-side-apis#using-firebase-client-sdks
Please make sure to upgrade to<EMAIL_ADDRESS>Also, please note that with the introduction of custom token, the size of authorization cookie has increased twice in size, so if you use custom claims, it's recommended to set enableMultipleCookies to true, unless you're using Firebase Hosting: https://next-firebase-auth-edge-docs.vercel.app/docs/usage/middleware#multiple-cookies


Want to be a contributor

@xmnlab Hey, I want to be contributor. Could you please accept my PR?

@conda-forge-admin,please add bot automerge

@conda-forge-admin, please rerender

thanks @abhijeetSaroha for helping here.
PS: next please don't remove the original text in the first comment, that is the guides/checklist for the PR.


Visually differ the site from onetech.info

Small background avatar in a corner of the screen?
Can quickly identify if you may be accidentally viewing onetech.info.

Considering reskinning the colour shades. I grabbed #BA93DB from the AHAP Steam banner and made a Monochromatic pallet based upon it, giving me various shades which I then roughly transformed against the existing design:

#151515 > #231133
#222222 > #342342
#333333 > #675675

Pallet:

Outcome:

vs Original:

I'm not quite happy with this, but I think purple is the right direction to signify AHAP or at least provide a quick recognition that this is AHAP and not OHOL.
I'll play around with the shades and see if I can better match the original scaling from black, but with a purple tint.


Updates to READMEs & Containerfiles

this PR:

removes chatbot,model_services/builds/arm,x86
moves Containerfile to ./model_services/base/Containerfile
adds a chatbot/model_services/cuda
moves the current x86/Containerfile under chatbot/model_services/cuda/
updates READMEs
adds docs for how to run sample app alongside model-service
adds gitrepo to ai-studio.yaml - so all that's required to pass to podman-desktop is the single ai-studio.yaml file, then, contextdir is relative to the root of the gitrepo, and containerfile is relative to contextdir
adds backend to ai-config to distinguish between multiple images with same arch
adds gpu-env to distinguish images by gpu environments

note:

We talked about stripping the 'sample-app' logic from the model-service Containerfiles - that can be a follow-up PR
I built the images and pushed to quay.io/sallyom/model-services, see the ai-studio.yaml where i have those images listed/commented.

@sallyom @MichaelClifford adding it here but it can be handled discusses somewhere else. Another thing that would be useful for us would be to add a version value to the ai-studio.yaml file. So if in future there is some breaking changes we can check the version and know how to parse the file/which schema to use.

@MichaelClifford I don't think we're using the Makefile - we could update it but rn it doesn't match our docs, should we remove it for now?

@MichaelClifford I don't think we're using the Makefile - we could update it but rn it doesn't match our docs, should we remove it for now?

yeah, that was something I was using a while back. We can probably remove it. But that can also happen in a separate PR.

@MichaelClifford I made this PR smaller - split up other changes into follow-ups - went from 24 files changed to 12, ptal!

Thanks @sallyom 😄


Firestore VectorValue type

@paulb777, fyi, this PR adds a new public FST class that will break FST's SPM-binary build until a new XCFramework is staged. I'm kicking off a zip build to stage a FST to fix CI.


[T1Lib] T1Font.saveAs() broken?

After doing:
t1 = T1Font('font.pfb')
t1.parse()
t1.saveAs('font-out.pfb', 'PFB')

and trying to open the resulting pfb file in fontforge I get an error from fontforge:

Didn't understand "/...  " in blended font defn

This happens for every .pfb font I've tried (the original files are opened in fontforge with no problems at all).
Using the latest pip3 install of fontTools

fonts.zip

I've managed to fix the problems, but be aware that Type 1 is extremely Legacy, and fontTools.t1Lib is hardly maintained.
fontTools.t1Lib has had only limited use, and mostly for reading. Writing has hardly been testing in the field.
So while #3240 seems to address the issues exposed by this font, I'm not guaranteeing much support for the future.
Please reconsider wether you really really really need Type1 fonts in the first place.

Thanks form the prompt fix!
I've run your commit and the result causes the fontforge to output the same error. Not sure, what the problem is. At one point I thought that it's because I'm running it in python3 (the T1Font page on python docs says something like "python 2 only"), so I tried running under Python 2 and I get this:
Python 2.7.16 (default, Mar 25 2021, 18:52:10)
[GCC 4.2.1 Compatible Apple LLVM 10.0.1 (clang-1<IP_ADDRESS>)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

from fontTools.t1Lib import T1Font
Traceback (most recent call last):
File "", line 1, in
File "/Users/user/Code/Python/lib/fontTools/init.py", line 2, in
from fontTools.misc.loggingTools import configLogger
File "/Users/user/Code/Python/lib/fontTools/misc/loggingTools.py", line 5, in
from collections.abc import Mapping, Callable
ImportError: No module named abc

Any ideas on how to troubleshoot this?
As for your:

Please reconsider wether you really really really need Type1 fonts in the first place.
well, the Type1 fonts may be retired by Adobe, but these are almost exclusively the fonts used in TeX/LaTeX typesetting. In other words, pretty much every scientific paper published to date (I mean those that were electronically typeset, and I exclude the ugly MS Word-typeset ones) and pretty much every paper that will be publish in the next decade will be using Type1 fonts exclusively.

(The reason is that in TeX/LaTeX, there are gazillion lines of tex code written for packages that heavily rely on the fonts being in the TFM/PFB combo; It's hard to imagine how a transition may occur to anything other than that. There's, of course, XeTeX/XeLaTeX, which uses TTF fonts, but it's incompatible on the package level, and so despite some initial promise, its use by the scientific community is negligible)
So, I am sorry to say that as far as publishing science is concerned, Type1 fonts are to stay for at least another decade (subjectively).
And as for whether I personally really need these — yes, I'm myself a scientist and I'm writing a tool that will migrate pre-Type1 era scientific papers to the Type1 era, so to say, by replacing the Type3 fonts with Type1 — kinda like what the https://en.wikipedia.org/wiki/Pkfix and https://ctan.org/pkg/pkfix-helper?lang=en do, but for PDFs instead of Postscript files.
Why not move one step further: Type3 --> TTF. Well, because these old fonts are only available in Type1, and some of them — not even in Type1, but in the form of the METAFONT sources (https://en.wikipedia.org/wiki/Metafont). And for these I am using a tool called mftrace  (https://ctan.org/pkg/mftrace?lang=en) that vector-traces bitmaps with the help of potrace (https://potrace.sourceforge.net/) to produce, you guessed it, Type1 PFB files.
Now, if you know of a way to convert Type1 to TTF I would love to use it of course — that would add another step to all the processes I described above, and in the end my code would go for a direct replacement of Type3 --> TrueType inside PDFs. Otherwise, I guess I am stuck with Type1 and with asking you to fix more bugs.
An alternative would be for me to read the Adobe Type1 font spec, figure out what the current code in T1Lib does, and join the ranks of its developers. But frankly, I am already overstretched as it is, given the mess I mentioned above.
And this is why I am really really asking for help here. And I think the cause is worth the effort.
Btw, when in my first successful test a file is converted from using raster fonts at 300dpi to using vector Type1 fonts (with proper hinting) the results look just amazing. Let me know if you have time for watching a few beautiful glyphs in the formulas in scientific papers, I might upload a few. If not just take my word for it — this might give new life to tons of old papers, for which no TeX/LaTeX sources exist anymore. And which look uglier than they should.

I've run your commit and the result causes the fontforge to output the same error.

No idea — are you sure you are running the patched fonttools?

so I tried running under Python 2

FontTools does not support Python 2.

I've run your commit and the result causes the fontforge to output the same error.

No idea — are you sure you are running the patched fonttools?

I am: I cloned master, but it for some reason had the old version of the file (so I assumed the commit was to a branch other than master, but I couldn't figure out which), so what I did was: I opened the commit page:
https://github.com/fonttools/fonttools/commit/2808d995b2e66969d84470450b168d928c0336d7
then clicked browse files:
https://github.com/fonttools/fonttools/tree/2808d995b2e66969d84470450b168d928c0336d7
then clicked Code and chose to download ZIP.
After unpacking I made sure the new t1Lib/init.py reflected the changes you made (all this bc I have no idea how to use github properly, I suppose). But none of that helped.

so I tried running under Python 2

FontTools does not support Python 2.

https://fonttools.readthedocs.io/en/latest/t1Lib.html — I meant the header here.

https://fonttools.readthedocs.io/en/latest/t1Lib.html — I meant the header here.

Ah, that's a stale comment. I've removed it in my PR.
What you can do to check whether you are actually running the patched module is to introduce an error, say add raise AssertionError("test") at some place in the patched code that you know must run. For example in the T1Font.__init__().

Did that, and it raises the error, as expected.
I've attached the before/after pfb files, as well as the init.py file I got.
fonts.zip

I don't have fontforge, but another tool opens the "-out" font just fine (which it didn't with your initial fonts.zip). There still may be something wrong with the font, but I'm out of capacity to debug this further. If you can find out specifically what makes fontforge choke on this font we can perhaps work out a further fix.

I tried to use the resulting file with pdftex (it embeds pfb files into PDF, basically). The output:
!pdfTeX error: pdftex (file ./file-out.pfb): 138039 bytes more than expected
==> Fatal error occurred, no output PDF file produced!

I merged #3240, but will reopen this as the issues aren't completely resolved.

@sl2c with this script you can convert a Type 1 font into an OpenType-CFF font.
If you need a TrueType font you can use otf2ttf.py to convert the OTF font.

@justvanrossum I used the AFDKO's detype1 tool to convert the font-out.pfb file into a PFA and the charstrings are garbled. If I use font.pfb instead the charstrings look correct.

Is the out font you’re looking at made with fonttools after my initial set of fixes? Because I did fix a lot, but apparently not enough. But I believe the charstrings survive now.

But I believe the charstrings survive now.

Confirmed. My feedback was based on a file that was posted at the start of the thread.
I've updated to 4.42.1, round-tripped the PFB font, and the output looks good. Sorry for the false alarm.


Fix webcam support on Linux

This requires that we set a format string to "v4l2" when opening the
camera. Complicating matters is the usage of the "mjpeg" format string
that can offer higher frame rates and resolutions on common
webcams. Usage is simple: specify "mjpeg" as the format
string. Internally, we explicitly attach an MJPEG decoder to a v4l2
input format.
Fixes #52

Quick ping. I need to cut a new release of the package; any chance you can merge this PR into your audio work and then PR the audio work back?


Object parsing and symbol table writing

POC at ranlib branch for elf files (gnu format only) right now.
It uses object parsing code from zld directly with minimal changes to compile without unneeded files, but maintains compatibility with upstream zld.

[x] ELF symbols
[x] MachO symbols
[ ] PE/COFF symbols (currently blocked by missing upstream support from zig/zld)
[X] GNU & Thin format
[X] GNU64 format
[x] BSD format
[x] Darwin (BSD64) format (llvm doesn't seem to support this format)
[ ] Microsoft ECOFF extended sorted symbol table (not sure if wanted as llvm doesnt seem to support it?)
[x] FreeBSD style archives with GNU symbol table but BSD string format (but does this even exists?) (not needed, see below)

[ ] Support sorted BSD and Darwin formats
[ ] Investigate consequences of not having a symbol table in darwin (32 and 64)

Pretty much any change beyond this point would require some clarification from Jakub. I will ask him soon.
Anyways, valid symbol tables are generated for simple linux (elf) and mac (macho) archives. Need more testing on a bit larger projects.

FreeBSD seemed to follow GNU format completely, tested FreeBSD 12 on QEMU.

Can you make please make a PR? Happy to help with resolving differences in how symbols are handled.

Coff symbols is being worked at coff-sym branch.
Also submitted the coff parser as a PR to zld.

@moosichu I am a bit lost right now. It seems that native mach archives (the ones in test/data/test5) are generated quite a bit differently in that they are in non-deterministic mode by default. Did you used any additional flags or my assumption is correct?
If so, I wonder how to deal with, like maybe create a new ArchiveType darwin which is basically bsd + U flag + sorted table and other minor differences, and then have it as default type on MacOS?

It should only be considered as a test case for parsing. It's a native archive, i.e. one generated by the native OS archived on Darwin. Not LLVM ar.

Oh well that's great then. I will wrap up everything soon then.


fix: redraw tabline whenever marks change

Right now when you add a file to harpoon, the tabline doesn't update and add your new file.

Now tabline.setup registers a callback on the changed event of harpoon.marks.
I couldn't require('mark') inside the tabline.setup because it caused a circular import. This is why I required harpoon inside each function in harpoon.marks so that I could call require('mark') without causing a circular import
I couldn't come up with a better solution.

I did the same with less code here (plus a fix):
https://github.com/ThePrimeagen/harpoon/pull/290

Don't you think its bad practice to check global settings inside of an emitter function. I presumed the whole point of the event system implemented was so that other functions like the tabline could register callbacks to run on a certain event and the event emitter doesn't need to know internal details.
In any case, thanks a lot for the tabline, it has made my workflow close to perfect. Really amazing job, thanks a lot.


how to fix feature encoder weights during SS process

during pythorch version
new_weight = self.weight.mul(new_mtl_weight)(line 95 in conv2d_mtl.py)
self.weight = Parameter(torch.Tensor(out_channels, in_channels // groups, *kernel_size))(line 42 in conv2d_mtl.py)
How to load pretrained and fix feature encoder weights during SS process?

How to freeze the convolution weights?
If you set mtl=True in the following line:
https://github.com/yaoyao-liu/meta-transfer-learning/blob/fe189c96797446b54a0ae1c908f8d92a6d3cb831/pytorch/models/resnet_mtl.py#L165
It means that you're using _ConvNdMtl function, so
https://github.com/yaoyao-liu/meta-transfer-learning/blob/fe189c96797446b54a0ae1c908f8d92a6d3cb831/pytorch/models/conv2d_mtl.py#L45
i.e., the convolution weights are frozen.
How to load the pre-trained model?
You may directly load normal checkpoints to MTL models like this:
https://github.com/yaoyao-liu/meta-transfer-learning/blob/fe189c96797446b54a0ae1c908f8d92a6d3cb831/pytorch/trainer/meta.py#L69
If you have any further questions, feel free to ask.

Thanks for your detailed reply. I can completely understand the experiment now.
在 2021-05-12 17:26:14，"Yaoyao Liu" @.***> 写道：
Reopened #52.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thanks for your detailed reply. I can completely understand the experiment now.

new_mtl_weight = self.mtl_weight.expand(self.weight.shape)
new_weight = self.weight.mul(new_mtl_weight)
I don't fully understand your code, self.weight should be the weights in the pre-training model, why self.weight = Parameter (torch.Tensor (.
In_channels, out_channels / / groups, * kernel_size) to generate


Can you assign the ctrl - alt - v shortcut to another browser?

I am fairly new to programming and tend to use safari as my default browser. I do know you can use ctrl - alt - s with this plugin to open in safari but I am just curious if there is a way to alter user settings to ctrl - alt - v so that will also use safari as the default?
I have tried creating a sublime-settings user file and putting in:

{
"selectedBrowser": "safari"
}

but this does not work. Does anyone know of another way

The working method for setting Safari as default is:
{
  "browser": "safari"
}


server.py example: corebluetooth missing argument: 'max_write_without_response_size'

The problem
I am getting the following error when running the server.py example:
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/bless/backends/corebluetooth/server.py", line 191, in add_new_characteristic
    await characteristic.init(service)
  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/bless/backends/corebluetooth/characteristic.py", line 78, in init
    super(BlessGATTCharacteristic, self).__init__(obj=cb_characteristic)
TypeError: __init__() missing 1 required positional argument: 'max_write_without_response_size'

Reproduction
Run the example code of server.py on macOS
Expected behavior
The example should run without errors...
Screenshots
None
Desktop (please complete the following information):

OS: macOS 12.6

Additional context
None
Thanks for the work on bless and let me know if I can provide any more information to resolve this issue

:point_up:

Is there any workaround for this bug? E.g. by using previous versions of bless?

This is fixed in development. I should be merging this into the next version soon. If you need it to work now. You can install the current development version and it should work.
pip instal git+https://github.com/kevincar/bless@develop

Just as a feedback: This development version seems to be working fine. I am still having some issues with the bidirectional data transfer, but this does not seem to be related to the bluetooth interface.

@runman19 Is the bidirectional data transfer related to this issue or something else?

@kevincar, isn't a similar correction necessary for the other backends? It seems I got the same error on a RPi using de bluezdbus backend. Sorry, but I am don't understand the code well enough to make the correction myself.
@WouterJD, maybe you cn reflect on this as well.


WIP: Implement logic to send service logs to syslog

Motivation
Several of the CF and Diego platform services send logs to the local syslog, tagged as vcap.*. . The metron agent from loggregrator configures the local syslog to send the logs to metron so that later can be sent to a centralised logging service.
In some cases it is the service application itself who sends the logs to syslog, but it seems to be a common pattern across CF and Diego services to let the service log to stdout/stderr, and redirect that output to local files or syslog using the logger command.
Not all the services implement this feature, and instead they only log to local files. In order to centralise all the logs, so we will add the logic required to send the logs of the missing services.
We will implement the log to stdout and redirect  to logger pattern whenever is possible.
Implementation in logsearch bosh release
We want to implement the same idea in all the logsearch services.
For that we we add several properties: <service>.log_to_syslog. When true, we redirect the stdout and stderr in the ctl script into syslog following the standard vcap pattern, in addition to files.
The only exception is redis in the queue job. In that case, we use redis capabilities to send logs to syslog, to avoid complex setups deamonising redis.
How to review?
Enable the *.log_to_syslog and deploy. Logs should be sent to syslog.
If metron agent is installed locally, the logs will be redirected to metron agent the loggregrator.
Open questions
This PR is open to debate for several open questions:

Is OK to add a specific property to enable this feature for each service? Shall we use one unique property? or should this be enabled by default?
Is the tag vcap.* the most appropriate one? This is not a CF official release. But the generic tag vcap.* might be handy to refer to a service deployed with bosh.
tee and logger run as root. Is that fine?

@keymon We had a similar requirement a while ago and we came up with the syslog_forwarder job that can be added as a job template to any VM, it creates a configuration file for rsyslogd instructing it to pick up the contents of certain files and send them to a remote syslog server.
it's configured like this.
Is this mechanism not sufficient for you?

Yep, we were considering do something like that, but we wanted to get the feedback from the community first, that is why we did this PR.
In the CF/Diego ecosystem they are doing the tee+logger redirect approach for all the services. But we were not sure for 3rd party community releases like this one.
Your approach is good for me, and if this is the way you want to proceed, feel free to close this PR. But if you prefer follow the pattern of the CF/Diego ecosystem, we can iterate on this PR.
Thx!

@keymon the reason syslog_forwarder gets my vote is because its an out-of-box functionality, it has no external dependencies and it's easy to simply not deploy it if it's not needed. This was the driving logic behind its implementation.
However, I generally like loggregator and I certainly see some merit in using a logging infrastructure that works similarly to CF/Diego so I'm happy to debate it.
I see one big difference between the 2 approaches and it is the log destination. syslog_forwarder was designed to make it easy to ship the logs from the logsearch VMs to the cluster monitor VM, which, just to make it clear, is not the same ElasticSearch cluster as the "main" logsearch cluster. Whereas if the logs are picked up by the loggregator pipeline (I assume it's the CF loggregator pipeline) they will end up where all the other deployment logs are.
Does that make sense? Please explain if I misunderstood your use-case.

syslog_forwarder was designed to make it easy to ship the logs from the logsearch VMs to the cluster monitor VM, which, just to make it clear, is not the same ElasticSearch cluster as the "main" logsearch cluster. Whereas if the logs are picked up by the loggregator pipeline (I assume it's the CF loggregator pipeline) they will end up where all the other deployment logs are.

That is actually a good point. Currently we use loggregator and the same logsearch for everything. I guess we will check the local files in case of trouble in the logsearch cluster itself.
For me is fine and makes sense. I will close the PR.
Thank you!


Make inline results copy&paste'able

:memo: Summary
At the moment, results showed inline cannot be selected, copied and then pasted elsewhere. This functionality is available for results showed in the dock.
:checkered_flag: Motivation
I prefer to have my results showed inline, especially for plots and/or tables, because there is just more space available. On the other hand, I sometimes do calculations and would like to copy results into a LaTeX (or other) document. Also, the only way to switch between inline and dock view is by changing the settings, there is no quick toggling of this setting via the command palette.
:runner: Approach
As I understand, inline results are showed in an additional div attached to a marker. An easy solution could be to add the icon-clippy button clipboard icon (that is shown in the dock) just below the x icon that closes the div. The onclick event handler would probably need a few changes.
:anchor: Drawbacks
I see absolutely no drawbacks.

inline results are "copy & pastable" already, just click it to copy into clipboard, as the hover message says.

While looking at the code yesterday, I saw that there should be a tool tip. However, there is not. Also, I can click on the result as much as I want, nothing is ever copied.
I will open another issue about the bug.


modify chart.yaml

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. E.g. helm upgrade on minikube, helm install on gke)

It looks like @abal09 hasn't signed our Contributor License Agreement, yet.

The purpose of a CLA is to ensure that the guardian of a project's outputs has the necessary ownership or grants of rights over all contributions to allow them to distribute under the chosen licence.
Wikipedia

You can read and sign our full Contributor License Agreement here.
Once you've signed reply with [clabot:check] to prove it.
Appreciation of efforts,
clabot


listing registers

The command :registers, while recognized by the command menu, does not seem to do anything.

We are hoping to have some form of UI, either in the same location as problems UI at the moment (the bottom) or maybe the sidebar. This would be for registers, as well as potentially say marks etc. Its part of the potential work for this current vim specific block of work.

I personally dont think that the problems/info UI is a good fit, although this might be because those are still a bit clunky when it comes to keyboard navigation.
VSCodeVim has a nice solution where :reg for example shows all registers with values in the same way as a file search result, so you can navigate and select from it in the same way. Could be a nice way of handling :ls as well..

i think that having something that allows using a minimum number of keys, such as the way that :reg works on vim, is useful for this kind of command that you just fire to "refresh your short term memory". Of course only my 2 cents, I may be wrong.


fix: workflows query issues

Description
Changelog

Removed create module options from workflows queries inside apps
Added error handling for undefined js actions

PR fixes following issue(s)
Fixes #31048
Type of change

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

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[ ] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

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

Checklist:
Dev activity

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

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

Summary by CodeRabbit

New Features

Enhanced the action entity component to include pluginType, enabling conditional rendering of menu options based on the plugin type.

Bug Fixes

Fixed an issue in the JavaScript action utility to safely iterate over variables, preventing errors when the variable list is uninitialized.

Closing this as it does not have an appropriate label associated with a pod

/ok-to-test<EMAIL_ADDRESS>@tag.IDE @tag.JS"


Slate is missing sounds on touch down and on touch up. These should be configurable via OnTouchDown and OnTouchUp events in the slate contents, like we do for manipulation.

Ported to Github, reference 21090800.
Slate is missing sounds on touch down and on touch up. These should be configurable via OnTouchDown and OnTouchUp events in the slate contents, like we do for manipulation.

Merged


add test for allow partial case

Add test for case where only 1 of 2 configured attributes is present, but allow partial is specified.

This change is

Merged manually to apache/master.


Add endpoint parameter to LogsClient and MetricsClient

What caused the recordings to change?

An additional recorded variable.


Introduce join provisioning

When provisioning the device during runtime (e.g. through serial, WiFi or Bluetooth), we need to be able to set the AppEUI and AppKey, without having to join, or let it reset before join.
Proposed API:
bool provision(const byte appEui[8], const byte appKey[16]);

This method does a mac set appeui, mac set deveui and mac save, see command reference.
Then, you can call just join() in setup() or loop(), that uses the AppEUI and AppKey from memory, and thus only takes retries, as in #39

As part of this change bool join(const byte appEui[8], const byte appKey[16]) should first call provision(const byte appEui[8], const byte appKey[16]) and then bool join()

Closed by #59


Add makefile that uses system mbedTLS

Original makefile is still available with make -f localmbedtls.mak

@jkarneges IIRC you maintain the .deb build scripts; this (among other benefits) should make those closer to upstream.

I'd like to get the Debian-specific patches as small as possible, and this would definitely help.
But I wonder if this patch could break other ports: For example, I noticed it removes OPTLIBS from the LIBS variable. And OPTLIBS seems to be used for solaris and mac targets.

@jannic good catch; I intended to change the OPTLIBS to LDFLAGS in the various port targets, and will do so now.  OPTLIBS appears to have the same meaning as the more traditional LDFLAGS.

Reviewing the makefile, I see there is a separate "OPTLIB" passed to some recursive make invocations; however it never seems to be set, and nobody has complained about things working.  I'll save changing that for a future PR though.


[Feature Request] random pick one problem

now show command will randomly pick one non-AC problem if problem id/name not provided. e.g.
$ leetcode show