swap issue

@tailwindcss/forms is causing this issue - maybe state this in the docs?
swap checkbox is visible
package.json
"tailwindcss": "^3.2.4"
"@tailwindcss/forms": "^0.4.1",
"@tailwindcss/typography": "^0.5.7",
"daisyui": "^2.42.1",

in build:
🌼 daisyUI components 2.43.0  https://daisyui.com
  ✔ Including:  base, components, 2 themes, utilities
  ❤ Support daisyUI:  https://opencollective.com/daisyui

tailwind.config.js
plugins: [
   require('@tailwindcss/forms'),
   require("@tailwindcss/typography"),
   require("daisyui")
 ],
 daisyui: {
   themes: ["fantasy","dark"],
 },

What @tailwindcss/forms does is precisely described in its repo:

All of the basic form elements you use will now have some simple default styles that are easy to override with utilities.

So when we install a plugin that says it applies style to all form elements by default, we can't expect otherwise.
This is not an issue. @tailwindcss/forms is simply doing its job.
If you really need @tailwindcss/forms alongside with daisyUI (which I doubt because both are doing the same job) consider using its strategy: 'class' config so it only applies style to the elements with specific class name (not all form elements)
Let me know if you have any questions.

I still have this problem

@aimehai Flowbite has a same class name .toggle as daisyUI's .toggle so using them together will mix the styles.
To avoid that when using daisyUI and Flowbite together you may want to add a prefix to only daisyUI class names. This avoids mixing the styles with the same class name coming from other CSS libraries.


USSL support

I tried adding in ussl.py and get the following error:
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
  File "ussl.py", line 36, in wrap_socket
RuntimeError: maximum recursion depth exceeded

The owner of umail suggesting "flattening the recursion", which I will try to do as a last ditch attempt.
Would it be a big job putting ussl in the last image you produced or will it exceed some memory requirement?
Thanks,
Dave

For SSL, please try firmware-20221203.

Using this image, uMail https://github.com/shawwwn/uMail and an example of sending the image https://github.com/shawwwn/uMail/issues/2 it worked ... first time!
Thanks for your effort again.

Finished


Adding plus (+) symbol does not decrypt

We're using this package to encrypt user data which includes First Name, Last Name, Email, and Phone. When adding a plus symbol/character to the data being encrypted, it seems to encrypt correctly but does not decrypt. E.g<EMAIL_ADDRESS>

I've just tested this and I can't find any evidence of this being the case. I have just pushed some test cases to github -- admittedly fairly weak test cases because I can't use the Crypt facade in a test case, but they do test the case of encrypting/decrypting strings with and without a + sign and it appears to work perfectly.
If you can PR a test case to the contrary then I will take a look.

Closing due to inactivity.


Get rid of new warning / potentially fix code

Potential dead code, the '?? !!' is gobbling up the result of the '&infix:<+&>' (line 32)

Oh heck, thanks lizmat!
Would you mind adding a test that would have broken for the old code?

I wouldn't know what to do, actually.  I just saw the warnings after a rakudo update and a recompilation of Cro and its dependencies, looked at the line that caused it, and fixed the line.
        Precompiling TinyFloats
WARNINGS for /Users/liz/Github/RAKU/Ecosystem-Archive/site#sources/01330D909025FEEB1D0D60B324BBA5201E13EC04 (TinyFloats):
Potential dead code, the '?? !!' is gobbling up the result of the '&infix:<+&>' (line 32)

Fair enough.  I've merged for now, and I'll try to figure out a reasonable test when my brain is actually working fully ....

After some testing and discussion on IRC, it appears this construct was already correctly interpreted by Rakudo for my intent, but that intent was not obvious from the original code from the point of view of the parser.  Thus the warning is valid and lizmat's silencing is correct, but there's no failing test to be added since Rakudo was already handling it correctly.
I'll close this after releasing a new version with warning silenced.

0.0.4 now uploaded to Zef.  Closing.


[Question] Updating Mailchimp when a user changes their email in Firebase

Apologies if this has already been addressed but I couldn't find an answer for this anywhere. If a user changes their email address in my firebase app I want to automatically update their email address in Mailchimp to reflect the change. I can't figure out how to make this work using the current extension.

Currently the plugin will only write to the "new" email address.
We'll need to have a look into how this can be achieved.

We need to make a small tweak to the code to prefer the "previous" email address for the hash identifier, but after that we can update the mergeFields mapping to point your email address to the "EMAIL" field and achieve email updates.

Resolved with #46


Add host platform to ByoHost CR info on registration

Signed-off-by: Shubham Bajpai<EMAIL_ADDRESS>What this PR does / why we need it:
This PR adds the host platform information (arch/os/distribution) to the ByoHost CR when the agent registers the host. Tested the same locally and this is what the CR would look like.
$ kubectl get byohosts host1 -oyaml
apiVersion: infrastructure.cluster.x-k8s.io/v1beta1
kind: ByoHost
metadata:
  creationTimestamp: "2022-04-25T05:52:54Z"
  generation: 1
  name: host1
  namespace: default
  resourceVersion: "169327"
  uid: 572acde9-2d80-446c-ab7a-260f71e8e8f4
spec: {}
status:
  conditions:
  - lastTransitionTime: "2022-04-25T05:52:55Z"
    reason: WaitingForMachineRefToBeAssigned
    severity: Info
    status: "False"
    type: K8sNodeBootstrapSucceeded
  hostinfo:
    architecture: arm64
    osimage: Ubuntu 20.04.4 LTS
    osname: linux
  network:
  ...

This PR also adds additional printers for the Byohost CRD and with those the output would look like this:
$ kubectl get byohost
NAME    OSNAME   OSIMAGE              ARCH
host1   linux    Ubuntu 20.04.4 LTS   amd64
host2   linux    Ubuntu 20.04.4 LTS   amd64

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #470
Additional information
The function added in this PR fetches information directly from files from the underneath operating system. Hence not sure how to add a test for the same.
Special notes for your reviewer

Codecov Report

Merging #516 (baaea08) into main (a3cfff7) will increase coverage by 0.20%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #516      +/-   ##
==========================================
+ Coverage   67.11%   67.32%   +0.20%
==========================================
  Files          22       22
  Lines        1721     1732      +11
==========================================
+ Hits         1155     1166      +11
  Misses        494      494
  Partials       72       72

Impacted Files
Coverage Δ

agent/main.go
15.48% <0.00%> (-0.42%)
:arrow_down:

agent/reconciler/host_reconciler.go
81.48% <0.00%> (+2.24%)
:arrow_up:


Empty Cluster

Hi
I get something strange from the structure. I generated STRUCTURE for K=4 to K=8.
But the results are the same. I mean, I found four reference populations for K=5 ... K=8.
I checked the meanQ files, and for K=8, four columns are zero for all individuals.
Thank you so much in advance

Hi,
I encountered the same problem, and I don't know if this issue has been resolved or not. The issue is the same as #65 :)


Session stays open even after bulk insert compeletes

What I observe is spid opened for data insert stays alive for days after data load completes when using bulk load, as a result when someone tries running select it gets stuck with blk by spid of bulk insert job.
I needed can provide screenshots of same
code:
val bulkCopyConfig = Config(Map(
"url"               -> "servername.eastus.cloudapp.azure.com",
"port"              -> "1",
"databaseName"      -> "PPPP",
"user"              -> "vvvvv",
"password"          -> "Password",
"databaseName"      -> "P360",
"dbTable"           -> tablename,
"bulkCopyBatchSize" -> "50000",
"bulkCopyTableLock" -> "true",
"bulkCopyTimeout"   -> "600"
))
data.bulkCopyToSqlDB(bulkCopyConfig)

As you would have noticed, this project is not being actively maintained. Instead, Apache Spark Connector for SQL Server and Azure SQL is now available, with support for Python and R bindings, an easier-to use interface to bulk insert data, and many other improvements. This repo will soon be archived (set to read-only). We encourage you to actively evaluate and use the new connector.
Unfortunately, this is a known issue which we have no plans to fix in this connector. Please check if you see similar issues with the newer connector and we can address it in that one.


Jest configuration - test environment value

I was just trying out this but i was struggling to render the css styles in my snapshot. After spending a few hours, i realized i had "testEnvironment": "node" set.
Wondering if this should be a documentation update or a warning that gets shown when the tests are run. I can try to contribute with this.

Hi! Thanks for the issue. Yeah, let's just add a note to the docs. Thanks!

Thanks @kentcdodds. I just forked this repo and ran "npm start validate" and got an error. Happy to update snapshot but wanted to check if that's ok.
 FAIL  src\custom-sheet.test.js
[test]   ● media queries
[test]
[test]     expect(value).toMatchSnapshot()
[test]
[test]     Received value does not match stored snapshot 1.
[test]
[test]     - Snapshot
[test]     + Received
[test]
[test]     @@ -4,20 +4,8 @@
[test]
[test]      .m-12 {
[test]        margin: 12px;
[test]      }
[test]
[test]     -@media (max-width: 641px) {
[test]     -  ._9gzisy {
[test]     -    font-size: 20px;
[test]     -  }
[test]     -}
[test]     -
[test]     -@media (max-width: 641px) {
[test]     -  ._d2w6i1 {
[test]     -    margin: 10px;
[test]     -  }
[test]     -}
[test]     -
[test]      <div
[test]        className="fs-24 m-12 _9gzisy _d2w6i1"
[test]      />
[test]
[test]       at Object.<anonymous> (src\custom-sheet.test.js:104:18)

Go ahead and update. We'll see if Travis does the same. Thanks!


Deprecate old protocols

All of those have better replacements.
Not sure "deprecated" is the correct wording.

Maybe "Retained for compatibility" or "Not recommended for new applications"?

Proposed language:
/*
 * This protocol is obsolete and will be removed in a future version. The
 * recommended replacement is <x>.
 */

Yeah, that's a more accurate statement. Updated.

Thanks!


Getting "Error: EBUSY: resource busy or locked, access '\.\pipe\nitro\worker-24144-2.sock' | Nuxt"

Environment
Nuxt - v3.7.4
Nitro - v2.6.3
Reproduction
I don't have a proper link to reproduce but using the specified version of nuxt in an app where you have multiple endpoints being called within the same timeframe will cause this error.
Describe the bug
When building the nuxt project, getting Error: EBUSY: resource busy or locked, access '\\.\pipe\nitro\worker-24144-2.sock' | Nuxt errors for random endpoints.
Additional context
No response
Logs
No response

please fix this. my all projects does not works

I am experiencing the same issue. Due to this problem, I am unable to proceed with parallel processing. This is a critical issue that needs to be resolved quickly.

The best way to solve this issue is to help making reproduction steps we cannot solve it without.

I am experiencing the same issue.   My system is Windows10
https://github.com/hefty/nitro-app.git  may help


K-FAC

Is it possible to use your implementation of K-FAC as an optimizer for other RL algorithms (e.g. DDPG) or is it especially designed for ACKTR?

Yes, it can be used. You just need to change the computations of Fisher to  https://github.com/ikostrikov/pytorch-a2c-ppo-acktr/blob/master/main.py#L167
In this case it's PG loss + regression loss, in case of DDPG it will be two regression losses.


I'll be:

Migrating the codebase to ES6 using Babel
Removing all the custom Grunt tasks for officially supported contrib plugins
Swapping out the custom styles compilation for PostCSS
Replacing Karma with Intern
Replacing Bower with NPM for frontend dependencies

Anyone wanna help or have ideas?

Follow along in the 2.0 branch

Should I just rename the project to Boilerplate and remove Backbone?

Closed for now, will update more in the master branch as I have time.


Create a nats-subscriber image

Each LFH instance can be both a NATS publisher and a NATS subscriber, so add a NATS subscriber image.

Issue moved to LinuxForHealth/connect #98 via ZenHub


Added back list of available files as annotations to block in BlackRockRawIO

The latest version of BlackrockIO using the RawIO API was missing a few annotations for the Block objects that contained information on available files and recording pauses. Using the already existing structure for annotations in RawIO I added the checks for those annotations like it was done in earlier versions of BlackrockIO.

Coverage decreased (-0.008%) to 48.975% when pulling 8c7f56e2ea852935fdc64b0f4a55534316d659fa on bjoern1001001:fix/block_annotations into 932d06a92aafff8cf3c312af6fea24bd008aba83 on NeuralEnsemble:master.

I guess we can merge.
OK ?

I think so, yes.


data Slowness Issue

Hi Team,
I am using your library while using this library very slow to load data for months on the scheduler. Could you please help me out?
Thanks

Hi there,
Sorry for the late reply. This repo has been deprecated for a while and I don't provide any support or accept any pull request anymore. Feel free to fork the project!
Hopefully you will find a solution to your problem


folding-cell:backSideColor not working

folding-cell:backSideColor not working

I just checked on multiple devices - all works fine.

make sure you have
xmlns:folding-cell="http://schemas.android.com/apk/res-auto"
and not
xmlns:folding-cell="http://schemas.android.com/tools"
in root


cmd/bosun: Shorten-only http proxy

This adds shortenProxy as option in bosun.toml to add a proxy only to requests out to googleapis' shortener api. The alternative is making use of the default http client's http.ProxyFromEnvironment but it results in all http calls to use it. That includes calls to OpenTSDB which isn't a something we want.

Silly question: what problem does this solve?

Our outbound proxies are on a different network than where OpentTSDB is. In our case we simply cannot use the same for both sets of calls. I also think going through a proxy to fetch data from OpenTSDB is generally unneeded in most deployments, unlike reaching out to googleapis.

yeah... Internet calls vs Intranet calls makes sense. I'd change the name to InternetProxy so it can be reused if we ever add any other APIs, but otherwise sounds fine to me.

How about this?

Thanks for those changes. I like it.

LGTM


sekiro heavy flickering

so i'm a windows user, only trying this out bc ive seen people report dxvk working on sekiro on windows with improved performance, needed a bump since my gpu is old/weak. downloaded 1.9.4 put it on sekiros folder and the game would boot but flicker heavily on the title screen and by heavy flickering i mean almost every letter of the title screen disappearing and reappearing rapidly, thought that was a shader loading situation closed n booted the game up again or tried to at least, wouldn't open until i deleted every dxvk file from the foulder. After that i bumped down to 1.8, not entirely sure if this is what caused the game to be able to open after the first time but still heavy flickering.
i tried messing with a bunch of things to troubleshoot was thinking it might be a driver issue or version of the game issue then i bumped all the way down to version 1.5.2 and the flickering was entirely gone, but the fps would drop to 1 and the game would freeze
am aware this application isn't really made for me but if possible and if any of this rung any bells i'd like to know what this is a symptom of? just the fact im running windows or a driver issue? maybe this doesn't work on every version of sekiro?

No idea which gpu/driver you're on but the game runs perfectly fine on Linux.


Concurrency Issues on poolmanager.py and _collections.py

Dear urllib3 developers,
After reading the source code, I have some questions on the thread-safety of the poolmanager.
This code:
def connection_from_pool_key(self, pool_key, request_context=None):
      """
      Get a :class:`ConnectionPool` based on the provided pool key.
      ``pool_key`` should be a namedtuple that only contains immutable
      objects. At a minimum it must have the ``scheme``, ``host``, and
      ``port`` fields.
      """
      with self.pools.lock:
          # If the scheme, host, or port doesn't match existing open
          # connections, open a new ConnectionPool.
          pool = self.pools.get(pool_key)
          if pool:
              return pool

          # Make a fresh ConnectionPool of the desired type
          scheme = request_context['scheme']
          host = request_context['host']
          port = request_context['port']
          pool = self._new_pool(scheme, host, port, request_context=request_context)
          self.pools[pool_key] = pool

      return pool

It seems that it only locks the pool operation. However, it does not lock between after the pool is created and before the connection is made. During this gap, the connection could be closed by the following code:
def __setitem__(self, key, value):
        evicted_value = _Null
        with self.lock:
            # Possibly evict the existing value of 'key'
            evicted_value = self._container.get(key, _Null)
            self._container[key] = value

            # If we didn't evict an existing value, we might have to evict the
            # least recently used item from the beginning of the container.
            if len(self._container) > self._maxsize:
                _key, evicted_value = self._container.popitem(last=False)

        if self.dispose_func and evicted_value is not _Null:
            self.dispose_func(evicted_value)

The RLock will be released after the connectionpool operation is completed. If the RLock is released, and another thread tries to operate on the connection pool - the existing connection could be evicted. Any call on the evicted connection could fail.
I also looked at the source code that calls the urlopen function, and it seems that it is called without any lock whatsoever. It is either a plain HTTPConnectionPool object or a HTTPSConnectionPool object.
It seems that after the new pool is created and added to the connection pool, no more thread-safety is guaranteed.
Is this an issue, or is it just me mis-interpreting the code?
Thanks,
Jinhua

It seems that it only locks the pool operation. However, it does not lock between after the pool is created and before the connection is made. During this gap, the connection could be closed by the following code:

This appears to be a possible risk. More generally it seems that objects contained in the LRU cache cannot safely be used ever: if they are in the process of being evicted that eviction may occur while they are being used for some other purpose.
The risk does appear to be vanishingly low: it requires that more than maxsize connection pools are in use at once in very rapid succession such that the pools are being created and evicted very swiftly. In particular, maxsize pools need to be created in between the interval of creating a pool and a connection being extracted from it (in _get_conn).
This does not appear to happen often. However, we should aim to mitigate it. The easiest way to handle it would be to hold the lock longer: however, the urlopen function in PoolManager does not have the appropriate abstraction level to do this. It may be that the best thing to do is to just increase maxsize to a level where triggering this would be entirely improbable.
As to the connection pool thread safety, there is also thread safety there. Note that the connection pool uses a LifoQueue object to store connections. These are thread-safe. Once a connection is extracted from there it "belongs" to the thread making the request, and will not be visible to any others until it is completely used. Setting attributes on the pool is not thread safe, but it is also not the preferred API to urllib3: the PoolManager is.


Incorrect time zone in struct tm returned from SOCI

Renaming of the develop branch #305, caused unintentional closure of the #190 pull request.
This task is to review and port #190 to the current master branch.

The following change to the test:
diff --git a/tests/common-tests.h b/tests/common-tests.h
index b3cfa10..333e042 100644
--- a/tests/common-tests.h
+++ b/tests/common-tests.h
@@ -508,24 +508,25 @@ class common_tests

     SECTION("Round trip works for date without time")
     {
-        std::tm nov15;
-        nov15.tm_year = 105;
-        nov15.tm_mon = 10;
-        nov15.tm_mday = 15;
-        nov15.tm_hour = 0;
-        nov15.tm_min = 0;
-        nov15.tm_sec = 0;
-
-        sql << "insert into soci_test(tm) values(:tm)", use(nov15);
-
-        std::tm t;
-        sql << "select tm from soci_test", into(t);
-        CHECK(t.tm_year == 105);
-        CHECK(t.tm_mon  == 10);
-        CHECK(t.tm_mday == 15);
-        CHECK(t.tm_hour == 0);
-        CHECK(t.tm_min  == 0);
-        CHECK(t.tm_sec  == 0);
+        std::time_t const t = std::time(NULL);
+
+        std::tm tm_in = *gmtime(&t);
+        tm_in.tm_hour = 0;
+        tm_in.tm_min = 0;
+        tm_in.tm_sec = 0;
+
+        sql << "insert into soci_test(tm) values(:tm)", use(tm_in);
+
+        std::tm tm_out;
+        sql << "select tm from soci_test", into(tm_out);
+        CHECK(tm_out.tm_year == tm_in.tm_year);
+        CHECK(tm_out.tm_mon  == tm_in.tm_mon);
+        CHECK(tm_out.tm_mday == tm_in.tm_mday);
+        CHECK(tm_out.tm_hour == 0);
+        CHECK(tm_out.tm_min  == 0);
+        CHECK(tm_out.tm_sec  == 0);
+
+        CHECK(tm_out.tm_gmtoff == tm_in.tm_gmtoff);
     }

     SECTION("Round trip works for date with time")

results in failures in the last comparison with SQLite3, MySQL, PostgreSQL and ODBC (and probably DB2 and Oracle as well) under Linux, where struct tm does have a tm_gmtoff field.
So we do appear to have a problem here, albeit one that doesn't manifest itself under Windows (without tm_gmtoff it doesn't matter whether mktime() or _mkgmtime() is used there).

Conclusion: the only reasonable thing to do currently is store all dates/times/timestamps in UTC and convert them to/from local time if needed at application level. So, finally, I don't think SOCI needs to be changed. It could support storing timestamps with time zones as well, but this is a completely different issue.


Probot failing to start with bad JWT expiration too far in the future

Bug Report
Current Behavior
Starting the bot with probot run ./dist/index.js throws an error:
ERROR probot: 'Expiration time' claim ('exp') is too far in the future

Expected behavior/code
Probot should start with the current configuration without erroring.
Environment

Probot version(s): 9.11.5
Node/npm version: Node v12.18.0/npm 6.14.4
OS: Ubuntu 20.04 - WSL 2.0 [Windows 10]

Possible Solution
This started happening 7/6/20. I should also add that I am using the @octokit/rest module as well for github api calls outside of the app which failed with the same message. I was generating my own JWT with an exp of 10 minutes but when I switched it to 9 minutes I no longer received this error.

Is this for github.com or for github enterprise?
Most likely the clocks are out of sync between the server your probot app is running and the github API you are connecting to

I'm running this locally and authenticating manually with @octokit/rest works fine but probot errors. This is github.com as well.

@gr2m You were right! The WSL was out of sync with the system time and required me to either do a sudo hwclock -s or a wsl --shutdown in powershell. After doing that time synced up and works fine.


ci: Securely allow fork repo PRs and unittest coverage

Description
This PR introduces a secure way of handling fork repo PRs with delegating the actual work to workflow_run workflows to get proper access for workflows as suggested in the below link:
https://securitylab.github.com/research/github-actions-preventing-pwn-requests/
Motivation and Context
We didn't handle required action permissions for PRs from fork repos resulted in unittest coverage not being published on PR as well as Close PR workflow failing to close PRs on pan.dev.
With the updated workflows unittests are successful and coverage results are commented on the PRs from fork repos.
How Has This Been Tested?
Tested on a fork repo and by creating another fork repo based on it.
Closing of pan.dev preview PRs are also tested.
⚠ Important Note
For coverage report to be commented on the PR from fork repos, the repository name in fork repo must match the original repository name. This happens from a limitation in coverage report action using Github API list PRs which doesn't allow filtering of fork repo PRs with a different repository name. See "head" filter on the Github API List pull requests call.
Types of changes
CI changes.
Checklist

[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes if appropriate.
[x] All new and existing tests passed.

:tada: This PR is included in version 0.3.4 :tada:
The release is available on PyPI and GitHub release

Posted by semantic-release bot


chore: remove unused res folder

@Vid201 Does it make sense to remove this?

@Vid201 Does it make sense to remove this?

Yeah, I think it does, as we are currently not supporting different chains. We can  reiterate on this after we plan to support for multiple chains/rollups (there will be probably some differences between them).


fix: restore Mason config timing for DAP startup (again)

Addresses regression of issue #554 fixed in #555 but later reintroduced in 8b5d48a and adds note to prevent regression from occurring for a third time.

Thanks for that!


(PUP-4890) Add code_id to the catalog

Adds a code_id accessor to the catalog, updates the api docs, schema, and tests.
Updates the compiler terminus' find method to add the code_id from the request to the catalog it returns.

@kylog @cprice404 @lutter @senior I hear you want a code_id?

:+1:


Implement prepend instrumentation for Delayed Job

Before contributing, please read our contributing guidelines and code of conduct.
Overview
Updated delayed job instrumentation to have both prepend and chain options hooked up and defaults to prepend
Related Github Issue
closes #572

Also, rebase or merge to clear out conflicts


Messaging: Self-hosted onboarding emails update

Context
As per https://github.com/PostHog/meta/issues/123 I'm looking at the onboarding email flows. One thing I noticed is that the self-hosted email onboarding flow is still set up exactly as it was before the sunset of K8s.
This shouldn't have been a big issue because we no longer support self-hosted and discourage users from trying it, which means few people are giving it a go. They are therefore hitting content which, while not technically incorrect, could lead them to believe SH is actively supported.
I'm still investigating where users may be coming to SH from, but we want to move those users to Cloud. So, an update is needed. Documenting it here for visibility, and to get any feedback.
Current flow
The current flow is a hangover from the old, old Cloud onboarding flow with some specific tweaks in the copy. Here's a description of the current state. Worth noting that it includes event ingested flow that we dropped from the Cloud emails for being unreliable.

When a user signs up with a valid email address, we send them the first welcome email after a 1 hour delay.
We check if an event has been ingested.

If yes: Do nothing.
If no: We send an email directing them to the docs, and advising them to invite an engineer, then wait 1 day and until a weekday.

We check if an event has been ingested, again.

If yes: Go to next step.
If no: We send an email directing them to the Slack and the Community, then wait 1 day and until a weekday.

We check if an event has been ingested, a penultimate time.

If yes: Go to next step.
If no: We send an email directing them to book a demo.

We check if an event has been ingested, a final time.

If yes: Go to next step.
If no: Do nothing until an event is ingested, then go to next step.

We wait 1 day and until a weekday, then send an email which explains what an AARRR dashboard is and directs to a tutorial.
We wait 1 day and until a weekday, then send them an email upselling them to session replay which directs them to the product page on the site.
We wait 1 day and until a weekday, then send them an email upselling them to feature flags which directs them to the product page on the site.
We add the completed_onboarding_email property as true

Proposed flow
We should change this flow to be more similar to the current email flow for open source users, but with a greater emphasis put on the lack of support. That would look like this:

When a user signs up with a valid email address, we send them the first welcome email after a 1 hour delay. We are very clear that support is not offered and direct them to migration guides.
We wait for 1 week and for a week day, then send an email advising them to migrate to Cloud in order to continue scaling and benefit from support.
We wait for 2 weeks and for a week day, then send an email advising them to migrate to Cloud in order to benefit from the latest features, such as surveys and performance monitoring.

Draft messaging.
Email 1

Email 2

Email 3

I've pushed this live immediately, as there are users in the funnels who would be getting incorrect information as it is. Happy to take any feedback still, however.

Do people get this messaging if they've set up the FOSS docker-based version? If so I think the first email isn't quite appropriate. Self-host4ed docker deployments won't be using kubernetes, and we shouldn't be scaring them away from self-hosted so much as enticing them to try cloud.

No, there's a separate flow for that. The emails are similar, but they're tailored to open source and the tone is a little different. Less "You should really upgrade because K8s is dead" and more "Hope you're having fun, and did you know there are extra features on Cloud?"

This is now launched and seems to be going well, so...


change file location

@anhmanh1011 Please provide us with:

the school official website URL
the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course

@anhmanh1011 You might miss my previous comment. Please react.

@anhmanh1011 I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!


Sample program Runnig Failed

Hi,
I have installed sipster successfully and my pjsip is installed at default location(/usr/local/).
I have followed your earlier guidelines to install sipster.
Thanks a lot for that.
But at the time of running sample program given by you I am facing problem.
I am getting error like this:
module.js:460
return process.dlopen(module, path._makeLong(filename));
^
Error: libpjsua2.so.2: cannot open shared object file: No such file or directory
at Error (native)
at Object.Module._extensions..node (module.js:460:18)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:313:12)
at Module.require (module.js:366:17)
at require (module.js:385:17)
at Object. (/home/root/test/node_modules/sipster/lib/main.js:4:13)
at Module._compile (module.js:435:26)
at Object.Module._extensions..js (module.js:442:10)
at Module.load (module.js:356:32)
But I have checked that libpjsua2.so.2 file is available at /usr/local/lib.
Can you please help me regarding this?

You may try manually updating the ld.so.cache via ldconfig.
If it still can't find it, you should verify /usr/local/lib is in your shared library search path. You can check that by checking if this outputs /usr/local/lib: ldconfig -v 2>/dev/null | grep -v ^$'\t' | grep -iF "/usr/local/lib"

Thank you very much for your earliest response.
Thanks again your solution worked for me.

Hi Brian,
Your solution worked for me.
We want to develop SIP server using NodeJS for that we want to use PJSIP as stack.
So, I have already worked on PJSIP for building SIP server but our SIP server is based on C.
So we want to work on NodeJS based SIP server.  For that we need your help for accessing low level pjsip api to access from Node.
So, will you be interested to help us regarding this ?
If you are interested please share your mail id so that we can discuss more.
Best regards,
Dhiraj

#ldconfig

``
export LD_LIBRARY_PATH="/usr/local/lib"
Did the trick on Ubuntu 16.04


Keycloak error on installation on Kind

Describe the bug: (a clear and concise description of what the bug is)
Otomi fails to install because Keycloak chart fails
To Reproduce
Steps to reproduce the behavior:

Install a Kind cluster with 1 master and 3 workers, with Cilium CNI and MetalLB
Install Otomi with the following values.yaml

cluster:
  k8sVersion: "1.25"
  name: "kind-kind"
  provider: "custom"
otomi:
  hasExternalDNS: true
  adminPassword: EcWu^TotM66#mFl%*Da7x%KQ
apps:
  metrics-server:
    enabled: true
    _rawValues:
      extraArgs:
        kubelet-preferred-address-types: InternalIP
        kubelet-insecure-tls: true

Otomi fails at bringing up keycloack-0 pod (database pod comes us fine).

Expected behavior: (a clear and concise description of what you expected to happen)
Screenshots: (if applicable, add screenshots to help explain your problem)
keycloak-0 keycloak # A fatal error has been detected by the Java Runtime Environment:
keycloak-0 keycloak #
keycloak-0 keycloak #  SIGSEGV (0xb) at pc=0x00007ffffe497026, pid=89, tid=143
keycloak-0 keycloak #
keycloak-0 keycloak # JRE version: OpenJDK Runtime Environment 18.9 (11.0.13+8) (build 11.0.13+8-LTS)
keycloak-0 keycloak # Java VM: OpenJDK 64-Bit Server VM 18.9 (11.0.13+8-LTS, mixed mode, sharing, tiered, compressed oops, g1 gc, linux-amd64)
keycloak-0 keycloak # Problematic frame:
keycloak-0 keycloak # V  [libjvm.so+0x7d0026]  G1ParScanThreadState::copy_to_survivor_space(InCSetState, oopDesc*, markOopDesc*)+0x56
keycloak-0 keycloak #
keycloak-0 keycloak # Core dump will be written. Default location: /opt/jboss/keycloak/core
keycloak-0 keycloak #
keycloak-0 keycloak # An error report file with more information is saved as:
keycloak-0 keycloak # /opt/jboss/keycloak/hs_err_pid89.log
keycloak-0 keycloak #
keycloak-0 keycloak # If you would like to submit a bug report, please visit:
keycloak-0 keycloak #   https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20Linux%208&component=java-11-openjdk
keycloak-0 keycloak #
keycloak-0 keycloak /opt/jboss/tools/databases/change-database.sh: line 7:    89 Aborted                 (core dumped) bin/jboss-cli.sh --file=/opt/jboss/tools/cli/databases/$DB_VENDOR/standalone-configuration.cli

Cluster(s):
kind on Mac M1max (64gb RAM) Docker Desktop with 10 vCPU, 32gb ram and 100GB of disk space
Versions: (seen in console's /settings)

Core Version 0.55.1

Desktop: (if relevant)

OS:  macOS 14.0

Additional context: (add any other context about the problem here)
Full keycloak error log is here: https://pastebin.com/ACByrkjL

Hi @ams0
It appears that you are utilizing a machine equipped with an ARM CPU. Keycloak has introduced ARM support starting from version 18. Currently, Otomi is running on version 15.
We are actively engaged in the process of upgrading Keycloak and anticipate completing it in the near future. I will leave this ticket open until the upgrade is successfully completed.
Best regards,

Can I submit a PR? This being an open source project :) can you point me in the right direction?

Yes, of course you help will be very much appreciated :)
In order to submit PR you need to fork this repo and submit PR from the fork.
There is also documentation for developers: https://github.com/redkubes/otomi-core/blob/main/docs/README.md
By the way, the support of the new keycloak version is almost there.
You could actually try to deploy Otomi by using the kc_upgrade image tag and the following values from otomi helm chart.
cluster:
  name: 'dev'
  k8sContext: notUsed
otomi:
  version: 'kc_upgrade'

The ARM compatibility issue is also here #1217.


Is it compatible with cakephp 4.4.7 ?

I am trying to implement the plugin on cake version 4.4.7 and I found several incompatibilities.
Does this version is compatible with recent cakephp ?
Thank you

Yes, it is. I am using it on latest Cake - see also running tests.
Whats the issue - you need to be a bit more specific here.

AHA, looks like CakePHP released a BC break by not having those interfaces inherit from each other?

Hi Mark! that's the error!!!

In the code there is the "old fashion" $this->loadModel as well, which seems deprecated, as far as I know

Deprecation is not a BC issue, though.

After https://github.com/cakephp/cakephp/commit/88a4f70d6339e50daa2b382b8af1c1be6b976388 this will be released as fix in 4.4.8 :)

Thank you very much Mark!


#965 change dapr startup from daprd to dapr CLI

This PR:

replaces the daprd startup with dapr CLI in order to have the dapr dashboard detect dapr services started with Tye as described in #965

@jkotalik
 tye --version
0.7.0-alpha.21153.4+528c743efc48eb0c5aa18c9272fac5235f38b0ed

Hm, for some reason your change didn't make it to a public build. I'll look into it.

In the mean time, you can also build from source: https://github.com/dotnet/tye/blob/master/docs/developer_guide.md#using-local-builds

@mmisztal1980 it's available now.

@jkotalik fooling around with the locally-built version, trying to run one of the samples (pub-sub) to verify that the change is working, however the services are in a crash-loop.
I've stopped and removed all containers prior to executing tye run  - any hints how can I diagnose what's going on?

found something, working on it

I've managed to fix the crash-loop, the tye run local environment is stable, however the dapr dashboard is empty.

@rynowak any hints?
[22:49:34 INF] Executing application from D:\Checkout\tye\samples\dapr\pub-sub\tye.yaml
[22:49:35 INF] Dashboard running on http://<IP_ADDRESS>:8000
[22:49:36 INF] Docker image redis already installed
[22:49:36 INF] Docker image daprio/dapr already installed
[22:49:36 INF] Creating docker network tye_network_3547df07-4
[22:49:36 INF] Running docker command network create --driver bridge tye_network_3547df07-4
[22:49:37 INF] Running image redis for redis_241d5926-b
[22:49:37 INF] Running image daprio/dapr for placement_7e2fa832-d
[22:49:37 INF] Building projects
[22:49:40 INF] Running container redis_241d5926-b with ID afe8f1fa4f8a
[22:49:40 INF] Running docker command network connect tye_network_3547df07-4 redis_241d5926-b --alias redis
[22:49:40 INF] Running container store-proxy_03d2042d-c with ID 9a20937e6988
[22:49:40 INF] Running docker command network connect tye_network_3547df07-4 store-proxy_03d2042d-c --alias store
[22:49:41 INF] Launching service products_7bed6681-e: D:\Checkout\tye\samples\dapr\pub-sub\products\bin\Debug\netcoreapp3.1\products.exe
[22:49:41 INF] Launching service orders_f558bac5-9: D:\Checkout\tye\samples\dapr\pub-sub\orders\bin\Debug\netcoreapp3.1\orders.exe
[22:49:41 INF] Launching service products-dapr_cb5ca785-4: C:/dapr/dapr.exe run --app-id products --app-port 52296 --dapr-grpc-port 52303 --dapr-http-port 52304 --placement-host-address localhost:52293 --log-level debug --components-path ./components/
[22:49:41 INF] Launching service store_48f71d31-b: D:\Checkout\tye\samples\dapr\pub-sub\store\bin\Debug\netcoreapp3.1\store.exe
[22:49:41 INF] Launching service store-dapr_95baa976-8: C:/dapr/dapr.exe run --app-id store --app-port 52298 --dapr-grpc-port 52306 --dapr-http-port 52307 --placement-host-address localhost:52293 --log-level debug --components-path ./components/
[22:49:41 INF] Launching service orders-dapr_de2f8f43-7: C:/dapr/dapr.exe run --app-id orders --app-port 52294 --dapr-grpc-port 52300 --dapr-http-port 52301 --placement-host-address localhost:52293 --log-level debug --components-path ./components/
[22:49:41 INF] products_7bed6681-e running on process id 21844 bound to http://localhost:52296, https://localhost:52297
[22:49:41 INF] Replica products_7bed6681-e is moving to a ready state
[22:49:41 INF] Running container orders-proxy_16a2a8b8-9 with ID 419f2d1b761e
[22:49:41 INF] Running docker command network connect tye_network_3547df07-4 orders-proxy_16a2a8b8-9 --alias orders
[22:49:41 INF] orders_f558bac5-9 running on process id 26872 bound to http://localhost:52294, https://localhost:52295
[22:49:41 INF] Replica orders_f558bac5-9 is moving to a ready state
[22:49:41 INF] products-dapr_cb5ca785-4 running on process id 1876 bound to https://localhost:52303, http://localhost:52304, http://localhost:52305
[22:49:41 INF] Replica products-dapr_cb5ca785-4 is moving to a ready state
[22:49:41 INF] store_48f71d31-b running on process id 12940 bound to http://localhost:52298, https://localhost:52299
[22:49:41 INF] store-dapr_95baa976-8 running on process id 13840 bound to https://localhost:52306, http://localhost:52307, http://localhost:52308
[22:49:41 INF] orders-dapr_de2f8f43-7 running on process id 18616 bound to https://localhost:52300, http://localhost:52301, http://localhost:52302
[22:49:41 INF] Replica store_48f71d31-b is moving to a ready state
[22:49:41 INF] Replica store-dapr_95baa976-8 is moving to a ready state
[22:49:41 INF] Replica orders-dapr_de2f8f43-7 is moving to a ready state
[22:49:41 INF] Selected process 21844.
[22:49:41 INF] Selected process 26872.
[22:49:41 INF] Listening for event pipe events for products_7bed6681-e on process id 21844
[22:49:41 INF] Listening for event pipe events for orders_f558bac5-9 on process id 26872
[22:49:42 INF] Selected process 12940.
[22:49:42 INF] Listening for event pipe events for store_48f71d31-b on process id 12940
[22:49:44 INF] Replica redis_241d5926-b is moving to a ready state
[22:49:44 INF] Collecting docker logs for redis_241d5926-b.
[22:49:44 INF] Running container products-proxy_6431a91d-6 with ID 52ee2aef02c3
[22:49:44 INF] Running docker command network connect tye_network_3547df07-4 products-proxy_6431a91d-6 --alias products
[22:49:44 INF] Running container orders-dapr-proxy_76f612ac-3 with ID 00e30e026355
[22:49:44 INF] Running docker command network connect tye_network_3547df07-4 orders-dapr-proxy_76f612ac-3 --alias orders-dapr
[22:49:44 INF] Running container store-dapr-proxy_06ff3263-b with ID b4dd349d5c7b
[22:49:44 INF] Running docker command network connect tye_network_3547df07-4 store-dapr-proxy_06ff3263-b --alias store-dapr
[22:49:44 INF] Collecting docker logs for store-proxy_03d2042d-c.
[22:49:44 INF] Running container placement_7e2fa832-d with ID 3b7dd7d3e5c4
[22:49:44 INF] Running docker command network connect tye_network_3547df07-4 placement_7e2fa832-d --alias placement
[22:49:44 INF] Running container products-dapr-proxy_bb4be1f3-9 with ID 6f5fd5281bf6
[22:49:44 INF] Running docker command network connect tye_network_3547df07-4 products-dapr-proxy_bb4be1f3-9 --alias products-dapr
[22:49:44 INF] Collecting docker logs for orders-proxy_16a2a8b8-9.
[22:49:45 INF] Collecting docker logs for products-proxy_6431a91d-6.
[22:49:45 INF] Collecting docker logs for orders-dapr-proxy_76f612ac-3.
[22:49:45 INF] Collecting docker logs for store-dapr-proxy_06ff3263-b.
[22:49:45 INF] Replica placement_7e2fa832-d is moving to a ready state
[22:49:45 INF] Collecting docker logs for placement_7e2fa832-d.
[22:49:45 INF] Collecting docker logs for products-dapr-proxy_bb4be1f3-9.
[22:49:46 INF] Failed to collect diagnostics for products-dapr_cb5ca785-4 after 00:00:05.
[22:49:46 INF] Failed to collect diagnostics for store-dapr_95baa976-8 after 00:00:05.
[22:49:46 INF] Failed to collect diagnostics for orders-dapr_de2f8f43-7 after 00:00:05.


Is priority (salience) working properly?

Hi @jruizgit, I've been playing with rule priority levels, and in the following example is not behaving the way I would expect. The conditions for both rule1 and rule2 are met after the initial fact is asserted, and so I would expect the one with the lower priority value (rule2) to fire, but rule1 is triggered instead. Assuming this isn't a bug, would you mind explaining what is happening so that I can better understand the logic around rule priority/execution?
from durable.lang import *

with ruleset('ex3'):

    @when_all(
        pri(2),
        c.fact1 << m.toggle == True,
        none(+m.cancel)
    )
    def rule1(c):
        c.assert_fact({"cancel":True})
        print("rule1 fired")

    @when_all(
        pri(1),
        none(+m.cancel)
    )
    def rule2(c):
        c.assert_fact({"cancel":True})
        print("rule2 fired")

    @when_start
    def start(host):
        x = host.assert_fact("ex3",{"toggle":True})

run_all()

Output:
 * Running on http://<IP_ADDRESS>:5000/ (Press CTRL+C to quit)
rule1 fired

Many thanks,
Mac

Hi @macroach, I took a quick look at the test case. I think salience is working OK. The problem is the none expression standalone is not triggering the rule. Let me debug and I will report back on my findings.

The current behavior of none: none requires data to reason about no data. The code below illustrates the point: With the first assert_fact("ex3",{"cancel":True}) the engine blocks both rules. With the retract_fact("ex3",{"cancel":True}) the engine unblocks both rules honoring the rule priority.
from durable.lang import *

with ruleset('ex3'):

    @when_all(
        pri(2),
        c.fact1 << m.toggle == True,
        none(+m.cancel)
    )
    def rule1(c):
        c.assert_fact({"cancel":True})
        print("rule1 fired")

    @when_all(
        pri(1),
        none(+m.cancel)
    )
    def rule2(c):
        c.assert_fact({"cancel":True})
        print("rule2 fired")

    @when_start
    def start(host):
        host.assert_fact("ex3",{"cancel":True})
        host.assert_fact("ex3",{"toggle":True})
        host.retract_fact("ex3",{"cancel":True})

run_all()

Gotcha - thanks so much for looking into this and responding so quickly, @jruizgit !
Is this the intended behavior? (And if it is, is it documented somewhere? If so, I'll go ahead and mark the issue as closed.)
Thanks again!
Mac

Yes, it is the intended behavior of none. I have just added a note to the docs:
https://github.com/jruizgit/rules/blob/master/docs/py/reference.md#lack-of-information
Thanks,

Thanks!


Proposed WW-5068 change

Proposed WW-5068 change.
Proposed list of library version updates:
cdi-api 1.0-SP4 -> 1.2
weld-core 1.0.1-SP4 -> 2.2.16.SP1
weld-se 1.0.1-Final -> weld-se-core 2.2.16.SP1
htmlunit 2.27.0 and 2.37.0 -> 2.39.0
slf4j-api 1.7.29 -> 1.7.30
slf4j-simple 1.7.29 -> 1.7.30
log4j2 2.12.1 - > 2.13.1
jackson 2.10.1 -> 2.10.3
ognl 3.2.12 -> 3.2.14
asm 7.2 -> 7.3.1
spring 4.3.25.RELEASE -> 4.3.26.RELEASE
fluido-skin 1.8 -> 1.9
freemarker 2.3.28 -> 2.3.30
org.apache.felix.main 4.6.1 -> 6.0.3
velocity 2.1 -> 2.2
junit 4.12 -> 4.13
easymock 3.5.1 -> 4.2
javax.el 3.0.1-b10 -> 3.0.1-b11
jstl 1.1.2 -> 1.2
tomcat-jasper 8.5.37 -> 8.5.53
tomcat-api 8.5.37 -> 8.5.53
tomcat-juli 8.5.37 -> 8.5.53
commons-lang3 3.9 -> 3.10
assertj-core 2.9.1 -> 3.15.0
mockito-core 2.23.0 -> 3.3.3   (required exclusion for objenesis)
testng 5.14.10 -> 7.1.0
juneau-marshall 7.2.2 -> 8.1.3
validation-api 1.1.0.Final -> 2.0.1.Final
hibernate-validator 5.4.3.Final -> 6.1.2.Final
jaxb-impl 2.3.1 -> 2.3.2

Proposed list of Maven plugin version updates:
maven-project-info-reports-plugin 2.7 -> 3.0.0
updateimpact-maven-plugin 1.0.10 -> 1.0.12
maven-surefire-plugin 2.22.2 -> 3.0.0-M4
jacoco-maven-plugin 0.8.4 - > 0.8.5
maven-war-plugin 3.2.2 -> 3.2.3
maven-bundle-plugin 3.5.0 -> 4.2.1
maven-dependency-plugin 3.1.1 -> 3.1.2
dependency-check-maven 5.2.4 -> 5.3.2
maven-enforcer-plugin 3.0.0-M2 -> 3.0.0-M3
maven-failsafe-plugin 2.22.2 -> 3.0.0-M4
maven-site-plugin 3.8.2 -> 3.9.0
doxia-core 1.9 -> 1.9.1
doxia-module-markdown 1.9 -> 1.9.1

Coverage remained the same at 49.181% when pulling 9d0a6a80adf433c80ba1289a81277beb75f0cf77 on JCgH4164838Gh792C124B5:WW-5068-26x into e8ce2c756f0a9015072216e1c366f4b29ac867cf on apache:master.

Hello Apache Struts Team.
This PR is pretty straightforward, but any of the changes can be modified if needed after review and discussion.
Local builds with JDK8 completed successfully, but with JDK11 locally I experienced test failures in DateRangeValidatorTest and VisitorFieldValidatorTest of struts-core (could be a local build issue with my environment but I wanted to note it in case it turns out to be significant in the future).
The Travis CI builds for JDK8/9/11 against the PR all completed successfully, though.
Let me know if any additional changes could be considered.

Nice 👏 , LGTM 👍


Package conflict in Anaconda3

On Ubuntu-14.04 LTS 32-bit, installing reprozip in Anaconda3 leads to a package conflict with python 3.4:
स्वक्ष@ilak:~/anaconda3$ conda install -c https://conda.anaconda.org/vida-nyu reprounzip
Fetching package metadata: ......
Solving package specifications: ..........
Error: Unsatisfiable package specifications.
Generating hint:
[      COMPLETE      ]|#######################################################################################################################################| 100%

Hint: the following packages conflict with each other:
  - reprounzip
  - python 3.4*

Use 'conda info reprounzip' etc. to see the dependencies for each package.

स्वक्ष@ilak:~/anaconda3$ conda info reprounzip
Fetching package metadata: ....
Error: No packages found in current linux-32 channels matching: reprounzip

Thanks.

Indeed, the Conda package lists a dependency on "python", and it looks like this means it needs Python 2.7. Anaconda environments can only have one Python version, so this conflicts with Python 3.4.
I don't know if there is a way to create "universal" packages, in the worse case I can make two versions since conda has a proper dependency solver. In the meantime, you can create a Python 2 environment to install reprounzip in (or install reprounzip using pip, or conda skeleton).
Thanks for reporting this, I am looking into it!

On Sun, Oct 25, 2015 at 5:17 AM, Remi Rampin<EMAIL_ADDRESS>wrote:

Indeed, the Conda package lists a dependency on "python", and it looks like this means it needs Python 2.7. Anaconda environments can only have one Python version, so this conflicts with Python 3.4.
I don't know if there is a way to create "universal" packages, in the worse case I can make two versions since conda has a proper dependency solver. In the meantime, you can create a Python 2 environment to install reprounzip in (or install reprounzip using pip, or conda skeleton).

IIRC, the anaconda installation for 2.x and 3.4 have been split?
Earlier I could create a distinct 3.x version with a simple flag but
now the installers have been split I suppose. I suppose it makes sense
as the dep management will be easier, so for your usecase, you may
have to create a new version for 3.x versions.

Thanks for reporting this, I am looking into it!

Thanks for writing this!
SVAKSHA ॥  http://about.me/svaksha  ॥

The Anaconda installation is not actually split, in that you can use Conda to change your version of Python; but every other package that is part of Anaconda would conflict. You can however create environments with a different version of Python.
It looks like Conda packages are only linked against one version of Python, that is chosen with the --python flag of conda build; even changing the dependencies in meta.yaml doesn't help since the directory name depends on the version (e.g. lib/python3.5/site-package/). I'm going to change my build scripts to build packages for both 2.7 and 3.2+.

I have built packages for Python 3.5 for all platforms (except Windows, which is Python 3.4). You should be able to install and use ReproZip in Anaconda environments with Python 3.
Let me know if something goes wrong.

On Tue, Oct 27, 2015 at 12:47 AM, Remi Rampin<EMAIL_ADDRESS>wrote:

I have built packages for Python 3.5 for all platforms (except Windows, which is Python 3.4). You should be able to install and use ReproZip in Anaconda environments with Python 3.

Thank you Remi. I shall try them out soon.
SVAKSHA ॥  http://about.me/svaksha  ॥


Introduce  sharing before the group work

Introducing what is  sharing before the group work might help the learners in the discussion. Some thing like sharing is not emailing a copy of the code or file sharing  to some in the context of current talk.

This is done


Roles won't update pre13

Dear Aberdeener,
The group sync on the discord roles currently has some issues when you change your rank in the game.
Your roles get set on the forums to the correct rank but on discord  it only removes rank and doesn't add them.
I had contact with Derkades he said i should create an issue for this on github.
Can you look in to this?
Kind regards!

The website keeps sending /roleChange requests repeatedly: https://paste.rkslot.nl/asefipoyoc.txt
A few issues with this:

The website keeps sending role remove requests, even though it has already send those requests before.
The website makes a request to /roleChange individually for every role, instead of making a request with all roles to add or remove. This makes it very slow.

I have also noticed that when changing a role on the website there will be requests being sent to the bot:
link               | [Grizzly-worker(4)] INFO RoleChange endpoint - Role change request from website processed successfully.
link               | [Grizzly-worker(5)] INFO RoleChange endpoint - Role change request from website processed successfully.
link               | [Grizzly-worker(6)] INFO RoleChange endpoint - Role change request from website processed successfully.
link               | [Grizzly-worker(7)] INFO RoleChange endpoint - Role change request from website processed successfully.
link               | [Grizzly-worker(8)] INFO RoleChange endpoint - Role change request from website processed successfully.
link               | [Grizzly-worker(9)] INFO RoleChange endpoint - Role change request from website processed successfully.
link               | [Grizzly-worker(10)] INFO RoleChange endpoint - Role change request from website processed successfully.
link               | [Grizzly-worker(11)] INFO RoleChange endpoint - Role change request from website processed successfully.
link               | [Grizzly-worker(12)] INFO RoleChange endpoint - Role change request from website processed successfully.
link               | [Grizzly-worker(13)] INFO RoleChange endpoint - Role change request from website processed successfully.
link               | [Grizzly-worker(14)] INFO RoleChange endpoint - Role change request from website processed successfully.

but wont actually change anything on discord (at least in my case) not even adding or removing any role, but adding and removing roles on discord instantly syncs to the site with no issue


Set to the most recent previous Friday if the occurrence is on Saturday of Sunday

I'm wondering if there's a way to schedule the following: monthly on 15th and the last day, if the day is a weekend (Saturday or Sunday), set to the Friday before that day.

Unfortunately no, not currently. This should be doable with BYSETPOS, have a look at #289 and #349.


fix(glide): Pin the pflag, go-homedir, and cobra deps to a specific sha

This PR locks down the versions for pflag, go-homedir, and cobra to their respective shas that are currently in the glide.lock file on master. This PR is a duplicate of a commit I currently have in #709 but we should do this before we cut the release of acs-engine.

This change is

@jchauncey,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Why is this needed if the shas are already specified in the lock file?

Per https://github.com/Masterminds/glide

and glide install will install the versions listed in the glide.lock file

What benefit does it provide to lock them this hard in the glide file? This means we won't get security fixes automatically by just executing glide up, for example.

First if the glide.yaml changes the lock file is updated and it will pull down the latest changes from that repo. So because the original yaml file did not have any versions/release set it would always update the version to whatever the head of master is.
These 3 repos do not cut tagged releases so you can have 1 thing or the other. You either pin it to a sha or you are open to the world and accept that you may get an update that was not intended.

I don't understand at all. Can we back up? What is the goal of this PR?
Simply running glide install should never change the revisions installed. AFAICT based on using glide and reading the docs, this only makes it harder for us to be able to run glide up and get security updates, etc.

In my other PR you brought up the fact that the lock file included a new version and that should not have happened. So the only way to stop that from happening is to pin these dependencies to a sha (since they do not do github releases). That way we can pull in new dependencies without unattended consequences.

If you ran glide install and it rewrote your lock file, then we should file a bug on glide, because it explicitly says that should not happen (and I've never personally had it happen). There's no chance you ran glide up?

I ran a glide get that rewrote the lock file

Ugh. I wonder if it's similar to this bug: https://github.com/Masterminds/glide/issues/252. When the get runs it maybe triggers the same up logic. I still think we should file a bug on glide for that weird behavior, but I understand why the PR is needed. I'd be curious to know, if you had put the restrictive SHA into the glide.yaml file and then ran glide get <whatever> does it respect the SHA specified in glide.yaml? I guess it must...
Anyway, sorry for all the questions and thanks for helping me understand.
LGTM to me.

yes if version restrictions are in place it will honor them to the best of its ability. The more promiscuous version constraints for the other deps may mean that they are updated as well though.

@acs-bot test this please

Thanks @jchauncey, can you rebase and we'll merge this in ASAP?

@jchauncey Will merge right after CI passes. Ping me if I forget!

(or go ahead and merge yourself, PR is approved)

I dont have access to merge in this repo

@acs-bot test this please


FEATURE: Enhanced Trace Skipping

Make sure to skip dyadic functions that have a scalar on the right or left.


Add Async Support

Add async support. There are still a few outstanding gaps and potential issues which are tracked in async_checklist.md. We'll wait to release 0.8 for those to be resolved.
Addresses #13

New Rust 1.82 lint https://github.com/rust-lang/rust/pull/129207
It is allow by default - our CI is causing it to be an error when running rustdoc.
error: elided lifetime has a name
Error:    --> butane_core/src/db/dummy.rs:123:59
    |
123 |     async fn transaction(&mut self) -> Result<Transaction<'_>> {
    |                          -                                ^^ this elided lifetime gets resolved as `'life0`
    |                          |
    |                          lifetime `'life0` declared here
    |
    = note: `-D elided-named-lifetimes` implied by `-D warnings`
    = help: to override `-D warnings` add `#[allow(elided_named_lifetimes)]`

error: elided lifetime has a name
Error:    --> butane_core/src/db/pg.rs:113:59
    |
113 |     async fn transaction(&mut self) -> Result<Transaction<'_>> {
    |                          -                                ^^ this elided lifetime gets resolved as `'life0`
    |                          |
    |                          lifetime `'life0` declared here

error: elided lifetime has a name
Error:   --> butane_core/src/db/mod.rs:94:59
   |
94 |     async fn transaction(&mut self) -> Result<Transaction<'_>>;
   |                          -                                ^^ this elided lifetime gets resolved as `'life0`
   |                          |
   |                          lifetime `'life0` declared here

error: elided lifetime has a name
Error:    --> butane_core/src/db/mod.rs:116:47
    |
116 |     async fn transaction(&mut self) -> Result<Transaction> {
    |                          -                    ^^^^^^^^^^^ this elided lifetime gets resolved as `'life0`
    |                          |
    |                          lifetime `'life0` declared here

error: elided lifetime has a name
Error:    --> butane_core/src/db/mod.rs:289:47
    |
289 |     async fn transaction(&mut self) -> Result<Transaction> {
    |                          -                    ^^^^^^^^^^^ this elided lifetime gets resolved as `'life0`
    |                          |
    |                          lifetime `'life0` declared here

error: elided lifetime has a name
Error:    --> butane_core/src/fkey.rs:100:74
    |
100 |     async fn load<'a>(&'a self, conn: &impl ConnectionMethods) -> Result<&T>
    |                   -- lifetime `'a` declared here                         ^ this elided lifetime gets resolved as `'a`

error: elided lifetime has a name
Error:    --> butane_core/src/fkey.rs:106:79
    |
106 |     async fn load<'a>(&'a self, conn: &impl ConnectionMethodsAsync) -> Result<&T>
    |                   -- lifetime `'a` declared here                              ^ this elided lifetime gets resolved as `'a`

error: elided lifetime has a name
Error:    --> butane_core/src/fkey.rs:123:68
    |
123 |     fn load<'a>(&'a self, conn: &impl ConnectionMethods) -> Result<&T>
    |             -- lifetime `'a` declared here                         ^ this elided lifetime gets resolved as `'a`

IMO we should ignore this warning in the rustdoc step if it cant be easily fixed.


2 axioms for upcoming release

This is consistent with OBI's use of 'life cycle stage' in the axiom for this term.

ID
label
subclass axiom

EUPATH:0000528
gametocyte detection assay
realizes some ('measurand role' and ('role of' some ('participates in' some 'gametocyte stage')))

EUPATH:0000796
sporozoite detection assay
realizes some ('measurand role' and ('role of' some ('participates in' some 'sporozoite stage')))

Or should these be submitted to OBI?

submitting gametocyte assay to OBI but don't need sporozoite assay.


Add new practice exercise: killer-sudoku-helper

Getting Started
This task requires the implementation of a new practice exercise. If you have not yet contributed to concept exercises before, this task requires some upfront reading to acquire the necessary background knowledge.
Here you can read about what Concept Exercises are and how they are structured:

What are Practice Exercises?
Anatomy of a Practice Exercise

Also, be aware of these general guidelines:

Exercism Markdown Specification
Exercism Formatting and Style Guide

Problem Specifications
The description and test cases for all practice exercises are taken from the problem specifications repository.

Problem specifications PR - This is the PR in problem specifications that created this exercise. Use it to read more about the decisions taken about the exercise.
Problem specifications exercise directory - This folder contains the description and test cases you must have for the exercise.

For more information on how to use the information from problem specifications when building the exercise, check Anatomy of a Practice Exercise.
How to proceed

First accept this issue by saying "I'd like to work on this". After posting that, feel free to start working on the issue right away. A maintainer will later assign put you as an assignee on the issue, but you don't have to wait for that to work on the issue.
Use this issue to discuss any questions you have, what should be included in the content and shouldn't, and to collect more reference material.
Create a PR and set "exercism/go" as reviewers. Additionally, you can write in #maintaining-go on Slack that your PR is ready for review. Once you incorporated any critical feedback that the reviewer might give you and the PR is approved, it will be merged by a maintainer.

"I'd like to work on this"

@CODETOSPACE - Are you still working on this?


Popped up in my subreddit, but it shouldn't be there

Only bots that I authorize should be posting in my subreddit. How to ensure this doesn't happen again?

Currently, there's no way to exclude subreddits or users from my end, but you can ban the bot and it won't be able to comment in your subreddit again.


Friendly suggestion

Hello @tranchikhang , I have been following your progress in this project, is getting better and better.
Can I sugges an improvement in the task/feature managment?
I see you have a "task backlog" in the readme. I would create one github issue for each of this entries, such as one issue for "Core Gameplay :: Ally support", this way you can link commits with their task, and it's way easier to find where you implemented each thing, you can even have a "kanban" style board (known as Github projects)
You can see working example in my repo "owge".
Best regards!, keep the great work :wine_glass: :beers:

Hi Kevin,
Thank you for your suggestion.
I agree with you, putting those "backlog" into issues would make everything easier for keeping track. I will use this weekend to create them.
Also thanks for the encouragement  :fire: :beers:

Hi Kevin,
Thank you for your suggestion.
I agree with you, putting those "backlog" into issues would make everything easier for keeping track. I will use this weekend to create them.
Also thanks for the encouragement  :fire: :beers:


Support Py3

Is your feature request related to a problem? Please describe.
简洁描述下新feature的内容
Support py3
Describe the solution you'd like
描述下你想要什么样的解决方案
调研python3和python2区别， 并开启支持python3
Describe alternatives you've considered
是否有其他替代方案
Additional context
可以辅助其他人理解你的信息

Please Support py3

yes

py 3 will be supported before July (H1 of 2019).


Can the clock be paused?

During a benchmark run, is it possible to pause the clock? If so, what are you allowed to do while the clock is paused?

SWG Decision:
The clock should not be paused. The clock should start at the beginning and end only once the target accuracy has been reached.
If there is a good reason otherwise, please let us know.


Dockerfile4.9

Fixed docker build for simulator, marvin and management-server.
Fixed change of release script to update dockerfiles.
I will update Jenkins builds once merged.

@pdion891 rebase against latest master and squash commits into a single commit, thanks
LGTM
tag:easypr

ACS CI BVT Run
Sumarry:
Build Number 146
Hypervisor xenserver
NetworkType Advanced
Passed=68
Failed=5
Skipped=3
Link to logs Folder (search by build_no): https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0
Failed tests:

test_vpc_vpn.py

ContextSuite context=TestRVPCSite2SiteVpn>:setup Failing since 11 runs

ContextSuite context=TestVpcRemoteAccessVpn>:setup Failing since 11 runs

ContextSuite context=TestVpcSite2SiteVpn>:setup Failing since 11 runs

test_volumes.py

test_06_download_detached_volume Failed

test_vm_life_cycle.py

test_10_attachAndDetach_iso Failed

Skipped tests:
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_deploy_vgpu_enabled_vm
Passed test suits:
test_deploy_vm_with_userdata.py
test_affinity_groups_projects.py
test_portable_publicip.py
test_over_provisioning.py
test_global_settings.py
test_scale_vm.py
test_service_offerings.py
test_routers_iptables_default_policy.py
test_routers.py
test_reset_vm_on_reboot.py
test_snapshots.py
test_deploy_vms_with_varied_deploymentplanners.py
test_login.py
test_list_ids_parameter.py
test_public_ip_range.py
test_multipleips_per_nic.py
test_regions.py
test_affinity_groups.py
test_network_acl.py
test_pvlan.py
test_nic.py
test_deploy_vm_root_resize.py
test_resource_detail.py
test_secondary_storage.py
test_disk_offerings.py

@swill, @runseb does one of you could LGTM or comment  thanks,

LGTM
I still think we need to put the db in another container, and start the whole thing with compose.
Also we need to make the image smaller, maybe using Debian as base would be smaller than then full ubuntu:14.04

@runseb I agree, images must be smaller. for the simulator, it's kind of usefull to have everything in it but it's not container best practice for sure.  other images, we could probably use alpine linux, but still need to figure out how to run cloudstack as a single .war file.

@resmo I've updated the PR. I've tested the simulator and marvin.

Hi @jburwell, do you think we can merge this in master or you are in a code freeze for <IP_ADDRESS> ?
Thanks,

@pdion891 if possible, I would like to get this merged for <IP_ADDRESS>.  How does this PR relate to #1789?  Also, could you please investigate the Jenkins failure and create JIRA ticket for this issue?

@PaulAngus @rhtyd what are your thoughts on automating the testing of the Docker container?

@pdion891 can you please investigate the Jenkins failure?

@jburwell good to have this, not sure how many people maybe using container/docker based mgmt servers?

@rhtyd agreed.  I apologize for being unclear -- I would like to get this PR into <IP_ADDRESS>, but it is not a release blocker.

I used it for development and testing.

I've retested the management server, it work with Jenkins as the build is back online.
@jburwell, do you know if there is a way to squash a commit within the same PR ?

@pdion891 this blog is  good description of squash process.

This PR is not valid anymore replaced by Squashed: #1815


Resolves #36

If you would, migrate the Element interface syncs to the PageLoaded class so everything pulls from the same source.
I.E.
//In the ElementImpl class
public boolean syncVisible(int timeout,  boolean returnError) {
 return PageLoaded.syncVisible(getWrappedDriver(), timeout, returnError, getWrappedElement());
}


arrow hovering behavior

Just a start to the callout for more obvious hover responses over arrows on the site.
Started with the Trade page. The down arrows next to the From ATOM v and the To OSMO v now scale slightly on hover by a factor of 1.3, which is stored as a constant ARROW_HOVER_SCALE in layout.ts.
The pagination arrows at the bottom of the Tools page also use that same scale to grow on hover when the arrow can be clicked. I also added a small hover to the button that switches direction on the Trade page - wasn’t sure it was a strong match to the current UI, though.
Other areas on the site have pagination arrows as well. I couldn’t figure out where they were in the code - but thinking they could possibly make use of the same  styling used in the AllPoolsPagination.

This was fun - my first contribution to an open source project. Anyone more familiar with the code base is welcome to edit/add on!

Hi @lymba. Thanks for you contribution. We're currently undergoing a refactor of the frontend which will be written exclusively in tailwind CSS. Given your knowledge on this issue, think you could revisit this post-refactor? Thanks again.

Sure.
Sorry for dipping out.
I have been studying and practicing for interviews and haven’t dedicated much time to other endeavors lately.
My apologies.
lynne
From: Jon Ator @.>
Date: Thursday, March 3, 2022 at 7:57 AM
To: osmosis-labs/osmosis-frontend @.>
Cc: Lynne Banki @.>, Mention @.>
Subject: Re: [osmosis-labs/osmosis-frontend] arrow hovering behavior (PR #248)
Hi @lymbahttps://github.com/lymba. Thanks for you contribution. We're currently undergoing a refactor of the frontend which will be written exclusively in tailwind CSS. Given your knowledge on this issue, think you could revisit this post-refactor? Thanks again.
—
Reply to this email directly, view it on GitHubhttps://github.com/osmosis-labs/osmosis-frontend/pull/248#issuecomment-1058191165, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APZAFAXO3HJJGRYCGF6DZC3U6DONVANCNFSM5N6WNSVA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>


Fix up 1.2 release branch

Fix up wording on the new 1.2 features.
Remove preview labels from 1.1 features.

Docs Build status updates of commit d920a51:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TerminalDocs/tips-and-tricks.md
:warning:Warning
View
Details

TerminalDocs/command-line-arguments.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/global-settings.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/key-bindings.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/profile-settings.md
:white_check_mark:Succeeded
View

TerminalDocs/panes.md
:white_check_mark:Succeeded
View

TerminalDocs/tips-and-tricks.md

Line 31, Column 233: [Warning-file-not-found] Invalid file link: './customize-settings/profile-settings'.
Line 35, Column 263: [Warning-file-not-found] Invalid file link: './customize-settings/profile-settings'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


WIP: pyside2 and shiboken2

built on top of the zeus branch
fixes #253
depend on meta-clang
build failure in shiboken2:
| [ 94%] Built target shiboken2
| make -f shibokenmodule/CMakeFiles/shibokenmodule_generator.dir/build.make shibokenmodule/CMakeFiles/shibokenmodule_generator.dir/depend
| make[2]: Entering directory '/wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/shiboken2/1.0+gitAUTOINC+f5265a2ab8-r0/build'
| cd /wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/shiboken2/1.0+gitAUTOINC+f5265a2ab8-r0/build && /wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/shiboken2/1.0+gitAUTOINC+f5265a2ab8-r0/recipe-sysroot-native/usr/bin/cmake -E cmake_depends "Unix Makefiles" /wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/shiboken2/1.0+gitAUTOINC+f5265a2ab8-r0/git/sources/shiboken2 /wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/shiboken2/1.0+gitAUTOINC+f5265a2ab8-r0/git/sources/shiboken2/shibokenmodule /wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/shiboken2/1.0+gitAUTOINC+f5265a2ab8-r0/build /wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/shiboken2/1.0+gitAUTOINC+f5265a2ab8-r0/build/shibokenmodule /wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/shiboken2/1.0+gitAUTOINC+f5265a2ab8-r0/build/shibokenmodule/CMakeFiles/shibokenmodule_generator.dir/DependInfo.cmake --color=
| Dependee "/wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/shiboken2/1.0+gitAUTOINC+f5265a2ab8-r0/build/shibokenmodule/CMakeFiles/shibokenmodule_generator.dir/DependInfo.cmake" is newer than depender "/wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/shiboken2/1.0+gitAUTOINC+f5265a2ab8-r0/build/shibokenmodule/CMakeFiles/shibokenmodule_generator.dir/depend.internal".
| Dependee "/wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/shiboken2/1.0+gitAUTOINC+f5265a2ab8-r0/build/shibokenmodule/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/shiboken2/1.0+gitAUTOINC+f5265a2ab8-r0/build/shibokenmodule/CMakeFiles/shibokenmodule_generator.dir/depend.internal".
| Scanning dependencies of target shibokenmodule_generator
| make[2]: Leaving directory '/wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/shiboken2/1.0+gitAUTOINC+f5265a2ab8-r0/build'
| make -f shibokenmodule/CMakeFiles/shibokenmodule_generator.dir/build.make shibokenmodule/CMakeFiles/shibokenmodule_generator.dir/build
| make[2]: Entering directory '/wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/shiboken2/1.0+gitAUTOINC+f5265a2ab8-r0/build'
| [ 96%] Running generator for 'shiboken2'...
| cd /wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/shiboken2/1.0+gitAUTOINC+f5265a2ab8-r0/git/sources/shiboken2/shibokenmodule && shiboken2 --project-file=/wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/shiboken2/1.0+gitAUTOINC+f5265a2ab8-r0/build/shibokenmodule/shibokenmodule.txt
| /bin/sh: shiboken2: command not found
| shibokenmodule/CMakeFiles/shibokenmodule_generator.dir/build.make:60: recipe for target 'shibokenmodule/mjb_rejected_classes.log' failed
| make[2]: *** [shibokenmodule/mjb_rejected_classes.log] Error 127
| make[2]: Leaving directory '/wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/shiboken2/1.0+gitAUTOINC+f5265a2ab8-r0/build'
| CMakeFiles/Makefile2:318: recipe for target 'shibokenmodule/CMakeFiles/shibokenmodule_generator.dir/all' failed
| make[1]: *** [shibokenmodule/CMakeFiles/shibokenmodule_generator.dir/all] Error 2
| make[1]: Leaving directory '/wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/shiboken2/1.0+gitAUTOINC+f5265a2ab8-r0/build'
| Makefile:129: recipe for target 'all' failed
| make: *** [all] Error 2

I followed https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=shiboken2-git

@snke I got shiboken to compile for the host (shiboken2-native) in db999de
Now the pyside2 recipe fails during configure:
| CMake Error at sources/pyside2-tools/CMakeLists.txt:11 (find_package):
|   By not providing "FindPySide2.cmake" in CMAKE_MODULE_PATH this project has
|   asked CMake to find a package configuration file provided by "PySide2", but
|   CMake did not find one.
|
|   Could not find a package configuration file provided by "PySide2"
|   (requested version 2.0.0) with any of the following names:
|
|     PySide2Config.cmake
|     pyside2-config.cmake
|
|   Add the installation prefix of "PySide2" to CMAKE_PREFIX_PATH or set
|   "PySide2_DIR" to a directory containing one of the above files.  If
|   "PySide2" provides a separate development package or SDK, be sure it has
|   been installed.
|
|

OK, now I'm stuck at b99766a
This comment in the PySide JIRA explains how they achieved a cross-compile.
AFAICT, one of the important steps is to use the /usr/bin/shiboken2 generator binary from the host to build the shiboken2 python module.
I did that in b99766a, and it does indeed generate the shiboken2 python module.
However, pyside2 fails to compile with:
| CMake Error at /wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/pyside2/1.0+gitAUTOINC+f5265a2ab8-r0/recipe-sysroot/usr/lib/cmake/Shiboken2-5.13.3/Shiboken2Targets.cmake:72 (message):
|   The imported target "Shiboken2::libshiboken" references the file
|
|      "/usr/lib/libshiboken2.cpython-37m-x86_64-linux-gnu.so.5.13.3"
|
|   but this file does not exist.  Possible reasons include:
|
|   * The file was deleted, renamed, or moved to another location.
|
|   * An install or uninstall procedure did not complete successfully.
|
|   * The installation package was faulty and contained
|
|      "/wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/pyside2/1.0+gitAUTOINC+f5265a2ab8-r0/recipe-sysroot/usr/lib/cmake/Shiboken2-5.13.3/Shiboken2Targets.cmake"
|
|   but not all the files it references.
|
| Call Stack (most recent call first):
|   /wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/pyside2/1.0+gitAUTOINC+f5265a2ab8-r0/recipe-sysroot/usr/lib/cmake/Shiboken2-5.13.3/Shiboken2Config.cpython-37m-x86_64-linux-gnu.cmake:50 (include)
|   /wrk/OS/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/pyside2/1.0+gitAUTOINC+f5265a2ab8-r0/recipe-sysroot/usr/lib/cmake/Shiboken2-5.13.3/Shiboken2Config.cmake:5 (include)
|   CMakeLists.txt:64 (find_package)
|

However, /usr/lib/libshiboken2.cpython-37m-x86_64-linux-gnu.so.5.13.3 exists in recipe-sysroot, so I don't understand why cmake doesn't pick it up.
Do you have any idea?

Qt5 is dead please follow up with TQC for their meta-qt6 if you're still interested.


Grammar issues in Reducer.md

I'm not a native speaker, so perhaps the following phrase from Reducer.md is in fact correct:

Should be given to mounted to your Redux state at form.

but it is really difficult to comprehend for me and the Grammarly plugin:)
Sorry for not being constructive in my critique, bu I don't even know what it was supposed to mean, so I can not propose any correction :(

I think the correct would be

Should be mounted to your Redux state at form

Would you like to send a PR to fix that? 😃


Fixed Email Sugestion Problem

PR Fixes:

1
2

Resolves #1595
Checklist before requesting a review

[☑] I have performed a self-review of my code
[☑] I assure there is no similar/duplicate pull request regarding same issue

video Preview :
https://github.com/user-attachments/assets/1b8364a2-726e-437f-aa3b-2a6913f1c6dc

Closing in favour of #1601


Timeouts

Hello,
we are running node-esl in a busy system. by design, it creates a new connection for each command and we are having around 20 connections per second (very short).
Sometimes we are getting timeouts:
authorizing state: null, authed state: false, connecting state: false, connected state: true
authorizing state: null, authed state: false, connecting state: true, connected state: false
Could you please suggest what we might be hitting, I do not see TCP attempts for failed connections in tcpdump. linux limits all "unlimited" or crazy high,  It must be something internal Node.js
Thank you in advance.

There is no internal node.js limit unless you set it yourself in your code. If you are not even seeing TCP attempts in a tcpdump, then my first guess is your operating system file descriptor limits.
How are you starting your node process? Sometimes, even if you have setup your ulimit file descriptor values, they will not be used (see the answers here).

@byoungdale I'm working with @nvitaly on this... I was able to narrow down part of the problem on the Node-ESL side.
In a happy case, the connection flow is as follow:

Node creates TCP Socket connection to FreeSwitch
Node receives 'auth/request' event
Node initiates the auth process

When testing 25+ simultaneous connections, I'm seeing that the event in step 2 does not always happen. This prevents the auth process and hence the "timeout" that we're experiencing.
Any idea why that might be happening?
I'm considering skipping that event listener and going straight to the auth process after the TCP connection.

Closing this because it sounds like a ulimit or freeswitch configuration issue. If we get more details or encounter a more specific node problem feel free to open a new issue.


Randomize the monster numbers

A small request: please randomize (or provide a button) the monster numbers in a given room.  In a crowded scenario like Forgotten Sewers it can have a pretty big impact.

Hi @amusedleg , the monster numbers should already be randomly assigned. Is this not what you're seeing?
What should happen is that as you add a monster or reveal a room the first available number should be taken from a randomised list of possible numbers for that monster type. When a monster is defeated this number is then added back to the stack, ready to be re-used. Are you seeing different behaviour? Or is there an alternative way you'd like to see monster numbers being distributed?

Closing this until there's more info


Update k8s to v0.31.2

This PR contains the following updates:

Package
Type
Update
Change

k8s.io/api
require
patch
v0.31.1 -> v0.31.2

k8s.io/apimachinery
require
patch
v0.31.1 -> v0.31.2

k8s.io/cli-runtime
require
patch
v0.31.1 -> v0.31.2

k8s.io/client-go
require
patch
v0.31.1 -> v0.31.2

k8s.io/kubectl
require
patch
v0.31.1 -> v0.31.2

Release Notes

kubernetes/api (k8s.io/api)
v0.31.2
Compare Source

kubernetes/apimachinery (k8s.io/apimachinery)
v0.31.2
Compare Source

kubernetes/cli-runtime (k8s.io/cli-runtime)
v0.31.2
Compare Source

kubernetes/client-go (k8s.io/client-go)
v0.31.2
Compare Source

kubernetes/kubectl (k8s.io/kubectl)
v0.31.2
Compare Source

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

ℹ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

1 additional dependency was updated

Details:

Package
Change

k8s.io/component-base
v0.31.1 -> v0.31.2

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

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

Totals

Change from base Build<PHONE_NUMBER>6:
0.0%

Covered Lines:
438

Relevant Lines:
990

💛  - Coveralls


Check 1.0 docs for accuracy against 0.9 changes

See https://github.com/ably/docs/issues/264 and 1.0 PR at https://github.com/ably/docs/pull/260
@ricardopereira please can you do a similar task to what Peter did and review all Realtime & REST API docs and provide a list of what needs changing please.
Please note that Peter did not provide a list of links to Github as a reference for method definitions / interfaces etc.  Please can you do that so that it's easier for me to jump straight to code when working out what to change.

https://github.com/ably/docs/blame/77fe470b34d29524a4ed1e118e83d2f649e2ce33/content/root/quick-start-guide.textile#L142
(only the Blame view provides the ability to link to a specific line within the source)
Use ARTRealtimeConnectionEvent instead of ARTRealtimeConnectionState.
[realtime.connection once:ARTRealtimeConnectionEventConnected callback:^(ARTConnectionStateChange *stateChange) {

Types
ARTTokenRequest
ttl property of type NSTimeInterval in Swift & ObjC:
https://github.com/ably/docs/blame/77fe470b34d29524a4ed1e118e83d2f649e2ce33/content/types/_token_request.textile#L9
timestamp property of type NSDate in Swift & ObjC:
https://github.com/ably/docs/blame/77fe470b34d29524a4ed1e118e83d2f649e2ce33/content/types/_token_request.textile#L10

Done ✅

Thanks, please leave this open as we need to update this before we release 1.0.

@ricardopereira I believe this is all fixed in	155fa73. I'm merging into www.ably.io/documentation now so it would be nice if you could double check the issues you mentioned above and confirm everything is OK. Thanks

@mattheworiordan Reviewed. I only found this issue https://github.com/ably/docs/pull/285.

Thanks @ricardopereira


types: add recursive option to SeprType

this PR sits on top of #108, so consider that one first.
here we add support for recursive comp types. that is, a subprop of a comp type may be an instance of that comp type. i've updated SeprType to support recursion. this means you can do something like:
>>> tlib.addType('path',
                 subof='sepr',
                 sep='/',
                 reverse=1,
                 fields='dirname,path|filename,str:lwr',
                 recursive=1)
>>> tlib.getTypeChop('path','/home/user/Downloads')

<<<
('/home/user/downloads',
  {
    'dirname': '/home/user',
    'filename': 'downloads',
  })

there's possible a number of applications for this (fqdn, file paths, etc.), so i hope its worth the increased complexity within SeprType.
also adds the strictfields option to SeprType. by default, this option is set. when it is unset, then missing propvalues are not set, and no BadPropValu exception is raised. this makes it easy to parse strings with an optional suffix. for example:
>>> tlib.addType('filename',
                 subof='sepr',
                 sep='.',
                 reverse=1,
                 strictfields=0,
                 fields='basename,str:lwr|ext,str:lwr')
>>> tlib.getTypeChop('filename','kernel32.dll')

<<<
('kernel32.dll',
  {
    'basename': 'kernel32',
    'ext': '.dll',
  })

>>> # look, no error!
>>> tlib.getTypeChop('filename','Downloads')

<<<
('Downloads',
  {
    'basename': 'downloads',
  })

Coverage increased (+0.02%) to 87.011% when pulling 0c6633a72b5ad60c1bffc0a81d50c6f24627d438 on williballenthin:sepr-recursive into 3a4136db971d77c5c3ed9423ee064ae1ecc59966 on vivisect:master.

Coverage decreased (-0.006%) to 86.983% when pulling c4da9e56ba5954d1ee2e3a5c3bdbe32ba3f619ca on williballenthin:sepr-recursive into 3a4136db971d77c5c3ed9423ee064ae1ecc59966 on vivisect:master.

removed the strictfields option cause (1) it didn't belong here, and (2) there are better ways to do this.

Coverage decreased (-0.2%) to 86.742% when pulling 665d9a3c7f0a66109fe1283ea4006d787923567f on williballenthin:sepr-recursive into 3a4136db971d77c5c3ed9423ee064ae1ecc59966 on vivisect:master.

Coverage decreased (-0.2%) to 86.742% when pulling 665d9a3c7f0a66109fe1283ea4006d787923567f on williballenthin:sepr-recursive into 3a4136db971d77c5c3ed9423ee064ae1ecc59966 on vivisect:master.

addressed all recommendations. removed the recursive option, which really simplified the code. awaiting further suggestions, or reject/merge.

Coverage decreased (-0.2%) to 86.761% when pulling c8d42054a78a3100b1e94ea3e39883043bdb219e on williballenthin:sepr-recursive into 3a4136db971d77c5c3ed9423ee064ae1ecc59966 on vivisect:master.


Seach File

I wanna add on this APP the SearchBar , i think it's will be a good idea , and it's verry essential .
so i need your confirmation to begin .

Yes, sounds good

Good evening, I added the search bar for the application, I took some time
to read the code, I finally added the searchable icon in Menu > main.xml .
(searchable.xml): to bind the menu with the icon searchresultactivity the
activity which allows the writing of the text to look .
Folder for Activirty: contains the treatment to apply the search in list
navigation . For the general search,i am working it, it’s a little bit
complex I have errors in the search that there are sub-lists of list .
On waiting if you want to add this version before the last version very
soon..
2015-04-07 19:58 GMT+02:00 Michal Dabski<EMAIL_ADDRESS>
Yes, sounds good
—
Reply to this email directly or view it on GitHub
https://github.com/mick88/filemanager/issues/7#issuecomment-90676576.

How can i send you my code , i can't push the modifiction in GitHub ?
2015-05-24 1:23 GMT+02:00 simo ghrissi<EMAIL_ADDRESS>
Good evening, I added the search bar for the application, I took some time
to read the code, I finally added the searchable icon in Menu > main.xml .
(searchable.xml): to bind the menu with the icon searchresultactivity the
activity which allows the writing of the text to look .
Folder for Activirty: contains the treatment to apply the search in list
navigation . For the general search,i am working it, it’s a little bit
complex I have errors in the search that there are sub-lists of list .
On waiting if you want to add this version before the last version very
soon..
2015-04-07 19:58 GMT+02:00 Michal Dabski<EMAIL_ADDRESS>
Yes, sounds good
—
Reply to this email directly or view it on GitHub
https://github.com/mick88/filemanager/issues/7#issuecomment-90676576.

You can push to your own form and make a pull request to my repository from yours

The first time , i downloaded the application not clonning it in my git
respectory so now i had clone your's and add my modification , that is why
you gonna see a lot of change in my pull request .
2015-05-24 17:40 GMT+02:00 Michal Dabski<EMAIL_ADDRESS>
You can push to your own form and make a pull request to my repository
from yours
—
Reply to this email directly or view it on GitHub
https://github.com/mick88/filemanager/issues/7#issuecomment-105028161.


Make -v --version argument

Need  to provide ability to get version of moonworm from cli

Id like to take a stab at this. I'm guessing it shouldgo in cli.py

@twelsh37, cool.
Yes, it will go to cli.py
Basically moonworm -v should print current version from version.py

@twelsh37 , @Yhtiyar : It might be easier to add a subcommand called moonworm version. Getting the right behaviour for moonworm -v requires messing with arparse actions, which can be kind of a pain.

resolved in #68


[$500]  Inconsistency - Emoji suggestions doesn't appear after "@"

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

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

Open any report
Type "#:jo" or ":jo" with any special character before ":jo"
Observe the suggestions appear
Type "@:jo"
Observe the suggestions deosn't appear

Expected Result:
Suggestion should appear when "@:jo" is typed like any other special character at the start.
Actual Result:
Suggestions doesn't appear when "@:jo"  is typed.
Workaround:
unknown
Platforms:

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

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/38435837/0ecffc6d-bbf8-4098-817c-a7e5857a594c

Android: mWeb Chrome

https://github.com/Expensify/App/assets/38435837/6470f1ed-6a81-4d5e-85f2-76833d142693

iOS: Native

https://github.com/Expensify/App/assets/38435837/b4ffda8a-b55f-4bce-a3f9-3545cc8a0e4a

iOS: mWeb Safari

https://github.com/Expensify/App/assets/38435837/edf2e339-24de-49ef-9311-d232c986c9cc

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/38435837/be680b08-a4ad-4132-aa83-08f6b80af2fc
https://github.com/Expensify/App/assets/38435837/84a8d9d1-97e1-418e-96bc-09c07535c32e

MacOS: Desktop

https://github.com/Expensify/App/assets/38435837/5ee161fe-76ac-4f6b-a457-6ebd2c086768

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0132b0a190e276b033
Upwork Job ID:<PHONE_NUMBER>297076224
Last Price Increase: 2023-10-23

Proposal from @Krishna2323
Please re-state the problem that we are trying to solve in this issue.
Inconsistency - Emoji suggestions doesn't appear after "@"
What is the root cause of that problem?
We haven't added "@" in special chars regex here:
https://github.com/Expensify/App/blob/e73cd31a567c5f026f3a9f1435ecb6f99b2fae82/src/CONST.ts#L1325
What changes do you think we should make in order to solve the problem?
We just need to add "@" between [] brackets.
Updated Regex: SPECIAL_CHAR: /[,/?"{}[\]()&^%;$=#<>!@*]/g`
Result

I don't think showing emoji suggestion in this situation is a good idea, it will be confusing. Just checked slack and they don't show it too

I agree with @alitoshmatov and think we should treat @ differently here, since we use the @ for mentions in NewDot. No other special characters have special uses like that. I'm going to close this one, but thanks for raising for discussion!