Figure out if moving to net40 is a good thing

Yeah, best issue title ever. This is just a placeholder so I remember to do some digging.
For alpha8, the dependencies are this:

For alpha9, they became this:

Yes I know, dnx46 is based on full .NET Framework 4.6. I wonder if I need to have multiple TFMs in the library now.

lol. Interesting issue.
The only problem I foresee with the net40 tfm is people trying to use it outside of dnx (which the library might appear to support). Being agile, I suggest we wait and see if anyone raises an issue as such. Otherwise, I don't see their being any problems.
I'd have preferred to use a netstandard1.* (dotnet5.*+1) moniker but our dependencies don't support it. I suspect there are actually only a few TFM's that we can use due to the dependencies. (.Net3.5 - .Net4.5.1?).

I think I just had an allergic reaction to seeing .NET 4 in this shiny new DNX library.
What dependencies prevent netstandard? You'd think I'd know, but I don't think we have any blockers...?
I think we can move to a netstandard TFM when it's available. It's not working yet (waiting on NuGet tooling), but looks like they are aiming for support in RC2. The current guidance is:

The earliest .NET Framework to support a .NET Platform Standard version is .NET Framework 4.5.

... which is netstandard1.1, but I'd rather limit to just 4.5.1/4.5.2 with netstandard1.2.

You can use netstandard in rc1 under the caveat it's called dotnet, the major is 5 instead of 1, and the minor is 1 higher than the netstandard version. :laughing:
What that translates to is actually simpler than I've described:
netstandard1.0 -> dotnet5.1
netstandard1.1 -> dotnet5.2
etc.
However, you'll find SpecFlow 1.9.0 doesn't support any of these currently (hit this issue last night when implementing the dnx451 support). SpecFlow doesn't appear to support much in the way of netcore and therefore isn't available to the netstandard tfm's.

Well, if I haven't looked at this yet, I don't care about it enough. Can always reopen to investigate later.


Add setuptools as a package dependency

The setup.py file is used to generate scripts. The generated scripts
create a runtime dependence on the setuptools, thus these must be
installed on the target system where the code is supposed to run.

Current coverage is 98.32% (diff: 100%)

Merging #347 into master will not change coverage

@@             master       #347   diff @@
==========================================
  Files            38         38
  Lines          2925       2925
  Methods           0          0
  Messages          0          0
  Branches        145        145
==========================================
  Hits           2876       2876
  Misses           43         43
  Partials          6          6

Powered by Codecov. Last update 14a50a6...2a6112a

Wrong branch will sent new PR against devel


from tensorflow.python.data import Dataset  ModuleNotFoundError: No module named 'tensorflow.python.data'

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (windows 10):
TensorFlow installed from (source or binary):
TensorFlow version (cpu 1.2.1):
Python version: 3.6.2

ModuleNotFoundError                       Traceback (most recent call last)
 in ()
----> 1 from tensorflow.python.data import Dataset
ModuleNotFoundError: No module named 'tensorflow.python.data'

@Auroratan
Please provide part of the code which is throwing error.
Please try import tensorflow.data.Dataset(). Let me know what you get. thanks

@jvishnuvardhan
Thank you for your help！ I know my mistake, because the version of tensorflow is 1.2, it is a version problem, I used conda install tensorflow=1.12.0 to solve my problem.

@Auroratan Thanks. I will close this.


operator hive-operator (1.2.3904-e25c14f)

Update Hive community operator channel(s) [['alpha']] to 1.2.3904-e25c14f
/hold

/unhold

/merge possible

/merge possible

/merge possible

/merge possible


change test-report output directory

Proposed Changes
what?
I propose these changes to move the test-result file output directory to /Users/user/.maestro/tests/*/report.xml instead of the root folder.
why?
Since the generated files from test execution are stored at /Users/user/.maestro/tests/*, I think it'll be easier to find the test result if it's stored in the same location.
result

I missed that an old PR I had for this got closed waiting for some feedback from me.
I've reopened it as #1748 which makes exactly the same change as you've got here, but makes it optional, and avoids accidentally deleting the contents if you set a custom path like $HOME

@depapp I'm not sure if I followed your goal with this PR. We already have the --output flag that you can use to save the report file. Isn't that enough for your use case?
This PR actually removes the functionality of that flag, so I don't get it

@depapp I'm not sure if I followed your goal with this PR. We already have the --output flag that you can use to save the report file. Isn't that enough for your use case?
This PR actually removes the functionality of that flag, so I don't get it

@felipevolpone Actually, the goal of this PR is to change the default location of the generated test report to the same location as other generated files (like screenshots and maestro.log).
I am aware that Maestro has the --output option to save the report file. However, if I use that option, I cannot place the test report file in the same folder as those other files because the folder name includes a timestamp.
With this change, we can ensure that all related outputs are in the same folder, which greatly simplifies organization and accessibility.
If this PR doesn't make sense, feel free to close it 🙇🏻


[NSE-29]support mul-key sort without codegen

What changes were proposed in this pull request?
This pr supports a non-codegen version of mutiple-key sort using std::function.
fixes #29
How was this patch tested?
locally tested

@zhouyuan verified on TPC-DS/H queries.
When comparing performance,

setting "spark.sql.columnar.codegen.sort" as false will disable codegen.
"spark.sql.columnar.nanCheck" should be false, for nan is not supported in non-codegen sort.

@zhouyuan nan support is added to this pr

notes: the framework for non-codegen sort is ready, we'll continue improve the performance in future pr.


FE-1174 Feature/unit tests cache service

Why?
Unit Tests for the CacheService.
How?
Added a unit test for each different function and created some helper classes in order to improve code readibility.
Testing
Ensure that the unit tests have a 100% success rate (can be found as a workflow run in this PR).

Summary by Bito
This pull request introduces comprehensive unit tests for the CacheService class and related components. It includes new test files, updates existing ones, and makes minor modifications to the main code. The changes aim to improve code coverage, ensure reliability, and achieve a 100% test success rate for the CacheService implementation.

Code change type: Tests, Refactoring

Unit tests added: True

Estimated effort to review (1-5, lower is better): 4

AI Code Review is in progress (usually takes <3 minutes unless it's a very large PR).

Changelist by Bito
This pull request implements the following key changes.

Key Change
Files Impacted

Testing - Add Unit Tests for CacheService

- DeviceOTADataSource.kt - Updated method call to setDeviceLastOtaTimestamp with timestamp parameter

- UserPreferenceDataSource.kt - Renamed analytics-related methods and updated timestamp setting

- UserPreferencesRepository.kt - Updated method call to getAnalyticsDecisionTimestamp

- CacheService.kt - Refactored methods, added new methods, and updated existing ones

- TestConfig.kt - Added new imports and mock configurations

- DeviceOTADataSourceTest.kt - Updated test cases for setDeviceLastOtaTimestamp

- UserPreferenceDataSourceTest.kt - Updated test cases for analytics-related methods

- UserPreferencesRepositoryTest.kt - Updated test cases for getAnalyticsDecisionTimestamp

- CacheServiceTest.kt - Added comprehensive unit tests for CacheService

- InMemoryTest.kt - Added helper class for testing in-memory cache operations

- PrefsSingleVarTest.kt - Added helper class for testing SharedPreferences operations

Testing - Comprehensive Unit Tests for CacheService

- PrefsStringEitherTest.kt - Added new test class for string-based SharedPreferences operations

- DeviceOTADataSource.kt - Updated method call to setDeviceLastOtaTimestamp with timestamp parameter

- UserPreferenceDataSource.kt - Renamed analytics-related methods and updated timestamp setting

- UserPreferencesRepository.kt - Updated method call to getAnalyticsDecisionTimestamp

- CacheService.kt - Refactored methods, added new methods, and updated existing ones

- TestConfig.kt - Added new imports and mock configurations

- DeviceOTADataSourceTest.kt - Updated test cases for setDeviceLastOtaTimestamp

- UserPreferenceDataSourceTest.kt - Updated test cases for analytics-related methods

- UserPreferencesRepositoryTest.kt - Updated test cases for getAnalyticsDecisionTimestamp

- CacheServiceTest.kt - Added comprehensive unit tests for CacheService

- InMemoryTest.kt - Added helper class for testing in-memory cache operations

- PrefsSingleVarTest.kt - Added helper class for testing SharedPreferences operations

Code Review Agent Run #d0cda9

AI Based Review: ✔ Successful

High-level Feedback
The addition of comprehensive unit tests is commendable and will significantly improve the reliability of the CacheService. However, there are several areas that require attention. The error handling and null safety in the DeviceOTADataSource interface and CacheService methods need to be standardized. Consider using Either consistently and avoiding nullable default values. Additionally, address potential race conditions in asynchronous operations by using commit() instead of apply() or implementing proper callback mechanisms. Lastly, enhance test cases to cover edge scenarios, particularly for empty string tokens in authentication methods. These improvements will further strengthen the codebase's robustness and security.

Actionable Issues

:page_facing_up: app/src/main/java/com/weatherxm/data/datasource/DeviceOTADataSource.kt

Issues: Total - 1, High importance - 1

Line 5-5

🔴 High importance - 1

:page_facing_up: app/src/main/java/com/weatherxm/data/services/CacheService.kt

Issues: Total - 3, High importance - 3

Line 115-115

🔴 High importance - 1

Line 271-271

🔴 High importance - 1

Line 280-280

🔴 High importance - 1

:page_facing_up: app/src/test/java/com/weatherxm/data/datasource/DeviceOTADataSourceTest.kt

Issues: Total - 2, High importance - 2

Line 39-39

🔴 High importance - 1

Line 85-85

🔴 High importance - 1

:page_facing_up: app/src/test/java/com/weatherxm/data/services/CacheServiceTest.kt

Issues: Total - 1, High importance - 1

Line 58-93

🔴 High importance - 1

:page_facing_up: app/src/test/java/com/weatherxm/data/services/InMemoryTest.kt

Issues: Total - 1, High importance - 1

Line 35-35

🔴 High importance - 1

AI Code Review powered by
Note: Introducing Bito’s AI Code Review Agent in your IDE. Get on-demand feedback with context as you code in JetBrains or Visual Studio Code. Catch issues early, improve code quality, ship faster — all before you get to PR. Learn more

AI Code Review is in progress (usually takes <3 minutes unless it's a very large PR).

Changelist by Bito
This pull request implements the following key changes.

Key Change
Files Impacted

Testing - Add Unit Tests for CacheService

- DeviceOTADataSource.kt - Updated method calls to CacheService

- UserPreferenceDataSource.kt - Renamed analytics-related methods

- UserPreferencesRepository.kt - Updated method call to UserPreferenceDataSource

- CacheService.kt - Refactored methods and added new functionality

- TestConfig.kt - Added imports and mock configurations for testing

- DeviceOTADataSourceTest.kt - Updated test cases for DeviceOTADataSource

- UserPreferenceDataSourceTest.kt - Updated test cases for UserPreferenceDataSource

- UserPreferencesRepositoryTest.kt - Updated test cases for UserPreferencesRepository

- CacheServiceTest.kt - Added comprehensive unit tests for CacheService

- InMemoryTest.kt - Added helper class for testing in-memory cache operations

- PrefsSingleVarTest.kt - Added helper class for testing SharedPreferences operations

Testing - Add Comprehensive Unit Tests for CacheService

- DeviceOTADataSource.kt - Updated method calls to CacheService

- UserPreferenceDataSource.kt - Renamed analytics-related methods

- UserPreferencesRepository.kt - Updated method call to UserPreferenceDataSource

- CacheService.kt - Refactored methods and added new functionality

- TestConfig.kt - Added imports and mock configurations for testing

- DeviceOTADataSourceTest.kt - Updated test cases for DeviceOTADataSource

- UserPreferenceDataSourceTest.kt - Updated test cases for UserPreferenceDataSource

- UserPreferencesRepositoryTest.kt - Updated test cases for UserPreferencesRepository

- CacheServiceTest.kt - Added comprehensive unit tests for CacheService

- InMemoryTest.kt - Added helper class for testing in-memory cache operations

- PrefsSingleVarTest.kt - Added helper class for testing SharedPreferences operations

- PrefsStringEitherTest.kt - Added helper class for testing string-based Either operations in SharedPreferences


blender: Switch to fetchFromGitea

Description of changes
Splitting up #257780, part 1 (I'm probably going to rewrite some of it, now that I know a bit more about nixpkgs)
This switches from building with a source tarball to cloning the repository directly. From what I understand, this is common practice, but it's a lot slower.
This is a much smaller change so hopefully it doesn't get stalled like my last attempt.
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

[x] 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.05 Release Notes (or backporting 23.05 and 23.11 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

[ ] Fits CONTRIBUTING.md.

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

@ofborg build blender blender.passthru.tests.render

@ofborg eval

@ofborg build blender blender.passthru.tests.render

Turns out that's not what I wanted - I don't know how to cancel it, I apologize for taking up the resource

I'm gonna update this and then get the module up as well, closing

Dang it wrong PR

There are more files than just scripts/addons absent in release tarball vs. Git. Most are irrelevant, but some are important. Notably release/datafiles/assets (from blender-assets repo). We at least need those to be viable.

Turns out they are using submodules and LFS for assets, lib, and tests (blender commit, arch issue)
As fetchLFS isn't implemented on fetchFromGithub (and therefore fetchFromGitea), I'll change the implementation to fetchgit.

Finally, Blender’s (tarball) build process is quite complex, and I worry about missing something in the future. To be clear: this isn’t me saying “this is a bad idea”, but rather: I’m not totally sure which direction is better.

To be honest, I don't either, so I asked on the matrix server. nevivurn made a good point that if the release servers ever go down, it's easier to get the git repo rather than the specific tarball.

If we don't use LFS, I could just add the respositories needed - looking at arch pkgbuild, there's three additional repos to include.


Using on backend under proxy

Is there any way to use a proxy for all request in this library?

Hi @oboloka, look over the domain property that is assignable when creating a DirectLine object. I spoke with a colleague who suggested it is possible to factor in a proxy by use of "domain" but he also said it would likely be a fairly sizable lift to make happen.
In essense, the "domain" property acts as a kind of redirect which may allow you the ability to build in a proxy.

Hi, @stevkan
Thanks for your answer!
To be honest, I don't want to implement another proxy server. I would rather prefer to use custom clients with http.Agent implementation that connects to a specified proxy server (e.g. https-proxy-agent).
I do see the possibility to pass properties for clients (WebSocket and ajax, but it's not documented):
const bot = new DirectLine({       secret: mySecret,       WebSocket: myWebSocketWithProxy,       ajax: myClientObservableWithProxy,     });
But it doesn't work out of the box. I had to override some methods in DirectLine to make it work.
Maybe it makes sense to have support for this case?

Hi @oboloka,
Using the domain property does not necessitate your needing to implement another proxy server. The domain property simply allows you to specify an alternate destination for your web chat traffic to flow to. In this way, you can continue to use the proxy server you already have setup.
I'm been advised by one of our Direct Line devs that this is, in fact, the best approach for you to go forward. In short, you would use the domain property to point your Web Chat traffic to your proxy server. At the proxy server level, you will send out the API call to retrieve the Direct Line response (i.e. the token, conversationId, streamUrl, etc.). The streamUrl is the important item here as you will need to overwrite the wss://directline.botframework.com/v3/... endpoint with the websocket endpoint you have configured. This can then point to the actual Direct Line websocket endpoint to complete the circle.
Hope of help!


Use the polytype python API to read input data for models

Short Description of the issue
The polytope API can be used to read input data needed to run the models for DT Flood Early Warning and DT Flood Climate Impacts.
Here we explore using the API in our workflow.

notes from meeting with Thomas

could consider reading data from polytope to rucio to benefit from smart caching etc. --> action for WP5?
also need to think about link between DCache, rucio and polytope.

action

discuss with Paul / Dijana

notes from meeting with Andrea

smart caching in rucio done at file level not on "loading subset of data into memory" level.

is the client smart enough to cache the data? When we download the data each time using polytope.

[ ] action could be to access data from DestinE using polytope API from interTwin resources and check speeds


Fix #10 #38: Comment out failing migrations

Just applied fixes described in #10 #38.
I did not have any problems using the app after commenting out those lines.

Coverage remained the same at 81.729% when pulling 5ef3741c102123b95a01273afcfb9f6f2b1fe698 on thiagojobson:fix-migrations into 8f1d484348bf1c887d68ddf5a4fded7faaaa3e5f on pygame:master.


Program can't launch due to glibc, on GNU/Linux

I tried to launch circuitblocks' AppImage on NixOS 20.09 but it didn't work. The standard error output gives me this :
A JavaScript error occurred in the main process
Uncaught Exception:
Error: /usr/lib/libc.so.6: version `GLIBC_2.32' not found (required by /tmp/.org.chromium.Chromium.BQVBDl)
    at process.func (electron/js2c/asar.js:140:31)
    at process.func [as dlopen] (electron/js2c/asar.js:140:31)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:922:18)
    at Object.func (electron/js2c/asar.js:140:31)
    at Object.func [as .node] (electron/js2c/asar.js:149:18)
    at Module.load (internal/modules/cjs/loader.js:735:32)
    at Module._load (internal/modules/cjs/loader.js:648:12)
    at Module._load (electron/js2c/asar.js:717:26)
    at Function.Module._load (electron/js2c/asar.js:717:26)
    at Module.require (internal/modules/cjs/loader.js:775:19)
Fontconfig warning: "/usr/share/fontconfig/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"

First, I thought it was owing to NixOS which is quite a special distribution so I checked it on an Ubuntu 18.04 with the AppImage binary as well but also with the .deb package file. And both two gave me the same error.

I have the identical problem, running Ubuntu 20.04.1 64-bit.  I tried the AppImage first, and when that didn't work, tried the .deb package.  Both give the same error.
$ circuitblocks
A JavaScript error occurred in the main process
Uncaught Exception:
Error: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /tmp/.org.chromium.Chromium.V0FhTE)
    at process.func (electron/js2c/asar.js:140:31)
    at process.func [as dlopen] (electron/js2c/asar.js:140:31)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:922:18)
    at Object.func (electron/js2c/asar.js:140:31)
    at Object.func [as .node] (electron/js2c/asar.js:149:18)
    at Module.load (internal/modules/cjs/loader.js:735:32)
    at Module._load (internal/modules/cjs/loader.js:648:12)
    at Module._load (electron/js2c/asar.js:717:26)
    at Function.Module._load (electron/js2c/asar.js:717:26)
    at Module.require (internal/modules/cjs/loader.js:775:19)

I have the identical problem, running Ubuntu 20.04.1 64-bit.  I tried the AppImage first, and when that didn't work, tried the .deb package.  Both give the same error.
$ circuitblocks
A JavaScript error occurred in the main process
Uncaught Exception:
Error: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /tmp/.org.chromium.Chromium.V0FhTE)
    at process.func (electron/js2c/asar.js:140:31)
    at process.func [as dlopen] (electron/js2c/asar.js:140:31)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:922:18)
    at Object.func (electron/js2c/asar.js:140:31)
    at Object.func [as .node] (electron/js2c/asar.js:149:18)
    at Module.load (internal/modules/cjs/loader.js:735:32)
    at Module._load (internal/modules/cjs/loader.js:648:12)
    at Module._load (electron/js2c/asar.js:717:26)
    at Function.Module._load (electron/js2c/asar.js:717:26)
    at Module.require (internal/modules/cjs/loader.js:775:19)

Hello guys. The latest version of CircuitBlocks was compiled agains glibc 2.27, on Ubuntu 18.04, so that should work on both of your machines. You can find it on the releases page. Sorry for the inconvenience.

Hello guys. The latest version of CircuitBlocks was compiled agains glibc 2.27, on Ubuntu 18.04, so that should work on both of your machines. You can find it on the releases page. Sorry for the inconvenience.


export and import lockStatusSetByUser flag [MRXN23-600]

The lockStatusSetByUser scenario PU flag had not been added to piece exporters and importers, leading to loss of this data when cloning scenarios. This change fixes this.
Testing instructions
Set some PUs to excluded, some to available and some to included for a scenario.
Clone the scenario (or its whole parent project). The new copy of the scenario must preserve the statuses set manually in the source scenario.
Feature relevant tickets
https://vizzuality.atlassian.net/browse/MRXN23-600

Checklist before submitting

[ ] Meaningful commits and code rebased on develop.
[ ] If this PR adds feature that should be tested for regressions when
deploying to staging/production, please add brief testing instructions
to the deploy checklist (docs/deployment-checklist.md)
[ ] Update CHANGELOG file

reopening a new PR with correct branch name to link to Jira


Add OSD secret before monitor starts

Commit e1f084 introduced a regression when the bootstrap OSD secret is
stored in encrypted databags (EDB). The problem is that if the first
monitor is started without the bootstrap OSD key in the keyring, a
random OSD secret is generated, which will then not match the
pre-generated one.
The solution is to revert the resource that adds the bootstrap OSD key
to where it was (before monitor starts) but add a condition that ensures
this is only done if EDBs are enabled. When EDBs are not enabled, it is
not necessary to add the bootstrap OSD key to the keyring.

:+1: from the original author of e1f084


Formatting message

Hello (and thank you for this useful package)
I'd like to format a bit my error message.
I was wondering where I was supposed to write down my LERN::setMessage closure, so I put it in my Exceptions/Handler.php file, inside my report method:
if (app()->bound("lern")) {
                app()->make("lern")->setMessage(function ($exception) {
...

Am I doing right ?
I'm also trying to format my exceptions notification message and that's the aim of this issue.
I mainly use slack and I'm trying to beautify a bit the messages.
I tried to create new lines and add some bold such as
$msg .= "*URL*: {$method}@<{$url}>\r\n" . PHP_EOL;

But i doesn't work.
It seems a config flag mrkdwn have to be set to true but I can't figure out how and where I can do it.
Could you help, please ?

Hey @loranger , please give version 3.6.6 a try. Let me know if it fixes the issue with new lines
Yes you are using the setMessage method correctly :-)

That's much better, indeed.
I still miss the slack formatting (kind of minimal markdown) but at least, the reports are definitely readable !
Thank you so much !
By the way, It would be useful to being able to get the id of the current recorded exception from the notification itself.
That would be helpful to add a link to the current full and formatted exception from the notification message.

@tylercd100 is it possible to add markdown support for slack channel, to make the messages more readable?
Basic code formatting like in Cherry-Pie/LogEnvelope package would make messages more readable!

@tylercd100 I still have problems with markdown rendering on the latest version. Markdown markup looks like normal text, any idea how to fix it?


add batch requests support for the vmss.

fix the subnet fields not updated correctly.
add batch requests support for the vmss.

@bingosummer  @gossion  ping :)

@andyliuliming , could you please add more details about batch requests support for the vmss? E.g., what's the problem it fixed? Why it's supported?
In future, we or others can view the PR message to understand why we made this change. :)

@andyliuliming , could you please add more details about batch requests support for the vmss? E.g., what's the problem it fixed? Why it's supported?
In future, we or others can view the PR message to understand why we made this change. :)

updated the commit message. thanks.


[IconButton] Remove style-propable mixin

Cleaned up style argument that prevents unnecessary allocation (comment)

All good :smile:

@newoga Thanks!


proxyState is not iterable

Whenever I use any kind of Dialog, Input, Combobox etc. I am running into this error and the error trace doesn't help at all. I copied the components from the docs and used a createStyleContext I found browsing other issues on here. Using React (NextJS 13).

Fixed by forcing zag-js to be on the exact version of ark-ui. For some reason it had 0.20.0 and 0.12.0 installed somewhere too, absolutely no idea, where this came from.
"resolutions": {
  "@zag-js/store": "0.19.1"
}

in package.json


Taxon matching stops silently with (429) Too Many Requests

Taxon matching stops silently with (429) Too Many Requests resulting in unmatched names. Errors are currently silenced because of https://github.com/ropensci/worrms/issues/38
@bart-v Is there any documentation on rate limits for AphiaRecordsByMatchNames?

It's not formally documented, but there is something like Nettiquette.
If you send more than 180 requests during 10sec you will be blocked for a short time


Add a recognize! combinator

This combinator would take a child parser as argument. If that child parser is successful, it measures how much data was consumed, and returns the consumed slice as output

Fixed in 4b7494a


Multi replay operator (experimental API)

Replay a Multi (turned into a hot stream) to multiple (possibly late) subscribers.
See https://github.com/smallrye/smallrye-mutiny/issues/536 for the initial discussion.

I didn't review the implementation code, but the API and documentation look fine to me. My personal opinion is that replaying the entire stream (unbounded replay) is almost always a bad idea and perhaps the API should not allow it at all, but your choice :-)

I didn't review the implementation code, but the API and documentation look fine to me. My personal opinion is that replaying the entire stream (unbounded replay) is almost always a bad idea and perhaps the API should not allow it at all, but your choice :-)

We had that conversation with @cescoffier at some point, but we ended up realizing that users would expect full replays to be the default, and that at least that would be a good education if they used that operator the wrong way 🤣


NegativeUNL SField Changes

Several declarations in SField are changed so that the symbolic names and the text representations are consistent.
-- the SField declarations are sfDisabledValidator, sfValidatorToDisable, and sfValidatorToReEnable
-- their corresponding gRPC declarations are also changed
-- the related function names are also changed
-- changed negativeUnl to negativeUNL too
Tested with unit test and local network tests.

Changed sfNegativeUNL to sfDisabledValidators


[BUG] my bug is named CORS and I want to squish him

Bug
What is wrong?
CORS error when running locally
How can I, the developer, reproduce this?
Made a branch off of main, ran server and client (dotnet run and npm run dev, respectively) and upon visiting the /blogs endpoint of the Vue app I am receiving CORS errors. It seems there is also a type error that is preventing the blog from rendering at all. I 'fixed' this by creating local 'dummy' data, but this is API-free data, so not really useful.
Acceptance Criteria
Data pulls and blogs display from DB via backend

Added my current code as-is (with styling fixed and dummy data commented out) so you can see how I am arriving at this exactly.

At BlogView.vue:
//! This has had a name change so that it does not get used as data //! By commenting it out the page will run and locally useable dummy data works // const realBlogs: Blog[] = await BlogService.getAllStubs(); // TODO: fix const blogs = [   {     title: "uno",     id: '1',     content: "some content",     description: "yabba dabba doo"   } ]

I checked and this is because your dev branch is out of date with main and is missing the fix
Rebase your branch with main and you will be fine

Your PR says you have merge conflicts which is indicative of being out of date


Add tests for ofcourse new command

Turns out that iCal support breaks the ofcourse new command. This PR fixes the command and adds a test to make sure it at least completes successfully.

@msoucy

What is the offending commit? And how does it break ofcourse new?

The addition of the iCal file copying to ofcourse new in commit 24c34743 causes the new command to try to copy a nonexistent file.
$ ofcourse new
✔ Glorious README
✔ CSS/Javascript for browser art
✔ Starter Mako templates for great good
Traceback (most recent call last):
  File "/home/ryansb/.pyenv/versions/tmpenv-tKdut4PdR0CnD9O/bin/ofcourse", line 9, in <module>
    load_entry_point('ofcourse==0.2.1.post21', 'console_scripts', 'ofcourse')()
  File "/home/ryansb/.pyenv/versions/tmpenv-tKdut4PdR0CnD9O/lib/python2.7/site-packages/click/core.py", line 700, in __call__
    return self.main(*args, **kwargs)
  File "/home/ryansb/.pyenv/versions/tmpenv-tKdut4PdR0CnD9O/lib/python2.7/site-packages/click/core.py", line 680, in main
    rv = self.invoke(ctx)
  File "/home/ryansb/.pyenv/versions/tmpenv-tKdut4PdR0CnD9O/lib/python2.7/site-packages/click/core.py", line 1027, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/ryansb/.pyenv/versions/tmpenv-tKdut4PdR0CnD9O/lib/python2.7/site-packages/click/core.py", line 873, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/ryansb/.pyenv/versions/tmpenv-tKdut4PdR0CnD9O/lib/python2.7/site-packages/click/core.py", line 508, in invoke
    return callback(*args, **kwargs)
  File "/home/ryansb/code/ofcourse/ofcourse/cli/__init__.py", line 85, in new
    os.getcwd(), update=True)
  File "/home/ryansb/.pyenv/versions/2.7.9/lib/python2.7/distutils/file_util.py", line 110, in copy_file
    "can't copy '%s': doesn't exist or not a regular file" % src)
distutils.errors.DistutilsFileError: can't copy '/home/ryansb/code/ofcourse/ofcourse/course.ics': doesn't exist or not a regular file

lgtm :+1:

Blargh. Whoops, sorry.

LGTM :+1:


Control costs = 0 in demo

Hi MJPC team:
When I am running the cartpole demo (https://github.com/google-deepmind/mujoco_mpc/blob/main/python/mujoco_mpc/demos/agent/cartpole.py), I find that the cost term of the control is always 0. Is it as designed?

The weighted control term is small. If you increase the weight (eg, to 1.0) in the GUI you can see this term in the Objective live plot.

Thank you very much for your quick reply!
I am using cartpole.py in the demos. I think the variable cost_terms is achieved from the function get_cost_term_values, which is not weighted. I think the problem comes from the agent.planner_step doesn't update data.ctrl.

It looks like you are correct that we don't set data->ctrl in the gRPC interface with an action from the policy. The mjData object here needs to have the correct ctrl in order for the cost term to be computed correctly.

@mikezhang95 this bug should be addressed with #327.

Thank you for your great work!


It runs very slowly

Great, but it runs very slowly compared to C.
I tested the C and Delphi programs on a system, especially for images captured from a camera.

What was tested?
If the components, then they are made for example. It's very inefficient code. Test examples without components and in the release version.

I only displayed the image through the camera, showing approximately 2 frames per second. However, the speed was good and the image was smooth when using the OpenCV library from https://github.com/Laex/Delphi-OpenCV.


hello-world: add example benchmarking function

This is a great add @robphoenix along the lines of #515 :+1:


sails-linker Grunt task doesn't honor ignored files

Using Sails 0.10.5.
I am trying to prevent specific JS files from being linked into the layout.ejs file. It seems adding a "!" to the start of a file pattern in pipeline.js has no effect (I have tried varying the ordering of the elements too).
To reproduce:

Create a new sails app (e.g. sails new tmpsails)
Edit tasks/pipeline.js and change js/dependencies/**/*.js to !js/dependencies/**/*.js
lift sails and check layout.ejs - you'll see:

    <!--SCRIPTS-->
    <script src="/js/dependencies/sails.io.js"></script>
    <!--SCRIPTS END-->

I expected that moving the exclusion pattern above after the inclusion js/**/*.js would solve the problem, but alas no - it still links in the dependencies (and other files).

Was the pull request ever created? Or is this even still an issue after the new release (v0.11)?

Yes - from my brief testing, it is still an issue with v0.11.0.  My test was:
'js/**/*.js',
'!js/**/*.js

Also see related SO questions: http://stackoverflow.com/questions/29327025/sails-js-specify-js-files-to-exclude-from-auto-insertion, http://stackoverflow.com/questions/12632029/grunt-minimatch-glob-folder-exclusion, http://stackoverflow.com/questions/21470128/sailsjs-linker-grunt-ignore-files-gruntfile-js.  It is a commonly requested feature / capability for Sails that Grunt should already have (http://stackoverflow.com/a/12633119/3232832).

Thanks to @mitom for the fix


camel-jackson-avro data format native support

These are two new dataformats added to Camel 3.10 that are needed in Kamelets.

Moved and camel-jackson-protobuf to a separate issue https://github.com/apache/camel-quarkus/issues/2615

A JVM only extension is underway https://github.com/apache/camel-quarkus/pull/2643


Disable more error codes on .pyi files

Requesting that imports be moved into a type-checking block does not make sense when linting stub files, since they will only be executed in a typing context.
There may be other error codes that also should be disabled in stub files.
flake8s --filename parameter includes .pyi files by default, so this happens even if an end-user doesn't explicitly try to type-check their stub files.

We already disabled TC100 for stubs files here.
Which error types do you think would be useful for stubs files, and which errors aren't?

TC001, TC002 and TC003 are all about moving imports into a type-checking block - and can therefore be disabled.
TC004 makes me think that maybe it should request that all imports should be moved out of type-checking blocks, plausibly as a new error code.
TC200 should be disabled for the same reason as TC100. You could maybe even raise TC201 for all stringified parameters.
And TC006 should never be raised in stub files either.
... which means that the only remaining useful ones would be TC101/TC201, and TC004/[new error code for existence of type-checking blocks].

Sounds to me like skipping .pyi would be the most pragmatic solution. Adding dynamic behavior for stubs files doesn't seem to be of much value to anyone. Does that seem reasonable to you?

Yepyep

Interested in creating the PR? :slightly_smiling_face:


A few rows on Functions and Operators are not rendering

@dt Mind helping me tag-team this?

Turns out this is a known limitation of Redcarpet


avoid the use of install-config

Back in my openshift dev days, I remember the recommendation
was to never use install-config after the cluster is installed. The
information in install config is only prevalent during install time and
can change when cluster is running.
We currently use the install config to get the apiserver URL. A more
reliable way IMHO of finding the same information would be using
the infrastructures API
[alpatel@alpatel agnosticd]$ oc get infrastructures -oyaml | grep apiServerURL -C 2
  status:
    apiServerInternalURI: https://api-int.cluster-alpatel-pvc-migrate-440.alpatel-pvc-migrate-440.mg.dog8code.com:6443
    apiServerURL: https://api.cluster-alpatel-pvc-migrate-440.alpatel-pvc-migrate-440.mg.dog8code.com:6443
    etcdDiscoveryDomain: cluster-alpatel-pvc-migrate-440.alpatel-pvc-migrate-440.mg.dog8code.com
    infrastructureName: cluster-alpatel-pvc-m-g9k4h
[alpatel@alpatel agnosticd]$

Thank you for investigating @alaypatel07

@alaypatel07++

I had to revert the PR.
 TASK [set_fact] ********************************
fatal: [localhost]: FAILED! => {"msg": "The conditional check 'infrastructures is defined and infrastructures.get('resources', [{}])[0].get('status'. {}).get('apiServerURL', '') != ''' failed. The error was: template error while templating string: expected name or number. String: {% if infrastructures is defined and infrastructures.get('resources', [{}])[0].get('status'. {}).get('apiServerURL', '') != '' %} True {% else %} False {% endif %}\n\nThe error appears to be in '/opt/ansible/roles/migrationcontroller/tasks/main.yml': line 86, column 7, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n    block:\n    - set_fact:\n      ^ here\n"}
111


Add focus states to buttons

Many buttons have non-existent or terrible focus states, which negatively affect accessibility.

@random3900 Oh yeah.
By the way, you don't have to do it for all the buttons. Just as many as you can. Also feel free to make separate pull requests for each button group. For example, one pull request for "Slide from bottom right" buttons, another pull request for "Subtle moving gradient " and so on.
Thank you!


What's the Training Costs of Knowledge Distillation for FLux Mini

Dear developers,
I really appreciate your most most most valuable works. Could you please tell me how much data and training hours are utilized to distill the Flux into Flux Mini? This can help us to decide whether we should follow your work for making better distilled diffusion models.
If possible, could you please tell us the datsets for training?
Many thanks

Thank you for your interests.
We used Laion and JourneyDB to train the model. The training takes around two weeks on 2 910B nodes. You may find about more in our readme:
The distillation process is performed with 512x512 laion images recaptioned with Qwen-VL in the first stage for 90k steps, and 1024x1024 images generated by Flux-schnell using the prompts in JourneyDB with another 90k steps.


Gemnasium displaying invalid results

If you click the package dependencies badge on the readme it links to an invalid report.
Not sure what the mechanism is for gemnasium.com but it appears to be displaying results for packages that are no longer listed in package.json. If I can do anything to help please let me know.

The Gemnasium link is showing the former repo location (RobertHerhold/IcedFrisby). Maybe @MarkHerhold needs to re-configure it in the new location?
Greenkeeper has become popular. We could look at switching to that instead.

@RobertHerhold Can you fix/get rid of Germnasium please?
@paulmelnikow I can setup Greenkeeper if you like, but the downside is that it's pretty noisy. Let me know.

It did get a bit better in version 2. They make one thread per dependency now, instead of one per notification. I'm game to give it a shot.

@paulmelnikow I'm glad to hear they improved it. I just added it.

I removed this library from Gemnasium, but the link still works for some reason. Regardless, we should be fine to switch off of it.


String view2

This PR tries to get a green CI for the original string_view PR.

See https://github.com/nlohmann/json/issues/1529#issuecomment-1003733316

Coverage remained the same at 100.0% when pulling 7254b1f6df6b80ee604b86364be1cf553e11f322 on string_view2 into b69713c39480a4aa0b05b24ea07cc542219012ff on develop.

I might have a solution: 19c26cc
Similar overloads may be needed for other member functions like at(json_pointer).

Wait … this is not the expected behavior at all, is it? Why is it in the regression test?
My "solution" is based on this comment from the unit test:
// mixed type - the JSON Pointer is implicitly converted into a string "/root"

I've thoroughly confused myself now. Help.


Chapter 2 Homework 1

Chapter 2 Homework 1
Refer to https://github.com/csinn/CSharp-From-Zero-To-Hero/tree/Chapter1/Homework/8/Src/BootCamp.Chapter and implement the same homework using OOP style.
Please Note
Normally, I would not include the notes below, but I struggled to understand to what to do.  I coded so that the program could run and that the given Tests would pass. It should be noted that all the given Tests will pass.  Because of my difficulties in doing this assignment, I am including below what I did that led to me with what I am submitting this time for Chapter 2 Homework 1. Hopefully, I have something closer to what you expected, and if not, well, at least you can see what I did that led to me to the program that I am handing in, and let me know where I went off course.

After the first time of submitting my Chapter 2 Homework 1, I got feedback to redo it with suggestions.
I tried to understand what do by going back to the beginning by looking at Chapter 1 Homework 8 again.
I am not sure why (may be I was asleep or dreaming back when I first worked on Chapter 1 Homework 8), but this time I discovered that more corrupt data had changed and code frame had changed, such as FileCleaner.cs file now exists where I do not recall it existed.
I re-coded Chapter 1 Homework 8 and merged the changes into the Chapter 2 Homework 1 that I fetched from the csinn-Repository in GitHub.
I created a Person class, as suggested when I was told to redo this assignment.
I then coded to pass data using this Person class instead of the string.  However, there was a puzzling problem for me.  The Tests that are given are built to pass data using string, which is why I originally thought I was supposed to continue for this assignment to pass data using string data.  Since I am not familiar with how Tests are coded to work, I changed the code in Check.cs file to transform the String data from the Tests into Person type data and then would make the calls from there to do the testing just as before but with this time passing with Person type data instead of String type data.  In doing so, Tests continue to work and still fulfill the requirement to use Person type data in passing data.
I ran the Tests.  All the tests passed.
I ran the program.  It produced output using TextTable class and using Person type to pass data.

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 2
- Added 12

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/Person.cs  3
- Src/BootCamp.Chapter/FileCleaner.cs  5
- Src/BootCamp.Chapter/InvalidBalancesException.cs  1
- Src/BootCamp.Chapter/BalanceStats.cs  5
- Src/BootCamp.Chapter/TextTable.cs  7
- Src/BootCamp.Chapter/Checks.cs  3

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 7
- Added 2

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/Person.cs  3
- Src/BootCamp.Chapter/BalanceStats.cs  5
- Src/BootCamp.Chapter/Checks.cs  3
- Src/BootCamp.Chapter/InvalidBalancesException.cs  1
- Src/BootCamp.Chapter/TextTable.cs  7
- Src/BootCamp.Chapter/FileCleaner.cs  5

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 7
- Added 4

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/InvalidBalancesException.cs  1
- Src/BootCamp.Chapter/BalanceStats.cs  5
- Src/BootCamp.Chapter/Person.cs  3
- Src/BootCamp.Chapter/FileCleaner.cs  8
- Src/BootCamp.Chapter/Checks.cs  3
- Src/BootCamp.Chapter/TextTable.cs  7

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 7
- Added 3

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/Checks.cs  3
- Src/BootCamp.Chapter/InvalidBalancesException.cs  1
- Src/BootCamp.Chapter/Person.cs  3
- Src/BootCamp.Chapter/TextTable.cs  7
- Src/BootCamp.Chapter/BalanceStats.cs  5
- Src/BootCamp.Chapter/FileCleaner.cs  8

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 7
- Added 2

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/FileCleaner.cs  8
- Src/BootCamp.Chapter/InvalidBalancesException.cs  1
- Src/BootCamp.Chapter/Checks.cs  3
- Src/BootCamp.Chapter/Person.cs  3
- Src/BootCamp.Chapter/TextTable.cs  7
- Src/BootCamp.Chapter/BalanceStats.cs  5

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 7
- Added 3

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/InvalidBalancesException.cs  1
- Src/BootCamp.Chapter/Person.cs  3
- Src/BootCamp.Chapter/TextTable.cs  7
- Src/BootCamp.Chapter/FileCleaner.cs  5
- Src/BootCamp.Chapter/BalanceStats.cs  5
- Src/BootCamp.Chapter/Checks.cs  3

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 7
- Added 2

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/FileCleaner.cs  5
- Src/BootCamp.Chapter/Checks.cs  3
- Src/BootCamp.Chapter/InvalidArgumentException.cs  1
- Src/BootCamp.Chapter/Person.cs  3
- Src/BootCamp.Chapter/InvalidBalancesException.cs  1
- Src/BootCamp.Chapter/TextTable.cs  7
- Src/BootCamp.Chapter/BalanceStats.cs  5

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 7
- Added 2

Complexity increasing per file
==============================
- Src/BootCamp.Chapter/BalanceStats.cs  5
- Src/BootCamp.Chapter/InvalidBalancesException.cs  1
- Src/BootCamp.Chapter/FileCleaner.cs  5
- Src/BootCamp.Chapter/Checks.cs  3
- Src/BootCamp.Chapter/InvalidArgumentException.cs  1
- Src/BootCamp.Chapter/TextTable.cs  7
- Src/BootCamp.Chapter/Person.cs  3

See the complete overview on Codacy


Create flatten-array.hs

To make this problem a bit interesting in Haskell, one has to define his/her own datatype. Lists in Haskell are uniform meaning that they cannot store different datatypes (e.g., [1, 'a', 2] will not work). In this case, elements of sublists should also have the same datatypes meaning that [[1,2], ['a', 'b'], [3,4]] is also not possible. We would be left with boring lists like [[1,2,3],[4,5,6],[7,8,9]] where everything (on all access levels) has the same datatype so I defined the brand new - Nested List datatype. I also added a note regarding this datatype in README.
This datatype could also be found at https://wiki.haskell.org/99_questions/Solutions/7 where you can see the classic solution to this problem. As seen on the link above, there are lots of different approaches yet, I found this one to be one of the easiest.

It's been a while since I last touched Haskell, but your solution looks fine to me.
Thanks for that good sir. 🐕


Notes for v2

Just writing these down so I don't forget
Main Components
These are going to be the main components of the v2 architecture
Resolvers
Resolvers will be responsible for resolving the path to a file based on relativity. They should be able to accept multiple module dirs and support live fs changes.
Loaders
Loaders will have the responsibility to process the raw contents of the files, even css or woff or something, and convert it into a js source, that automatically sets the contents to module.exports.
Loaders will also have the responsibility to tell pundle what others modules were required from it (only the ones where we can do it dynamic, like for js or coffee sources but NOT for less sources) as well as swap values in require to be usable in runtime
Transformers
Transformers will work in a way that they accept javascript and output javascript. Babel is an example use case of transformers.
Post-Transformers
Post-Transformers will work just like transformers, except after all transformers have been executed. UglifyJS is an example use case of transformers. Unlike transformers, these will not be executed on individual files but on the generated content.
Plugins
Everything else that does not modify the contents of the generated output will be a plugin. ESLint, NPM Installer and others could be counted as plugins.
Generators
Generators will be given the processed contents of each files and will be responsible for making output bundles. The default generator generates CommonJS style output.
Reporters
Reporters will be responsible for keeping the user aware of the status of the builds. For example, a reporter in pundle-dev could show the messages in browser, while the pundle CLI would show them in the terminal like this post
Other Notes to self

Make sure to split CLI into a separate package pundle-cli or something and make pundle an API only base package
Make sure to implement advance resolve config like aliases
Every component should have a this context that has a report() method, useful in cases like eslint
When this.resolve(path, ?from, ?cached) is called from a component, and the component is a resolver, make sure NOT to invoke that one again for that request until the existing request is fulfilled

TODO: Write more notes here

Done in Pundle v2Alpha1


安装时候提示这个请问正常吗？

sh: 12: [[: not found
sh: 23: [[: not found
sh: 12: [[: not found
sh: 23: [[: not found
sh: 40: 当前node版本(如果没有node，请自行安装): : not found
sh: 41: node: not found
sh: 44: 当前npm版本(如果没有npm，请自行安装): : not found
sh: 45: npm: not found
sh: 47: npm: not found
sh: 48: cd: can't cd to /ql
sh: 49: pnpm: not found
sh: 51: pnpm: not found
sh: 53: npm: not found
sh: 55: pnpm: not found
sh: 57: pip3: not found
sh: 59: cd: can't cd to /ql/scripts/
sh: 60: cd: can't cd to /ql
sh: 61: apk: not found
sh: 62: cd: can't cd to /ql
sh: 63: apk: not found
sh: 12: [[: not found
sh: 23: [[: not found
sh: 12: [[: not found
sh: 23: [[: not found
bash: line 4: -e: command not found
bash: line 4: $'1m安装依赖...\E[0m': command not found
bash: line 6: -e: command not found
bash: line 6: $'1m安装依赖需要时间，请耐心等待!\E[0m': command not found
bash: line 13: -e: command not found
bash: line 13: 1m依赖安装完毕...建议重启: command not found
bash: line 15: -e: command not found
bash: line 15: 1m有任何问题，请在此仓库提交Issue：: command not found

报错了，命令没找到，检查下环境


Additional example to handle sentry in specific environments in phoenix (README.md)

Following the instructions, I was receiving errors in the test environment. I added a small example of how I fixed it to the readme.

@cdvv7788 can you elaborate on the errors you are receiving?

@mitchellhenke Just warnings when running the controller tests. Situations where normally sentry sends the message. It complains about an invalid DSN.
Obviously, setting the DSN for the test settings is not an option.
Is there a better approach to handle this?

Controlling the situations in which Sentry runs should be done via the :environment_name and :included_environments configuration keys. An example is here:
config :sentry,
  dsn<EMAIL_ADDRESS>  # ...
  environment_name: Mix.env(),
  included_environments: [:prod]

@mitchellhenke Well, my setup differs a little from what is in https://github.com/getsentry/sentry-elixir#configuration
I have the configuration in prod.secret.exs, to load the dsn from an environment variable.
If you just use the Sentry.Plug in the router, it will try to load sentry when it has not been configured.
I think that loading the dsn from an environment variable is a pretty common pattern. Is it still recommended to add it in the config.exs file, even when it is only wanted for sites that use prod.exs settings? (staging and prod use that one, for example).

@cdvv7788 The method for loading the DSN shouldn't cause any issues around this, it's an issue with Sentry's defaults, which is hard to make fit for the different use cases (though yours is a common pattern).
Sentry is trying to send events while in the :test MIX_ENV because the configuration for :environment_name is matching whatever is in :included_environments.
Could you try adding the following to config/config.exs?
# config/config.exs

config :sentry,
  included_environments: []

@mitchellhenke that worked. Does this deserve something in the readme or should I just close the PR?

@cdvv7788 Closing I think is fine. I've rewritten the README a little bit to hopefully make it clearer, and I'm working on some configuration-related things to make the initial setup better.


installation details, debugging what is wrong?

Hi, I've installed this on a 16.x server, it's failing:
23:38:55.015 [go] Start to execute task: Plugin with ID: docker-task.
23:38:55.032 Cannot connect to the Docker daemon. Is the docker daemon running on this host?
23:38:55.040 Cannot connect to the Docker daemon. Is the docker daemon running on this host?
23:38:55.043 Error: Interaction with plugin with id 'docker-task' implementing 'task' extension failed while requesting for 'execute'. Reason: [null]
23:38:55.049 [go] Current job status: failed.

It's hard for me to understand what is wrong. The docker daemon is running and listening on local port 2375, but I don't know how to point gocd-docker at that. I tried setting the DOCKER_HOST env variable, it didn't seem to change anything. As far as I can tell this is the code that is actually turned into a command, but I don't really understand how to add a host entry to it, or understand how it's working for others.

+1 I have the same problem....
Could you please help us.
Thanks.


Data security guard rails

Fixing multiple edge cases where data can potentially go in the wrong directory. These issues can only be caused if staff don't follow prescribed steps and accidentally run into these edge cases.
Edge case 1:
When "Queue collect" is on it allows staff to add requests to multiple samples. These samples could belong to different proposals. We only want to add requests to samples of the currently active proposal. The commit will not allow adding requests for proposals that exist in the API, if it doesn't exist in the API (for e.g. 999999) it will ask the user if they are sure about adding the request. Code is in commit: https://github.com/NSLS-II/lsdc/commit/e02dba893b71c38b892d33b7a78c2c2f5a43e5c0
Edge case 2:
When staff schedules an auto raster to a sample belonging to proposal A while proposal A is active but accidentally collect after switching to proposal B. The two rasters will go to directory B but the standard will go to directory A. This is because any new request created uses the currently active proposal directory. The commit will fix it so that rasters will use the path of the standard collection instead of blindly using the current proposal directory. Code is in commit:  c9ca3097c2159c7ff896dd9592544849bbb9a935
Paths used are resolved so that paths with /data/ can be compared to /data4/. Commit in 67ba3533d8c4bb2cbf47491c29f003972af6ae67 and c0a61703320a7433b3f163a1e62394d6ef4f69aa
Edge case 3:
Because there can be a large number of pucks and samples that can be loaded at the same time, staff can sometimes forget that they have added requests to a proposal that is NOT the current proposal. i.e. Add the request to a sample for proposal A when its active but forget to collect or remove it after switching to proposal B. When the user pushes collect queue in this situation, popNextRequest will check if the queue has samples from multiple proposals. If it finds that there are requests from multiple proposals AND the commissioning directory is not used, it will return a None, otherwise will return the next collection to run. Commit in cba5c95d66be202f188f1df39640fd4d3eeb530f
Related fixes:
Dewar tree will show which directory the data will go to in the pop up box for collections (cba5c95d66be202f188f1df39640fd4d3eeb530f)
Prevent LSDC from crashing if a proposal number doesn't exist in NSLS2 API (cba5c95d66be202f188f1df39640fd4d3eeb530f)
Message to let user know why the queue didn't run (4e23d203b969f05b5de8fcca48b252d2ed0182f1)

Edge case 1 - looks good, makes sense
Edge case 2 - looks good
thanks for handling the data path resolution - a new surprise!
Edge case 3 - looks like it works - logging fixes suggested


[WIP] Docker images

Dockerfile Integration #3
Just started to work with the docker images.
TODO

[ ] Dockerfiles for the other architectures

[ ] Automation scripts for building the images

[ ] Possible changes to config.json file

[ ] Can be filled dynamically using env vars.

[ ] Use a fixed to the json file, so it can be a volume to persist config.

[ ] Not using config.json at all, and use dynamic values

[ ] Values declared in CLI with flags instead. (e.g. docker run url-shortener --clientID 'XXX' --clientSecret 'YYY' --baseUrl 'http://domain.com' and so on)
[ ] Values in json file can be declared using env vars instead (e.g. docker run -e CLIENTID="XXX" -e CLIENTSECRET="YYY" -e BASEURL="http://domain.com" url-shortener and so on)

[ ] Fixed or default path to database, so it can be a volume to persist data. (Same approach as with config.json can be used)

Related Issues
#2 #3
Depends on

[x] #36

Hello,
It probably makes sense to switch from the normal json.Decode/Encode in Go to something with more features like viper. It has e.g. support for overriding config values by priority. So environment variable will override the values from the config.json and so on, see here for more information.
For the building, I would have imagined that they would always be rebuilt by Source. Maybe the build steps could be:

build frontend
build Go binary
run binary

So that the size of the last build step is really small, because of the very less dependencies of a Go binary.

Sure, will take a look at it, one more thing in order to get a small binary, it could be statically built, at least for the Docker image, that'd result in a really small footprint image (either based on scratch or alpine)

The binaries already embed the frontend and the templates, in my opinion they are already really small (tar.bz2 ~4-5mb). If you mean that with statically built.

Hi,
I've updated the configuration, so that we can use environment variables easily. For usage check out the wiki.

@maxibanki thanks for the great news, will take a look at the changes asap, i have free time on weekends mostly.
and about the docker images, sure! Although I'm not familiar with Travis CI, a GitLab CI user here,  guess i can learn easily.

@klud1 sorry for my not very professional behavior towards you and excuse me for having built the dockerfile myself. However, I would like to thank you very much for the ideas and the proposal on how this should be implemented.


Natively support strings in clang

Previously strings are supported with an out-of-band indexing step that replaces the strings with integers. This branch adds the string type.
Important:
this branch breaks grappalang: a tuple stores a STRING_TYPE as a C++ std::string, which has a pointer to a string. In grappalang, since this is not a GlobalAddress, strings won't work.
suggested fix is to replace std::string with std::array<char, N> so that the data is stored in the Tuple struct

[x] array refactoring
[x] test grappa running

replaces #400 to change base branch

String support in grappalang will be more complicated.
A few options:

send std::string in a Grappa RPC, and the internal char* is turned into a GlobalAddress and a second message retrieves it.
serialize tuples before sending
this will complicate the code because we cannot rely on a lambda capture of the tuple or the string
we can serialize to a std::array<SIZE>
use std::array in the tuple structs
this might actually work quite well as string operations are not really needed

On Tue, Apr 14, 2015 at 10:27 PM, Brandon Myers<EMAIL_ADDRESS>wrote:

String support in grappalang will be more complicated.
A few options:

send std::string in a Grappa RPC, and the internal char* is turned
into a GlobalAddress and a second message retrieves it.
serialize tuples before sending

this will complicate the code because we cannot rely on a lambda
capture of the tuple or the string
we can serialize to a std::array

- use std::array in the tuple structs
  - this might actually work quite well as string operations are not
  really needed

I'm too far away from the code to have a meaningful opinion, but I think
std:array seems reasonable.  If we need string ops down the road, casting
from array to string in the context of the apply op that invokes the string
functions seems feasible.

—
Reply to this email directly or view it on GitHub
https://github.com/uwescience/raco/pull/408#issuecomment-93196706.

--
Bill Howe
Associate Director and Senior Data Science Fellow, UW eScience Institute
Affiliate Faculty, Computer Science & Engineering
University of Washington
To acknowledge eScience: "Supported in part by the University of Washington
eScience Institute"

Coverage increased (+0.14%) to 90.11% when pulling 41e99c6b322c7db2e5437fe9786c64ae94102435 on bmyerz/stringz into a8701294b13234e11338f8e3ae8cb089e6765e91 on master.

Coverage increased (+0.14%) to 90.11% when pulling 41e99c6b322c7db2e5437fe9786c64ae94102435 on bmyerz/stringz into a8701294b13234e11338f8e3ae8cb089e6765e91 on master.

Coverage increased (+0.14%) to 90.11% when pulling c3b30d57fe48186f5ae331d6c1e0b8b1db1da71c on bmyerz/stringz into a8701294b13234e11338f8e3ae8cb089e6765e91 on master.

Coverage increased (+0.14%) to 90.12% when pulling 6543fe750c996b159e47125062eabe7a8d46ea48 on bmyerz/stringz into a8701294b13234e11338f8e3ae8cb089e6765e91 on master.

Coverage increased (+0.14%) to 90.12% when pulling 6543fe750c996b159e47125062eabe7a8d46ea48 on bmyerz/stringz into a8701294b13234e11338f8e3ae8cb089e6765e91 on master.

Coverage increased (+0.15%) to 90.12% when pulling adbcd236fce4efd42084fb883420aaf9c5b7cc0d on bmyerz/stringz into a8701294b13234e11338f8e3ae8cb089e6765e91 on master.

Coverage increased (+0.15%) to 90.12% when pulling adbcd236fce4efd42084fb883420aaf9c5b7cc0d on bmyerz/stringz into a8701294b13234e11338f8e3ae8cb089e6765e91 on master.

Coverage increased (+0.15%) to 90.12% when pulling adbcd236fce4efd42084fb883420aaf9c5b7cc0d on bmyerz/stringz into a8701294b13234e11338f8e3ae8cb089e6765e91 on master.

Coverage increased (+0.14%) to 90.11% when pulling 4827f872dc9f811ed1369a658829daf63c399b2c on bmyerz/stringz into a8701294b13234e11338f8e3ae8cb089e6765e91 on master.

Coverage increased (+0.14%) to 90.11% when pulling fe8ba7861e74e47ed4f4f65ecfae914107b49d10 on bmyerz/stringz into a8701294b13234e11338f8e3ae8cb089e6765e91 on master.

Coverage increased (+0.14%) to 90.11% when pulling fe8ba7861e74e47ed4f4f65ecfae914107b49d10 on bmyerz/stringz into a8701294b13234e11338f8e3ae8cb089e6765e91 on master.

Coverage increased (+0.13%) to 90.1% when pulling 6859cd2bcb59b9ea858dbf3465abaffd4cca95e9 on bmyerz/stringz into a8701294b13234e11338f8e3ae8cb089e6765e91 on master.

Coverage increased (+0.13%) to 90.1% when pulling c9dc0000b8d8807eed633fd536758ff6b97cb8c3 on bmyerz/stringz into a8701294b13234e11338f8e3ae8cb089e6765e91 on master.

Coverage increased (+0.13%) to 90.1% when pulling c9dc0000b8d8807eed633fd536758ff6b97cb8c3 on bmyerz/stringz into a8701294b13234e11338f8e3ae8cb089e6765e91 on master.

Coverage increased (+0.11%) to 90.08% when pulling 5876939fb7582bfa5d7eb0b4bfb14ba832ee0f93 on bmyerz/stringz into a8701294b13234e11338f8e3ae8cb089e6765e91 on master.

Coverage increased (+0.11%) to 90.08% when pulling 5876939fb7582bfa5d7eb0b4bfb14ba832ee0f93 on bmyerz/stringz into a8701294b13234e11338f8e3ae8cb089e6765e91 on master.

Coverage increased (+0.11%) to 90.08% when pulling 52522225ac4d849689e46e6ece3ee90d734be526 on bmyerz/stringz into a8701294b13234e11338f8e3ae8cb089e6765e91 on master.

Coverage increased (+1.43%) to 91.4% when pulling f1f2ce062d80a45aaba33e910f0e731034b63ca4 on bmyerz/stringz into a8701294b13234e11338f8e3ae8cb089e6765e91 on master.

Coverage increased (+0.16%) to 91.4% when pulling ad90f2154dec685f359ccc8a7132e0c9bc29d9eb on bmyerz/stringz into 950c602e3342c0c854f702f8ffecb76d880d358c on master.


MultiIndex for obs/var

Can we enable pd.MultiIndex for obs/var?
I assume that should be implemented somewhere here? Would that be doable?

What do you expect to work which doesn’t? Some specific examples would be nice. Is this about passing in a pandas.Index instance which doesn’t behave as expected or do you want to index with a list of tuples and that doesn’t work as expected?
At a glance, the former should probably work? What’s a MultiIndex’s dtype?
https://github.com/theislab/anndata/blob/2723c9c9e8bc0fe50a9513f292916616a603923b/anndata/_core/index.py#L85-L104
Please help out with some proactive investigation for feature requests like this, that makes it much more pleasant to get started!


How can ı make payment with nfc

ı want to make payment using nfc for flutter. Do you know? how can ı do?

did you know how to do it?


Support for macOS's pkgbuild utility

In macOS you can create the equivalent of an .rpm or .deb package (roughly) using .pkg via the pkgbuild utility. Are there any plans to support this format in pkg_rules? Would this be the right ruleset for such a rule?

I think it is fair to have them here, as long as they are a separable module that can be auto-configured on macos and silently skipped on other platforms. We are doing something like that with rpmbuild.
As for plans to support it? I know I won't have the time for that. I am, however, happy to review a design proposal.

I think it is fair to have them here, as long as they are a separable module that can be auto-configured on macos and silently skipped on other platforms. We are doing something like that with rpmbuild.
As for plans to support it? I know I won't have the time for that. I am, however, happy to review a design proposal.

Along a similar line, it might be nice to get support for .dmg archives too? If someone had the time to throw open a PR for that it'd be greatly appreciated!

Maybe we can all work together on this.

Interested parties can provide examples of what they are doing now to get bazel to produce things that they then consume with pkgbuild.
We can compare those and design the way these toolchains should work

I am happy to advise any design and review PRs, but I honestly don't have time for the remainder of this year to do Mac or Windows specific packaging myself.

https://github.com/keith , https://github.com/thomasvl , or https://github.com/sergiocampama might have some ideas as this isn't met by any example in the https://github.com/bazelbuild/rules_apple project (and I wish it was).

It's a perpetual tough call if pkgbuild should be here or in rules apple.
Part of me says, put them in rules_pkg. We've got all the tools for laying
out what the final image should look like. This just bundles it.
Another part of me says absolutely not. Finding the right instance of
pkgbuild is the domain of people building the toolchain that gets you xcode.
On Sun, Jan 16, 2022 at 3:05 PM Allan Clark @.***>
wrote:

https://github.com/keith , https://github.com/thomasvl , or
https://github.com/sergiocampama might have some ideas as this isn't met
by any example in the https://github.com/bazelbuild/rules_apple project
(and I wish it was).
—
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_pkg/issues/264#issuecomment-1013942926,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXHHHBM7UL2RALILTQZMPDUWMQJ3ANCNFSM4U6T2TGQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

@aiuto if you're fine accepting a Minimum-Ship for this capability, I've got a basic rule that packages pkg_tar archives into a flat-pack -style .pkg.  ...essentially compatible with sudo installer -pkg thing.pkg -target /:
pkg-tar (
    name = "tools",
    srcs = [ ... ],
    mode = "0755",
    package_dir = "/usr/local/bin",
)

pkgbuild_tars(
    name = "thing",
    tars = [ ":tools" ],
    version = "1.11.0",
)

I'd rather ship a basic functionality to start, and improve over time, than wait for perfect.  If this basic functionality is too weak, please advise.

look at pkg_tar's implementation (and soon pkg_zip's), rather than pkg_deb
or pkg_rpm.
On Tue, Mar 29, 2022 at 12:36 PM Allan Clark @.***>
wrote:

Yeah, looks like the Debian packaging example rewritten as trivial MacOS
would be something like this today; notice both use pkg_tar, so perhaps
changing over to a different archive should be at the same time. I did
expect a different pkgbuild_ function, so it's possible
current and future definitions can coexist:
@._pkg//pkg:tar.bzl", @._pkg//pkg:pkgbuild.bzl", "pkgbuild_tars")
pkg_tar(
name = "bazel-bin",
strip_prefix = "/src",
package_dir = "/usr/local/bin",
srcs = ["//src:bazel"],
mode = "0755",
)
pkg_tar(
name = "bazel-tools",
strip_prefix = "/",
package_dir = "/usr/local/share/lib/bazel/tools",
srcs = ["//tools:package-srcs"],
mode = "0644",
)
The resulting PKG should be installable by:## sudo installer -pkg bazel.pkg -target /pkgbuild_tars(
name = "bazel",
tars = [ ":bazel-bin", ":bazel-tools" ],
package_name = "bazel",
version = "0.1.1",

)
—
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/rules_pkg/issues/264#issuecomment-1082105873,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXHHHDGZAYMOZBSRNXILSDVCMWRPANCNFSM4U6T2TGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

look at pkg_tar's implementation (and soon pkg_zip's), rather than pkg_deb or pkg_rpm.

Laying out multiple subdirs would typically require a few iterations of an action to unspool derived objects into the "base" or "root" to package up.  This means likely either leveraging the existing pkg_tar a few times, or leveraging nearly exact copies of this logic.
re-using tar for this easily handles the situation of multiple subdirs or paths off the root, and adds the ability to confirm the makeup of each tar archive individually.  I checked my own usage to debug one that wasn't as expected by un-tarring the intermediate tar files.
After coding around this for another week, I end up with a sticky mess of copied pkg_tar that I don't want to maintain, that seems to offer no benefit over the ability to untar components to check, and just adds a maintenance burden.
I'd be embarrassed to submit it.

Interested parties can provide examples

This PR 6 days ago is the best example of how I'm doing this, and I'll evolve it from there as my needs expand.  Let's see if there's another submission to compare.
I appreciate your feedback, and the work you've done.

Your example is using pkg_tar as a substitute for pkg_files. Yes, it will get you mode assignment and a package prefix, but that is a dead end solution. Any functionality we add in the future (for example, bulk rename of files via regex) is going to happen in pkg_files, so it is generically available, not in pkg_tar. So that puts users in the situation where they will mostly structure their final layout with pkg_files.
You could have pkg_pkgbuild be a macro that passes srcs along to an internal pkg_tar rule and then sends the single tarball to the pkgbuild builder. That would at least have a more general api than requiring tar files as the only input.
To go along with that, we could increase debugabililty by adding a rule which takes pkg_files as input and creates a textual description of the mapping of input files to output tree.  That would be useful to everyone, not just tar users.
OTOH, we are getting ahead of ourselves. What we have not talked about are what are the minimum requirements for a pkg_pkgbuild rule?  I haven't used that in a few years, so I don't know which of the many options it has are a basic set. I can see it getting quickly out of hand if you want signing, because you'll want the keys injected into the action input tree, but you don't want them to come from your source tree.  I think the right place to discuss those needs is in rules_apple.

My intent was a Minimum-Viable before going too far.  My initial needs are a pkgbuild that builds a package, and -- you're right -- as needs approach signing and multi-arch binaries, the simple offer this would provide should transition to rules_apple.
Perfect being the enemy of shippable, what's shippable as a component of a packaging project that doesn't itself go deeply into, say, apple-specific things?  Following steps are easier to plot to the limit of what  you'll accept in your project, but having a minimum-viable at least gets a capability on-the-table.  That would allow, say, @UebelAndre to look into DMG while we take the next step in capability.  I don't have to explain concurrent development to you though!
Smaller deliverables are easier for people like me who have other commitments.
I've found rules_apple things to be a bit complex and mobile-focused.
What would be the minimum-ship for a packaging macro that doesn't get too deep into Apple-specific things ?

To me, the minimal thing would be

a rule that takes a macos_application as a source and emits a .pkg file of it
and it should pick up the path to pkgbuild with a toolchain rather than just assuming it is in your path
and work with target_compatible_with so that people can safely skip the rules if they are running from anything but OSX.
examples of how to use it

But that is really just a guess. I don't know what macos_application produces under the hood.  Does it just give you the binary, or does it lay out the full tree as it should appear under /Applications ?   If it doesn't lay out the application, then there should really be something in rules_apple that does.
I think the target of MVP misses the point, because that assumes someone will be around to maintain and improve it.  What I really require is someone to own the design of the feature set, provide development and leave it in a state where it is usable to a wide enough group of people so that it only requires little tweaks, and not new major features.  The rules_apple team are better domain experts than the people who work on rules_pkg.

Depending on any Provider() from rules_apple causes a dependency between that project and yours.  You might end up needing rules_apple just to compile (parse syntax and pass analysis) sufficiently to build .deb packages on Linux.
This minimum you’ve described, that’s much, much more barrier-to-entry than I can surpass right now.  Not on the tiny amount of volunteer time I have outside work and family.

On Wed, Apr 20, 2022 at 5:42 AM Allan Clark @.***>
wrote:

Depending on any Provider() from rules_apple causes a dependency between
that project and yours. You might end up needing rules_apple just to
compile (parse syntax and pass analysis) sufficiently to build .deb
packages on Linux.

We avoid that by making that toolchain optional, like rpmbuild. You have to
explicitly load that slice in your workspace.

This minimum you’ve described, that’s much, much more barrier-to-entry
than I can surpass right now. Not on the tiny amount of volunteer time I
have outside work and family.

That really hits the nail on the head - time commitment, not only for
development, but for end user support. Too many repositories in bazelbuild
are essentially abandonware. We're moving from a model of "add anything" to
making sure there is committed support. I can't offer any time from the
Bazel team to be Apple packaging experts, so we need someone to explicitly
own the entire problem.
The flip side of trying to prevent abandonware is that the bazel team is
more and more willing to advise people to go to repositories outside of the
bazelbuild org for features that we can't support.  If you want to make a
small package builder and host it under another org, I can add a pointer to
that in the readme here.  That makes the support obligations clearer.

Message ID: @.***>

Closing issues that no one is likely to work on for any forseable future


😎 Add lgtm action and docs.

Update readme with lgtm badge and docs
Add lgtm action.

Opened a new PR #18, which is not based on a branch in this repo instead of my fork.


Consider Generics for Tree

The tree interface here expects bytes on Push:
https://github.com/celestiaorg/rsmt2d/blob/80d231f733e9dd8ca166c3d670470ed9a1c165d9/tree.go#L18-L22
This makes sense but at the same time we'd rather want to use some explicit type in NMT instead of just aliasing byte slices (see: https://github.com/celestiaorg/nmt/issues/71).
Push could leverage generics potentially instead.
This is a low-priority consideration.

Looking back at this issue there is no clear benefit over simply using an interface for data instead (just needs a way to serialize from whatever is pushed to the tree).
Closing this issue for now. It is too focused around a specific implementation detail (generics).


Add setup files

Just nitpicking, but could you add a newline at the end of nimble.lock, please?

Just nitpicking, but could you add a newline at the end of nimble.lock, please?

It is autogenerated file, if we want that we should change nimble

Of course, good point, my bad 😄


MongoConnectionException doesn't exists for hhvm

I installed on Ubuntu 14.04LTS MongoDB module in drupal:
curl http://ftp.drupal.org/files/projects/drupal-7.39.tar.gz | tar xvz
curl http://ftp.drupal.org/files/projects/mongodb-7.x-1.x-dev.tar.gz | tar xvz

# hhvm --version
HipHop VM 3.9.1 (rel)
Compiler: tags/HHVM-3.9.1-0-g0f72cfc2f0a01fdfeb72fbcfeb247b72998a66db
Repo schema: 6416960c150a4a4726fda74b659105ded8819d9c

# apt-show-versions hhvm-dev
hhvm-dev:amd64/trusty 3.9.1~trusty uptodate

And crash in line 58 in mongo.module:
\nFatal error: Class undefined: MongoConnectionException in /usr/share/nginx/closure.es/blog/sites/all/modules/mongodb/mongodb.module on line 58
//Line 58 => $mongo = new MongoClient($host, $options);

The snippet code:
    try {
      // Use the 1.3 client if available.
      if (class_exists('MongoClient')) {
        $mongo = new MongoClient($host, $options); //<-- LINE: 58
        // Enable read preference and tags if provided. This can also be
        // controlled on a per query basis at the cursor level if more control
        // is required.
        if (!empty($connection['read_preference'])) {
          $tags = !empty($connection['read_preference']['tags']) ? $connection['read_preference']['tags'] : array();
          $mongo->setReadPreference($connection['read_preference']['preference'], $tags);
        }
      }
      else {
        $mongo = new Mongo($host, $options);
        if (!empty($connection['slave_ok'])) {
          $mongo->setSlaveOkay(TRUE);
        }
      }
      $mongo_objects[$host][$db] = $mongo->selectDB($db);
      $mongo_objects[$host][$db]->connection = $mongo;
    }
    catch (MongoConnectionException $e) {
      $mongo_objects[$host][$db] = new MongoDummy();
      throw $e;
    }

But when i try a simple example like:
<?php

try {
$m = new MongoClient(); // connect
$db = $m->foo; // get the database named "foo"
}
catch (MongoConnectionException $e) {
	print_r($e);
}

?>

Any error is reported in the hhvm/error.log. Bug is generated when hhvm compile the php file because if i add a print_r($host) before $mongo = new MongoClient($host, $options); don't show my print_r()
Another test
<?php

echo 'HHVM version: ' . phpversion() . '
';
echo 'MongoFill version: ' . phpversion('mongo') . '
';
echo '-----------------------------------------
';
echo 'MongoClient: ' . (class_exists('MongoClient') ? 'true' : 'false') . '
';
echo 'MongoConnectionException: ' . (class_exists('MongoConnectionException') ? 'true' : 'false') . '
';
echo 'MongoException: ' . (class_exists('MongoException') ? 'true' : 'false');

?>
```

```
//Output:
HHVM version: 5.6.99-hhvm
MongoFill version: 1.4.5
-----------------------------------------
MongoClient: true
MongoConnectionException: false
MongoException: true
```

Live version: http://closure.es/mongo.php

--------------------------------------------------------------------------
Updated:
- I've tried to recompile mongofill-hhvm and redownload from git
- I've reinstalled Drupal
- I've tested with 2 versions (dev  and stable version) of Mongo Module for Drupal
- reboot hhvm, nginx and mongo
- reboot the machine
- Mongo is up with service --status-all
- With the mongo command i can add, list and remove dbs

And seems that hhvm dont find the MongoConnectionException class.

- In my src/ext_mongo.php file the class MongonConnectionException exists
- But when i use get_declared_classes (); in hhvm dont show the MongoConnection Exception:
https://gist.github.com/layane/1d7887d0ceb94ee207fe
- So I confirm that hhvm dont find the MongoConnectionException class
- **I ugly resolve this bug, adding MongoConnectionException.php to my Drupal and importing with require_once();**

Solved:
I rename in MongoFill the file MongoException.php to AMongoException.php and recompile it. So the problem is the order to merge all php files in the ext_mongo.php.
MongoException need to be parsed before all inherited classes.
HHVM version: 5.6.99-hhvm
MongoFill version: 1.4.5
-----------------------------------------
MongoClient: true
MongoConnectionException: true
MongoException: true

I have a fix for this in https://github.com/mongofill/mongofill-hhvm/pull/47

I surmise this would fix my issue: https://github.com/mongofill/mongofill-hhvm/issues/45

@rowillia perfect solution is more elegant that rename base classes.


Feature/WRN-16901

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: daniel-stoian-lgp:x: vladut-clapou-lgpYou have signed the CLA already but the status is still pending? Let us recheck it.

Checklist

[X] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[X] Documentation was added or is not needed
[X] Documentation was verified or is not changed
[X] UI test was passed or is not needed
[ ] Screenshot test was verified or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
Updated tests to work asynchronously.
Resolution
Additional Considerations
Links
WRN-16901
Comments


Add test for HttpTransformer.Empty

Fixes #1409

@greenEkatherine FYI I changed the keyword above to close the issue automatically - see https://docs.devart.com/studio-for-sql-server/source-controlling-databases/associating-commits-with-github-issues.html

@greenEkatherine FYI I changed the keyword above to close the issue automatically - see https://docs.devart.com/studio-for-sql-server/source-controlling-databases/associating-commits-with-github-issues.html

Thank you! I always forget which words work 😃


add version control of extra manifest upgrade

add version control of extra manifest upgrade

Signed-off-by: Jian Wang<EMAIL_ADDRESS>
IMPORTANT: Please do not create a Pull Request without creating an issue first.
Problem:

The extra manifests are applied in each upgrade path.
Solution:

Add version control, apply them in specific upgrade path.
Related Issue:
https://github.com/harvester/harvester/issues/3644
Test plan:

check upgrade log.
From v1.1.2 -> v1.2.0 upgrade, the extra manifests log should be like:
No extra manifests in /usr/local/share/extra_manifests/v1.1.2 to apply

@mergifyio backport v1.2


#100 Automatic Refresh for V3 Recaptcha

In order to keep the token alive, the browser will now call the recaptcha execute method after 100 seconds. Keeping the token valid.
This fixes #100

@TimothyMeadows Any news on that? It owuld be fab to get that change merged in the next version!

@TimothyMeadows Please :)

Any possibility that you might release a new version?


Update Set-SPOTenant.md

Added missing parameters: InformationBarriersSuspension, IBImplicitGroupBased, DefaultOneDriveInformationBarrierMode.
The parameters are already available in the released SharePoint Online Management Shell v 16.0.22810.
The descriptions are based on https://learn.microsoft.com/en-us/purview/information-barriers-sharepoint.

@JohanFreelancer9

@JohanFreelancer9  Happy to. Thank you.

@PowershellScripts

@get-itips @tseward

@tseward

@tseward Gentle reminder

@tiburd Please merge this PR. Thanks


plugin: implement line highlighting metastring for protosaurus language

Prerequisite: https://github.com/imballinst/protosaurus/pull/34.
This PR implements line highlighting metastring for protosaurus language. Hence, we can do this:
```protosaurus collapsible title="Hello world" {1,3,5-8}
message Booking {
  // ...
}
```

That will make a collapsible with the title "Hello world", and will highlight the first line, second line, and 5th to 8th line.

Technical wise, we have one new information in MetastringInfo, highlightedLines. This field is the one that we will use to highlight lines. When we iterate lines in the code block, then it will be used to determine whether the line should be highlighted or not.
export interface MetastringInfo {
  title: string;
  isCollapsible: boolean;
  highlightedLines: number[];
}

Signed-off-by: Try Ajitiono<EMAIL_ADDRESS>

Thanks @dio for the review!


Fix ESC Shortcut (Backport #1205)

Backport of #1205

Closing this PR, I will backport this bugfix using mergify, when the original PR is merged on rolling


versions 2.1.3 and later break full webapi support

what doesn't work for me - authenticating usually fills out files in ./homebridge/xboxtv with authentication and input info - that works on version 2.1.2
versions 2.1.3 and later break switching inputs and custom buttons . re-authenticating doesn't fix it. removing device info and reinstalling plugin doesn't either. after authenticating webapi files: authtoken_xxxxxxxx, inputs_xxxxxxxx remain empty. my guess is that information fails to be pulled from the machine.
reverting back to 2.1.2 fixes the problem
we can talk in polish if you prefer that

Can You enable debug in plugin config Advanced Section  restart Homebridge and get the log?

homebridge.log.txt
i uninstalled the plugin and cleared device info in .homebridge/xboxtv, then clean install and configure device as the readme says (authorized console using authorization process in settings). this is the error I replicated while using remote control (arrow keys).

Your console is not authorized, please post also your config.json.

{
    "devices": [
        {
            "name": "Xbox",
            "host": "<IP_ADDRESS>",
            "xboxLiveId": "F4000EC3AFBC90EF",
            "clientId": "b376baa2-2c63-4e73-a4a0-fc28309fccce",
            "clientSecret": "SXP7Q~npCx16~kQdc55g_PC7aMCcgbGF1qkH7",
            "disableLogInfo": false,
            "disableLogDeviceInfo": false,
            "enableDebugMode": true,
            "webApiControl": true,
            "volumeControl": 0,
            "infoButtonCommand": "view",
            "getInputsFromDevice": false,
            "filterGames": false,
            "filterApps": false,
            "filterSystemApps": false,
            "filterDlc": false,
            "enableMqtt": false,
            "mqttAuth": false,
            "mqttDebug": false,
            "xboxWebApiToken": "M.R3_BAY.7c03374a-04fc-6ca1-73dd-6d9dd5060093"
        }
    ],
    "platform": "XboxTv"
}

Please remove clientId and clientSecret and authorize the console again.
Also always run the plugin as child bridge, this prevent to crash the home bridge.

homebridge.log3.txt
log after removing client and client secret and authorizing console again. log says anonymous login, files in .homebridge/xboxtv still empty

I don't se any info about authorization check in your log. Can you make and post vide with authorization process?
Anonymous login is other thing and have nothing to do with web api,

oops, accidentally in last update webApiControl properties was removed, please update to v2.2.2

updated the plugin, reauthorized the console, log still says 'unauthorized'
https://drive.google.com/file/d/16rbIIr_Au3IiOe4HCZW4XONEAjKZfw8v/view?usp=sharing
there's the link to the authorization video

reverting to earlier version - 2.1.0 fixes the issue - log says "Web Api enabled" and files in ./homebridge/xboxtv contain data upon server restart

Arę You sure You press Activate Console on end the authorization process?

.......... yup.
of course it was something trivial like this. worked the second I clicked 'activate'.
everything works fine now. thank you so much for the support.
consider issue closed and me silly :P


cleanup(ci): Delete unused cached state patch job

Motivation
The cached state isn't used for Docker unit tests, so its patch job isn't needed.
There is no corresponding job in the Docker unit tests:
https://github.com/ZcashFoundation/zebra/blob/main/.github/workflows/ci-unit-tests-docker.yml#L78
The job and patch are correctly configured in the Docker GCP integration tests:
https://github.com/ZcashFoundation/zebra/blob/main/.github/workflows/ci-integration-tests-gcp.yml#L105
https://github.com/ZcashFoundation/zebra/blob/main/.github/workflows/ci-integration-tests-gcp.patch.yml#L30
PR Author Checklist
Check before marking the PR as ready for review:

[x] Will the PR name make sense to users?
[x] Does the PR have a priority label?
[x] Have you added or updated tests?
[x] Is the documentation up to date?

Not a significant change.
If a checkbox isn't relevant to the PR, mark it as done.
Solution
Delete the unused duplicate patch job.
Testing
If CI passes we're fine here.
Review
This is a low priority cleanup. It can merge at any time during the release process, because it doesn't need to go in the changelog.
Reviewer Checklist
Check before approving the PR:

[ ] Does the PR scope match the ticket?
[ ] Are there enough tests to make sure it works? Do the tests cover the PR motivation?
[ ] Are all the PR blockers dealt with?
PR blockers can be dealt with in new tickets or PRs.

And check the PR Author checklist is complete.

This PR can merge at any time during the release process, because it doesn't need to go in the changelog.


Fix incorrect encoding strings in FileUploadInterceptorTest (cherry-pick fix for 2.6.x)

Fix incorrect encoding strings in FileUploadInterceptorTest (cherry-pick fix for 2.6.x)
Merge pull request #385 from JCgH4164838Gh792C124B5/local_25x_TstFix1
Fix incorrect encoding strings in FileUploadInterceptorTest
(cherry picked from commit 47c87bc62cd41c668146e18c1b06d49ecec7fd0a)

Hi.  Looks like the cherry-pick for 2.6.x was clean.  If anyone notices an issue let me know.

Coverage remained the same at 48.545% when pulling 54d01ae72b0421bc23580916356ddca1e87d7c99 on JCgH4164838Gh792C124B5:local_26x_TstFix1 into 6504e674b098efad90888ee198b7d977621123b8 on apache:master.

LGTM 👍


Update to new rust

has an ICE though :/

This should work now!

actually it's not perfect yet :(

I think that fixes it.

This should be good to go!


Project Console - UI issues in View Companies and View Signatures when Project name and Company name is too long

Background
Prerequisite

Project having long name should exist
Company having long name should exist and should have signed CLA for the project with long name

Steps to follow

Launch https://project.dev.lfcla.com
Login as Project Manager
Click on CloudFoundry.org Foundation, Inc.

Issue1
4. Click on VIEW COMPANIES for project Issue741TestIssue741TestIssue741TestIssue741TestIssue741TestIssue741TestIssue741TestIssue741TestIssue741TestIssue741TestIssue741TestIssue741TestMoreth
5. Observed that project name overlaps on CLOSE button

Issue2
6. Click on VIEW SIGNATURES for project Issue741TestIssue741TestIssue741TestIssue741TestIssue741TestIssue741TestIssue741TestIssue741TestIssue741TestIssue741TestIssue741TestIssue741TestMoreth
7. Observed that project name overlaps on CLOSE button

Issue3
8. Columns headers are not aligned properly in VIEW SIGNATURES
NOTE: This alignment issue is not seen when browser zoom level is below 90%

@hnexokonkwo can you review/diagnose/resolve?

@dealako Verified and working fine.

The old v1 console is deprecated and removed.