Feature/sdl0243 manager update display capability

Fixes #1158
This PR is ready for review.
Risk
This PR makes minor API changes.
Testing Plan
Extend unit tests to confirm display capability/capabilities conversion is as expected.
Summary
This PR changes SystemCapabilityManager according to SDL-0243 to make new capabilities available and also convert DisplayCapability and DisplayCapabilities objects.
Changelog
Existing SystemCapabilityTypes are marked as deprecated hence will appear as deprecated if apps are using them.
Enhancements

Adds new capability to the manager
Adds conversion of display capability objects for developer's convenience

CLA

[ ] I have signed the CLA

@yLeonid livio is taking over this PR due to time constraints, as this was needed last week. Thank you.

Closing as duplicate of #1188


Support monorepo builds in Next.js adapter

Currently, the Next.js adapter is unable to specify a custom build command to run the Angular application builder. It also makes certain assumptions that no longer hold true in monorepo contexts. We adjust those conditions to enable builds of Next.js projects using monorepo tooling.

Overall, this seems like a reasonable approach and I see now that this follows the pattern used by the Angular adapter as well.
My high level feedback is: Any env vars that we introduce as inputs into the build adapter should be treated as a public API for other framework (adapter) authors down the road. We should make sure that this API is 1) thoroughly documented, and 2) follows our usual standards of API design including go/easy-to-use-and-hard-to-misuse (also see go/tott/523).
In particular, I would recommend re-examining our current set of env vars. As of right now, we have:

process.env.MONOREPO_PROJECT
process.env.FIREBASE_APP_DIRECTORY
process.env.MONOREPO_BUILDER
process.env.MONOREPO_COMMAND

It seems like some (MONOREPO_BUILDER) are not always used, while others (MONOREPO_PROJECT) can probably be removed all together. It also seems like a bug that FIREBASE_APP_DIRECTORY is only ever respected in MONOREPO contexts. IMO we should either rename it to MONOREPO_APP_DIRECTORY or always respect it.

I wonder if our API could be simplified down to:
process.env.MONOREPO_PROVIDER = "nx"?
This gives (community) adapter authors the most flexibility as opposed to having to handle our buildpack-specific logic such as MONOREPO_COMMAND, and we can have a shared util for example:
getBuildCommand(monorepoProvider) => providerToBuildCommand[monorepoProvider];

It seems like some (MONOREPO_BUILDER) are not always used

MONOREPO_BUILDER is not used in the Next.js buildpack, but is necessary for the Angular buildpack. The Nx buildpack is responsible for reading project config files (i.e. project.json), which is how we determine which application builder Angular is using in an Nx monorepo (in non-Nx environments we would read the angular.json, but there is no angular.json for Nx + Angular projects). We need some way to pass the information of which app builder is being used. The alternative would be to  have the adapter read Nx project config files.
I do agree that MONOREPO_BUILDER is optional in many circumstances, however. This should be reflected in documentation.

while others (MONOREPO_PROJECT) can probably be removed all together

In the case of Nx, this is true - the MONOREPO_PROJECT is not strictly necessary because we can simply run nx run build from the context of the app directory and Nx will only build that app. Nx also supports nx run [project]:build to build a specific project. However, turbo run build by default builds every project regardless of the cwd context, and requires a --filter flag to run a build task for a single project (docs). So technically in the adapters, we should be using MONOREPO_PROJECT, but I haven't made the change yet.

It also seems like a bug that FIREBASE_APP_DIRECTORY is only ever respected in MONOREPO contexts. IMO we should either rename it to MONOREPO_APP_DIRECTORY or always respect it.

We should probably always respect it to support setups where the repo root != the app root.

Overall LGTM pending a few small nits.
My main ask following this CL is to see if we can encapsulate all of the env var wrangling in a single nx library that can be shareable across both the angular and the next adapters

Sounds good - do you mean a single monorepo library?


Removing and item for array does not update the list until user scrolls

If I have a list of items:
<virtual-scroll         (update)="themeItems = $event"         [items]="themes"         class="list-group">         <theme-item             class="list-group-item"             *ngFor="let themeItem of themeItems"             [theme]="themeItem"             (onDeleteTheme)="deleteTheme( $event, confirmDeleteTheme )">         </theme-item>     </virtual-scroll>
onDeleteTheme removes an item for "themes" which is bound to items.
Once removed calling refresh() does not  update the list. The item only gets removed once I scroll a little bit. Am I missing something here?

The only work around I have found so far is removing the viewPortItems manually and calling update, but this means that the number of items shown is one less per delete until the user scrolls.
ie.
this.virtualScroll.update.emit( pull( this.virtualScroll.viewPortItems, this.themeToDelete ) );

I struggle with the same problem.

@blingerson, can you try to make themes an immutable array? ie. when you remove a theme from the array make sure to create a new array:
themes = themes.filter(theme => theme.id !== idOfThemeToBeRemoved)

Any update on this?

This should be fixed in the latest package on npm. Can you try it & let me know if it's still occurring? Thanks.

Closing this since I haven't received a response from the original poster. Please re-open if you continue to experience this issue.

@speige, this did indeed fix my issue. Thank you.


Add support for azure credential chain

This PR adds some improvements to how to authenticate in the Azure extension.
This is the first step towards implementing the feature request in https://github.com/duckdblabs/duckdb_azure/issues/6.
Interface changes
The complete set of parameters for the extension is now:

azure_connection_string
azure_account_name
azure_credential_chain
azure_endpoint

To authenticate the requests, the extension does, in this order:

check if the connection string is set, if so, use that.
check if the account name is set. If so, it:

checks the azure_credential_chain for which credential providers to check in order
the default is 'none' which means no authentication will be used.
the user can override the chain by specifying in a ; separated string one or more of the following: cli, env, managed_identity, default or none. Checkout the Azure docs on how to use them (https://github.com/Azure/azure-sdk-for-cpp/blob/main/sdk/identity/azure-identity/README.md#environment-variables). For example to use the full DefaultAzureCredential chain, set it to 'default'
the endpoint defaults to blob.core.windows.net but can be overridden through azure_endpoint

Examples
These changes simplify some things:
Public containers:
For fully public containers, reading and listing is now much cleaner not needing to set :
set azure_account_name='<azure storage account name>';
set azure_credential_chain = 'none';
SELECT * FROM 'azure://<container>/<path>/<to>/<file>.parquet';
SELECT * FROM 'azure://<container>/<path>/<to>/*.parquet';

CLI
Authentication using the cli can now work as follows:
Firstly, using the azure cli log in to your azure account using:
az login

This will forward you to a browser and ask you to login.
Now from duckdb, run:
set azure_account_name='<azure storage account name>';
set azure_credential_chain = 'cli';
SELECT * FROM 'azure://<container>/<path>/<to>/<file>.parquet';

TODO
Much more testing. The CLI authentication is tested but only locally, not in CI atm. The few other credential providers that are included in this PR (env, managed_identity), they are fully untested.
However, I feel like this is quite finicky to test properly test anyway, due to the different types of environments that you need to setup to test this. Since its only a little amount of code on DuckDB side with just a few lines, and the CLI log-in working very well, I think pushing this into the nightly repo allowing people to try it out on 0.9.1 is a nice way forward. Also to try out the whole workflow of deploying nightly releases for extensions allowing people to use a stable duckdb + an unstable/nightly extension.
Of course the next step is to add more testing infrastructure:

through azurite where possible
setting up test accounts with data sets in CI
then set up test cases for all the different credential providers

Thanks for the review @carlopi! There is no requirement on httpfs! the azure sdk ships its own http stuff.
The account name is a "storage account" name which is part of the url for the objects: https://<account_name>.blob.core.windows.net/<container_name>/file.ext so that is required afaik!
will check out the rest tomorrow!

Another question: would it not be nice to offer a load_azure_credentials('my_name', 'cli') option?

@carlopi That's a good point. Indeed we can pass a profile name to the cli credential provider. Currently it just picks the default.
For this PR i would argue this is good enough. We can consider improving this in a follow up
In the grand scheme of things: this comes down to the major question of proper API for table scans with credentials. What we would like to support is to basically be able to create and switch between multiple sets of credentials


[SUPPORT] MOR taking more time than COW using HoodieJavaWriteClient

I am doing a PoC of HUDI and I noticed that while using HoodieJavaWriteClient.java, the writes in case of MOR are taking more time when compared to COW.
But when using DataFrameReader, MOR is faster than COW for the same dataset.
In both cases I am doing 'insert' operation.
In case of java client, I notice a gradual decrease in throughput. There are total of 7million rows and I am batching with 200k rows.
I have deployed code in Azure databricks cluster and worker nodes pick up the task of executing below code snippet.
Attaching code snippet using java client :
          HoodieKey key = new HoodieKey(UUID.randomUUID().toString(), "partitionPath");
          HoodieAvroPayload payload = new HoodieAvroPayload(Option.of(rec));
          HoodieAvroRecord<HoodieAvroPayload> record = new HoodieAvroRecord<>(key, payload);
          records.add(record);
        }
      }

      String tableName = "tableName";
      String tablePath =<EMAIL_ADDRESS>+ tableName;
      Configuration hadoopConf = new Configuration();
      hadoopConf.set("fs.azure.account.key","xxx");
      Path path = new Path(tablePath);
      FileSystem fs = FSUtils.getFs(tablePath, hadoopConf);
      if (!fs.exists(path)) {
        HoodieTableMetaClient.withPropertyBuilder()
            .setTableType(tableType)
            .setTableName(tableName)
            .setPayloadClassName(HoodieAvroPayload.class.getName())
            .initTable(hadoopConf, tablePath);
      }

      HoodieWriteConfig cfg = HoodieWriteConfig.newBuilder().withPath(tablePath)
          .withSchema(avroSchema.toString())
          .withParallelism(2, 2)
          .withDeleteParallelism(2)
          .forTable(tableName)
          .withIndexConfig(HoodieIndexConfig.newBuilder().withIndexType(HoodieIndex.IndexType.INMEMORY).build())
          .withCompactionConfig(HoodieCompactionConfig.newBuilder().archiveCommitsWith(20, 30).build())
          .build();
      HoodieJavaWriteClient<HoodieAvroPayload> client =
          new HoodieJavaWriteClient<>(new HoodieJavaEngineContext(hadoopConf), cfg);

      String commitTime = client.startCommit();
      client.insert(records, commitTime);
      client.close();

Environment Description

Hudi version : 0.11.0

Spark version : 3.2

Hive version :

Hadoop version :

Storage (HDFS/S3/GCS..) : Azure storage account - StorageV2 (general purpose v2)

Running on Docker? (yes/no) : no

as long as use bulk_insert with NonSortPartitioner you can get better performance in cow mode than mor mode.
otherwise, cow table still need to copy small files into bigger one in every commit, that's also cause write amplification

But , I am not using bulk_insert option here as java client does not support it

If not using bulk_insert, in my experience mor mode should be faster than cow mode in most of the cases due to write amplification, I've tested it.

ok, I have noticed the same when using DataFrameReader. But after moving to java client, I see this behavior of MOR being slower than COW

OK understood, could you provide more information like the file layout and timeline of the MOR table?
btw, is there necessary to use HoodieJavaWriteClient? I think there are also some limitations on MOR when using it

What exactly do you mean by file layout and timeline? Could you elaborate?
I am reading just 1 table from SQL DB table which has basic column types (around 15 columns). I have chosen the simplest table possible to begin with. I have created default partition for now and all 7million rows go into the same partition.
It has become necessary to use HoodieJavaWriteClient as  sparksession, sparkcontext and sqlcontext are not available inside worker nodes of databricks cluster. And I believe without sparkcontext it is not possible to create DataFrameReader.

Can just provide screenshots of data files and upload the files in .hoodie here

Attached are the screenshots of files under the partition folder

and some of the files in .hoodie folder

@tommss  there are no delta-logs in the path,  normally if you use a Global index, should generate delta-log first. I go through the source code of  HoodieJavaCopyOnWriteTable and HoodieSparkMergeOnReadTable and found there are no differences between them in insert behavior, HoodieSparkMergeOnReadTable just inherits the insert method from HoodieJavaCopyOnWriteTable.

Aren't delta-log files created when there are any updates? But in my case I am doing only inserts. There are no updates in my batch. I am just dumping data from DB table to file

not exactly.  in this case, you choose MemoryIndex which is a CanIndexLog index. so data can append to delta-log even if a new record insert. but for now HoodieJavaMergeOnReadTable is unfinished but this should be normal behavior
I'm not exactly sure what's your requirements really are.  the Dataframe or rdd is already distributed, why do you need to create a spark session in the worker node?

I changed index to Bloom to see if it makes any difference, but it does not.
What do you mean by HoodieJavaMergeOnReadTable is unfinished ?
Below is what we are trying to achieve in the cluster and the reason for using hudi java client.

HoodieJavaWriteClient use HoodieJavaMergeOnReadTable for handle mor table, and HoodieJavaMergeOnReadTable does nothing but inherits function from HoodieJavaCopyOnWriteTable.
So if you cannot change to SparkWriteClient or Flink, we need to implement HoodieJavaMergeOnReadTable's function

why don't you create a dataframe on top of rdd and then save it to hudi?
btw have you joined hudi's slack? we can discuss this

https://hudi.apache.org/community/get-involved  just click the join group link

Already discussed with @tommss via slack, I recommend using SparkWriteClient
@tommss do you have any update about this?

Thanks for the support @fengjian428 !
@tommss do you need further assistance? we may close this in a week time due to inactivity

feel free to raise a new issue if you are looking for further enhancement.


Possible to have a customEventItem?

I like your project so far and it works really well. I see we can pass custom title and extra components into for when the popper is open, is it possible to add customEventItem so the user has control over how it looks on the scheduler?

Hi
Since this component is opinionated and totally depends on MUI, so the event item is intentionally been designed with the look & feel of MUI.
However, the event item is just a paper component, I believe you can target it and style it with your theme setup, though it would change all event items and not cherry-picked items, if you share a sandbox and try to tell me what you want to achieve, I might give a better help.
btw: if you just want to change the background, you can pass color: string to the event item object and it will be applied, I think this is not mentioned in the ReadMe.

I use MUI so don't mind the opinionated look. I was thinking it would be nice to show additional data points on scheduler like this example. Where you have the title, time, and then a location at the bottom in this screenshot. It seems the EventItem is limited to just title and time.

I believe you can accomplish that if you update to v2.5.1
See sandbox example: https://codesandbox.io/s/custom-event-renderer-rkf4xw
Known that it's not applicable to month view, or multi-day events, It will mostly be broken if you apply it to these cases, since an event height is barely have enough height in those cases.
Hope this helps

Great! Thanks for the quick turn around, I'll take a look.


Support react 17 for @microsoft/file-browser

Category

[ ] Question
[ ] Documentation issue
[x] Bug

Expected or Desired Behavior
Using @microsoft/file-browser should work with<EMAIL_ADDRESS>Observed Behavior
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@types/react
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer @types/react@"*" from<EMAIL_ADDRESS>npm ERR!   node_modules/@microsoft/file-browser
npm ERR!     @microsoft/file-browser@"*" from the root project
npm ERR!   1 more (@types/react-dom)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>|| ^15.x || ^16.x" from<EMAIL_ADDRESS>npm ERR! node_modules/@uifabric/utilities
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@microsoft/file-browser
npm ERR!     @microsoft/file-browser@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Steps to Reproduce
Use<EMAIL_ADDRESS>with @microsoft/file-browser.

As part of a repository clean up effort we are closing older issues. If this issue remains, please: open a new issue, reference this issue, and provide any additional details that may help in resolution. Thank you for your understanding as we work to improve our responsiveness.


TextArea Component

Create a TextBox Component

Support for custom class names (string or array)
Support for a value prop to set the default value for the text area
Support for disabled state (isDisabled prop)
Support for max length (maxContentLength prop)
Support for id prop (for use with html for in a label)
Support for isError
Support for errorMessage
When max length is reached, error state should be enabled with default error message

@mmellado should we remove this

Support for a value prop to set the default value for the text area

and use the props.children instead for the value?

Fixed by #39


Add support for JS backend

Hey there, I've made a library (NULID) and I wanted to implement support for the JS backend, but it seems like nint128 doesn't support the JS backend, but it does support the NimVM, so I'm wondering if it'd be possible to also support JS at the same time?

The problem with the JS backend is that it does not support 64-bit integers and the Int128 and UInt128 object use 64-bit integers.
At the time I designed nint128 I did not intend to support the JS backend, as there are libraries for large integers in JS.
See also this answer given on the forum.

Thank you for your response! I'll likely use BigInts then in my library for this use, and thank you for this amazing library :)


Digital Ocean plugin unstable (dobs)

Summary
I've been using the dobs plugin for rexray for a couple of months, and frequently, the volume gets disconnected and never reconnects
Bug Reports
This section is for issues that relate to discovered problems or bugs.
Version
$ rexray version
REX-Ray
-------
Binary: /usr/bin/rexray
Flavor: client+agent+controller
SemVer: 0.9.2
OsArch: Linux-x86_64
Branch: v0.9.2
Commit: 9c7b7329884bf2feeffe101fc5dc3a239730427d
Formed: Wed, 28 Jun 2017 20:09:01 UTC

libStorage
----------
SemVer: 0.6.2
OsArch: Linux-x86_64
Branch: v0.9.2
Commit: 7368564cc71be9a0dbe03ddfbaeda281232eee72
Formed: Wed, 28 Jun 2017 20:08:31 UTC

Expected Behavior
If a container is running on the same node for weeks, the volume should continue to be accessible and not disconnect
If a container gets rescheduled, the volume should be attached to the new node
Actual Behavior
The volume becomes unavailable and the only way to fix is detaching the volume, removing the service that relies on it, and redeploying the service
Steps To Reproduce
Use Rexray and dobs plugin for a couple weeks
Configuration Files
libstorage:
  service: dobs
  server:
    services:
      dobs:
        driver: dobs
        dobs:
          token: xxx
          region: nyc1
          tag: rexray
          convertUnderscores: true
          statusMaxAttempts: 10
          statusInitialDelay: 100ms

$ docker stack ps --no-trunc proxy

ID                          NAME                IMAGE                                                                                NODE                DESIRED STATE       CURRENT STATE             ERROR               PORTS
j7jw8eiu7zex7cnd9hevotykj    \_ proxy_proxy.1   vfarcic/docker-flow-proxy:latest@sha256:598f4ae2eb4a00a044ecf79e263a953b2acb034cb827cd4ffe2d9637c9787951   swarm-worker-02     Shutdown            Rejected 24 minutes ago   "VolumeDriver.Mount: {"Error":"resource not found"}
"
7sa8j17548dm0ifl9m9rqngy1    \_ proxy_proxy.1   vfarcic/docker-flow-proxy:latest@sha256:598f4ae2eb4a00a044ecf79e263a953b2acb034cb827cd4ffe2d9637c9787951   swarm-worker-02     Shutdown            Rejected 24 minutes ago   "VolumeDriver.Mount: {"Error":"resource not found"}
"
5uymxo3e2wzkctaheoel0790p    \_ proxy_proxy.1   vfarcic/docker-flow-proxy:latest@sha256:598f4ae2eb4a00a044ecf79e263a953b2acb034cb827cd4ffe2d9637c9787951   swarm-worker-02     Shutdown            Rejected 24 minutes ago   "VolumeDriver.Mount: {"Error":"resource not found"}
"
qgjsbm3w8rcntp32rzgavu0p6    \_ proxy_proxy.1   vfarcic/docker-flow-proxy:latest@sha256:598f4ae2eb4a00a044ecf79e263a953b2acb034cb827cd4ffe2d9637c9787951   swarm-worker-02     Shutdown            Rejected 24 minutes ago   "VolumeDriver.Mount: {"Error":"resource not found"}

Try something like:
libstorage:
  service: dobs
  integration:
    volume:
      operations:
        create:
          default:
            size: 1
        mount:
          preempt: true
        unmount:
          ignoreUsedCount: true
dobs:
  region: fra1

Worked for me...

yea the mount: preempt: true makes a big different, thanks!

Thanks for the assist @dave08!
@patrickleet sorry for the lack of response on our side. I just missed this. Pre-emption is required in the scenario where a volume needs to be moved from one node to another.
As for the volume becoming unavailable in the first place, that is most likely more on the Digital Ocean side. Since REX-Ray is control plane only (it simply makes API calls to Digital Ocean), there shouldn't be anything it can do make a volume become unavailable after working for days/weeks/months.


Updated utils to prevent errors on Django master

Django 1.9 will drop django.utils.importlib in favour of the stdlib's version.
Django 1.8 changes the way the standard loaders work, because of the multiple-template engine changes. The change to instantiating the loader should work for DjangoTemplates, though I have no idea if it'd work for others.

Thanks for your work!
There is a couple of things we could try to improve here

add importlib as a dependency - as it's only valid for some installations, perhaps it would be enough to just document it in README.rst?
bump the version

I'll have a look into logic this week.

add importlib as a dependency - as it's only valid for some installations

Django 1.7+ requires python 2.7 or 3.2+ all of which should have the python stdlib importlib
Django 1.6.x requires python 2.6.5 or 3.2+, and defaults to using the python stdlib importlib for 3.2+, falling back to it's own backport of import_module for python 2.6+
Django 1.5.x requires python 2.6.5 and has experimental support for 3.2+, and always uses the Django backport of import_module
Django 1.4.x requires python 2.5+, without any 3.x support, and uses the backport of import_module always.

As far as I can reason out, the try/except should cover pretty much every valid installation you could be expected to support.

Oh, you're right! Sorry, I was missing the point about importlib.
So now we'll possibly just want to add tox / travis config for recent Django /  Python versions.

Right, so I've run the test suite and got following results:
________________________________________________ summary ________________________________________________
ERROR:   py3.4-django1.7: commands failed
ERROR:   py3.3-django1.7: commands failed
ERROR:   py2.7-django1.7: commands failed
  py3.4-django1.6: commands succeeded
  py3.3-django1.6: commands succeeded
  py2.7-django1.6: commands succeeded
  py2.6-django1.6: commands succeeded
  py3.3-django1.5: commands succeeded
  py2.7-django1.5: commands succeeded
  py2.6-django1.5: commands succeeded
  py2.7-django1.4: commands succeeded
  py2.6-django1.4: commands succeeded
  py2.7-django1.3: commands succeeded
  py2.6-django1.3: commands succeeded

I guess we might want to address the Django 1.7 issues?
Here is a stack trace from Django 1.7 / Python 3.4 run:
======================================================================
ERROR: test_explicit_name (templatefinder.tests.AppDirectoriesLoaderTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/piotr/Opensource/django-template-finder/templatefinder/tests.py", line 10, in test_explicit_name
    self.assertEqual(['404.html'], find_all_templates('404.html'))
  File "/home/piotr/Opensource/django-template-finder/templatefinder/utils.py", line 64, in find_all_templates
    loader_class = getattr(import_module(module), klass)
  File "/home/piotr/.virtualenvs/django-template-finder/lib/python3.4/importlib/__init__.py", line 109, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 2254, in _gcd_import
  File "<frozen importlib._bootstrap>", line 2237, in _find_and_load
  File "<frozen importlib._bootstrap>", line 2226, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 1200, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 1129, in _exec
  File "<frozen importlib._bootstrap>", line 1471, in exec_module
  File "<frozen importlib._bootstrap>", line 321, in _call_with_frames_removed
  File "/home/piotr/.virtualenvs/django-template-finder/lib/python3.4/site-packages/django/template/loaders/app_directories.py", line 33, in <module>
    app_template_dirs = calculate_app_template_dirs()
  File "/home/piotr/.virtualenvs/django-template-finder/lib/python3.4/site-packages/django/template/loaders/app_directories.py", line 21, in calculate_app_template_dirs
    for app_config in apps.get_app_configs():
  File "/home/piotr/.virtualenvs/django-template-finder/lib/python3.4/site-packages/django/apps/registry.py", line 137, in get_app_configs
    self.check_apps_ready()
  File "/home/piotr/.virtualenvs/django-template-finder/lib/python3.4/site-packages/django/apps/registry.py", line 124, in check_apps_ready
    raise AppRegistryNotReady("Apps aren't loaded yet.")
django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.

Do you have any idea how to address this? Perhaps we need to adjust runtests.py? If not I should be able to help with this.

Off the top of my head, I believe that:
if hasattr(django, 'setup'):
    django.setup()

will be necessary in runtests.py (after django.configure) to run the tests on 1.7+, because of the appconfig refactor

Cheers. I'll try that.

Awesome! I have rebased this origin/master and all went well this time. As I cannot push to your PR, I'm opening a separate one and merging this in right away.
Many thanks for this fix! :bow:


sherlock: reduce verbosity of database output to a minimum

Review the current output sherlock writes to the Lasair database and reduce to the minimum feasible content set that doesn't hamper potential science exploits.

There is now a lite parameter added to the Sherlock transient_classifier object (Default False).
classifier = transient_classifier(
    log=log,
    settings=settings,
    ra=ra,
    dec=dec,
    name=name,
    verbose=verbose,
    updateNed=False,
    lite=True
)
classifications, crossmatches = classifier.classify()

Adding lite=True does 2 things:

Returns only the top-ranked matches in the crossmatches list, and
Returns only the most pertinent information for those top-ranked sources

This should drastically reduce the Sherlock footprint in the transient database.
Here is the lite column listing with example values:
transient_object_id : ATLAS17jed
association_type : SN
catalogue_table_name : NED D/SDSS/2MASS/GLADE/PS1
catalogue_object_id : NGC0716
catalogue_object_type : galaxy
raDeg : 28.248701
decDeg : 12.708479
separationArcsec : 31.06
northSeparationArcsec : -16.204
eastSeparationArcsec : -26.493
physical_separation_kpc : 8.52
direct_distance : 56.6
distance : 65.88
z : 0.02
photoZ : 0.02
photoZErr : 0.01
Mag : 17.41
MagFilter : r
MagErr : 0.0
classificationReliability : 2


Add new MessageFlags

https://discord.com/developers/docs/resources/channel#message-object-message-flags

Thanks for your contribution!


test: fix registry cleanup to delete images after

A recent refactor updated the cleanup logic to only delete images in cleanup for local registries. The registry state needs to be reset regardless of the registry type.

/assign @karlkfi

/retest
Looks like a metrics flake maybe

/lgtm


Clean up processor documentation

Also expose ctors for the EventArgs types for mocking.

/azp run net - servicebus - tests

/azp run net - servicebus - tests

/azp run net - servicebus - tests


tip can't resove mathod

pdfView.fromAsset("text.pdf").pageFling(true).load() ;
The ide tip me    Cannot resolve method 'pageFling(boolean)'   .How to solve it?

this problem has been solved,


Add UI tests (OSOE-616)

Add tests that run the Tester app and test all the operations with a running Orchard Core application. This then needs to be run as part of OSOCE.
Jira issue

Something you might be interested in next @DAud-IcI?

Sure, I'm interested. But https://github.com/Lombiq/Open-Source-Orchard-Core-Extensions/issues/378 is a blocker to this for the reasons explained here.
Also do you think we still need the tester app as a separate executable if we have UI tests? I think the ApiClient can be created inside the normal UI test body, rather than running an application. They are communicating over HTTP anyway so I don't think they have to be separate processes.

Yes, we still need the tester app to be able to run the API client for quick manual tests, but the UI test doesn't need to drive that; rather, as you say, the API client can be used from the test itself (I'm calling it UI test because it's still interacting with a running app's UI, though not GUI).


support automatic pagination

Hey, nice library! I was thinking, it would be useful for the package to support pagination for get() (maybe other methods), to make it easier to retrieve large datasets. Maybe an optional paginate=True keyword argument? Thanks!

As it stands now, you can implement your own pagination with the $limit and $offset SoQL keywords. If you want to take a stab at implementing something like this with a default limit (1K records?) I think that would be be a  real benefit for many users of this library.


Rancher 1.3.0 upgrade ipsec containers doesnt start and doesnt write any logs

Rancher Version:
1.3.0
Docker Version:
1.12.3
OS and where are the hosts located? (cloud, bare metal, etc):
Rancher on 16.04 vm, failing host ipsec container on 14.04 bare metal host
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Singlenode MySQL Bind mount
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
Upgrade from 1.2.1 to 1.3.0
Results:
ipsec containers starts but dies on one host, no logs in docker logs output
60225cd4adb0        rancher/net:v0.7.5                         "/.r/r start.sh"         35 seconds ago      Up 35 seconds                                                               r-ipsec-ipsec-3-88aac834
c97be2d47cde        rancher/net:v0.7.5                         "sh -c 'touch /var/lo"   40 seconds ago      Up 40 seconds                                                               r-ipsec-ipsec-cni-driver-3-591ad6a1
root@bender:~# docker logs 60225cd4adb0
root@bender:~# docker logs c97be2d47cde
root@bender:~#

Expected:
Ipsec containers to run continously and not fail as on other hosts

I am guessing I have the same issue #7308  ?

@roflmao can you please share the logs of the network-manager?

network-manager logs consists:
Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
time="2017-01-05T19:51:08Z" level=info msg="Waiting for metadata"
Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
time="2017-01-05T19:51:55Z" level=info msg="Waiting for metadata"
Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
time="2017-01-05T19:52:46Z" level=info msg="Waiting for metadata"
Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
time="2017-01-05T19:53:38Z" level=info msg="Waiting for metadata"
Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
time="2017-01-05T19:54:29Z" level=info msg="Waiting for metadata"
Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
time="2017-01-05T19:55:16Z" level=info msg="Waiting for metadata"
Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
time="2017-01-05T19:56:02Z" level=info msg="Waiting for metadata"
Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
time="2017-01-05T19:56:54Z" level=info msg="Waiting for metadata"
Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
time="2017-01-05T19:57:45Z" level=info msg="Waiting for metadata"
Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
time="2017-01-05T19:58:36Z" level=info msg="Waiting for metadata"
Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
time="2017-01-05T19:59:28Z" level=info msg="Waiting for metadata"
Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
time="2017-01-05T20:00:15Z" level=info msg="Waiting for metadata"
Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
time="2017-01-05T20:01:07Z" level=info msg="Waiting for metadata"
Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
time="2017-01-05T20:01:53Z" level=info msg="Waiting for metadata"
Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
time="2017-01-05T20:02:40Z" level=info msg="Waiting for metadata"
Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
time="2017-01-05T20:03:28Z" level=info msg="Waiting for metadata"
Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
time="2017-01-05T20:04:20Z" level=info msg="Waiting for metadata"
Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
time="2017-01-05T20:05:11Z" level=info msg="Waiting for metadata"

Still broken in 1.3.2

getting the same:
2/23/2017 6:46:46 PMtime="2017-02-24T00:46:46Z" level=info msg="Waiting for metadata"
2/23/2017 6:47:29 PMCreating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
2/23/2017 6:47:48 PMtime="2017-02-24T00:47:48Z" level=info msg="Waiting for metadata"
2/23/2017 6:48:31 PMCreating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
2/23/2017 6:48:50 PMtime="2017-02-24T00:48:50Z" level=info msg="Waiting for metadata"
2/23/2017 6:49:33 PMCreating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
2/23/2017 6:50:01 PMtime="2017-02-24T00:50:01Z" level=info msg="Waiting for metadata"
2/23/2017 6:50:44 PMCreating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
2/23/2017 6:51:04 PMtime="2017-02-24T00:51:04Z" level=info msg="Waiting for metadata"
2/23/2017 6:51:47 PMCreating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
2/23/2017 6:52:17 PMtime="2017-02-24T00:52:17Z" level=info msg="Waiting for metadata"
2/23/2017 6:53:00 PMCreating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
2/23/2017 6:53:16 PMtime="2017-02-24T00:53:16Z" level=info msg="Waiting for metadata"
2/23/2017 6:53:59 PMCreating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
2/23/2017 6:54:17 PMtime="2017-02-24T00:54:17Z" level=info msg="Waiting for metadata"
2/23/2017 6:55:00 PMCreating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
2/23/2017 6:56:06 PMtime="2017-02-24T00:56:06Z" level=info msg="Waiting for metadata"
2/23/2017 6:56:49 PMCreating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
2/23/2017 6:57:22 PMtime="2017-02-24T00:57:22Z" level=info msg="Waiting for metadata"
2/23/2017 6:58:05 PMCreating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
2/23/2017 6:58:39 PMtime="2017-02-24T00:58:39Z" level=info msg="Waiting for metadata"
2/23/2017 6:59:22 PMCreating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
2/23/2017 6:59:45 PMtime="2017-02-24T00:59:45Z" level=info msg="Waiting for metadata"
2/23/2017 7:00:28 PMCreating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
2/23/2017 7:00:58 PMtime="2017-02-24T01:00:58Z" level=info msg="Waiting for metadata"
2/23/2017 7:01:41 PMCreating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
2/23/2017 7:02:03 PMtime="2017-02-24T01:02:03Z" level=info msg="Waiting for metadata"
2/23/2017 7:02:46 PMCreating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
2/23/2017 7:03:08 PMtime="2017-02-24T01:03:08Z" level=info msg="Waiting for metadata"
2/23/2017 7:03:51 PMCreating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
2/23/2017 7:04:30 PMtime="2017-02-24T01:04:30Z" level=info msg="Waiting for metadata"
2/23/2017 7:05:13 PMCreating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
2/23/2017 7:05:50 PMtime="2017-02-24T01:05:50Z" level=info msg="Waiting for metadata"
2/23/2017 7:06:47 PMCreating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2/23/2017 7:07:13 PMtime="2017-02-24T01:07:13Z" level=info msg="Waiting for metadata"
2/23/2017 7:08:04 PMCreating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
2/23/2017 7:08:51 PMtime="2017-02-24T01:08:51Z" level=info msg="Waiting for metadata"
2/23/2017 7:09:34 PMCreating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
2/23/2017 7:10:12 PMtime="2017-02-24T01:10:12Z" level=info msg="Waiting for metadata"

same here on one of our rancher hosts while others work perfectly. There is nothing different on this host compared to the other ones - at least nothing I'd know about:
docker logs -f 2f5806dba9e5 time="2017-03-01T09:46:41Z" level=info msg="Waiting for metadata"  Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host time="2017-03-01T09:47:28Z" level=info msg="Waiting for metadata"  Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host time="2017-03-01T09:48:14Z" level=info msg="Waiting for metadata"  Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host time="2017-03-01T09:49:00Z" level=info msg="Waiting for metadata"

I came accross the same messages in ubuntu server but cannot tell if it is the same.
getsockopt: no route to host: check if you have any CATTLE Chain in your iptables. You should have.
My routing table looks like:
route
<IP_ADDRESS>       *               <IP_ADDRESS>     U     0      0        0 docker0
<IP_ADDRESS> *               <IP_ADDRESS> UH    0      0        0 docker0
<IP_ADDRESS>      *               <IP_ADDRESS>     U     0      0        0 docker0
The reason was a race condition with dnsmasq. Check your logfile for
dnsmasq[1234]: Ignoring query from non-local network
If you have this line, you have a race condition between docker0 interface coming up and the start of dnsmasq.
Hope that helps

Rancher: 1.5.2
OS: Ubuntu 14.04
Im still unable to get my rancher agent working.
On the host:
root@bender:~# curl <IP_ADDRESS>:80
curl: (7) Failed to connect to <IP_ADDRESS> port 80: No route to host

ip route:
root@bender:~# ip route
default via <IP_ADDRESS> dev br0
<IP_ADDRESS> dev docker0
<IP_ADDRESS>/16 dev docker0  proto kernel  scope link  src <IP_ADDRESS>
<IP_ADDRESS>/24 dev br0  proto kernel  scope link  src <IP_ADDRESS>

iptables:
root@bender:~# sudo iptables -L -n --line-numbers -t nat
Chain PREROUTING (policy ACCEPT)
num  target     prot opt source               destination
1    DOCKER     all  --  <IP_ADDRESS>/0            <IP_ADDRESS>/0            ADDRTYPE match dst-type LOCAL

Chain INPUT (policy ACCEPT)
num  target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
num  target     prot opt source               destination
1    DOCKER     all  --  <IP_ADDRESS>/0           !<IP_ADDRESS>/8          ADDRTYPE match dst-type LOCAL

Chain POSTROUTING (policy ACCEPT)
num  target     prot opt source               destination
1    MASQUERADE  all  --  <IP_ADDRESS>/16        <IP_ADDRESS>/0

Chain DOCKER (2 references)
num  target     prot opt source               destination
1    RETURN     all  --  <IP_ADDRESS>/0            <IP_ADDRESS>/0

networkmanager container log:
Creating metadata client: Get http://<IP_ADDRESS>/2016-07-29/version: dial tcp <IP_ADDRESS>:80: getsockopt: no route to host
time="2017-04-03T09:22:03Z" level=info msg="routesync: DOCKER_BRIDGE=docker0, METADATA_IP=<IP_ADDRESS>"
time="2017-04-03T09:22:03Z" level=info msg="routesync: starting monitoring on bridge: docker0, for metadataIP: <IP_ADDRESS> every 60 seconds"
time="2017-04-03T09:22:03Z" level=info msg="Waiting for metadata"

Shouldnt i see some CATTLE chains in iptables? Is it the rancher-agent which sets this up? @leodotcloud

@roflmao The network-manager is what sets up these chains. Looking at the logs that you have posted, there seems to be some problem connecting to metadata. All the info needed to do the programming is locked inside metadata, so ...
Please find/ping me on https://slack.rancher.io when you have a setup in this state.

the metadata container had faulty settings for net.ipv4.conf.all.arp_announce, net.ipv4.conf.all.arp_filter and net.ipv4.conf.all.arp_ignore, thus arp failed for the container so the other infrastructure containers couldnt connect to it. Fixed by @leodotcloud by:
2028  cid=c87648478744 #metadata container id
 2029  pid=`docker inspect -f '{{.State.Pid}}' $cid`
 2030  echo $pid
 2031  mkdir -p /var/run/netns
 2032  ln -sv /proc/$pid/ns/net /var/run/netns/$cid
 2033  ip netns ls
 2034  ip netns exec $cid sysctl -w net.ipv4.conf.all.arp_filter=0
 2035  ip netns exec $cid sysctl -w net.ipv4.conf.all.arp_ignore=0
 2036  ip netns exec $cid sysctl -w net.ipv4.conf.all.arp_announce=0
 2037  docker exec -it $cid bash
 2038  ping <IP_ADDRESS>

Observation from @roflmao's setup:
On one of the hosts in the cluster, sysctl settings for arp_filter, apr_ignore, arp_announce were not set to the default value of 0. Due to this the network-manager container running on this host was not able to reach metadata IP (<IP_ADDRESS>). The container running rancher-metadata was able to see the ARP requests for the IP <IP_ADDRESS> but it was not responding because of the sysctl settings being wrong. Not sure why this host had these settings wrong in the first place.
Fix was to set these sysctl settings to 0. As the container was not started in privileged mode, couldn't modify the settings from the inside the container. Hence had to do it from the host after mapping the network namespace of the container.

Do we need to wait for #8527 to be fixed for this issue to be resolved?

@srinisubramanian As pointed out in the previous comment, this problem is due to a misconfiguration of the host. So there is need to wait for a fix.
#8527 is a failsafe approach (enhancement) to fix things if we ever run into this problem.

@srinisubramanian Can you check if you are having the same sysctl settings on your host where you are seeing the problem?

@leodotcloud All sysctl settings are already 0. That does not seem to be
the issue in my system at least. Any ideas what I can try?
I have an issue already open. #7306. I also have masquerading enabled.
Sent from my mobile.
On Apr 18, 2017 7:47 AM, "leodotcloud"<EMAIL_ADDRESS>wrote:

@srinisubramanian https://github.com/srinisubramanian Can you check if
you are having the same sysctl settings on your host where you are seeing
the problem?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rancher/rancher/issues/7280#issuecomment-294652874,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH9OiwYv3_16IS52V5qg8rpX3k5OVyheks5rxB0rgaJpZM4LaZ4E
.


jaxsim v0.5.0

Fixes #10
Fixes #11

Checklist

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

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe/meta.yaml:

ℹ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.

For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

# [...]
chex 0.1.87 requires setuptools, which is not installed.

@traversaro this looks strange to me. Should we really add setuptools in test requirements?

It seems that is a bug of chex upstream. Probably we can at least patch it in the feedstock.

But yes the quickest solution is to add setuptools to test dependencies.


doc: Add Amazon EKS to the list of implementations

What type of PR is this?
Add one of the following kinds:
/kind documentation
What this PR does / why we need it:
AWS Gateway API Controller is a new implementation of the Gateway API that may be of interest to the wider audience of the Gateway API project.
Which issue(s) this PR fixes:

Fixes #
Does this PR introduce a user-facing change?:

Thanks @liwenwu-amazon!
/lgtm
/approve

/ok-to-test

This auto-merged through my request for changes, which included a fix for the link for EKS so I've created a follow-up https://github.com/kubernetes-sigs/gateway-api/pull/1921


Error Compile

Compiled with problems:X
ERROR in ./src/pages/Board/Board.tsx 18:35-46
export 'DndProvider' (imported as 'DndProvider') was not found in 'react-dnd' (module has no exports)
ERROR in ./node_modules/react-icons/all.js 4:0-22
The requested module './io5' contains conflicting star exports for the names 'IoLogoAndroid', 'IoLogoAngular', 'IoLogoApple', 'IoLogoBitbucket', 'IoLogoBitcoin', 'IoLogoBuffer', 'IoLogoChrome', 'IoLogoClosedCaptioning', 'IoLogoCodepen', 'IoLogoCss3', 'IoLogoDesignernews', 'IoLogoDribbble', 'IoLogoDropbox', 'IoLogoEuro', 'IoLogoFacebook', 'IoLogoFlickr', 'IoLogoFoursquare', 'IoLogoGithub', 'IoLogoGoogle', 'IoLogoHackernews', 'IoLogoHtml5', 'IoLogoInstagram', 'IoLogoIonic', 'IoLogoIonitron', 'IoLogoJavascript', 'IoLogoLinkedin', 'IoLogoMarkdown', 'IoLogoNoSmoking', 'IoLogoNodejs', 'IoLogoNpm', 'IoLogoOctocat', 'IoLogoPinterest', 'IoLogoPlaystation', 'IoLogoPython', 'IoLogoReddit', 'IoLogoRss', 'IoLogoSass', 'IoLogoSkype', 'IoLogoSlack', 'IoLogoSnapchat', 'IoLogoSteam', 'IoLogoTumblr', 'IoLogoTux', 'IoLogoTwitch', 'IoLogoTwitter', 'IoLogoUsd', 'IoLogoVimeo', 'IoLogoVk', 'IoLogoWhatsapp', 'IoLogoWindows', 'IoLogoWordpress', 'IoLogoXbox', 'IoLogoXing', 'IoLogoYahoo', 'IoLogoYen', 'IoLogoYoutube' with the previous requested module './io'
ERROR in ./node_modules/react-dnd/lib/index.js 1:0-24
Module not found: Error: Can't resolve './types' in '/home/sanonichan/projetos/emendas/emendas-frontend/node_modules/react-dnd/lib'
Did you mean 'index.js'?
BREAKING CHANGE: The request './types' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '.mjs' file, or a '.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
ERROR in ./node_modules/react-dnd/lib/index.js 2:0-23
Module not found: Error: Can't resolve './core' in '/home/sanonichan/projetos/emendas/emendas-frontend/node_modules/react-dnd/lib'
Did you mean 'index.js'?
BREAKING CHANGE: The request './core' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '.mjs' file, or a '.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.
ERROR in ./node_modules/react-dnd/lib/index.js 3:0-24
Module not found: Error: Can't resolve './hooks' in '/home/sanonichan/projetos/emendas/emendas-frontend/node_modules/react-dnd/lib'
Did you mean 'index.js'?
BREAKING CHANGE: The request './hooks' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '.mjs' file, or a '.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.

WIP: https://github.com/react-dnd/react-dnd/pull/3369


move assets folder to correct location

@mihaiblaga89 this is correct fix. while assets get copied they were under wrong folder so would not make it to platformAssets. above fixes that issue

Codecov Report

Merging #346 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #346   +/-   ##
========================================
  Coverage    29.18%   29.18%
========================================
  Files           55       55
  Lines         6052     6052
  Branches      1381     1381
========================================
  Hits          1766     1766
  Misses        3066     3066
  Partials      1220     1220

Flag
Coverage Δ

#rnvunittests
29.18% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


NextJS 13 getServerSnapshot issue

When using react-rxjs inside a nextjs client component, I see this on the server sometimes:
- error Error: Missing getServerSnapshot, which is required for server-rendered content. Will revert to client rendering.

There's a similar issue on zustand: https://github.com/pmndrs/zustand/issues/886.
I only saw this error when I started using react-rxjs, seems to apply to state/hook related libraries? I'm not entirely sure why it would occur when I start using react-rxjs.

Hey, thank you for raising this issue. Currently looking for some options.

I only saw this error when I started using react-rxjs, seems to apply to state/hook related libraries? I'm not entirely sure why it would occur when I start using react-rxjs.

Yes, useStateObservable (or the hook returned by bind) uses React's useSyncExternalStore, and this one emits this warning when it's not set up for SSR.

Nice!

Fixed on 0.10.7


Authorization failed. These requirements were not met

Downloaded completed code and followed instructions from
https://github.com/microsoftgraph/msgraph-training-blazor-clientside/tree/main/demo
Get the following error when trying to login with AAD Account
Adding User.Read to requested permissions Adding MailboxSettings.Read to requested permissions Adding Calendars.ReadWrite to requested permissions info: Microsoft.AspNetCore.Authorization.DefaultAuthorizationService[2]       Authorization failed. These requirements were not met:       DenyAnonymousAuthorizationRequirement: Requires an authenticated user. info: Microsoft.AspNetCore.Authorization.DefaultAuthorizationService[2]       Authorization failed. These requirements were not met:       DenyAnonymousAuthorizationRequirement: Requires an authenticated user.

Apologies for the confusion - the app registration instructions in that README are outdated, which is causing your problem. Specifically, the app should be registered as a SPA, not a web app. Instructions here are correct.

@rhollamby were you able to try the updated app registration?


Linux Build

Considering it is open source, I think you could capture more contributors by supporting a Linux build.

Yes, there are people working on Linux porting (at least, at some rate). I'll look into a few more issues myself when I get time (I noticed some recent commits kind of messed things up).

@gavanw I am very pleased with this answer :smile:

I got it to run on linux with the following steps

clone the repo, extract resources
put the lzz binary from http://www.lazycplusplus.com/download.html into the main directory
remove the VoxelQuest folder
cmake .
make
create a folder (I call it "game" but it doesn't matter) and put the VoxelQuest executable there
move into the folder, and play the game!


fix: docs: small fixes

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

Comparison is base (3cdca8d) 86.85% compared to head (0f98523) 86.85%.
Report is 1 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2486   +/-   ##
=======================================
  Coverage   86.85%   86.85%
=======================================
  Files          85       85
  Lines        9296     9296
  Branches      481      481
=======================================
  Hits         8074     8074
  Misses       1222     1222

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


Support loading certificates from Cert-Manager

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you expect to see?
It would be great to be able to have cert-manager as an available option for loading TLS certificates

Hello @robd003 :wave:
Could you be more specific and the type of support you are expecting?
As of today, Traefik can perfectly handle the certificates issued by cert-manager. Indeed, Traefik will load the secrets defined on your Ingress, IngressRoute and HTTPRoute.


verification API

Verification of the CCA token is a three-legged procedure comprising cryptographic verification of the platform and realm tokens, as well as their hash-lock binding.
Platform

CBOR decode the Sign1 array
decode the payload into a Platform claims-set
fetch the instance-id to lookup the matching CPAK from the TA store
use the CPAK to verify the Platform Sign1

Realm

CBOR decode the Sign1 array
decode the payload into a Realm claims-set
fetch the RAK from the associated claim
use the RAK to verify the Realm Sign1

Binding

fetch the RAK hash algorithm identifier from the Realm claims-set
use it to hash the RAK
check that the nonce claim in the Platform claims-set matches the computed hash of the RAK

Adressed by #16


docs: instructions syntax

Here is what I have noted for myself.
The syntax to write instructions: "Represent the domain text_type for task_objective: ", where:

domain is optional, and it specifies the domain of the text, e.g., science, finance, medicine, etc.
text_type is required, and it specifies the encoding unit, e.g., sentence, document, paragraph, etc.
task_objective is optional, and it specifies the objective of embedding, e.g., retrieve a document, classify the sentence, etc.

The questions:

what is the exhaustive list of possible values for domain?
what is the exhaustive list of possible values for text_type?
what is the exhaustive list of possible values for task_objective?

Awesome work! 👍 Thank you for the models!

Hi, Thanks a lot for your interest in the INSTRUCTOR!
Although it may be hard to exhaustively list all possible values of domain, test type and task objective, we provide some examples in the table 4 of our paper.
Feel free to add more questions or comments!

@hongjin-su , thank you!
The info I was looking for.
domain = [
  'wikipedia',
  'news',
  'medicine',
  'biology',
  'reddit',
  'stackoverflow',
  'science',
  'quora',
  'coronavirus',
  'math',
  'physics'
]

text_type = [
  'question',
  'query',
  'answer',
  'summary',
  'sentence',
  'review',
  'post',
  'comment',
  'statement',
  'paragraph',
  'passage',
  'document'
]

task_objective = [
  'classify the sentence as positive or negative',
  'retrieve a duplicate sentence',
  'retrieve the supporting document'
]


Add spotbugs checks

Add more spotbugs checks

[x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[x] Ensure that the pull request title represents the desired changelog entry
[x] Please describe what you did
[x] Link to relevant issues in GitHub or Jira
[x] Link to relevant pull requests, esp. upstream and downstream changes
[x] Ensure you have provided tests - that demonstrates feature works or fixes the issue

May want to ignore CloudStatisticsTest.ui on Windows, or find some way to make really sure it's completed. Seems https://github.com/jenkinsci/cloud-stats-plugin/pull/32 just made it fail less often


MODE-2402 Changed the WF kit to use a transient binary store when no store is explicitly configured.

Looks great.


Pre-Anvil/Post-.mclevel Worlds Won't Load

I couldn't get any information on whether support was completely dropped for McRegion and Alpha level types, but what I do know is MCEdit doesn't even seem to attempt to load chunks. I even was able to load up the worlds with "minecraft_server.jar" files but the chunks don't load in MCEdit. The chunks will still load fine when I load up Minecraft, which means even when MCEdit creates the world, it corrupts nothing. It seems to only read .mca and .mclevel files.
The versions Infdev-Release 1.1. Namely the versions I used were Beta 1.3B, Beta 1.2_02 and the Infdev version that is accessible on the launcher.
I was using MCEdit v.<IP_ADDRESS>
My computer runs Windows 10. Although I don't think that matters for this case, it is in the guidelines.

To reproduce this issue, load up an Infdev-Minecraft 1.1 world and no chunks will appear.

I'll just use the original MCEdit for now.


Blinds module activated when opening het accessory page

Everytime i open a room in the accessory page within homebridge, the blinds (Fibaro Roller Shutter modules) in that room receive some sort of signal. I can hear the relays of the modules clicking. The plugin sends the last known value to the modules: i tested and confirmed this by:

changing the position of the blinds in homebridge
going to another room and back to the room with the blinds (position doens't change, you only hear the delays for blinds that are completely open or closed)
Change their position straight from the fibaro
Change rapidly to another room in homebridge and back to the room with blinds, before the blinds' state is updated in homebridge
This time the blinds do change position, to the values last known by homebridge / fibaro plugin.

I used homebridge and the plugin for a couple of years now, this problem only arrised today after i decided to upgrade the system.

@FBerriere, which update are you referring to ?

stale


Change ModListItem drag button to div

This would fix the issue of the mods not being dragged when pressing on the padding of the drag handle

I can squash while merging 😃 Thanks for the fix!


Go module file cannot create (yeah, again)

Cannot create go module (go.mod) file.

Fixecd in b9c60ae.


support olmo

https://github.com/ggerganov/llama.cpp/pull/6741
Now
This is now support in llama.cpp can you new support into ollama thanks
Build with truly open dataset and fully open-source model can this be supported in olllama thanks.
https://allenai.org/olmo
https://huggingface.co/allenai/OLMo-7B

Closing for https://github.com/ollama/ollama/issues/2337


Post submit job for Athens

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm


Updating documentation for async requests

I took me many hours to realize I could use the settle function instead of unwrap if I wanted to get the responses regardless of their status.

Sounds like a good thing to add. Thanks.


Update proto file to support higher precision

The latest proto file for geobuf uses sint64 for coordinates, but pygeobuf uses sint32. This means that if you have a feature encoded with precision higher than 6 (which admittedly the reference encoder will refuse to do, but nowhere does it say it's not allowed), the coordinates will be read incorrectly on deserialization. I'm using higher precision coordinates as intermediary storage for our seamless census data extraction tool. Six decimal places on geographic coordinates is about 10 cm at the equator, which is not high enough resolution for some applications.

@mattwigway thanks for getting me to update this with respect to the master project.


Added null checks when dependency is not found

Contains
Fixes #3464. Game no longer crashes when viewing Module details with missing dependencies.
How to test

Repeat the steps given in #3464 to reproduce the issue
Go to a details page of the module with missing dependency. (eg. Gooey defense with Flexible pathfinding not installed)

Can one of the admins please verify this patch?

Looks fine to me, triggering bot:
@GooeyHub: add to whitelist
Did you want to add in the tweak to make some text red in the case of a missing dependency or nah maybe later? Let me know 👍

Hooray Jenkins reported success with all tests good!

Hooray Jenkins reported success with all tests good!

Tests out and I see red text! Thanks :-)
Merging and adding you to the game credits 👍


Waiting for CertificateRequest using Vault Issuer

Describe the bug:
I created Certificate with Vault Issuer and found that certificate status with Status: Waiting for CertificateRequest "XXX" to complete.
Expected behaviour:
Certiciate should be automatically issued by Hashi Vault.
Steps to reproduce the bug:

Create Issuer

apiVersion: cert-manager.io/v1alpha2
kind: Issuer
metadata:
  name: gohub-devopscockroachdb-vaultcert-issuer
spec:
  vault:
    server: https://<vault cluster service>:8200
    path: pki-int/sign/vaultcert-devopscockroachdb-signer
    caBundle:  <base64 caBundle string>
    auth:
      kubernetes:
        mountPath: /v1/auth/kubernetes
        role: vaultcert-issuer
        secretRef:
          name: default-token-55h2t
          key: token

Create certificate

apiVersion: cert-manager.io/v1alpha2
kind: Certificate
metadata:
  name: gohub-devopscockroachdb-cluster-cert
spec:
  secretName: gohub-devopscockroachdbclustercert-secret
  duration: 2160h # 90d
  renewBefore: 360h # 15d
  organization:
  - XXX
  commonName: XXX
  isCA: false
  keySize: 2048
  keyAlgorithm: rsa
  keyEncoding: pkcs1
  usages:
    - digital signature
    - key encipherment
    - server auth
    - client auth
  # At least one of a DNS Name, URI, or IP address is required.
  dnsNames:
  - cluster.local
  uriSANs:
  - spiffe://cluster.local/ns/<namespace>/sa/default
  ipAddresses:
  - <IP_ADDRESS>
  # Issuer references are always required.
  issuerRef:
    name: gohub-devopscockroachdb-vaultcert-issuer
    # We can reference ClusterIssuers by changing the kind here.
    # The default value is Issuer (i.e. a locally namespaced Issuer)
    kind: Issuer
    # This is optional since cert-manager will default to this value however
    # if you are using an external issuer, change this to that issuer group.
    group: cert-manager.io

Anything else we need to know?:
Tried to run "vault write pki-int/issue/vaultcert-devopscockroachdb-signer common_name=XXXX".  Everything works fine.  I can obtain ca_chain, certificate, expiration, issuing_ca, private_key, private_key_type, and serial_number.
Issuer status
Status:
Conditions:
Last Transition Time:  2020-07-05T15:33:39Z
Message:               Vault verified
Reason:                VaultVerified
Status:                True
Type:                  Ready
Environment details::

Kubernetes version (e.g. v1.10.2): 1.17.0
Cloud-provider/provisioner (e.g. GKE, kops AWS, etc):
cert-manager version (e.g. v0.4.0): quay.io/jetstack/cert-manager-controller:v0.15.0
Install method (e.g. helm or static manifests): helm

/kind bug

Can you get us the output of kubectl describe certificaterequest?
/triage support

@meyskens I cannot find CSR so struggling how to check details

Have you looked at https://cert-manager.io/docs/faq/troubleshooting/ ?


Activating Open Collective

Hi, I'm making updates for Open Collective. Either you or another core contributor signed this repository up for Open Collective. This pull request adds financial contributors from your Open Collective https://opencollective.com/react-simple-animate ❤
What it does:

adds a badge to show the latest number of financial contributors
adds a banner displaying contributors to the project on GitHub
adds a banner displaying all individuals contributing financially on Open Collective
adds a section displaying all organizations contributing financially on Open Collective, with their logo and a link to their website

P.S: As with any pull request, feel free to comment or suggest changes.
Thank you for your great contribution to the Open Source community. You are awesome! 🙌
And welcome to the Open Collective community! 😊
Come chat with us in the #opensource channel on https://slack.opencollective.com - great place to ask questions and share best practices with other Open Source sustainers!

Thanks @monkeywithacupcake for your contribution!


Error on model/base does not to work with ember-data

Since ember-data seems to expect source/pointer to be "data/attributes/base" for errors on the model which aren't specific to a model attribute (https://github.com/emberjs/data/blob/v3.5.0/addon/-private/adapters/errors.js#L446) and https://github.com/jsonapi-suite/jsonapi_errorable/pull/13/files#diff-464e7d878a98e6a985d3f83118db6c98R97 started setting source/pointer to nil. The error on returned from the api can no longer be found on the ember-data model. Why was this change made? Can it be undone or made an option?

@richmolj any comments about this one ?

I'm up for rendering a source/pointer in this case specifically to support ember-data; I'd merge a PR.
That said, seems more like ember-data issue than anything else. It seems ember-data doesn't support the concept of validation errors that are not on an attribute - if we did data/attributes/base, we're saying "there is an attribute called base that has an error", which is not actually the case.
So I'd merge a fix to accommodate real-life, but note that fix would be an annoying hack.


Create index.html

This is a basic tic-tac-toe web app.
Tic-tac-toe is a two-player game where each player takes turns marking a 3x3 grid with their symbol, usually X or O. The goal is to get three of your symbols in a row, either horizontally, vertically, or diagonally, before your opponent does.
Contributing
If you want to add a project to this list, please make sure that:

[x] You read the contributing guide
[x] The repository has hacktoberfest as topic and counts for hacktoberfest event
[x] The project can't be just an "add your name" or simply + 1 contribution to hacktoberfest
[x] Place them in alphabetical order
[x] One repository per PR/contribution - avoid conflicts and simplify review
[x] Your pull request is not spammy just adding an empty line, otherwise it will be marked as invalid and not count to hacktoberfest.

If they meet the requirements above, feel free to create a PR. Happy Hacking! :sparkles:

That's spam, read our contributing guide.


feature: Easy release testing for KS on OCP

Configure an OCP environment for KCP (hub + 2 WECs)
Script(s) based procedure for release testing

Download KS release sources to get the testing scripts
Download all release artifacts (KS, OTP, etc..)
Install KS environment (KS components, WECs, agents , etc.._)
Run the KS e2e tests (deployment t multiple clusters + ginkgo)

Goal:  Have a very simple procedure, preferably using 1-2 scripts that automatically will perform the needed configuration and launch the tests.

Thanks Braulio for delivering #2046.  As discussed, this issue will also contain the method of access to the OCP cluster.

A simple procedure to automatically run our e2e tests in a OCP env has be implemented in this PR: https://github.com/kubestellar/kubestellar/pull/2046


AMQ-7376 - Use correct type for collections retrieval

It seems that this change is causing issue at least in Spring support. I'm investigating.


Question: how to pronounce evcxr?

Honestly, I've been struggling, and now I'm curious ;-)

I pronounce it eee-vic-ser. The name perhaps wasn't an ideal choice. I wanted something that was unique enough that you could do a Google search for things related to it - but pronunciation definitely isn't a strength of the name.

Thanks!


If a database does not have is_deleted field library crashes

Also expose type definitions

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 83.33333% with 9 lines in your changes missing coverage. Please review.

Project coverage is 58.73%. Comparing base (0e48542) to head (71712cb).
Report is 1 commits behind head on main.

Files with missing lines
Patch %
Lines

src/api.ts
0.00%
8 Missing :warning:

src/index.ts
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main       #6      +/-   ##
==========================================
+ Coverage   58.46%   58.73%   +0.27%
==========================================
  Files          15       15
  Lines         520      538      +18
  Branches       76       77       +1
==========================================
+ Hits          304      316      +12
- Misses        210      216       +6
  Partials        6        6

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


Sporadic reproducible GetListing, Download and other failures

This has been reported quite a few times.
What does the failure look like?
Typically, it manifests as an IOException. Depending on the API call being performed, this exception can cause

a GetListing result to be empty while the exeption is ignored
other commands to fail with an IOException.

If you look closely at the IOException, you might see:
an attempt was made to access a socket in a way forbidden by its access permissions
When does it happen?
It happens on an  control connection (only if encrypted) when you have issued many API calls (that execute commands and get the response).
Reported by (ignore the incorrect title):
@omanThYp https://github.com/robinrodricks/FluentFTP/issues/104#issuecomment-632437591
@oleksabor https://github.com/robinrodricks/FluentFTP/issues/104#issuecomment-953899294
#752 could such a case, but sadly there is no log
See also #723 : one of the "strange" ways this problem can show up.

Some first results of testing, using @oleksabor initial approach as a basis.
The goal was to find out a little bit more about the real problem and to remove conjecture.

I have modified the test program to only do the following (up to 500 times):

CWD /home/testuser
PWD

These commands do not use a data connection. No data connection (SSL) needs to be created and disposed. They only exercise the control connection.
These commands are iterated up to 500 times with no waits in between.
They always fail in the same way on the 474th iteration, on all of my available client systems.

The test suite will run all 500 iterations without failure if encryption is turned off.

The test suite encounters the problem or multiple problems if encryption is turned on.

Disabling stream buffering does not help.

Disabling or enabling socket polling does not have any effect on the problem occurrence(s).

.NET 6.0 or .NET Framework 4.8 targets both exhibit the same problem(s).

Any problems occur after the same amount of iterations - deterministic and not random. Independent of host system.

The errors occur in GetReply...ReadLine --> FtpSocketStream.ReadLine --> Read. I put a try/catch into FtpSocketStream.Read: The errors themselves are always, (note: also in the original Getlisting/Download szenario) "an attempt was made to access a socket in a way forbidden by its access permissions", an IOException, after which the socket is no longer connected, which is reacted to in different ways when they percolate upwards, depending on the function that you called. In a GetListing(), in a Download..., depending on the code that catches this exception, the further behaviour difffers. The control connection is closed though, which can cause a reconnect attempt, thus causing confusion if you don`t see that happening, or you can get "empty directories". Standardizing this behaviour could be a todo-item.

It looks like continuous reading from the SSL control connection stream in a huge amount of single byte READ operations is somehow exhausting some resource inside the implementation of SslStream.

I then wrote, in #104

@oleksabor Using your exact github code and connecting to a very high performace proftpd server of my own, I can reproduce the issue.
I am getting the same errors ( your sln is using FluentFTP V35).
After upgrading to FluentFTP V42 and making the few neccessary ->V40 migration changes, the problem STILL can be reproduced.
So now we can start to search for the problem.

Some first results of testing, using @oleksabor initial approach as a basis.
The goal was to find out a little bit more about the real problem and to remove conjecture.

I have modified the test program to only do the following (up to 500 times):

CWD /home/testuser
PWD

These commands do not use a data connection. No data connection (SSL) needs to be created and disposed. They only exercise the control connection.
These commands are iterated up to 500 times with no waits in between.
They always fail in the same way on the 474th iteration, on all of my available client systems.

The test suite will run all 500 iterations without failure if encryption is turned off.

The test suite encounters the problem or multiple problems if encryption is turned on.

Disabling stream buffering does not help.

Disabling or enabling socket polling does not have any effect on the problem occurrence(s).

.NET 6.0 or .NET Framework 4.8 targets both exhibit the same problem(s).

Any problems occur after the same amount of iterations - deterministic and not random. Independent of host system.

The errors occur in GetReply...ReadLine --> FtpSocketStream.ReadLine --> Read. I put a try/catch into FtpSocketStream.Read: The errors themselves are always, (note: also in the original Getlisting/Download szenario) "an attempt was made to access a socket in a way forbidden by its access permissions", an IOException, after which the socket is no longer connected, which is reacted to in different ways when they percolate upwards, depending on the function that you called. In a GetListing(), in a Download..., depending on the code that catches this exception, the further behaviour difffers. The control connection is closed though, which can cause a reconnect attempt, thus causing confusion if you don`t see that happening, or you can get "empty directories". Standardizing this behaviour could be a todo-item.

It looks like continuous reading from the SSL control connection stream in a huge amount of single byte READ operations is somehow exhausting some resource inside the implementation of SslStream.

I have further reduced the tests to
Command:  NOOP
Status:   Waiting for response to: NOOP
Response: 200 NOOP command successful

I can do 1057 of these commands and then I get the above described failure.
Choosing a "longer" command (i.e. more bytes) does not change the number of commands before the exception occurs.
So I my environment I can cycle about 1057 commands/responses and then I get an IOException.

Conversely, if I do
Command:  PASV
Response: 227 Entering Passive Mode (192,168,1,109,132,201).
Command:  MLSD /home/mike
Response: 150 Opening BINARY mode data connection for MLSD
....listing deleted....
Response: 226 Transfer complete

Guess how many? 289.
Looks like we must count the response lines, not the commands.

Made a small change to only honor SslSessionLength if the FTP connection is using FTPS (IsEncrypted).

This is now released as V42.1.0


fix(schema): make AND/OR fields non-nullable

This change makes filter field lists and and or non-nullable
and: [CommentFilter!]
or: [CommentFilter!]

Implements https://github.com/graphqlcrud/spec/pull/26

Merging to get this into release.


GitHub discussions

Could github discussions be enabled for this repository? https://github.com/features/discussions
It would probably help let the community help each other more easily and have more in-depth conversations about Redisson.

Thanks for the good idea. Done


Remove import intel_extension_for_pytorch from benchmarks

CI run: https://github.com/intel/intel-xpu-backend-for-triton/actions/runs/10742594240

Please take a look to #2106.

Please take a look to #2106.

I just wanted to see the results without most of the changes from #2106.


(Status: error) for site behind Authelia

Does the site redirecting for authentication keep jump from being able to pick up that the site is up?  I feel like 2XX and 3XX should be considered up, 4XX and 5XX considered down.  (Or maybe have the ability to specify which status codes are considered up?)

Looks like this is because the HEAD method is returning a 405 Method Not Allowed.

Yep essentially 4xx or 5xx HTTP response codes are considered down, as per the underlying guzzle library. When I am able I do plan on adding some more options to the status checking feature, maybe an alternate URL or as you suggest a list of acceptable responses.
Thanks for reaching out, keep me posted on the response from authelia 😀

@daledavies Seems like the easiest approach (for here anyway) would be a way to override the request type per site.  So, something like
        {
            "name": "Recipes",
            "url": "https://recipes.example.com",
            "description": "Recipes and meal planning",
            "icon": "tandoor.svg",
            "verb": "GET"
        }

@daledavies Don't suppose you want to add to the discussion?

Based on the discussion, it sounds like maybe the best thing to do is to allow the list of acceptable responses while also allowing a specification of if redirects should be followed?  From my viewpoint, if the site is returning a 303 See Other, it's up for my use case.

Yes this feature was only intended to be a simple status check, I'm not going to implement authentication and passing a request body etc.
I'm happy to implement additional request methods and a list of acceptable response codes if I can though.
One other thing though, I had set the gizzle client options to allow redirects, so this shouldn't be a problem.

Aside from this, would an alternate status URL help too? I think it might be beneficial for some cases.

@daledavies I do think that would help - being able to point to one place for the link and another for the status could let me try to set up a health check endpoint that's not protected by authentication.

I'll see about implementing all the above then :)

This will probably help with https://github.com/daledavies/jump/issues/53

I've added a change to allow for per-site status options as discussed above. I'll push a new release of Jump soon but just want to look at a few other issues first.

@daledavies Trying to test this - I added "request_method": "GET" to the sites.json config for this site, but I'm still getting an error.  Are there logs that I can check to see what's happening?  If I curl directly with GET, I do get a 200 OK back, so not sure what's going on.

There aren't any verbose logs specific to the status checking, you'll get a mixture of nginx and php logs via docker logs. I can make it give us more logs though, I'll hack something into a test image tomorrow if I can to give us an idea of the response jump is getting.
Other than that remember docker has its own internal network so the true test would be to exec into the jump container and curl from there, if you haven't already.

Relevant bits:
/var/www/html # curl -v "https://recipes.example.com/invite/[redacted]"

< HTTP/1.1 302 Found
302 Found

/var/www/html # curl -v "https://login.example.com/?rd=https%3A%2F%2Frecipes
.example.com%2Finvite%2F[redacted]&rm=GET"

< HTTP/1.1 200 OK

All my testing suggests that Jump correctly sends a GET request and also follows redirects, the status returned is from the final destination. I think though that by default guzzle will only follow 5 redirects so that could possibly be your problem.
Could you test with curl like before, but also paste the location header rather than the response body?

It might also help if I set guzzle to add the referrer when redirecting, by default it does not and this works for everything I've tested with, but maybe authelia needs it.

While testing with curl you could also tell it to follow redirects and limit the number to 5, will make it similar to what guzzle is joing in Jump...
curl -vL --max-redirs 5 "https://recipes.example.com/invite/[redacted]"

I've pushed an image to Docker Hub you can test with, it shold give some more information in docker logs. Specifically the eventual status code, the redirect history and the status code at each redirect.
Could you pull daledavies/jump:redirecttest and give it a spin? :)

That's working!
Still don't know why the app is seeing just a straight 401 instead of the 302, but I'm happy.  Thank you!

Interesting, glad it's working for you. Out of interest can you share your full sites.json file? That first error is unrelated to this problem but I'm intrigued what caused it.

{
  "sites": [
    {
      "name": "Home",
      "url" : "https://welcometo.example.com",
      "description": "You are here",
      "icon": "jump.png"
    },
    {
       "name": "Media",
       "url" : "https://media.example.com",
       "description": "Watch media",
       "icon": "jellyfin.png"
    },
    {
       "name": "Requests",
       "url" : "https://requests.media.example.com",
       "description": "Request series and movies",
       "icon": "jellyseerr.svg"
    },
    {
       "name": "Recipes",
       "url": "https://recipes.example.com/invite/[redacted]",
       "description": "Recipes and meal planning",
       "icon": "tandoor.svg",
       "status": {
         "allowed_status_codes": [401]
        }
    },
    {
       "name": "Restaurants",
       "url" : "https://wiki.example.com/example/restaurants",
       "description": "Example  restaurant ratings",
       "icon": "wikijs.svg"
    },
    {
       "name": "Reset Password",
       "url" : "https://login.example.com/reset-password/step1",
       "description": "Reset your password",
       "icon": "authelia.jpg"
    }
  ]
}

So the app is seeing a 401 instead of the 302. Trying with "allowed_status_codes": [401]" instead.

Perhaps a 401 might be correct, in terms of the request being unauthorized.
Also some differences between the curl and what Jump is doing, Curl wil be using the GET method where your configuration for Jump means it will use the default HEAD method for the request.
It looks like Authelia have implemented something to handle HEAD requests, but maybe they might respond differently depending on the request method.

If I do it with a HEAD request, I get:
HTTP/1.1 303 See Other
HTTP/1.1 405 Method Not Allowed

So still don't really know where the 401 comes from.

NOTICE: PHP message: Site (https://recipes.example.com/invite/[redacted]) returned status of... 401
2023/03/07 16:26:00 [error] 30#30: *17 FastCGI sent in stderr: "PHP message: Site (https://recipes.example.com/invite/[redacted]) returned status of... 401" while reading response header from upstream, client: <IP_ADDRESS>, server: _, request: "GET /api/status/94b68d17fb7a292d5c0f130303a0fd16fe363ef78f0e3ae1ef1456bf827d418e/ HTTP/1.1", upstream: "fastcgi://unix:/run/php-fpm.sock:", host: "welcometo.lab.example.com", referrer: "https://welcometo.example.com/"

If you we're not seeing anything in Jump's logs referring to redirect  history or redirect status history then this suggests Authelia isn't responding with a redirect status at all, it's just straight up responding with a 401 Unauthorized code.
I'm trying to think why this might be. I've done some testing with guzzle in Jump and can see there are two differences in the request headers sent by Jump are that guzzle doesn't set the Accept: */* header like curl and it uses a user agent of "GuzzleHttp/7" compared to curl's curl/7.81.0.
Anyway I can't help thinking that we might gain some insight from Authelia's own logs, can you see anything relevant in those when you do the curl vs Jump test?

@cinderblockgames Did you find anything in the Authelia logs?

I haven't had a chance, but I'll try to look this week.


Implement jörmungandr txId

Issue Number
#219
Overview

[x] I have implemented txId = blake2b256 . putTokenTransfer
[x] A golden test
[x] Auxiliary: I have renamed putTransaction to putSignedTransaction

Comments

I have not verified that the golden matches jcli

@rvl thanks, good point 😅  I should have a look at that. I suspect all the uses of fromIntegral in the module are potentially very dangerous and that it in this case would overflow.


sync: Update 0.8 kube-mixin dependencies and generate

Sync upstream dependencies via jb update. The driver behind this sync is https://bugzilla.redhat.com/show_bug.cgi?id=1978208 where dashboards fail to show pod name and instead show {{pod}}. The fix was back ported in https://github.com/kubernetes-monitoring/kubernetes-mixin/pull/618

I'd prefer if we only update the dependency that contains the fix your need to backport, which I presume is kubernetes-mixins. Also, would you mind detailing in the description of this PR, what is the fix you are trying to backport?

/hold

Pods name seems to be showing correctly after this change

/unhold


Api sauce doesn't get full list of HTTP header fields

Api sauce doesn't get full list of HTTP header fields.
You can check the list here.
For now, I only get 4 fields:
cache-control:"no-cache, no-store, max-age=0, must-revalidate"
content-type:"application/json;charset=UTF-8"
expires:"0"
pragma:"no-cache"

Do I miss any configuration to see full of list?

You should get what the server sends you. Are you experiencing a situation where the server is sending you more when you use curl or postman?

I checked from swagger for header's response & this is the result:
{
  "pragma": "no-cache",
  "date": "Sat, 24 Jun 2017 16:05:12 GMT",
  "x-content-type-options": "nosniff",
  "x-frame-options": "DENY",
  "access-control-allow-methods": "POST, GET, OPTIONS, DELETE, PUT, PATCH",
  "content-type": "application/json;charset=UTF-8",
  "access-control-max-age": "3600",
  "cache-control": "no-cache, no-store, max-age=0, must-revalidate",
  "transfer-encoding": "chunked",
  "access-control-allow-credentials": "true",
  "access-control-allow-headers": "Content-Type, Accept, X-Requested-With, Authorization",
  "x-xss-protection": "1; mode=block",
  "x-total-count": "25",
  "expires": "0"
}

But apisauce only returns to me only 4 fields cache-control, content-type, expires, pragma.
Have you faced this issue yet?

I haven’t see this issue, no.  Are you getting the right data back in your API? Are you using react-native? Android?

I only use pure React.
export const API = create({
  baseURL: 'http://localhost:8080'
});

const response = yield call(() => API.post(
      '/api/v1/users',
      {
        user: action.user,
        ...new FormData('profile', action.profile)
      },
      {
        headers: {
          Authorization: token
        }
      }
    ));

When that response comes back, I know the headers aren’t all there, but does the right data appear? Looks like you might be creating a new user in your example.  Does the server create it ok? Does it send back data you can see ok?

Another thing to check is the response.config object.  This contains the request that axios sent. Do all the outbound headers look right to you?

Yup. New user is creating successfully. But I can't full of response headers.

Does this only happen with that end-point?  Or do you see different headers for a GET to a use 9for example)?
Does that end-point redirect after posting?  Or is it a straight-up 200?
You should be able to verify this in your chrome debugger on the network tab.
Thanks for bearing with me.  This is a scooby doo mystery.

This happens to all my endpoints.
It is a straight up 200.
I did verify on chrome debugger & see full of headers list.
But get by apisauce only return 4 above fields.

Ok, this sounds like a CORS concern.
Are you able to add the headers you would like to read in your list "access-control-allow-headers": "Content-Type, Accept, X-Requested-With, Authorization"?
CORS is a security thing.
More info https://stackoverflow.com/questions/37897523/axios-get-access-to-response-header-fields
Could this be it?

It worked. Thanks a bunch @skellock.

Sweet!


Feature: accessible_by with includes vs joins (ActiveRecord 4+)

Take for instance :
Project belongs_to :team
Team has_many :teams_users

# and in ability.rb
can :read, Project, team: { teams_users: {user_id: @user.id}}

projects = Project.accessible_by(current_ability)

In this query, Cancancan will load all the teams associated with the user (and all the TeamsUser objects) [see: https://github.com/CanCanCommunity/cancancan/blob/develop/lib/cancan/model_adapters/active_record_4_adapter.rb#L17].
The user may belong to hundreds of teams, the team object could be big... This could create a huge memory footprint for no real reason.
Sometimes we do not want to load all the associated objects, we could do so by using joins instead of includes+references.
What is your opinion on this ? Is there any other cancancaner interested in such feature ?

@arambert I'm not sure this is still an issue or not for you. It is to the best interest of the community to use includes versus joins here. There may be room for improvement on CanCan's side here, as a stopgap you can define your ability with a block, and specify your condition yourself:
https://github.com/CanCanCommunity/cancancan/wiki/Defining-Abilities-with-Blocks

This is not an issue for me anymore. Like you're suggesting, I have set my abilities with blocks and defined «Policy» classes (à la Pundit) to be used in ability blocks and handle optimized accessible_by methods.

@arambert We will be moving to joins, apologies. I'm glad you have a workaround. There are a few other issues and PR's about this, I'll close this one in favor of those. See https://github.com/CanCanCommunity/cancancan/pull/171