Naming collision error when running packager, caused by "lodash" and "yeoman-generator"

Description
In my project I am using "react-native": "0.36.0" and among the dependencies:

"lodash": "^4.15.0"
"yeoman-generator": "^0.24.1"

When using versions higher than "^3.10.1" for "lodash" and "0.21.2" for "yeoman-generator" I get naming collisions on "lodash", "inquirer" and "cli-width" when running packager.
Reproduction
Have the dependencies described above and run: react-native start --reset-cache
Result:
jest-haste-map: @providesModule naming collision:
  Duplicate module name: inquirer
  Paths: /CoolProject/node_modules/react-native/node_modules/yeoman-generator/node_modules/inquirer/package.json collides with /CoolProject/node_modules/react-native/node_modules/inquirer/package.json

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: lodash
  Paths: /CoolProject/node_modules/react-native/node_modules/lodash/package.json collides with /CoolProject/node_modules/react-native/node_modules/inquirer/node_modules/lodash/package.json

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: cli-width
  Paths: /CoolProject/node_modules/react-native/node_modules/yeoman-generator/node_modules/cli-width/package.json collides with /CoolProject/node_modules/react-native/node_modules/cli-width/package.json

This warning is caused by a @providesModule declaration with the same name across two different files.

Solution
Using the same versions for "lodash" and "yeoman-generator" as the ones used in<EMAIL_ADDRESS>(i.e. "^3.10.1" for "lodash" and "0.21.2" for "yeoman-generator") fixes the issue, but changing them is really not an option for me at the moment.
Is there any other possible fix?
Additional Information

React Native version: 0.36.0
Platform: both
Operating System: MacOS

You are building a mobile app that depends on a different version of yeoman-generator? I am confused as to what exactly is happening. You create a new react native app, and then install specific versions of some other dependencies, and it breaks react native itself? In general ^3.x.x and ^4.x.x are not supposed to be compatible, is my understanding, so you do actually have to use versions of the dependencies which match package.json.

@lacker To explain my problem more clearly think of it like this: My app has a dependency on react-native and another personal module, let's say named my-module. Each of them has a dependency on two different versions of yeoman-generator:
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>
What I want to understand is if my-module was just another public node module and I had no access over it to change the version of it's yeoman-generator then I would not be able to use it in conjunction with react-native?
I have an Android dev background and there when we set our dependencies in Gradle we have the ability to exclude a internal dependency of a dependency if it doesn't match our needs. E.g.:
compile("com.facebook.react:react-native:+") {
  exclude group: 'com.android.support'
}

Do we have something similar for react?

It seems like npm should solve this - react and react native don't really manage their dependencies themselves, they are just libraries that you use according to npm. How did you install your own version of yeoman-generator, which npm version are you using?

@lacker - I am using npm v3.10.8 and node v7.0.0.
In my-module I just have<EMAIL_ADDRESS>among all the dependencies, nothing out of the ordinary:
"dependencies": {
    "chalk": "^1.1.3",
    "glob": "^7.0.5",
    "lodash": "^4.15.0",
    "yeoman-generator": "^0.24.1",
    "yosay": "^1.2.0"
  },

I am starting to think that this is more an npm issue rather than something related to react-native. I think it was just a coincidence that react-native was one of the modules involved in the "naming collision" error.
What do you think?

Yeah I agree I think this sounds like an npm problem. I'm gonna close this under that theory but if you do figure out that it's a React Native thing please feel free to reopen!

Thanks @lacker! I will do as you suggested if I figure out that this issue has any connection to React Native.

@lacker - After looking more closely I found that it is expected for npm to install different versions for different modules if that is requested by their package.json files. There is the npm dedupe command that tries to flatten the dependency structure, but that doesn't help in this case.
Looking through the node_modules folder I found that there are many sub-modules that are installed with different versions for different dependencies, but the react-native packager doesn't complain about them. The only ones that it doesn't like are the "lodash", "inquirer" and "cli-width".
The node modules seem to be installed correctly and the code that causes the error is the one that processes them, i.e. react-native packager.
As we can see in the initial logs I provided, the error is thrown by the jest-haste-map module: https://github.com/facebook/jest/blob/master/packages/jest-haste-map/src/index.js#L303
Could this bug be directly related to react-native-cli, and more exactly to jest-haste-map?
I created a test project where I have the following dependencies for both cases:

packager working correctly:

"dependencies": {
    "inquirer": "^0.12.0",
    "lodash": "^3.10.1",
    "yeoman-generator": "^0.21.2",
    "react": "15.3.1",
    "react-native": "0.36.0"
  },

packager throwing "naming collision error":

"dependencies": {
    "inquirer": "^0.10.1",
    "lodash": "^4.16.4",
    "yeoman-generator": "^0.24.1",
    "react": "15.3.1",
    "react-native": "0.36.0"
  },

but in both cases there are different versions of different nested modules installed, so I think we can exclude npm from the culprit list.

OK, I am reopening. I am not sure if this is a known issue - maybe @cpojer can comment on whether this is expected behavior in some sense of "expected".

What does your Jest config look like?

@cpojer I don't have any config for Jest. The error is thrown by jest-haste-map when I run react-native start --reset-cache on a vanilla React Native project with the dependencies from my previous comment.

Oh, this is inside of RNP (which also uses jest-haste-map). This is very odd and shouldn't be happening. Can you upload a repository on github that shows this issue?

@cpojer Here is a vanilla React Native project where I only updated the package.json file to contain the dependencies (and versions) that are causing the issue: https://github.com/andreipt/VanillaReactNative
In the readme file you can find the dependency versions for which packager is running successfully.
Thanks!

I'm facing similar issues after upgrading dependencies of my RN app.
Logs when starting the RN packager or jest:
jest-haste-map: @providesModule naming collision:
  Duplicate module name: babylon
  Paths: /Users/winterbe/Projects/PondusApp/node_modules/react-native/node_modules/babel-traverse/node_modules/babylon/package.json collides with /Users/winterbe/Projects/PondusApp/node_modules/react-native/node_modules/babel-core/node_modules/babylon/package.json

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: babel-runtime
  Paths: /Users/winterbe/Projects/PondusApp/node_modules/react-native/node_modules/babel-traverse/node_modules/babel-runtime/package.json collides with /Users/winterbe/Projects/PondusApp/node_modules/react-native/node_modules/babel-core/node_modules/babel-runtime/package.json

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: babel-runtime
  Paths: /Users/winterbe/Projects/PondusApp/node_modules/react-native/node_modules/babel-types/node_modules/babel-runtime/package.json collides with /Users/winterbe/Projects/PondusApp/node_modules/react-native/node_modules/babel-traverse/node_modules/babel-runtime/package.json

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: lodash
  Paths: /Users/winterbe/Projects/PondusApp/node_modules/react-native/node_modules/babel-core/node_modules/lodash/package.json collides with /Users/winterbe/Projects/PondusApp/node_modules/react-native/node_modules/babel-types/node_modules/lodash/package.json

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: lodash
  Paths: /Users/winterbe/Projects/PondusApp/node_modules/react-native/node_modules/babel-traverse/node_modules/lodash/package.json collides with /Users/winterbe/Projects/PondusApp/node_modules/react-native/node_modules/babel-core/node_modules/lodash/package.json

This warning is caused by a @providesModule declaration with the same name across two different files.

package.json:
  "jest": {
    "preset": "jest-react-native",
    "testResultsProcessor": "node_modules/jest-teamcity-reporter"
  },
  "devDependencies": {
    "babel-eslint": "7.1.1",
    "babel-jest": "17.0.2",
    "babel-plugin-transform-decorators-legacy": "1.3.4",
    "babel-preset-react-native": "1.9.0",
    "eslint": "3.11.1",
    "eslint-plugin-react": "6.8.0",
    "eslint-teamcity": "1.3.1",
    "jest": "17.0.3",
    "jest-react-native": "17.1.0",
    "jest-teamcity-reporter": "0.2.0",
    "react-test-renderer": "15.4.1"
  },
  "dependencies": {
    "filesize": "3.3.0",
    "lodash": "4.17.2",
    "mobx": "2.6.5",
    "mobx-logger": "0.3.1",
    "mobx-react": "4.0.3",
    "moment": "2.17.1",
    "react": "15.4.1",
    "react-native": "0.39.0",
    "react-native-vector-icons": "3.0.0",
    "streamjs": "1.6.4",
    "underscore.string": "3.3.4"
  }

@cpojer Do you have any updates on the issue? Were you able to reproduce it using the repository I provided? Thanks!

Would you mind upgrading to RN 0.39 or master to see if this issue still persists?

I have about 532 of the following messages for different modules:
jest-haste-map: @providesModule naming collision:
This warning is caused by a @providesModule declaration with the same name across two different files.
I don't use lodash or yeoman-generator.
This started appearing when I upgraded to latest React, RN, Jest, etc. as you can see in my package.json.  @cpojer I am using 0.39.2 (the latest).  Thought I should post this here after reading the thread and recommendations.
{
"name": "ExampleRN",
"version": "0.0.1",
"private": true,
"scripts": {
"start": "react-native start",
"test": "jest",
"flow": "flow; test $? -eq 0 -o $? -eq 2"
},
"dependencies": {
"invariant": "^2.2.2",
"react": "^15.4.1",
"react-addons-shallow-compare": "^15.4.1",
"react-native": "^0.39.2",
"react-redux": "^4.4.6",
"redux": "^3.6.0",
"whatwg-fetch": "^2.0.1"
},
"jest": {
"preset": "jest-react-native"
},
"devDependencies": {
"babel-jest": "^17.0.2",
"babel-preset-react-native": "^1.9.0",
"flow-bin": "^0.37.0",
"jest": "^17.0.3",
"jest-react-native": "^17.1.0",
"react-test-renderer": "^15.4.1"
}
}

@cpojer I confirm that after upgrading react-native to 0.39 I am not seeing the naming collision errors anymore.
Do you know if the actual fix was the removal of yeoman from RN's dependencies? https://github.com/facebook/react-native/commit/1fd7a574ba538d05da4be841c84a70766464ec13
Thanks!

Upgrading a project to react-native 0.41.2 is giving me a bazillion of these errors

@MattyK14 I think it might be a similar symptom of a different problem. Would you mind opening a new issue? In particular it would be really useful to have a brief repro, for example if creating a new project with React Native Version X and upgrading to React Native Version Y doesn't work.

@lacker I did a rm -rf node_modules && npm install and it fixed it up.

I see. Yeah that works a lot! @mkonicek is working on improving this tooling so I think/hope that failure mode will be fixed soon.

Upgrading project to react-native 0.42.0 still is giving a lot of naming collision. I did node_modules delete and reinstall, but this did not help.

On react-native 0.42.0 as well and seeing a bunch of these, for example:
This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: minimist
  Paths: /Users/****/BitBucket/****/mobile/node_modules/react-native/node_modules/minimist/package.json collides with /Users/****/BitBucket/****/mobile/node_modules/react-native/node_modules/optimist/node_modules/minimist/package.json

Which seems to be internal to react-native.

Turns out after deleting node-modules and npm install a few times, these warnings went away. Not entirely sure that was what did it or not.

:grep 'naming collision' temp.txt  | wc -l       59
I am getting a huge number of these naming collisions - I just installed react-navigation and tried running react native run-android
{   "name": "MyProject",   "version": "0.0.1",   "private": true,   "scripts": {     "start": "node node_modules/react-native/local-cli/cli.js start",     "test": "jest"   },   "dependencies": {     "react": "~15.4.1",     "react-native": "0.42.3",     "react-navigation": "^1.0.0-beta.7"   },   "devDependencies": {     "babel-jest": "19.0.0",     "babel-preset-react-native": "1.9.1",     "jest": "19.0.2",     "react-test-renderer": "~15.4.1"   },   "jest": {     "preset": "react-native"   } }

I was getting this issue with an application where I install with "yarn install" , instead of npm install.  I did npm install -g npm, sudo rm -rf node_modules, and ran npm install, ..npm deduped these files (yarn did not do any deduping)...and now i no longer get that error...perhaps that will help?

Running yarn install && npm dedupe worked for me too (an alternative solution of @susanner23 's solution)


v0.0.53 breaks Hue remote

I have been using Quirks v0.0.49 for a couple of months and all has been well.  However, on updating to v0.0.53, I noticed that none of my Hue remotes would trigger any automations, either with HA automations or using ControllerX under AppDaemon.  None of my other zigbee switches (Ikea, Aqara) were affected.
I tested the Hue remotes under ZHA_Event and the triggers are being picked up just fine, as far as I can tell.  I was contemplating if there was a subtle change which broke the automation within ControllerX, but the remotes would also not trigger new HA automations using them either.
On reverting back to v0.0.49 and restarting HA, the problem was resolved.
I haven't tried any other versions between these two, so I can't say for sure whether it's this version or a previous one where the break happens, but I'm suspecting there has been a change made to the quirk for the Hue remote which breaks mine.
My Hue remotes are model RWL021 with firmware version 0x42006f9d
My HA installation is as follows:
Type:  Supervised on Debian Buster
Core version: 2021.1.5
Supervisor version: 2021.01.7

you need to run it with the beta HA release.

you need to run it with the beta HA release.

Ah, fair enough.

Ah, fair enough.

Ah, fair enough.

Have you updated HA beyond 2021.1.5 and if so are the dimmers working OK still?

I tried the update and the Hue remotes had an issue again. They would be visible in ZHA and checking the ZHA_event would see responses, but none of the triggers worked. So I’m stuck at 2021.1.5 until I can work out how to fix it.

Thanks for replying, that's literally the problem I was having, zha events not matching those used by ControllerX after updating past 2021.1.5. Have now fixed it this evening thanks to the devs help, check the end of the issue below but essentially just deleted the /config/deps/ folder and am now in full working order and bang up to date across the board...
https://github.com/zigpy/zha-device-handlers/issues/782

Thanks for the info.  I've given that a whirl, updated HA and the Hue remotes are still working properly!  Thank you for getting to the bottom of this and letting me know.

No probs, credit to @MattWestb for tracking it down.

Thanks for the credit !!
Im glad i can helping :-))
I was having similar problems for one year ago then testing bellows (V8 support) and installing pre commits with pip that was not in the dev branch and they was later blocking then upgrading the the "normal" dev branch.


Update Spark version from 1.6 to 2.2

Hi,
The renault datalake updated its Spark version from 1.6 to 2.2
Do you think you can update the Spark version on hadoop unit standalone version too?
Thanks,

Hello,
Hadoop Unit does not provide spark.
If you want to use spark, you have the local mode.
Hadoop Unit just provides a pom’s helper (hadoop-unit-client-spark) with which you can use to avoid manually adding exclude section in the pom.xml.
By the way, Hadoop Unit is already using Spark 2.2.

Ok, thank you jetoile.


Iron Router showing undefined route

Getting this message in the browser console on a clean install:
You called Router.url for a route named undefined but that route doesn't seem to exist. Are you sure you created it?

Will have a look at this the next days.

I'm looking at this right now, there's a template called 'atForm' in the header that isn't defined, I'm guessing it's supposed to be some kind of login form?

It is, but in a package: https://github.com/meteor-useraccounts/semantic-ui/blob/master/lib/at_form.html. Let's just wait until this bug get's resolved in ms-seo. It won't break anything.

I was able to get rid of the warning/message by assigning the default home route a name:
Router.route('/', {
name: 'home'
}, function () {
this.render('home');
SEO.set({ title: Meteor.App.NAME });
});

This is fixed now

This still appears in my app. How can I fix it?

Have a look at the structure of the default mainRoutes: https://github.com/matteodem/meteor-boilerplate/blob/master/routes/mainRoutes.js


Doc thumbnail disappears after a long sleep

Does this issue occur when all extensions are disabled?: Not sure, if I disable extensions for a long period I can't use the editor.

VS Code Version: 1.59.0-insider
OS Version: Darwin x64 20.6.0

Steps to Reproduce:

Minimize a VSCode instance
Keep it on that state for a long time (I think the trigger might be a long sleep, but I am not sure)
You will not see the thumbnails, just the small icon (see screenshots).

Adding to point 2: is it possible that this happens when I have a new update? Because I think everytime this happen I will have the option "Restart to Update". I had open this tab to create the ticket for a week and it didn't happen until today.
Screenshot of how it should be:

Screenshot of what I am describing as a bug:

Screenshot of what happens if I open & minimize again one of the editors:

Thanks!

Feels like an electron issue, for now assigning @rzhao271

Yes, it still happens.
Sorry I didn't comment earlier but I wanted to reproduce the error again and I was able to do it today:

I was able to repro this with other apps after waking from sleep, looks like this is known issue in the community https://discussions.apple.com/thread/252130664. Closing as this not something particular to vscode.


Add fineweb classifier

Description
This PR adds fineweb clasifier.
Usage
python3 fineweb_edu_classifier_example.py --input-data-dir input_data --output-data-dir "test_classifier"

Checklist

[x] I am familiar with the Contributing Guide.
[ ] New or Existing tests cover these changes.
[ ] The documentation is up to date with these changes.

Merge after we switch this repo to 0.0.3 https://github.com/rapidsai/crossfit/releases/tag/0.0.3  , PIP process is still ongoing.

@ryantwolf , Thanks for the careful review. Made relevant changes and followed up with questions. Let me know what else to change.

Ok looks good. Just need to figure out the AEGIS memory changes

@ryantwolf , Pushed the memory changes  https://github.com/NVIDIA/NeMo-Curator/pull/168/commits/18d93da0d6193796339d1b89b457c88766d64a7d
Please take a another look


Error when running "make dockerrun-all" after pytest execution

Getting this error -
________________________________________________________________________________________________________ ERROR collecting test_bs.py _________________________________________________________________________________________________________
import file mismatch:
imported module 'tests.test_bs' has this file attribute:
/Users/yuval/dev/sm/go/src/github.com/spacemeshos/go-spacemesh/tests/test_bs.py
which is not the same as the test file we want to collect:
/go-spacemesh/tests/test_bs.py
HINT: remove pycache / .pyc files and/or use a unique basename for your test file modules
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 1 errors during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
========================================================================================================== 1 error in 0.44 seconds ===========================================================================================================
It is better if we canfail the execution at the beggining instead of waiting until it is needed to fail it

should not happen anymore as pycache is now in dockerignore


Multi-Device Example crash on posting temperature data (MEGH-1907)

ESP32-S2
To reproduce:
Compile example and upload.
Wait for Temperature to be updated
Log:
I (32458) esp_rmaker_time: The current time is: Thu Mar  4 01:40:12 2021 +0800[CST], DST: No.
I (60508) esp_rmaker_param: Reporting params: {"Temperature Sensor":{"Temperature":25.50000}}
E (65498) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (65498) task_wdt:  - IDLE (CPU 0)
E (65498) task_wdt: Tasks currently running:
E (65498) task_wdt: CPU 0: esp_timer
E (65498) task_wdt: Print CPU 0 (current core) backtrace
Backtrace:0x400C15A3:0x3FFC81B0 0x400245B2:0x3FFC81D0 0x4010CBB4:0x3FF9F7F0  |<-CORRUPTED
0x400c15a3: task_wdt_isr at C:/esp/esp-idf/components/esp_common/src/task_wdt.c:189
0x400245b2: _xt_lowint1 at C:/esp/esp-idf/components/freertos/port/xtensa/xtensa_vectors.S:1105
0x4010cbb4: aes_ll_get_state at C:\esp\esp-idf\esp-rainmaker\examples\multi_device\build/../../../../components/hal/esp32s2/include/hal/aes_ll.h:140 (discriminator 1)
(inlined by) aes_hal_wait_done at C:/esp/esp-idf/components/hal/aes_hal.c:92 (discriminator 1)
Thank you.

I decided to do some further testing and this problem is only on ESP32S2. On the C3, it runs well.

@JohnMacrae , some fixes related to this were made in this MR. Can you confirm if it works for you?

All running well - many thanks for this MR.


#<Mysql2::Error: Can't connect to MySQL server on 'db' (111)>

I'm running install.sh -l in my MacOSX, and when it tries to start local_db_1_e6351c097e85, it fails when it tries to connect to the MySQL server and thus fails to create the database
[6/6] Init database...
Starting local_tango_1_b01116f87ab0 ... done
Step 20/20 : RUN apt-get clean && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/*
 ---> Running in 5e8912df8499
Removing intermediate container 5e8912df8499
 ---> a09378dae1e9
Successfully built a09378dae1e9
Successfully tagged local_web:latest
WARNING: Image for service web was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
Creating local_tango_1_f972b5a1c594 ... done
Creating local_db_1_d824e7c0230a    ... done
Creating local_web_1_783357f955cc   ... done
[5/6] Done
[6/6] Init database...
Starting local_tango_1_b01116f87ab0 ... done
Starting local_db_1_e6351c097e85    ... done
#<Mysql2::Error: Can't connect to MySQL server on 'db' (111)>
Couldn't create database for {"adapter"=>"mysql2", "database"=>"app_autolab_development", "pool"=>5, "username"=>"root", "password"=>nil, "socket"=>"/var/run/mysqld/mysqld.sock", "host"=>"db"}, {:charset=>"utf8", :collation=>"utf8_unicode_ci"}
Starting local_tango_1_b01116f87ab0 ... done
Starting local_db_1_e6351c097e85    ... done
rake aborted!
ActiveRecord::NoDatabaseError: Unknown database 'app_autolab_development'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/mysql2_adapter.rb:23:in `rescue in mysql2_connection'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/mysql2_adapter.rb:10:in `mysql2_connection'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:438:in `new_connection'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:448:in `checkout_new_connection'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:422:in `acquire_connection'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:349:in `block in checkout'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:348:in `checkout'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:263:in `block in connection'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:262:in `connection'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:567:in `retrieve_connection'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_handling.rb:113:in `retrieve_connection'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_handling.rb:87:in `connection'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/migration.rb:913:in `initialize'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/migration.rb:820:in `new'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/migration.rb:820:in `up'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/migration.rb:798:in `migrate'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/tasks/database_tasks.rb:137:in `migrate'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/railties/databases.rake:44:in `block (2 levels) in <top (required)>'
/var/lib/gems/2.2.0/gems/rake-12.0.0/exe/rake:27:in `<top (required)>'
Mysql2::Error: Unknown database 'app_autolab_development'
/var/lib/gems/2.2.0/gems/mysql2-0.3.18/lib/mysql2/client.rb:70:in `connect'
/var/lib/gems/2.2.0/gems/mysql2-0.3.18/lib/mysql2/client.rb:70:in `initialize'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/mysql2_adapter.rb:18:in `new'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/mysql2_adapter.rb:18:in `mysql2_connection'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:438:in `new_connection'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:448:in `checkout_new_connection'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:422:in `acquire_connection'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:349:in `block in checkout'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:348:in `checkout'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:263:in `block in connection'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:262:in `connection'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:567:in `retrieve_connection'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_handling.rb:113:in `retrieve_connection'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/connection_handling.rb:87:in `connection'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/migration.rb:913:in `initialize'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/migration.rb:820:in `new'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/migration.rb:820:in `up'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/migration.rb:798:in `migrate'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/tasks/database_tasks.rb:137:in `migrate'
/var/lib/gems/2.2.0/gems/activerecord-4.2.1/lib/active_record/railties/databases.rake:44:in `block (2 levels) in <top (required)>'
/var/lib/gems/2.2.0/gems/rake-12.0.0/exe/rake:27:in `<top (required)>'
Tasks: TOP => db:migrate
(See full trace by running task with --trace)
./install.sh: line 98: ./install.sh: No such file or directory
Failed command:

ERROR: Line 186 of script has return value 1. The log file is saved at /var/folders/b6/xq5h_sm935v4fgp8c0qs9dp00000gn/T/tmp.2InULY6t.

Thank you for trying out Autolab! For questions and comments, email us at<EMAIL_ADDRESS>

Apparently the install script is only known to work on a fresh install of Ubuntu 16.04, and anything other than that may have issues. I'm a bit stumped, since it failed on my U14.04 setup and the only dependencies that aren't OS-agnostic are Pip and Docker. I'll try this out a bit more and see if I can find a fix

Thanks Theodor. Any luck tracking down a fix?

Now it doesn't seem to complain about creating the database anymore:
$ sudo docker-compose run --rm -e RAILS_ENV=production web rake db:create
Password:
Starting local_db_1_e6351c097e85 ... done
Starting local_tango_1_b01116f87ab0 ... done
app_autolab_development already exists

Huh, looks like sudo was the error. Are any of the other rake db: commands working? I haven't found  a fix, but at this point, it looks like it's already created the database and you can proceed with the migration.

I ran the migrate command earlier and it executed without any errors: https://gist.github.com/natea/e504f66320e719a2fb99dfc192a2a897
It's the autolab:populate that is still giving the permission denied error. https://github.com/autolab/autolab-oneclick/issues/18


chore: use chainsaw wait operation

Use chainsaw wait operation.
NOTE: this potentially fixes a bug, timeout was not honoured.

@RealAnna i have a better one coming 😋


Use native python print function in trik studio

Download:
Environment: QT=5.12, ARCH=32, CONFIGURATION=release, QTIFW=C:\Qt\Tools\QtInstallerFramework\3.1


"World Time" Widget

If you enable the widget "World Time" while the setting "Always am/pm" is off the whole watchface crashes. Some more info, Amazfit Pace with stock US rom <IP_ADDRESS>, italian language set into watchface settings, time format 24-hour.

Except from the reported problems, some more improvements where requested for this feature:
A more stable global timer displaying standard UTC/GMT
Example:

I didn't notice any crashes in the latest code state, so I am reporting the lattest updates/fixes on this feature in general:

World time proper SLPT update fixed
Now is based on GMT zones

Commits 9974f3a82bc944c4e2ff4e4f77beade5a469779c , d56e1c6fe1651bdae852ba8bff0bac9580c768fe


PR: Add cron job for cancelling old builds

Description of Changes

[ ] Wrote at least one-line docstrings (for any new functions)
[ ] Added unit test(s) covering the changes (if testable)

[ ] Included a screenshot or animation (if affecting the UI, see Licecap)

Issue(s) Resolved

Fixes #
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: @goanpeca

Until this is merged we cannot check it works 🤷 @ccordoba12

You mean the cron job can't run in a PR?

You mean the cron job can't run in a PR?

Correct

Ok, will merge after I release 4.1.3.


virtcontainers: add firecracker initrd support

Add the ability to boot a firecracker VM using an initrd instead of a
block device.
Fixes: #2093
Signed-off-by: Marco Vedovati<EMAIL_ADDRESS>

More info here: https://github.com/firecracker-microvm/firecracker/pull/1246

@marcov any updates on this PR? Thx!

I am still waiting for https://github.com/firecracker-microvm/firecracker/pull/1246 to be merged in master. Once done, I'll resume this.

@marcov This needs a rebase. Do you think you will be able to work on this? If not we have someone else take over this PR.

Hey, firecracker does finally support loading initrd!
But a.t.m. code is just in master, so I'm waiting for 1. a fc release, and 2. for that release to be used by Kata.
If it bothers you to keep this PR open, feel free to close it and can just resume when all dependencies are satisfied :-)

@marcov ping. Any updates? Thx

Hi~ @marcov
Firecracker in kata has been updated to v0.21.1, which included the support for booting with an initial RAM disk image. In case you wanted to resume. ;)

Thank you @Pennyzct , @raravena80 for the ping.
I resumed working on that and I'm mostly done, just need to figure out how to deal with this "workaround":
https://github.com/kata-containers/runtime/blob/6e398f7c715a9b1960a9fa490f4d2650f5567a05/virtcontainers/device/drivers/block.go#L95-L101
The assumption is not holding when using initrd (where no block device for the VM rootfs is passed), so the block device ID index of the container rootfs is off by 1.

I think this can now be reviewed @kata-containers/runtime.
I would need some guidance for adding integ / e2e tests for firecracker + initrd :-)

/test

/test

As an easy action, I nudged a rebuild of the 18.04 fc CI at least.. http://jenkins.katacontainers.io/job/kata-containers-runtime-ubuntu-1804-PR-firecracker/
@marcov - when convenient, give us an update - if you are still able to work on this, and will be rebasing/pushing an update?

Luckily rebasing was easy :D. Let me know if there's anything broken that I need to fix
/test

Looking fine, apart from the ARM and fc CI's. I wonder if @Pennyzct might be able to help figure those out?

@marcov Ping - What do you want to do with this one? It needs some rebasing. AFAIU, the initrd support in firecracker was merged.

Rebased, and I'd like to get this merged.
Nobody so far showed a strong interest on this feature, and I did not push hard enough to get it merged upstream.
It would be helpful to ping the right fols ;-)

/test

@marcov, considering CI is happy, I'll merge this one for our final 1.13.0  release.
However, I think, I really think, this should be forwarded port to https://github.com/kata-containers/kata-containers and I promise you the review there will come faster.  Would you have the time / energy / interest to do so?


multipleQueries should be in lite client

Hello,
We are using the search features and want to use the lite client, however, the multipleQueries method is not available in it while it is still a search feature.
How can we use the search lite client to optimize our bundle size, could the multipleQueries be added in it and how ?
Thanks in advance
Related issues: https://github.com/algolia/algoliasearch-client-javascript/issues/1421

It seems it is present in algoliasearch-lite.esm.browser.js ,  but the typing is wrong.

the method search exists, which is preferred over multipleQueries, does that solve your use case before the typings would be updated?

Hello, no we have to patch-package in order to solve our use case because:

Typing for lite vesrion is wrong, the lite version include multipleQueries but not it's typing
browser field use umd imports while our react-native is web ios and android, and can use ESM

This is our PR: https://github.com/pass-culture/pass-culture-app-native/pull/3523
The patch package consist of editing in node_modules those files :

node_modules/algoliasearch/lite.js
node_modules/algoliasearch/index.js
node_modules/algoliasearch/dist/algoliasearch.umd.js
node_modules/algoliasearch/dist/algoliasearch.cjs.js
node_modules/algoliasearch/dist/algoliasearch-lite.umd.js

With new content (with or without dist prefix depending on the file):
/* eslint-disable functional/immutable-data, import/no-commonjs */
const algoliasearch = require('./dist/algoliasearch-lite.esm.browser.js');

/**
 * The Common JS build is the default entry point for the Node environment. Keep in
 * in mind, that for the browser environment, we hint the bundler to use the UMD
 * build instead as specified on the key `browser` of our `package.json` file.
 */
module.exports = algoliasearch;

/**
 * In addition, we also set explicitly the default export below making
 * this Common JS module in compliance with es6 modules specification.
 */
module.exports.default = algoliasearch;

We haven't found another way to do so for both iOS Android and Web.
It was possible to fix the web only using Webpack resolve.alias configuration, because UMD file is bigger than ESM when builded, but this didn't solve the issue for the native app.
I suggest to keep the issue open until this matter is resolved.

Hey, closing since this should be addressed in v5.


Windows UCRT Redist DLL version is not deterministic

The openjdk make/autoconf logic correctly finds the VS2022 vcruntime location. But the UCRT logic finds the “Windows Retail location”, which I think depends on the particular Windows you have installed, and when you installed it, or possibly the first VS you may have installed.
This means we are not distributing a managed version of the UCRT, rather whatever happens to be in the Windows Kits\10\Redist standard retail location on the particular build machine.

Although it is true that

we are not distributing a managed version of the UCRT, rather whatever happens to be in the Windows Kits\10\Redist standard retail location on the particular build machine.

We do manage the Windows OS images that are used on build machines, so it indirectly influences which runtime libraries will be packaged. That said, since they are part of our product redistributable I think it would be preferable to explicitly define them in the OS install and build configuration.


how to get embing vec for unseen document

average word embding or?

Hello,
After Training the model, how do I generate the vectors for the unseen test?


Remove no longer needed hacks that enable spacebar scrolling in Firefox (issue 3498)

Note: We probably want to hold off merging this a few days (or maybe a week), to ensure that the upstream patch sticks. ~~Edit: https://bugzilla.mozilla.org/show_bug.cgi?id=915962#c14.~~
Now that bug 915962 has landed, we no longer need any hacks to enable spacebar scrolling in Firefox.
Fixes #3498.

/botio-linux preview

Thank you! Confirmed with Nightly that this is working and the patch has been merged almost a week ago upstream, so we should be good.


Include Epinio in https://suse-projects.github.io/

We need to submit a PR here: https://github.com/suse-projects/source
Check the README and other PRs to see how

Strange. Epinio project was already created but was missing the website link. Added the website link - https://github.com/suse-projects/source/pull/26


Add profile likes and recent likes

Fixes #134
Creator

[x] Build relevant tests if any apply
[x] Ensure there are no new warnings
[x] Upload an animated GIF showcasing the solution (if it applies)
[x] Set a relevant reviewer

Reviewer

[ ] Run test and make sure all tests pass
[ ] Review function and form on iOS
[ ] Review function and form on Android
[ ] Review function and form on Web
[ ] Review new test logic

These only add the queries used for the profile. Content queries are coming from mongo so we'll need to build an integration for that on Heighliner. I'll put that in a separate issue.


fix: make Assignment 7 and the grading sheet match

In the last question,

Now change the prior for the $\sigma$, residual parameter(s), to a $\text{Gamma}(1,1)$. What happens? Why?

I added the following clarification:

Report the mean and 90% CI for the mean ($\mu$) of the quality measurements of the sixth machine.

Moreover, I made the grading question Q8 say the sixth machine so that it's comparable with the previous task

the posterior for mu for machine 6 has 90% credibility intervals close to ...

And added the following 1 point grading question

In f), is a reasonable explanation given?

Does this make sense?
Also, can you upload general_info_rstan.tex so that I don't need to comment it out.

Will fix!


:recycle: Feat(tx): Add ImpersonatedTx class

Description
Concise description of proposed changes
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

#1081  👈
main

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

Join @roninjin10 and the rest of your teammates on  Graphite


Repl.it Issue

I am aware of the repl.it video on the wiki and the steps are no longer working. I will try and update wiki new video to support it :)

Updated Github Codespace wiki

Hi, I followed all the steps, but at the end it says,
@Nicolee0129 ➜ /workspaces/texas-dps-scheduler (main) $ npm run start

<EMAIL_ADDRESS>start
ts-node --transpile-only src/index.ts
sh: 1: ts-node: not found
How do i fix this?

@Nicolee0129 , switch to terminal and try to enter npm install then enter. then try the run code button again. If not delete the repl.it and redo it. If not try Github Codespaces tutorial ;)

Thank you so much, but unfortunately the dps nearby are all not available
within 30 days lol.
On Wed, Feb 28, 2024 at 2:27 PM Duy Pham Le @.***>
wrote:

@Nicolee0129 https://github.com/Nicolee0129 , switch to terminal and
try to enter npm install then enter. then try the run code button again.
If not delete the repl.it and redo it. If not try Github Codespaces
https://github.com/phamleduy04/texas-dps-scheduler/wiki/Installation#github-codespaces
tutorial ;)
—
Reply to this email directly, view it on GitHub
https://github.com/phamleduy04/texas-dps-scheduler/issues/101#issuecomment-1969861558,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGRE6AEWWTZLFSWCTA64TDTYV6HKXAVCNFSM6AAAAABDV3K2R2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRZHA3DCNJVHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

you have to keep the bot running since spots will open randomly throughout the day

Ohhh okay~~ thank you so much!
On Wed, Feb 28, 2024 at 3:04 PM Duy Pham Le @.***>
wrote:

you have to keep the bot running since spots will open randomly throughout
the day
—
Reply to this email directly, view it on GitHub
https://github.com/phamleduy04/texas-dps-scheduler/issues/101#issuecomment-1969913446,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGRE6AEAG3AEQGOMIYEXQRTYV6LUPAVCNFSM6AAAAABDV3K2R2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRZHEYTGNBUGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

/usr/bin/env: ‘node’: No such file or directory

getting the below error, while trying to run it
/usr/bin/env: ‘node’: No such file or directory

I think I got the problem this morning also. Seems like DPS's server has some issue. Try again later I guess.

Is this normal?
[07/30/2024 12:54:17] WARNING -> Got 504 status code
[07/30/2024 12:54:17] ERROR:
504 Gateway Time-out

504 Gateway Time-out
Microsoft-Azure-Application-Gateway/v2

[07/30/2024 12:54:47] WARNING -> Got 504 status code
[07/30/2024 12:54:47] ERROR:
504 Gateway Time-out

504 Gateway Time-out
Microsoft-Azure-Application-Gateway/v2

/home/runner/texas-dps-scheduler-1/node_modules/undici/lib/dispatcher/client-h1.js:622
util.destroy(socket, new HeadersTimeoutError())
^
HeadersTimeoutError: Headers Timeout Error
at Timeout.onParserTimeout [as callback] (/home/runner/texas-dps-scheduler-1/node_modules/undici/lib/dispatcher/client-h1.js:622:28)
at Timeout.onTimeout [as _onTimeout] (/home/runner/texas-dps-scheduler-1/node_modules/undici/lib/util/timers.js:22:13)
at listOnTimeout (node:internal/timers:569:17)
at processTimers (node:internal/timers:512:7) {
code: 'UND_ERR_HEADERS_TIMEOUT'
}

I am getting this error in GH codespaces:
WARNING -> Got 403 status code
WARNING -> Got rate limited, sleep for 10s...
Any idea on how to solve?

I'm also getting the
WARNING -> Got 403 status code
WARNING -> Got rate limited, sleep for 10s...
did anyone find a solution?

I'm also getting the
WARNING -> Got 403 status code
WARNING -> Got rate limited, sleep for 10s...
Any info on how to resolve?


feat: add agETH token

Adding Kelp's agETH config to whitelist on ITS.

Hi @Olanetsoft, am I able to call these tokens on L2s as axl_agETH ? Is that convention fine ?

Hi @Olanetsoft, am I able to call these tokens on L2s as axl_agETH ? Is that convention fine ?

Any reason for doing this?

We have a canonical token called agETH or wagETH on these L2s. Wouldn't want axelar tokens to be called with the same name.

We have a canonical token called agETH or wagETH on these L2s. Wouldn't want axelar tokens to be called with the same name. @Olanetsoft

@galacticminter I see. You can't rename the token agETH on a chain, i see that's what its registered as here. You won't be able to change the chain name on the chain itself. ERC20s don't support something like a changeName function.
Alternatively, if you have a UI, you can map the proposed name to the name on-chain, e.g., `"agETH": "axl_agETH," so that any time someone tries to load agETH, you can show on your UI the axl-prefixed name.

Sounds good @Olanetsoft
Could you please approve & merge this?

@galacticminter, one last thing. Could you please add your coingecko id ? eg. "coinGeckoId": "your-id".

@galacticminter on the Squid front end they'll be displayed using a prettySymbol, that we can edit as you like. Please let me know the preferred symbol on each chain

Please use the pretty symbol as axl_agETH

Please use the pretty symbol as axl_agETH

Sounds good. In Squid we are switching to the standard agETH.axl is that ok with you? We think it reads much better and is consistent with other bridge notations, such as USDC.e for ESDU bridged from ethereum native bridge

Please use the pretty symbol as axl_agETH

Sounds good. In Squid we are switching to the standard agETH.axl is that ok with you? We think it reads much better and is consistent with other bridge notations, such as USDC.e for ESDU bridged from ethereum native bridge

@ecdsafu - Jake from our BD team confirmed with theirs that your proposal is okay. Do you need to reflect that symbol here or do you have a separate mapping elsewhere that does that? If the latter, I will merge this PR rn

Please use the pretty symbol as axl_agETH

Sounds good. In Squid we are switching to the standard agETH.axl is that ok with you? We think it reads much better and is consistent with other bridge notations, such as USDC.e for ESDU bridged from ethereum native bridge

@ecdsafu - Jake from our BD team confirmed with theirs that your proposal is okay. Do you need to reflect that symbol here or do you have a separate mapping elsewhere that does that? If the latter, I will merge this PR rn

Friendly bump @ecdsafu ^


Allow the consul addr to be configured

When I try to run mesos-consul I'm unable to specify the location of consul, it seems to want to connect to consul as if it's running on a mesos master node. It would be great if I could specify consul-addr <IP_ADDRESS>, looks like consul-port is already supported.

In order to get a service registered with the correct node in Consul's catalog, it has to be registered with an agent running on the same node as the service. Otherwise all of the services are listed as being on the consul master node and a failed service check affects the consul server instead of the node the service is running on.

@ChrisAubuchon that explains it, I was just testing and didn't have agents running on all hosts which had mesos tasks. Thanks.

It would be really helpful if this was spelled out somewhere. Adding a paragraph or two on how this should be deployed would be very helpful.

So if i have a mesos cluster of say 300 nodes i need to setup consul on every single one? This seems like an insane waste to me.

This is part of the consul design. It is expected to run an agent on every node so that registrations and health checks are performed locally.

just put it in your slave chef/puppet/etc. script that creates the node. It actually simplifies things since you can count on it being there, and helps with multi-data-center functions.

True, seems to be a little bit of an issue bridging the gap between using consul with docker/mesos/marathon vs just using it in a VM which is incredibly simple.

The issue is with how Consul registers services. If you have a service running on Mesos agent A and you register that service with a central Consul server, the Consul server becomes the "owner" of the service. So if the consul server is taken out of service, then the service that is running on the is marked as unavailable. If you try to specify the mesos agent as the "owner" while registering at the Consul server, the created service is cleaned up by anti-entropy.


4.2.15 released but not in master or develop

Latest in setup.py is 4.2.14.
Tip: Would suggest to only have one master branch (remove develop) and then branch off into major release branches if you want to patch up older releases.

Agree with all your points - closing this just as 4.2.15 has been replaced by a newer version for some time


Legitimately Registered Through GitHub, But Have Been Removed

What's the deal Keybase? I followed your rules, and I have been on GitHub long enough. Are you going to fix this, and re-include people that are legit?

Stellar is a shitcoin. I am just glad it shined light on this amazing app.
I was looking for something like this for years! I got kicked out of airdrop as well but I don't care.

I disagree with your opinion on the coin, but the app is rather nice. IBM & Franklin Templeton seem to like it, as well. I certainly hope they work this out better than they have so far.

Same

I registered on September 10th and I even informed friends about keybase and that with a Github account they still can take part at the airdrop!
If that is the final word, than Keybase' and Stellar's reputation will be irreparable damaged.
Trustworthiness is everything, especially in finance and data-security
How can I  trust a company that isn't even capable to filter out scammers, that they'll be able to protect my important data?
The upswing in Stallar (re)gained me more than $500 in the last 24h.. I'm not just here for those lousy airdrop. But this business conduct isn't acceptable.

Same here.  Its ridiculous! Is it so hard to filter scammers? I think People who have github accounts can protect their data...

Hey everyone. So I was digging in, and I think it's just new registration, at least I'm hoping so. I went to https://keybase.io/a/i/r/d/r/o/p/spacedrop2019 and it showed my user as still registered for the drops. Might want to check it, and see what it returns. It'll show on the bottom of the page, where it uses the UID to address the reader.


Only provide Prometheus metrics at specific endpoint /metrics

Only provide Prometheus metrics to single HTTP route /metrics, this makes it easier for other routes to be expanded by other HTTP services.
// Create a local server to serve Prometheus metrics
export const server = http.createServer(async (req, res) => {
    if (!req.url) return;
    if (req.method == "GET") {
        if (req.url === "/metrics") {
            res.writeHead(200, { 'Content-Type': prometheus.registry.contentType });
            return res.end(await prometheus.registry.metrics());
        }
    }
});

Added in commit: https://github.com/pinax-network/substreams-sink/commit/9ffa81024dd133c6ccacc3cd4084f8cb64d4a9ad

Published new release


Add custom asdict for dataclasses

Description
#1098

Related Issues

Checklist

[ ] Is this code covered by new or existing unit tests or integration tests?
[ ] Did you run make test successfully?
[ ] Do new classes, functions, methods and parameters all have docstrings?
[ ] Were existing docstrings updated, if necessary?
[ ] Was external documentation updated, if necessary?

Additional Notes or Comments

Codecov Report
Attention: 53 lines in your changes are missing coverage. Please review.

Comparison is base (cbe6b32) 78.22% compared to head (1fe2999) 81.02%.
Report is 61 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1108      +/-   ##
==========================================
+ Coverage   78.22%   81.02%   +2.79%
==========================================
  Files         101       98       -3
  Lines        6351     6434      +83
==========================================
+ Hits         4968     5213     +245
+ Misses       1383     1221     -162

Files
Coverage Δ

superduperdb/__init__.py
100.00% <100.00%> (ø)

superduperdb/__main__.py
71.42% <100.00%> (ø)

superduperdb/container/component.py
82.92% <100.00%> (+2.92%)
:arrow_up:

superduperdb/container/encoder.py
89.83% <100.00%> (ø)

superduperdb/container/serializable.py
98.00% <100.00%> (+2.87%)
:arrow_up:

superduperdb/db/filesystem/artifacts.py
75.86% <100.00%> (ø)

superduperdb/db/mongodb/artifacts.py
80.00% <100.00%> (ø)

superduperdb/server/client.py
75.18% <100.00%> (-0.18%)
:arrow_down:

superduperdb/server/server.py
83.05% <100.00%> (-0.15%)
:arrow_down:

superduperdb/container/artifact.py
96.36% <92.85%> (-1.51%)
:arrow_down:

... and 10 more

... and 5 files with indirect coverage changes

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


How can I use a wildcard in a content assertion

Hi,
I guess this is not directly related to testinfra (more python stuff or pytest stuff), but I did not know how to do this, so :
I would like to use a wildcard inside a content assertion, something along :
 assert (host_ip + '\t\t' + fqdn + '*' + hostname) in content
is it possible at all or is it not in the pytest philosophy and I am handling this the wrong way ?
Thanks

Hi, this is indeed a python question.
I think you can write:
assert content.startswith(host_ip + '\t\t' + fqdn)
assert content.endswith(hostname)

or use the regexp module
import re
assert re.match('^{}\t\t{}.*{}'.format(host_ip, fqdn, hostname), content)

Arf the 'endswith', I should have though about this ....
Thanks a lot for the regexp insight, and for answering a question that is not directly related to this product.


No line breaks in source code of logging messages

In order to find messages printed in logs, one shall be able to search for the whole string in the IDE, e.g. "TEST_DEPLOYMENT: IDS-Message is sent without a valid DAT, will not be sent...". But this String is not found, due to a line break in the source code:
See src/main/java/de/fraunhofer/ids/messaging/core/daps/aisec/AisecTokenManagerService.java
log.warn(
    "TEST_DEPLOYMENT: IDS-Message is sent without a valid DAT, "
    + "will not be sent in PRODUCTIVE_DEPLOYMENT. [reason=({})]", error);
}

I will create a PR in which we will introduce error codes according to the following scheme, these error-codes can be searched for accordingly:
Log Error Codes

format: IMS-XY-L-1234
-> short: IMSXYL1234

IMS = IDS-Messaging-Services
XY = Subsystem Module (CO Core, AP AppStore, BR Broker, CL ClearingHouse, ME Messaging, PA Paris, VO Vocol)
L = Event Severity (E Error, W Warn, I Info, D Debug)
1234 = Error number

will e.g. print as [code=(IMSCOE0001)]  -> IDS-Messaging-Services Core-Module Error 0001


Make LineEdit underlines thinner in the editor theme

This also fixes a typo in the code that disables the bottom rounded corners.
Note: Not cherry-pickable to the 3.x branch as this only pertains to the new editor theme.
Preview
Before

After

Alternative (not included in this PR)
Alternatively, we may want to keep the rounded corners at the bottom while making underlines thinner. It would look like this:

The suggested alternative with rounded bottom corners looks good to me, but I don't have a strong opinion. The implemented version is fine too.

I agree, the rounded bottom corners seem to fit better with the other elements in the editor.

^ How it looks like in 4.0.2
This recent PR also touched this part: #75823


Connections.json

I have a few questions on the purpose of Connections.json.
PASopa.exe doesnt seem to consider this file when packing up the canvas application.
We have been using DevOp Pipelines to Automate our build processes across environments and tenants as well. The pipeline works great with using solutions, connection references, and environment variables.
However! The only issue (that hasnt been built out by Microsoft yet) is the SQL Server AAD Authentication (connection reference/environment variable).
Within DataSources/* and Connections.json files for SQL Tables/Connection. We can see the server,db however when we modify this to point to a different db within the same server. PASopa does not mention the checksum for Connections.json
When importing the PowerApp still points to the old version. Which makes me wonder if this is a Protected file from Microsoft on server side. If we add say another table manually, the Application after import recognizes the new datasource however it says appDataSourceConfig.
We have also tried deleting Entropy.json, Connections.json to see if we could force the app (on initial bootup) to reconfigure itself to pull these values in.
It just seems strange that if we completely remove all references to the old database, package, and import. Microsoft is able to revert back to old values which makes me wonder if Microsoft is Caching and overriding this file (connections.json)
Related #259, #216

@mitchellromanuik , I'll do my best to answer this and provide some general information. If you have a specific example of the change you're making that might help me to provide more detailed feedback.
My understanding of the Connections.json and how it works is that it holds reference information to a Power Platform Connection. Ultimately, that Power Platform Connection is what determines the link between your Power App and the Data Source. Changing the data within the Connections.json or related Data Source file may have some impact on the information shown, but if it is still pointing to the same Power Platform Connection, it will continue to resolve to that Connection.
For example, if I had the following Connections.json:
  {
    "e771971d-7763-4c4d-b0d1-e88649d6c2c6": {
      "connectionParameters": {
        "database": "example-db",
        "privacySetting": "None",
        "server": "example-server.com"
      },
      "connectionRef": {
        "authenticationType": "sqlAuthentication",
        "displayName": "SQL Server",
        "iconUri": "https://example.com/icon.png",
        "id": "/providers/microsoft.powerapps/apis/shared_sql",
        "sharedConnectionId": "/providers/microsoft.powerapps/apis/shared_sql/connections/3b10ee7359694a4fa2d7b45fd7761d51"
      },
      "datasets": {
        "example-server.com,example-db": {
          "dataSources": {
            "TestTable1": {
              "tableName": "[dbo].[TestTable1]"
            }
          }
        }
      },
      "dataSources": [
        "TestTable1"
      ],
      "dependencies": {},
      "dependents": [],
      "id": "e771971d-7763-4c4d-b0d1-e88649d6c2c6"
    }
  }

I can change the connectionParameters.database and connectionParameters.server values, or the underlying dataset, but when this Power App is opened the Connection established is determined by the reference to the Connection that exists within the Power Platform (in this case, the connectionRef.sharedConnectionId.)
I'm not particularly familiar with SQL Database Connections, so perhaps there is a difference in the expected behavior, but I believe that the best course of action would be to avoid modifying the Connections.json information. As it exists today, this file is meant to preserve Connection information during the pack/unpack process and not for manually establishing connections in offline editing.

Closing this for now - please feel free to re-open if you have any additional questions or concerns.


where Uplink frame-counter and Downlink frame-counter restore in postgres

Is this a bug or a feature request?
request
What did you expect?
Uplink frame-counter and Downlink frame-counter in postgres
What happened?
What version are your using?
How can your issue be reproduced?
Could you share your log output?

They are stored as part of the node-session in LoRa Server.

I have found that it restored in redis. thank you


Locked at old version of formtastic

formtastic-plus-bootstrap (>= 0) ruby depends on
  formtastic (~> 2.2) ruby

Yet, 3.1.3 is out.

@tibbon formtastic 2.3 breaks this gem.
I switched to simple_form + bootstrap 3 because it's too hard to maintain this gem for new versions of formtastic and bootstrap.
If you make formtastic 3 + bootstrap 3 adaption I can place link to your fork in readme.


Update index.md

Proposed changes

What: In the public doc, added new section as FAQ
AWS S3 destination connection error “Multiple instance of AWS S3 are not allowed for this source"
Before inspecting the AWS S3 configurations (i.e.: IAM role and trust policy), it’s worth checking if you already have an S3 destination connected to the source in question. Segment only supports one AWS S3 destination per source.
Why: The customer wanted to add multiple instance of the AWS S3 for the same source, which is not possible.
Zendesk:
https://segment.zendesk.com/agent/tickets/533718
https://segment.zendesk.com/agent/tickets/510242
Slack: https://twilio.slack.com/archives/C8AA794FN/p1706136425243499
Merge timing

Related issues (optional)

@pthorat-twilio if this PR is ready for review, please move it from draft to ready for review and tag someone from your own department to check accuracy.

Hi @pthorat-twilio - I'm happy to review this again after you accept/reject the suggestions I made on the last review. If you have any questions/concerns about the suggestions, I'm happy to address them with you!

Hi @forstisabella Do I just need to "Commit Change" if I am happy with the change, is that correct? I just committed all the changes. Please let me know what's the next step of action. Sorry, this is first time I am making the change using GitHub.

Hi @forstisabella Do I just need to "Commit Change" if I am happy with the change, is that correct? I just committed all the changes. Please let me know what's the next step of action. Sorry, this is first time I am making the change using GitHub.

No worries! Yes, you go through each change in the UI and either "commit suggestion" or "resolve conversation". If a member of the docs team has approved your PR, generally once you go through and approve/reject each suggestion you can merge the PR!

@forstisabella are there any action pending from my end?

nope, I'll go ahead and merge. Thanks! @pthorat-twilio


Remove unused build dependency HFuse

Thanks for this! Yeah, I've just been stapling this together and didn't realize this was still here. I'll upload this to hackage too so people won't be pinged to install the dev headers. Thanks!


build: add cscope support

This will create a new target in the Makefile, allowing devvers to enjoy cscope
utility just by typing 'make cscope'.
'make clean' will also clean up the intermediate cscope files.
Signed-off-by: Liu Yuan<EMAIL_ADDRESS>

thanks!


Disable HTTP2 for metrics and the results server

Let's use HTTP 1.1 in these cases to mitigate the risk of resource
consumption through streams.

cc: @xiaojiey


Implement std::error::Error for writer::Error

This should improve internal debugging.
Naturally writer::Error should also implement std::fmt::Display.

Fixed in 5c76a168bfe49774a8692fa2cf5a30353bb01651


add jasonsanta.xyz

https://jasonsanta.xyz
53.1kb uncompressed
https://gtmetrix.com/reports/jasonsanta.xyz/rfBjEggF

Welcome to the 250kb Club!
The direct URL will be https://250kb.club/jasonsanta-xyz

Is there anything I can add to my website? Like some kind of sticker or do just a link to the 250kb website?

Do you want a sticker? I saw that the 512kb club has badges. Is that something you'd like to have?

@jason123santa how about one of these?

yeah that works thanks


release/1.5.0

Checklist

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

@conda-forge-admin, please rerender

@luca-martial  @sugatoray can you review and merge it .


Error with "screen" command

When i try to use the "screen" command, it gave me this error below. How do I fix it?

same here


⚠ Bofrost.de has degraded performance

In 37c25d1, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1624 ms

Resolved: Bofrost.de performance has improved in 7f7e0fe.


Allow getting control focus owner from the scene tree

Godot version:

Godot v3.1
OS/device including version:

Windows 10
We should be able to get the focus owner from the scene tree because right now the only way to get the focus owner of any control node is to create or find a control node in the scene and then call the get_focus_owner function.

The focus owner is actually referenced in Viewport, yet not exposed.

#34269 adds a signal emitted when focus changes, providing the focused Control, so I assume that would be sufficient if it gets merged.

Aaand it got merged.
@Flairieve Is gui_focus_changed(control) signal enough to close this? You can connect to it to receive the focused control, but the downside is that you can't poll for the focus owner at any time.

I think we could just expose Viewport's _gui_get_focus_owner as a public method (without _ prefix).

Would be nice @akien-mga, to expose that method!
Also a "gui_focus_lost" signal could be useful in Viewport, since the gui_focus_changed(Control) does not emit NULL when focus is lost.
I am making a node that needs to know the focus owner, but doesn't have access to Control nodes.

It looks like this was implemented in
https://github.com/godotengine/godot/pull/57517
and
https://github.com/godotengine/godot/pull/92573.
So feel free to close.


Update gorethink from v3 to v6 and rename to proper rethinkdb-go package

Gorethink is currently on v6 this is a bump to the v3 client to consume the latest client as well as update required dependencies by the v6 library as well.

It appears there are existing linting errors for gosec.

Ah I think gosec did some updates recently and we are not pinning the version.

Oh, ignore the mattproud testdata comment; I don't think it's referencing it (looking again)

Looks like that issue was fixed in v1.0.1, so updating it to v1.0.1 should address it; https://github.com/matttproud/golang_protobuf_extensions/compare/v1.0.0...v1.0.1
Can you also run go mod vendor ? Because it looks like revendoring with go mod removes a number of files:

root@2f91fcfa08c9:/go/src/github.com/theupdateframework/notary# go mod vendor
root@2f91fcfa08c9:/go/src/github.com/theupdateframework/notary# git status
Refresh index: 100% (1727/1727), done.
On branch gorethink_v6
Changes not staged for commit:
  (use "git add/rm <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	deleted:    vendor/github.com/google/certificate-transparency-go/x509/root_darwin_arm_gen.go
	deleted:    vendor/github.com/google/certificate-transparency-go/x509/x509_test_import.go
	deleted:    vendor/github.com/lib/pq/oid/gen.go
	deleted:    vendor/golang.org/x/sys/unix/mkasm_darwin.go
	deleted:    vendor/golang.org/x/sys/unix/mkpost.go
	deleted:    vendor/golang.org/x/sys/unix/mksyscall.go
	deleted:    vendor/golang.org/x/sys/unix/mksyscall_aix_ppc.go
	deleted:    vendor/golang.org/x/sys/unix/mksyscall_aix_ppc64.go
	deleted:    vendor/golang.org/x/sys/unix/mksyscall_solaris.go
	deleted:    vendor/golang.org/x/sys/unix/mksysctl_openbsd.go
	deleted:    vendor/golang.org/x/sys/unix/mksysnum.go
	deleted:    vendor/golang.org/x/sys/unix/types_aix.go
	deleted:    vendor/golang.org/x/sys/unix/types_darwin.go
	deleted:    vendor/golang.org/x/sys/unix/types_dragonfly.go
	deleted:    vendor/golang.org/x/sys/unix/types_freebsd.go
	deleted:    vendor/golang.org/x/sys/unix/types_netbsd.go
	deleted:    vendor/golang.org/x/sys/unix/types_openbsd.go
	deleted:    vendor/golang.org/x/sys/unix/types_solaris.go
	deleted:    vendor/golang.org/x/text/unicode/bidi/gen.go
	deleted:    vendor/golang.org/x/text/unicode/bidi/gen_ranges.go
	deleted:    vendor/golang.org/x/text/unicode/bidi/gen_trieval.go
	deleted:    vendor/golang.org/x/text/unicode/norm/maketables.go
	deleted:    vendor/golang.org/x/text/unicode/norm/triegen.go
	modified:   vendor/modules.txt

D'oh! That may be because I ran it on Go 1.13. sigh.

Looks like it's still failing on that permission error 😞
I also noticed these errors;
find: unknown predicate `-not -path './bower_components/**' -not -path './node_modules/**' -not -path './vendor/**''

Could it be that we're using busybox, and that busybox's find doesn't support these?

Looks like it's still failing on that permission error 😞
I also noticed these errors;
find: unknown predicate `-not -path './bower_components/**' -not -path './node_modules/**' -not -path './vendor/**''

Could it be that we're using busybox, and that busybox's find doesn't support these?

This change shouldn't be affecting busybox though right?

@thaJeztah I believe the buildscripts/circle-validate-vendor.sh script which invokes buildscripts/validate-vendor.sh ends up touching the go.sum file

Go is updated now, this needs a rebase and should fix the go.mod issue.

Go is updated now, this needs a rebase and should fix the go.mod issue.

Thanks @justincormack it did ineeded 👍

@HuKeping ptal 🤗


sync os pragma won't work on M1 mac

🐛 Describe the bug
// @sync os pragma won't work on M1 mac.
🌴 Visual Studio Code Version : 1.65.2
🌴 Code Settings Sync Version : 3.4.3
🌴 Standard or Insiders : Standard
🌴 Portable or Installed : Installed
🌴 OSS or Official Build : Official Build
🌴 Operating System : macOS Monterey 12.3(M1)
🌴 Occurs On: startup
🌴 Proxy Enabled: No
🌴 Gist Id: Not relevant I think, will be added if needed
📰 To Reproduce
Steps to reproduce the behavior:

Open settings.json and comment out as follows
// @sync os=windows
"python.pythonPath": {windowsPath}
// @sync os=mac
"python.pythonPath": {macPath}
Save and restart the vscode
See if the line that contains {windowsPath} gets commented out automatically

💪 Expected behavior
The line belonging to // @sync os=windows should be commented out
📺 Console Error Log
None

Any news? I catch this bug in windows and mac.


Updating wiki after the merge new connection handling (PR#1)

The underlying connection to the server has been slightly changed after #1 and knows rely more o direct interaction between the R script and the MYSQL server. For now, as the port in BIAD main server aren't open, this means more reliance on ssh tunnels. The wiki should be modified to reflect that (and update the explanation for creating a tunnel)

Wiki now updated accordingly in the Rconnect section


Typo "VS code"→"VS Code"

https://docs.microsoft.com/en-us/power-bi/developer/visuals/environment-setup?tabs=windows

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@hyoshioka0128,
Thanks for spotting this typo and fixing it!


#3203 render tex errors in red instead of throwing

kick jenkins

OK looks like the file has been added but the throwOnError wasn't added so I am still not getting red errors from bad tex in a text cell.  (make a text cell and put in $\asdfasdf$).

I am still getting a popup for a syntax error like:
a TeX cell that has just a {
in this case, it should leave the input unchanged, format it red, and put a tooltip on it with the text of the error message from katex.

error in text cell is not handled the same, it should format as much as possible like TeX cells do:

also the main tutorial is giving an TeX error popup about indexOf not being defined...

Kick jenkins

https://pub.beakernotebook.com/publications/66fbe76c-6f7e-11e6-b0b9-8fe2204af9ff
I am still getting a popup error from a TeX cell with just a {
and in a text cell a syntax error like that should be formatted in red.
and still need this to pass jenkins.
and please add this to top of the file:
copied from https://github.com/Khan/KaTeX/tree/master/contrib/auto-render
until https://github.com/Khan/KaTeX/issues/425 is resolved.

kick jenkins

kick jenkins

instead of the popup, should generate a proper error like this:

except "unknown unexpected token" should be replaced with the error text from katex which now appears in the popup.

kick jenkins


Suggestion

I suggest relocating the X-Ways Checkbox to be next to the user data to quickly enable/disable. This would allow users who want everything except X-Ways to more easily identify the checkbox under a subcategory since having it enabled requires user data.

Second suggestion would be to include Everything from Voidtools as this tool can benefit in finding tools or files locally while also doubling other purposes like malware analysis or regex/wildcard file searches on mounted drives.

Hey @Jonesckevin , regarding the X-Ways box movement, it's a good idea. I'll review how this is going to take shape.
As for the Voidtools, I've already added it to the Winrepo, and will give it a shot in the upcoming release.

Sounds good!!

@Jonesckevin RC 12 has been released which addresses the X-Ways suggestion. The display is now dynamic and no longer static, allowing for a live update of available tools.


installation: database init for any host

BETTER Adds default priviledges for database user to access from any
host.

Signed-off-by: Jiri Kuncar<EMAIL_ADDRESS>--
cc @hachreak @crepererum
PS: It's going to maint-2.0.

Working on docker.


Update docker image

I haven't updated the docker image with the last few tags. I also need to change the base image to be swift instead of this unmaintained sourcekit image. I believe sourcekit is now part of the normal swift image.

Done in 1.0.0


Keyboard shortcut with quoted command gives invalid nix config

Hey, first of thanks for this plugin. Really makes managing my gnome state easier :)
I encountered a bug just now where I've added a keyboard shortcut:
<Super>space --> gnome-terminal -e "vim --cmd startinsert"

This fails to apply in the nix configuration:
building the system configuration...
error: undefined variable 'vim'

       at /nix/store/n3w211g7700r9d2h58qqj2fjs5hri2xq-source/home/dconf.nix:280:38:

          279|       binding = "<Super>space";
          280|       command = "'gnome-terminal -e "vim --cmd startinsert"'";
             |                                      ^
          281|       name = "Launch scratchpad";
(use '--show-trace' to show detailed location information)

Seems like quotes aren't escaped?

Definitely,
$ dconf dump /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom2/
[/]
binding='<Super>space'
command='gnome-terminal -e "vim --cmd startinsert"'
name='Launch scratchpad'

Thanks for taking a look at this!


Adding large SDKs to the library-and-framework-list.json

Is your feature request related to a problem? Please describe.
Adding the AWS SDK for Java 2.0 to the library-and-framework-list.json is difficult because it is made up of 418 separate artifacts. Adding each one individually would be annoying and bloat the file for other users.
Describe the solution you'd like
Allow the artifact field to include a * "artifact": "software.amazon.awssdk:*"
Describe alternatives you've considered
Writing out 418 separate enteries
Additional context
Add any other context or screenshots about the feature request here.
This was my first draft at the addition
  {
    "artifact": "software.amazon.awssdk:*",
    "description": "AWS SDK for Java 2.0",
    "details": [
      {
        "minimum_version": "2.16.1",
        "metadata_locations": [
          "https://repo1.maven.org/maven2/software/amazon/awssdk/"
        ],
        "tests_locations": [
          "https://github.com/aws/aws-sdk-java-v2/tree/master/test/sdk-native-image-test"
        ],
        "test_level": "community-tested"
      }
    ]
  }

Hi Mark,
Let's follow up on this. So far, the JSON is used to generate the table on this website, so I don't see a reason why we can't allow wildcards for the artifact ID. If you could open a PR with the entry you'd like to add, we can adjust the schema accordingly. Thanks!


com.intuit.karate.resource.ResourceUtils.findFeatureFiles, *.getResource are unable to find feature files using Windows paths

mac or linux

open command prompt
cd ~
git clone https://github.com/karatelabs/karate-npm
npm install
npm run test "/Users//karate-npm/karate/httpbin.feature:3"
notice feature file is found and test passes as reflected in attached image

windows

open command prompt
cd /d %userprofile%
git clone https://github.com/karatelabs/karate-npm
npm install
npm run test "c:\Users<your profile name>\karate-npm\karate\httpbin.feature:3"
notice feature file is not found and test fails as reflected in attached image

tagging as help wanted - a good opportunity for those who want to get started with contributing to open-source / karate

I have no option but to "guess" a fix for this. if anyone can test, that'll be great

It works on Windows! Thanks @ptrthomas and @kirksl !

1.3.0 released


Loading authenticated Images

For most cases we can simply fill out an image component with:
{
  "type": "image",
  "url": "<A_PUBLIC_IMAGE_URL>"
}

However, sometimes the image assets are protected and require authenticated requests. I made a branch to make this work, which adds a new attribute 'header' for image components, which will attach the header when making a request to the image asset:
{
  "type": "image",
  "url": "<A_PROTECTED_IMAGE_URL>",
  "header": {
    "Authorization": "Basic dne9ns0dlanengensDEhd="
  }
}

I tried to make it consistent with rest of the syntax but if anyone has a better idea on how to represent this in JSON, please feel free to share ideas. Here's the branch: https://github.com/Jasonette/JASONETTE-iOS/tree/authenticated_image

For basic auth, I believe that providing the credentials via the URL should be enough<EMAIL_ADDRESS>Now, being able to provide extra headers when needed is a great feature anyway. This gives us better control over how we communicate back to our servers.

Resolved with https://github.com/Jasonette/JASONETTE-iOS/commit/9010fcdb8979b1ea3bf44316091fd3152abc785e

This works for both image components and (image type) button components using the newly introduced header attribute.
Also it automatically attaches the header from session in case there's an existing session with the domain.

Here's the syntax:

Image component

{
  "type": "image",
  "url": "<A_PROTECTED_IMAGE_URL>",
  "header": {
    "Authorization": "Basic dne9ns0dlanengensDEhd="
  }
}

image type button component

{
  "type": "button",
  "url": "<A_PROTECTED_IMAGE_URL>",
  "header": {
    "Authorization": "Basic dne9ns0dlanengensDEhd="
  }
}


importlib problems

I think your approach is very interesting and wanted to try it myself. When setting up the repository I encountered following problem:
File "C:\Users\jk267\DFormer\utils\train.py", line 116, in
config = getattr(import_module(args.config), "C")
File "C:\Users\jk267.conda\envs\dformer\lib\importlib_init_.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1050, in _gcd_import
File "", line 1027, in _find_and_load
File "", line 1006, in _find_and_load_unlocked
File "", line 688, in _load_unlocked
File "", line 883, in exec_module
File "", line 241, in _call_with_frames_removed
File "C:\Users\jk267\DFormer.\local_configs\NYUDepthv2\DFormer_Large.py", line 4, in
C.backbone = "DFormer-Large"  # Remember change the path below.
NameError: name 'C' is not defined
I think I may have some package problems, because of not installed packages or libs. Are the installations in readme point 0 all I need and do you have an idea what I could do?
Thank you for your response beforehand.

Thank you for your attention to our work!
It appears that our code behaves differently on a Windows system. Since we do not have access to a Windows machine with graphic cards, it is challenging for us to reproduce this issue. Therefore, we propose two potential solutions:

Change the following line:
https://github.com/VCIP-RGBD/DFormer/blob/3dd8a45fb1e294b2c39f0664c66eaeeb385aaa47/train.sh#L10
to

PYTHONPATH="$(dirname $0) \"

as the PYTHONPATH structure might be different on Windows.

If the above approach doesn't resolve the issue, there's another workaround. You can manually copy the code from local_configs/_base_/__init__.py and local_configs/_base_/datasets/NYUDepthv2.py into local_configs/NYUDepthv2/DFormer_Large.py. This will create a single large config file. Then, rerun the code.

If the above methods still do not solve the problem, please provide more information so we can try to address the issue.

I apologize for the late answer.
We did change the line with
PYTHONPATH="$(dirname $0)/..":"$(dirname $0)":$PYTHONPATH \
and it worked out.
Another thing we noticed was, that there were problems when using only 1 GPU, because the local rank is not set then.
We added
else:
self.local_rank = int(os.environ['LOCAL_RANK'])
self.devices = [0, 1]  # parse_devices(self.args.devices)
in engine.py line 67, 67, 69 and it seems to work out this way.


[infra]: failing bundle req

Ref -> https://github.com/babel/website/issues/2138#issuecomment-560116963
https://packd.now.sh/ not working

https://bundle.run/@babel/polyfill@7 is now working


Add hot loader to redux-bootstrap-example

Enable hot loader in the example. This issue is blocked by #17.

Done by https://github.com/remojansen/redux-bootstrap-example/commit/27775385d0647a8288db442bfe02bfb01c2005d3 (needs server side routing to fully work)


Support embedding fonts for SVG, HTML and PDF

How can I embed fonts when exporting to SVG or PDF format? I know I can use image formats instead, but sometimes I really need a vector format file with fonts embedded.
https://desk.draw.io/a/tickets/35437

"It would be nice if one could embed custom fonts into the exported files. I just created a three page document with a custom font, and would have to either export a PNG (awkward format for this kind of doc) or restyle the whole document.
For HTML export, I realize local fonts are not always available, but one could prompt the user for a URL (e.g a googlefonts location).
EDIT: this feature would also make it easy to use draw.io to make slide decks! So bonus feature is to also add screen resolution canvas sizes to the list of defaults."

The file gets bigger, but neither Inkscape nor Safari can actually see the embedded font.


building this docker image from Windows OS: lanelet_core stuck

Dear Lanelet devs,
I downloaded and I am bilding this image from the windows command prompt. This is the command corresponding to catkin build. It gets stuck at lanelet_core forever.
Starting  >>> mrt_cmake_modules
Finished  <<< mrt_cmake_modules                     [ 0.1 seconds ]
Starting  >>> lanelet2_core
[build - 14.9] [1/10 complete] [6/6 jobs] [0 queued] [lanelet2_core:make (60%) - 21.1]
[build - 34.5] [1/10 complete] [6/6 jobs] [0 queued] [lanelet2_core:make (60%) - 44.1]
[build - 01:24.3] [1/10 complete] [6/6 jobs] [0 queued] [lanelet2_core:make (60%) - 01:34.1]
[build - 05:03.0] [1/10 complete] [6/6 jobs] [0 queued] [lanelet2_core:make (60%) - 05:12.3]

If I force it to build it using only one core catkin build -j 1 lanelet_core succeeds but lanelet_python is not stuck.
Can you try on Windows and see what happens ?

wrong page. sorry


Add sitemap and robots file to improve SEO

Added sitemap file

Added robots file

run pnpm build - build success ✅

use https://seocheckup.vercel.app/sitemap?q=https://trypear.ai/sitemap.xml to check sitemap/metadata after deployment

How to test sitemap: check /sitemap.xml

Big! thank you sm


grass: pin to python 3.11

Description of changes
Pin to Python 3.11 since wxpython is not yet compatible to Python 3.12.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Thanks, fixed qgis-ltr.

qgis-ltr still fails. But this is not due to the update of the python version but the update of gqgis to 3.34.8: https://hydra.nixos.org/job/nixpkgs/trunk/qgis-ltr.x86_64-linux. Thus unrelated to this PR.

I QGIS is building successfully even without this PR on Hydra.

I am not sure why QGIS-LTR fails. It was building successfully at the moment of 3.34.8 update.

QGIS is building successfully even without this PR on Hydra.

Then it maybe was the gdal update? Not sure judging by hydra.

@imincik I disagree because right now QGIS doesn't work at all. With this PR at least qgis works. I don't know why qgis-ltr fails but this PR improves the situation.

The be more precise: Without this PR, qgis fails to evaluate:
error: wxpython-4.2.1 not supported for interpreter python3.12

With the grass changes qgis builds but fails to start.
With the gross and qgis changes from this PR, qgis works. qgis-ltr fails in the same way with or without the changes in this PR but the changes are necessary until wxpython supports python 3.12.

but the changes are necessary until wxpython supports python 3.12.

I am not able to investigate now, but we have python312Packages.wxpython.
Will have a look ASAP.

I am not able to investigate now, but we have python312Packages.wxpython.

Which fails to evaluate. :smile_cat:

@fpletz , @globin qgis-ltr should be fixed in https://github.com/NixOS/nixpkgs/pull/326550 . Please review if you can.


Terragrunt asks to create backend if credentials expired

When using an AWS profile and the credentials have expired, terragrunt does not notify the user that their credentials have expired.  Instead, it suggests that the backend does not exist or is inaccessible, and asks the user if it should be created, which can be misleading.
For example, when running terragrunt apply with expired credentials:
$ terragrunt plan
...
Remote state S3 bucket tf-state does not exist or you don't have permissions
to access it. Would you like Terragrunt to create it? (y/n)
^C

Compared to terraform in the same scenario, which gives more helpful information:
$ terraform plan
Failed to load backend:
Error configuring the backend "s3": ExpiredToken: The security token included
in the request is expired
	status code: 403, request id: xxx

Good point. We should show the underlying error to make that clearer. PR very welcome!


Change times to bigints

Codecov Report

Merging #20 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #20   +/-   ##
=======================================
  Coverage   66.93%   66.93%
=======================================
  Files           8        8
  Lines         490      490
=======================================
  Hits          328      328
  Misses        154      154
  Partials        8        8

Impacted Files
Coverage Δ

db/db.go
41.6% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Fixed #29985 -- Added ModelAdmin.list_prefetch_related

https://code.djangoproject.com/ticket/29985
This PR adds ModelAdmin.list_prefetch_related and ModelAdmin.get_list_prefetch_related().

Closing as per ticket.


Color contrast in light mode is bad

Hi! I stumbled upon your great website, and noticed the color contrast in light mode is bad:

Chrome DevTools' CSS overview suggests the same:

Dark mode looks fine, but not everyone prefer it (especially since that's not the default most of the time).

Hi there!
Thank you for bringing this to my attention.
I have resolved this issue with the commit 0271ad8. The contrast should (hopefully) be easy on the eyes now.


make dataset info updatable

[ ] I added an entry to CHANGELOG.md if knowledge of this change could be valuable to users.

Here is a brief summary of what I did:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

-93 of 215 (56.74%)  changed or added relevant lines in 8 files are covered.
19 unchanged lines in 11 files lost coverage.
Overall coverage decreased (-0.05%) to 90.392%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

services/src/api/model/responses/datasets/errors.rs
0
7
0.0%

services/src/datasets/postgres.rs
12
31
38.71%

services/src/api/handlers/datasets.rs
101
125
80.8%

services/src/pro/datasets/postgres.rs
0
43
0.0%

Files with Coverage Reduction
New Missed Lines
%

services/src/api/handlers/layers.rs
1
88.87%

services/src/api/handlers/tasks.rs
1
97.91%

services/src/api/handlers/workflows.rs
1
90.28%

services/src/datasets/external/pangaea/mod.rs
1
83.19%

services/src/pro/api/handlers/permissions.rs
1
95.44%

services/src/pro/api/handlers/users.rs
1
96.74%

services/src/pro/datasets/external/sentinel_s2_l2a_cogs.rs
2
86.11%

services/src/pro/layers/postgres_layer_db.rs
2
94.96%

services/src/pro/projects/postgres_projectdb.rs
2
89.46%

services/src/pro/contexts/postgres.rs
3
96.96%

Totals

Change from base Build<PHONE_NUMBER>:
-0.05%

Covered Lines:
127297

Relevant Lines:
140828

💛  - Coveralls

 [DEVOPS-434] Manager: Editieren der General Info


Fix user profile email

This will truncate longer emails in the user info popovers by chopping and adding an ellipsis.
Fixes: #7567.

This fixes up #7698 to apply styling to the .message-info-popover by applying another commit to apply the previous code to both overlays. This can be squashed or on its own; it doesn't regress the codebase at any point.
Good to merge @showell.

merged, thanks @brockwhittaker


Use the Http4sOrgSitePlugin for publishing microsite

It's the first follow-up after #97 😄

This one is pretty straightforward, so merging


new image processors: blend, compositing

Adds blending/compositing(macOS) processors. Allows easily blend/compositing.
For example, I was needed to blend unedited images which have the different background color so they will appear blended with the background color of my interface.

Also, I changed macOS version to 10.11 to successfully build and run.

@yemodin Looks great.
However, if we increase the minimal deploy target, we have to release another major update since it breaks compatibility. May I know which API you are using is 10.11 above?
And do not worry about the failing tests. If we could add this processor to the framework, I will check and fix these tests.

@onevcat I changed only demo project target, not framework target. Next lines of macOS demo require 10.11+:

Also, I added the test to each image processor. And made the pull request for image assets:
https://github.com/onevcat/Kingfisher-TestImages/pull/1

Oh, cool! I will check it now.


Use EventLoopExtWebSys::spawn in bevy_winit

See https://github.com/rust-windowing/winit/issues/1714 for the relevant discussion, but the TLDR is that EventLoopExtWebSys::spawn provides a work around for the hack of using an exception to get the event loop working on the web platform.
https://github.com/rust-windowing/winit/pull/2208 is included in winit 0.27.0 which is included in Bevy 0.9, however, bevy_winit is current not using this feature.
Other related issues: https://github.com/rust-windowing/winit/issues/900 https://github.com/rust-windowing/winit/issues/1199

I haven't investigated this yet, but @bjorn3 pointed out the following on Discord:

It (EventLoopExtWebSys::spawn) also isn't compatible with the App::run interface as App::run allows dropping the App after it returns


Can I define the cube inner texture for each side ?

This example show a simple demo for texture for many cubes. But the texture  is a repeated in the cube and looked from the outside. Can I define the cube inner texture for each side? the camera should be in the inner of the cube.
Thanks
`from vedo import dataurl, show, Cube
cubes = Cube()
cubes.texture(textures_path+'up.jpg'))
cubes.texture(textures_path+'down.jpg'))
cubes.texture(textures_path+'left.jpg'))
cubes.texture(textures_path+'right.jpg'))
show(cubes).close()`

Hi, no, it cannot work that way! you need to specify a single texture map and provide uv-coordinates..


Add files via upload

please review and confirm. I have added my school to the list and added the requested file as requested.

@surikata11 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
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

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

Hello,
I am providing the requested information as follows:

Official website: https://www.b2.eu/
Official address and name: B2 d.o.o., Tržaška cesta 42, 1000 Ljubljana
Official website of my study program, where the goal is to complete my studies: https://www.vspv.si/sl/studijski-programi (I am currently enrolled in: https://www.vspv.si/sl/poslovna-informatika)
Official email (from which I am writing to you): https://e-studij.eu/show.aspx?xid=WBT:Xhttps://e-studij.eu/show.aspx?xid=WBT:X:Home

If you need anything else, please feel free to let me know.

From: Philip Torchinsky @.>
Sent: Thursday, August 8, 2024 7:15 AM
To: JetBrains/swot @.>
Cc: Matic Kocijančič @.>; Mention @.>
Subject: Re: [JetBrains/swot] Add files via upload (PR #22314)
@surikata11https://github.com/surikata11 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
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

—
Reply to this email directly, view it on GitHubhttps://github.com/JetBrains/swot/pull/22314#issuecomment-2274968307, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BGBAXQ27CQSXFEBIGBRLQDTZQL5GXAVCNFSM6AAAAABL5BGUJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZUHE3DQMZQG4.
You are receiving this because you were mentioned.Message ID: @.***>

@surikata11  Thank you for the clarifications. Pull request merged. Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


Fix a typo in docker-cluster controller

Signed-off-by: Chuck Ha<EMAIL_ADDRESS>/assign @fabriziopandini
What this PR does / why we need it:
this PR fixes the DockerCluster's Watch on Cluster objects.
I also changed some imports to be more in line with the new import style.
Special notes for your reviewer:
Release note:
NONE

/close


Can we make Translation type compatible with string ?

Hi,
First of all, thank you for your package ✨ ! It's great to see other libs emerging for i18n that perform better.
I was wondering if it was possible to make the Translation type compatible with the string type?
Example with a dropdown component which take a string label :
{
  label: t('See'),
  icon: 'i-lucide-eye',
  click: () => showSalarySlip(row.id)
}

The error is Type [unkown] is not assignable to type [string].
I am therefore obliged to add an assertion type: t('See') as string

need full ecaample

<script setup lang="ts">
const items = [
  [{
    label: t('See'), <!-- here : Type [unkown] is not assignable to type [string] -->
    icon: 'i-lucide-eye',
    click: () => showSalarySlip(row.id)
  }]
]
</script>

<template>
  <UDropdown :items="items" />
</template>

I need a complete example project, with settings and dependencies, so that I can understand something