Unable to read parquet files registered as dataset using ml_client.data.get

Package Name: azure-ai-ml, azureml-fsspec
Package Version: 1.8.0, 1.1.1
Operating System: Windows
Python Version: 3.9

Describe the bug
Unable to read parquet file registered as File (uri_file) from jupyter notebook or python shell. When below code runs, it ends up crashing the kernel. The size of parquet file is only 65 MB.
import pandas as pd
from azure.ai.ml import MLClient
from azure.identity import DefaultAzureCredential

ml_client = MLClient.from_config(path="./Model", credential=DefaultAzureCredential())
data_asset = ml_client.data.get(name="bst", version="1")
df = pd.read_parquet(data_asset.path)

To Reproduce
Steps to reproduce the behavior:

Register a parquet file as  File (uri_file) type
Read it back as a pandas dataframe inside Jupyter notebook using the code given above

Expected behavior
Should be able to read dataset as pandas frame
Screenshots

Cannot execute code, session has been disposed. Please try restarting the Kernel.

The Kernel crashed while executing code in the the current cell or a previous cell. Please review the code in the cell(s) to identify a possible cause of the failure. Click here for more info. View Jupyter log for further details.

Additional context
Reading other datasets which are smaller (5 MB - 10 MB) works file.

Thank you for the feedback @waqassiddiqi. We will investigate and get back to you asap.
cc @azureml-github

I recently ran into the same issue and tried running the code in a terminal. When trying to read the parquet file I got a segmentation fault. Last time I encountered a segmentation fault when working with python it was a memory issue with part of the C/C++ source in opencv.
The parquet file itself is about 300mb. I was able to download it and load it locally. According to sys.getsizeof it was about 13 gb in memory. When I first encountered this issue on a notebook in azure ml studio I was using a compute with 32gb ram, which should have been enough to hold the uncompressed dataset.
I was also able to load the parquet file when running a command job.

Will Check this. Thank you for let us know.

Me and my team have encountered this issue as well. Some parquet files simply don't work when using azureml-fsspec (==1.2.0). It doesn't really matter whether we save them using pyarrow or fastparquet (tried out different [random] engine versions too). Both compressed (snappy) and uncompressed files fail.
Downloading those files to local storage helps. Also, running our tasks inside command components seems to work just fine.
My intuition tells me that the root cause is similar to what's happening here: https://github.com/Azure/azure-sdk-for-python/issues/30518

We have some fixes for this bug. Please wait a little bit for release.

Update to azureml-dataprep 4.12.9 (https://pypi.org/project/azureml-dataprep/4.12.9/) should fix this issue. Thanks.


FileNotFoundError: [Errno 2] No such file or directory: '*.pkl'

Thank you for this excellent work.I got an error when I trying to compute the FID using the following command.
torchrun --standalone --nproc_per_node=1 generate.py --outdir=cifar10_tmp --seeds=0-49999 --subdirs \
    --network=*.pkl

I have placed the. pkl file generated by training and generate.py file in the same path, which seems to recognize *.pkl as specific file names. How can I solve this problem?

Thank you for your interest in our work.
Please rename *.pkl using the name/dir of your .pkl file.

Thank you for your reply.I misunderstood.


shallowMount fails with TypeError when component uses a data of type Symbol in it's template

Version
1.1.4
Reproduction link
https://github.com/penguintree/vue-test-util-symbol-issue
Steps to reproduce
npm run test:unit
What is expected?
Unit tests should pass
What is actually happening?
One of the unit test fails with error :
TypeError: Failed to execute 'setAttribute' on 'Element': parameter 2 is a symbol, which cannot be converted to a string.

Possibly a regression in regards of this closed issue
Basically, it is not possible to shallowMount a component wich passes a Symbol to a child component.

Can confirm, It's still an issue and only happening when running tests. In the browser console no errors are shown regarding the usage of a Symbol

Some of our users are also running into this issue with Ionic Vue (see: https://github.com/ionic-team/ionic-framework/issues/24181). Vue 3.1 sets all property keys in the properties object, even if certain properties are not actually being used by the end developer (see https://github.com/vuejs/vue-next/issues/3889). We use Symbol to differentiate between properties that are used and properties that are not used.
Using shallowMount on Ionic Vue components causes this bug to appear. Using mount instead of shallowMount works for now, but it would be great if this could get fixed.

I looked into this, I posted my findings and some ideas to proceed here: https://github.com/ionic-team/ionic-framework/issues/24181#issuecomment-971550734

@lmiller1990 any news? Ionic 6.0 is now out as stable, but can't be used before this fix is out.

@boboldehampsink Ionic 6 seems to use Vue 3, so you'll need Test Utils v2. This bug is fixed here https://github.com/vuejs/vue-test-utils-next/issues/1076 which will be released this week.
As for back-porting that fix, you could do something similar and strip out symbols in this library. It's not a priority for me right now, but if you'd like to make a PR, that'd be great.

@lmiller1990 Do we leave this ticket open for back porting it?
For me, no response from 2y so I'd go and close it. If anyone is interested he can make a PR and back port it, right?

I think it's fine to leave this open - known issue, not fixed. It's unlikely anyone is using Vue 2 with Ionic now, they would likely be looking to upgrade.

This problem can be solved using the wrapping layer arrow function

Please share a snippet @wangxiang4, this sounds like useful info. Thanks!


Warning using SQLRecordManager

System Info
LangChain version: 0.0.285
Python version: 3.11.2
Platform: x86_64 Debian 12.2.0-14
Weaviate 1.21.2 as vectorstore
Who can help?
No response
Information

[X] The official example notebooks/scripts
[ ] My own modified scripts

Related Components

[ ] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[X] Document Loaders
[X] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[ ] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction
Following the instructions here,
from langchain.indexes import SQLRecordManager, index returns the following warning:
/lib/python3.11/site-packages/langchain/indexes/_sql_record_manager.py:38: MovedIn20Warning: The ``declarative_base()`` function is now available as sqlalchemy.orm.declarative_base(). (deprecated since: 2.0) (Background on SQLAlchemy 2.0 at: https://sqlalche.me/e/b8d9)
  Base = declarative_base()

LangChain's indexes documentation doesn't include SQLRecordManager. Additionally, RecordManager documentation doesn't mention it can be used with SQLite.
Expected behavior
No warnings.

@RoderickVM I get same issue like you:

record_manager.update(
File ".../venv/lib/python3.11/site-packages/langchain/indexes/_sql_record_manager.py", line 269, in update
update_time = self.get_time()

Did you solve this issue?


Build system

Import libraries used, e.g. ajv and zmx
Copy internal schemas to extension folder, which would allow all the schemas to be under one schema folder

Validate schemas against meta schema (iow ensure they are valid schemas)

Targets would be Chrome extension, Firefox extension, polyfill library (with a version packaged for closure).


feat(rgbpp-list): add others

https://github.com/Magickbase/ckb-explorer-public-issues/issues/711

i18n for ckb.tx_id is not properly handled
question mark is not aligned


RuntimeError: Failed to initialize OpenGL

Does anyone know how to solve this problem?
(mujoco_py) xxxx@XXXX:~/.mujoco/mujoco-py/examples/MuJoCo_RL_UR5$ python3 example_agent.py
Creating window glfw
Created new control group 'Arm'.
Created new control group 'Gripper'.
Model timestep: 0.002
Set number of frames skipped:  1
dt = timestep * frame_skip:  0.002
Frames per second = 1/dt:  500
Actionspace:  MultiDiscrete([40000     6])
Observation space: Dict(rgb:Box(200, 200, 3), depth:Box(200, 200))
Found 1 GPUs for rendering. Using device 0.
Could not make EGL context current
Traceback (most recent call last):
File "example_agent.py", line 16, in
obs = env.reset()
File "/home/xxxx/anaconda3/envs/mujoco_py/lib/python3.8/site-packages/gym/envs/mujoco/mujoco_env.py", line 108, in reset
ob = self.reset_model()
File "/home/xxxx/.mujoco/mujoco-py/examples/MuJoCo_RL_UR5/gym_grasper/envs/GraspingEnv.py", line 477, in reset_model
return self.get_observation(show=self.show_observations)
File "/home/xxxx/.mujoco/mujoco-py/examples/MuJoCo_RL_UR5/gym_grasper/envs/GraspingEnv.py", line 398, in get_observation
rgb, depth = self.controller.get_image_data(
File "/home/xxxx/.mujoco/mujoco-py/examples/MuJoCo_RL_UR5/gym_grasper/controller/MujocoController.py", line 719, in get_image_data
self.sim.render(width=width, height=height, camera_name=camera, depth=True)
File "mjsim.pyx", line 156, in mujoco_py.cymj.MjSim.render
File "mjsim.pyx", line 158, in mujoco_py.cymj.MjSim.render
File "mjrendercontext.pyx", line 46, in mujoco_py.cymj.MjRenderContext.init
File "mjrendercontext.pyx", line 114, in mujoco_py.cymj.MjRenderContext._setup_opengl_context
File "opengl_context.pyx", line 130, in mujoco_py.cymj.OffscreenOpenGLContext.init
RuntimeError: Failed to initialize OpenGL

I met the same problem. Have you solved this?

I met the same problem. Have you solved this?

I solved. The following two lines of code conflict with each other and cannot be implemented at the same time, which is a bug of mujoco_py.
viewer = mujoco_py.MjViewer(sim)
image = sim.render(width=300, height = 300, camera_name='cam0', depth=False)

I solved. The following two lines of code conflict with each other and cannot be implemented at the same time, which is a bug of mujoco_py.
viewer = mujoco_py.MjViewer(sim) image = sim.render(width=300, height = 300, camera_name='cam0', depth=False)

@STONEKONG
Hello, Stone!
I agree that the error is caused by implementing these two lines of code together. But how should we solve it. Could you please share some suggestions?
Thank you very much.

I met the same problem. Have you solved this?


Consider using WRC or Arc instead of Rc?

WRC(Weighted reference counter) or Arc can be used for multithreading.

Threading is now implemented.


Compiled CSS is incorrect (SCSS in single file component, using calc() with custom property)

Version
2.6.11
Reproduction link
https://github.com/AngusMacrae/solar-system-explorer
Steps to reproduce
In the "client" folder, run "npm install" to install dependencies, then "npm run serve". Navigate to http://localhost:8080/ in your browser. Inspect one of the .planet-system elements and find the .orbit div within it. Note that in the style browser, the following line is applied:
top: calc(var(--diameter-vw) / 2 - var(--orbit-diameter) / 2);

This is accurate to the scoped SCSS in the .vue Single File Component source file.
Now either run "npm run build" and spin up a local webserver, or you can just navigate to https://solar-system-explorer.netlify.app/ which is where I have deployed the site. The site is deployed directly from the /client/dist folder in the GitHub repo, the contents of which were generated by running "npm run build".
Inspect the same .orbit element as before. But now, you'll find that the following line is different:
top: calc(var(--diameter-vw) - var(--orbit-diameter));

This line is not correct.
What is expected?
I expect the two lines to be the same. The latter should be the same as the former because they are compiled from the same source .vue file.
What is actually happening?
The CSS rule that is applied in my deployed app is not correct, resulting in breaking the visual appearance of the app.

That's not a valid reproduction, it's a whole project. It could just be related to SCSS.

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server or StackOverflow.


[Bug] Gradle 8 support

https://github.com/flutter/flutter/issues/125181
Flutter app android module can't be upgraded to gradle 8, until all dependencies which use native code are also upgraded or at least have namespace in app/build.gradle.
android {
namespace = "com.example.myapp"
...
}

Downgrade your build to gradle 7.
Only need to add the namespace for the module in the package for working with the newest requisites from gradle 8.x. Can do it manually until they fix it entering in the package and adding the namespace="de.mintware.barcode_scan"

@ArocaAlejandro do you have any updates on here?

Sorry, i don't see the mail with the response, i've answered on this
#78

I've created a PR, you can use my fork untill this is merged by changing your pubspec.yaml to:
dependencies:
  barcode_scan2:
    git:
      url: https://github.com/robinbonnes/barcode_scan2

Merged #87 and released v4.3.2 🐶


DM-13399: Use cls for first argument to Python metaclass methods

Any idea when a new version of pep8-naming might be released?  Given their history, it looks like it could be a year or more.  We could go with the 0.5.0 + patch, but I'm a bit worried that in-editor linters might not pick up that version.

There is a thread in PyCQA/pep8-naming#47 but there has been no feedback from the developer.


Development

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

Comparison is base (8d86334) 100.00% compared to head (f8f311d) 100.00%.
Report is 9 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main       #26   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines            5         5
=========================================
  Hits             5         5

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


Support PSR Cache version 3.0

Doesn't seem to be measurable differences between psr/cache version 2 and version 3.
I realize there might be something better to do with this, but Drupal ...
So the chain for me is that Drupal 10 eventually requires psr/cache ^3.0 because of guzzle requirements. The bibcite_crossref integration for Drupal depends on the client https://github.com/renanbr/crossref-client and that depends on cache/array-adapter.
So resolving the dependency here allows bibcite to be enabled in the Drupal 10 installation.
This is a READ ONLY repository.
Please make your pull request to https://github.com/php-cache/cache
Thank you for contributing.

Hey.
Thank you for your contribution, but this repository is READ ONLY. You should close this PR and make a new one at http://github.com/php-cache/cache.
Regards
The bot at SubtreeSplit.com


column not aligned

Problem Description
When creating a table with scroll the column header and content is not aligned.
Steps to Reproduce

Go to example at https://react-table.js.org/#/story/fixed-header-w-vertical-scroll

System Information

Browser: Chrome 58.0.3029.110

This is a known issue we are tracking internally.  There is a quick fix right now you can use by applying overflow-y: scroll to the .rt-thead class. This should add a scrollbar to the header and align things temporarily.

Is there a permanent fix for this?

In case this helps anyone, here's how I manually adjust the column headers to be aligned:
adjustHeaders() {
        const tableBody = document.querySelector('.rt-tbody');
        const tBodyWidth = tableBody.clientWidth;
        const tBodyStyle = window.getComputedStyle(tableBody);
        const tBodyOuterWidth = parseInt(tBodyStyle.width.slice(0, -2));
        const tr = document.querySelectorAll('.rt-thead > .rt-tr');

        const margin = tBodyWidth < tBodyOuterWidth ?
             tBodyOuterWidth - tBodyWidth :
             0;

        tr.forEach(h => {
            h.style.marginRight = margin + 'px';
        });
}

I call this method from componentWillMount() and componentWillReceiveProps() (which is necessary for my use case, but may not be necessary for everyone), as well as set it to be a debounced listener for a window resize event.

Here is how I solve this problem using css only without showing the extra scroll bars on the headers:
    overflow-y: scroll;
}

.ReactTable .rt-thead::-webkit-scrollbar {
   background: transparent;
} ```

My recommendation is to avoid using the height to set a scroll bar for the following reasons:

react-table is a page-based table (not a scrollable table)
the scrolling (while possible with the height setting) has not be properly integrated into the package and only works reliably for a very specific set of use-cases

NOTE: react-table needs to an arcihtecture design to stay "true" to React and the original design to properly incorporate a vertical scroll bar - and may then not even be what it was originally intended to be

I ended up with something slightly different, but build upon, noam3217's answer.
`componentDidUpdate() {
this.adjustHeaders();
}
adjustHeaders = () => {
const tableBody = document.querySelector('.rt-tbody');
if (tableBody) {
const tBodyWidth = tableBody.clientWidth;
const tBodyStyle = window.getComputedStyle(tableBody);
if (tBodyStyle && tBodyStyle.width) {
const tBodyOuterWidth = parseInt(tBodyStyle.width.slice(0, -2), 0);
const headerRows = document.querySelectorAll('.rt-thead > .rt-tr');
            if (headerRows) {
                const margin = tBodyWidth < tBodyOuterWidth ?
                    tBodyOuterWidth - tBodyWidth :
                    0;

                headerRows.forEach(r => {
                    r.style.marginRight = margin+1 + 'px';
                });
            }
        }
    }
}`

I have an alternative hack to fixing this, and that is simply removing all scroll bars (or more technically speaking, the appearance of there being one). My issue with both of the code solutions above is that they didn't work in IE, which I unfortunately have to always ensure is compatible with my apps.
That said, below is the css solution I'm using (I can confirm that it works in FF, IE and Chrome):
.ReactTable .rt-thead {
   overflow-y: scroll;
   scrollbar-width: none;

   /* IE properties */
   scrollbar-track-color:  #FFF;
   scrollbar-3dlight-color:  #FFF;
   scrollbar-darkshadow-color:  #FFF;
   scrollbar-arrow-color:  #FFF;
}

.ReactTable .rt-tbody {
   scrollbar-width: none;
}

.ReactTable .rt-thead::-webkit-scrollbar {
  background: transparent;
}

for me only this adding this class worked like charm
.ReactTable .rt-tbody .rt-td{
margin-left: 0;
}

@zemagnifique Your css rules worked until I realized clicking the headers for filtering multiple times in a row causes the top black line above the header to flicker. Pretty strange side effect. Do you have any idea how to fix this/why it is happening?

@willbee28 it's been working for me for a year plus with that CSS. I'm not able to reproduce the issue. Can you provide steps to reproduce or a jsfiddle?

@zemagnifique   Turns out it was a problem with one of my css rules. Using a different font causes you the need to add more padding than the default for the headers. Thanks anyway!

To hide the scrollbar in the header in firefox, you can use scrollbar-width: none;.

To hide the header scrollbar in firefox, you can use scrollbar-color: transparent transparent;


Issue pasting new file name when saving file to a directory

I have been having an issue pasting file names as I save my documents. Is this a issue for anyone else?

Hi @vsteve - assuming you're on macOS, the known issue is here as mentioned below.
For future issues, please completely fill out the issue template and if you have general questions about Atom, our message board is a great place to have those conversations:
https://discuss.atom.io/

Thanks for taking the time to contribute!
We noticed that this is a duplicate of https://github.com/atom/atom/issues/14145. You may want to subscribe there for updates.
Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


Fix getInOnlyTemplate in SpringRabbitMQProducer.java

Description
getInOnlyTemplate is checking if inOutTemplate is null to determine whether or not it should initialize inOnlyTemplate.  It should check inOnlyTemplate.  This change fixes that.
Target

[ X ] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ N/A ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[ X ] I checked that each commit in the pull request has a meaningful subject line and body.

[ X ] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

This needs to be backporte on 4.4.x too and maybe in 4.0.x

/component-tests spring-rabbitmq


ENH: Simplify return names in stats.theil/siegelslopes (and fix bug where mstats.siegelslopes was ignoring the method parameter)

Reference issue

N/A -- this is a follow-up on https://github.com/scipy/scipy/pull/16167.
What does this implement/fix?

This simplifies the naming of the return values from stats.theilslopes and stats.siegelslopes. In particular

medslope -> slope
medintercept -> intercept
lo_slope -> low_slope
up_slope -> high_slope

These were not exposed prior to https://github.com/scipy/scipy/pull/16167, so there is no loss of backwards compatibility.
This also fixes a minor bug where stats.mstats.siegelslopes was accidentally ignoring the method parameter.
Before:
>>> x = [1, 2, 3, 4, 5, 6]
>>> y = [2, 7, 3, -4, 2, 5]
>>> from scipy.stats import siegelslopes
>>> siegelslopes(y,x)
SiegelslopesResult(medslope=-0.25, medintercept=3.5)
>>> siegelslopes(y,x,method='separate')
SiegelslopesResult(medslope=-0.25, medintercept=3.0)
>>>
>>> from scipy.stats.mstats import siegelslopes
>>> siegelslopes(y,x)
SiegelslopesResult(medslope=-0.25, medintercept=3.5)
>>> siegelslopes(y,x,method='separate')  # does not match stats version
SiegelslopesResult(medslope=-0.25, medintercept=3.5)

After:
>>> x = [1, 2, 3, 4, 5, 6]
>>> y = [2, 7, 3, -4, 2, 5]
>>> from scipy.stats import siegelslopes
>>> siegelslopes(y,x)
SiegelslopesResult(slope=-0.25, intercept=3.5)
>>> siegelslopes(y,x,method='separate')
SiegelslopesResult(slope=-0.25, intercept=3.0)
>>>
>>> from scipy.stats.mstats import siegelslopes
>>> siegelslopes(y,x)
SiegelslopesResult(slope=-0.25, intercept=3.5)
>>> siegelslopes(y,x,method='separate')  # now matches stats version
SiegelslopesResult(slope=-0.25, intercept=3.0)

The mstats.stats.siegelslopes documentation also had a very slight wording difference in the "See Also" section compared to the stats.siegelslopes version.
Additional information

Probably all stats.mstats method should have a test to check that they have the same results as the underlying stats methods when no masking occurs, but I'm not sure that the valid optional parameter values are easily available in the automated test suites.

@mdhaber @tupui This is the relevant follow-up to https://github.com/scipy/scipy/pull/16167.
I've chosen low_slope and high_slope instead of low and high to avoid ambiguity on whether the confidence interval refers to the slope or intercept, but feel free to override if you see fit.

The whole new result class is probably worth a note in the release note to ask users to prefer using the names instead of relying on the unpacking.


Can TagUI not exit on error (for example element not found)?

from user's query in issue #148

Full details at #148, but below is the conclusion and workaround if user really really wants that.

It is bad automation program to not quit on error. If you really really want that, you can modify tagui_parse.php, search and replace '.exit()' with blank '' and it may be able to make program not quit on exit. For the current version, there should be 8 replacements of '.exit()' to blank ''.
But I wont adjust the TagUI default code base to support something like that. Because it will just lead to more badly designed automation scripts by users.
Also, you can use functions such as present(), visible() which can be used for web elements or sikuli visual automation to detect if an element is on the screen. So it should be able to be handled by good automation program design instead of relying on not exiting when error is encountered -
https://github.com/kelaberetiv/TagUI#helper-functions
https://github.com/kelaberetiv/TagUI#visual-automation
Below sample automation script shows after making above replacement, TagUI does not exit on error.
sample
https://google.com
click test_error_element
type q as testing[enter]
wait 5 seconds
click test_error2_element
click test_error3_element
echo 'end of test'

tagui sample chrome
START - automation started - Thu Jul 26 2018 22:36:19 GMT+0800 (+08)
https://google.com - Google

click test_error_element
ERROR - cannot find test_error_element
type q as testing[enter]
wait 5 seconds
click test_error2_element
ERROR - cannot find test_error2_element
click test_error3_element
ERROR - cannot find test_error3_element
end of test

https://www.google.com/search?source=hp&ei=Y9xZW6OqIYfWvgTZwomYDQ&q=testing&oq=testing&gs_l=psy-ab.12..0i131k1j0l9.13427.14059.0.145<IP_ADDRESS>.<IP_ADDRESS>.3<IP_ADDRESS>....0...1c..64.psy-ab..0.7.310....0.axPdS6U6ZBI - testing - Google Search
FINISH - automation finished - 48.6s

fyi @adegard @Aussiroth @lohvht @alvinphee @chiotkk - if you ever encounter a situation where really need TagUI not to quit on error encountered, there is a workaround above.
But not recommended, because it can easily encourage bad automation script design..

Hi @kensoh thanks for your suggestion but I prefer checking the presence of selector, because I don't now what are the consequences if code continue without control!!
thanks ;-)
if present(element_selector)
{
//doing stuff
}


rsync errors when starting sbt-1.3.0

steps

upgrade sbt to version: 1.3.0 (on version 1.2.8 everything is OK)
start sbt in any project (tested on 2 different projects)

problem
SBT prints this in console when starting:
rsync: chgrp "/home/vasya/.sbt/preloaded/." failed: Invalid argument (22)
rsync: chgrp "/home/vasya/.sbt/preloaded/com" failed: Invalid argument (22)
rsync: chgrp "/home/vasya/.sbt/preloaded/com/eed3si9n" failed: Invalid argument (22)
rsync: chgrp "/home/vasya/.sbt/preloaded/com/eed3si9n/gigahorse-core_2.12" failed: Invalid argument (22)
... about 100-200 lines like that ...
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1189) [sender=3.1.3]
[info] Loading settings for project global-plugins from plugins.sbt,idea.sbt ...
[info] Loading global plugins from /home/vasya/.sbt/1.0/plugins
[info] Loading settings for project ***** from plugins.sbt ...

Then it starts seemingly normally. test:compile works, for example. Maybe it wouldn't work if I wouldn't have ~/.sbt/preloaded already present though.
expectation
same behavior as on 1.2.8, e.g. no problems.
notes
java version is java-8-openjdk, OS is ArchLinux.
sbt is used from the official Arch repos:
https://www.archlinux.org/packages/community/any/sbt/
https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/sbt

@vn971 Thanks for the report! I think it worked ok on Ubuntu, so is there something I did weird that's making Arch mad?
Side note. The layout of the preloaded changed to Maven in sbt 1.3.0 because of https://github.com/sbt/sbt/issues/4661.

Google says https://serverfault.com/questions/213647/rsync-fails-to-backup-some-files-giving-error-22. Is there FAT32 or NTFS involved?

@eed3si9n nope, certainly no FAT32 or NTFS... Just the usual ext4.

The bug apparently happens because SBT is invoked in a user namespace (on my system). Having that in mind, maybe we can understand more on why the bug happens? Where does this rsync happen? Maybe I can help. I tried to search: https://github.com/sbt/sbt/search?q=rsync&type=Issues  but no results in code.

Before 1.3.0 it worked fine in a user namespace, so it certainly sounds like something fix-able to me. (And it still works fine if I just use the later version for now.)

Forgot to reply on this. Currently bash scripts are in https://github.com/sbt/sbt-launcher-package.
See https://github.com/sbt/sbt-launcher-package/pull/315

@eed3si9n thanks! I possibly found the reason. SBT does this command internally:
rsync -a --ignore-existing "$source_preloaded" "$target_preloaded" || true

rsync expands the -a flag to -rlptgoD. The -o flag (meaning --owner) is what makes it break in a user namespace. Can we maybe remove the flag -o and thus write rsync -rlptgD? This would allow the tool to work inside a user namespace, if I understand things correctly.
Thoughts?

Sounds good to me.

Here's my PR for this - https://github.com/sbt/sbt-launcher-package/pull/316

Thanks! This should work I think. Especially dropping all unnecessary flags, keeping only the minimum required. Awesome.

Confirming that the fix works! :tada:
sbt-1.3.6 starts up and runs without any warnings.

Awesome. Thanks for the confirmation.


Update Greengrass Hello World examples

Issue #, if available:
Description of changes:

Greengrass Hello World NodeJS

Migrate to Node8
Add Greengrass Core SDK v1.4.0

Greengrass Hello World Python

Migrate to Python3.7
Update Greengrass Core SDK v1.4.0
Remove Greengrass Commons and Greengrass IPC SDK, because these should be provided by Greengrass Core.

Description of how you validated changes:
End-to-end test with Greengrass v1.9.3.
Checklist:

[ ] Write/update tests
[ ] make pr passes
[ ] Update documentation
[ ] Verify transformed template deploys and application functions as expected
[ ] Add/update example to examples/2016-10-31

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1191   +/-   ##
=======================================
  Coverage   94.36%   94.36%
=======================================
  Files          71       71
  Lines        3621     3621
  Branches      713      713
=======================================
  Hits         3417     3417
  Misses        104      104
  Partials      100      100

Continue to review full report at Codecov.

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


Deptry should detect missing dependencies in tests/

As of now, deptry simply ignores eveything under tests/. This means that imports that are used but not present will be noticed only at execution time, not before.
For instance, suppose I have a tests/test_sending_request.py with the following content:
import httpretty

def test_sending_request():
    with httpretty.enabled():
        # do stuff
        pass

If httpretty is not included in the dev-dependencies, my test would crash with ModuleNotFoundError, even if I used deptry. Given that deptry can detect exactly this kind of issue for normal dependencies, I would love to see that extended to tests/ and, possibly, other folders as well.

The part regarding possibly, other folders as well is explained in a bit more detail in #300.

This would be a nice feature, but it does require us to rethink and redesign the way deptry handles development dependencies. Right now, all development dependencies are placed together in one list, see here. However, if we want to support the functionality mentioned here, we would need to ;

Extract development dependencies as groups (This project has the groups dev and docs)
Map which group of development dependencies should be mapped to which directory. e.g. the group dev should be considered for the tests directory, but the group docs should not.

For point (1) this is already a bit complicated, since deptry supports Poetry, PDM, PEP-621, and requirement.txt.

For Poetry, we can simply extract the different groups, although before Poetry 1.2.x, there was no way to group development dependencies (see the docs.
For requirements.txt, I think we can allow the user to pass a dict as arguments {'dev' : 'requirements-dev.txt', 'docs' : 'requirements-docs.txt'}.
For PEP-621, there does not seem to be a standardized way to list or group development dependencies, see here.
The documentation for PDM, also does not seem to include a method to group development dependencies.

So with the lack of standardization, I am a bit hesitant to incorporate this. Maybe I am over-complicating this or overlooking something. Please let me know if you have any feedback or thoughts on the above!

I understand your hesitation here. However, I think much can be gained by using a less complex approach. If deptry continues to place all development dependencies in a single list, it could nonetheless check if a dependency used in tests/ is part of that single list.
This approach would cover a huge use case of simple projects with only prod- and dev-dependencies. It would allow to cover the use case in #300. It would not cover the advanced use cases you presented, but these are not supported as of now neither. So, in a nutshell: Some additional use cases would be supported without, presumably, too much effort.
However, I would totally understand if you would prefer not to implement something that does not cover all use cases.

I think your suggestion makes sense. If we were go with the approach you mention, I think we should add a fifth check (next to the four existing checks that deptry scans for; missing development dependency.
In addition to adding the check, we would also need to enable the user to configure directories that use development dependencies, such as scripts and tests. Then, deptry should ignore these directories for the four existing checks, but use it for the fifth check.
Then the remaining question is; is the check 'missing development dependency' worth the (small) additional complexity in the code and configuration? Wouldn't missing development dependency in general already caught be CI/CD pipelines trying to run unit tests? For regular dependencies, finding obsolete ones was originally the main purpose, since those do not raise errors, and also finding missing dependencies was just a nice additional result. But for development dependencies the obsoleteness-check is not possible.

P.S. Sorry for my slow responses!

You are totally right, missing dependencies used in unit tests should be noticed when running the tests. However, if deptry would cover that, missing dependencies could be caught by a pre-commit hook or even by a LSP compatible IDE. This would move the check into the developers direct workflow, which might be a nice thing. At least I would welcome that.
However, the most value of a tests check would come from supporting #300. After having very fine-granular dependencies for some time, I am back to lumping everything into group.dev.dependencies if it is not relevant for production. As you mentioned, having Python files in scripts/ being dependencies-checked would be very helpful, because these are not part of the test suite usually.

That makes sense! I personally have no time to work on this at the moment, might pick it up in the future if it remains open. In the meantime, if anyone feels like this is something they want to implement I'd be happy to assist or review PR's.

One idea, now that PEP 735 is a thing, is to have a special case to handle the tests folder, and look for a special dep group in  [dependency-groups] called tests specifically, rather than lumping in all the dev deps together. I suspect some further thought is needed around the wisdom of this.


Deployment on MCU

Hi @Flora233333 , I've read your paper, what a wonderful project!
Btw, I am doing my thesis and would like to ask if you are currently continuing to develop this topic to deploy on MCU like STM32. If so, I would like to be involved and cooperate with you.
BRs,

Hello @trieu1162000 ,
Thanks for your interest in my project !
This project is designed to run on Linux-based development boards (Cortex-A series + NPU), such as Jetson. Software architecture based on Torch and OpenCV.
In the short term, I have no plans to deploy it on MCU like STM32.
In my opinion, deploying on MCU would be more suitable with architectures like the NXP MCXN947 (MCU + NPU), as they provide better support for neural network inference.
Additionally, deploying this project to MCU would require rewriting many OpenCV-based image processing code.


Merging PR 35546 to SB3.

Merging

Revert "Merging"

This reverts commit ade79320f3fc6fc4ef9367f2d4c1d74795d69c4d.

Exposing diagnostic threshold's at the client level in Spring SDK.

Revert "Revert "Merging""

This reverts commit 6bab94ee75af52ca82e6966c486f606623507910.

Updating changelog.

Removing unused import.

Adding defaults to application.properties

Fixing copy/paste error in code.

Fixing PR comments.

Fixing PR comments.

Fixing PR comments.

Adding test case.

Adding javaagent sample to readme.

Updating readme wording.

Removing unused imports.

Fixing bad merge resolution.

Update sdk/spring/azure-spring-data-cosmos/CHANGELOG.md

Changing wording.

Update sdk/spring/azure-spring-data-cosmos/README.md

Wording change.

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-spring-data-cosmos

/azp run java - spring - tests


Freeze after World Generation is Finished

debug.log : https://gist.githubusercontent.com/Rongmario/3d499033c70762c5f53ba57ba95cef9c/raw/a8ab1463bccae9539cad38a63aac2f1bb40b5813/gistfile1.txt
latest.log:
https://gist.githubusercontent.com/Rongmario/fe1d9ff586e0d7af8b555e6b29943310/raw/21840a429c1b1679f4896b8f9582c3d8ef68fc4c/gistfile1.txt

Mixin didn't load, probably didn't include something needed for it in compilation.


Add toLowerCase to fixMac

DylanPiercey/local-devices currently requires the MAC address to be lowercase. By adding .toLowerCase() to the end of the fixMac return we mitigate this issue.

Good addition, thanks!


Enhancements

[x]  Fix COPASI results file for the latest version
[x]  Fix nested structure in COPASI simulator (BIOMD0000000297.omex)

Fixing tests...


Add once() method to Listenable event interface

This implementation is essential to ensure compatibility with the existing usage of once from the previous event library.

Do we really need once()? If not, there is value to keeping the Listenable interface as it is. If we add once(), then all implementers (and composers) of Listenable forever after have another function to write/test.
The behavior given by once() is easily implementable by the user without once().
The following code
events.once("event", () => { /* ... */ });

is equivalent to
const off = events.on("event", () => { off(); /* ... */ });

Before we add something like once(), I'd like to understand the customer need. Once the customer is aware of the above pattern, it seems purely a matter of convenience, and not a prohibitive gap in the API. The convenience seems slight to me; the small upside should be weighed against the downside of having a larger interface and having multiple ways to do the same thing. However, there may be patterns we're not anticipating which make the available method cumbersome (and I'd love to know about them!).

Do we really need once()? If not, there is value to keeping the Listenable interface as it is. If we add once(), then all implementers (and composers) of Listenable forever after have another function to write/test.
The behavior given by once() is easily implementable by the user without once().
The following code
events.once("event", () => { /* ... */ });

is equivalent to
const off = events.on("event", () => { off(); /* ... */ });

Before we add something like once(), I'd like to understand the customer need. Once the customer is aware of the above pattern, it seems purely a matter of convenience, and not a prohibitive gap in the API. The convenience seems slight to me; the small upside should be weighed against the downside of having a larger interface and having multiple ways to do the same thing. However, there may be patterns we're not anticipating which make the available method cumbersome (and I'd love to know about them!).

The motivation for implementing once() was to support existing usage patterns observed across packages. Since at least one implementation exists in every package, I thought it would best to consolidate this pattern.


Location of SCDPBundleInstall.exe

It seems that the file is moved to [SERVICE_VOLUME]:\AosService\PackagesLocalDirectory\Bin\SCDPBundleInstall.exe
(Ref: PU15)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 66b4c899-c7e0-0406-0d39-d32fc41b6104
Version Independent ID: 5d015069-177d-e33c-094c-257df088a7c0
Content: Install metadata hotfixes in development environments - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/dev-itpro/migration-upgrade/install-metadata-hotfix-package.md
Service: dynamics-ax-platform
GitHub Login: @RobinARH
Microsoft Alias: robadawy

Thanks for the feedback! I will update the topic to reflect that the file is now in the Bin folder. These changes should be live later today.


Update theme override doc

Description
Add more detailed DOC about theme override
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] I updated the documentation (see here)
[x] I agree that this code will be published under the MIT license

@cavasinf you write "add more detailed doc" but the PR includes only the adapted scss file.
Can you share more details? Because I do not get it. Is this your set of fixes for Tabler? What does it do?

I've just added more scss color override like light backgrounds, border colorsandtext colors`.
They were not overridden by variables colors of Tabler's default css.
I mean doc because it is not used by the Bundle. It's just an example if devs want to change default Tabler's colors.

Okay then 😄


Check implementation of GTR1MDF D and lambda functions

Currently GTR1MDF fails Weak White Furnace test with result 0.5
Check implementation of the formulas from  https://docs.chaosgroup.com/download/attachments/7147732/gtr_shadowing.pdf?version=2&modificationDate=1434539612000&api=v2

Fixed in 71036823e764ace444345265afaa5da1d552b038


nvme-tcp support

What this PR does / why we need it:
nvme tcp support in nbp
Which issue this PR fixes* *(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
None
Special notes for your reviewer:
vendor code of opensds connector should be updated with latest hotpot development

/retest

LGTM


Fork Rainbow.me wallet

Overview:

Fork Rainbow.me wallet https://github.com/rainbow-me/rainbow
Add media player to play Video/Music NFTs using any opensource media player
Add feature to post NFT to instagram
Add feature to Airplay NFT to smart tv

contact<EMAIL_ADDRESS>or @fourtwentytiesto on telegram if you have any questions

@gitcoinbot @420tiesto I am still working on the issue. I will submit a WIP PR post install. Thanks!

@gitcoinbot, still working.

@gitcoinbot, still working.

@gitcoinbot, thanks + still working, should have an update by end of the weekend.

Still working @gitcoinbot. https://github.com/loganbek/rainbow.

@gitcoinbot, Still working.

I'm still working @gitcoinbot, will have an update for you shortly.


Will we have a Dictionary release today?

Folks, as mentioned in the Read Me file, the dictionaries should be released on the first day of each month. As such, I want to know if the first release will be made available today. If so, I suggest that the Read Me file also describe what NVDA users should do in order to use hyphenated words in ENUmain.dic. A setting should be altered in NVDA's Punctuation/Symbol Pronunciation dialog.

Yes, a release will be made today, sorry, we were both doing other things. I'll manage this, and update readme as described.


Update PullApprove configuration

Rename the PullApprove configuration. Modify PullApprove conditions and add unmet status explanations.

Reassigned reviewer as @manuerumx  is out for the week.


Fix typo

Codecov Report

Merging #65 (f90577d) into main (2cfe126) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #65   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            8         8
  Lines          502       502
=========================================
  Hits           502       502

Continue to review full report at Codecov.

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


feat: Table widget v2 with support for non-ASCII characters and improved jest coverage

Fixes #10722
Fixes #10497
Fixes #5445
Fixes #13223
Fixes #13648
Fixes #13325
Fixes #9284
Fixes #4183
Fixes #5693
Fixes #11243
Fixes #11403

if no issue exists, please create an issue and ask the maintainers about this first

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions, so we can reproduce.
Please also list any relevant details for your test configuration.

Test A
Test B

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

@sbalaji1192

Sniping mode creates Table 1 on canvas (Need info on what should be the behaviour here)

SelectedRows populate data without enabling multi-select — first row is populated (Bind {{Table_v2_new.selectedRows}} to text widget and do not enable multi-select, still the row data is coming)

{{currentRow. }} is giving weird autosuggestions

Clicking on field give suggestion for {{currentRow.ColumnName}}

{{currentRow['']}} — auto suggestion do not work

Disable button on table widget select and unselect the row https://www.loom.com/share/d901cf5621474bcb983f8ab303f6e535

By default button/menu/icon colour property is blank

App crash on using {{Query1.data[0].name}} in Default search text

Testing is in progress...

1st row is selected by default even after clearing the default selected row property

After search result the row is getting selected
https://www.loom.com/share/c9dd3e33790c427bb2e903652b43d27f

@ashit-rath you may wanna exclude below files as they have been copied from v1
TableWidgetV2/component/CascadeFields.tsx
TableWidgetV2/component/CommonUtilities.test.ts
TableWidgetV2/component/CommonUtilities.ts
TableWidgetV2/component/Constants.test.ts
TableWidgetV2/component/Constants.ts
TableWidgetV2/component/index.tsx
TableWidgetV2/component/Table.tsx
TableWidgetV2/component/TableAction.tsx
TableWidgetV2/component/TableActionIcon.tsx
TableWidgetV2/component/TableDataDownload.tsx
TableWidgetV2/component/TableFilterPane.tsx
TableWidgetV2/component/TableFilterPaneContent.tsx
TableWidgetV2/component/TableFilters.tsx
TableWidgetV2/component/TableHeader.tsx
TableWidgetV2/component/TablePagination.tsx```

/ok-to-test sha=23049b4

/ok-to-test sha=bcdcaaf

:clap:


message toolbar is disappearing when calling UIControllerSheet

Hi @jessesquires
I would like to know if there is any way to prevent hiding input message toolbar from hiding when UIAlert is called
JSQMessagesViewController version: 7.3.4
iOS version: 10 and 8 same thing
Reproducible in the demo project? (Yes)

Anyone had same issue??

I have same issue please let me know if u will find solution.


[BUG FIX] Safe environment configuration

Safe environment configuration
Currently if any of the expected environment variables is omitted from the application.yml file, or if this file doesn't exist at all, the application startup will crash.
This PR suggests changes for ensuring safe loading of the environment configuration even if application.yml is not configured properly or is missing.

Pull Request Test Coverage Report for Build 386

12 of 15 (80.0%)  changed or added relevant lines in 2 files are covered.
696 unchanged lines in 20 files lost coverage.
Overall coverage decreased (-53.7%) to 32.692%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

env/env.go
7
10
70.0%

Files with Coverage Reduction
New Missed Lines
%

api/osb/logic.go
1
97.14%

env/env.go
2
85.48%

api/info/info_controller.go
3
75.0%

rest/interfaces.go
4
0.0%

types/credentials.go
8
0.0%

rest/util.go
11
38.89%

types/broker.go
12
0.0%

types/platform.go
12
0.0%

util/util.go
15
0.0%

api/common/common.go
16
40.74%

Totals

Change from base Build 366:
-53.7%

Covered Lines:
425

Relevant Lines:
1300

💛  - Coveralls

https://github.com/Peripli/service-manager/pull/71 reworks the environment and the file check added here might be obsolete

Not relevant anymore


should make the package compatible with visual studio 2015 to 2019

Tested on visual studio 2019 only so far

As the extension now asynchronously loads, the menu item may be greyed out in the meantime

@kmpm Do you wish to review the changes on this PR and #20 or can I merge it ?

Looks good to me. Just had a quick glance. Go ahead and merge.


do not raise change until property is selected in animated style

https://github.com/CartoDB/cartodb/commit/c24cac01dc75ac9b54ecdb0474e1a323f796d513


feat: Add headers option

Add support for optional headers field (#22)
Add tests for parsing YAML multiline string

@googlebot I signed it!

@bharathkkb
Thanks for the review! I added integration test and replied to your comments.

Hey @bharathkkb, please wait a little bit with the merge. I think I've found one issue with this change (I've been using my fork for some time in the meantime).
Please take a look at: https://github.com/jakub-bacic/upload-cloud-storage/commit/e96820efa2fa723612c0129f1533b00fe1361fd8

@jakub-bacic sounds good, I rebased this branch. Feel free to push the fixes in when you get a chance.

@googlebot I consent.

@bharathkkb
Done

@googlebot I consent.

@jakub-bacic that does seem odd, I did some digging and it seems like the lib is using a new obj per https://github.com/googleapis/nodejs-storage/blob/160271318a2da9c378e87af6255c50f441ce6893/src/bucket.ts#L3810

@jakub-bacic I was able to repro, added a test to make sure its WAI. I'll try to make a standalone repro and open an issue on the upstream pkg.


fix dead code in UpdateFromProto

Removes an additional condition that is not required.

@wally-the-cartographer merge

Merge requested by authorized user wohe. Merge queue now has a length of 1.


accident F5 refresh clears all my undo/redo options

Please remove F5 shortcut key from brackets as it reloads and clear all undo/redo options entirely. I usually use chrome and brackets together to check every changes by pressing F5. And whenerver I press F5 from brackets, it simply clears all my undo/redo options.
It would be better using another shortcut for reloading brackets
Thanks Brackets Team

You might like my brackets-persistent-history-extension, which saves your editing history between changing projects and closing/reloading Brackets.
Note that the extension is still quite alpha as I haven't had much time to improve it lately, but I have been using it since I made it with small / negliable issues). Contributions to improve it are of course welcome!

This is by design in brackets. But if you like to override it,
goto debug>open user key map file add the following in the json file
"overrides": {
"F5" : ""
}

Closing as designed, and user override already available.

thanks petent and abose for your valuable comments :+1: . I have override using keymap file. It works perfectly well now.
Thanks again :)

I guess that's worst design idea that i've ever met in my IDE experience


feature/LocalDataBase Dao and Repository

TL;DR

close #39

Why we need this change? (required)
Access to DataBase
What does this change? (required)
Create Dao and Repository
What is the value of this and can you measure success? (required)
Can use test data and regist data

If you are OK, please approve this PR.
If anyone approve this PR, I'll merge this PR myself.

ThankYou for your review!!!


Update definition of geogenic.
Add disjoints (biogenic<>fossil; renewable<>conventional; biofuel<>fossil combustion fuel).
Add alternative term biogenic combustion fuel to biofuel.

In my opinion, everything looks good.

@stap-m : Does it now also look good for you? If so, please approve.


Support manually adding Google Service files without using flutterfire configure

If you try and manually add google service config files to your android and iOS project (i.e. not using flutterfire configure), it tries to call optionsFromResouce(). This behaviour needs to change to account for users who have not used the FlutterFire CLI. The condition for this line needs to change:
https://github.com/firebase/flutterfire/blob/ea03c6b349ccd63317f96e37c85daf7e11f2a28a/packages/firebase_core/firebase_core_platform_interface/lib/src/method_channel/method_channel_firebase.dart#L89

I don't think this is a problem anymore, at least, I couldn't recreate it.


Installation?

Hi, how can I instal this on my VPS?

There is nothing to install. This is just a list of resources.


Extend the tokenizer on another language

Hi, How could I extend tokenizer of llama3 with my custom dataset on my language?

Have you tried using the BPE property of some tokenizers? Extending it will make training much more complex

Yes. Now I found llama3 tokenizer supported well on my language


Storybook 8 upgrade

Is your feature request related to a problem? Please describe.
When starting up storybook 8 it states this Addon is out of date.
Describe the solution you'd like
It still works though so I'm guessing just need a version release to appease storybook?
Describe alternatives you've considered
Design types

[ ] figma
[ ] figspec
[ ] link
[ ] image
[ ] iframe

Additional context
This is the warning I get.

Your addon is not listed on https://github.com/storybookjs/storybook/issues/26031 though.

Thanks. I'm attempting to fix this in #232, but I'm doing quite a big refactor so it would be helpful if you could test the canary release out to ensure that I haven't broken anything in the process. The refactor shouldn't be noticeable to users.
At the time of writing the canary version is<EMAIL_ADDRESS>but you can always check the PR description for the most up-to-date version.

Here are my tests

Installation on fresh Storybook 8 beta 👍
Setting params in story

Error:


Doesn't work on Godot 4.0.2

Looks like script can't parse key, I entered it in gui, but there are errors on request
SCRIPT ERROR: Invalid get index 'choices' (on base: 'Dictionary').
          at: _on_request_completed (res://addons/GPTIntegration/GPTIntegration.gd:160)
{ "error": { "message": "You didn\'t provide an API key. You need to provide your API key in an Authorization header using Bearer auth (i.e. Authorization: Bearer YOUR_KEY), or as the password field (with blank username) if you\'re accessing the API from your browser and are prompted for a username and password. You can obtain an API key from https://platform.openai.com/account/api-keys.", "type": "invalid_request_error", "param": <null>, "code": <null> } }

Fixed in latest push.
Thank you for the ticket!

It isn't fixed, I'm currently getting this same error. Printing out the headers array inside call_GPT shows it doesn't append the api key to the Authorization header. I was able to fix this by moving the headers array into call_GPT:
`func call_GPT(prompt):
var headers = ["Content-Type: application/json","Authorization: Bearer " + api_key]
var body = JSON.new().stringify({
	"prompt": prompt,
	"temperature": temperature,
	"max_tokens": max_tokens,
	"model": "text-davinci-003"
})

(...)
`

It isn't fixed, I'm currently getting this same error. Printing out the headers array inside call_GPT shows it doesn't append the api key to the Authorization header. I was able to fix this by moving the headers array into call_GPT:
`func call_GPT(prompt):
var headers = ["Content-Type: application/json","Authorization: Bearer " + api_key]
var body = JSON.new().stringify({
	"prompt": prompt,
	"temperature": temperature,
	"max_tokens": max_tokens,
	"model": "text-davinci-003"
})

(...) `

This is what i have in the current release:

it "should" be fixed

Ok. For some reason the version in Godot's AssetLib isn't up to date. I'll just clone it directly then, nvm.

I may need to ask them to update it
On Sat, Apr 15, 2023, 3:39 PM Kenneth Rapp @.***> wrote:

Ok. For some reason the version in Godot's AssetLib isn't up to date. I'll
just clone it directly then, nvm.
—
Reply to this email directly, view it on GitHub
https://github.com/finepointcgi/Godot-Open-AI-GPT-Integration/issues/2#issuecomment-1509940695,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC3UWDA65QHUUIGZT6BQD7TXBL2O7ANCNFSM6AAAAAAWY7JCTM
.
You are receiving this because you modified the open/close state.Message
ID: @.***
.com>


Navigation items change order as you change sections - they shouldn't

I don't think the navigation should swap order when you click on a section.
I tend to agree with the old-fashioned UI rule that things shouldn't move — and people are pretty used to expanding menus.

This is one @gauntface and I disagree on, I prefer that they remain in a consistent order, he prefers the change.  CAGE FIGHT.
@gauntface - what are your reasons for keeping it as is?

If thats what you want then fine.
I question how often users will jump between sections and I hate the idea of putting a set of highlevel navigation above the title of the current section.
BUT if you want it can change.

Let's leave as is for now, keep this bug open, and ask the material folks when they do the review @addyosmani asked them to do.

I opened a dupe on the topic. Here's my text from the dupe:
The new nav menu seems unconventional (in terms of UX).

Clicking on Showcase in the screenshot above effectively transports the user to the Showcase section of the site. With Showcase in place of Web Fundamentals and the top-level Showcase documents listed beneath.
Pure first impression: As a user I was lost for a couple of seconds. I've never seen a nav UI like this. It took (literally) a couple seconds for me to understand what was going on.
An accordion-style nav menu seems more conventional to me.
I think the current UI could work, if the site provides a little more visual feedback. Take the screenshot above again for example. When I click on Showcase, some sort of animation that replaces the Web Fundamentals link, and then populates the list with the Showcase pages, and then moves Web Fundamentals down to the bottom of the nav, would probably be sufficient for me to understand what just happened.
LMK if that all makes sense :+1:

:+1: to the UI rule that "things shouldn't move"

Ok will change. Thanks for feedback.
On Thu, 24 Sep 2015 at 23:19 Kayce Basques<EMAIL_ADDRESS>wrote:

[image: :+1:] to the UI rule that "things shouldn't move"
—
Reply to this email directly or view it on GitHub
https://github.com/google/WebFundamentals/issues/1842#issuecomment-143064819
.

I've made this change.
@petele @kaycebasques @samdutton thoughts on this change?


Stylesheets loaded in backwards order with docker mods

Describe the bug
Since the change to docker mods to load the stylesheets under <body> instead of <head>, the sheets are being loaded in the opposite order from what they previously were.  This is causing my custom theme to break because the variables it defines are being overridden by values in the base.css file.
Theme Install Method docker mods

Docker run / Compose Config

Sonarr log example
[mod-init] Attempting to run Docker Modification Logic
[mod-init] Adding gilbn/theme.park:sonarr to container
[mod-init] Downloading gilbn/theme.park:sonarr from registry-1.docker.io
[mod-init] Installing gilbn/theme.park:sonarr
[mod-init] gilbn/theme.park:sonarr applied to container
[migrations] started
[migrations] no migrations found
───────────────────────────────────────
      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝
   Brought to you by linuxserver.io
───────────────────────────────────────
To support the app dev(s) visit:
Sonarr: https://sonarr.tv/donate
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID:    1000
User GID:    1002
───────────────────────────────────────
---------------------------
|  Sonarr theme.park Mod  |
---------------------------
Variables set:
'TP_DOMAIN'=novinha:8080
'TP_COMMUNITY_THEME'=
'TP_SCHEME'=http
'TP_ADDON'=sonarr-calendar
'TP_THEME'=tender
---------------------------
|  Adding the stylesheet  |
---------------------------
Stylesheet set to tender
Added custom addon: sonarr-calendar
[custom-init] No custom files found, skipping...
[Info] Bootstrap: Starting Sonarr - /app/sonarr/bin/Sonarr.exe - Version <IP_ADDRESS>7
[Info] AppFolderInfo: Data directory is being overridden to [/config]
[Info] Router: Application mode: Interactive

Application Info (Don't skip)

Version
Sonarr <IP_ADDRESS>7
Branch
latest
Container
lsio

Additional context
The reason it's loading backwards is because the sed command is replacing an opening tag rather than a closing tag, meaning that the second replacement actually gets inserted before the first one.  I may be able to work around this by judicious use of !important but I haven't tried it yet, and it really feels like the theme file should be loaded after the base file anyway. I'm happy to try to put together a PR, or happy to leave it to someone with more experience in the code base, as you see fit :smile:

Hm. I see. Yeah, sure you can make a PR one the *arr mods that are affected. Make the pr on the develop branch.

new mods built with tag <app>-develop


Error UI state if fetching error

When fetching initial data for the form fails, the error notification must be displayed

Error handling playground: https://jsfiddle.net/skorphil/cbxu10kp/40/

Not sure, but it looks like react-hook-form does not have a built-in mechanism for catching fetching errors. So error handling could be achieved via catching and setting state manually
defaultValues: async () => {
      try {
        await getLatestRecord();
      } catch (error) {
        console.log("defaultValues error:", error); // setState here
      }
    },

Created a new react Component, which takes error message as a prop.
It displayed based on errorState in RecordForm
https://github.com/skorphil/nextjs-form/assets/6762009/952ec7ae-6c3c-499e-b940-d722e7d7651d

There is a bug - default values not receiving values after await
defaultValues: async () => {
      try {
        await getLatestRecord();
      } catch (error) {
        setErrorState(error.stack);
      }
    },

Probably can be done with useEffect:
useEffect(() => {
  const fetchData = async () => {
    try {
      const data = await getLatestRecord();
      setLatestRecord(data);
    } catch (error) {
      setErrorState(error.stack); // Handle errors appropriately
    }
  };

  fetchData();
}, []);

But what the point in defaultValues compatible with promises?

Ah, that is

There is a bug - default values not receiving values after await
defaultValues: async () => {
      try {
        await getLatestRecord();
      } catch (error) {
        setErrorState(error.stack);
      }
    },

only this works:
defaultValues: async () => getLatestRecord();

so how to cath errors?

ah, i just did not returned the walue - that was a problem
defaultValues: async () => {
      try {
        const initialValues = await getLatestRecord();
        return initialValues; // here
      } catch (error) {
        setErrorState(error.stack);
      }
    },


MTL-2092 Use the newer 23.1 cloud-init

Summary and Scope

Fixes: MTL-2092
Requires:
Relates to:

Issue Type

Bugfix Pull Request
RFE Pull Request

Our fork now builds 23.1 with our custom cloud-init code. This upgrades us from 21.4 to 23.1, which will appease some of our CVE scans while providing some newer/modern functions.
Prerequisites

[ ] I have included documentation in my PR (or it is not required)
[ ] I have tested this by building an image using this branch HEAD, or this is does not pertain to the node-images pipeline.
[ ] I tested this on internal system or this pertains to the node-images pipeline (if yes and not build related, please include results or a description of the test)
[ ] I tested this on a vshasta system or this pertains to the node-images pipeline (if yes and not build related, please include results or a description of the test)

Idempotency

Risks and Mitigations

This is a draft while images are built and tested.
We had issues with cloud-init-22, which didn't like our underscores. We fixed those, but we need to do the same validation with cloud-init-23.


Add support to AWS and GCP to get standard out

Also modified spark benchmark to demonstrate the features.
@ehankland, PTAL.  @pmkc, you may also be interested.

Currently adding the system-reported time the operations take, so you might want to wait on your views until that change is in.

SGTM

Output of the benchmark now includes the wall_time, the run time, and the pending time, where the runtime and pending time as reported by the platform.
SPARK:
  class="org.apache.spark.examples.SparkPi" jarfile="file:///usr/lib/spark/lib/spark-examples.jar" job_arguments="[]" machine_type="None" num_workers="4" print_stdout="True" spark_cluster_id="foo" spark_service="dataproc"
  wall_time                            29.074358 seconds
  runtime                              16.781000 seconds
  pending_time                          9.554000 seconds
  End to End Runtime                   29.079056 seconds

@ehankland, PTAL.

@ehankland, Added support for subnets on AWS, which are needed for m4 machine types.

LGTM


Configure GitHub Social Preview Image

Background

GitHub introduced a new feature to customize a preview image on social sharing.

References

https://github.blog/changelog/2019-04-16-repository-social-media-image/

Resolved