text:
update entity interfaces

Update the Entity interfaces to support new features

Add sortable option to the entity class attribute schema. Here is an example entity class's attributes' schema which has 4 attributes but only serialNumber and modelNumber are sortable.
{
    "entityClass": "robot_ruber_3000",
    "displaySettings": {
        "name": "Ruber 3000",
        "description": "Delivery robot Ruber model 3000",
    },
    "metricsDefinitions": [
        ...
    ],
    "attributeSchema": [
        {
            "key": "serialNumber",
            "type": "string",
            "required": true,
            "sortable": true,
            "label": "Serial Number",
            "description": "Robot serial number"
        },
        {
            "key": "modelNumber",
            "type": "string",
            "required": false,
            "sortable": true,
            "label": "Model Number",
            "description": "The robot's model number"
        },
        {
            "key": "gps_lat",
            "type": "number",
            "required": false,
            "label": "GPS Latitude",
            "description": "Latitude value of the site GPS location"
        },
        {
            "key": "gps_lng",
            "type": "number",
            "required": false,
            "label": "GPS Longitude",
            "description": "Longitude value of the site GPS location"
        }
    ],
}

Add summary attribute to Entity instance interface. All entity instances can now have an optional attribute call summary which is a map of entityClass => entityInstancesCount. Here is an example list of Line entity instances that has summary data
[
  {
      "entityId": "line-1",
      "projectId": 1367,
      "homeId": 2067,
      "parentId": "region_1",
      "entityClass": "line",
      "displaySettings": {
          "name": "...",
          "description": "..."
      },
      "summary": {
          "nozzle": 123,
          "head": 23,
          "machine": 4
      }
  },
  {
      "entityId": "line-2",
      "projectId": 1367,
      "homeId": 2067,
      "parentId": "region_1",
      "entityClass": "line",
      "displaySettings": {
          "name": "...",
          "description": "..."
      },
      "summary": {
          "head": 2,
          "machine": 343
      }
  },
  {
      "entityId": "line-3",
      "projectId": 1367,
      "homeId": 2067,
      "parentId": "region_1",
      "entityClass": "line",
      "displaySettings": {
          "name": "...",
          "description": "..."
      },
      "summary": {
          "machine": 12
      }
  },
  {
      "entityId": "line-4",
      "projectId": 1367,
      "homeId": 2067,
      "parentId": "region_1",
      "entityClass": "line",
      "displaySettings": {
          "name": "...",
          "description": "..."
      },
      "summary": {
          "nozzle": 13,
          "machine": 434
      }
  }
]

Add sortBy param to the GET entities filters. So now when fetching entities, the front end can pass a sortBy param to the back end to have the back end sort the result by the specified param. For example this will ask the back end to return all entities and sort them by attribute name serial_number in desc order

https://dev.tinkermode.dev:7002/projects/1367/entities?limit=100&sortBy=serial_number:desc

Add recursive param to the GET entities filters. So now when we call to fetch descendants of an entity instance, not just children. For example, this will call the back end to return all entities of class ruber_3000 that are descendants of the customer with id customer_1' AND sort the results by serial_numerindesc` order

https://dev.tinkermode.dev:7002/projects/1367/entities?limit=100&entityClasses=ruber_3000&parentId=customer_1&sortBy=serial_number:desc

@bananaumai, these are the changes to the react-common-public repo that I think we need for now. Included in the PR are some example data you asked for. Let me know if you need some more examples.

Are we expecting that the user / frontend will append attributes. to the query or that the backend will do it?

https://dev.tinkermode.dev:7002/projects/1367/entities?limit=100&entityClasses=ruber_3000&parentId=customer_1&sortBy=serial_number:desc

Are you talking about the orderBy option? Yes, the front end will append the attribute and sort order and pass it to the backend. For example, to fetch all robots of class ruber_3000 and sort them by their serial_number in descending order, the front end will pass these params to the back end
https://dev.tinkermode.dev:7002/projects/1367/entities?limit=100&entityClasses=ruber_3000&sortBy=serial_number:desc

https://dev.tinkermode.dev:7002/projects/1367/entities?limit=100&entityClasses=ruber_3000&sortBy=serial_number:desc

Ok, so the sortField component of sortBy will not include attributes. so I will need to prepend it in the backend.

https://dev.tinkermode.dev:7002/projects/1367/entities?limit=100&entityClasses=ruber_3000&sortBy=serial_number:desc

Ok, so the sortField component of sortBy will not include attributes. so I will need to prepend it in the backend.

Are you thinking of having the front end adding attributes to the param so that the back end knows whether this value serial_name is an attribute or just one of the entity's base attributes e.g. name, description, homeId, etc...?
Actually we need to discuss whether or not we allow sort by the base attribute like name, description, homeId, etc... If we do then maybe we need to add something to the param to let the backend knows. Because it is possible for someone to create an attribute schema with the name name which will have a conflict with the entity's name.

Are you thinking of having the front end adding attributes to the param so that the back end knows whether this value serial_name is an attribute or just one of the entity's base attributes e.g. name, description, homeId, etc...?

Actually we need to discuss whether or not we allow sort by the base attribute like name, description, homeId, etc... If we do > then maybe we need to add something to the param to let the backend knows. Because it is possible for someone to create an attribute schema with the name name which will have a conflict with the entity's name.

I think the frontend should add attributes. since it's conceivable that someone would want to sort by other fields not in attributes. This will give that option by default.

Are you thinking of having the front end adding attributes to the param so that the back end knows whether this value serial_name is an attribute or just one of the entity's base attributes e.g. name, description, homeId, etc...?

Actually we need to discuss whether or not we allow sort by the base attribute like name, description, homeId, etc... If we do > then maybe we need to add something to the param to let the backend knows. Because it is possible for someone to create an attribute schema with the name name which will have a conflict with the entity's name.

I think the frontend should add attributes. since it's conceivable that someone would want to sort by other fields not in attributes. This will give that option by default.

Yeah, only the front end knows if the user want to sort by base attribute name or custom attribute that happen to also be name. Sure, I will add attributes to the sortField if the user want to sort by custom attributes. If the sortField does not contain  attributes then back end can assume it is base attribute.
So what convention should we use?
Below are some example of sort by base attributes
sortBy=homeId:desc
sortBy=entityClass:asc
sortBy=parentId:desc
... and others
For custom attributes, maybe prepend attributes_ to the attribute name?
sortBy=attributes_serial_number:desc
sortBy=attributes_driver_id:asc
sortBy=attributes_address:desc
... and others
Prefixes options

attributes_
attributes:
attributes+

Let's decide on the prefix. We probably want to use special characters that can't be used in attribute name.

The easiest prefix option from backend perspective is attributes. e.g. sortBy=attributes.serial_number:desc the sortField can be passed directly to the mongo query. Unless there is some other consideration I am not aware of.

Yeah sure, attributes. works for me.

In another discussion with @bill-mode, we found that we may want to use summary fields as sort fields.
To make it consistent, we should use the summary. prefix when the specified field is a summary field, right.
e.g., summary.nozzle:desc means sort by the nozzle summary field in descendant order.

Let's use : as separators for all 3 fields. Because we are going to prepend sortFieldType to this string, the back end will need to split this string anyway. So using . between sortFieldType and sortFieldName and use : between sortFieldName and sortOrder will make it even harder to split the string for the back end right?
So let's use this template sortFieldType:sortFieldName:sortOrder
Examples:

basic:entityId:desc
basic:entityClass:desc
basic:homeId:asc
attributes:serial_number:desc
attributes:driver_id:asc
summary:feeder:desc
summary:driver:asc
summary:site:asc

BTW: Have we decided on the summary attribute name yet? Are we going with summary or descendantsSummary? If we are going to use descendantsSummary, should we use descendantsSummary as sortFieldType as well? For examples

descendantsSummary:feeder:desc
descendantsSummary:driver:asc
descendantsSummary:site:asc

For attributes there is no need to split the string around the . because attributes is a field on the document object, so a nested document inside attributes is accessed by attributes.<fieldname>. If summary is similarly going to be a top-level field with nested fields inside, then the . notation will be easiest. If there is a different structure then we need to re-think.

For attributes there is no need to split the string around the . because attributes is a top-level field on the document object, so a nested field inside attributes is accessed by attributes.<fieldname>. If summary is similarly going to be a top-level field with nested fields inside, then the . notation will be easiest. If there is a different structure then we need to re-think.

I think this will be a problem with basic attribute. Unless for basic attributes, we don't include sortFieldType. For example

entityId:desc
entityClass:desc
homeId:asc
attributes.serial_number:desc
attributes.driver_id:asc
summary:.eeder:desc
summary.driver:asc
summary.site:asc

I think this will be a problem with basic attribute. Unless for basic attributes, we don't include sortFieldType. For example

Yeah top-level fields would not need any prefix.

I think this will be a problem with basic attribute. Unless for basic attributes, we don't include sortFieldType. For example

Yeah top-level fields would not need any prefix.

Sure, I am ok with that convention too.
So, the template will be this

For top level fields ${sortFieldName}:${sortOrder}
Other fields ${sortFieldType}.${sortFieldName}:${sortOrder}

@bananaumai what do you think?

And do we have a decision on the summary field name?

@bananaumai, do you have any objection on this "orderBy" convention?
For top level fields ${sortFieldName}:${sortOrder}

entityClass:desc
homeId:asc

Other fields ${sortFieldType}.${sortFieldName}:${sortOrder}

attributes.serial_number:desc
attributes.driver_id:asc
descendantsSummaries.feeder:asc
descendantsSummaries.site:desc

@bill-mode I'm okay with it!

I think we've settled on this now?

Yes, I think we can go with this, NOTE: we will use descendantCounts instead of descendantsSummaries
For top level fields ${sortFieldName}:${sortOrder}

entityClass:desc
homeId:asc

Other fields ${sortFieldType}.${sortFieldName}:${sortOrder}

attributes.serial_number:desc
attributes.driver_id:asc
descendantCounts.feeder:asc
descendantCounts.site:desc

authors: bananaumai bill-mode jamesbalcombe83

repo: moderepo/react-common-public


text:
createStore返回的store，使用reduxStore的方法时，类型有丢失

RT

类型丢失具体指哪些类型呢？
Reduck 底层虽然是基于 Redux 实现，但是屏蔽了 Redux 的一些底层概念，如 Reducer。另外，Reduck 对于 model 是动态挂载的，而 Redux 创建 store 的时候，就会传入所有的 reducer。因为这些不同，直接使用 Redux 的一些底层 API，可能获取不到准确的类型提示。
例如：store.getState() 无法获取全局 state 的类型。（因为 Reduck 对于 model 是动态挂载的）
一般建议尽量直接通过 Reduck 的 API 来实现需求，这样可以获得良好的类型信息。

source: gharchive/issue

authors: Juliiii xuchaobei

repo: modern-js-dev/reduck

license: MIT

license_type: permissive

license_source: github-api


text:
ability to edit title for individual forms

This would be a way to title forms separate form the id_string that isn't tied to any back-end mechanics.

this is NOT the id_string
this should also involve showing the title in some places that now show the id_string

https://github.com/modilabs/formhub/pull/94

repo: modilabs/formhub


text:
Stuck at this warning for >20 min: UserWarning: Distributing <class 'dict'> object. This may take some time.

I am trying to use modin to speed up an image processing pipeline that uses pandas dataframes to store images in individual columns together with computed image properties in other columns. I am new to modin, and I was trying it as a drop-in replacement to pandas by changing the import statement to import modin.pandas as pd. However, when I run a function to compute a set of image properties which takes just a few minutes with standard pandas, modin gets stuck at the warning UserWarning: Distributing <class 'dict'> object. This may take some time. for at least 20 min (aborted manually).
I would like to try to narrow down this issue, but I don't know where to start looking and did not find anything on the issue tracker relating to this warning either. The function I am running is rather long, so not sure how helpful it would be to post it here, but it is essentially applying functions over the image columns either individually or together in permutations to compute properties of the images. I am already using joblib to parallelize, but for testing with modin I set the joblib loops to only use a single core.
I am sorry this is not more specific, is there anything that can be said about where to start looking for why I am getting stuck? Or is modin not a good fit for working with dataframes containing images?
I tried this with modin 0.7.3 installed from the conda-forge, and running with the dask backend. I tried installing ray and modin via pip, but could not get it to work (I could try more if you believe it would make a difference). I am on Arch Linux 5.6.15-arch1-1

Hi @joelostblom, thanks for the detailed question! I will explain some details about how Modin works first, then we can try to debug this performance.
When Modin takes in data, it partitions datasets in the way that makes them scalable. So when we get a dictionary object, we have to manually split the data to each partition and this can't (reliably) be done in parallel without making many copies because the data cannot be accessed by all of the Modin workers in parallel. There are still some tricks we can do here to make things marginally faster, but there is a limitation at the Python language level that will be hard to get around.
Ideally, we can ingest the data from a CSV file or some other format. Then all of the workers can access the shared filesystem and read in-parallel. This will be faster than having the data already in memory. Is it possible to read the data in from a file?
The joblib point is another challenge with Modin. If Modin only has 1 CPU it will basically be pandas + some communication overheads, so the more the better here. There are also known issues with Modin working with joblib (#672). I assume you were trying to manually parallelize a large job with pandas before, my recommendation here is to try Modin without joblib.
Your type of workload is a good fit for what we want to do with Modin, so let's see if we can help your case more. A lot of the workarounds people used with pandas to fix certain things are counter-productive in Modin.

Thanks for your reply @devin-petersohn !
Your explanation makes a lot of sense to me. I did not previously understand that modin's parallelization depends is best applied during the reading of data, I thought it was generally when constructing a pandas dataframe. I think this makes sense with the error because I am reading tens of GBs of images into a dictionary that I am then converting to a dataframe and I guess this is where modin/python chokes.
I might try your suggestion with writing these images to a single CSV (probably as flattened arrays then) that I read into modin. I am a bit afraid that the tripled IO (read imgs, write csv, read csv) will negate much of the later performance benefit in terms of overall execution time. Still, I think it is an attractive option to allocate most of the processing time to the initial IO in order to speed up later parts of the pipeline, so I will give this a go (but it might be a little while before I can rewrite that part of the pipeline).
Does this makes sense to you, or do you see any more immediate way of scaling up the image? I have meant to look into storing images in an HDF5 store for other reasons, would this also be a suitable format for reading a dataframe into modin or is CSV preferred?
Once I have this initial dataframe of images, what happens to performance if I construct a second dataframe from the first one (e.g. through a reshape, subset, etc). Would I face similar problems as now since this second dataframe is not created directly from a read operation?

@joelostblom how are you initially reading the images? We have some extensible parsers that would potentially allow us to directly read those in parallel at first. Are you doing something with the dictionary or is it simply needed to create a dataframe? What format are you reading from?
The triple IO can potentially be problematic, and it would depend on what you're doing later. Depending on what you're doing with the dictionary we may be able to avoid this altogether.
HDF5 support is not yet implemented in Modin. There are some limitations to the parent libraries we might depend on and haven't had the time to focus on writing a custom HDF5 engine. Anything we have implemented will work just fine, these can be found on the readme.
Constructing a new DataFrame from another will still be fast. The speed problem is coming from some structure that Modin doesn't control. Python dictionaries are more difficult to distribute because the Python executor that controls it must communicate it directly to other Python executors, so we are limited by how fast Python can loop over the data and send it. After all of this data is split up and distributed, Modin will run fast.

I use imread from scikit-image in a loop using joblib to paralellize over a list of all the file names to read in. The images are in tiff format, and I believe that scikit-image uses the tifffile library under the hood (these are microscopy images, so eventually I might switch to xarray instead of numpy since that seems to provide some conveniences , but this is more of a long term goal).
The only thing I am doing with the dictionary is storing some image metadata (short strings) that is extracted from the file names, but as long as I can store the file name and the image using the modin approach, I could extract this metadata as a separate step. I also downscale the images using scikit-learn right after reading them so that I don't need to store the full size image, but I imagine this would not be a problem to do with the approach you are suggesting (or possible as a separate step afterwards).
Let me know if you need more info or some sample code if it is not clear from the above. Excited to learn how I can speed this up using modin!

I should also say that the image processing I am doing relies on scikit-image and numpy so I would need to eventually have the images in a format that is compatible with those libraries (the scikit-image imread function returns a numpy array).

@joelostblom This helps quite a bit. Some code samples might help here. How many image files are you processing and what does the structure of a row or column look like in the dataframe?
Modin doesn't have a numpy API yet, so this might be a challenge at the current time. We have some plans in the works for this, but (as you can imagine) it is a big undertaking so we're making sure the design is right. We can convert a Modin dataframe to a numpy array at the moment, but it will not be distributed (yet).
We are also building out the extensibility component of the API and custom parsers. This would be a good test of that. There's no good high level API for these at the moment, so it will take some collaboration until we introduce a high level API for custom parsers and functions.

Sorry for the delayed reply @devin-petersohn, I have had some thesis deadlines to tend to over the weekend so got lost in that.
It is unfortunate that there is no numpy API atm, then it sounds like modin might not be the tool I need for my image processing needs right now? In the meantime, I found https://github.com/nalepae/pandarallel which has been working great and fit well with my pipeline since it was mainly a few .apply call on the image columns that constituted the bottleneck for me currently. I believe modin would bring additional benefits when it starts working with numpy images, but for my current application I might stick with pandarallel since I already have a working solution for the performance issues I was experiencing.
In terms of your questions on the data, I am processing anything from 10 to 300-400 images, typically around 100. Then I process these with skimage to crop objects out of the images and measure the properties of these objects. So the initial dataframe has 1-4 big images per row (depending on how many channels we record in the microscope), but the final data frames with measurements has a single of the original images split out into multiple rows, one object per row. This would be the typical structure of the final data frame (truncated from around 20ish columns and hundreds of rows):

major_axis
aspect_ratio
perimeter
area
circularity
img1a
img1b

0
79.103
1.14776
323.492
4222
0.859097
2D np.array
2D np.array

1
89.6788
1.26829
524.653
4836
0.765625
2D np.array
2D np.array

2
78.4372
1.21918
352.599
3909
0.808969
2D np.array
2D np.array

I don't see a particular actionable task in this issue, so I'm going to close it. @joelostblom I hope you are using Modin. Please comment here or in a new issue if you would like help.

authors: devin-petersohn joelostblom mvashishtha

repo: modin-project/modin


text:
slice_shift doesn`t work correctly at MODIN_STORAGE_FORMAT=omnisci

When I run at MODIN_STORAGE_FORMAT=omnisci:
import pandas
import modin
import modin.pandas as pd
from modin.utils import to_pandas
from modin.pandas.test.utils import test_data_values
data = test_data_values[0]
modin_series = pd.Series(data)
data_column_length = len(data[next(iter(data))])
modin_series.index = np.arange(2, data_column_length + 2)
modin_result = modin_series.slice_shift(periods=1000000000)
hasattr(modin_result, 'index')

I have error:
KeyError: 'Column F___reduced__ does not exist in schema'

@modin-project/modin-omnisci  could someone please check if this still happens?

I'm unable to reproduce this issue. Closing as not reproducible.

authors: AndreyPavlenko Rubtsowa vnlitvinov


text:
PERF-#5549: copy dtypes for __invert__ op

Signed-off-by: Anatoly Myachev anatoly.myachev@intel.com

What do these changes do?

[x] first commit message and PR title follow format outlined here

NOTE:  If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

[x] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] signed commit with git commit -s
[x] Resolves #5549
[x] tests added and passing
[x] module layout described at docs/development/architecture.rst is up-to-date

@dchigarev let's merge

source: gharchive/pull-request


text:
FEAT-#1611: Add some datetime extraction functions for HDK

What do these changes do?

Continuation of work done in https://github.com/modin-project/modin/pull/2750. Still not all functions are implemented in the HDK.

[x] first commit message and PR title follow format outlined here

NOTE:  If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

[x] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] signed commit with git commit -s
[x] Resolves #1611
[x] tests added and passing
[x] module layout described at docs/development/architecture.rst is up-to-date

@AndreyPavlenko please take a look


text:
Make more friendly for use with autolayout

Perhaps MDCSwipeToChooseView could have an init for just initWithOptions or expose options property

This will really help!

authors: altyus yisheng

repo: modocache/MDCSwipeToChoose

license: mit

license_source: bigquery


text:
Warning on console - shared strategy

Describe the bug
Using "next": "14.2.10" with "@module-federation/nextjs-mf": "8.6.2" and "webpack": "5.94.0" is getting this warning on console:

next.config.js
const { NextFederationPlugin } = require('@module-federation/nextjs-mf')

module.exports = {
  webpack(config, options) {
    config.plugins.push(
      new NextFederationPlugin({
        name: 'delivery',
        filename: 'static/chunks/remoteEntry.js',
        dts: false,
        exposes: {},
        remotes: {},
        shared: {},
        extraOptions: {
          exposePages: true,
        },
      })
    )

    return config
  },
}

▲ Next.js 14.2.10

Environments: .env.local

✓ Linting and checking validity of types
Creating an optimized production build ...
✓ Compiled successfully
Collecting page data  .[Module Federation Data Prefetch]: Your shared strategy is set to 'loaded-first', this is a necessary condition for data prefetch
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[Module Federation Data Prefetch]: Your shared strategy is set to 'loaded-first', this is a necessary condition for data prefetch
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[Module Federation Data Prefetch]: Your shared strategy is set to 'loaded-first', this is a necessary condition for data prefetch
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[Module Federation Data Prefetch]: Your shared strategy is set to 'loaded-first', this is a necessary condition for data prefetch
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[Module Federation Data Prefetch]: Your shared strategy is set to 'loaded-first', this is a necessary condition for data prefetch
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
✓ Collecting page data
Generating static pages (2/5)  [=   ][Module Federation Data Prefetch]: Your shared strategy is set to 'loaded-first', this is a necessary condition for data prefetch
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[Module Federation Data Prefetch]: Your shared strategy is set to 'loaded-first', this is a necessary condition for data prefetch
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
[ Federation Runtime ]: "shared.strategy is deprecated, please set in initOptions.shareStrategy instead!"
✓ Generating static pages (5/5)
✓ Collecting build traces
✓ Finalizing page optimization
Route (pages)                           Size     First Load JS
┌ ○ /                                   322 B          58.3 kB
├   /_app                               0 B              58 kB
├ ○ /404                                244 B          58.2 kB
├ ƒ /api/addresses/[zipCode]            0 B              58 kB
├ ƒ /api/carts/[cartId]                 0 B              58 kB
├ ƒ /api/checkout/carts/[cartId]        0 B              58 kB
├ ƒ /api/customers                      0 B              58 kB
├ ƒ /api/customers/addresses            0 B              58 kB
├ ƒ /api/date                           0 B              58 kB
├ ƒ /api/deliveries/quote               0 B              58 kB
├ ƒ /api/healthcheck/live               0 B              58 kB
├ ƒ /api/healthcheck/ready              0 B              58 kB
├ ƒ /api/last-commit                    0 B              58 kB
├ ƒ /api/orders                         0 B              58 kB
├ ƒ /api/orders/search                  0 B              58 kB
├ ○ /neighborhood-delivery              10.3 kB         600 kB
└ ○ /neighborhood-delivery-orders       5.51 kB         596 kB

First Load JS shared by all           62.9 kB
├ chunks/main-c0d52c21dff0ec6a.js     32.1 kB
└ chunks/webpack-2d075e27e48baec4.js  25.5 kB
└ other shared chunks (total)         5.27 kB

ƒ Middleware                            32.6 kB
○  (Static)   prerendered as static content
ƒ  (Dynamic)  server-rendered on demand
Reproduction

Used Package Manager
npm
System Info
System:
    OS: macOS 15.0
    CPU: (8) arm64 Apple M3
    Memory: 87.64 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
Binaries:
    Node: 18.17.0 - /usr/local/bin/node
    Yarn: 1.22.21 - ~/.nvm/versions/node/v16.20.2/bin/yarn
    npm: 9.6.7 - /usr/local/bin/npm
    bun: 1.1.18 - ~/.bun/bin/bun
Browsers:
    Safari: 18.0

Validations

[X] Read the docs.
[X] Read the common issues list.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Module federation issue and not a framework-specific issue.
[X] The provided reproduction is a minimal reproducible example of the bug.

Hey try to upgrade @module-federation/enhanced@0.6.10

repo: module-federation/core


text:
license file

Is this open source?

Yes it is but we need to to add a license file.

authors: mogwai srevay


text:
Number of lines in ErrorLabel?

Is there a possibility to have a multiline error message under text field?

im working on it @sevgjan
but changing form height will cause jumpy UI which will confuse users. should find a proper solution

thank you! @mohammadalijf

Hello, Do you have any update about this issue?

What about this issue?

authors: Annate20105 mohammadalijf sevgjan umairsuraj

repo: mohammadalijf/UnderLineTextField


text:
Add a Gitter chat badge to README.md

mohbasheer/angular-chips now has a Chat Room on Gitter
@mohbasheer has just created a chat room. You can visit it here: https://gitter.im/mohbasheer/angular-chips.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

I added badge so this is not required.

authors: gitter-badger mohbasheer

repo: mohbasheer/angular-chips


text:
"Add to Cart" button bug

There are two issues with the buttons:

Inconsistent button width: The "-" and "+" buttons have different widths, which makes the UI look uneven.
Button unresponsiveness: After increasing the value and then decreasing it beyond one resets the button to the "Add to Cart" text and the button becomes unresponsive after that.

I want to work on fixing this bug. Thanks!

You can start working on this i will assign, you when I start pc again,
Make sure you star ⭐ repo and follow on GitHub
On Sat, Oct 5, 2024, 12:35 AM Sanjana Biswas @.***>
wrote:

There are two issues with the buttons:

Inconsistent button width: The "-" and "+" buttons have different
widths, which makes the UI look uneven.
Button unresponsiveness: After increasing the value and then
decreasing it beyond one resets the button to the "Add to Cart" text and
the button becomes unresponsive after that.

I want to work on fixing this bug. Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/mohitahlawat2001/Loco-Musica/issues/39, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APQVYO26UR3AQUFBQH26PIDZZ3RGTAVCNFSM6AAAAABPMOBFQKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3DOMJRGU4TKNI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

not any progress


text:
Check the dictionary before cloning a habtm or has many through

deep_cloneable doesn't dup HABTM associated objects, only the associations themselves.
This patch introduces logic to check the dictionary for an existing clone.  This way if two classes joined by a HABTM (or has_many :through) are deep_cloned via a shared parent, they won't be unnecessarily duplicated.
I couldn't think of a situation in which you wouldn't want to check the dictionary, so I figured it would be best to make it the default behavior rather than passing in an option, but that's a possibility as well.
I have added a test to illustrate the use case.

Thanks, will look into it this week! Sorry for my late response, I was on holiday ;)

Great!
Yea, the call on like deep_cloneable.rb:148:
if(dict && object.find_in_dict_or_clone(dict, false))
Required it to be protected rather than private.

authors: cspeper moiristo


text:
Stylus watch got an issue of parsing

I installed stylus and jeet in my project folder.
When execute 'stylus -u jeet -w style.styl', got the below error.
ParseError: node_modules/jeet/stylus/jeet.js:2:10
   1| module.exports = function(opts) {
   2|   return function(style) {
---------------^
   3|     style.include(__dirname);
   4|   };
   5| };

expected "ident" or "string", got "return"

May I know what is the root cause and how to fix it?

I found all file name has changed and added 'index.styl' file in master.
That already fixed my issue, but not released yet.

repo: mojotech/jeet


text:
Fix http2 agent doesn't work with request module

Fix #174

This looks good, but it also needs fixed in getTLS

I have also applied the fix to requestRaw and getRaw because even if in current implementation the agent option of Agent.prototype.request does not seems to be handled in plain mode (is it?), it may change in the future.

I just checked that test are passing. We should normally add tests for this fix but I have not the time to do it now. I may do it next week

Thanks! This also continues to pass the Firefox integration tests, so it's good to go in my book.

authors: felicienfrancois nwgh


text:
Locale 'zh-HK' is missing

> moment.locale()
< "en" //OK
> moment.locale('zh-CN')
< "zh-cn" //OK
> moment.locale('zh-HK')
< "zh-cn" //expected "zh-HK"

This issue relates https://github.com/moment/moment/pull/2776, which hasn't been merged.

Thanks for the reminder.  We'll track it in #2776.

repo: moment/moment


text:
Publish typing as a separate package

Is your feature request related to a problem? Please describe.
moment JS size is a big
It's best to exclude it from JS bundle if not used
So in pikaday 1.8.0, moment is only included when installed
However since there is no separate typing package for moment (@types/moment is depreacted)
Many typing packages are including moment as dependency instead and this leads to issue of including moment in built JS bundle accidentally: https://github.com/DefinitelyTyped/DefinitelyTyped/issues/27942
Describe the solution you'd like
As mentioned by member of DefinitelyTyped:

We generally don't add packages that already have their own types, and I have a feeling we probably won't in this case unless there's been a drastic misunderstanding or exceptional behavior we haven't accounted for.

That means the best way to solve it is to have a separate typing only package (which doesn't include the huge moment JS code)
and managed by moment team (unless you want to defer the responsibility back to the community, fine for me though)
Describe alternatives you've considered
If moment team would like other contributors to manage the typing part
Here is an example:
https://github.com/DefinitelyTyped/DefinitelyTyped/pull/36252
It might be quicker to release fixes/changes this way (based on my past experience with DefinitelyTyped
Additional context
(none)

Would be good to hear some response so we can discuss about next steps

I would be ok moving the types to a community-maintained place.

Someone can publish the typings elsewhere, so you don't need to include moment when you just need its types.

authors: PikachuEXE marwahaha


text:
Bug with parsingFlags().parsedDateParts

http://jsfiddle.net/qmuk7er0/
Month param is February => return part is January

Oh. Months in js starts with 0. OMG. Close


text:
[Nuxt3] moment.locale not set new locale

Describe the bug
moment.locale not set new locale, instead of this it always return 'en'
UPD: It seems in ssr mode it works fine, but on client is not
To Reproduce
https://stackblitz.com/edit/nuxt-starter-fy3grx?file=app.vue

Have the same issue. Any solutions?

For those that are experiencing the SyntaxError: Unexpected token 'export', make sure to add the file extension at the end of import.
In my case was
import 'moment/dist/locale/es.js';
moment.locale('es');

If you still have the same error, go to node_modules/moment/dist/locale and check the extensio is mjs or js

The following helped when using Nuxt 3:
`import moment from 'moment'
import 'moment/dist/locale/ru.js'
moment.updateLocale('ru', null)`

authors: Gamblt ideafm jorge-vnarvaez rivz-a


text:
Removed verbal numbers from Finnish translation

I am still very confused why is the Finnish translation showing verbal numbers instead of the actual number. All of the other languages I looked at are using real numbers so after this change, the translation would be more consistent. As a native speaker, I couldn't think of any reason why in particular there should be an exception for the Finnish language.

I appreciate the contribution. The wrong file is modified here - it should be the file under src/locale - what this is is the built file. Once you make that modification, we can give a shout to the original locale author and hear out his/her reasoning. This seems right to me too though.

@maggiepint Sorry, it took so long for me to come back. It has been a quite hectic spring :) I've now made the changes to source files.

@lauriii you also need to update the tests src/test/locale/fi.js because they're failing now.

@lauriii - Thanks for your contribution. Sorry this is taking so long to merge!
We need you to update the tests for the Finnish language translation.
@bleadof - could you confirm this change?

It's stylistically common to write the smaller numbers especially under ten with words especially since the inflection of the number changes depending whether we're expressing time before or after specified time. (http://jkorpela.fi/kielenopas/4.11.html#lukujen-ilm)[Jukka Korpela's Nykykielen opas]. I thought quite a bit about it and thought it's better to keep this. If we would use the shortened version of the minute, like 1 min, then using numbers would be stylistically more correct.
Just as a side note, you can always create your own language pack that contains shortened versions of everything. I've done this to a web shop where we needed to conserve space. I think actually doing that would be a nicer way to contribute! So basically fi-short.
How does that sound?

authors: bleadof ichernev lauriii maggiepint marwahaha


text:
remove subclass: muscular disease classified as skeletal disease

cc @paolaroncaglia @zoependlington
This comes from EFO:
https://www.ebi.ac.uk/ols/ontologies/efo/terms?iri=http%3A%2F%2Fwww.ebi.ac.uk%2Fefo%2FEFO_0002970

@cmungall thanks for spotting this, we'll fix it in time for our release next week. I'll open a ticket in EFO now.

@cmungall should be fixed now and visible after April 15.

authors: cmungall paolaroncaglia

repo: monarch-initiative/mondo


text:
Marchiafava Bignami disease (MONDO:0016370) has incorrect xref and synonyms

Mondo term (ID and Label): MONDO:0016370 Marchiafava Bignami disease
Xref that should be fixed (ID and label): NCIT:C97045 "Metabolic Bone Disorder" -- no obvious relation between these two concepts.
Note that MONDO:0016370 also has synonyms "metabolic bone disease" and "metabolic bone disorder", so one of the other xrefs is probably incorrect as well.
Your nano-attribution (ORCID) 0000-0003-0587-0454
If you don't have an ORCID, you can sign up for one here
Other comments:
Tracking this in our repository at https://github.com/TranslatorSRI/Babel/issues/175

hi @gaurav!
thanks for the ticket, we will take a look at this as soon as possible.

authors: gaurav nicolevasilevsky


text:
[Merge] "non-atopic asthma" with "intrinsic asthma"?

I stumbled across this in #7685. The two classes have the same exact synonym after fixing the typos.
Mondo term (ID and Label)
[Term]
id: MONDO:0800112
name: non-atopic asthma
def: "A type of asthma that isn't related to an allergy trigger like pollen or dust, and is less common than atopic asthma." [PMID:23724224]
synonym: "intrinsic asthma" EXACT [https://orcid.org/0000-0002-7371-8158, https://orcid.org/0000-0003-0113-912X]
synonym: "non-allergic asthma" EXACT [https://orcid.org/0000-0002-7371-8158, https://orcid.org/0000-0003-0113-912X]
is_a: MONDO:0004979 {source="https://orcid.org/0000-0002-7371-8158", source="https://orcid.org/0000-0003-0113-912X"} ! asthma
property_value: IAO:0000233 "https://github.com/monarch-initiative/mondo/issues/5261" xsd:anyURI

[Term]
id: MONDO:0004765
name: intrinsic asthma
def: "An asthma that is triggered by factors not related to allergies such as anxiety, stress, exercise, cold air, dry air, hyperventilation, smoke, viruses, chemical irritants, autonomic imbalance, hormonal deficiencies and psychogenic influences. It is characterized by airway obstruction and inflammation that is at least partially reversible with medication. The symptoms include coughing, wheezing, shortness of breath or rapid breathing, and chest tightness." [DOID:9360, http://www.aafa.org/display.cfm?id=8&sub=17, http://www.ncbi.nlm.nih.gov/pmc/articles/PMC1532783/pdf/califmed00272-0002b.pdf]
xref: DOID:9360 {source="MONDO:equivalentTo"}
xref: ICD10CM:J45 {source="DOID:9360"}
xref: ICD9:493.1 {source="DOID:9360"}
xref: SCTID:155576005 {source="DOID:9360"}
xref: SCTID:195973000 {source="DOID:9360"}
xref: SCTID:195976008 {source="DOID:9360"}
xref: SCTID:266361008 {source="DOID:9360", source="MONDO:equivalentTo"}
xref: SCTID:266397004 {source="DOID:9360"}
xref: SCTID:8312004 {source="DOID:9360"}
xref: UMLS:C0155880 {source="DOID:9360", source="MONDO:equivalentTo"}
is_a: MONDO:0004979 {source="DOID:9360"} ! asthma
disjoint_from: MONDO:0004784 ! allergic asthma
relationship: disease_has_feature HP:0000739 ! Anxiety
relationship: disease_has_feature HP:0002099 ! Asthma
relationship: disease_has_feature HP:0002883 ! Hyperventilation

Reason for deprecation
Non-atopic asthma and intrinsic asthma are generally considered to be the same. These terms describe a type of asthma that is not triggered by allergic reactions, which is distinct from atopic or extrinsic asthma that is typically triggered by allergens such as pollen, dust mites, or pet dander. --- ChatGPT
Term to be merged with
Your nano-attribution (ORCID)
https://orcid.org/0000-0002-7356-1779

This issue blocks this PR

I removed the "intrinsic asthma" synonym from MONDO:0800112 to resolve the QC fail until these terms are merged

Agree with the merging of MONDO:0800112 non-atopic asthma into MONDO:0004765 intrinsic asthma because they represent the same concept.

@sabrinatoro is not on the list/does not have an obsoletion tag, it needs to be tagged

Thank you. It is on the list (though there was not "on list" tag)

authors: katiermullen matentzn nicolevasilevsky sabrinatoro


text:
TypeScript Project References + Eslint

Currently not very well supported. Adding this as a TODO for when this is possible.

Updated config recently. Appears to be working well, but definitely not production-ready yet.

repo: mondash/ts-library-template


text:
Change "magazines" section to "newsletters" and update resources at library page

Renamed "magazines" title because using "newsletters" title is more appropriate.
Didn't write a description for resources, if needed feel free to make suggestion.
Didn't include revuo-xmr.com because @erciccione pointed some issues at #1976

and it will close #1976

If the moneromoons ccs proposal is not merged to funding , he will not produce the newsletter anymore , something to consider (and is currently away for the next 4 weeks)

Opinions about my comment above?

@HardenedSteel i don't know as i'm not very familiar with any of them, but even just author and structure (published every N) would be enough.

ping @HardenedSteel

we can merge as is OR add/test html scripting with this pull request ive made here https://github.com/HardenedSteel/monero-site/pull/2

I'd merge as it is, since this is already reviewed and i would open a dedicated pr after if you want to propose that patch. That said, personally i don't see the need to increase complexity and add a new file. It's only two entries, but even if it was more, the current structure could still be used without problems.

authors: HardenedSteel erciccione plowsof

repo: monero-project/monero-site


text:
Fix #273

Trim zeros and dot in order to have numbers with trailing zeros snd only trailing zerod to be seen as no decimal.

@sagikazarmark Could you review this PR? It became a little more than a simple fix.

Okay, even some more changes were required because of failing tests after merging. Let me explain why.
Number::isInteger('5.0'); // false
(new Number('5', '00'))->isDecimal(); // false

That is inconsistent. And that was basically tested @sagikazarmark recently added test for really big numbers containing zeros. Hence, the tests failed. With the updated PR the Number class is now consistent, allowing '5.00' as an integer and therefore allowing the same for Money. So the following is now allowed.
new Money(5, new Currency('USD'));
new Money('5', new Currency('USD'));
new Money('5.00', new Currency('USD'));

@sagikazarmark Could you have a look at this one? Afterwards I want to tag a new beta.

Due to rounding and consistency of behaviour of numbers with trailing zeros, this package now accepts integers with trailing zeros.

repo: moneyphp/money


text:
[4] Modify Club More Info Page and associated Components (Dynamic);

Do all work for this task in a branch called issue-08.
Modify the Club page (There should be a single more info page that dynamically changes using flow routing)

Using useParams(), query the URL to get the specific club that the page should load
Using the tracker,

subscribe to the Clubs publication
Pull a single club from the collection

Pass Club data to components

Club Info Page Complete
(use the template as a guide)
More Info page will dynamically render its contents by querying the URL (to determine the specific club) and pulling the data for the specific club from the Clubs Collection.
Routing is setup using flow routing, to allow page re-use

authors: LuuDanny pamanuel

repo: mongo-mongoers/club-hub


text:
CLOUDP-166849

Description
Remove digest from openapi as it does generate +400 lines of warnings and a lot of dead code in the SDK.
Digest is not supported authentication scheme by many generators.
After removing security we can still pass custom http/token refresh option.
Security in generated clients is only used to automatically configure authentication.

After discussion I think we can close that and reconsider adding it using different tool.

repo: mongodb/go-client-mongodb-atlas


text:
feat(NODE-2014)!: return the result of provided callback in withTransaction and withSession

Description
Updates withTransaction and withSession helpers to return the return value of the user provided callback.
What is changing?

session.withTransaction() now properly returns the return value of the callback.
client.withSession() updates its signature to return Promise<any> instead of Promise<void and returns the return value of the provided callback.
Updates migration guide.

Is there new documentation needed for these changes?
None
What is the motivation for this change?
NODE-2014

Double check the following

[x] Ran npm run check:lint script
[x] Self-review completed using the steps outlined here
[x] PR title follows the correct format: type(NODE-xxxx)[!]: description

Example: feat(NODE-1234)!: rewriting everything in coffeescript

[x] Changes are covered by tests
[ ] New TODOs have a related JIRA ticket

From slack: We're moving this effort down the road to the next major to get ahead of documentation updates that we would want to have ready before committing to this change.

authors: durran nbbeeken

repo: mongodb/node-mongodb-native


text:
feat(NODE-5444)!: emit deprecation warning for useNewUrlParser and useUnifiedTopology

Description
What is changing?

emit deprecation warning for useNewUrlParser and useUnifiedTopology
unit test for warning

Is there new documentation needed for these changes?
Yes. Docs changes is filed on the ticket.
What is the motivation for this change?
See below
Release Highlight

useNewUrlParser and useUnifiedTopology emit deprecation warnings
These options were removed in 4.0.0 but continued to be parsed and silently left unused. We have now added a deprecation warning through Node.js' warning system to prepare for finally removing these options in the next major release.

Double check the following

[x] Ran npm run check:lint script
[x] Self-review completed using the steps outlined here
[x] PR title follows the correct format: type(NODE-xxxx)[!]: description

Example: feat(NODE-1234)!: rewriting everything in coffeescript

[x] Changes are covered by tests
[x] New TODOs have a related JIRA ticket

Fun fact - Mongoose removed these options with Mongoose 6.0.0

authors: alexbevi nbbeeken


text:
Getting uninitialized constant

error_message:
 - uninitialized constant Mongoid::Scroll::Cursor::Origin
    Origin::Selector.new

backtrace:
~/.gem/ruby/3.1.2/gems/mongoid-scroll-0.3.7/lib/mongoid/scroll/cursor.rb:20:in `criteria'
    ~/.gem/ruby/3.1.2/gems/mongoid-scroll-0.3.7/lib/mongoid/criteria/scrollable.rb:60:in `build_cursor_criteria'
    ~/.gem/ruby/3.1.2/gems/mongoid-scroll-0.3.7/lib/mongoid/criteria/scrollable.rb:10:in `scroll'
    ~/.gem/ruby/3.1.2/gems/slack-ruby-bot-server-1.2.1/lib/slack-ruby-bot-server/api/helpers/cursor_helpers.rb:19:in `paginate_by_cursor'
    ~/.gem/ruby/3.1.2/gems/slack-ruby-bot-server-1.2.1/lib/slack-ruby-bot-server/api/helpers/cursor_helpers.rb:47:in `paginate_and_sort_by_cursor'
    ~/.gem/ruby/3.1.2/gems/slack-ruby-bot-server-1.2.1/lib/slack-ruby-bot-server/api/endpoints/teams_endpoint.rb:29:in `block (2 levels) in \u003cclass:TeamsEndpoint\u003e'

This appears to be an error originating from another gem I'm using.  Perhaps something is misconfigured in my application, but I'm not sure where to begin.

What version of mongoid? I bet it's 8. It has been a while since we have updated this library. I would start by replacing Travis CI with GHA, and then adding mongoid 8 support.

What version of mongoid? I bet it's 8. It has been a while since we have updated this library. I would start by replacing Travis CI with GHA, and then adding mongoid 8 support.

YEs it's version 8.

@Altonymous you know what to do, I can review/merge PRs

Added support for Mongoid 8 in #33 and CI in #34.

authors: Altonymous dblock

repo: mongoid/mongoid-scroll


text:
Task.> and < combinator

It can be found in cats.Apply syntax and/or cats.FlatMap
but it's very common to use, so importing cats all the time is annoying.
final def *>[B](that: => Task[B]): Task[B]
final def <*[B](that: => Task[B]): Task[A]

taskA *> taskB // runs taskA, then taskB, returns the result of taskB
taskA <* taskB // runs taskA, then taskB, returns the result of taskA

I will pick it up

I see that we have >>. Can we also have <* and *>, with the signature from Cats?
These operators are still useful, in spite of their strict parameter and remember that many people import cats.implicits._ anyway, so they are available.

I use <* a lot for triggering side effects, like logs, after some important action.

And <* shouldn't have a non-strict param, because it wouldn't help 😉

authors: Avasil alexandru valenterry

repo: monix/monix


text:
Update sbt-scalajs, scalajs-compiler, ... to 1.16.0 in series/4.x

About this PR
📦 Updates

org.scala-js:sbt-scalajs
org.scala-js:scalajs-compiler
org.scala-js:scalajs-library
org.scala-js:scalajs-library_2.13
org.scala-js:scalajs-test-bridge
org.scala-js:scalajs-test-bridge_2.13

from 1.14.0 to 1.16.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-js" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-js" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #1872.


text:
Task timeout doesn't cancel the task which has timed out

Task.timeout is implemented as https://github.com/monixio/monix/blob/13021b735320ecd76581158716557df0d7d1dcf4/monix-eval/shared/src/main/scala/monix/eval/Task.scala#L486:
timeoutTo(after, raiseError(new TimeoutException(s"Task timed-out after $after of inactivity")))

and
  def timeoutTo[B >: A](after: FiniteDuration, backup: Task[B]): Task[B] =
    Task.chooseFirstOf(self, backup.delayExecution(after)).map {
      case Left(((a, futureB))) =>
        futureB.cancel()
        a
      case Right((futureA, b)) =>
        futureA.cancel()
        b
    }

If the original task succeeds, then the map operator will cause the backup (timeout) task to cancel.
However, if the backup (timeout) task completes first, it will return a Task in an error state.  The map operator is then short circuited and the original task is not cancelled.

chooseFirstOf should cancel everything in case one task ends in error. I modified it a little in the last release and might have made a mistake.
I'm not at a computer right now. Will confirm later.
Thanks for the report. Do you want to attempt a fix?

@lukestephenson there was a test already that proves the main task is indeed getting canceled, because as I said, chooseFirstOf cancels all tasks in case one of them terminates in error. Link to the test.
BTW, this happens on master and in the latest version at least. Make sure you're on the latest version.
On the other hand, in case you have modeled a flatMap loop, then you may have been bitten by this other issue: https://github.com/monixio/monix/issues/207 - if yes, then a fix is already on master and will be available in the next release.
Cheers,

@lukestephenson doing some cleanup. You can reopen this issue if I missed anything and you can reproduce the problem.

authors: alexandru lukestephenson

repo: monixio/monix


text:
There was a problem retrieving the latest weather information.

Any idea why ?

Yahoo service is unavailable maybe?
https://github.com/monkeecreate/jquery.simpleWeather/issues/174#issuecomment-180872480

Yahoo's API was down. It seems back up now.

I have the same problem. A library with this issue is completely useless.

@oligalma I completely agree. See #221 for information.

Do you know how to get the weather using PHP? In this page (http://99webtools.com/blog/get-weather-information-using-php) says that is possible with Open Weather Map. But I tried the example code and I get a "Unauthorized" error, I don't know why...

Open Weather Map now requires registering and using an API key (free and paid plans at http://openweathermap.org/price). Looks like that post is just out dated. That type of question would be better fit for http://stackoverflow.com though since that post isn't something I have anything to do with.

authors: fleeting georgekaf oligalma vimorozov


text:
One pixel border around isometric tile map and map larger than expected

Testing isometric tile maps on iOS.
My game view is setup like this:
gameView.DesignResolution = new CCSizeI (1920, 1080);
gameView.ResolutionPolicy = CCViewResolutionPolicy.ShowAll;

My TMX map is 30x33 tiles (sized 64x32), which results in 30x64 = 1.920 pixels width and 33x32 = 1.056 pixels height. This means the entire map should fit on the screen without any scaling.
The result however shows that:

There is a border around each tile
The width is wider than 1.920 and the map is cropped on the left edge

Map and textures: https://dl.dropboxusercontent.com/u/111612273/CocosSharp_tiles_border_issue.zip

@Krumelur your tile-map is not perfectly diagonal. If you'll notice the left-most tile is at (0,32) while the right-most is at (29,0). So your calculation of the width is incorrect.

You are right about the dimensions.

I'm getting much better results by turning anti aliasing off map.Antialiased = false;
Still, there are incorrect pixels.
iPhone 6:

iPhone 6+ (= design resolution)

@Krumelur I have inspected the pre-existing tile-map isometric tests and from what I've seen, the trick is to make the tile-map dimensions of the map itself slightly smaller and/or offset than the tile dimensions of the tile-set as seen below

In this way, there's a slight overrun of each tile quad which helps to remove these border artefacts. I'm by no means on expert with TMX, but given this problem is not unique to CocosSharp, I'm going to close this issue for now.

authors: Krumelur rtabbara

repo: mono/CocosSharp


text:
Indenting broken

I am working through the MDN Django Tutorial and noticed this problem:
{% extends "base_generic.django-html" %}
{% block content %}

Title: {{ book.title }}

        Author:{{ book.author }}

        Summary: {{ book.summary }}

        ISBN: {{ book.isbn }}

{% endblock content %}
{% block content %}

Title: {{ book.title }}

        Author:{{ book.author }}

        {{ book.summary }}

        {{ book.isbn }}

{% endblock content %}
{% block content %}

Title: {{ book.title }}

        Author:{{ book.author }}

        Summary: {{ book.summary }}

    ISBN: {{ book.isbn }}

{% endblock content %}

I have repeated the content block 3 times here to demonstrate the issue.
The final content block shows the issue. The p tag indentation breaks when they contain a strong tag followed by a variable.
The top block shows that it works OK if I enclose the variable in a tags or span tags ( I assume any tags would work ).
The middle block shows that it works if the p tags only contain a variable.
DJLint is the only formatter installed, but I also have the Baptiste Darthenay Django extension installed. My settings.json looks like this:
{
    "workbench.colorTheme": "Default Dark+",
    "emmet.includeLanguages": {
        "django-html": "html"
    },
    "files.associations": {
        "*.django-html": "DjangoHTML"
    },
    "[django-html]": {
        "editor.defaultFormatter": "monosans.djlint"
    },
    "editor.minimap.enabled": false,
}

Hi!
This issue is not related to the VSCode extension, but to djLint itself.
Please open an issue in their repository.

repo: monosans/djlint-vscode


text:
test the performance on fashion-mnist

Great job, it would be interesting to see how it performs on Fashion-MNIST. It's a drop-in replacement of the original MNIST for benchmarking algortithms. Dataset is available here https://github.com/zalandoresearch/fashion-mnist

Thank you. Yes, you can try, would be interesting to see!

authors: hanxiao monsta-hd

repo: monsta-hd/ml-mnist


text:
🛑 Nitter USA is down

In 608318e, Nitter USA (https://nitter.moomoo.me) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nitter USA is back up in 841945e.


text:
add assert_ne, assert_false, assert_true to built-in

Move some frequently used functions from the test package to built-in.
Mark old API deprecated

Pull Request Test Coverage Report for Build 2671
Details

0 of 10 (0.0%)  changed or added relevant lines in 1 file are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.3%) to 78.668%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

builtin/assert.mbt
0
10
0.0%

Files with Coverage Reduction
New Missed Lines
%

test/test.mbt
4
9.52%

Totals

Change from base Build 2667:
-0.3%

Covered Lines:
3378

Relevant Lines:
4294

💛  - Coveralls

authors: Yoorkin coveralls

repo: moonbitlang/core


text:
feat: support asdf plugins through a proto WASM plugin

Fixes #539
/claim #539

@varshith257 Plugins don't belong in this repo, so it should probably be its own repo? I'm not sure how bounties work in that case.

@milesj We can implement it and reference this issue there and if a PR merged there it will automatically considered for claim and another approach is to maybe we can update our readme or docs right in that PR you can tip it .

Moving this work to the new repo as we discussed

repo: moonrepo/proto


text:
🛑 plex server is down

In 5bf388f, plex server ($PLEX_URL/identity) was down:

HTTP code: 0
Response time: 0 ms

Resolved: plex server is back up in af149ed.

repo: mooseburgr/kmj-wtf-upptime


text:
fix: generate length prefix with encoded data

Problem
While dealing with the EBCDIC1047 encoding, some characters can be decoded from 1 byte to 2 bytes. It can cause an issue with the message packing.
For instance, this decodes EBCDIC1047 to UTF-8. it will transform 65 (0x41) to 2 bytes (0xc2, 0xa0).
When we pack this data again, the data length we got is 2 instead of 1.
How to reproduce
	spec := &field.Spec{
		Length:      5,
		Description: "Field",
		Enc:         encoding.EBCDIC1047,
		Pref:        prefix.EBCDIC1047.L,
	}

	str := field.NewString(spec)
	str.SetBytes([]byte{194, 160, 49})
	packed, err := str.Pack()
	size, err := str.Unpack(packed)

the Unpack will fail with the error failed to decode content: not enough data to decode. expected len 3, got 2.
Because the str.Pack() encode 3 as length prefix. The actual representation in EBCDIC1047 of []byte{194, 160, 49} has only 2 bytes (0x41, 0xf1)
How to fix
Encode the length prefix with encoded data, instead of original data.

Closed. Open a new PR https://github.com/moov-io/iso8583/pull/340 with another fork


text:
Possible to Put multiple items?

We have a use case where we want to upload a JSON array. That would require parsing the JSON and multiple putitems or a batch write. Is it possible to support that use case?

Oh, That sounds great. But unfortunately, Github Actions does not support array inputs even YAML can represent array types. Since Input of Github Actions rely on Environment Variable, it won't be supported.
Anyway, It would be nice if we support batchPut (batchWrite) operation. but as i earlier mentioned,  it will require serialized json array input.
Below is candidate interface:
type BatchPutItemInput = {
  operation: "batch-put";
  region: string;
  table: string;
  items: string; // JSON-serialized array
}

# ...
jobs:
  job:
    runs-on: ubuntu-latest
    timeout-minutes: 5
    steps:
      - name: Put DynamoDB Item
        uses: mooyoul/dynamodb-actions@v1.1.3
        env:
          AWS_DEFAULT_REGION: us-east-1
          AWS_REGION: us-east-1
          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
        with:
          operation: batch-put
          region: us-east-1
          table: my-awesome-config
          item: |
            [{
              key: "one",
              value: "wow",
              awesome: true,
              stars: 12345
            }, {
              key: "two",
              value: "such a item",
              awesome: true,
              stars: 12345
            }]

What do you think about it? Can you share your use cases if possible?

We'd need a few tweaks and they are inter-related:

first, an ability to take multiple files or folder as input.
then use AWS marshaller to convert JSON into dynamo db input format https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/DynamoDB/Converter.html#marshall-property

So something like this:
 with:
          operation: batch-put
          region: us-east-1
          table: my-awesome-config
          files: ['path/to/fileA.json', 'path/to/fileB.json', ...]

Cool! I never thought that someone wants to use file as input 😅
If so, I'd like to implement two features:

Add file support to put (single) operation
Add batchPut operation with file support

At this moment, there's a concern about file path input.
As i mentioned in previous comment, Github Actions does not support array type in Action Input. So, Multiple file input should use comma-delimited string instead. What do you think about Glob?

What do you think about Glob?

Anything that works - I know the pains of GH actions firsthand :)

Add file support to put (single) operation

I'm trying to find better evidence but I think that if your JSON file has an array, then AWS marshall should be converting it to a {'L': ...} format. So in that case, you should be able to Put the items in the whole file in a single op. Otherwise, it'd suck to iterate through the file and do putItme for every array entry.

:tada: This issue has been resolved in version 1.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

Hello @mrchief 👋
I just released v1.2.1 (Please note that v1.2.0 was broken due to missing action metadata update. Use v1.2.1 (latest) instead.)
I've added a new batch-put operation with file input support (including Glob support).
Take a look and please leave feedback. Thanks! :)

authors: mooyoul mrchief

repo: mooyoul/dynamodb-actions


text:
Invoking client hub method ReceiveMessage failed due to valueNotFound

Hello.
Thank you for your library.
I have a problem.
When I send message I get error on iOS client
2020-04-20T10:51:24.650Z debug: Message received: {"type":1,"target":"ReceiveMessage","arguments":["CreatedMessage"]}
2020-04-20T10:51:24.654Z error: Invoking client hub method ReceiveMessage failed due to: valueNotFound(Swift.String, Swift.DecodingError.Context(codingPath: [_JSONKey(stringValue: "Index 1", intValue: 1)], debugDescription: "Unkeyed container is at end.", underlyingError: nil))

My code on server:
_hubContext.Clients.All.SendAsync("ReceiveMessage", "CreatedMessage")

On JS client works good.
iOS client code:
connection = HubConnectionBuilder(url: url).withLogging(minLogLevel: .debug).build()
connection.on(method: "ReceiveMessage", callback: { (user: String, message: String) in
            do {
                self.handleMessage(message, from: user)
            } catch {
                print(error)
            }
})

connection.start()

on JS code (works):
const connection = new signalR.HubConnectionBuilder().withUrl("/hub").build();

connection.on("ReceiveMessage", function (res) {
    // works

});

I found problem.
In my case need use
connection.on(method: "ReceiveMessage") { response in
            self.handleMessage(response)
}

instead of
connection.on(method: "ReceiveMessage", callback: { (user: String, message: String) in
            do {
                self.handleMessage(message, from: user)
            } catch {
                print(error)
            }
})

repo: moozzyk/SignalR-Client-Swift


text:
Problem with executable jars

I call 'mvn compile' and 'mvn install' but big jar morfologik-polish-2.1.7-SNAPSHOT.jar has not main manifest file and small jars have class loading errors.

mvn package is probably what you want and need. I don't know why you experience class loading errors - the build works on the CI all the time and it passes it just fine.

authors: borneq dweiss

repo: morfologik/morfologik-stemming


text:
chore(deps): bump Microsoft.Web.WebView2 from 1.0.2045.28 to 1.0.2210…

….55 in /src/shell/dotnet/Shell

Replacing #512

repo: morganstanley/ComposeUI


text:
Release/v0.23.2

daily: https://github.com/mosaicml/composer/actions/runs/9425165344
regression testing: https://github.com/databricks-mosaic/regression-testing/actions/runs/9425191646

@bigning good to close?

repo: mosaicml/composer


text:
deadlock at composer.trainer.trainer: Spinning the dataloaders

Environment
Collecting system information...
---------------------------------
System Environment Report
Created: 2023-07-07 01:31:32 PDT
---------------------------------

PyTorch information
-------------------
PyTorch version: 2.0.1+cu117
Is debug build: False
CUDA used to build PyTorch: 11.7
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.6 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang version: Could not collect
CMake version: version 3.26.3
Libc version: glibc-2.31

Python version: 3.9.7 (default, Sep 16 2021, 13:09:58)  [GCC 7.5.0] (64-bit runtime)
Python platform: Linux-5.4.0-149-generic-x86_64-with-glibc2.31
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration:
GPU 0: NVIDIA A100-SXM4-40GB
GPU 1: NVIDIA A100-SXM4-40GB
GPU 2: NVIDIA A100-SXM4-40GB
GPU 3: NVIDIA A100-SXM4-40GB
GPU 4: NVIDIA A100-SXM4-40GB
GPU 5: NVIDIA A100-SXM4-40GB
GPU 6: NVIDIA A100-SXM4-40GB
GPU 7: NVIDIA A100-SXM4-40GB

Nvidia driver version: 525.105.17
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   43 bits physical, 48 bits virtual
CPU(s):                          256
On-line CPU(s) list:             0-255
Thread(s) per core:              2
Core(s) per socket:              64
Socket(s):                       2
NUMA node(s):                    8
Vendor ID:                       AuthenticAMD
CPU family:                      23
Model:                           49
Model name:                      AMD EPYC 7742 64-Core Processor
Stepping:                        0
Frequency boost:                 enabled
CPU MHz:                         1706.139
CPU max MHz:                     2250.0000
CPU min MHz:                     1500.0000
BogoMIPS:                        4491.70
Virtualization:                  AMD-V
L1d cache:                       4 MiB
L1i cache:                       4 MiB
L2 cache:                        64 MiB
L3 cache:                        512 MiB
NUMA node0 CPU(s):               0-15,128-143
NUMA node1 CPU(s):               16-31,144-159
NUMA node2 CPU(s):               32-47,160-175
NUMA node3 CPU(s):               48-63,176-191
NUMA node4 CPU(s):               64-79,192-207
NUMA node5 CPU(s):               80-95,208-223
NUMA node6 CPU(s):               96-111,224-239
NUMA node7 CPU(s):               112-127,240-255
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Mmio stale data:   Not affected
Vulnerability Retbleed:          Vulnerable
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling, PBRSB-eIBRS Not affected
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate sme ssbd mba sev ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr wbnoinvd arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif umip rdpid overflow_recov succor smca

Versions of relevant libraries:
[pip3] numpy==1.24.4
[pip3] pytorch-ranger==0.1.1
[pip3] torch==2.0.1
[pip3] torch-optimizer==0.3.0
[pip3] torchdata==0.6.1
[pip3] torchmetrics==0.11.4
[pip3] torchtext==0.15.2
[pip3] torchvision==0.15.2
[conda] numpy                     1.24.4                   pypi_0    pypi
[conda] pytorch-ranger            0.1.1                    pypi_0    pypi
[conda] torch                     2.0.1                    pypi_0    pypi
[conda] torch-optimizer           0.3.0                    pypi_0    pypi
[conda] torchdata                 0.6.1                    pypi_0    pypi
[conda] torchmetrics              0.11.4                   pypi_0    pypi
[conda] torchtext                 0.15.2                   pypi_0    pypi
[conda] torchvision               0.15.2                   pypi_0    pypi

Composer information
--------------------
Composer version: 0.15.1
Composer commit hash: None
Host processor model name: AMD EPYC 7742 64-Core Processor
Host processor core count: 128
Number of nodes: 1
Accelerator model name: NVIDIA A100-SXM4-40GB
Accelerators per node: 1
CUDA Device Count: 8

To reproduce
get the dataset ,and then use the exactly same command at https://github.com/mosaicml/llm-foundry/tree/main#quickstart
composer train/train.py   train/yamls/pretrain/mpt-125m.yaml   data_local=my-copy-c4   train_loader.dataset.split=train_small   eval_loader.dataset.split=val_small   max_duration=10ba   eval_interval=0   save_folder=mpt-125m

and we'll see the output as below:
...
Starting training...
2023-07-07 01:36:02,640: rank0[1074804][MainThread]: INFO: composer.trainer.trainer: Using precision Precision.AMP_BF16
******************************
Config:
enabled_algorithms/GradientClipping: true
node_name: unknown because NODENAME environment variable not set
num_gpus_per_node: 8
num_nodes: 1
rank_zero_seed: 17

******************************
2023-07-07 01:36:02,649: rank0[1074804][MainThread]: DEBUG: composer.trainer.trainer: Spinning the dataloaders

I waited for a long time and no progress, and it can be stopped with Ctrl+C.
At this time, I checked the dataset and found that most files have been deleted.
$ tree my-copy-c4/
my-copy-c4/
├── train_small
│   └── index.json
└── val_small
    └── index.json

I've tried to add 'keep_zip: true' in mpt-125m.yaml, but no use.
I also tried to change the mode size from 12 layers to 1 layers, and tried on two GPUs with below commands:
#1. re-get the data set
tree my-copy-c4/
my-copy-c4/
├── train_small
│   ├── index.json
│   ├── shard.00000.mds.zstd
│   ├── shard.00001.mds.zstd
│   ├── shard.00002.mds.zstd
│   ├── shard.00003.mds.zstd
│   ├── shard.00004.mds.zstd
│   ├── shard.00005.mds.zstd
│   ├── shard.00006.mds.zstd
│   ├── shard.00007.mds.zstd
│   ├── shard.00008.mds.zstd
│   ├── shard.00009.mds.zstd
│   ├── shard.00010.mds.zstd
│   ├── shard.00011.mds.zstd
│   ├── shard.00012.mds.zstd
│   ├── shard.00013.mds.zstd
│   ├── shard.00014.mds.zstd
│   ├── shard.00015.mds.zstd
│   ├── shard.00016.mds.zstd
│   ├── shard.00017.mds.zstd
│   ├── shard.00018.mds.zstd
│   ├── shard.00019.mds.zstd
│   ├── shard.00020.mds.zstd
│   ├── shard.00021.mds.zstd
│   ├── shard.00022.mds.zstd
│   ├── shard.00023.mds.zstd
│   └── shard.00024.mds.zstd
└── val_small
    ├── index.json
    ├── shard.00000.mds.zstd
    ├── shard.00001.mds.zstd
    └── shard.00002.mds.zstd

2 directories, 30 files

#2 the the command with 2 GPUs and with verbose.
composer -n 2 -v train/train.py   train/yamls/pretrain/mpt-125m.yaml   data_local=my-copy-c4   train_loader.dataset.split=train_small   eval_loader.dataset.split=val_small   max_duration=10ba   eval_interval=0   save_folder=mpt-125m

and this time, I saw the crash as below.
Starting training...
2023-07-07 01:42:36,789: rank0[1085371][MainThread]: INFO: composer.trainer.trainer: Using precision Precision.AMP_BF16
******************************
Config:
enabled_algorithms/GradientClipping: true
node_name: unknown because NODENAME environment variable not set
num_gpus_per_node: 2
num_nodes: 1
rank_zero_seed: 17

******************************
2023-07-07 01:42:36,800: rank0[1085371][MainThread]: DEBUG: composer.trainer.trainer: Spinning the dataloaders
2023-07-07 01:42:37,380: rank0[1086841][ThreadPoolExecutor-0_0]: ERROR: concurrent.futures: exception calling callback for <Future at 0x7f70f0254160 state=finished raised RuntimeError>
Traceback (most recent call last):
  File "/raid/miniconda3/envs/yjguo_mpt/lib/python3.9/site-packages/streaming/base/stream.py", line 275, in _download_file
    download_file(remote, local, self.download_timeout)
  File "/raid/miniconda3/envs/yjguo_mpt/lib/python3.9/site-packages/streaming/base/storage/download.py", line 285, in download_file
    raise ValueError(
ValueError: In the absence of local dataset, path to remote dataset must be provided

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/raid/miniconda3/envs/yjguo_mpt/lib/python3.9/concurrent/futures/_base.py", line 329, in _invoke_callbacks
    callback(self)
  File "/raid/miniconda3/envs/yjguo_mpt/lib/python3.9/site-packages/streaming/base/dataset.py", line 1086, in on_exception
    raise exception
  File "/raid/miniconda3/envs/yjguo_mpt/lib/python3.9/concurrent/futures/thread.py", line 52, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/raid/miniconda3/envs/yjguo_mpt/lib/python3.9/site-packages/streaming/base/dataset.py", line 1132, in _download_thread
    self.download_shard(shard_id, False)
  File "/raid/miniconda3/envs/yjguo_mpt/lib/python3.9/site-packages/streaming/base/dataset.py", line 985, in download_shard
    stream.download_shard(shard)
  File "/raid/miniconda3/envs/yjguo_mpt/lib/python3.9/site-packages/streaming/base/stream.py", line 366, in download_shard
    self._download_shard_part(raw_info, zip_info, shard.compression)
  File "/raid/miniconda3/envs/yjguo_mpt/lib/python3.9/site-packages/streaming/base/stream.py", line 345, in _download_shard_part
    self._download_file(zip_info.basename)
  File "/raid/miniconda3/envs/yjguo_mpt/lib/python3.9/site-packages/streaming/base/stream.py", line 284, in _download_file
    raise RuntimeError(
RuntimeError: Failed to download None -> my-copy-c4/val_small/shard.00002.mds.zstd. Tried 3 times, got errors:
[ValueError('In the absence of local dataset, path to remote dataset must be provided'), ValueError('In the absence of local dataset, path to remote dataset must be provided'), ValueError('In the absence of local dataset, path to remote dataset must be provided')]

btw, I have network issue and could not download the data again,  and so have to use the local files but they are deleted in the script running.

I now found that the issue is relative to the compression of the dataset, the issue is gone if I remove "--compression zstd" at https://github.com/mosaicml/llm-foundry/tree/main/scripts/data_prep#huggingface-data

with "--compression zstd" removed, I successfully debug the script for some times, but suddenly the issue appeared again (see below). I never touch the data files manually during the period.  I have tried to uninstall/install mosaicml, mosaicml-streaming, and llm-foundry, but no use, still the same issue.  Once I see the issue, I always see the issue.
ValueError: Reused local directory: ['/raid/yjguo/mpt/llm-foundry/scripts/my-copy-c4/train_small'] vs
['/raid/yjguo/mpt/llm-foundry/scripts/my-copy-c4/train_small']. Provide a different one. If using a unique local directory, try
deleting the local directory and call `streaming.base.util.clean_stale_shared_memory()` only once in your script to clean up the
stale shared memory before instantiation of `StreamingDataset`.

I've tried call streaming.base.util.clean_stale_shared_memory() in train.py, but no use.

I am so sorry to hear that.
Streaming uses several data structures that live in in shared memory in order to coordinate worker processes (eg, jointly managing the shard cache(s)).
There unfortunately are ways for processes to die or go into a zombie state that leaves shared memory objects behind. We have been improving this situation over time, but our work here is clearly not over.
Because the pain of debugging race conditions due to shared resources being modified (especially unknowingly) by multiple runs at the same time is even worse, we added strict local dir collision checks.
I see you are running on Ubuntu. You should be able to list /dev/shm/ and find whatever streaming bookkeeping that should not be there (it will end with _locals) and can be removed. Feel free to reply with the listing and we can write you the script.
If you can reboot the system, that will clear away all shared memory too.

thanks, the issue is fixed with "rm -rf /dev/shm/*" and prepare the data files again.

thanks, the issue is gone after machine reboot.

btw, the issue is still there if I download the dataset with "--compression zstd"

btw, the issue is still there if I download the dataset with "--compression zstd"

I am facing the same issue. Any clue on how to fix this?

@guoyejun What would happen if you run this composer train/train.py train/yamls/pretrain/mpt-125m.yaml   data_remote=my-copy-c4 data_local=/tmp/streaming/dataset  train_loader.dataset.split=train_small   eval_loader.dataset.split=val_small   max_duration=10ba   eval_interval=0   save_folder=mpt-125m. Atleast, you should not see the dataset getting deleted. The changes here are, provide remote location as a current local directory location and a local as a new directory. Streaming dataset would copy the data from remote to local.
@knighton is working on a fix as part of PR https://github.com/mosaicml/streaming/pull/330

I believe this has been fixed by the linked pull request. Please open a new issue if you are still encountering problems.

This problem is still there, and it can be solved with clear the cache mentioned above.

authors: LingxiaoShawn dakinggg guoyejun karan6181 knighton mayankjobanputra

repo: mosaicml/llm-foundry


text:
Create flick/glitch while set navigation params

Prepare StackNavigator
Render Radio Buttons in the second screen
Inside second screen, use this.props.navigation.setParams to set any value.
Press back button, you might see the flick/blink/glitch on the navigator -> very ugly effect. I think navigator might be refreshed after setParams

Remove radio buttons and it works fine with set navigation params.

Thanks for your issue.
Could you try the latest version?
If you still have a problem, please feel free to re-open this issue.


text:
Reading a '.sbfmf' file

I'm trying to read a file from http://ctrax.sourceforge.net/ctrax.html#example-video-annotation-and-mat-files specifically movie20071009_163231.sbfmf from http://sourceforge.net/projects/ctrax/files/Ctrax samples/example-sbfmfvideo-ann-mat-5M5F5min-20090518.zip/download
I can't find any documentation on the .sbfmf format versus the .fmf format so I'm guessing that difference is the cause of my issue.  Here is the gist of how Im trying to convert the fmf to an mp4 (on mac osx 10.5) using opencv.
import cv2
import motmot.FlyMovieFormat.FlyMovieFormat as FlyMovieFormat

capture_stream = FlyMovieFormat.FlyMovie('video/movie20071009_163231.sbfmf')

# define the codec and create VideoWriter object
codec = cv2.cv.CV_FOURCC('m','p','4','v')
size = (capture_stream.get_width(), capture_stream.get_height())
frames_per_second = 20
output_stream = cv2.VideoWriter(
    'video/five_flys.mp4',
    codec,
    frames_per_second, # Frames per second
    size # Width / Height
)

for frame_number in range(capture_stream.get_n_frames()):
    frame,timestamp = capture_stream.get_frame(frame_number)

    try:
        output_stream.write(frame)
        if cv2.waitKey(1) & 0xFF == ord('q'):
            break
    except Exception,e:
        print e
        break

capture_stream.release()
output_stream.release()

And I get a big stack trace:
$ python fmf2mp4.py
(0, 4215296)
Traceback (most recent call last):
  File "fmf2mp4.py", line 26, in <module>
    frame,timestamp = capture_stream.get_frame(frame_number)
  File "build/bdist.macosx-10.5-x86_64/egg/motmot/FlyMovieFormat/FlyMovieFormat.py", line 332, in get_frame
  File "build/bdist.macosx-10.5-x86_64/egg/motmot/FlyMovieFormat/FlyMovieFormat.py", line 327, in get_next_frame
  File "build/bdist.macosx-10.5-x86_64/egg/motmot/FlyMovieFormat/FlyMovieFormat.py", line 293, in _read_next_frame
NotImplementedError: Reading not implemented for |??N?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o@?o...

No rush, just playing.  Thanks.
Thatcher

Oh, sorry, I missed this issue when you filed it 5 years ago. I don't know much about sbfmf files and certainly would not expect them to be compatible with fmf. I'm closing the issue. Sorry once again for the delay.

authors: astraw thatcher

repo: motmot/flymovieformat


text:
TRIVIA IS NOT WORKING

URGENT ISSUE
TRIVIA DOESN'T SEEM TO BE WORKING
GRA4UNATORBOT - Today at 5:31 PM
ну пиздец
По___и___ь _огил
lehadnk - Today at 5:51 PM
Повгыивдеь ыогил < MATCHED ALL THE LETTERS
Поцщсиыщць согил < AND AGAIN, NOT WORKING
Понурикзвь тогил < DOESN'T SEEM TO BE WORKING AT ALL
required to be fixed AS SOON AS POSSIBLE
please let me know when you start working on this issue
IT IS VERY IMPORTANT ISSUE PLEASE PUT EVERYTHING YOU'RE WORKIN ON ASIDE AND MAKE TRIVIA WORKING AGAIN. YOU'LL GET BACK TO YOUR WORK AFTER YOU DONE BY TOMORROW.

I am researching your problem. will stay in touch

Hello, Mouzfun!
So how does your research goes so far? Did you figured root case of the issue? Can you give a few possible solutions and estimate it?
It is an urgent issue, so we're expecting a really quick progress on it.

IRL took over, will look into it next week

authors: lehadnk mouzfun

repo: mouzfun/discbot


text:
(HAL-02) USE OF WRONG ERROR MESSAGES

(HAL-02) USE OF WRONG ERROR MESSAGES
Auditor: Halborn
Severity: Informational
Description
MCR SENDS WRONG ERROR MESSAGE ON BLOCK ALREADY COMMITED
In the MCR.sol contract, the error message returned when the proposed block commitment height is behind the tolerable block height is AttesterAlreadyCommitted which can be confusing, as it is not describing the issue and is also used for when the attester tries to submit the same block commitment twice.

Recommendation
It is recommended to:
Replace the MCR error message by a more understandable message such as BlockCommitmentTooFarAhead.
Replace the Bridge error message by a more understandable message such as TimeLockNotExpired.

Fixed in https://github.com/movementlabsxyz/movement/pull/693

repo: movementlabsxyz/movement