"dsa_builtin_paramgen2" support in 1.1.1

I've built 2 versions of OpenSSL: 1.0.2p (with fips-2.0.16) and openssl 1.1.1.
I'm trying to test DSA PQG Verification with both versions of OpenSSL.
I see the dsa_builtin_paramgen2() function in libcrypto.so.1.0.0 (version 1.0.2p) but not in libcrypto.so.1.1 (version 1.1.1). Is there no support for it in newer OpenSSL version?
I do see the implementation in dsa_gen.c but nothing in the library generated.
Below is the output from both versions of libcrypto:
amritha@thorath-vm:~/ultima_latest$ nm -D /home/amritha/ssl/lib/libcrypto.so.1.0.0 | grep dsa_builtin_paramgen2
000000000019ba34 T dsa_builtin_paramgen2
00000000000971f0 T fips_dsa_builtin_paramgen2

amritha@thorath-vm:~/ultima_latest$ nm -D /home/amritha/new_openssl/ssl/lib/libcrypto.so.1.1 | grep dsa_builtin_paramgen2
amritha@thorath-vm:~/ultima_latest$

I would expect to see atleast 1 entry with new openSSL.

dsa_builtin_paramgen2() was never intended to be a public symbol,
it's not in any of the public headers.

How can I achieve the functionality that's perfomed by dsa_builtin_paramgen2() if I cannot access it? Is there an alternative?

You will need to explain what you're trying to do. You're using it
to generate g again, having passed in p and q, and then check that
it's the same g you already had?
I think it should be possible to do that with the EVP_PKEY_keygen. I
think you need to call EVP_PKEY_CTX_set_dh_paramgen_type() with 2.

I'm trying to do the following (CAVP testing)
[A.1.1.2 Generation of the Probable Primes p and q Using an Approved Hash Function]

[A.2.1   Unverifiable Generation of the Generator g]

[A.2.3   Verifiable Canonical Generation of the Generator g]

[A.1.1.3 Validation of the Probable Primes p and q that were Generated Using an Approved Hash Function]

[A.2.2   Assurance of the Validity of the Generator g]

[A.2.4   Validation Routine when the Canonical Generation of the Generator g Routine Was Used]

Ref: look at DSA vectors (PQG Gen and Ver) provided here.

I'm having the same problem, trying to do CAVP testing.  Have you had any luck figuring it out?

This doesn't seem relevant with the provider model and the necessity of implementing CAVS tests there.


What happens to the cards swiped off the screen.

Is there a way to reset the adapter position to the initial state? And how to add an item to top card rather than adding it to the end of the list?

+1 I tried to reset adapter but it doesn't work (index is from cardSwipedRight or cardSwipedLeft):
                    if (index == 1) {
                        Log.i("LIST_SWIPE", "reloading...");
                        adapter = new SwipeDeckAdapter(threads.data, getContext());
                        cardStack.setAdapter(adapter);
                    }

Update: to reset adapter position, just call cardStack.setAdapterIndex(0);
Not sure about inserting card to desired position, which might introduce UE confusion IMO.


[es-dev-server] File extension plugin error

I am facing the issue with<EMAIL_ADDRESS>When trying to run the server, which is created programmatically, I get the following error:
TypeError: Cannot read property 'some' of undefined
      at Object.resolveMimeType (/node_modules/es-dev-server/dist/plugins/fileExtensionsPlugin.js:13:32)
      at pluginMimeTypeMiddleware (/node_modules/es-dev-server/dist/middleware/plugin-mime-type.js:19:103)
      at async responseTransformMiddlewareConfig (/node_modules/es-dev-server/dist/middleware/response-transform.js:6:9)
      at async pluginTransformMiddleware (/node_modules/es-dev-server/dist/middleware/plugin-transform.js:15:9)
      at async watchServedFilesMiddleware (/node_modules/es-dev-server/dist/middleware/watch-served-files.js:17:9)
      at async responseBodyCacheMiddleware (/node_modules/es-dev-server/dist/middleware/response-body-cache.js:70:9)
      at async etagCacheMiddleware (/node_modules/es-dev-server/dist/middleware/etag-cache.js:8:9)
      at async /node_modules/es-dev-server/dist/create-middlewares.js:86:9
      at async /node_modules/koa-compress/index.js:43:5

A quick investigation shows that serverStart function is never run from fileExtensionsPlugin, so fileExtensions variable is undefined.

Ah, this hook is called only when you use startServer programmatically. I'll fix this.


Error when launching a simulation in container

I get this stack trace when launching a simulation using the demo script in plug.
'File case_storage.mat not found in /mnt/bes/pcm/tmp/scenario_1',
  'Demand flexibility profiles not found in /mnt/bes/pcm/tmp/scenario_1',
  'Julia exception: UndefKeywordError: keyword argument duration not assigned',
  'Stacktrace:',
  '[1] read_demand_flexibility(::String) at /app/src/read.jl:178',
  '[2] run_scenario(; num_segments::Int64, interval::Int64, n_interval::Int64, start_index::Int64, inputfolder::String, outputfolder::String, threads::Nothing, optimizer_factory::Type{T} where T, solver_kwargs::Nothing) at /app/src/REISE.jl:64',

Oops. This probably came from https://github.com/Breakthrough-Energy/REISE.jl/pull/118.

Whoops, I'm working to address this right now.

It's here: https://github.com/Breakthrough-Energy/REISE.jl/blob/f192da66d87c61d7e2c1fd9c1d8af5a3886873e7/src/read.jl#L105 Another csv is needed as inputs based on the latest PR @danielolsen mentioned above. PowerSimData hasn't been updated to support the latest demand flexibility feature yet as discussed with @lanesmith before the above PR is merged.

It's here:
https://github.com/Breakthrough-Energy/REISE.jl/blob/f192da66d87c61d7e2c1fd9c1d8af5a3886873e7/src/read.jl#L105
Another csv is needed as inputs based on the latest PR @danielolsen mentioned above. PowerSimData hasn't been updated to support the latest demand flexibility feature yet as discussed with @lanesmith before the above PR is merged.

There is a problem on the REISE.jl side. If a file is not provided, not all of the parameters in the DemandFlexibility are assigned. I thought that not all parameters need to be assigned, but I was wrong. There may still be problems on the PowerSimData side, but the error that @jon-hagg posted above matches with the REISE.jl error I just found. I'm making the REISE.jl fix right now and should be able to get a PR submitted soon.


feat(Tooltip): Attach to Target Element

Feature Description
Current Tooltip isn't compliant with WCAG - 1.3.2 Meaningful order (Level A), because it's attached to <body> bottom and positioned absolutely. There should be an option to attach it closer to the target element.
Use Case
Component would meet a11y requirements.

The component doesn't need to be in the same DOM hierarchy, because it's a description, not actual content. Furthermore, it is actually hidden from screen readers, we read out the message using aria-describedby.


Add License section to README

Requirement by CELA that all ADS extensions must have a license section in their README with a link to the applicable license.

Oops, didn't realize there was a separate folder for the ADS extension. Closing and will make new one targeting the correct README.

ok, thanks!

BTW it's here: https://github.com/microsoft/SandDance/blob/main/extensions/azdata-sanddance/README.md

Yup, opened up another PR here : https://github.com/microsoft/SandDance/pull/654


c.kv.put('a//b', '1') results in an empty key a/b

This is due to kennethreitz/requests#2590 : with Requests v2.x, when PUT /v1/kv/a//b is redirected to PUT /v1/kv/a/b, the content data is dropped (and Consul cannot distinguish it from a genuine empty content, returning 200.)
We can either wait for Requests v3.0 to be released or use os.path.normpath() to rewrite an offending key on our side. I'm not 100% sure if it's valid to rewrite a//b to a/b when we think about an abstract notion of a "key" but the current implementation of Consul handles a key as something like a path (as opposed to what's merely passed around as a path) so it's okay at least for now.
a/./b and a/../b suffer from the same issue.

Hi!
Sorry for the delay in responding to this. You're right, this is an issue.
It's kinda overkill for python-consul to rely on requests. It could just use python's built in HTTP client. There would just need to be a little juggling to make it work for python 2.6 -> python 3.6.
Would you like to take a stab at creating a pull request?


Condtionally build denormalized table for constructing core__encounter

This table performs a join from three optional fields, which has some level of risk if the data is not present from a specific EHR. We should build a table we can use that will select data from these fields only if it is present.

Adressing via #81


Upgraded to work with latest SDKs and release with jitpack.io

Waiting this MR, thanks for support new sdk and jitpack


Bridge.Console improvements

The Bridge.Console utility needs some improvements. Ideas are being collected here.

[x] Make optional by removing bridge.console.js <script> from .html
[x] Capture JavaScript errors
[x] Render JavaScript Exception messages (Deck)
[x] Better rendering of custom [object] objects (#2556)

See Also

#2556

I added a comment in #1993 that maybe more relevant here:

It seems a little strange to me to ship all the console code inside bridge.json and have another package to disable it. A switch to toggle is better, but it does feel a bit bloated to include a dev feature in all production builds that you might not want. Wouldn't it be better to have it in a separate package that you pull in if you want it, but otherwise it's not there?

@geoffreymcgill Do you still plan to let us opt-out of this console? It's rather annoying to have this weird in-page console pop up when I have the browser console open (and can do more in there).

Yes, we will try to add some settings to disable Bridge Console in Bridge 16.0.
How about using the following to write to the browser console directly if you want to completely avoid Bridge Console?
http://deck.net/bb9e377ca599b32827d9cbf0954f3c34
//@ console.log(msg);

Thanks! I've been using @ProductiveRage's workaround for now (so I can still use the C# Console methods), it'd just be nice to have a cleaner (and supported) way :-)

A pull request has been submitted with Bridge.Console improvements. Once testing is finished, the PR will be merged into the master branch and will be included with the next Bridge release.
The new functionality can be tested at https://dev.deck.net.
Bridge.Console has been separated into a dedicated bridge.console.js file and is now completely optional by adding or removing the .js file from the .html.
<!DOCTYPE html>

<html lang="en" xmlns="http://www.w3.org/1999/xhtml">
<head>
    <meta charset="utf-8" />
    <title>Bridge ClassLibrary28</title>
    <script src="bin/Debug/bridge/bridge.min.js"></script>

    <!--
            Q: Don't want Bridge.Console?

            A: Remove bridge.console.js from this file
    -->
    <script src="bin/Debug/bridge/bridge.console.min.js"></script>

    <script src="bin/Debug/bridge/demo.js"></script>
</head>
<body>
    <!--
        Right-Click on this file and select "View in Browser"
    -->
</body>
</html>

Hope this helps.

Great! Is this still separate/removable even if you use combineScripts?

The bridge.console.js is automatically emitted to the output folder and will be combined if "combineScript": true.
For better control over combining the .js files, please use resources config.
With the resources config, you can explicitly exclude files from being emitted to the output folder. Please see the following sample for excluding bridge.console.js:
{
  "resources": [
    {
      "name": "bridge.console.js",
      "extract": false
    }
  ]
}

Hope this helps.

Great, thanks!


Maybe fix for PUT deprecation (translate PUT to POST)

This change treats received PUT requests as POST inside gRPC.

@yashykt

Actually, I'm pretty sure this won't work for RBAC.  If there's a rule that requires POST, this would make PUT look like POST to the RBAC rules, so we'd wind up allowing the request when we shouldn't.

Actually, I'm pretty sure this won't work for RBAC. If there's a rule that requires POST, this would make PUT look like POST to the RBAC rules, so we'd wind up allowing the request when we shouldn't.

This is what I was thinking.. whether doing this is actually safe? and won't we have the same problem with GET?

What is the timeline for this to be removed? If it is short-term, then it could be fine for RBAC and others. In some ways this isn't that different from the previous code for PUT support, to my understanding (other than RBAC). If it is longer, I'm not sure what we'll want to do.


Remove version: Jackett.Jackett version 0.20.3340

404 - release deleted
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/Jackett/Jackett/releases/download/v0.20.3340/Jackett.Installer.Windows.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 918)


creating a page which contains about alumni of college

Hey, I am one of participant of GSSOC'21..
I would like to contribute by creating a landing page that contains info about  alumni of college.
looking forward for your reply.
Thank you.

@shefali12-ab That task is assigned to someone else as per the FCFS rule. You may have to wait until we get any result from that assignee or I would say you must start with posting some more ideas in the Open to Ideas thread.
I have some other designs for pages as well. Let me know if you can do some complex pages involving inside features of this project.

yes sure, you can discuss with me about complex pages . I would like to work on them.

@shefali12-ab Okay, I am adding some more designs and will let you know very soon.

Okay thank you, waiting!!
On Thu, Mar 25, 2021, 16:42 YASH PATEL @.***> wrote:

@shefali12-ab https://github.com/shefali12-ab Okay, I am adding some
more designs and will let you know very soon.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ChetnaNSharma/Alumni-Connect/issues/8#issuecomment-806565022,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANRGX72JBT4AKAEMHN7QQWTTFMLAHANCNFSM4ZTZCNCQ
.

Okay thank you, waiting!!
…
On Thu, Mar 25, 2021, 16:42 YASH PATEL @.***> wrote: @shefali12-ab https://github.com/shefali12-ab Okay, I am adding some more designs and will let you know very soon. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANRGX72JBT4AKAEMHN7QQWTTFMLAHANCNFSM4ZTZCNCQ .

@shefali12-ab

@shefali12-ab Can you open one more issue, I am assigning you some screens there. I accidentally closed the issue.

@arpit456jain Can you open one more issue, I am assigning you some screens there. I accidentally closed the issue.

Yes sure sir

#24


Adding Planning status to UI filter

Currently there is no Planning filter in UI on Jobs Tab. Its immensely difficult to traverse all jobs to find reflections that are waiting for other reflection to complete. Currently waiting reflections are in Planning state which is not covered by UI filter.
Probably current Enqueued filter can unite both Enqueued and Planning statuses? Let me knwo if it is

is this under consideration?

@rclintonrca I don't work for Dremio, but I did manage to get a PR pulled in. In general, you should assume a PR is not under review unless you hear otherwise.  I asked Dremio about this directly back at the beginning of the year, and the message I got back was that while Dremio (the company) supports many various open source efforts such as Apache Arrow, Catalyst, etc... The Dremio-OSS release is mainly something produced internally, with external releases.  In general, Dremio (the company) does not accept PR's for Dremio-OSS.


Why no FromRawFd?

How do I use pre-opened (for example by inetd) or received from another UNIX socket file descriptor in tokio-uds?

I see there is from_stream, and usual UnixStream has FromRawFd. It would be easier to just provide FromRawFd.

Thanks for the report! There's no FromRawFd because these types are associated with an event loop, and FromRawFd doesn't give the ability to pass in an event loop to associate.

Maybe it should be mentioned in the docs then, for searching for "FromRawFd" or "from_raw_fd" not to hit nothing.

Sounds like a good idea to me!


One issue that confused me in lesson 6, about link address

This is a great tutorial, I learned a lot of concepts about linux in this site. But one issue confused me in lesson 6:
In linker.ld, the third line set link address to 0xffff000000000000, and in function kernel_process invoke move_to_user_mode, inside which invoke allocate_user_page. The second parameter of allocate_user_page is 0. I think this means that in user space, the address is from 0 to 4k, but the link address is above 0xffff000000000000. How this could work normally?

This works because compiler only uses relative addresses when compiling user.c and user_sys.S (those are 2 files that are copied to the new page in the move_to_user_mode function ) So in this particular case we don't care what the link address is.

Thanks for your reply. But why compiler only use relative addresses when compiling user. c and user_sys. S.  I checked the makefile, no special options found.  Did I miss some thing?

Because this is the default behavior: compiler always generates only relative addresses, unless it is not possible or you tell him otherwise


show active nav item in docs

closes #1870
uses location.path to set an active class on matching nav items
uses the current hover state as active state, open to suggestions for improved styles though

Coverage remained the same at 78.819% when pulling 562dc7f2bbf032962de4d30a52753f727c14cb54 on mparke:add-nav-active-state into 568bf00788b46a133d38df4fbff2946610a886b2 on linode:develop.

Coverage decreased (-0.03%) to 78.826% when pulling 3f792e9a26052551743fd014ed717c0a47a742ba on mparke:add-nav-active-state into 2cd079b7264b9bfd51b921bfda18b0f76b973a5b on linode:develop.

@eatonphil fixed, now represented in endpoints

Coverage increased (+0.01%) to 78.865% when pulling 818f4d39deb5e5c4f210cdaabf103af9ffd3c43d on mparke:add-nav-active-state into 2cd079b7264b9bfd51b921bfda18b0f76b973a5b on linode:develop.

Nothing that it doesn't work correctly in Guides or Libraries subsections.

Coverage increased (+0.01%) to 78.865% when pulling 8b972819f6e8f016b6d81a6895625c99a27f4b01 on mparke:add-nav-active-state into 2cd079b7264b9bfd51b921bfda18b0f76b973a5b on linode:develop.

@eatonphil updated & rebased, should be good

Coverage remained the same at 78.871% when pulling 3bceed3df27046d05caf2fe512cc6ee6089c1de6 on mparke:add-nav-active-state into 83819efa183d6b0c5fea9e99eb2c5ee09a62983b on linode:develop.


Incorrect jQuery value in Ajax call.

In our Jaxon class, a click handler is set on a button with this PHP code.
$this->jq('li.delete>a')->click($this->rq()->del(jq()->parent()->parent()->attr('data-id'))->confirm('Delete?'));

The following javascript code is generated.
$('li.site_delete>a').click(function(){jaxon.noty.confirm('Delete?',function(){Jaxon.App.Source.Site.del($(this).parent().parent().attr('data-id'));});})

The javascript $(this) variable is supposed to be the a link the user clicked on.
But due to the confirm function, the variable is used in a different context, making its value undefined.

Fixed in commit 2017a5c700dc58c26ef1ca97f0679030a177808c.


feat(@angular/cli): expose setup hook so the user can access the Express app object and apply custom middleware

In some cases its useful to do some custom routing on the server.
webpack-dev-server covers this use case by exposing the express app instance trough the "setup hook" on the config. With this pull request this feature is exposed to the user.
From the webpack-dev-server docs:
...
setup: function(app) {
    // Here you can access the Express app object and add your own custom middleware to it.
    // For example, to define custom handlers for some paths:
    // app.get('/some/path', function(req, res) {
    //   res.json({ custom: 'response' });
    // });
  },
...

An example of a setup-script:
var cookieParser = require('cookie-parser')

module.exports = function(app) {
  app.use(cookieParser())

  app.get('/', function(req, res, next) {
    if (!req.cookies['connect.sid']) {
      res.redirect('http://localhost:4200/oauth/authorize')
    }

    next()
  })
}

How to run:
ng serve --setup-script setup-script.js

I'm sorry but we're not looking at adding command hooks in this way. This is something we're looking at for the addon system though.


[5.9] Fix issue with is() and unpersisted models

Following up from a #28240 which made this change against 5.8 this applies it to the next release. The commentary from the previous PR highlighted the breaking change of this bug fix and that perhaps it should be held off for now.

This fixes an issue with is() as described in #28172 where it would return true when given model instances that weren't actually persisted in the database. I think the expected functionality would be that it only returns true when comparing persisted database records.

In updating other tests that used is() without taking into considering actual database persistence I've just relaxed them to a simple ID comparison - I think that's probably a better compromise than having to set $exists = true to get them to pass.

@dwightwatson Thanks for taking this on. Is there a reason not to return true in the case of unpersisted models that are the same object (i.e. $a === $b)? This is the situation I've found myself in more than once, to the point that I've overridden the default is() method.

Actually, now that I think about it, it seems like two references to the same object should always return true regardless, whether or not they've been persisted.

@adamtgehutt this was the one issue I had with changing the functionality. Even though this is being put off until the next release, I think it would be good to allow this to continue working.

@devcircus I hear you, but the breakage you describe in #28240 happens either way. With this pull request, is() will always return false on unpersisted models, even if they're literally the same object. Your code wants it to always return true on unpersisted models, so this pull request breaks it with or without my proposed change.

Ah. Thx.

I don't totally understand the use case for comparing unpersisted model instances, but would something like this achieve what you're after?
public function is($model)
{
    if ($this === $model) {
        return true;
    }

    return ! is_null($model) &&
           $this->exists &&
           $model->exists &&
           $this->getKey() === $model->getKey() &&
           $this->getTable() === $model->getTable() &&
           $this->getConnectionName() === $model->getConnectionName();
}

That is, if it is literally a reference to the same object instance it returns true otherwise it falls back to the "persisted and representing the same database row" result.

Personally I'm not looking for the functionality at all as I see it as the wrong way to achieve such comparisons. However since it has worked like this for 3 years you have to expect that it's being used this way.
Currently the "unpersisted" check only works by comparing the table name of each model, so the above code seems to handle that.

@dwightwatson Yes, that does it exactly. Thank you. There are a handful of different use cases, but they often involve iterating through a collection and doing something to a specific item (e.g., removing it, performing a method on it, etc.) Because collections have unreliable keys, using is() is the most dependable test, but currently it only works if everything is already persisted.
@devcircus I totally understand your desire to avoid BC breakages, but the method is called "is". Isn't the idea that it's checking to see if two models are the same? I don't understand why it would be expected to return true arbitrarily just because the two models are both unpersisted. I guess it depends upon what the meaning of the word "is" is.

Here is the original PR for model::is(): https://github.com/laravel/framework/pull/14281
If we look at the code, the intention of is() is clear; it is to compare if the two models refer to the same persistent row on the database. Nothing more.
If we changed this function to do any direct model comparison at any time, regardless of persistence, that changes the "behavior" of this function to be very unintuitive and likely to cause issues for people.
Consider
$userA = User::find(1);
$userB = clone $userA;
$userB->first_name = 'Changed';

In this scenario - doing $userA::is($userB) will still give true, because they refer to the same persistent record. Note how the models are different though.
People wanting to compare two models for equal can just do $userA === $userB - or even put in a PR for a model::equals() which would better describe that scenario.

Also - the fact that we are changing tests to accommodate the fix is also an issue IMO. Why dont we just do
    return ! is_null($model) &&
           $this->getKey() !== null &&
           $model->getKey() !== null &&
           $this->getKey() === $model->getKey() &&
           $this->getTable() === $model->getTable() &&
           $this->getConnectionName() === $model->getConnectionName();

That solves the original issue (that two null IDs would incorrectly give true) - and would allow this PR to be added without changing any of the existing tests?

@laurencei The example you cite:
$userA = User::find(1); $userB = clone $userA; $userB->first_name = 'Changed';
That returns true under the existing code and it still returns true under the proposed change. What am I missing?

@adamthehutt you're right. honestly I'm good with the change and the move to 5.9. I was just concerned that people were using it to say a post IS a post, persisted or not. Truthfully, this method shouldn't be used in that case, so we should probably take this opportunity to remove that functionality altogether and have the method compare persisted models, as it was most likely intended in the first place.

That returns true under the existing code and it still returns true under the proposed change. What am I missing?

Sorry, to clarify - that was in relation to the option being discussed to compare the models "equal" as a fallback, which is why we should not do a direct comparison at anytime.

I don't think I'm going to make this breaking change. It's fairly easy to do the persistence check in user-land if you want to do it yourself.


Git fails to run at all

After a fresh install of Pythonista and Stash, when I run git I get the output:
[~/Documents]$ git
Opening: https://github.com/jsbain/gittle/archive/master.zip
Save as: /private/var/mobile/Containers/Data/Application/B6E83203-4A0E-4C04-B8C3-D99525B426CF/tmp//gittle.zip (??? bytes)
28334
mv: Error: Destination path '/private/var/mobile/Containers/Shared/AppGroup/2BC0A6FB-75F4-42EB-A4BC-4590A3FD623E/Pythonista3/Documents/site-packages/stash/lib/gittle/gittle' already exists
Opening: https://github.com/FriendCode/funky/archive/master.zip
Save as: /private/var/mobile/Containers/Data/Application/B6E83203-4A0E-4C04-B8C3-D99525B426CF/tmp//funky.zip (??? bytes)
8474
mv: Error: Destination path '/private/var/mobile/Containers/Shared/AppGroup/2BC0A6FB-75F4-42EB-A4BC-4590A3FD623E/Pythonista3/Documents/site-packages/stash/lib/funky/funky' already exists
<class 'ModuleNotFoundError'>: No module named 'urlparse'
[~/Documents]$

git really wants to run in py2.  add a #!python2 to the top of launch_stash, or maybe create a copy called launch_stash2...

git really wants to run in py2. add a #!python2 to the top of launch_stash, or maybe create a copy called launch_stash2...

Yep, adding #!python2 to launch_stash.py worked, except when running merely git an error pops up saying that it couldn't import the utils module.
To fix that, run stashconf py_traceback 1, then git and note the error. On StaSh 0.7.2 it says something like "Cannot import utils on line from . import utils". Go to the file where this error originates (it's gittle.py or something like that) and change this line to import utils, then restart Pythonista, and now git should work fine. If it still doesn't, delete the dulwich, funky and gittle folders from site-packages/stash/lib and redo the process described above.

have same issue, running via py3

Python 2 died 1,368 days ago on 1/1/2020 so please do not expect anyone to support it.


Search page: wording

Best solution for this problem
Is it correct English to say 35 contributions to collectives? rather than 35 contributor to collectives

These cards are being redesigned as per the Search Experience redesign project and the new design just has 35 Contributors. So I think that should take care of it. 🙂

Looks beautiful, excited about this :)


Spanish translation

What feature do you want to get added on the base engine?
More than asking for a feature, I would like to add a Spanish translation for Latin America (I created my translation and if it doesn't end up in the official Psych Engine, I will distribute it as a mod or translation of the Psych Engine). I am willing to change the dialogues to Spanish and their correct interpretation (maybe I would add the Tankman voices in Spanish if possible).
I would like to help with other translations into French, but I am terrible at translating many technical things.
For those who want to try my idea, I will launch an unofficial translation of the compiled engine on itch.io (just interface translation and some dialogues).
es-MX.txt
To test your sight, and reliability, please select the option of what should NOT be requested.
Stage Editor, 6K+ support, and winning icons.

I'm experimenting a bit with translations, and it might be a good idea to reduce the font sizes, as some translations take up more space than others
I really don't know if this can be done or not, in the end it's just a comment

What about the main menu and story menu, drawn assets need to be translated

What about the main menu and story menu, drawn assets need to be translated

You can easily reuse the ones that are already made, although it is an example of a proposal, in any case if I need to I can also draw the precision ones.

Duplicate of https://github.com/ShadowMario/FNF-PsychEngine/issues/15093


hypervisor: switch to Q35

Fixes #706

depends on https://github.com/clearcontainers/runtime/pull/705

depends on https://github.com/clearcontainers/packaging/pull/34

depends on https://github.com/ciao-project/ciao/pull/1536

depends on https://github.com/containers/virtcontainers/pull/456


mooplus

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Motivation and Context / Related issue
Dimo convinced me that this was super useful :-)
How Has This Been Tested (if it applies)

Checklist

[x] The documentation is up-to-date with the changes I made.
[x] I have read the CONTRIBUTING document and completed the CLA (see CONTRIBUTING).
[x] All tests passed, and additional code has been covered with new tests.

@brockho @Corwinpro


Handle routing information for each bulk item in the elastic connector

Pull request
Description
Previously we didnt handle routing metadata for single bulk items in a batched event, now we do.
Related
Checklist

[x] The RFC, if required, has been submitted and approved
[x] Any user-facing impact of the changes is reflected in docs.tremor.rs
[x] The code is tested
[x] Use of unsafe code is reasoned about in a comment
[x] Update CHANGELOG.md appropriately, recording any changes, bug fixes, or other observable changes in behavior
[x] The performance impact of the change is measured (see below)

Performance

It already says it is there in the docs, thats why this is a bug.

Oh sneaky so the docs PR was done long before the code PR :joy: more of a very long lag between code and docs then :P


auto change local

while in admin panel with local EN and then navigate to Velocity button, it goes to AR local (which is the default in .env)
please check the video
https://watch.screencastify.com/v/7r6HakAJVS5hjCQb7T4Q
also in tenant button

Hi @mtrf3,
We are not able to reproduce this.

not getting this issue
https://user-images.githubusercontent.com/96044834/152990294-379090e2-15c7-4f98-bb71-167d04d51f48.mp4


545407D8 - Bioshock

Marketplace
Tested on https://github.com/xenia-canary/xenia-canary/commit/7d36c94d6cf1f64d0a420c992fb37249f7adc35d
Issues:
Bioshock does nothing when loading into the current canary build.
Log:
Bioshock_CanaryLog.zip
Labels:
state-nothing

Tested on: https://github.com/xenia-project/xenia/commit/d246e3bc70292b2034ff153feb5ee0ac73cff97b
xenia.zip

audio issues after playing for a while.
Epilepsy warning. Some light sources are flickering violently, especially with unlocked FPS.

Audio issues might be resolved with new XMA decoder, untested.
ConfigINI.IBF modding

ConfigINI.IBF is checked for bytes. For example forcing x16 anisotropic filtering:

apu-garbage | state-gameplay | tech-engine-unreal


Ask : Caffe converter

I try to convert this model for age and gender prediction.
I got really different result than caffe model.
Does I failed or is it possible that caffe and mxnet differences generate this ?

My bad it's me, I forgot a *255 in images modifications before prediction


Inso doesn't pickup inherit from parent authentication

Expected Behavior
Inso should pick up the inherit from parent authentication
Actual Behavior
Inso doesn't pickup inherit from parent authentication
Reproduction Steps

Go to inso shell and execute  test script which contains inherit from parent authentication
Authentication is not picked up from the parent request
This works properly if test is executed from Insomnia app

Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
No response
Insomnia Version
9.3.0
What operating system are you using?
Ubuntu
Operating System Version
Linux Mint 21.3
Installation method
download from insomnia.rest
Last Known Working Insomnia version

Thanks for the report. We're currently working a bunch of inso change, please bear with us.

I have the same problem. The authentication works for a few minutes. Then it stops working but it starts working again when I clone the request (but just in the cloned request).

Also encountering this issue on the MacOS app. Insomnia version 9.3.3.

Have the same problem in the API client. If I switch to another test environment, and refresh the parent authentication, it will still use the old/previous token. Clearing and refetching the token has no effect.
However, if I duplicate the failed request, the new copy will inherit and use the new authentication from parent.
As it is quite annoying to duplicate 20 request for every single staging environment, I hope for a fix soon

Same for me on the macOS app Version 10.0.0

Same MacOS v10.0.0
Any updates, regarding this issue?
Also tried rollback to 9.3.0 and 9.3.2 without success...

Its related to the statefulness of oauth2 tokens compared to other auth methods which don't have a token persistence step.
I think it would be helpful for dx and ux to raise a valid fetched oauth2 token to somewhere higher in the UI than it currently is. I'm thinking perhaps a hover over the auth tab could show key expiry or something. That way it would be clearer if a key is resolved and its state, when inheriting a token.


math mode in gate names is not working

Environment

Qiskit Terra version: 0.23.0.dev0+67f85b0
Python version: 3.9
Operating system: MacOS

What is happening?
Inspired by https://quantumcomputing.stackexchange.com/a/29167/1859
According with https://github.com/Qiskit/qiskit-terra/pull/4669, it is possible to use $ for activate LaTeX math mode in gate names. However, that triggers an error.
How can we reproduce the issue?
Take the possible example:
from qiskit import QuantumCircuit
from qiskit.circuit.library import HGate
circ = QuantumCircuit(1)
circ.append(HGate(label="$U^a$"),[0])
circ.draw('latex')

This triggers a pdflatex compilation error. However, circ.append(HGate(label="U^a"),[0]) works.
What should happen?
This might be a regression. I think at some point we supported math mode in names. What it should happen is that $ activates it.
Any suggestions?
No response

The PR you reference is for the MPL drawer, not the LaTeX one.  From a quick scan-through, it looks like we've pretty much always been drawing LaTeX labels in math mode, except wrapped in a \mathrm.  #5855 added the explicit escaping for ^ and _.
We could probably use a similar approach to #4669; escape the name components that are outside the dollar signs, and pass through the inside-dollar-sign bits to LaTeX verbatim.
(I note that in that stackexchange question, the user's gate name isn't valid LaTeX already - _ consumes one single token, but they want it to consume the entire \mathrm{rot}.  They should have written $U_{\mathrm{rot}}$, most likely.)

The PR you reference is for the MPL drawer, not the LaTeX one.
ups! my bad.

(I note that in that stackexchange question, the user's gate name isn't valid LaTeX already - _ consumes one single token, but they want it to consume the entire \mathrm{rot}. They should have written $U_{\mathrm{rot}}$, most likely.)
I extended the answer with that clarification, thanks.


Use the current default branch to avoid extra redictions

github/explore now has main branch as default.
Signed-off-by: Takuya Noguchi<EMAIL_ADDRESS>Please confirm this pull request meets the following requirements:

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/master/CONTRIBUTING.md.
[x] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).

Which change are you proposing?

[x] Something that does not neatly fit into the binary options above

Editing an existing topic or collection
n/a
Curating a new topic or collection
n/a
Something that does not neatly fit into the binary options above

[n/a] My suggested edits are not about an existing topic or collection, or at least not a single one
[n/a] My suggested edits are not about curating a new topic or collection, or at least not a single one
[n/a] My suggested edits conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs
[x] My suggested edits would be helpful to contributors in future to save their time and to save energy resources.

👍👍


[WIP][RHCLOUD-17832] Internal authentication endpoint

Creates a new internal "Authentications" endpoint which exposes the password of the authentication.

It also removes the password field from the public AuthenticationResponse objects.

Do not review yet, as it will need to be rebased once the following PR gets merged: https://github.com/RedHatInsights/sources-api-go/pull/93

Links
RHCLOUD-17832

/retest

I added a small patch to it so the rewrite doesn't break the current implementations that are passing the query parameter. Nonetheless, what's the purpose of the query parameter?

I added a small patch to it so the rewrite doesn't break the current implementations that are passing the query parameter. Nonetheless, what's the purpose of the query parameter?

Basically if we had multiple encrypted fields we could expose them selectively. For us there is only one so it makes less sense. Basically just an extra layer of security by obscurity for us afaik.

Thank you for the explanation! :smiley:


Support for obtaining the Layer Computed for Rewards

Description

Currently, there is no way to get the LayerComputed field, i.e. the layer in which a reward was computed. Support needs to be added for this, because the Rewards API endpoints need this information.
Affected code

This issue appears in commit hash:
Related files (optionally with line numbers):

Doesn't this need to wait until the new rewards scheme is finalized because rewards might not be for a specific layer but for example the number of blocks submitted in an epoch? @lrettig

Yup. All these related issues are tracked with the rewards tag here, we'll work through them all as we figure out how rewards are going to work.

What this field even means? Layer where reward is computed is the layer where block with that reward was applied

@dshulyak we considered rewards designs where we do epoch-wide smoothing of rewards, and/or reward maturation, where a reward "computed" in layer m is paid (and spendable) in layer m+n. We're going with a simpler reward scheme for now, without either of these, so this isn't needed for now. Thanks for asking.

@lrettig, should layer_computed field be removed from message Reward in proto definition then? https://github.com/spacemeshos/api/blob/7fbc096071e0d3bf7f1feffbc5de8661276dc6af/spacemesh/v1/types.proto#L81

@poszu yes it can be removed for now. If and when we introduce a more sophisticated reward scheme we can revisit this design.


DefinitionItem child cannot be dumped

Example:
package Model {
item Orbit {
attribute sma_km = 6578 [km];
}
}

 DefinitionItem child cannot be dumped


remove QNameID from view value storage

Do not store QName in view value
Pain (fixed):
See issue #103
Now:
Current codec stores QNameID into view value, but ignore stored value in read.
Dept:
Do not store QName in view value.


OAK-9783: useInExcerpt support

Making the ExcerptTest portable from oak-search to the LuceneExcerptTest in oak-lucene.
Porting it to oak-search-elastic.
Enabling the ingestion of fields to use in excerpts into elastic.
Implementing the excerpts:

keeping the original test code
skipping the relative excerpt test because of https://github.com/apache/jackrabbit-oak/blob/a0d1d8c8e511139299252a3ab4aef7d08c1a289c/oak-search/src/main/java/org/apache/jackrabbit/oak/plugins/index/search/spi/editor/FulltextDocumentMaker.java#L147
ignoring allProps because they are not supported yet.
using assert eventually
keeping a single excerpt value (fragment) because even though the Lucene implementation seems to support multiple values (https://github.com/apache/jackrabbit-oak/blob/a87a66322f536832863fce2615fd55d80c9d0f75/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/LucenePropertyIndex.java#L711) they will never be executed because the same implementation is requesting a single fragment (https://github.com/apache/jackrabbit-oak/blob/a87a66322f536832863fce2615fd55d80c9d0f75/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/LucenePropertyIndex.java#L684)

Whenever we merge this PR, the fields to be used in excerpts that weren't indexed already will be indexed now using the default dynamic mapping strategy (keyword + text). Consider optimising the mapping property definition before merging.

@nit0906 for Elastic, excerpts (aka highlight) get extracted from the source. We have decided to always store the complete source. Disabling it could save some space but it would have some consequences. See Think before disabling the _source field in https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-source-field.html


Hotfix/fix ui version

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug Fix.
This PR addresses the bug with incorrect Gekko version shown at the UI, due to old artifact of the UI committed to the code.
What is the current behavior? (You can also link to an open issue here)

UI is prebuilt for an older version (0.5.2) while current stable is 0.5.8
More information at #1221

What is the new behavior (if this is a feature change)?

Fixes the bug by rebuilding the frontend
After this update, users will need to additionally build the frontend (docs are updated)

I know see the current stable has an outdated UI build, I manually fixed this for now.


stop using gcr.io/kubebuilder/kube-rbac-proxy before 18 March 2025 (image being deleted)

Currently, we make use of the gcr.io/kubebuilder/kube-rbac-proxy image which is going to become unavailable on or after 18 March 2025.
As this will break every KServe instance currently deployed, we MUST create a migration plan and help users become aware of what they must do.
You can see the notice about deprecation of all gcr.io repos in a few places:

Notice from Kubebuilder
Notice on GCR Repo
Notice from Google

To fix new versions of KServe, we either need to remove our dependency on gcr.io/kubebuilder/kube-rbac-proxy or migrate to the direct replacement brancz/kube-rbac-proxy, see this notice on the Kubebuilder docs for more info.
NOTE: we should also probably ask Google to redirect some of the critical gcr.io images after that date, to avoid breaking legacy systems which fail to be updated in time.

@yuzisun @sivanantha321 @johnugeorge I just want to bring this critical issue to your attention, as it will break every KServe deployment on 18 March 2025.

Hi,
i have successfully tested the kube-rbac-proxy from quay.io/brancz/kube-rbac-proxy. Can you please update the kserve deployment to use this image instead of the outdated kubebuilder version?
Thanks!

Updated as part of #3867


Embedding op hangs when memory_config is used with  BufferType.L1

@arakhmati , this didn't get picked up and has gone stale, do you know if this still need to be addressed? asking for #4173 and for #4172 as well.


Skip documented fields on models

Resolves #14

Codecov Report

Merging #16 into master will increase coverage by 1.27%.
The diff coverage is 64.28%.

@@            Coverage Diff             @@
##           master      #16      +/-   ##
==========================================
+ Coverage   56.56%   57.84%   +1.27%
==========================================
  Files           6        6
  Lines         198      204       +6
==========================================
+ Hits          112      118       +6
  Misses         86       86

Impacted Files
Coverage Δ

sphinxcontrib_django/docstrings.py
42.28% <64.28%> (+2.42%)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks, good point!

FYI, I've merged this code locally with rebasing. the web editor for resolving conflicts isn't doing what I wanted :-)


3/21 PM Publish

Docs Build status updates of commit a2ea95e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-6.6.0/toc.yml
:white_check_mark:Succeeded
View (azps-6.6.0)

docs-conceptual/azps-7.2.0/toc.yml
:white_check_mark:Succeeded
View (azps-7.2.0)

docs-conceptual/azps-7.3.2/toc.yml
:white_check_mark:Succeeded
View (azps-7.3.2)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Not able to detect if input is dirty or touched and also not possible to disable submit button

@NewOldMax  It is not able to detect if form is dirty or touched and feature to make it dirty by function

For my opinion it's you app logic to check if input is touched or disable submit button on some conditions. This library is only validates value, prevent form submitting if validation fails and give you validation result
class MyForm extends React.Component {
    state = {
        touched: false,
    }

    handleTouch = () => {
        this.setState({ touched: true });
    }

    render() {
        return (
            <TextValidator
                onBlur={this.handleTouch} // or onChange, whatever you need
             />
        );
    }
}


Review usage of global objects

In some places of Compose there are global objects used:
CanFocusChecker
MinLinesConstrainer.last
LazyGridItemSpanScopeImpl
TextLayoutResult

(discovered from an iOS build log)

There's also

SentinelHead
PlacementScope.Companion

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.

The issues still persists. Every time I use minLines attribute I get a memory leak (Android here)


Iceberg Parquet supports multi-threaded reading.

Contributes to https://github.com/NVIDIA/spark-rapids/issues/5942 and https://github.com/NVIDIA/spark-rapids/issues/6085
PERFILE reading for Parquet and the Iceberg reading framework were introduced in PR https://github.com/NVIDIA/spark-rapids/pull/5941, and this PR is adding the multi-threaded reading.

Create a new class GpuMultiFileBatchReader as the wrapper of the multi-threaded and coalescing readers.
Some refactor in GpuMultiFileReader to reuse the useMultiThread logic for Iceberg.
Make some necessary methods static to reuse them in GpuBatchRapidsReader.
Change the original GPU Parquet cloud reader to support per-file read schema.

The current structure of Iceberg multi-threaded reading may not be good enough, will try to improve it in the future.
Performance for s3 compatible storage (seconds)

24 data files are on the cloud

The test ran on the local machine (CPU 12 cores, and one GPU (Titan V, with 12GB memory))

Data Size
CPU
PERFILE
MULTI-THREADED

453.5MB(compressed)
129.220
106.970
49.447

Signed-off-by: Firestarman<EMAIL_ADDRESS>

build

build

Resolved conflicts.

build

build


Text Classification (Multi-Class) not supported anymore?

Hi everyone, i have tried the Autotrain UI in huggingface space and i can't find how to train text classification multi-class setting? Can anyone help me with this?

there is a text classification dropdown. isnt there? 🤔

just to close. it is supported and still there.


Optimize module resolution cache for watch and editor

Before this change we had few issues with the resolution cache.. It only stored resolutions per file. So when something changed we had to go through map and invalidate the resolutions in each file based on what changed. Because earlier resolution was readonly only object with resolution and failed lookup locations, every resolution is distinct even when resolution in say file "/a/b/c.ts" was reused as resolution from file /a/b/x/d.ts. The difference was that the later resolution would contain more failed lookup locations but everything else will be same. Given the number of resolutions to go through to invalidate them, we use to skip going through resolutions and just re-evaluate them when asked for if program contained more than 256 files. So there was lot of time spent in module resolution on rename of files or some such updates..
This PR makes below changes:

This makes resolutions's failed lookup locations as non readonly array so we can append more failed lookup locations to already present resolution. This also returns same resolution instead of copying the content so we have less number of unique resolutions.
Resolutions with failed lookup locations are stored in separate array so its easier to scan through and invalidate them (since that number is lower compared to number of unique resolutions. In case of vscode 475 resolutions with failed lookup locations compared to 13923 unique resolutions)
We also have a map that is from file the resolution is resolved to.  (The max number in this case are 322 in vscode scenario.) Again this makes it easy to invalidate resolutions resolving to certain file.

Here are the number of resolutions for vscode source and rename action in repro
Note that  ResolutionsToFile I am listing files only if number of resolutions are more than 100 to that file otherwise list gets long...

While investigating eslint perf with @uniqueiniquity found out that this helps with eslint when the program contains large number of files

@amcasey
The description already has two data structures added as part of point 2 and 3. Ping me if you have any questions..


permission of /tmp/uwsgi.sock

I'm getting a 502 Bad Gateway when running the docker-compose.yml with podman.
Version: v3.8.1-p3.8.16
Looks like a permission problem on /tmp/uwsgi.sock
podman-compose exec privacyidea cat /var/log/nginx/error.log

shows these lines:
2023/03/13 13:18:24 [crit] 169#169: *1 connect() to unix:///tmp/uwsgi.sock failed (13: Permission denied) while connecting to upstream, client: <IP_ADDRESS>, server: , request: "GET / HTTP/1.1", upstream: "uwsgi://unix:///tmp/uwsgi.sock:", host: "localhost:45655"

When I run a chmod go+rw /tmp/uwsgi.sock in the container all works fine afterwards. That's just to see where the issue is... some permission problem. Did not yet have a look on how to solve it....

@brammeleman thank you for reporting the issue. I'll check on this.

Anyway, could share with me the docker image tag version you are using?

I built the docker image with:
      podman build -t khalibre/privacyidea:dev .

using the version just released (v3.8.1-p3.8.16).

Using a network port instead of a socket-file works for me. (not tested with docker ;-)).
--- a/rootfs/etc/uwsgi/uwsgi.ini
+++ b/rootfs/etc/uwsgi/uwsgi.ini
@@ -1,9 +1,7 @@
 [uwsgi]
 wsgi-file=/opt/privacyidea/etc/privacyidea/privacyideaapp.wsgi
 buffer-size=8192
-socket = /tmp/uwsgi.sock
-chown-socket = www-data:www-data
-chmod-socket = 664
+socket = <IP_ADDRESS>:8000
 # Graceful shutdown on SIGTERM, see https://github.com/unbit/uwsgi/issues/849#issuecomment-118869386
 hook-master-start = unix_signal:15 gracefully_kill_them_all
 need-app = true

--- a/rootfs/opt/templates/nginx-pi-ssl.conf.template
+++ b/rootfs/opt/templates/nginx-pi-ssl.conf.template
@@ -17,6 +17,6 @@ server {
     location / {

         include uwsgi_params;
-        uwsgi_pass unix:///tmp/uwsgi.sock;
+        uwsgi_pass <IP_ADDRESS>:8000;
     }
 }

and ditto for the other nginx template.
This would also allow for having a separate nginx service in docker-compose.yml.

yeah, I'm experimenting to remove nginx from this image, so we have the choice to use another proxy like Traefik or the other.


feat(): add collapse menu item directive

Fixes #16

@Lordnoname Please review!

Due non reviewing. Merging now.


Use label_seq_id if auth_seq_id is not present in CIF

Per https://mmcif.wwpdb.org/dictionaries/mmcif_pdbx_v50.dic/Items/_atom_site.auth_seq_id.html, auth_seq_id is an alternative numbering to match a publication, whereas label_seq_id is a sequential identifier. It is possible to have CIF files with the latter, but not the former (in my case, the file I was using was created by extracting the chain chain LB from PDB 3J9Z in PyMOL, then exported to CIF).
Related: #696

Thank you @luxaritas - looks good to me!


Architecture Week

Things that we should discuss:

Interfaces: How do the various components interact with the state?
Components: What methods make sense?
Mutexes: Who is responsible for locking/unlocking a mutex?
Errors: How much context should errors have? Who is responsible for displaying the error?
Panics: Where (if anywhere) is it acceptable to panic?
API: how can we synchronize API changes across both siad and siac?

Feel free to add more.

API: what gets exposed? What do we use as passthrough? How much does the golang do for you vs. what does it expect to receive? (I'm expecting we'll do a complete re-write of the api in a few months - I feel very new to it)

Save/Load/New conventions for persistence. The State should really be seen as a module and maybe even we should make an interface for it?

Interfaces as a form of documentation vs. flexibility. I've really implemented the modules at this point to provide a clean documentation of exported stuff. I guess it was a bad move. I remember one of the other things that really motivated me to make the interface was that I was having circular import problems. The core was importing the modules, and the modules were also importing the core for some reason. I don't think they do that anymore. (They needed eachother?)

At the same time, it's nice to think of each component as being able to be swapped out for other stuff. Except the core does less and less and you start to wonder if it's even needed anymore? Should we design components to always be exposed? When exposing components, the things we typically try to protect are the configuration variables. Are those things that should be protected? The other modules/components do need to be looking at each other, which tends to expose the configuration stuff anyway. Ironically, I think the daemon can just replace the core, and we can move 'modules' to a top level directory with a bunch of sub packages, and 1 file for each interface.
I like the idea of having the modules regulate all of their own complexity. Maybe each module should even expose it's own api handlers, as opposed to having the daemon do everything? (probably not though). You just spin them up and they exist in their own world, and request things from each other and do stuff as you ask them.

File staging: We want to support low latency stuff, but we also want to support high latency stuff. Especially when the network is in the early days, there might be glorious volumes of downtime. This means that recovering a file could take a while. Need a way to upload it, erasure code it, encrypt it, and send it out. If you're doing a 20GB file at redundancy of 4, you've got 80GB of stuff to manage. We need to make sure we can erasure code it, encrypt it, and ship it to a bunch of different hosts without needing extra workspace on the disk. You'll have to do every part of the process in memory, which is rough because you'll need to get the merkle hashes of everything before you can make the contracts.

General Robustness: Read a thing about biological robustness and general system robustness. And the successful strategy seems to be a silly amount of redundancy and failure tolerance. Trees can lose 30% of their branches and still recover. Humans can lose 30% blood and still recover. A huge portion of your liver can go and you'll be okay. Basically, if you want a good network that'll survive any problems, make each part self-sufficient and able to route around the outages of any other part. I think this should apply to our programming style as well. Bugs are less of a problem if you need a chain of 3 or 4 things to all go wrong at once, especially if the system is self-repairing. That's why I'm really against panics in the code, one bad function can knock out the whole program, when really it could just return an error and everything else could work around the issue.

Good talk about Go design decisions (from the guy who wrote Cobra): http://www.slideshare.net/spf13/common-mistakes-in-go

What do we have that's considered still needs to be done for this?
I would like to see the network/peering stuff reorganized.
Do we want to split siad into a 'main' and a 'meat' package? The main would probably be just one or two files, and the meat package would be the rest. But then siad would be a library instead of purely an executable, which I think makes sense.
The renter/host/hostdb all need to be brought back alive so the api is working again. There is still some work to go on this.
Is there anything else? I think that we've mostly cleaned up a lot of this in a good way.

I don't see a lot of value in having a separate siad package. I'd prefer to split off an API package, because it would be useful to both siad and siac.
network will probably wind up as a module. I'm not sure that this will have many benefits besides removing a folder from the top-level, though. I suppose the consistency is nice.

lol we're still not done with this part.
Things got disorganized a bit when I went ham on the consensus package but I think it was the right time to do that.

I'm going to consider this finished now that the gateway has been moved out. All that potentially remains is splitting main and siad, but that can be considered maintenance instead of architecture.


reset role_id_seq and do not specify id on inserts

this removes test failures from when role_id_seq
is an id already inserted.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1628/
Test PASSed.


Migrate from secrets in supervisord.conf to environment variables

supervisord.conf currently uses handwritten secrets:
https://github.com/twolfson/twolfson.com-scripts/blob/99b863ae15bf5d933bbdd5463b77eee6d250b81c/data/etc/supervisord.conf#L37
This is problematic because it doesn't allow for simple rsync + mv to update/track files.
One solution that we've used plenty is to use .env files in the repo itself to handle secrets.
In practice, we'd probably:

During provisioning, establish .env by hand in twolfson.com/main on digital-twolfson.com
Update deploy-twolfson.com.sh to copy that file between deployments

There are plenty of other solutions that work for environment variables as well
See relevant TASK: ... https://github.com/twolfson/twolfson.com-scripts/issues/15 via git grep

We also had some thoughts/ideas here: https://github.com/twolfson/twolfson.com-scripts/tree/4590a82e86294e77f2cec6e184723d6358b82a6c#managing-secrets

Our twolfson.com repo already handles .local files so this was easily added to the repo in 3.1.0 =)


Enable databricks-sql-connector dependency when installing for Databricks

Uncomment this line. Probably there is a reason why this line is commented. Now I am installing this dependency myself.

ping


Minified library is not up to date

Hi guy.
I think you forgot to update the minified version of your library ;)
When using it, with independent set as false (by default and as explicit parameter), the accordions don't work! Maybe there are other bugs, but I didn't tested more.
Thanks for reading!

Hi @JonGarbayo,
Thank you for your report.
Il will check this immediatly.

I have created a new v0.3.1 release with that correction.
Regards,


[bug] ruamel is not being properly installed in the pip package

Describe the bug
Ruamel isn't properly imported. When running the render command I see this error:
$ qhub render -c qhub-config.yaml -o ./
Traceback (most recent call last):
  File "/home/tyler/anaconda3/bin/qhub", line 5, in <module>
    from qhub.__main__ import main
  File "/home/tyler/anaconda3/lib/python3.7/site-packages/qhub/__main__.py", line 3, in <module>
    from qhub.cli import cli
  File "/home/tyler/anaconda3/lib/python3.7/site-packages/qhub/cli/__init__.py", line 6, in <module>
    from qhub.cli.deploy import create_deploy_subcommand
  File "/home/tyler/anaconda3/lib/python3.7/site-packages/qhub/cli/deploy.py", line 4, in <module>
    from ruamel import yaml
ModuleNotFoundError: No module named 'ruamel'

The package in the setup.py file has a .yml extension when it shouldn't:
https://github.com/Quansight/qhub/blob/main/setup.py#L36

This was a local environment error that caused the problem. Solved by creating a blank conda environment and pip install qhub again.


Adding missing equals Methods and Tests

PR for #2034

Hi @tomakehurst, any feedback on this? Would be nice to have these features ;)

I'm curious as to why you feel these are required on these classes. Can you share some examples of where the lack of these is a problem?

@tomakehurst  Without these methods, using hash-based, sets or sorted collections (or just sort()) may lead to undesired results.  I can imagine that someone uses WireMock as an API and wants to organize data before passing the parameters (e.g. for UX purposes). But I am not sure whether it is the use-case @jnt0r has in mind

I'm building a layer above WireMock to dynamically create Mappings at runtime via proxyMappings. Every proxied request is recorded and then transformed to the format and checks we need and dynamically saved as a mapping. To detect if a mapping already exists, I'm using equals method. Without overriding these methods, you cannot compare mappings and parts of them.

@oleg-nenashev I understand in general what the impact of not including these methods is, but when I see people asking about them in internal classes where they're not needed for WireMock to work correctly I worry we're encouraging coupling to implementation details.
Having said that I think @jnt0r has a reasonable use case in mind here so I think we should merge this.
One comment about the change - I notice there are no test assertions for the hashCode() implementations - could we add these too?

Alright, thanks @tomakehurst.
I updated the PR and added the tests for the hashCode methods.


Docs: mention about gmake on FreeBSD

I am not sure this problem occurs in all situations but on my shared hosting with SSH access and FreeBSD OS I have to use gmake command instead make to manually compile Gitea. It seems to be it would be good to mention this in the documentation on the "Installation from source" page.

Feel free to submit PR with such changes as at least I don't have much FreeBSD experience :)

https://github.com/go-gitea/gitea/pull/4446?

I will check it.

I checked it. It works if I try to build Gitea from the master but this PR is not backported to current stable (which I tried to build the first time).

@TomaszGasior I don't think it's necessary to back port that PR to v1.5. You can copy that make file and build yourself.

@TomaszGasior we are already short on people who help on documentation so we can't keep it up version specific as in 1.6.0 it will be already solved

Okay. Thanks for info!


Add configuration/setting button

Add the setting button.
Allow user to modify the string that identifies the versions.
Make the app maintain that info even after closed.

The feature was pushed


[flex_attention] Softcap perf questions

I am using this pytorch provided script to benchmark flex attention with eager and got the attached results (default_results.txt) on an A100.
I modified the script to change the score_mod function to soft_cap function  like this and got the following results. Full result output is attached as well (softcap_results.txt). Speedup is compared with eager (afaict).
=========================================================FWD Speedups========================================================

| Type    |   Speedup | score_mod   | mask_mod   | dtype          | shape(B,Hq,M,Hkv,N,D)       |
|---------|-----------|-------------|------------|----------------|-----------------------------|
| Average |     0.488 |             |            |                |                             |
| Max     |     0.537 | soft_cap    | None       | torch.bfloat16 | (2, 16, 512, 2, 512, 128)   |
| Min     |     0.385 | soft_cap    | None       | torch.bfloat16 | (2, 16, 1024, 16, 1024, 64) |

Is this the expected performance for softcap? Did I miss something?
GPU used: A100
Packages and their versions
torch                    2.5.0.dev20240812+cu118
pytorch-triton           3.0.0+dedb7bdf33

nvcc version:
$ nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2022 NVIDIA Corporation
Built on Wed_Sep_21_10:33:58_PDT_2022
Cuda compilation tools, release 11.8, V11.8.89
Build cuda_11.8.r11.8/compiler.31833905_0

Please feel free to let me know if I need to provide more information. Thanks.

You might want to use approx tanh instead of torch.tanh() for soft capping. check out this example: attn_gym/mods/softcapping.py

Yes, definitely, you need to use approx tanh (like in this example: https://github.com/pytorch-labs/attention-gym/blob/5e0d1b8053a19b339ddf7c8015f2c4e02bf5b92c/attn_gym/mods/softcapping.py#L13). Normal tanh in CUDA is extremely expensive.

Isn't the formula for softcapping incorrect?
    def tanh_softcap(score, b, h, q_idx, kv_idx):
        return score * tanh(score / soft_cap)

https://github.com/pytorch-labs/attention-gym/blob/5e0d1b8053a19b339ddf7c8015f2c4e02bf5b92c/attn_gym/mods/softcapping.py#L68
Seems like it should be
    def tanh_softcap(score, b, h, q_idx, kv_idx):
        return soft_cap * tanh(score / soft_cap)

@SmerkyG Yeah, that's right haha. Do you want to submit a PR :)

Sorry, I don't even use the repo or have it downloaded, was just looking quick and noticed!

fixed


[5.6.8] Not able to use tightenco/collect

Laravel Version: 5.6.8

Description:
Because we now treat tightenco/collect as a conflict (PR https://github.com/laravel/framework/pull/23379) composer installs both packages and adds them to the autoloader.
The problem is that the autoloader sequence is wrong and puts tightenco/collect in front, therefore loading the tightenco/collect helper methods instead of Laravel's helpers.
'fe62ba7e10580d903cc46d808b5961a4' => __DIR__ . '/..' . '/tightenco/collect/src/Collect/Support/helpers.php',
'caf31cc6ec7cf2241cb6f12c226c3846' => __DIR__ . '/..' . '/tightenco/collect/src/Collect/Support/alias.php',
'f0906e6318348a765ffb6eb24e0d0938' => __DIR__ . '/..' . '/laravel/framework/src/Illuminate/Foundation/helpers.php',
'58571171fd5812e6e447dce228f52f4d' => __DIR__ . '/..' . '/laravel/framework/src/Illuminate/Support/helpers.php',

Because of this, the wrong collection classes will be passed internally:
Type error: Argument 1 passed to Illuminate\Routing\Router::sortMiddleware() must be an instance of Illuminate\Support\Collection, instance of Tightenco\Collect\Support\Collection given, called in /Users/marcel/Code/chatwidget/vendor/laravel/framework/src/Illuminate/Routing/Router.php on line 676

Steps To Reproduce:
laravel new testapp
cd testapp
composer require spatie/crawler
open http://testapp.test

See error:
Type error: Argument 1 passed to Illuminate\Routing\Router::sortMiddleware() must be an instance of Illuminate\Support\Collection, instance of Tightenco\Collect\Support\Collection given, called in /Users/marcel/Code/chatwidget/vendor/laravel/framework/src/Illuminate/Routing/Router.php on line 676

Could someone help me understand why tightenco/collect is used at all in the frameworks composer.json?

We're declaring that we're incompatible with the older (<5.5.33) version of tightenco/collect since that version was using identical namespaces and class names as Laravel provided. It's not being pulled into your project by the root composer.json file, but the spatie/crawler project.
So, the tightenco/collect package declare helpers that are not compatible with Laravel. I believe the current stance is that this is someone else's fault. They shouldn't use our function names. Booo them! Booo! https://github.com/laravel/framework/issues/20370 https://github.com/laravel/internals/issues/709
On a more serious note, the only way around this is to namespace/prefix all our helpers with something relevant. We cannot control what third party code is declaring, but we can reduce the area of conflict.
Another problem is that we're conditionally defining the helper functions. This means that the code doesn't fail in helpers.php, but instead later when someone discovers that the function they called wasn't the one they intended to call.

The clarify, the problem is not that we're declaring a conflict in our composer.json file, that doesn't pull down the tightenco/collect package. You get it because you're installing spatie/crawler with depends on it.
The problem is that you've got a package that has conflicting helpers. That's not allowed. Boo!

FWIW, we consider this an issue that collect and the collect team are are taking the responsibility to fix. If it requires a change at the framework level we will attempt to PR it but I believe it won’t.

I installed a captcha package for Laravel and got the exact same problem.

@mattstauffer any updates/ETA on this, we'd really like to use spaties mixed-content-scanner ;-)

@repat Please see https://github.com/tightenco/collect/issues/92 , a fix is released.

@mpociot this issue can be closed i guess :)

Yeah - this is now fixed in 5.6.12 of tightenco/collect - https://github.com/tightenco/collect/releases/tag/v5.6.12

Hiya, somewhat of a modern PHP noob here.  What's the bottom-line fix for this?  I did a composer update and now my valet is broken:
'''
Parse error: parse error in /Users/loslosbaby/.composer/vendor/tightenco/collect/src/Illuminate/Support/Collection.php on line 154
'''
Etc.  Do I understand that I need to look for this in one of the composer files and remove it?


Run grub stuff from chroot

Description

Why is this needed

Fixes: #
How Has This Been Tested?

How are existing users impacted? What migration steps/scripts do we need?

Checklist:
I have:

[ ] updated the documentation and/or roadmap (if required)
[ ] added unit or e2e tests
[ ] provided instructions on how to upgrade

@mmlb - Is this PR still being worked on? Do you need any help to move this forward?

Nope not being worked on atm, we can close and I'll re-open if/when I dust it off. Alternatively, happy to have anyone else pick it up :D.

Which actually would be a little difficult as I think this is stuck waiting on useful image in github.com/packethost/packet-images that we can test with.

@sfunkhouser has been working on the image build pipelines

Oops I closed this by mistake somehow.

Hey @mmlb, is this still something you're working on? If so, maybe we put a help-wanted label on it?

@mmlb, I see this is in draft for a long time. Please can you take look at this PR and update it?


Updated locales

Using the following python script (that anybody can use as they wish, I made it with ChatGPT after all lol), updated a bunch of EPG locales.
The json file was an extract of all the programs from the same channels based off the same source for reference.
import json
import fasttext
import xml.etree.ElementTree as ET
import os
from collections import defaultdict

model = fasttext.load_model('/root/lid.176.bin')

json_file_path = '/root/epg_programs.json'

def update_xml_file(site_id, channel_id, new_lang):
    xml_file_path = f'/root/epg/sites/{site_id}/{site_id}.channels.xml'
    if os.path.exists(xml_file_path):
        tree = ET.parse(xml_file_path)
        root = tree.getroot()
        channel_element = root.find(f".//channel[@xmltv_id='{channel_id}']")
        if channel_element is not None:
            channel_element.set('lang', new_lang)
            tree.write(xml_file_path, encoding='utf-8', xml_declaration=True)
            print(f"Updated language for channel '{channel_id}' in XML file for site '{site_id}'")
        else:
            print(f"Channel '{channel_id}' not found in XML for site '{site_id}'")
    else:
        print(f"XML file not found for site '{site_id}'")

with open(json_file_path, 'r') as file:
    data = json.load(file)

channel_lang_counts = defaultdict(lambda: defaultdict(int))

for entry in data:
    if entry['type'] == 'table' and entry['name'] == 'programs':
        for program in entry['data']:
            detected_lang = model.predict(program['description'], k=1)[0][0].split("__label__")[1]
            channel_lang_counts[program['channel']][detected_lang] += 1

for channel, lang_counts in channel_lang_counts.items():
    most_common_lang, count = max(lang_counts.items(), key=lambda x: x[1])
    total_counts = sum(lang_counts.values())

    if total_counts > 0 and count / total_counts >= 0.8:
        for entry in data:
            if entry['type'] == 'table' and entry['name'] == 'programs':
                for program in entry['data']:
                    if program['channel'] == channel and program['lang'] != most_common_lang:
                        update_xml_file(program['site'], channel, most_common_lang)

print("Processing complete.")

There we go.
Also edited the code, and made some checks better.
Updated the code at the top of the page for anyone who wants to use it


Add Terp Network: Testnet Resources, Delete Chronic Network Resources

Chronic Network Project was killed due to corrupted distribution of ownership.
Also included is testnet registry resources for athena-1, the testnet for Terp Network.

For now let's set Chronic Network's network status to 'killed' rather than delete it all. At least until we figure out how to best handle killed chain data (which might go to its own folder).


fix(actions): ghcr prefix

Description
quick fix to trusted-sync publish

#377  👈
main

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

Join @refcell and the rest of your teammates on  Graphite

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 77.7%. Comparing base (c7954ea) to head (68cf425).

Additional details and impacted files

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix/webpack v5

Codecov Report

Merging #181 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #181   +/-   ##
=======================================
  Coverage   90.71%   90.72%
=======================================
  Files          47       47
  Lines        3739     3741    +2
  Branches      491      493    +2
=======================================
+ Hits         3392     3394    +2
  Misses        347      347

Impacted Files
Coverage Δ

src/webpack/plugin.ts
100.00% <100.00%> (ø)


Migrate txs to DashMap

As a small optimization

We would potentially have to be careful not to hold locks across await-points here. Tokio's Mutex allows that, but DashMap does not.


iOS Xamarin Support

Has this ever been tested with iOS?

Well no this is not tested with iOS. However, I have run some compatibility tests from Xamarin and I remember that only a few items would need modification.
However, my biggest concern with iOS would be  XMPP support in general, iOS does not allow persistent TCP connections, on the background, afaik, and XMPP and especially this library do need them, in order to have a background active connection.


Mock setupNotification overwrites Gatt value

Summary
Why does the setupNotification(...) method overwrite the value of the BluetoothGattCharacteristic?
In detail, look at https://github.com/Polidea/RxAndroidBle/blob/master/mockrxandroidble/src/main/java/com/polidea/rxandroidble/mockrxandroidble/RxBleConnectionMock.java#L430
private void setCharacteristicNotification(UUID notificationCharacteristicUUID, boolean enable) {
   writeCharacteristic(notificationCharacteristicUUID, new byte[]{(byte) (enable ? 1 : 0)}).subscribe();
}

Hello @blakopf
To be honest — I do not see a reason — this may be a bug. Why do you ask?

I setup my mock with various services and characteristics with values.
If I connect to the mock later and setupNotifications(...) for a UUID, the value of the characteristic for this UUID becomes 1 (and 0 if I unsubscribe from the notification):
new byte[]{(byte) (enable ? 1 : 0)}
I think this is a bug and the value should not be overwritten.

It seems so. The fix has just been landed and should be available shortly in 1.3.0-SNAPSHOT.
Best Regards.

That was fast, thank you very much.


Add option to include all but some files

TL;DR
Currently the only way to do this is by specifying every file to be included. An "include all but X" would be convenient to have.
cc @verbanicm @drevell
Detailed design
No response
Alternatives considered
No response
Additional information
No response

I had forgotten this until I just saw it in the source code, but I already implemented one version of this: https://github.com/abcxyz/abc/blob/cd9db9a341951066442084bbdc788fd7dca24553/templates/model/spec.go#L313 . We may want to redesign it with our latest thoughts though. cc @kevya-google

Will rename to exclude.

Discussed offline, we're ok with keeping this as skip.


Fix for memory arbitration/reclaim in single-threaded execution

Memory arbitration/reclaim works as expected in single-threaded execution in most cases except for some issues during handling task pause/resume. This patch fixes the issues.
And enable 3 existing test cases in SharedArbitratorTest for single-threaded execution:

SharedArbitrationTest.reclaimToJoinBuilder
SharedArbitrationTest.reclaimToAggregation
SharedArbitrationTest.reclaimToOrderBy

@xiaoxmeng @mbasmanova

@mbasmanova comment addressed, thanks.


[NG] Fix for focus issue when escaping forms in modals

Added a reference to the previous active element
Adds a method to let focus trap users set focus in the previousActiveElement if they need to
closes #1194

Signed-off-by: Matt Hippely<EMAIL_ADDRESS>

Added do-not-merge b/c I need a second round of reviews for the feedback changes.

Looks good from my end.


exception:TypeError: Object [object Object] has no method 'registerModule'

按照官方文档
weex.registerModule('guide', {
  greeting () {
    console.log('Hello, nice to meet you. I am your guide.')
  },
  farewell () {
    console.log('Goodbye, I am always at your service.')
  }
})

在android端调用出现如下错误：

出现了类似的错误
entry.js 中已引入 weex-vue-render, 在组件中使用 weex.registerModule 注册组件时提示如下:
weex.registerModule is undefined

This PR/issue doesn't received response since Weex migrated to Apache two years ago and this repository is no longer active yet.
Feel free to ask question in new repository and thanks for your contribution.

This issue is outdated for a long time and will be closed now. You can create a new one if you still have questions.


Is the development of this plugin abandoned?

Just curious if there will be further updates to this plugin.

Yeah. Just been super busy over the holidays.

From: lensherm @.>
Sent: Wednesday, December 29, 2021 6:28:38 AM
To: fjs21/homebridge-blueair @.>
Cc: Subscribed @.***>
Subject: [fjs21/homebridge-blueair] Is the development of this plugin abandoned? (Issue #5)
Just curious if there will be further updates to this plugin.
—
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ffjs21%2Fhomebridge-blueair%2Fissues%2F5&data=04|01||8b659bc167ea4dd92a9a08d9cabe5c7b|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637763741203733375|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=wBbGj83ar66TcWdKFfdY1JCOP67YaOWQeoPMNK2%2B%2FZ8%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPVM4C3UWJZGIW7MBE36BTTUTLWGNANCNFSM5K5ZCHKA&data=04|01||8b659bc167ea4dd92a9a08d9cabe5c7b|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637763741203733375|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=X%2BAZ67njcPeqs9XOliM04PtczPIaqzomDrMmgsN8Ir8%3D&reserved=0.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Got it. Thanks for your work on this.


added kanister app

Description

Motivation and Context

[x] I have raised an issue to propose this change (required)

#569
How Has This Been Tested?

Are you a GitHub Sponsor (No)

[ ] Yes
[X] No

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Documentation

[ ] I have updated the list of tools in README.md if (required) with ./arkade get -o markdown
[x] I have updated the list of apps in README.md if (required) with ./arkade install --help

Checklist:

[x] My code follows the code style of this project.
[X] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[X] I've read the CONTRIBUTION guide
[X] I have signed-off my commits with git commit -s
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

[ ] I have tested this on arm, or have added code to prevent deployment

As far as I'm aware, kannister can't run on arm clusters, so do we need to put a blocker in this app just like we do for Istio?

Yes, currently Kanister cannot run on ARM.


Modify README with steps to upgrade from older repo

Ghost for OpenShift
Ghost is a free, open, simple blogging platform that is available to anyone who wants to use it.
Visit the project's website at http://ghost.org • docs on http://support.ghost.org.
Running Ghost on OpenShift
The easiest way to deploy Ghost on OpenShift is to use the QuickStart on the OpenShift Hub.
Note these OpenShift specific changes:

The content/data and content/images directories have been removed.  They are created on the server and symlinked to your $OPENSHIFT_DATA_DIR so that posts and uploaded images will persist across 'git pushes'

Even though the Node.js cartridge itself is scalable, this application will not play nice with scaling right now because the images are stored on disk, and since OpenShift does not currently support shared physical disk storage across scaled gears, this cartridge will not scale.  We are working on a solution for this.

This quickstart is setup to use MySQL (5.1 or 5.5) or PostgreSQL (8.4 or 9.2).  Once you click the Deploy link on the OpenShift Hub, you can choose which database you would like to use.

If you use a custom domain, modify the production url field in the config.js file.

Upgrading to The Latest Version
Upgrading from the older version of this repo < 0.5.7 requires extra steps. You'll notice there is no longer ./core, that is because this repo now depends on ghost which lives in ./node_modules/ghost.

Delete ./core
Delete ./package.json & ./index.js
./Gruntfile.js & ./bower.json are unnecessary because they are handled by the external ghost dependency and can be removed.
Copy the following files to the root: ./Makefile, ./index.js, ./package.json
Make a copy of your ./config.js because you'll need to copy that over but you don't want to overwrite it.
Copy ./config.js to the root.
Modify ./config.js so it uses your configuration variables, I.E. mail {...} and url.
Run npm install --production
push your updates.

If you are upgrading from >= 0.5.7 then in most cases all you need to do is run npm update in root directory. There are 2 things you should be aware of while upgrading your blog:

RedHat OpenShift runs on Linux x64 platform. If you are running npm update on any other plaform (e.g. Linux x32 or Mac) you will need to make sure you have node_modules/ghost/node_modules/sqlite3/lib/binding/node-v11-linux-x64/node_sqlite3.node in place.

If you are using default theme Casper you will need to update its code manually with following command: cp -r node_modules/ghost/content/themes/casper/ content/themes/. Note: this will override all custom modifications that you did in the theme.

More information can be found on the Ghost Support Site
Logging in For The First Time
Once you have the Ghost server up and running, you should be able to navigate to http://<your-website>/ghost/ from a web browser, where you will be prompted to register a new user. Once you have entered your desired credentials you will be automatically logged in to the admin area.
Copyright & License
Copyright (c) 2013-2015 Ghost Foundation - Released under the MIT license.

Hi @cleversprocket
Thank you for this work
Could you please create a pull request with these changes?

Hi, I tried but I don't have access.
On Jun 24, 2015 10:58 AM, "Shmavon"<EMAIL_ADDRESS>wrote:

Hi @cleversprocket https://github.com/cleversprocket
Thank you for this work
Could you please create a pull request with these changes?
—
Reply to this email directly or view it on GitHub
https://github.com/openshift-quickstart/openshift-ghost-quickstart/issues/48#issuecomment-114958506
.

Neither do I.
You can fork this repository ("Fork" button at the top), so it will be copied to your account.
You will be able to edit your version and then send a pull request to this "parent" repository.
When you will finish with you changes there will be a "Pull Request" button at the top of your fork of the repository.

Thanks @MunGell I created the pull request.

https://github.com/openshift-quickstart/openshift-ghost-quickstart/pull/49

Awesome, thank you!


Search keeps retrying when there's no data left to scrape

Hi! Thank you for your work, it's helping me so much! I found an issue that is annoying me recently:
Searching for astrophysics since:2023-04-01 until:2023-04-02 with only 50 tweets:
>>> latest_results = search.run(
...     'astrophysics since:2023-04-01 until:2023-04-02',
...     limit=50,
... )
2023-05-04 15:59:47,016.016 DEBUG: astrophysics since:2023-04-01 until:2023-04-02
2023-05-04 15:59:48,164.164 DEBUG: astrophysics since:2023-04-01 until:2023-04-02
2023-05-04 15:59:49,244.244 DEBUG: [success] returned 66 search results for astrophysics since:2023-04-01 until:2023-04-02

Now searching for astrophysics since:2023-04-01 until:2023-04-02 with 200 tweets:
>>> latest_results = search.run(
...     'astrophysics since:2023-04-01 until:2023-04-02',
...     limit=200,
... )
2023-05-04 15:54:43,028.028 DEBUG: astrophysics since:2023-04-01 until:2023-04-02
2023-05-04 15:54:44,178.178 DEBUG: astrophysics since:2023-04-01 until:2023-04-02
2023-05-04 15:54:45,508.508 DEBUG: astrophysics since:2023-04-01 until:2023-04-02
2023-05-04 15:54:46,758.758 DEBUG: astrophysics since:2023-04-01 until:2023-04-02
2023-05-04 15:54:47,883.883 DEBUG: astrophysics since:2023-04-01 until:2023-04-02
2023-05-04 15:54:49,059.059 DEBUG: astrophysics since:2023-04-01 until:2023-04-02
2023-05-04 15:54:50,067.067 DEBUG: astrophysics since:2023-04-01 until:2023-04-02
2023-05-04 15:54:50,733.733 DEBUG: astrophysics since:2023-04-01 until:2023-04-02
2023-05-04 15:54:51,159.159 DEBUG: No data for: astrophysics since:2023-04-01 until:2023-04-02 | retrying in 1.45 seconds
2023-05-04 15:54:53,052.052 DEBUG: No data for: astrophysics since:2023-04-01 until:2023-04-02 | retrying in 2.13 seconds
2023-05-04 15:54:55,555.555 DEBUG: No data for: astrophysics since:2023-04-01 until:2023-04-02 | retrying in 4.80 seconds
(Retries almost lasts forever)
...

The expected behavior for me, when data ends, should be ending the search with only the data that was able to be scraped (let's say that it was 100 tweets).
Other possible error is that the account is being temporarily suspended of searching because of request limits, but I don't think that this is the case. (That's why I chose a low-key topic in a very short date range)
What I think it should be done:

Differenciate whether the account is suspended of searching or there's no data left to scrape
If there's no data left to scrape, stop the search there instead of retrying
Limit the retry interval to a more reasonable one (like only 4 retries) or possibly make it so we can choose how many retries we want

Thanks for the feedback, I think these are all great suggestions. I'll have a look and see what I can do.

Thanks for the feedback, I think these are all great suggestions. I'll have a look and see what I can do.

Check #48 please. I did a few things that I suggested.

Search has now been updated to include a retries param


Map: Add data to shapefile

Good to dump in some of this data so it's not buried in the code. Also might be useful to highlight counties by things like congressional/presidential margin rather than random colors.

[x] Competitive districts
[x] 2016 congressional margin
[x] 2016 presidential margin

fields to the shapefile:
statePostal (string) - state abbreviation for future use
party (string) - party currently holding district
race_margin (real) - 2016 congressional race margin with positive indicating GOP win, negative DEM win
race_margin (real) - 2016 presidential race margin with positive indicating Trump win, negative Clinton win
cpvi (integer) - Cook Partisan Voting Index score, positive R and negative D
rating (string) - Cook race rating
status (string) - Whether a seat is Open, vacant, etc. A null value indicates an incumbant
compete (boolean 1 or 0) - whether or not the race is considered competitive


Project 2 Designs v1

I think there may be some errors in your python file.
https://github.com/SiEPIC/openEBL-2024-02/actions/runs/7841151041/job/21396976372

Thanks for pointing this out- will open another PR to fix

lukasc@Lukass-MacBook-Air submissions % python KLayout\ Python/EBeam_EthanJ_fpcavitiesLargen.py  KLayout SiEPIC-Tools version 0.5.4 SiEPIC-EBeam-PDK Python module: siepic_ebeam_pdk, KLayout technology: EBeam SiEPIC-EBeam-PDK Python module: pymacros No libraries associated to EBeam technology SiEPIC_EBeam_Library_Beta, version 0.4.4 Traceback (most recent call last):   File "/Users/lukasc/Documents/GitHub/openEBL-2024-02/submissions/KLayout Python/EBeam_EthanJ_fpcavitiesLargen.py", line 217, in <module>     klive.show(file_out, lyrdb_filename=file_lyrdb, technology=tech_name) NameError: name 'file_lyrdb' is not defined


Expression processor: Results & Error Handling

Looks good! The only comment left is the updated test expectation. Is it just a temporary change?
The untyped evaluator can be done in its own PR.

Did you check if the escaping issue is a real issue (by running the commandline interface) or just a testing issue?

Did you check if the escaping issue is a real issue (by running the commandline interface) or just a testing issue?
Oh, yes, the three lines only occur when parsing the error during testing. When running the command line interface, the error is the same as the one that is created in the message


feat: convert accelerometer to have units of km per hour per second.

feat: convert accelerometer to have units of km per hour per second (i think?) instead of meters per second per second
fix: change max default value displayed in the bars from 15 to 54 as we are multiplying its value by 3.6.

I looked into this during the implementation itself, it was mentioned that the velocity that the game stores is in meters per second, and that you can convert that to km/h by multiplying it by 3.6.
float curr_acc = ((speed - prev_speed) / (g_dt/1000));
Here we calculate the current acceleration by taking the speed (in meters per second) - previous speed (meters per second) and dividing it by the timedelta since the last frame (in milliseconds) / 1000 to get seconds
Then we end up with an acceleration in terms of meters per second per second
Adding * 3.6 in here you would instead be trying to calculate the acceleration in km per hour per second?
I think I had issues because I tried multiplying the velocity before doing the acceleration calculation.

That sounds correct. Although, perhaps the unit that's displayed should be an option?
Wikipedia's Accelerometer article mentions the following:

Acceleration is quantified in the SI unit metres per second per second (m/s2), in the cgs unit gal (Gal), or popularly in terms of standard gravity (g).

We don't really care about those last 2, but I am curious if km/h/s is a popular unit to use for accelerometers. Not sure if there's any such "standard" for vehicles.

Me neither. I thought the standard was meters per second per second.

@codecat I added an enum where you can switch the unit of measurement to either m/s/s or km/h/s.

Looks good. Thanks! 👍


feat: Added informational page: 'Optimize your ingest'

Great addition by Lucy Lu from EMEA.  She added an informational page which provides data optimization suggestions to the dash and links back to the OMA Data Ingest Governance Guide.

Looks like the NR1 logo was broken when I took the screenshot.  It looked correct earlier.  Any suggestions on how we can fix it?


Does ridables modify the spawning conditions of vanilla mobs?

I noticed a few settings that touched up on whether mobs can spawn or not naturally. Does Ridables modify / overwrite the vanilla spawning conditions at all or is it applied additionally?

It's been awhile, but I do believe the only spawn settings I touch are for the two mins that do not naturally spawn at all in the game (illusioner and giant).
I'll double check sometime this weekend, but I think all other mobs spawn normally without interference.

The only spawn configurations I see are for the two mobs I mentioned (giants and illusioners).
Are you seeing any elsewhere or experiencing anything unexpected?


Custom UITableViewCell from xib

Is there any way to use custom UITableViewCell loaded from xib?

I tried this using the CustomBinder as described here, because I also want to show a section header.
After binding my custom cell class, only the standard cells are created. The TableViewBinderDataSource seems to register new cells which causes Bond to initialize my CustomCell not with the storyboard initializers.
The only way I could make it work is using the tableview bind and dequeueing my own cells in the closure. But if you use this approach, then you can't change other TableViewDataSource delegates e.g. the section header.

Pull request with these improvements was merged into master branch. So I think we can expect this functionality in next version.

One more thing Custom Cell identifier should match Cell's class name.

Thanks @pilmen for contributing support for this!