Automate release creation

Fixes #503
Test command:
./create-release.py prepare --version 1.3.0

Sample results:
-----------------------------------------------------------------
--------------------- Release configuration ---------------------
-----------------------------------------------------------------
Goal 		 -> prepare
Git URL 	 -> git@github.com:elyra-ai/elyra.git
Git reference 	 -> HEAD
Git user 	 -> Luciano Resende
Git user emain 	 -><EMAIL_ADDRESS>Work dir 	 -> /Users/lresende/opensource/elyra/elyra/build/release
Source dir 	 -> /Users/lresende/opensource/elyra/elyra/build/release/elyra
Old Version 	 -> 1.3.0.dev0
New Version 	 -> 1.3.0
Release Tag 	 -> v1.3.0
-----------------------------------------------------------------

Processing release from 1.3.0.dev0 to 1.3.0

-----------------------------------------------------------------
-------------------- Retrieving source code ---------------------
-----------------------------------------------------------------
Cloning repository: git@github.com:elyra-ai/elyra.git
Removing working directory: /Users/lresende/opensource/elyra/elyra/build/release
Creating working directory: /Users/lresende/opensource/elyra/elyra/build/release
Cloning : git@github.com:elyra-ai/elyra.git to /Users/lresende/opensource/elyra/elyra/build/release

-----------------------------------------------------------------
--------------------------- Building ----------------------------
-----------------------------------------------------------------

... build output suppressed ...

-----------------------------------------------------------------
------------------------ Release Files --------------------------
-----------------------------------------------------------------

Location 	 /Users/lresende/opensource/elyra/elyra/build/release/elyra/dist

total 36696
drwxr-xr-x  11 lresende  staff       352 Oct 12 13:04 .
drwxr-xr-x  38 lresende  staff      1216 Oct 12 13:04 ..
-rw-r--r--   1 lresende  staff    436731 Oct 12 13:04 elyra-1.3.0-py3-none-any.whl
-rw-r--r--   1 lresende  staff  17989343 Oct 12 13:04 elyra-1.3.0.tar.gz
-rw-r--r--   1 lresende  staff      9631 Oct 12 13:03 elyra-code-snippet-extension-1.3.0.tgz
-rw-r--r--   1 lresende  staff      5667 Oct 12 13:03 elyra-metadata-extension-1.3.0.tgz
-rw-r--r--   1 lresende  staff     62483 Oct 12 13:03 elyra-pipeline-editor-extension-1.3.0.tgz
-rw-r--r--   1 lresende  staff     20047 Oct 12 13:04 elyra-python-editor-extension-1.3.0.tgz
-rw-r--r--   1 lresende  staff      5870 Oct 12 13:03 elyra-theme-extension-1.3.0.tgz
-rw-r--r--   1 lresende  staff    208535 Oct 12 13:04 jupyterlab-git-0.21.1.tgz
-rw-r--r--   1 lresende  staff     33501 Oct 12 13:04 jupyterlab-toc-4.0.0.tgz

Release version: 1.3.0 is ready for review
After you are done, run the script again to [publish] the release.

Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

@kevin-bates @akchinSTC this should be working for the release now, quick test:
./create-release.py prepare --version 1.3.0 --dev-version 1.4.0


Logic to hardcode the RPC nav link

Implemented logic to show a RPC link in the left navigation that is not based on pages front mater but hard coded logic in _includes\nav.html

Two things here:
1. This renders the "RPC" link at the bottom of the nav with a triangle to its left, implying there are sub-links, which isn't true. Please check the styling here.

Thanks @thanethomson, OK, I'll look into removing that.

2. When building the v0.37.0-rc2 docs, I see two "RPC" links at the bottom now. One pointing to the v0.37 OpenAPI docs, and the other pointing to the v0.34 OpenAPI docs.

Did you test the it before the changes were ported to v0.37.x ? If the page was removed it shouldn't show up. But I will look into this too.

@thanethomson I believe I've fixed both issues reported above. The triangle on the left was removed with commit 0ac2a33 and the duplicate RPC link is removed with https://github.com/cometbft/cometbft/pull/420


Tags with no Images

Found using Datasette. In DB2022, there are 18,009 tags which have a count of zero images.

Verify.
Remove any true zero entries

Some tags have images except the images are marked banned/deleted. Need to not count those.


Sidekiq launcher shouldn't be required except when inside a Sidekiq process

I submitted a bug to the Sidekiq project and it turned out that it seems to be a sikdekiq-cron issue.
Please have a look here:
https://github.com/mperham/sidekiq/issues/4505

In fact there appears to be a lot of code loaded at all times which should only be loaded within the Sidekiq process. Use this pattern:
Sidekiq.configure_server do
   require "..."
end

@arent-groebner ondrejbartas any tips?  Is this project still actively maintained?

@sarahgriffis  @arent-groebner hi can you try to use this new branch:
gem 'sidekiq-cron', github: 'ondrejbartas/sidekiq-cron', branch: :"fix-launcher-problem"
if it works for you? If it will work I will create new release

Hi @ondrejbartas I tested your new branch and it solved this issue

@ondrejbartas yes, this works!

@ondrejbartas: Works for me to

thanks for verification I just released sidekiq-cron (1.2.0) so you can use it. I haven't deleted fix branch so it will not mess up your deployments.

Sorry for not fixing this earlier :/

No worries at all. We appreciate the quick resolution!

Thanks for the fix!

@ondrejbartas I am still hitting this on v 1.2.0
I'm seeing Redis::CannotConnectError: Error connecting to Redis on <IP_ADDRESS>:6379 (Errno::ECONNREFUSED) during RUN bundle exec rake assets:precompile after adding the sidekiq-cron dep.
I attempted installing the gem from the branch you mentioned above as well.
Can you suggest any workarounds in the meantime? Or other things I might be able to do to troubleshoot?
I'm surprised to be hitting this since it sounds like it was indeed resolved in this version, so I'm not sure what's going on in my case.

@ondrejbartas I am still hitting this on v 1.2.0 I'm seeing Redis::CannotConnectError: Error connecting to Redis on <IP_ADDRESS>:6379 (Errno::ECONNREFUSED) during RUN bundle exec rake assets:precompile after adding the sidekiq-cron dep. I attempted installing the gem from the branch you mentioned above as well. Can you suggest any workarounds in the meantime? Or other things I might be able to do to troubleshoot? I'm surprised to be hitting this since it sounds like it was indeed resolved in this version, so I'm not sure what's going on in my case.

Update - I resolved this by adding config.assets.initialize_on_precompile = false to config/application.rb

@ondrejbartas This seems to be happening again with sidekiq-cron v 1.12.0. Is there any fix for this or do we need to downgrade?

The error still occurs during the docker image build at the command RUN SECRET_KEY_BASE_DUMMY=1 ./bin/rails assets:precompile.
rails: 7.2.1. ruby: 3.3.5, sidekiq: 7.3.2, sidekiq-cron: 1.12.0
------
 > [build 6/6] RUN SECRET_KEY_BASE_DUMMY=1 ./bin/rails assets:precompile:
0.907 bin/rails aborted!
0.907 RedisClient::CannotConnectError: Connection refused - connect(2) for <IP_ADDRESS>:6379 (redis://localhost:6379) (RedisClient::CannotConnectError)
0.907 /rails/config/initializers/sidekiq.rb:9:in `<main>'
0.907 /rails/config/environment.rb:5:in `<main>'
0.907
0.907 Caused by:
0.907 Errno::ECONNREFUSED: Connection refused - connect(2) for <IP_ADDRESS>:6379 (Errno::ECONNREFUSED)
0.907 /rails/config/initializers/sidekiq.rb:9:in `<main>'
0.907 /rails/config/environment.rb:5:in `<main>'
0.907 Tasks: TOP => environment
0.907 (See full trace by running task with --trace)
0.910 2024-11-09T20:20:52.211Z pid=7 tid=42v INFO: Sidekiq 7.3.2 connecting to Redis with options {:size=>10, :pool_name=>"internal", :url=>"redis://localhost:6379/0"}
------


Training Code

Hello, thanks for sharing this amazing research! Do you plan to release the training code?

Thanks for your interest. The training code is little messy. We may not  release it recently. Since the training process is detailed in our paper, you can also easily reimplement it by yourself.


SOLID Violation

Data/Bloggable.Data.Models/Tag.cs
Are you 100% sure that your tagging is going to be used in Posts and Pages? Why are you tightly coupling the Tag object with Posts and Pages?
You are putting a direct dependency on 2 other classes.

Actually that's to help EntityFramework generate the one-to-many relationships Tag-Posts and Tag-Pages. Also it's for ease of use when getting the most popular post tags here
Data models are classes that describe the data to be stored in the data store. As such they are like placeholders for values that generate a domain specific object - there is no logic in them. So I think that's not a problem to have all the relationships between the classes in the code. :)

I see. I would still decouple it to make it framework/storage agnostic (if you were to decide to move from EF/SQL).

Yes, I will consider it. Thanks for your suggestion! :)


Changes to 'suppression by virus of host IRF3 activity', 'suppression by virus of host IRF7 activity' and 'suppression by virus of host IKBKE activity'

'suppression by virus of host IRF3 activity'
'suppression by virus of host IRF7 activity'
'suppression by virus of host IKBKE activity'

[ ] move under  GO:0039537 suppression by virus of host viral-induced cytoplasmic pattern recognition receptor signaling pathway
[ ] change labels to  'suppression by virus of host viral-induced cytoplasmic pattern recognition receptor signaling pathway via inhibition of xx activity'

Hi Pascale,
here are some pubmeds : https://pubmed.ncbi.nlm.nih.gov/22674996/
and https://pubmed.ncbi.nlm.nih.gov/17438296/
Hope this helps
Patrick.


ic-include parses single item JSON list but not multiple items JSON list

Doing the following, when ic-include is a multiple item JSON list, will result in an error
<input type="hidden"
     ic-include='[8, 9]'
     ic-post-to="/event/some_id/day_clicked"
     ic-trigger-from="#day_label">

but works if the JSON list contains one element only
<input type="hidden"
     ic-include='[8]'
     ic-post-to="/event/some_id/day_clicked"
     ic-trigger-from="#day_label">

[8, 9] is valid and parsed when you do var obj = jQuery.parseJSON( '[8 ,9]' );
Can you do multiple items JSON lists in ic-include?

You have to create a JSON object, so that there are names for the submitted variables.


[Issue 62] Test change of scope during ref resolution

The closest parent "id" must be used to resolve refs.

Hey @Julian, have you thought any more about this PR? A test for this case would definitely be a nice thing to have. I don't think there's any way to do it without a remote reference either (though I'm not an expert and could be wrong).

I've been swamped, I was hoping someone would do the work for me here but
doesn't seem like it :/. Sorry for the delay, I'll try to give this a bit
of time this week.
On Feb 21, 2015 2:07 AM, "Ian Jeffries"<EMAIL_ADDRESS>wrote:

Hey @Julian https://github.com/Julian, have you thought any more about
this PR? A test for this case would definitely be a nice thing to have. I
don't think there's any way to do it without a remote reference either
(though I'm not an expert and could be wrong).
—
Reply to this email directly or view it on GitHub
https://github.com/json-schema/JSON-Schema-Test-Suite/pull/65#issuecomment-75359786
.

OK, the problem with this is that doing a remote request or not is a question of policy for the validator.  If they trust one schema to be accurately speaking for another (e.g. same domain, subpath, etc.) then it might be reasonable to use the existing version they already have.  Alternatively, some validators might not trust any schema to speak for another, and therefore perform a remote fetch every time.
The "id" keyword here is claiming that the schema in question is the same as the one at the supplied URL.  The below schema #/definitions/schema1 is claiming to be identical to "subSchemas.json":
"schema": {
            "definitions": {
                "schema1": {
                    "id": "http://localhost:1234/subSchemas.json",
                    "a": {"$ref": "#/integer"},
                    "integer": {
                        "type": "integer"
                    }
                }
            },
            "integer": {
                "type": "string"
            },
            "$ref": "#/definitions/schema1/a"
        },

As such, a validator would be justified in not performing a remote fetch, and resolving using the existing version it had.  However, it would be equally valid to perform a remote fetch.
So, this PR isn't quite correct, because a validator should be within its rights (depending on its own security policy) to not perform a remote fetch.  However, resolving to the outer "integer" entry is always wrong.

Thanks Geraint. isn't this just the difference between canonical and inline
dereferencing?
On 25 Feb 2015 12:32, "Geraint"<EMAIL_ADDRESS>wrote:

OK, the problem with this is that doing a remote request or not is a
question of policy for the validator. If they trust one schema to be
accurately speaking for another (e.g. same domain, subpath, etc.) then it
might be reasonable to use the existing version they already have.
Alternatively, some validators might not trust any schema to speak for
another, and therefore perform a remote fetch every time.
The "id" keyword here is claiming that the schema in question is the same
as the one at the supplied URL. The below schema #/definitions/schema1 is
claiming to be identical to "subSchemas.json":
"schema": {
"definitions": {
"schema1": {
"id": "http://localhost:1234/subSchemas.json",
"a": {"$ref": "#/integer"},
"integer": {
"type": "integer"
}
}
},
"integer": {
"type": "string"
},
"$ref": "#/definitions/schema1/a"
},
As such, a validator would be justified in not performing a remote fetch,
and resolving using the existing version it had. However, it would be
equally valid to perform a remote fetch.
So, this PR isn't quite correct, because a validator should be within its
rights (depending on its own security policy) to not perform a remote
fetch. However, resolving to the outer "integer" entry is always wrong.
—
Reply to this email directly or view it on GitHub
https://github.com/json-schema/JSON-Schema-Test-Suite/pull/65#issuecomment-75952258
.

I think there needs to be some clarification in the spec as to what 'id' is. All that's really said in the spec is a change of resolution scope. And there's also no clarification on what validators supporting inline dereferencing should do if the referenced scope does not exist within the current document, only that it "will notice that [the URI scope] is already defined within the schema, and choose to use the appropriate subschema."
I'll adjust the PR to your suggestion.

... In which case we provide both paths


Add deep merging

Hi!
I've started to use the extension but I encountered one issue - instead of deep merging config files (like VS Code does with User -> Folder settings), it merges them in a flat way. Example:
settings.shared.json
{
  "[typescript]": {
    "editor.tabSize": 4,
    "editor.tabCompletion": "on"
  }
}

settings.local.json
{
  "[typescript]": {
    "editor.tabCompletion": "off"
  }
}

settings.json
{
  "[typescript]": {
    "editor.tabCompletion": "off"
  }
}

This PR changes this behavior so settings.json would look like this:
{
  "[typescript]": {
    "editor.tabSize": 4,
    "editor.tabCompletion": "off"
  }
}

Please let me know if it makes sense for you :)
Cheers!

PS. I think it goes even deeper as in the case of launch.shared.json and launch.local.json - the launch.local.json configurations field would always replace all of configurations from launch.shared.json making the case of adding local configuration practically impossible.

I'm good with the change, thanks again for the report and fix. Would you be up for adding a test as part of this, or even a follow up if you prefer? No worries if not as that doesn't need to block, but I would like to get one of the scenarios you've shared incorporated into the test suite.
If you are then somewhere around here and similar to this test should suffice:
https://github.com/swellaby/vscode-workspace-config-plus/blob/6fd0eb56749746599b1e3090cb53f7f47adc56cc/tests/unit/file-handler.js#L200-L220
but feel free to use function-local variables/ignore any of the more global ones used in some of the other tests

@calebcartwright there you go :)


Add missing location information for some lexer errors

Fixes https://github.com/apollographql/apollo-rs/issues/731
I think these are all the missing locations, but there are a few more places that do Error::new - as far as I can tell though these errors are getting location information filled in at a later stage (via self.done()).
I saw the original issue proposed removing Error::new completely - I'm happy to do it, but it would be a break, and I'm not sure what the policy on those is in this repo.

@PhoebeSzmucer: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/

Also, totally fine to remove Error::new entirely. We are still working on the apollo-rs v1 release and we are regularly making breaking changes in apollo-compiler until then.

@goto-bus-stop I removed Error::new entirely. There is only Error::with_loc left - I wonder if it should become the new Error::new 🤔


Windows windows_android_aot_engine is stuck on collect builds -> get, all subtests passed

https://ci.chromium.org/p/flutter/builders/try/Windows windows_android_aot_engine/1030?
All sub-tests succeeded, the get step has been stuck for 2+ hours.

cc @vashworth

How frequently is this happening?

No idea, saw it once and filed it.

I haven't seen any other failures like this. Setting as P3 and keeping it open for investigation.

I'm struggling to do any sort of additional investigation on this since the build shows no additional error information, @godofredoc Do you have any suggestions for steps that could be taken to learn more about this, or should we wait and see if this was a one-off issue?

Seems to be one-off. Closing for now until we encounter this again.


Add support for validating the schema only once

Hey all, really nice library, thank you! It has saved me tons of time on a project I'm working on.
We have some feedback after adapting it for our use case. We wanted to validate the JSON schema once instead of every time we call jsonschema.validate. Our concern wasn't so much the performance of validating the schema every time, we just wanted to validate the schema before starting our web server.
Here is some source code of how we wrap jsonschema:
import json
import jsonschema
import jsonschema.validators
from .exceptions import SchemaError

class JsonSchema(object):

    def __init__(self, filename):
        self._filename = filename

        with open(self._filename) as f:
            try:
                self._value = json.load(f)
            except ValueError as e:
                raise SchemaError(e.message)

            self._validator = jsonschema.validators.validator_for(
                self._value
            )(self._value)

        # make sure the schema is valid just once now we don't have to validate
        # it every single time how jsonschema.validate does
        try:
            self._validator.check_schema(self._value)
        except jsonschema.SchemaError as e:
            raise SchemaError(e.message)

    @property
    def value(self):
        return self._value

    def valid(self, instance):
        try:
            self._validator.validate(instance, self.value)
            return True

        except jsonschema.ValidationError:
            return False

With this we will have some global schema:
schema = JsonSchema('schema.json') # raises an error if schema is invalid before starting app

web_app.run()

The documentation gave us enough hints to get this done but it did take some digging. I would like to:

Export validator_for in the jsonschema module, so jsonschema.validator_for works. Making it part of the public API.
Add a documentation example of doing this.

If you think this isn't worthwhile feel free to close this issue, no feelings hurt.
Thank you.

Hi! Thanks for the ticket. You're the second person to say that finding the validator API was difficult, so I am definitely open to improvements -- something must be misaligned for people to be having difficulty so happy to hear what could be better of course! On the specific suggestions:

Export validator_for in the jsonschema module, so jsonschema.validator_for works. Making it part of the public API.

Why does this signal to you that things are any more public? Mostly it was an old mistake that validate lives in the global package in the first place, owing back to ancient history when jsonschema was a single module -- these days if I was older or wiser, even validate would not be exposed there, since generally __init__.pys should be empty, but it's left exposed for the old backwards compatibility reasons. But I'd be much happier deprecating using jsonschema.validate as is without importing jsonschema.validators at this point than adding even more things there I think :/
Because of the first time I got this feedback, the docstring for validate itself now says something like "probably if you want to do this more than once, you want Draft7Validator(schema) instead. In your search, did you find and read https://python-jsonschema.readthedocs.io/en/stable/validate/#jsonschema.validate ?
Certainly that page could still use further improvements, but curious to hear.
And yeah definitely appreciate the usability report! Definitely up for further improvements.

Why does this signal to you that things are any more public?

Many libraries use __init__.py to export "key" components of their library so the front end simply involves importing the package name and not every single module that they need. i.e. the things they define as the public facing API. The idea that __init__.py should be empty just isn't backed up practically. I mean, just look at something like numpy's init.py, or requests, or Scrapy (they specifically declare top level shortcuts), or Flask. They import (and thus export) everything that they want to provide easy access to.
Not every library does it. But a lot do.

I don't maintain those projects but I do maintain this one :)
I agree there certainly are others who don't hold the same opinion.

Oh don't get me wrong. I have absolutely no issue with the layout of the project. It's not like the minuscule extra effort of importing jsonschema.validators is an issue in the slightest.
I was just responding to your question about why exports in __init__.py may appear more "public" by presenting some of the most popular Python libraries and the practices they use. I think it comes down a lot to autocomplete within IDEs and the more modern practices of importing module namespaces rather than specific functions:
i.e. import numpy as np; np.some_function(), rather than from numpy import some_function(); some_function().
because then typing np. into your IDE lists all the functions you can access, and smart autocompletes will often present exactly what you'll want as the first option.

But as you said, you maintain this project, so you can do whatever you like! :P As I said, this really isn't a problem. I'm going to use the library regardless, and I'm very happy it exists, and if I find any issues with it during my use I'll contribute back to this project.
I only replied in the first place because I too had wondered about the idea of exposing validator_for in __init__.py when I did pretty much the exact same thing as OP here (wrap jsonschema with a Schema() object) for my project.

Hey @julesjulian, like @Pluckerpluck  mentioned, thinking that adding validator_for to __init__.py makes it part of the API is just an assumption based on experiences with other libraries. I think it is a implicit agreement between some Python programmers. Another reason is the documentation, since everything I read only referenced jsonschema and jsonschema.exceptions, I thought these were the public API. Although I just noticed that one page does mention the jsonschema.validators module so that is my bad.
So here is what the documentation says:

If you know you have a valid schema already, especially if you intend to validate multiple instances with the same schema, you likely would prefer using the IValidator.validate method directly on a specific validator (e.g. Draft7Validator.validate).

The way I interpret this is, if you can assume the schema is valid i.e, it is an invariant that the schema is valid, then you can skip validating the schema and you should especially do this if you are going to validate multiple instances with the same schema.
In my use case, the schema being valid isn't an invariant but, I want to make it so by validating once, during application start up. So I clicked on the IValidator.validate link and get taken to this example:
>>> schema = {"maxItems" : 2}
>>> Draft3Validator(schema).validate([2, 3, 4])
Traceback (most recent call last):
    ...
ValidationError: [2, 3, 4] is too long

And I think: this isn't what I need because I also need to make sure the schema is valid at least once and at this point I just jumped to the source code directly instead of finishing reading the documentation like I should of. Had I done it, I would of found the references to check_schema
Now of course someone else might interpret the documentation another way. I just want to add my thoughts in case this does come up again, you might want to rewrite that paragraph a little bit. Honestly though I think its OK how it is.

I'll let you close this comment since I think its OK.

Cool! @wilbertom thanks for the feedback, definitely useful to hear how you read those!
Will close for now but more than happy to hear feedback from anyone else here as well.


Sound played twice

Hey. First of all thanks for the great work with the module ! I have a problem with a short sound (1sec) I play on repeat:
The loop is played successfully but at every turn of the loop (6 turns of 1 sec each) the sound is played twice (not exactly simultaneously, there is short delay (a few miliseconds) between the 2). Here is the part where I call the player.play() :
`export function playSound(soundId, options = {}) {
if (isBlocked) return;
const player = new Player(soundId);
if (options.repeat) player.looping = true;
if (options.blocking) isBlocked = true;
player.volume = VOL;

player.play();
player.on('ended', () => {
  isBlocked = false;
});

return player;

}`
If I log player.on('looped') with player.on('looped', () => console.log('player looped')); I get 12 events instead of 6.
Thanks in advance for your help

I've noticed this type of thing when I have multiple calls to new Player but don't re-use the player object or destroy the object after use.

Thanks for your feedback. I noticed this too. I am playing a sound on route transition and another when the new route loaded which is supposed to be looped and the sound gets played twice.
I worked around by forcing stop of previous sound before calling new Player again


[FEATURE] Add static code analysis check

Is your feature request related to a problem? Please describe.
For most software security checks it is just best practice and very standard to run static code analysis tools.
Describe the solution you'd like
I want a tool driven, standardized and performant solution to perform static code analysis with a focus on security for the most common programming languages or frameworks starting with, but not limited to:

Java
Go
TypeScript
Python
Ruby

Semgrep is an open source SAST tool which supports the languages you mentioned. There are publicly available rules which can be used, documented here: https://semgrep.dev/r
Custom rules can be written as per use case

Semgrep is an open source SAST tool which supports the languages you mentioned. There are publicly available rules which can be used, documented here: https://semgrep.dev/r Custom rules can be written as per use case

Sounds exactly like the perfect tool for the job an more! 😍

/assign


Tex input typescript

This is the big one! I will write more detailed description of that later.

I removed the three offending files introduced by the incorrect merge with alpha.
Everything else that was introduced during that merge has landed on master by now anyway.

We've discussed most issues already f2f.
I've done all the requested changes: Exceptions are the currentCS property, which is now needed.
However, I am now using the Factory and Options provided by the core utilities.
Just to recall:

I've resolved most conversation that are simple changes and commented on some.
I've left some of the more interesting changes unresolved so you can find them more easily.

PTAL

I think this is fully done now. Do you have any objections to my merging it now?

I think it is a go.    Way to go!

Woo-Hoo!

Unbelievable....
I guess it's time to start PRs for all the extension packages! But I'll do that tomorrow. Off to bed now.


Only track experiments that are set in the config

"will this not lead to loss of leads/views" no, this is not stopping any events tracked, its just prevents the experiment group to be sent to GTM if the experiment is not set in the config

Maybe if the users experiment cookie isn’t a running experiment, randomize to something that’s not running. In this case, only control is set so will always be that?


Deprecated PHP code error message

Below is the error message I got at the top of my JSON file when testing the file...using this URL: http://example.com/wp-update-server/?action=get_metadata&slug=example
Looks like the code in the ~/wp-update-server/includes/extension-meta/markdown.php file need to be updated. I don't know enough PHP how to fix this. Thank you!

Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; Markdown_Parser has a deprecated constructor in /home/[NAME]/public_html/example.com/wp-update-server/includes/extension-meta/markdown.php on line 223

 Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; MarkdownExtra_Parser has a deprecated constructor in /home/[NAME]/public_html/example.com/wp-update-server/includes/extension-meta/markdown.php on line 1696

Thank you for the report. It's odd that this warning is still showing up, I thought I already fixed it a while ago. Could it be that you have an older version of the code? Try downloading the latest release or the master branch.

Thanks for your response! I do have the latest version running. Does it help to diagnose knowing I'm running PHP 7.0.33?
Part of my issue is that I had the whole domain redirected, not excluding the one folder that contains the new plugin version. I fixed that issue in the htaccess file.
Even though I'm still getting this error message, my sites are able to pick up that a new plugin version has been released.

I checked the contents of markdown.php in the latest version and I don't see any classes using deprecated constructors. Can you check your copy of the file? What do the lines that were mentioned in the warnings (line 223 and 1696) actually look like? It's fine if you're not sure how to interpret those parts of the code; just copy 10 - 20 lines from both locations and post them here.

Thank you, Yahnis! from the markdown.php file...
From line 223:
#
# Markdown Parser Class
#

class Markdown_Parser {

	### Configuration Variables ###

	# Change to ">" for HTML output.
	var $empty_element_suffix = MARKDOWN_EMPTY_ELEMENT_SUFFIX;
	var $tab_width = MARKDOWN_TAB_WIDTH;

	# Change to `true` to disallow markup or entities.
	var $no_markup = false;
	var $no_entities = false;

	# Predefined urls and titles for reference links and images.
	var $predef_urls = array();
	var $predef_titles = array();

	### Parser Implementation ###

	# Regex to match balanced [brackets].
	# Needed to insert a maximum bracked depth while converting to PHP.
	var $nested_brackets_depth = 6;
	var $nested_brackets_re;

	var $nested_url_parenthesis_depth = 4;
	var $nested_url_parenthesis_re;

	# Table of hash values for escaped characters:
	var $escape_chars = '\`*_{}[]()>#+-.!';
	var $escape_chars_re;

	function __construct() {
...

From line 1696:
}

#
# Markdown Extra Parser Class
#

class MarkdownExtra_Parser extends Markdown_Parser {

	### Configuration Variables ###

	# Prefix for footnote ids.
	var $fn_id_prefix = "";

	# Optional title attribute for footnote links and backlinks.
	var $fn_link_title = MARKDOWN_FN_LINK_TITLE;
	var $fn_backlink_title = MARKDOWN_FN_BACKLINK_TITLE;

	# Optional class attribute for footnote links and backlinks.
	var $fn_link_class = MARKDOWN_FN_LINK_CLASS;
	var $fn_backlink_class = MARKDOWN_FN_BACKLINK_CLASS;

	# Optional class prefix for fenced code block.
	var $code_class_prefix = MARKDOWN_CODE_CLASS_PREFIX;
	# Class attribute for code blocks goes on the `code` tag;
	# setting this to true will put attributes on the `pre` tag instead.
	var $code_attr_on_pre = MARKDOWN_CODE_ATTR_ON_PRE;

	# Predefined abbreviations.
	var $predef_abbr = array();

	### Parser Implementation ###

	function __construct() {
...

Thank you. That code looks fine to me and it doesn't appear to use deprecated constructors. As you can see, the constructor method is called __construct, so it doesn't actually have the same name as the class. To the best of my knowledge, __construct is the correct constructor name for PHP 7.
I'm not sure why you're getting deprecation notices about method names that are not actually present in the code. Could it be than an older version of this file has been cached somewhere? Could you maybe try clearing the PHP opcode cache somehow?

That could be the issue. I can try contacting my host to see if they can clear the PHP opcode cache. Thank you for your help!


fix(codegen): render default endpoint resolver for machinelearning

Issue #

fix #423
Description of changes

Ensure a default endpoint resolver is still registered for machine learning. The custom resolver for predict now runs after the default resolver to override the endpoint. We don't currently have a way to replace/override middleware per/operation in codegen.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Can you briefly mention testing steps here as I believe we don't have test coverage for this?

I generated the machine learning client and noticed not endpoint resolver was registered in any of the operations except Predict. I regenerated after the change and verified that (1) every operation has an endpoint resolver and (2) Predict has the customized resolver registered after (again also covered by a protocol test)


Make search box use mapzen geocoder by default

duplicated https://github.com/CartoDB/cartodb.js/issues/1194


IstioStatus struct refactoring

Description
This PR introduces changes to IstioStatus struct, from using string to HelperVersion struct, that stores tag as semverVersion and library as string
Changes

Refactor code using version as string
Refactor tests to use HelperVersion
Refactor tag comparison code
Remove "prefix" moving it to HelperVersion as library field

/retest

/test pre-main-reconciler-cli-integration-kyma-latest-k3d

/test pre-main-reconciler-cli-kyma-prev-to-last-release-upgrade-k3d


fix: typo in dataset & data-transform

fix typo in dataset & data-transform docs:

datat set -> data set

Thanks for your contribution!

Thanks for your contribution!


Generate a sequence number

Story
As a developer,
I would like to be able to generate a sequence number easily,
So that I don't need to revert to RDBMS just to generate a unique sequence
Or spend a long time making this work by reading blogs
Discussion

How might laconia.js help this? How might the API look like?

Should a sequence be generated by API Gateway? See this article

DynamoDB can be used to generate sequences. What's everyone thoughts of make this easy for developer to do this?

There was also scaling issue i.e. we need to make sure that sequences can be generated in parallel by supporting multiple rows.

I’m appalled that people still feel the need to do this :-)
My (admittedly limited) view is that it’s very rare that a sequence number is really really needed, it’s just that was how key allocation worked in RDBMSs so got used as a side-effect. Looking at the examples given in the article:

order numbers generally don't need to be sequences, though purchase order numbers are a genuine use case, but this is quite a niche domain
the college registration requirement sounds vague. If you have a genuine need to sort by application order, then use the application date (likely to be a genuine data field in the domain rather than something synthetic)?
a counter is only a sequence under the hood. The abstraction would be something like counter.inc() and would return the new value. This is roughly what the article implements but exposes the sequence number in the response. If having a counter is a frequent requirement for serverless devs then let's implement that cleanly rather than exposing the implementation

Thanks for the input @ljcoomber

I didn't actually have the need for the sequence number, what I needed is a unique number across the application. Sequence implies uniqueness, unique doesn't always imply a sequence.
In our particular use case, it was actually demanded by the customers of our application; things like UUID is too long for their printed materials. We tried various approaches (a lot) to generate a unique number without a data store, until we acknowledged that it's just not possible! We actually adopted to the approach used in that article, but without the API Gateway part (we did this 2 years ago).

Building something that's too niche is undesirable. Would unique number be less niche?
Assuming that generating a unique number is less niche, an abstraction of counter wouldn't fit the use case. Probably uniqueNumber.next()?

I don't know how niche unique number would be, but I like the more specific use case and API proposal.
Could the UUID include chars as well as numbers?

Ah yes, I actually avoided the word UUID because it has a very specific format i.e. 32 hexadecimals.
Great! Renaming the title...


Turn off healtcheck or change time between health checks

The build in healthcheks are spamming Portainer every couple seconds with

2021-10-06 23:55:43
container
Unsupported event

2021-10-06 23:55:43
container
Exec instance started

2021-10-06 23:55:43
container
Exec instance created

There needs to be a command for docker run / docker-compose to either turn off the health checks or change times between each one.

Closing as the upstream bug has been fixed.


Question ⁉

Module works perfectly fine on Miui 12.5.3 android 10 but you know how can I adjust per app volume control? I can't find an app to do it. Media volume it's the same for all apps and I know that the module function only consists on allow multiple audio srouces at the same time but maybe you know an app that can adjust different volume values for each app.
Thanks for your work 😊

its maybe hard, but i can try it in free time!!
and thank you for reaction

its maybe hard, but i can try it in free time!!
and thank you for reaction

Bro I found audiohq magisk module, it gives the binaries and app to adjust volume for each app. With your module and audiohq it's like have sound assistant of miu based on android 11+ but on android 10. The problem it's that audiohq doesn't has a properly enforcing support, by default module changes selinux to permissive because on enforcing volume adjust has latency and can generate bootloop.

its maybe hard, but i can try it in free time!!
and thank you for reaction

Bro I found audiohq magisk module, it gives the binaries and app to adjust volume for each app. With your module and audiohq it's like have sound assistant of miu based on android 11+ but on android 10. The problem it's that audiohq doesn't has a properly enforcing support, by default module changes selinux to permissive because on enforcing volume adjust has latency and can generate bootloop.

https://github.com/Alcatraz323/audiohq_module


highlighten SQL by rouge

cf. https://github.com/esminc/adhoq/pull/56

:cool: thanks!! :sunglasses:


No DocumentQuery Linq to SQL evaluation

As far as I can see there is no equivalent of CreateDocumentQuery that supports a LINQ expression path which is converted to SQL behind the scenes but I can see that the evaluator is still in the code.
Are there plans to support this feature?

According to the 3.0 public preview blog post, the LINQ features are in development.
https://azure.microsoft.com/en-us/blog/azure-cosmos-dotnet-sdk-version-3-0-now-in-public-preview/

Gotcha thanks


Standard VAE and Multinomial VAE notebooks correct typos

Description

Related Issues

Checklist:

[x] I have followed the contribution guidelines and code style for this project.
[ ] I have added tests covering my contributions.
[ ] I have updated the documentation accordingly.
[x] This PR is being made to staging and not master.

@EvgeniaChroni there has been a problem with your PR and it took code from other people. Would you please do a branch from the latest staging, make the changes, and then do a PR to staging again?

@EvgeniaChroni there has been a problem with your PR and it took code from other people. Would you please do a branch from the latest staging, make the changes, and then do a PR to staging again?

Is everything ok now ?

Sorry for the late reply,
Do you still need to do that ?
On Wed, Nov 11, 2020 at 1:42 PM Miguel González-Fierro <
@.***> wrote:

@EvgeniaChroni https://github.com/EvgeniaChroni there has been a
problem with your PR and it took code from other people. Would you please
do a branch from the latest staging, make the changes, and then do a PR to
staging again?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/recommenders/pull/1239#issuecomment-725376096,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFLBHABSWVMQGLSWEJGRWZLSPJ2BLANCNFSM4TRF7QEA
.


More info regarding NvAPI_GPU_SetForcePstate parameters

I had a chat to someone today about what the parameters are for this function.
hPhysicalGpu: ctypes.c_void_p - gpu handle
pstate: int - Desired p-state. Valid values are 0 - 15 where 0 is the highest performance and 15 is idle. Not all cards support all states. By setting it to 16 you're using the fallback state as described below.
int3: int - The fallback state. 1 = fallback to high perf, 2 = fallback to low perf. This allows the driver to control the p-state as needed with the default being high or low performance based on the value passed. Using 2 means that the gpu will attempt to use a low p-state unless higher performance is required, and then it automatically increases as needed.
Hope that's helpful to you.

Thank you very much for this information. Added as docstring to the function.


USB device selector widget

I don't like how merging is blocked for maintainers when changes are requested. I'm not sure where the setting is for this:

#In terms of the UI layout, having the selector in the upper-left makes the window taller. I think it'd be more natural to place the selector to the left of the print icon, but no need to do that in this PR.
I agree that UI is sub optimal. I think we should reshape the entire UI, but it is not in my focus at the moment, and I believe changing anything at the moment will be premature optimization, as things might change soon.
For example, I think label selection (label height, colors) are associated with the labeler. A user might have multiple labelers with different colors. I think the widgets associated with label type selection and labeler selection should be grouped. I am not sure how we should 'memorize' which label is associated with which printer, but I think such association is needed. I guess we should add this to the configuration file at some point.
Not a big deal, but I'm not such a fan of declaring the private interfaces with a leading _. The reason is that the benefit of most conventions is to decrease entropy, but this does the opposite. Now when I'm trying to remember a name or come up with a new name, it's another thing I must think about, and it seems to me like a very subjective decision. Probably you have a clear idea in your head, but it's not entirely clear to me. So it might slightly increase friction for other contributors, and it'll probably be up to you to maintain the private/public distinction. Please don't change anything though, we'll just see how the code evolves.
I agree. I think that at some point we had file with many functions, and it was hard to notice which was internal function and which function intended to be used from outside. While making latest changes, I also felt that I am slowly being trapped by these new convention, with no significant gain. So maybe we should indeed remove this in the near future. I'll keep it as it is now, since I want to merge my changes soon.
As for how to proceed, what do you think of merging or rebasing on https://github.com/labelle-org/labelle/pull/13, turning the CI green, and cutting a new release? It'd be nice to ensure that you can run the release workflow yourself.

I would need the keys for https://pypi.org/project/labelle/.

There are no keys. I set things up with the new OIDC mechanism.
GitHub Actions is trusted by PyPI, and it generates a certificate saying that a package upload request is coming from labelle-org/labelle under the release environment. And PyPI is configured to accept exactly such a certificate:

So if everything is set up correctly, then all you have to do is "Draft a new release":

Choose a new tag name according to semver and set to "Create new tag on publish":

Click "Generate release notes" to get automatic release notes based on the merged PRs, add any additional notes, and hit "Publish release".
That will trigger a pending Actions workflow to upload to PyPI that requires manual approval from a maintainer. Approve, then it will run, and should create a release.

Hmm, _vendor should have been ignored by mypy. The idea is that you should never need to change vendored code except through an explicit patch.

That should fix the mypy errors from _vendor.
Would you be able to revert the changes to font_manager.py? It's supposed to be regeneratable via
pip install vendoring
vendoring sync

(Alternatively, there's vendoring/patches/matplotlib.patch, but currently it consists of only deleting lines.)

Any ideas about how to do device selection from the CLI? It'd be nice to get that sorted out before the next release.

Any ideas about how to do device selection from the CLI? It'd be nice to get that sorted out before the next release.

I'd like to point out that from GUI perspective, the printer must be known before the user starts their design as label printers vary in capabilities obviously. It was a very hard thing to do with existing code, as far as I can remember.
One way to do it in CLI is to have a switch for listing all available printers, and another switch to select one of them for an actual print job.
But for the reason stated above, perhaps we should consider another approach: Persistent printer configuration. One command line switch to set a printer, which will be remembered until reset into something else. This will be more in line with GUI experience and simplify batch job scripts.
Better yet, a CLI switch for selecting a printer while the job is run, and the last used printer is to be treated as the default.

I'd like to point out that from GUI perspective, the printer must be known before the user starts their design as label printers vary in capabilities obviously. It was a very hard thing to do with existing code, as far as I can remember.

Are you sure? The way I see things is that we have an abstract representation, e.g. "barcode, then some particular text, then QR code", and this representation works for any printer. It's just the rendering process from the abstract representation to the bitmap that requires knowledge of the printer.
Perhaps the simplest way would be to use labelle.ini:

If multiple devices are available, check in labelle.ini if a preferred device (ordering?) has been set. (Obviously this setting is not yet implemented.)
If not, then print an error listing the available devices and explaining how to add them to labelle.ini.

Note that this makes it inconvenient to print alternately to multiple devices, since it requires editing a file each time. Perhaps in labele.ini we could define an alias for each device. Then we could use that alias as a CLI parameter.
I could imagine a common use case would be having two or more LabelManager PnP devices, each with a different tape color. So it would be nice if we could distinguish between different devices of the same model. (This should be straightforward using the serial number.)
@systeemkabouter, once we have both a CLI and GUI solution I think that will close https://github.com/computerlyrik/dymoprint/issues/109.

I think the user has to pick the printer first, and tape width / label size, so Labelle knows the dimensions and colors of a canvas.
The preview must be a pixel perfect representation of the printout, so the user won't be disappointed with the print results after spending time on design, and potentially wasting the medium just to know what the end result looks like.
I can't see it working in any other way. We can't just let the user slap anything on the canvas and then send it to Dymo with a 128 point header.
Sure, internally we can work on abstracts and all, but the user ought to see what they will get and nothing else.
I'm against complicating the printer selection logic. I'm considering a few user cases now:

Casual user that has just one label printer,
Semi-automated label printing station, with many printers, operated by external software calling labelle
The first case requires sane defaults. The second case requires consistency across reboots and software updates, and proper error handling.

Here's my proposed algorithm:

If labelle is called with a specified printer, then use it and save it as the default in ini file.
-- throw error instead, if the specified printer cannot be found
If labelle is called without a specified printer, try using the default from ini file:
-- if no default printer is specified, pick the first one of the available printers
-- If the default printer is specified but isn't available, throw error.

This way, the casual user will unknowingly configure their only printer, and the industrial user will not print a batch of labels on a wrong printer by accident.
Moreover, the batch script using labelle will pick the printer only once, and not on each labelle call, this is convenient.
I agree that "Printer identification string", whatever it might be, should be unique enough to differentiate between two printers of the same make and model. A serial number alone could be sufficient if only we knew for sure that all thermal printers have unique S/Ns. Some cheaper USB devices are known to not have unique S/Ns.

@tomers, please see #19 for yet another fix to the mypy settings :see_no_evil:

Any ideas about how to do device selection from the CLI? It'd be nice to get that sorted out before the next release.

I just added a --device flag which should allow exactly this.

Another review round in #20.

For simplicity of code require explicit --text argument for the lab

There are advantages and disadvantages, but this is a pretty major breaking change. Do you think this is really worth it?

For simplicity of code require explicit --text argument for the lab

There are advantages and disadvantages, but this is a pretty major breaking change. Do you think this is really worth it?

Yes, it is definitely worth it. Please consider my additional commits. I've overhauled the CLI, and these changes were part of this effort.

Yes, it is definitely worth it. Please consider my additional commits. I've overhauled the CLI, and these changes were part of this effort.

I still don't understand. Change typer.Option to typer.Argument in text and it's no longer a breaking change.
Amazing work with Typer!!! :star_struck:

This PR is pretty crazy. Before it made a lot more sense when you were refactoring everything, but I don't think it makes sense to have these two completely different features (USB device selection and Typer) in the same PR.
Let's keep it for now, but not make this a habit.

I still don't understand. Change typer.Option to typer.Argument in text and it's no longer a breaking change.

Who said text label is a must? What makes text any more important than, say, a QR code? I wanted to reflect that in the API, that text is just something that we add, with no assumptions that this is what most people do with labels.

I totally agree in principle, but this is still a breaking change, and I don't see any necessity.
Think of it from the user perspective. We're asking people to switch from dymoprint to Labelle, and then they try it out and it doesn't work in the same way. The interface has been like this for the entire lifetime of the dymo project. People would need to adapt their habits, and also they may have built scripts that they now have to adjust.
I don't think it's that huge of a deal, and I agree that we should switch eventually, but the benefit of this seems the benefit over the disruption of introducing such a breaking change over the previous long-standing interface of many years shortly after a new release.
This is also a reason I dislike these long PRs. This discussion is holding all your previous work hostage.
How about this: let's convert it to Argument for now so that we can get this merged and released as v1.2.0. Then we create a 1-line PR to convert it back to Option that we save for when we decide to make a 2.0 release.

ok, I agree with what you said.
Actually, the mandatory text argument stood in my way many times with argparse, thus I wanted to remove it so badly.
Now with typer and the support for commands, it is no longer necessary, and I can live with keeping the API for BC.
I wanted to keep all my progress in a single PR, in order to save me from juggling between branchs, but I agree that I went too far with that :-) sorry

@tomers, feel free to give the release process a try for v1.2.0. I hope it is extremely easy. If not, please let me know.

Sure, @maresb. I am going for a 2 days vacation, so I would only be able to do it afterwards. If you want, and don't want to wait, you can release yourself, and I'll do the next release.

Ok, sure, I'll take care of it then. Enjoy your vacation!!! :beach_umbrella:


[SPARK-50055][SQL] Add TryMakeInterval alternative

What changes were proposed in this pull request?
Addition of two new expression try_make_interval.
Why are the changes needed?
This is a split PR from https://github.com/apache/spark/pull/48499 so that we divide the reasonings for PRs.
Does this PR introduce any user-facing change?
Yes, new expressions added.
How was this patch tested?
Tests added.
Was this patch authored or co-authored using generative AI tooling?
No.

@MaxGekk @HyukjinKwon Do we want to not support try_make_interval in pyspark? This PR seems to block it https://github.com/apache/spark/pull/46975. I believe we should update that make_interval is not supported as well, as CalendarIntervalType is not supported.

Should I just then remove it from python API? As we cannot really call it there.

hm, we can call them, no? It's just that we don't support df.collect() on CalendarIntervalType instances.

e.g., you can call df.select(make_interval(...)).show()

Aha, ok, so I should only change the test to use some other type of collection of data that is not collect() and then verify the results.

Yeah, i think so.

Ready for merge now @MaxGekk

+1, LGTM. Merging to master.
Thank you, @mihailom-db and @HyukjinKwon for review.


[System Tests]: Merge the system tests into master

This PR merges the feature/system-integration-tests feature branch into master.

LGTM! 💯  💖

Great Job! ⚒ 💯


[turborepo] HMR lost if you import shared ui package inside _app and index files

What version of Turborepo are you using?
1.9.3
What package manager are you using / does the bug impact?
Yarn v1
What operating system are you using?
Mac
Describe the Bug
HMR is not working as expected and performs full refresh of app and it looses it's state if you modify file in package that is both imported in:
_app.tsx
index.tsx

I've started to encounter this bug in some of my shared Layouts that I had and thought maybe I have some cyclic dependencies but I could also reproduce it on sample repo.
Expected Behavior
It should not perform full refresh and keep it's state.
To Reproduce

Open Console
Go to Button.tsx in ui package, modify eg. Button Text
App will perform full-refresh loosing it's state

Reproduction Repo
https://github.com/clumsier/turborepo-hmr-bug

Hi! Thanks for taking the time to open an issue here. I don't believe this is an issue with turborepo or turbopack since running the next in dev mode directly via yarn causes the same issue, and you have not opted-in to using turbopack. @vercel/web-tooling could anyone weigh in on this example and confirm that that is the case?

Hi, @pacxiu, I think you are best off opening this repro with https://github.com/vercel/next.js, since I don't believe this is a turbo-specific issue. I am closing this for now, thanks!


fix for bug #454, adds _isHTML condition at HTMLServer.js:151

This change adds a conditional wrapper at line 151 - 170 before server(content)

Hi @NYCJacob, would you be able to rebase your patch onto the latest commit on the master branch?

will do

ok I synced my fork with your master and did another push.  Is that good?

@NYCJacob you would need to close this pull request and open a new one. In the new one, make sure the base fork's branch is master and not bramble.


How can i provide the Datadog API Key via Environment Variable?

Hey,
i want to provide the Datadog API Key via environment variable since this is a secret. I tried numerous things now but neither seem to work. Any hints?
export QUARKUS_MICROMETER_EXPORT_DATADOG_API_KEY=122344557438294
export QUARKUS_MICROMETER_EXPORT_DATADOG_APIKEY=122344557438294
export QUARKUS_MICROMETER_EXPORT_DATADOG="API_KEY=122344557438294"
export MICROMETER_EXPORT_DATADOG_API_KEY=122344557438294
export MICROMETER_EXPORT_DATADOG_APIKEY=122344557438294

Hi @timmhirsens.
This property shouldn't have bee set as camel case... Please try:
QUARKUS_MICROMETER_EXPORT_DATADOG_API-KEY

Hey @brunobat
Thanks for the swift reply. I don’t think environment variables can have hyphens/dashes, though? At least not without workarounds

You are right... I'm confusing it with the system property convention.

In case someone does have the same issue as me, i worked around this by defining
quarkus.micrometer.export.datadog.api-key=${datadog.apikey}

in the application.properties and then setting
DATADOG_APIKEY=<theapikey>

in the runtime environment.


test fail with force shadowdom

 Issue by sigmundch
Originally opened as dart-lang/sdk#19414

we seem to be hitting an issue when forcing the shadow-dom polyfill. The following code:
 JsObject _polymerElementProto = () {
   var polyElem = document.createElement('polymer-element');
   var proto = new JsObject.fromBrowserObject(polyElem)['proto'];
   if (proto is Node) proto = new JsObject.fromBrowserObject(proto);
   return proto;
 }();
supposedly retrieves the proto of 'polymer-element', but later doing: proto['register'] fails to find the register method.
It seems to be that the following works ok:
   jsPolymerElement = new JsObject.fromBrowserObject(document)
       .callMethod('createElement', ['polymer-element']);
   var proto = jsPolymerElement['proto'];
   if (proto is Node) proto = new JsObject.fromBrowserObject(proto);
   print(proto['register']);
but this doesn't work for our call to 'init' that we do in registerSync.
Marking todomvc/markdone_shadow_test as failing for now.

 Comment by sigmundch

Removed Polymer-P-2 label.
Added Polymer-Milestone-Later label.

 Comment by sigmundch

Added this to the Later milestone.
Added Area-Pkg label.

 Comment by sigmundch

Removed this from the Later milestone.

 Comment by sigmundch

Added Polymer-P-2 label.

 Comment by sigmundch

Removed Priority-Medium label.
Added Priority-Low label.

 Comment by sigmundch

Removed Polymer-Milestone-Later label.
Added PolymerMilestone-Later label.

this test no longer exists


Insecure content in module setup (should use HTTPS)

When opening the Add-on Modules page in the Foundry VTT setup page, MountUp attempts to pull in the example video and gives the following warning. It would be good if this can be updated to point at your HTTPS domain.
Mixed Content: The page at 'https://example.com/setup' was loaded over HTTPS, but requested an insecure video 'http://brunhine.com/assets/img/mountup/mount-example.webm'. This content should also be served over HTTPS.

I can't see where this is set in your repository, so I'm guessing it's inside foundry repo where the list of add-on modules is stored.

Shouldn't be listed as a bug sorry. I can't change the label though.


less wrong part2: Pitfalls of Human Cognition

https://www.lesswrong.com/s/gFvira6tHpLXnqCLH

https://github.com/mefengl/what-i-read/commit/ea48a281a2c7bea6b0a9b65427bc126ea3828aaf


WIP: Move replay up to a top-level package

In this PR, replay would still be distributed with dataportal with their shared setup.py, but replay would be replay, not dataportal.replay. This makes it possible to import dataportal even if there are problems dealing with the fact that enaml must always be imported before matplotlib.
(Said problems have been resolved so far, but it will probably come up again. Yesterday, we saw how easy it is for users to sneakily import matplotlib somewhere where it takes us an hour to find it.)

Note to selves: run_tests.py must also be updated to include replay before merging.

I'm fairly certain that it does...  Doesn't replay still pop up when you
execute python run_tests.py?
On Mon, Apr 13, 2015, 5:34 PM Dan Allan<EMAIL_ADDRESS>wrote:

Note to selves: run_tests.py must also be updated to include replay
before merging.
—
Reply to this email directly or view it on GitHub
https://github.com/NSLS-II/dataportal/pull/157#issuecomment-92507761.

Nose is fine, but coverage isn't picking up replay.

I think adding source=replay to the run section of .coveragerc will fix that

@ericdill It looks like some imports are still broken here. Can you bail me out?

Closed as #164 is merged.


Is RTX 3060 supported?

Sorry have to ask, as I didn't see any compatibility list.
Is GeForce RTX 3060 (normal GA106-300   or   LHR GA106-302) supported?
how about other card in RTX 30xx series, do they support?
thank you.

https://github.com/DualCoder/vgpu_unlock/issues/8

I tried the latest version of the driver, it can run rtx 2060 normally https://gitlab.com/polloloco/vgpu-proxmox
But it shows error 43 in the guest

When I try to simulate the way to rtx 6000, the guest blue screen.
nano /etc/vgpu_unlock/profile_override.toml
[profile.nvidia-523]
pci_device_id = 0x1E30
pci_id = 0x1E3012BA
num_displays = 1
display_width = 1920
display_height = 1080
max_pixels = 2073600
cuda_enabled = 1
frl_enabled = 1
framebuffer = 0xEC000000

GIGABYTE GeForce RTX 3060 GAMING OC 12G 2.0 not work. Device not work in Windows 10.
Guest Driver: 512.78_grid_win10_win11_server2016_server2019_server2022_64bit_international.exe

same thing. I got rtx 3060 on a host machine working and mdevctl types outputs the right info
but I get code 43 in windows 11 or "insufficient resources whatever to perform api call*. Tried various methods such as disabling secure boot, trying to spoof gpu using different ids

same problems here

Curious


ipad mini layout issues

Wallet create page, elements are not centered on the page, fonts can be scaled larger.
Seed Restore page, font size can be scaled larger.
Pin page, should be centered and scaled larger, similar to the ipod unlock screen.
Welcome dialog, font should be scaled larger, text needs to be left justified.
Wifi dialog, scale larger.
Overview synchronizing, scale all text larger. Make progress bar thicker.
Nav bar, scale up to use unused space. Narrow the nav bar width to reduce wasted space.
Overview and Transaction list. iPads have a lot more screen space for the vertical number of transactions to show, as well as unused center space on the horizontal rows. We can display the date as its own column rather then having it with the confirmed status. We can make the rows slightly taller and increase the font size throughout.
Nav bar button on top left, should be larger.
Send page, increase font sizes for readability. Address font should be large enough to take up the available space on the screen. From drop down is extending to 100% width when it should only extend to the width needed for the account text. Qrcode button can likely be bigger. Tap to paste button is not correctly sized relative to the font size within it.
Receive page, Account drop down is extending to 100% width when it should only extend to the width needed for the account text. Address copied dialog box font is too small.
Security page, input rows appear to be floating above the underlines. Increase font sizes. Address area should show the full address with no empty space.
Accounts page, increase font size and row height.
Help page, increase font size.
Settings page, Save button on the top is not obvious. Need to be better designed, or removed like on android.
tx details page, full hash is not showing, instead it shows ... in the middle. This is not needed because there is plenty of room on this page to show the full hash.

no longer relevant, issue was created for an old UI design
New Ipad layout would be revisited here #822


stage1: copy /etc/resolv.conf instead of mounting it

Some applications require or expect to be able to modify /etc/resolv.conf.
This is however not currently possible as the file is bind-mounted.
Could it be possible to instead inject it by copying it?
#2044
#2430

Just to better understand the use-case, where did you encounter this and what was the expected behavior?
The code you pinpointed is preparing the app chroot, and it doesn't seem to mark it as read-only. Could it be just a user-permission issue?
If we switch this to copying, different apps in the pod may end up with different sets of resolvers; is this what you are trying to achieve?

Hi,
I read the pod manifest and it appears that /etc/resolv.conf is mounted read-only by kubelet from the host (source) as a workaround to #2430 when --net=host is used.
Forbidding users to override their /etc/resolv.conf is a limitation. It currently blocks our progress on Stackanetes.
What do you think would be the best way to fix this?
@yifan-gu

Can you explain how exactly it blocks progress on Stackanetes? What is the
application you're having trouble with and what are its requirements?
On 2 July 2016 at 10:39, Quentin Machu<EMAIL_ADDRESS>wrote:

Hi,
I read the pod manifest and it appears that /etc/resolv.conf is mounted
read-only by kubelet from the host (source
https://github.com/kubernetes/kubernetes/blob/f2ddd60eb9e7e9e29f7a105a9a8fa020042e8e52/pkg/kubelet/rkt/rkt.go#L653)
as a workaround to #2430 https://github.com/coreos/rkt/issues/2430 when
--net=host is used.
Forbidding users to override their /etc/resolv.conf is a limitation. It
currently blocks our progress on Stackanetes.
What do you think would be the best way to fix this?
@yifan-gu https://github.com/yifan-gu
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/coreos/rkt/issues/2861#issuecomment-230091125, or mute
the thread
https://github.com/notifications/unsubscribe/ACewN-0nvbfgiOaNf5qTx-IirtIaI44Aks5qRiOwgaJpZM4JCzo1
.

Hi,
Our containers requires to resolv kubernetes services using the cluster DNS. Currently, most of these containers use --net=host, some don't - it may change eventually. At startup, a script rewrites their /etc/resolv.conf to make them use the cluster DNS, cluster search domains and ndots option, regardless of the host/network configuration.
With the default runtime, it causes no particular issue. With rkt and --net=host, however, it isn't possible, because /etc/resolv.conf is mounted read-only from the host. It means that we would have to modify the infrastructure itself to have an appropriate /etc/resolv.conf, and drop the rewrite entirely.
Now, what if our infrastructure uses systemd.resolved / systemd.networkd? While they both support specifying extra DNS servers and search domains, neither of them allow configuring DNS options (i.e. ndots) as of v230.
I'd personally prefer to opt for the solution that involve having a proper infrastructure configuration and which doesn't not involve overwriting the file inside the containers but it seems that both solutions have pros/cons.

I did some quick investigation. /etc/resolv.conf is not being copied due to --net=host. Instead, /etc/rkt-resolv.conf being created in the stage1's rootfs because you are invoking rkt run --dns.... That file is then bind-mounted on to /etc/resolv.conf in the app's rootfs.
If you don't pass --dns to rkt run, then you are free to treat /etc/resolv.conf as any other pod / application volume.

Relevant:

kubelet/generateRunCommand
kubelet/makeHostNetworkMount

Hi,
Fixed by https://github.com/kubernetes/kubernetes/pull/29024.


[Security] Admin account should not be able to see other users password via curl requests

Reporting this here publicly as there is no security policy.
The /api/accounts endpoint reveals password for all other users when used from any admin account
POC below:
curl 'https://yourdomain/api/accounts' \
  -H 'authority: yourdomain' \
  -H 'accept: application/json' \
  -H 'accept-language: en-US,en;q=0.9,it;q=0.8' \
  -H 'authorization: yourbearertoken' \
  -H 'cache-control: max-age=0' \
  -H 'content-type: application/json' \
  -H 'cookie: kw_1pc_enableds=true' \
  -H 'if-none-match: W/"censor"' \
  -H 'referer: https://yourdomain/settings/accounts' \
  -H 'sec-ch-ua: " Not A;Brand";v="99", "Chromium";v="101"' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'sec-ch-ua-platform: "Linux"' \
  -H 'sec-fetch-dest: empty' \
  -H 'sec-fetch-mode: cors' \
  -H 'sec-fetch-site: same-origin' \
  -H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.64 Safari/537.36' \
  --compressed

[
    {
        "user_id": 2,
        "username": "ciao",
        "password": "censored",
        "is_admin": true,
        "created_at": "censored",
        "updated_at": "censored"
    },
    {
        "user_id": 1,
        "username": "pera",
        "password": "censored",
        "is_admin": true,
        "created_at": "censored",
        "updated_at": "censored"
    },
    {
        "user_id": 3,
        "username": "aaaa",
        "password": "$2a$10$HeDE07TEW3LLqDOBMx9vN.wfLRTNgdxiFE9eqBO4Lkp2uxTWMmYLG", (note, this is intentionally NOT censored)
        "is_admin": false,
        "created_at": "censored",
        "updated_at": "censored"
    }
]

The password is a bcrypt hash, so having it doesn't actually reveal what the original password is. Also, the admin should have access to everything, they are the admin.

The admin can already delete accounts, so that is more destructive than seeing a hashed password. But I suppose excluding the password in the result wouldn't hurt.


Translations for sync promos and getting on other platforms from sync flow

Task/Issue URL: https://app.asana.com/0/608920331025315/1208185599849132/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

#4961  👈
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @CDRussell and the rest of your teammates on  Graphite


Kerio Connect security.log

Requested parser and scenario in #437 and finally had the time to do it myself.

The timings may need some tuning due to kerio antispam measures already in place.

Hi @ToeiRei,
Did you had some time to finish the tuning ?
Also, this parser and scenario needs some tests. You can use cscli hubtest to generate new tests suite.

Sorry for the late reply. I'll do the hubtest as soon as I'm back home

I found a few issues with the blocks from kerio which I find disturbing.... their log entries are based on their detection

Converting to draft to proceed please upload some tests

Hi @ToeiRei
are you still working on this?
If yes, can I help? I'm quite interested to get this working as well.

I had the project on hold as the blocklist mirror wasn't too helpful. Hit me up on discord and we'll get the show on the road again


Changing name from astropile to mmu

Changing name as discussed from astropile to mmu.

It looks very reasonable to me, but impossible to tell if nothing breaks ^^

Ok, I found one issue in the demo notebook, fixing it

Ok, I've pushed revised notebook


Hitting ESC does not ask to save changes.

After selecting apps to download. Hitting Esc closes the program and asks if you want to Pre-Fill. It does not ask to save the changes to the list.

Released in v1.7.0 https://github.com/tpill90/steam-lancache-prefill/releases/tag/v1.7.0


GCP doc on deployment UI should describe new basic auth rather than "skip IAP"

https://www.kubeflow.org/docs/gke/deploy/deploy-ui/
The "skip IAP" option has been replaced by 3 options:

Log in with IAP
Log in with username / password
Set up endpoint later

/assign

At the same time, fix up the CLI and UI deployment guides so they give more of a clue about where the user made the choice between IAP and basic auth.

Also fix up the guide to monitoring IAP:
http://localhost:1313/docs/gke/deploy/monitor-iap-setup/

Note that the above PR does NOT attempt to address this issue. It just references the issue.

I've branched off the additional tasks in comments to another issue (see the above referenced issue). This current issue covers the updates to the deployment UI guide for auth options and storage options only.
@jay-saldanha is working on this issue.


New social media cards SEO/OG v2

I think it's much better than the current one from the previous stuff, so I guess this one is not perfect, but we will follow up with @exezbcz on it later for a much better v2 for neobrutalism
We will look on it once we will finish collection view 😏
Not urgent tho
Originally posted by @yangwao in https://github.com/kodadot/nft-gallery/issues/4384#issuecomment-1325183178

#5426


the netlist supported in GUI and SpiceSharpParser

I have edited a netlist in SpiceSharpGUI and it runs successfully. Then I want to use SpiceSharpParser to parse the netlist. However, I get several errors when I copy my netlist to the SpiceSharpParser. So is the netlist supported in SpiceSharpGUI is different from the one in SpiceSharpParser?
Thank you for your help in advance!

I have edited a netlist in SpiceSharpGUI and it runs successfully.  Then I want to use SpiceSharpParser to  parse the netlist. However, I get several errors when I copy my netlist to the SpiceSharpParser.  So is the netlist supported in SpiceSharpGUI is different from the one in SpiceSharpParser?
Thank you for your help in advance!

Thank you for your message. I would like to help you.
I will update ShareSharpGUI today to use latest packges from SpiceSharp project.
In theory a netlist should work the same in GUI and in raw parser.
The differences probably are caused by the fact that GUI project was not updated for long time.

Thank you for your message. I would like to help you.
I will update ShareSharpGUI today to use latest packges from SpiceSharp project. In theory a netlist should work the same in GUI and in raw parser. The differences probably are caused by the fact that GUI project was not updated for long time.

Oh,  This will be of great help to me.  Thanks a lot!

SpiceSharpGUI project has been refreshed.
Also I've published new version SpiceSharpParser that has one fix.
I hope it will solve your problem. Please let me know.

Hi, I've tried the new version and I find that some bugs I met when I edited in GUI have been fixed indeed.  But it still has some exceptions when I run the SpiceSharpParser in Visual Studio.  I would like to offer some details for you.
I move the netlist which runs successfully in GUI to the SpiceSharpParser(version 3.1.5),  I compiled it successfully with no error.  Then, I run the programe and meet an exception. It is in the part "//Translating netlist model to SpiceSharp".  This line,  "var spiceSharpModel = reader.Read(netlist);" , has an exception  as follows.
SpiceSharp. SpiceSharpException: "Unhandled exception during reading model"
ArgumentNullException: The value cannot be null.
Arg_ParamName_Name
This exception was originally raised in this call stack:
[external code]
Does this mean that the netlist I edited in the GUI has some errors?  But it does get correct image results in the GUI.

There is a typo in Netlist_InParser.txt file.

If you have problems with the projects, please ask and I would be happy to help.

 When I corrected it and ran it again, I found another exception: "InvalidOperationException: sequence  contains no elements". Fortuanately, I found that it was caused by copying the simulation part of Spice#Parser  without involving analysis statements such as ".DC",  ".AC",  ".TRAN"  in the text of netlist. After adding this statement together with another statement ".SAVE", the program ran successfully.
I considered that the program could run as long as the circuit was built successfully, ignoring the fact that the simulation part of the Spice#Parser required analysis statements.  I am not sure I've found the key, for I've been exposed to Spice and Spice# for less than a week.  I really appreciate your help.

How can I help?

Oh, I'm terribly sorry for not responding to you in a timely manner, as I have just finished all of my exams during the two months. I have already completed a project based on Spice#. In the future, I will teach my students to learn how to build an AC motor circuit using Spice#. To prevent them from copying the circuit netlist I submitted a few months ago, I deleted the netlist file I submitted. In addition, I accidentally clicked the 'close with comment’ button because I am not very familiar with the github interface. I only made these changes. Currently, I haven't encountered any new problems. Thank you very much for your help a few months ago!


Use bignum package for BigInteger

From @izaera on January 3, 2014 8:6
Currently I'm used a modified version internally added to cipher of that library. The patches I've made should be transferred to bignum and cipher should rely on that lib.
Copied from original issue: izaera/cipher#34

From @izaera on January 15, 2014 13:25
fixed in commit 540e64186c20a1e24ee79e0b5cc7e8b0302dab72