iOS - sqlite3_total_changes EXC_BAD_ACCESS

I am just trying to port my app to iOS. on Android everything works fine
i am using<EMAIL_ADDRESS>(I also tried 2.9.13) - iOs 12.1 - capacitor/ios 2.4.7 - capacitor/core 2.4.7 in a Vue project - ionic/vue 5.6.1 - vue 3.0.7
however when starting up and initializing the sqlite database I get the following error in line 167797 sqlite3.c:
return db->nTotalChange;
Thread 2: EXC_BAD_ACCESS (code=1, address=0x78)
could it be a problem with too many threads or too many sqlite connections open?
this should be the code where the error arises:
const initVFGDB = async (): Promise<boolean>  => {
      const db = await sqlite
      .createConnection("vdb", false, "no-encryption", 1);

      let ret = await db.execute(createTablesNoEncryption);
      if (ret.changes.changes < 0) {
          return false;
      }

      ret = await db.execute(importAllAnimals);
      if (ret.changes.changes < 0) {
          return false;
      }

      ret = await db.execute(importAllTypes);
      if (ret.changes.changes < 0) {
          return false;
      }
      return true;
    }

@Snogo Thanks for reporting an issue. Would be better that you move directly to 3.0.0-rc2 and capacitor/core3.0.2. It is fully operational for iOS and Android. It is not yet release at 3.0.0 due to Electron. So if you do not use Electron just use it. I will need to see how you implemented in Ionic/Vue Are you using the vue-sqlite-hook  What is the definition of sqlite in your example

@Snogo Can you provide the database schema createTablesNoEncryption and the importAllAnimals and importAllTypes. Did you try with a smaller number of Animals and types?

@Snogo Any news?

@jepiqueau no. will let you know soon. will first try to port everything to 3.0.0-rc2 and then see

@Snogo move to 3.0.0 or higher

porting it now to 3.1.2-1 (and all other 3+ versions of ionic/core) and got the following error in main.ts
in src/main.ts:66:36

TS2554: Expected 1 arguments, but got 0.
    64 |   retrieveConnection, retrieveAllConnections, closeAllConnections,
    65 |     addUpgradeStatement, importFromJson, isJsonValid,
  > 66 |     copyFromAssets, isAvailable} = **useSQLite**();

can I already use it with the latest vue-sqlite-hook 2.0.2? or respectively do you know the problem here?

@Snogo Delete Android and iOS folder of your app npm i --save-dev vue-sqlite-hook it should be version 2.0.4
then npx cap add android and ios then npx cap copy
and npx cap open it should work
the main.ts file should have
/* SQLite imports */
import { useSQLite } from 'vue-sqlite-hook/dist';
import { useState } from '@/composables/state';

const app = createApp(App)
  .use(IonicVue)
  .use(router);

/* SQLite Global Variables and Hook */
const [jsonListeners, setJsonListeners] = useState(false);
const [isModal, setIsModal] = useState(false);
const [message, setMessage] = useState("");
app.config.globalProperties.$isModalOpen = {isModal: isModal, setIsModal: setIsModal};
app.config.globalProperties.$isJsonListeners = {jsonListeners: jsonListeners, setJsonListeners: setJsonListeners};
app.config.globalProperties.$messageContent = {message: message, setMessage: setMessage};

const onProgressImport = async (progress: string) => {
  if(app.config.globalProperties.$isJsonListeners.jsonListeners.value) {
    if(!app.config.globalProperties.$isModalOpen.isModal.value) app.config.globalProperties.$isModalOpen.setIsModal(true);
    app.config.globalProperties.$messageContent.setMessage(
        app.config.globalProperties.$messageContent.message.value.concat(`${progress}\n`));
  }
}
const onProgressExport = async (progress: string) => {
  if(app.config.globalProperties.$isJsonListeners.jsonListeners.value) {
    if(!app.config.globalProperties.$isModalOpen.isModal.value) app.config.globalProperties.$isModalOpen.setIsModal(true);
    app.config.globalProperties.$messageContent.setMessage(
      app.config.globalProperties.$messageContent.message.value.concat(`${progress}\n`));
  }
}

// SQLite Hook
const {echo, getPlatform, createConnection, closeConnection,
  retrieveConnection, retrieveAllConnections, closeAllConnections,
  isConnection, addUpgradeStatement, importFromJson, isJsonValid,
  isDatabase, getDatabaseList, addSQLiteSuffix, deleteOldDatabases,
  copyFromAssets, checkConnectionsConsistency, removeListeners,
  isSecretStored, setEncryptionSecret, changeEncryptionSecret,isAvailable} = useSQLite({
    onProgressImport,
    onProgressExport
  });

  // Singleton SQLite Hook
  app.config.globalProperties.$sqlite = {echo: echo, getPlatform: getPlatform,
    createConnection: createConnection,
    closeConnection: closeConnection,
    retrieveConnection: retrieveConnection,
    retrieveAllConnections: retrieveAllConnections,
    closeAllConnections: closeAllConnections,
    isConnection: isConnection,
    isDatabase: isDatabase,
    getDatabaseList: getDatabaseList,
    addSQLiteSuffix: addSQLiteSuffix,
    deleteOldDatabases: deleteOldDatabases,
    addUpgradeStatement: addUpgradeStatement,
    importFromJson: importFromJson,
    isJsonValid: isJsonValid,
    copyFromAssets: copyFromAssets,
    checkConnectionsConsistency: checkConnectionsConsistency,
    removeListeners: removeListeners,
    isSecretStored: isSecretStored,
    setEncryptionSecret: setEncryptionSecret,
    changeEncryptionSecret: changeEncryptionSecret,
    isAvailable:isAvailable
  };

  //  Existing Connections Store
  const [existConn, setExistConn] = useState(false);
  app.config.globalProperties.$existingConn = {existConn: existConn, setExistConn: setExistConn};

router.isReady().then(() => {
  app.mount('#app');
});

Listeners have been added
Hope this will help you

@Snogo  Any news from your side? if it works on your side, can you close the issue

@jepiqueau sorry. I was sick last week and will try it hopefully this week. will give you an update then and close the issue

@Snogo Hope you are going better, take your time.

@Snogo Any news?

sorry. still on the backlog of other things which had priority. will do soon and let you know

Dear @jepiqueau . sorry it took so long but with a colleague I know managed to Upgrade the project to Capacitor3 and we have the latest @capacitor-community/sqlite version (3.2.0-2)
we now face the problem however that although I check with different ways if a sqlite-connection exists (with app.config.globalProperties.$existingConn but also with the methods iDBExists() or isConnection())
it always says there is no connection and never retrieves it (with retrieveConnection)  and then the error rises CreateConnection: Connection vdb already exists. - sqlite3 seems to be more sensitive here
do I need to set the existingConn manually or how do i check if there is already a connection and get it?
I have this method:
const getConnection = async(): Promise => {
let db: SQLiteDBConnection;
const {existConn} = app?.appContext.config.globalProperties.$existingConn;
if(!existConn){
db =  await sqlite.createConnection("vdb", false,"no-encryption",1);
}else{
db = await sqlite.retrieveConnection("vdb");
}
return db;
}

@Snogo are you using Live Reload with capacitor ? Can you share your app on github ?

@jepiqueau no but I will send you the clone via email. thank you very much

@Snogo It is quite complex as you spend your time to create the same connection or retrieve it without closing it .
i will create a utils-connection.ts
import { SQLiteDBConnection, SQLiteHook } from "vue-sqlite-hook/dist";
export async function getMyConnection(sqlite: SQLiteHook, dbName: string): Promise<SQLiteDBConnection> {
    try {
        const isConn: any = await sqlite.isConnection(dbName);
        let db: SQLiteDBConnection;
        if(isConn.result) {
            db = await sqlite.retrieveConnection(dbName);
        } else {
            db = await sqlite
                    .createConnection(dbName, false, "no-encryption", 1);
        }
        return Promise.resolve(db);
    } catch (err) {
        return Promise.reject(err);
    }
}
export async function closeMyConnection(sqlite: SQLiteHook, dbName: string): Promise<void> {
    try {
        const isConn: any = await sqlite.isConnection(dbName);
        if(isConn.result) {
            await sqlite.closeConnection(dbName);
        }
        return Promise.resolve();
    } catch (err) {
        return Promise.reject(err);
    }
}

and do something like this  each time you need the connection ( create or retrieve)
        // initialize the connection
        let db: SQLiteDBConnection;
        try {
          db = await getMyConnection(sqlite,"vfgdb");

          console.log("got DB connection");
          const ret = await db.isDBOpen();
            if (!ret.result) {
              // open db vfgdb
              await db.open();
            }
        } catch (err) {
          console.log(`error opening DB ${err}`);
          return false;
        }

you have also to take care with the try ...  catch ie
            try {
              const ret = await db.run(createNewSample, values);
              if(ret.changes != null && ret.changes.lastId != null) {
                const lastId = ret.changes.lastId;
                currentSample.value = addSample(
                  lastId,
                  loggedInUser,
                  cDateTimeformat,
                  "",
                  0,
                  0,
                  0,
                  0,
                  "",
                  "",
                  -1,
                  "",
                  -1,
                  -1,
                  0
                );

i start to modify the code but there are too much work
i will not use at all app.config.globalProperties.$existingConn
you can also simplify in the main.ts
  // Singleton SQLite Hook
  app.config.globalProperties.$sqlite = useSQLite({
    onProgressImport,
    onProgressExport
  });

hope this will help you to find the way

@Snogo Well i thing there is apparently a bug in @ionic/vue and @ionic/vue-router above 5.6.13 which re-execute the previous pages when you leave one page. stick to
    "@ionic/vue": "~5.6.13",
    "@ionic/vue-router": "~5.6.13",

Is that help ?

@Snogo i have tried to modify your app without success It has to do with some logic of the app and the way of using Vue. As you are using only one database i will make a connection once and using it all along the app. The best will be to restart from scratch and have a look to vue-sqlite-app and vue-sqlite-app-starter. I do not thing it is related to the plugin, so there is nothing i can do much to help you sorry for this and good luck.

@Snogo hope you find the way. i close the issue. Fell free to re-opens it if required


Configuration changes

Config variables are in board_defconfig or shield.conf depending on if it's a board or a shield, this could be moved to the top of config folder to be used and manipulated by the editor. config variables to be changed could be defined in info.json to be edited with bool ones changed using switches and int ones changed with a simple number box

Thanks for surfacing this here, I haven't had a need to touch these files yet personally so I'm unaware of their intricacies so far. You mention a couple of files though I'm seeing four in my repo (not counting the split left/right files). In my case it's a board/shield though I couldn't even say if all of those files even do anything or are necessarily recognized by ZMK in their current path. All of this is to explain my hesitation, but maybe these questions would be more helpful for now:

What syntaxes are used in these files? Would they need to be parsed to preserve arbitrary existing configurations or would the expected behaviour involve the editor overwriting files on commit? It sounds like you intend for the latter but I'm seeing more and more friction with trying to make custom JSON schemas for the subset of things that currently make sense in order to spit out actually code during the build (for example, behaviour definitions in the keymap).
Are these config options exhaustively described somewhere? I see mentions of them spread around the ZMK docs but I imagine these are more like typical examples and not necessarily everything someone might want to control (which again raises the question of how to handle configuration the the editor doesn't yet understand without clobbering the user's existing config).

All config options are explained in the root kconfig file in zmk, but I don't think being able to arbitrarily change all of them is necessary. A lot of them are required for the board to function like enabling gpio and so on. I'm viewing it from an integrator/manufacturers standpoint whereby they can define what configuration options make sense for the end user to change and what should be left alone, but they could all be parsed and made available for editing

https://github.com/PolarityWorks/editor-zmk-config/blob/bt65-ANSI/config/boards/arm/bt65/bt65_defconfig
Here's an example defconfig, as you can see a lot of the stuff doesn't need to be played with but things like RGB default settings and backlight power management options definitely can be

I'm going to go ahead and close this but feel free to reopen if you want to continue the discussion.


chore: replace mime with mrmime

Description
This is a package by Luke Edwards to replace mime and mime-db. Difference is not big but already used in sirv.
du -sk dist/node

before: 10784
after: 10748

Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[ ] Read the Contributing Guidelines.
[ ] Read the Pull Request Guidelines and follow the Commit Convention.
[ ] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

FWIW, if using only the mime types available in mime-db's lite version, and if what's only needed is converting back and forth from extensions to mime types, then I think my mime2ext and ext2mime modules should be the smallest available.

Probably but here mrmime already used by sirv.
cc @lukeed


[AWIBOF-6733] Refactor CLI client for SYSTEM commands

Refactor CLI client for SYSTEM commands.
Add some tests.

Looks good to me.


Feat/query params enum

Summary

Checklist

[ ] I understand that this PR may be closed in case there was no previous discussion. (This doesn't apply to typos!)
[ ] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
[ ] I've updated the documentation accordingly.

https://github.com/ItakGol/Skep_Tech.git

git pull origin master

git checkout feat/query-params-enum

git merge master

git push -u origin feat/query-params-enum

httpx/_urls.py

httpx/_utils.py


Problem in values.xml

<attr format="color" name="tint"/>

aapt: Attribute ''tint'' has already been defined
is a problem to this app.

This library uses pre-defined string resources as their default values. So you need to either create strings with different name or have to override the existing one.


How to play video in slow motion for selected intervals

I have run your project(https://github.com/google/grafika) in this project I played a video in slow motion by changing Play video(TextureView) activity's  FixedPlaybackRate value
SpeedControlCallback callback = new SpeedControlCallback();
callback.setFixedPlaybackRate(1);
It had played a whole video slowly. what I actually need is have to play video slowly for selected intervals not the entire video.is it any possible to set the regions(intervals)?.

The existing code doesn't provide a way to do this, but you can modify it to define the intervals and have SpeedControlCallback behave appropriately.


[IOTDB-306] new reader with ChunkMetaData for aggregateFunction

In the old interface, data filtering could not be use the chunk level, which I think may not have been considered in the previous design. Now the IAggregateReader interface has been added hasNextChunk nextChunkMeta hasNextPageInCurrentChunk.
The advantage of this is that Statistics can be used in the AggrFunction, there is no need to read page
This some test, i restart the server after each kind of test:

10,000 data without chunkMeta and unseq
IoTDB> select count(*) from root
It costs 0.290s
IoTDB> select first_value(*) from root
It costs 0.657s
IoTDB> select last_value(*) from root
It costs 0.156s
IoTDB> select sum(*) from root
It costs 0.224s
IoTDB> select avg(*) from root
It costs 0.272s
IoTDB> select max_time(*) from root
It costs 0.117s

10,000 data with chunkMeta but without unseq
IoTDB>  select count(*) from root
It costs 0.006s
IoTDB> select first_value(*) from root
It costs 0.006s
IoTDB> select sum(*) from root
It costs 0.005s
IoTDB> select avg(*) from root
It costs 0.006s
IoTDB> select max_time(*) from root
It costs 0.004s

In short, the performance of aggregate query without value filters is optimized by enabling sequence data skipping at the chunk level whenever possible. To sum up the updated facilities:

Aggregate Readers

IAggregateReader: add three interface methods

hasNextChunk
nextChunkMeta
hasNextPageInCurrentChunk

Readers which implement IAggregateReader are thus updated:

MemChunkReader
FileSeriesReaderAdapter
IterateReader

FileSeriesReader in the TsFile module is updated.

Aggregate Functions

AggregateFunction: add an abstract method calculateValueFromChunkMetaData
Functions which extend AggregateFunction are thus updated:

AvgAggrFunc
CountAggrFunc
MaxValueAggrFunc
MinValueAggrFunc
FirstValueAggrFunc
LastValueAggrFunc
MaxTimeAggrFunc
MinTimeAggrFunc

Aggregate Engine Executor

AggregateEngineExecutor.aggregateWithoutValueFilter method is modified
AggregateEngineExecutor.handleLastMaxTimeWithOutTimeGenerator method is modified

It looks good to me. Thank @liutaohua for your hard work.


Add test for ResponseModifier

There are still a few tests missing. I will add them in upcoming PRs and then work on the Response filtering.

Changes Unknown when pulling d373d9aee7fdad723d2e65f468bdd304dc250c2f on groyoh:response_test into ** on vinxi:master**.

Great. Will take a look.
BTW, I would appreciate some code review here:
https://github.com/vinxi/consul
The consul component is almost done, but still requires some minor features and better test coverage.


Add start/stop/pause functionality to UI

Related to #121

I believe this is partially, though maybe not fully, resolved via https://github.com/ssec-jhu/evolver-ui/pull/5


Fix ProgramTest step paths in tests

These paths were not found but the error was silently ignored, see https://github.com/pulumi/pulumi/issues/14694.

One of the modified tests seems to be failing.


Update flow-react-proptypes to ^1.2.0

Not much info necessary on this one. Fixes the issue discussed in #1045.

@joemckie Just tried this out locally and I'm getting the issue:

error: bundling: ReferenceError: Unknown plugin "flow-react-proptypes" specified in "/Users/dev/Documents/foo/node_modules/react-navigation/.babelrc.env.development" at 0, attempted to resolve relative to "/Users/dev/Documents/foo/node_modules/react-navigation"

@AlanFoster you're right - it looks like the dependency isn't being installed correctly. I tested and moving it to dependencies works, but it should work as it was in devDependencies before.
I don't think the other issue you're having is related. That looks like you've updated react, as they've removed PropTypes from the latest version and moved it to another dependency.
For me, using this PR as my react-navigation dependency and installing the babel-plugin-flow-react-proptypes dependency worked.
@grabbou, any idea why it isn't being installed correctly?

Thanks for the investigation @joemckie :+1: Pointing this to master after the recent changes seems more stable.
I can now also confirm that the PropTypes error was unrelated, I had copied the code samples from the redux examples but missed out the line where it explicitly imports PropTypes:
import React, { PropTypes } from 'react';

I was able to debug this by stepping through the module loading/factory logic manually :+1:


How to evaluate the model?

Dear Authors,
I have read your paper with great interest and I am particularly intrigued by the Fréchet Reconstruction Distance (FReD) metric introduced for assessing the quality of generated DNA samples. As mentioned in the paper, you trained an Auto-Encoder (AE) on a reference genome distinct from the training data used for generation to derive embeddings for this metric.
Could you please provide the code and the pre-trained weights for this Auto-Encoder? Having access to these resources would greatly facilitate the reproduction of your results and further application of the FReD metric in related research.
Thank you for your consideration.

Hi @yangzhao1230 ,
In the first workshop paper, we have both FReD and the FID computed with the Sei Embedding Distribution Distance. For FReD, the Auto-Encoder is used, while for the Sei Embedding Distribution Distance, Sei (https://www.nature.com/articles/s41588-022-01102-2) is used for encoding the data.
I suggest you follow the refined version of our paper (https://arxiv.org/abs/2402.06079), here we notice that the Sei based FID is more proper (as the Reconstruction based evaluation really depends on the Auto-Encoder used, so for transparency it is better to rely on a well-known ckpt for evaluation). I hereby recommend you to download the checkpoint of Sei model from https://github.com/FunctionLab/sei-framework and use it to compute the FID.  For the code to compute the FID, it is relatively simple, but you can refer to https://github.com/Zehui127/Latent-DNA-Diffusion/blob/b64d0334895747307a06efeb4669d5e2ae429dcf/src/utils/evaluator.py#L45 as a implementation.

Thanks for your help!


Using ${buildKit} in c_cpp_properties.json not working

Brief Issue Summary
It's really great that since version 1.1.2 the ${buildKit} variable is use able for defining the build directory. With this i can multiple toolchains with separate build folders without rebuilding everything.
I currently get an error with cpp-tools though, which looks for the compile_commands.json

This is true since my cmake.buildDirectoty includes the ${buildKit} variable. It seems the same variable can't be used in the c_cpp_properties.json. I have to add the exact path by hand and also have to change it, when i switch my kit for different toolchain file.
Expected:
Would be great if ${buildKit} would work in c_cpp_properties.json but i'm not sure if this is the right approach. It might be more of an issue for the cpp-tools.
Platform and Versions

Operating System: Windows
CMake Version: 3.13.1
VSCode Version: 1.30.1
CMake Tools Extension Version: 1.1.3
Compiler/Toolchain: arm-none-eabi-gcc

Hi, is there any news about it?

i think this issue would also be resolved when the "configuration provider" for the cpp tools would work correctly. I need the buildKit variable to find the compile_commands.json with multiple kits.
I wasn't aware when i wrote the ticket, that there is a configuration provider for the cpp_tools extension.
In my current configuration the cmake-tools.configuration provider seems not to work correctly when multiple kits with multiple toolchain files are configured. In this case intellisense is not working correctly with the configuration provider. This is why i want to use the compile_commands.json and directly and there it would be handy when the $buildKit variable would work

Would it not be possible to have something like ${command:cmake.buildDirectory} with the ${buildKit} and such already resolved, similar to ${command:cmake.launchDirectory}? This would also help me for other artifacts being produced such as coverage reports.

@hriekehof , can you provide us with more information about your configuration?  As you indicated, fixing the configuration provider seems like the better approach since cpptools doesn't have an awareness of extension-specific variables and commands.

sorry for answering so late. I think the problem i had here was during a time when the configuration provider of the cmake-tools extenstion was not working correctly. So i wanted to use the compile_commands.json directly in the cpp extension.
The place of the file switches with different build configurations using the ${buildKit} variable. So i had to update the c_cpp_properties.json everytime  i switched the kits.
I guess this is not a real problem right now anymore since the configurationProvider just works i assume.
Atm i use the cmake-integration extension for its support of multiroot workspaces so i cannot test this quickly right now :)
For me this can be closed

Ok, thanks for following up.  FWIW, we are testing a preview version of the extension with multi-root support and plan to make it available soon.

ah great to hear that. i looking forward to it


Length unit changes are not respected

To reproduce:

Start PyFluent and run the attached script.
Please use the geometry from this location
Run the following script:
diam_bug.py.txt
The length units are changed to "mm" in the solver before accessing the boundary conditions.
But when specifying the hydraulic diameter, the units get specified in "m".

Behaviour is as expected


[as2_behaviors_motion] Follow Reference Behavior Transforms Error

Basic Info

Info
Please fill out this column

Issue(s) this addresses
#196

ROS2 version tested on
Humble

Aerial platform tested on
Ignition

Description of contribution in a few bullet points

Remove follow reference from general motion behaviors launch

Future work that may be required in bullet points

Change as2 launch in projects where follow reference is used

Codecov Report

Merging #199 (eff73a0) into main (ba662c0) will decrease coverage by 0.07%.
The diff coverage is 0.00%.

:exclamation: Current head eff73a0 differs from pull request most recent head 9d18d29. Consider uploading reports for the commit 9d18d29 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff            @@
##            main    #199      +/-   ##
========================================
- Coverage   3.13%   3.06%   -0.07%
========================================
  Files         99      96       -3
  Lines       5133    5119      -14
  Branches     451     466      +15
========================================
- Hits         161     157       -4
+ Misses      4834    4808      -26
- Partials     138     154      +16

Flag
Coverage Δ

unittests
3.06% <0.00%> (-0.07%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...e/as2_behavior/__detail/behavior_server__class.hpp
0.00% <ø> (ø)

...behaviors/as2_behavior/tests/basic_server_test.cpp
0.00% <ø> (ø)

...w_reference_behavior/follow_reference_behavior.hpp
0.00% <0.00%> (ø)

... and 49 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


fix(angular-components): updating angular library dependencies to ang…

…ular 12; this was the case after the repo dependencies update, but needs to be reflected on the library package.json.
BREAKING CHANGE: angular library requires Angular 12 after this change.

:tada: This PR is included in version 2.0.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.7.0-beta.36 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.4.0-beta.64 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.4.0-beta.41 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.4.0-alpha.2 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix invalid freebsd version selection

Just realized when working on sysinfo that my stafs struct filled by getmntinfo was missing a lot of information. After trying to find out from my size what I missed, I simply check the size_of the rust struct vs the C struct and found 484 != 2384. After looking a bit more, I discovered that only the CI was using the right freebsd version, which is quite problematic.
r? @Amanieu

I'm not actually sure about this, isn't this a breaking change? I suppose that matching the version of freebsd that you are compiling on makes sense, so I'm inclined to accept this. But cc @JohnTitor just in case.

I'm not sure if it is but currently it's unusable and broken. Let's wait to hear from @JohnTitor then. :)

I don't have enough time to take a closer look at this, @Amanieu if you think it's reasonable and doesn't break anything, feel free to go ahead :)

@bors r+

:pushpin: Commit 53e79b886bf4e4d3682ae6669e3585b3586e5255 has been approved by Amanieu

:hourglass: Testing commit 53e79b886bf4e4d3682ae6669e3585b3586e5255 with merge 6fe1ff94948e805c0d20970adaa73ebdd4fd7d1b...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: Amanieu
Pushing 6fe1ff94948e805c0d20970adaa73ebdd4fd7d1b to master...

I think this change might have broke mio on FreeBSD 12, see https://github.com/tokio-rs/mio/issues/1539

It means their code was broken from the start unfortunately... They were using a struct with the wrong size on freebsd 12. I'm not teaching them anything new but they should use mem::zeroed. Unfortunately, freebsd changes the layout of its types from one version to another (adding field, changing field type, changing their order). It's a real nightmare...

This is incorrect.  FreeBSD uses ELF symbol versioning to change the interface for libc in a backwards-compatible way.  But Rust, because it is designed for cross-compilability, doesn't work with ELF symbol versioning.  That's why Rust's libc has always exposed a FreeBSD 11 ABI.  Your change broke that guarantee, and causes libc to now expose the native ABI for whatever platform the crate is compiled on.  mio broke because it was programming for the FreeBSD 11 ABI, and now suddenly libc is using a FreeBSD 12 ABI.  Please revert this change.  We ought to raise the ABI at some point, but it must be done very carefully, and please include me in the PR.

I'm a bit lost by your explanations: this is part of the freebsd header files and libraries.

mio broke because it was programming for the FreeBSD 11 ABI, and now suddenly libc is using a FreeBSD 12 ABI.

For cross-compilation, I guess we can add a cargo feature to handle it if you target a specific freebsd version. However, building using a freebsd 11 definitions version on a freebsd non-11 version is completely wrong. In my case it simply created UB because I passed types with the wrong type.

I'm a bit lost by your explanations: this is part of the freebsd header files and libraries.

mio broke because it was programming for the FreeBSD 11 ABI, and now suddenly libc is using a FreeBSD 12 ABI.

For cross-compilation, I guess we can add a cargo feature to handle it if you target a specific freebsd version. However, building using a freebsd 11 definitions version on a freebsd non-11 version is completely wrong. In my case it simply created UB because I passed types with the wrong ABI/size/layout.

@GuillaumeGomez for some context Mio has been used libc stuff pretty heavily and works without issues on FreeBSD 12.
(also for some further context @asomers knows FreeBSD pretty well ;) )

There's a been a lot of discussion about how to enable FreeBSD 12+ features in libc.  Unfortunately, there's no agreed plan yet.
And not, it's not completely wrong to use the FreeBSD 11 ABI.  That's the magic of ELF symbol versioning!  When you run mio under FreeBSD 12, the libc::kevent structure corresponds to what in C is known as freebsd11_kevent.  And the libc::kevent FFI function actually calls<EMAIL_ADDRESS>rather than plain kevent.  And this function calls the freebsd11_kevent syscall, rather than the plain kevent syscall.  That's why everything is backwards compatible.

As an aside about structures such as libc::kevent etc, aren't those structures expected to get new fields when OS get new features? Shouldn't they be marked #[non_exhaustive]?

As an aside about structures such as libc::kevent etc, aren't those structures expected to get new fields when OS get new features? Shouldn't they be marked #[non_exhaustive]?

That's not a bad idea.  But which structures should get the non-exhaustive treatment?  Of the hundreds of structures exported by libc, there are very few that are ever guaranteed not to grow.

In my case it simply created UB because I passed types with the wrong ABI/size/layout.

How did this happen?

What about this: we add feature to cargo which allows you to pick the freebsd version you want at compile-time instead of targetting the FreeBSD 11 in all cases? For people like me, we get what we want by default and you can choose which version to use. Does that sound reasonable to you?

To provide more context: I added freebsd in sysinfo recently and was testing it on freebsd 14. However, some types didn't have the expected ABI, preventing me to query disk information. I realized that valgrind was also complaining about some other structs I was using because they had the freebsd 11 ABI and I was on freebsd 14. The current situation is pretty bad in that regard because a highly specialized case is the default and anyone not aware of it (I still have no clue how you're doing what you're doing) will end up in my situation: it cannot work because the ABI is incompatible.

In my case it simply created UB because I passed types with the wrong ABI/size/layout.

How did this happen?

No, using 100% libc.

I think the issue is from #2058 which added getmntinfo without specifying an explicit version with link_name. This causes it to always use the latest version available on the host even though libc uses the FreeBSD 11 version of the statfs struct.

Here is the nm output:
nm -D /lib/libc.so.7 | grep getmntinfo
000000000000a1360 T getmntinfo
000000000000a1250 T getmntinfo

Sorry, wrong PR, the FreeBSD getmntinfo was added in #2572.

This is a ticking bomb and we need to do something about it. libc is one of the most used crate in the rust ecosystem and this is a huge bug. The CI didn't catch it and I don't know if it can. The fact that I'm the first to encounter this bug is quite surprising though.
Also, I was very happy to be able to get full disk information and I'll be forced to go back to freebsd 11's limitations. I'm very frustrated to be limited to a version like that.
@asomers What do you think about what I suggested above? I don't want to be stuck forever on one version without a way to be able to use the current version. If what I suggested doesn't work, how should we do it?

@asomers What do you think about what I suggested above? I don't want to be stuck forever on one version without a way to be able to use the current version. If what I suggested doesn't work, how should we do it?

Adding an on-by-default Cargo feature like "freebsd11-compat" was actually my first suggestion when this originally came up a long time ago.  However, the rest of the community didn't like it.  It is too FreeBSD-specific.  The same technique doesn't work with OpenBSD or Linux, for example.  OpenBSD users favor an approach of adding the major version number to the target-triple, making it a target-quadruple instead.
For the specific question of FreeBSD 11 compatibility, I favor dropping it entirely now that FreeBSD 11.4 is EoL.  See https://github.com/rust-lang/rust/pull/89083 .  That will resolve most issues like yours.  There are far fewer symbol changes between 12->13 and 13->14 than there were from 11->12.

That still leaves a lot of potential issues. Also, maybe it's worth opening the debate once again. Being stuck on one version is just too problematic. And there is also no way to "unlock" it too...
I'm surprised your suggestion was rejected though. What's the problem to have features specific for freebsd? Do you still have the conversation around by any chance?

I'm surprised your suggestion was rejected though. What's the problem to have features specific for freebsd? Do you still have the conversation around by any chance?

https://github.com/rust-lang/libc/issues/570

Wow, quite the thread. It's still far from done by at least there is hope. I am really surprised that such a big issue that a lot of people were aware of was not addressed much earlier. I'm really just the last one in a long list of people who encountered this issue...


Add node 16 info

With the addition from https://stackoverflow.com/questions/57110542/how-to-write-a-nvmrc-file-which-automatically-change-node-version to my .zshrc the node version is automatically updated.

thanks


feat!: add xsdata models

Refs: Fixes #126, fixes #152, fixes #111
Tasks

[x] add xsdata models for "oai_pmh" xsd
[x] add xsdata models for "oai_dc" xsd
[ ] add xsdata models for "oai_datacite" xsd
[x] add xsdata models for "marcxml" xsd
[x] add Response dataclass
[x] add _build_response() helper function
[x] add _parse_response() helper function
[x] remove obsolete get_namespace() helper function
[x] remove obsolete xml_to_dict() helper function
[x] tests are passing
[x] #152
[ ] #111
[x] Deleted status mixin for header and record
[x] xsdata in readme
[x] mock response needs content -> fixture with identify xml
[x] Encoding was set on response
[x] Add url attr to response
[x] mypy is passing (3 issues remaining)
[x] Example oai dc, datacite
[ ] update docs

[ ] customizing
[x] check if returns and yields sections are displayed twice under api/client/
[ ] nested api reference for models

[ ] Show example of response without known metadata format, e.g. "arxiv"
[x] Check if save to xml.code still works, uses raw

Refs:

https://xsdata.readthedocs.io/en/latest/codegen.html

Commit message draft

Lets start with only oai dc and oai pmh. No datacite, no marc etc.


num_pollers metric

Is your feature request related to a problem? Please describe.
There is no clear way to tell how many pollers were active at any given time when tuning a cluster or doing an outage post mortem.
Describe the solution you'd like
Please implement the num_pollers metric for the Go SDK: https://docs.temporal.io/references/sdk-metrics/#num_pollers

Need to be able to tell how many activity pollers and how many workflow pollers.


Autolabelling: Setup a data collection pipeline (e.g. what happens when new data comes in?)

Data collection pipeline should be reactive to data coming into a bucket, for example:
Images get added to bucket -> autolabelling pipeline happens for unlabelled images -> labelling cleaning happens -> model training pipeline happens for when all images are labelled -> evaluation pipeline happens -> deployment happens
See:

Modal Cron jobs for watching a storage bucket for changes: https://modal.com/docs/guide/cron
Google/TensorFlow continuous adaptation for ML system to data changes (watch bucket, do X if something happens): https://blog.tensorflow.org/2021/12/continuous-adaptation-for-machine.html

Potential autolabelling pipeline:

raw images downloaded (e.g. filtered images from large dataset, such as, LAION-COCO)
several rounds of zero-shot classification are run to further filter images

"edible_food" vs "other" (only keep images which contain edible food
"contains_logo" vs "other" (remove images with logos/text)
"apple" vs "banana" ... (label images with their appropriate class name)

Could use the pipeline above with multiple variants of CLIP-style models for redundancy.

See openclip for zero-shot classification: https://github.com/mlfoundations/open_clip

Much better to compute image embeddings + class embeddings up front.
Then reuse over time where necessary.
This could be setup via:

image gets given UUID
image embedding gets calculated
if the image UUID has an existing embedding, use that (can force to compute new if necessary)

See this resource for autolabelling object detection: https://github.com/facebookresearch/CutLER


Internalize some Docker types

Internalize the type declaration of a Docker image, so that we don't need to pull in code and a pile of additional dependencies when we just want to know how to parse out a JSON object.  Carry a copy of the license that covered the sources from which the definitions came.

LGTM

@rh-atomic-bot r+ fbf1b83adee1a70e67105075e316dfa57b8e2a6e


BUG | TextArea: minlength & maxlength not taking effect

Expected Behavior

TextArea should adhere to minlength or maxlength passed through props

Current Behavior

Using these attributes results in following error:
Type '{ placeholder: string; maxlength: number; cols: number; defaultValue: string; }' is not assignable to type 'IntrinsicAttributes & Pick<TextAreaProps, "required" | "key" | "id" | "name" | "color" | "translate" | "value" | "hidden" | "dir" | "form" | ... 260 more ... | "fixedSize"> & RefAttributes<...>'.
Property 'maxlength' does not exist on type 'IntrinsicAttributes & Pick<TextAreaProps,

Possible Solution

Steps to Reproduce (for bugs)

Pass either minlength or maxlength prop to  component

Context

Your Environment

Version used:  0.1.8
Browser name and version: Safari 16.0
Operating System and version (desktop or mobile): macOS Monterey 12.6
Link to your project:

@hnprashanth I think you have passed minlength and maxlength but the props are minLength and maxLength --> it's the capital 'L'.
I checked in Google Chrome and Safari as well, In both browsers, it's working.
@Raalzz or @pruthvi2103 anyone of you can re-check again?

@Shadow-Flash @hnprashanth pls confirm if this issue requires anything else, the ticket no is HOV-47

tried in codesandbox, the props work. Closing this issue


Failed Foreign Disk Import

[Enter feedback here]
When I imported the foreign disk, it gives me a status of failed for the Raid 1 folder but every other folders are ok:

What can I do? The document doesn't give any guidelines for this issue.
Thank you.
Best regards.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: d50fc049-8fad-f318-1d3a-f5a50ad2a5ac
Version Independent ID: 742902d7-d4be-d211-ee78-293101d06f02
Content: Move disks to another computer
Content Source: WindowsServerDocs/storage/disk-management/move-disks-to-another-computer.md
Product: windows-server
Technology: storage
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

Hey @francoluis,
Thanks again for contacting Microsoft, we value your feedback.
You have described an issue that is not covered in this documentation when importing foreign drives. It's outside our scope to address issues that aren't document related.
Please search and engage within our community forums:

Microsoft TechNet
Microsoft Developer Network
Microsoft Support Community
Or open a ticket with Microsoft Support

Hopefully one of our community members may be better able to assist. We'll now be closing this thread.
Thank you and have a most pleasant day.


[FEATURE] Add aliases for nodes URLs

Аbstract
Add an alias for a node's URL to make it easier to understand what node is currently analyzed.
Motivation and Purposes
Some nodes do not have a host name which makes it harder to understand what node is currently analyzed.

https://github.com/wavesplatform/nodemon/pull/146


Make the UI look as close to final (Due 8/31)

[x] replace placeholders with actual data where possible (8/14)
[x] create the charts for that data (8/14)
[ ] CSSing that needs to get done

Added blocked label -- I'm still playing with the CSS, but the pulling in and charting of data has gotten as far as I can get it. Which is to say, I've charted what data we have.

Also a reminder to help Ernie move some of the inline CSS he did for last minute dashboard changes into SASS and making things look generally less awful. (Sorry about that)


feat(www): enable providers to send custom error responses via the dynamic key

This PR enables service providers to return an error object to inform the end user about something wrong with their dynamic key or server connection. Service providers could then volunteer contact information via this error message.

We need to better understand the trade-offs between the different approaches, which also included a client response and a Client API.
During planning, we decided we needed a document for discussion.
There are also open questions regarding what format we should use, and what the UI should look like, but they can be decoupled from the chosen approach.

We also need to think about communicating the new feature in the next release, and perhaps add that to the wiki.


Match GHC changes for T16185

FunTy now has an AnonArgFlag that indicates whether the arrow is
a t1 => t2 or t1 -> t2.
This commit shouldn't change any functionality in Haddock.

Superseded by #1031


Updated login to new epic requirements

Added too short password error message
Trim email login form field

lookin good :+1:


convert interfaces_* to fa

interfaces_vlan.php uses $_POST instead on $_GET.
no clue why that is. after some googling i found there is no real benefit in this scenario to use $_POST. (big chance i'm wrong)
$_POST gave me an issue with the onclick js for act=del. (even when clicking cancel, the entry was deleted)
changed it to $_GET like every other similar page i've come across thus far.

There is a feature request in progress to turn all pages from GET to POST. The reasons being security and accidental actions when using the browser back button.
This proposal is OK for now, but I might change it back again :)
Steve
Stephen Beaver | +1<PHONE_NUMBER>;239 |<EMAIL_ADDRESS>| www.netgate.com

On Nov 2, 2015, at 11:31 AM, heper<EMAIL_ADDRESS>wrote:
interfaces_vlan.php uses $_POST instead on $_GET.
no clue why that is. after some googling i found there is no real benefit in this scenario to use $_POST. (big chance i'm wrong)
$_POST gave me an issue with the onclick js for act=del. (even when clicking cancel, the entry was deleted)
changed it to $_GET like every other similar page i've come across thus far.
You can view, comment on, or merge this pull request online at:
https://github.com/pfsense/pfsense/pull/2015 https://github.com/pfsense/pfsense/pull/2015
Commit Summary
convert interfaces_groups to fa
Update interfaces_groups.php
convert interfaces_wireless to fa
convert interfaces_vlan to fa
convert interfaces_qinq to fa
convert interfaces_ppps to fa
Update interfaces_qinq.php
convert interfaces_gre to fa
convert interfaces_gif to fa
convert interfaces_bridge to fa
convert interfaces_lagg to fa
File Changes
M src/usr/local/www/interfaces_bridge.php https://github.com/pfsense/pfsense/pull/2015/files#diff-0 (6)
M src/usr/local/www/interfaces_gif.php https://github.com/pfsense/pfsense/pull/2015/files#diff-1 (6)
M src/usr/local/www/interfaces_gre.php https://github.com/pfsense/pfsense/pull/2015/files#diff-2 (10)
M src/usr/local/www/interfaces_groups.php https://github.com/pfsense/pfsense/pull/2015/files#diff-3 (10)
M src/usr/local/www/interfaces_lagg.php https://github.com/pfsense/pfsense/pull/2015/files#diff-4 (4)
M src/usr/local/www/interfaces_ppps.php https://github.com/pfsense/pfsense/pull/2015/files#diff-5 (4)
M src/usr/local/www/interfaces_qinq.php https://github.com/pfsense/pfsense/pull/2015/files#diff-6 (4)
M src/usr/local/www/interfaces_vlan.php https://github.com/pfsense/pfsense/pull/2015/files#diff-7 (58)
M src/usr/local/www/interfaces_wireless.php https://github.com/pfsense/pfsense/pull/2015/files#diff-8 (4)
Patch Links:
https://github.com/pfsense/pfsense/pull/2015.patch https://github.com/pfsense/pfsense/pull/2015.patch
https://github.com/pfsense/pfsense/pull/2015.diff https://github.com/pfsense/pfsense/pull/2015.diff
—
Reply to this email directly or view it on GitHub https://github.com/pfsense/pfsense/pull/2015.

Actually I need you to revert the POST/GET change please and I will fix the immediate delete. The need to convert this page to POST was confirmed.
Steve
Stephen Beaver | +1<PHONE_NUMBER>;239 |<EMAIL_ADDRESS>| www.netgate.com

On Nov 2, 2015, at 11:31 AM, heper<EMAIL_ADDRESS>wrote:
interfaces_vlan.php uses $_POST instead on $_GET.
no clue why that is. after some googling i found there is no real benefit in this scenario to use $_POST. (big chance i'm wrong)
$_POST gave me an issue with the onclick js for act=del. (even when clicking cancel, the entry was deleted)
changed it to $_GET like every other similar page i've come across thus far.
You can view, comment on, or merge this pull request online at:
https://github.com/pfsense/pfsense/pull/2015 https://github.com/pfsense/pfsense/pull/2015
Commit Summary
convert interfaces_groups to fa
Update interfaces_groups.php
convert interfaces_wireless to fa
convert interfaces_vlan to fa
convert interfaces_qinq to fa
convert interfaces_ppps to fa
Update interfaces_qinq.php
convert interfaces_gre to fa
convert interfaces_gif to fa
convert interfaces_bridge to fa
convert interfaces_lagg to fa
File Changes
M src/usr/local/www/interfaces_bridge.php https://github.com/pfsense/pfsense/pull/2015/files#diff-0 (6)
M src/usr/local/www/interfaces_gif.php https://github.com/pfsense/pfsense/pull/2015/files#diff-1 (6)
M src/usr/local/www/interfaces_gre.php https://github.com/pfsense/pfsense/pull/2015/files#diff-2 (10)
M src/usr/local/www/interfaces_groups.php https://github.com/pfsense/pfsense/pull/2015/files#diff-3 (10)
M src/usr/local/www/interfaces_lagg.php https://github.com/pfsense/pfsense/pull/2015/files#diff-4 (4)
M src/usr/local/www/interfaces_ppps.php https://github.com/pfsense/pfsense/pull/2015/files#diff-5 (4)
M src/usr/local/www/interfaces_qinq.php https://github.com/pfsense/pfsense/pull/2015/files#diff-6 (4)
M src/usr/local/www/interfaces_vlan.php https://github.com/pfsense/pfsense/pull/2015/files#diff-7 (58)
M src/usr/local/www/interfaces_wireless.php https://github.com/pfsense/pfsense/pull/2015/files#diff-8 (4)
Patch Links:
https://github.com/pfsense/pfsense/pull/2015.patch https://github.com/pfsense/pfsense/pull/2015.patch
https://github.com/pfsense/pfsense/pull/2015.diff https://github.com/pfsense/pfsense/pull/2015.diff
—
Reply to this email directly or view it on GitHub https://github.com/pfsense/pfsense/pull/2015.

@sbeaver-netgate
gotcha, should be ok now.

Merged.
Thank you. I’ll look at the van_edit issue in a few minutes.
Steve
Stephen Beaver | +1<PHONE_NUMBER>;239 |<EMAIL_ADDRESS>| www.netgate.com

On Nov 2, 2015, at 12:06 PM, heper<EMAIL_ADDRESS>wrote:
@sbeaver-netgate https://github.com/sbeaver-netgate
gotcha, should be ok now.
—
Reply to this email directly or view it on GitHub https://github.com/pfsense/pfsense/pull/2015#issuecomment-153084473.

Confirm deletion fixed in a5855731c0276b72585c3a23378c85370f7ebf33


Move debug toolbar to bottom

The debug toolbar is anchored at top of editor area.

This area us precious, it is at the first lines of file and it already ocupied by the search/replace toolbar and the tabs.
Please move it (or allow it to move) to the bottom of editor area, where it could stay harmoniously without annoying.

Thanks for all.

Custom positioning is a duplicate of an already open issue. Currently you can drag it a bit up (to the tabs are) and you can also dock it to the debug viewlet, set the debug toolbar setting to "docked".
Custom positioning we do not really want to do -> out of scope and there might already be a duplicate for this

@bittnkr "debug.toolBarLocation": "docked"

It worked. Thank you!


How to solve the following warning from brew doctor?

MacOS Sierra 10.12.2
Recently, I ran into the following issue:
Warning: Unbrewed .la files were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected .la files:
  /usr/local/lib/psqlodbcw.la

I have tried different approaches like:
brew unlink postgresql && brew link postgresql
brew link --overwrite postgresql

But that doesnt seem to resove the warning.
appreciate any help

You can manually delete this file with rm /usr/local/lib/psqlodbcw.la or just ignore the warning.


Make error_chain with default-features = false work with Rust 1.10

error_chain uses attributes on statements, stablized in Rust 1.13.
Factor them out of functions in the non-backtrace codepath, making it
possible to build a crate that uses error_chain with Rust 1.10.
The backtrace feature still requires Rust 1.13 for attributes on
statements, due to the impl_extract_backtrace macro, which needs to emit
a function with one block for each linked error type, some of which may
have attributes on them.  And any code using compile-time conditionals
in attributes on variants within an error_chain! invocation (which
includes many of the tests and examples) will produce an error due to
https://github.com/rust-lang/rust/issues/22250 (fixed in Rust 1.11).
But a crate using error_chain with default-features = false and avoiding
such compile-time conditionals will now compile.

If it's not too much trouble, would you mind putting out an 0.7.2 with this included, so I can use that from another crate?

That's better than nothing. Could you update the README?

@Yamakaky Sure, will do. Do you know how to make Travis run --no-default-features builds, without tests, on Rust 1.10?

@Yamakaky Done.  (The Travis bits aren't perfect, since they still declare two builds for 1.10 and skip one at build time, but they do work correctly.)

OK, this now tests 1.10 properly with Travis.

Thanks!


code-server: add vscode-with-extensions compatibility

Description of changes
This change makes code-server compatible with vscode-with-extensions. I added an example to the code-server nixos module, indicating this functionality.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg eval

ofborg seems happy
why no merge?

Rebased and nix pilled. Test:
NIXPKGS_ALLOW_INSECURE=1 nix build --expr 'with (builtins.getFlake "github:pbsds/nixpkgs/code-server-ext-compat").legacyPackages.x86_64-linux; vscode-with-extensions.override { vscode=code-server; }' --impure

Oops, there are still merge conflicts

I had a pre-#232360 checkout it seems.

lib.mkPackageOptionMD does not seem to support lib.literalExpression.
Its fine in our case however, as the multi-line string is indented which in markdown denotes a code block. I removed lib.literalExpression and it looks just find

Thanks for your contribution! Keep them coming!


Deployment issue after OpenShift upgrade

Steps to deploy manually were shared with the devs, this will unblock our dev work for now while we're working to fix the issue with automated deployment.

This is working great! Thanks, @matbusby-fw
We can close this ticket.


Documentation/op-guide: discourage "--force-new-cluster" in recovery

Highlight the discussions from https://github.com/coreos/etcd/pull/9177.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@4e662b2). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #9279   +/-   ##
=========================================
  Coverage          ?   76.14%
=========================================
  Files             ?      364
  Lines             ?    30231
  Branches          ?        0
=========================================
  Hits              ?    23020
  Misses            ?     5627
  Partials          ?     1584

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 4e662b2...99e1bd2. Read the comment docs.


Add ThermostatCard

Adds the ThermostatCard component as part of the thermostat detail view

@razor-x in regard to CLS: this will be reduced when it's in a bounding container (I've updated the story to simulate its intended placement). The width of the card will no longer change based on the current unit; however, we will still, of course, see a width change within the card when the numbers change. This can be further reduced by making all temperatures non-floats, instead of just Fahrenheit. Up to you.

Ah ok thanks for the context! Let's make all temps non floats for now. We only support incrementing by integers anyway so I think this is an okay place to start.


 I fixed it on my private fork, but I just don't have the time for the bureacy of merging PRs on this repo.

it has a clicking/banging sound... If you really listen to it paying attention to detail, yeah it's mostly likely dynamic audio normalisation coz when I edited that out everything was alright

Thanks a lot for the heads up. A PR is already in the works.


Stabilize navigation and interaction in Settings editor

Issue Type: Feature Request
This is probably a bug, but let's start here first.
Clicking on checkboxes in the Settings editor has some odd behavior. Clicking on a control that is not currently focused causes an immediate and disorienting jump (scroll position shift). Sometimes the click on the control (e.g., checkbox) doesn't toggle it, but instead changes the scroll position only leaving you to wonder if you really toggled it.  In fact, sometimes that repositioning moves the view to a point where the element you clicked on no longer is visible and requires a manual rescroll to get the settings group back in view.
You might be able to repro this by searching for "inlay" in Settings and then trying to interact with the Javacript and Typescript settings dealing with inlay hints.
Expected behavior:

Clicking on a control, no matter where the scroll position is or if the settings group is focused should activate the behavior on the control first

Changing the scroll position should use smooth scrolling so the abrupt change of view is not disorienting

VS Code version: Code 1.60.0 (e7d7e9a9348e6a8cc8c03f877d39cb72e5dfb1ff, 2021-09-01T10:41:52.311Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

https://github.com/microsoft/vscode/issues/106577


Fullscreen apps

Another issue i have found is that when you have a few windows opened and lets say you have VLC on one of them and want to set the video full screen it doesnt work, it kinda fullscreens in its own window, if you only have 1 window it does work though.

Confirmed.

I reckon this is handled now. Will test it in the wild for a bit.


Powershell not able to access cookies

On this computer, cookies are available from the following browsers: [blank]
I am running powershell on admin configuration, how can I rersolve this pl?

Please check with the latest released version. The library used to decrypt browser cookies was changed, and perhaps it works better for you now.


Initial release observations

Thank you very much for your effort!
I can confirm that it connects automatically to the Bluetooth strip controller!
The only functionality that worked for me is turning it off. Everything else like turn on, color selection,  brightness, status, is not working.
Thanks again for creating this. Hopefully the community will have something fully working at some point

try new version

solved in new release https://github.com/dave-code-ruiz/elkbledom-ha/commit/e352a397bdd16b68d80990196a910c714a0ecf0d

I confirm. Thank you very much!


Add a limit on depth of thread trees

I absolutely love the thread view of Coracle, but it's sometimes clunky for smaller displays such as mobile. How about setting the maximum depth  of thread tree? It could be either of static or dynamic. I can work on it if approved.

I had this implemented in one place but not another, just pushed an updated that limits depth to 3 replies. Thanks for pointing that out!


Fix: Use json.Unmarshal() instead of json.Decoder

See https://ahmet.im/blog/golang-json-decoder-pitfalls/
json.Decoder is for JSON streams, not single JSON objects / bodies.
Signed-off-by: Julius Volz<EMAIL_ADDRESS>

So I'm not sure if this should actually go into 2.28.1 since these bugs were around forever, but not critical apparently... but just for good measure I opened it against release-2.28 for now. I can also put it into main instead.

Naturally, I don't have Hetzner machines, a Marathon server, etc. to try all these fixes out for real. So we might want to look closely...

I propose to move this to main.

Agreed, will close here and reopen against main.


Django views for getting individual and aggregated reports

Related to : #89

closed on 07.07.2021. Linked to main task #89


Remove setting unnecessary password flag to all commands

Change Overview
This PR removes RepoPassword from common args, as it's only required for establishing connection to the repository.
Pull request type
Please check the type of change your PR introduces:

[ ] :construction: Work in Progress
[ ] :rainbow: Refactoring (no functional changes, no api changes)
[ ] :hamster: Trivial/Minor
[ ] :bug: Bugfix
[ ] :sunflower: Feature
[ ] :world_map: Documentation
[ ] :robot: Test

Issues

fixes #issue-number

Test Plan

[x] :muscle: Manual
[ ] :zap: Unit test
[ ] :green_heart: E2E

Closing wrt new work being done for kopia server, will re-open if it still applies after that.


selecting images

A taxonomist would like to select the images that are helpful to him, and discard those, that are not.
Might it be possible to be able to select images and dismiss others so that at the end only those images are available, that are required?
In a later round, it might be helpful to save this selection for later reuse, so that you can build up a corpus of images relevant to a specific project?

This is a nice functionality but it requires a helluva lot of work. Primary among the requirements would be a way to track a user, and that gets into creating and managing user accounts, and that significantly increases the complexity (like many orders of magnitude). I have labeled this as "enhancement" and will keep it open so it doesn't fade away, but it will go on the back burner for now. Perhaps I can come up with a way to implement this without requiring user accounts.


Support platform version 0.2 and 0.3 and remove support for 0.1

Passes project metadata toml file to exporter for platform version 0.3

Codecov Report

Merging #311 into master will decrease coverage by 0.60%.
The diff coverage is 96.29%.

@@            Coverage Diff             @@
##           master     #311      +/-   ##
==========================================
- Coverage   68.25%   67.64%   -0.61%
==========================================
  Files          78       78
  Lines        3200     3140      -60
==========================================
- Hits         2184     2124      -60
  Misses        767      767
  Partials      249      249

Impacted Files
Coverage Δ

pkg/git/fetch.go
60.41% <80.00%> (-3.05%)
:arrow_down:

pkg/apis/build/v1alpha1/build_pod.go
97.36% <100.00%> (-0.38%)
:arrow_down:

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 f0f4698...0d74483. Read the comment docs.


Fix Edit Button for RECENTLY DUPLICATED / NEW CONNECTIONS

Refer to this issue for more details...
https://github.com/sqlectron/sqlectron-gui/issues/409
Below is a short description
Edit and Other commands don't work for RECENTLY DUPLICATED CONNECTIONS

duplicate an existing connection
try to edit it (notice it's not working)...

Connect button works, but the edit button doesn't work.
I'll check to see if I can send in a PR.

Hold up, looks like there are some encryptions / decryptions not being set properly in servers.items compared with config.data.servers

Nvm, I think data within servers.items might have been decrypted already. This should work.

Don't merge this yet. I think I found a bigger issue with our encryption and decryption logics when DUPLICATING, and UPDATING servers.
They don't work. Try to duplicate ABC, to ABC1, then ABC1 to ABC2, the encrypted passwords are not properly copied over, the same thing is true for Trying to edit / update the same connections multiple times.

Look like the logic to encrypt passwords is encapsulated in the core library sqlectron-core and not exported.
So we might not be able to use servers.items directly.

Okay guys, I finally ended up with the RELOAD after SAVING and after DUPLICATING path.
I think it's a safer path and solution to this problem.

Good catch @synle. Thanks again 👏 👏 👏


Add qwt port

Added option QUIET to vcpkg_apply_patches, to solve the problem in https://github.com/Microsoft/vcpkg/issues/411
Add vcpkg_configure_qmake and vcpkg_build_qmake helper functions
Add actual qwt port

Fixes https://github.com/Microsoft/vcpkg/issues/367

Thanks for the PR!


Bug: Optionally typed parameters do not render in OpenAPI docs properly

Description
When using an arbitrary enum as a type (or Literal assumedly), it generates a dropdown in the OpenAPI docs.
environment: Environment = Parameter(
        title="Environment",
        description="The environment to filter by.",
        default=None,
        required=False,
    ),

but hitting this endpoint gives a validation error:
 File ".venv/lib/python3.10/site-packages/litestar/_signature/model.py", line 190, in parse_values_from_connection_kwargs
    return convert(kwargs, cls, strict=False, dec_hook=deserializer, str_keys=True).to_dict()
msgspec.ValidationError: Expected `str`, got `null` - at `$.environment`

This makes sense, but the fix of adding  | None moves the dropdown field to just a plain textfield.
URL to code causing the issue
No response
MCVE
from enum import StrEnum
from litestar import Litestar, get
from litestar.params import Parameter

class Environment(StrEnum):
    DEVELOPMENT = "dev"
    TEST = "test"
    QA = "qa"

@get(path="/")
async def test(
    environment: Environment
    | None = Parameter(
        title="Environment",
        description="The environment to filter by.",
        default=None,
        required=False,
    ),
) -> None:
    return None

app = Litestar([test])

Steps to reproduce
1. Write mcve.py
2. Browse to OpenAPI schema
3. Observe dropdown fields
4. Execute on the test route
5. See error
6. Apply fix `Environment | None`
7. Reload OpenAPI schema
8. See no dropdown, just text field
9. Execute on the test route
10. See it work, but be deeply saddened that there is no longer a dropdown box and contemplate deleting your entire application.

Screenshots
: Environment

: Environment | None

Logs
No response
Litestar Version
2.x
Platform

[ ] Linux
[ ] Mac
[ ] Windows
[X] Other (Please specify in the description above)

[!NOTE]
While we are open for sponsoring on GitHub Sponsors and
OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.
Check out all issues funded or available for funding on our Polar.sh Litestar dashboard

If you would like to see an issue prioritized, make a pledge towards it!
We receive the pledge once the issue is completed & verified
This, along with engagement in the community, helps us know which features are a priority to our users.


fix(asset): calibration forecast timezone issues on datalinks

Pull Request
🤨 Rationale

Due to a reported issue in the CST time zone, it seems that the calibration forecast dashboard doesn't build the datalinks properly
The bucket label was also built in local time instead of UTC

👩💻 Implementation

The datalink time building algorithm was adjusted to account for the actual values from the backend when building the links
The Buckets labels respect the UTC values now

🧪 Testing

Unit testing
Manual testing on different time zones

✅ Checklist

[x] This PR has a title that follows the commit message format.

:tada: This PR is included in version 3.43.5 :tada:
The release is available on:

v3.43.5
GitHub release

Your semantic-release bot :package::rocket:


bugfix: #142 jest id missing

@kramer I did as you suggested. The one-liner turned out to be a several liner due to some broken tests. I also added a unit test for the issue in JestResultTest and fixed another. Pls comment.

Coverage increased (+0.69%) to 56.73% when pulling 61751eb01468e08b0fb747102dc3eceec445550f on tomsen-san:issue-142-JestId-missing into 7db9bf95c06e25ccd26f9a2896a7e7e7b8d1dfc7 on searchbox-io:master.

Do you mind also adding yourself to the Thanks section in README.md (keeping the same formatting) ?

Thanks a lot for the contribution @tomsen-san !


Fixes Bridge Translator's report file number output.

This makes numbers output to the report file to be dumped with
culture-independent .ToString() calls.
Fixes #3227.
Changes proposed in this pull request:

Sets up output of report files generated by Bridge.Translator to use culture-invariant number formatting
Keeps methods contracts intact so that other code calling them don't get affected by the changes
Will only use culture invariant output when explicitly specified, defaults to the former behavior.

Vladimir just ran the project off this branch and all tests passed! So it is good to go (as it mainly addresses issues with Vladimir running the test due to localization settings)


[DNM debugging] [ICEBERG] Use reflection to access Iceberg local classes to avoid IlegalAccessError

What changes were proposed in this pull request?
Use reflection to access Iceberg local classes to avoid IlegalAccessError
How was this patch tested?
Local build and explain on a iceberg table scan.

The issue is caused by class loader. We need to copy the gluten-iceberg jar to spark/jars


UpdatingQuickstartCsharp

Purpose
Updating QuickStart in C# for various requirements in the Prerequisites
Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[X] Documentation content changes
[ ] Other... Please describe:

Update to the C# QuickStart to reflect the updated Prerequisites.


how to set download file in headless chrome?

Selenium does not support downloading files.
You may, however, simply get URL of the file you want to download, and download the contents of the URL directly from you script.


to make it bangla

Dear Sir, I will like to make it Bangla language .
How to start?

@leonardomso I have already added the Bangla language translation long ago, but my pr is not approving.


Stream Langchain qa chain answer

Hello,
I would like to stream the answer of my langchain qa chain. Here is how I'm trying to do it in the pipe method (almost as in #141) :
    self.local_llm  = ChatOllama(model="llama3:70b",
                   #format="json",
                    temperature=0,
                    base_url="http://...:11434",
                    streaming=True,
                    keep_alive= -1,
                    callbacks=[StreamingStdOutCallbackHandler()]
                    )

   chain =  RetrievalQA.from_chain_type(
              llm=self.local_llm,
              retriever=retriever,
              return_source_documents=False,
              chain_type_kwargs={'prompt': prompt},
              verbose = True,
              input_key="question",
          )

    for chunk in chain.run(user_message):
        yield chunk

However, the words don't appear one by one as they should, instead I get large chunks of about 50 words at once. Any help would be much appreciated, thank you.

@thomassrour did you ever get your script to stream ?


bug: meltano state list with pattern - no such option

Meltano Version
2.3.0
Python Version
3.8
Bug scope
CLI (options, error messages, logging, etc.)
Operating System
Mac
Description
It looks like the --pattern argument thats in the docs https://docs.meltano.com/reference/command-line-interface#list isnt available on the CLI.
(meltano) Patricks-MBP:data pnadolny$ meltano --version
meltano, version 2.3.0

(meltano) Patricks-MBP:data pnadolny$ meltano state list --pattern '*tap-gitlab*'
2022-07-25T21:31:25.438941Z [info     ] Environment 'userdev' is active
Usage: meltano state list [OPTIONS] [PATTERN]
Try 'meltano state list --help' for help.

Error: No such option: --pattern

Code
No response

FYI @aaronsteers I'm adding this to next week's iteration to fix.

@tayloramurphy - Before we start dev work on this, I just want to confirm the spec regarding how wildcards should be implemented.
Is it a correct expectation that we'll use the same parser that is used by meltano select syntax syntax?
The docs for meltano state list currently only mention * as wildcard, but the select rules are documented as:

Unix shell-style wildcards can be used in selection patterns to match multiple entities or attributes at once:
*: matches any sequence of characters
?: matches one character
[abc]: matches either a, b, or c
[!abc]: matches any character but a, b, or c

Sidebar: select docs don't give instructions on how to escape characters, although it would not be common to have any of these characters in a state ID, stream name, or property name: [*, !, ?, [, ]`]

@kgpayne - Let me know (in accordance also with Taylor's response to the above), if you feel comfortable picking this up next week. Thanks!

Simplest solution is probably just to implement the same parser as in meltano select (refactoring into the utils library if needed for reuse?) and then for docs, we can just say something like:

@aaronsteers @kgpayne If it's actually simpler to use the more expressive matching patterns, then yeah I'm great with that. At a minimum I just want it to match what's in the docs, but if we get enhanced matching that's a nice bonus.

Related:

https://github.com/meltano/meltano/discussions/6270

@aaronsteers @tayloramurphy this ended up being really really simple - pattern matching was implemented with push-down to the database, but the CLI pattern was defined as an argument and not an option (as documented). It was a 1-line fix.
However this only gives us what is documented (i.e. use of *), rather than the more expressive options available in select. Given that the implementation of wildcards was done already, and that the select features are not readily reusable, I think it best to go with the minimum " I just want it to match what's in the docs" unless you feel strongly that more expressive pattern matching is needed at this stage 🙂

@aaronsteers @tayloramurphy this ended up being really really simple - pattern matching was implemented with push-down to the database, but the CLI pattern was defined as an argument and not an option (as documented). It was a 1-line fix.
However this only gives us what is documented (i.e. use of *), rather than the more expressive options available in select. Given that the implementation of wildcards was done already, and that the select features are not readily reusable, I think it best to go with the minimum " I just want it to match what's in the docs" unless you feel strongly that more expressive pattern matching is needed at this stage 🙂

Good call. And thanks for the quick turnaround.
As we discussed offline, there are advantages to keeping a simple * wildcard for now: specifically that this is more likely to be supported as a passthrough glob by state backends during their native list operations.


SpawnHeightOffset not working

Hi,
SpawnHeightOffset in .bo3 file not working.
I using 1.12 of TerrainControl.

Thanks for your working

nobody to response ? this plugin is abandoned or (...) ?

dupe #467


[FIX #3049] free stream when on_disconnect

只不播放不推流时，stream api会返回一个publish.cid为“”的stream, 离开播放器后，该stream其实无用了，需要清理。

Codecov Report

Merging #3050 (576671d) into 4.0release (0304e78) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

:exclamation: Current head 576671d differs from pull request most recent head 4d5d360. Consider uploading reports for the commit 4d5d360 to get more accurate results

@@              Coverage Diff               @@
##           4.0release    #3050      +/-   ##
==============================================
- Coverage       56.06%   56.05%   -0.01%
==============================================
  Files             153      153
  Lines           56958    56964       +6
==============================================
  Hits            31932    31932
- Misses          25026    25032       +6

Impacted Files
Coverage Δ

trunk/src/app/srs_app_statistic.cpp
27.05% <0.00%> (-0.51%)
:arrow_down:

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 0304e78...4d5d360. Read the comment docs.


feat: add privatek8s AKS cluster

Ref: https://github.com/jenkins-infra/helpdesk/issues/2844
previously:
Diff between ext_jenkins-infra.yaml & ext_jenkins-infra_privatek8s.yaml temporary introduced until the switch from temp_privatek8s and privatek8s cluster for infra.ci.jenkins.io:
--- ext_jenkins-infra.yaml
+++ ext_jenkins-infra_privatek8s.yaml
@@ -1,3 +1,4 @@
+## TODO: rename this file to ext_jenkins-infra.yaml and get rid of the old one when the switch from temp-privatek8s to privatek8s is done
 serviceAccount:
   create: true
   name: jenkins-controller
@@ -40,10 +41,6 @@
     readinessProbe:
       initialDelaySeconds: 120
   testEnabled: false
-  podSecurityContextOverride:
-    runAsNonRoot: true
-    runAsUser: 1000
-    supplementalGroups: [1000]
   overwritePlugins: true
   serviceType: "ClusterIP"
   javaOpts: >-
@@ -88,10 +85,10 @@
                     username: "MY-USERNAME"
                 - file:
                     fileName: "kubeconfig"
-                    id: "kubeconfig-controller-temp-privatek8s"
-                    description: "Kubeconfig file for temp-privatek8s"
+                    id: "kubeconfig-controller-privatek8s"
+                    description: "Kubeconfig file for privatek8s"
                     scope: SYSTEM
-                    secretBytes: "${base64:${KUBECONFIG_TEMP_PRIVATEK8S}}"
+                    secretBytes: "${base64:${KUBECONFIG_PRIVATEK8S}}"
                 - basicSSHUserPrivateKey:
                     scope: SYSTEM
                     id: "ec2-agents-privkey"
@@ -120,7 +117,7 @@
                 namespace: "jenkins-agents"
                 podRetention: "Never"
                 serverUrl: ${AGENTS_KUBERNETES_CLUSTER_URL}
-                credentialsId: "kubeconfig-controller-temp-privatek8s"
+                credentialsId: "kubeconfig-controller-privatek8s"
                 serverCertificate: |
                   ${AGENTS_KUBERNETES_CLUSTER_CERT}
                 podLabels:

About the removal of podSecurityContextOverride block:
Adding this override the default values, which are fine as they are. Crucially, this overriding block is missing fsGroup: 1000 default Jenkins Helm chart value, resulting in permission error in the initContainer when trying to deploy with it.

PR broke down:

#3233
#3235
#3247 (in draft while setting up a dual stack network)
infra part in a following PR

I was wondering if I could easily reuse this PR to include the remaining changes, nope ^^


70 refactor procesodedefensa clase innecesaria

Codecov Report
Patch and project coverage have no change.

Comparison is base (32579cf) 89.13% compared to head (32579cf) 89.13%.

:exclamation: Current head 32579cf differs from pull request most recent head 6c43edb. Consider uploading reports for the commit 6c43edb to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@                Coverage Diff                @@
##             felipeEntrega2      #73   +/-   ##
=================================================
  Coverage             89.13%   89.13%
  Complexity              232      232
=================================================
  Files                    42       42
  Lines                   580      580
  Branches                 33       33
=================================================
  Hits                    517      517
  Misses                   50       50
  Partials                 13       13

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


move from ert_shared to ert.shared

ert_shared is outdated, ert.shared is what to use..

Not a problem with sim2sumo, but uploader


Update credential tests

Update credential tests to avoid to use global project.

ran locally and worked as expected, just left a tiny requested change


FEATURE: Chat quoting

This commit introduces chat message quoting functionality. Selected messages from any channel except DM channels can be quoted:

This commit also allows non-staff users to bulk select messages, because it is necessary for quoting. The "Move to Topic" button is hidden for non-staff.
Quoting has a few different behaviours based on the current state:

When isolated on desktop, copy to clipboard and show a little message
Not isolated on desktop, open composer and insert markdown. This may open a reply composer if the user is currently inside a topic, otherwise it will open a new topic composer
On mobile, go to the category / topic that the chat is for and open the composer and insert markdown

When the quote button is clicked, a call to the /chat/:channelId/quote endpoint is sent with the selected message IDs. The quote BBCode is built with ChatTranscriptService. The bbcode is constructed server-side because other functions, such as Move to Topic and Archive Channel will need to build up the same bbcode later on. See the comment on ChatTranscriptService for further information on how that works.

Test to see if this lets me comment on sub-convos.

Ah just realised I need to make sure that messages with images get quoted correctly too.


ddev-router should not accept hostnames it's not configured for, fixes #2345

The Problem/Issue/Bug:
#2345 points out that if you run the PHPMyAdmin interface or mailhog UI, but then stop the project that it's referring to, it still shows there.
It turns out that any server on any port besides 80 and 443 demonstrates this behavior, it's not just mailhog and phpmyadmin. If you use router_http_port: "8080" in a project, then stop that project, anything else listening on 8080 will show up.
How this PR Solves The Problem:
Rework the catch-all (not matched) server stanza in ddev-router to list all available ports, so that it can properly redirect any of those if they're invalid.
Manual Testing Instructions:

Start two projects, preferably two projects with dissimilar databases so you can see the difference easily
Open the PHPMyadmin interface for one of them with ddev launch -p
Stop that project.
Referesh the PHPMyAdmin page. You should get "no backend" error message.

Automated Testing Overview:

Related Issue Link(s):
Release/Deployment notes:

The artifacts for this PR are at https://app.circleci.com/pipelines/github/drud/ddev/2760/workflows/252d6e80-289d-464f-a17c-b51da905f989/jobs/27564/artifacts


Various fixes

Various fix:

Format a technical term in README.md
Add the path to the processed libc in process_libc (common/libc.sh)
Escape a . on a regex (here it does not provoke a bug, but it's more clean) in get_current_debian_like (common/libc.sh)

hey @ajabep thanks a lot for these pull requests! it will probably take a bit before I get a chance to look at them


Wordreference.com: features not working on Kiwi browser

When using the language dictionary website https://www.wordreference.com/, there are at least two features not working on Kiwi browser:

On other browsers, when you start typing in the search field, a list of suggestions opens for possible entries in both ways (I mean: if you have chosen "English to Spanish", and you start typing on the search field, suggestions of entries are shown, both for English to Spanish and for Spanish to English).
On Kiwi browser, no suggestions show.

On other browsers, when you are reading a dictionary entry, you can click on a word to browse directly to that word. For example, let us suppose you are reading "be" in the English to Spanish dictionary. One possible translation (the main one, actually) is "ser". Then, if you tap on the word "ser", it opens the Spanish to English dictionary for the word "ser".
On Kiwi browser, tapping on a word does nothing.

Regards.

Number 1 works for me, I'm not completely sure what you mean by 2, but clicking on words do lead me to their respective pages. Do you have the builtin ad blocker enabled?

Hello,
I see that number 2 is working now. It may have been fixed in a recent
update, I do not know...
Unfortunately, number 1 is not working for me. I have the built-in
adblocker disabled. I have uBlock, but the problem persists after disabling
all the extensions (including uBlock).
Regards.
El sáb, 14 ago 2021 a las 20:20, DUO Labs @.***>)
escribió:

Number 1 works for me, I'm not completely sure what you mean by 2, but
clicking on words do lead me to their respective pages. Do you have the
builtin ad blocker enabled?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kiwibrowser/src.next/issues/326#issuecomment-898940825,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHQXFTLKJJOR6YC3N4PWY53T42XWTANCNFSM5CEN7XDQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Are you using the Play Store version or the GitHub version?

The Play Store version of Kiwi: version 93.0.4577.39
El sáb, 14 ago 2021 a las 21:55, DUO Labs @.***>)
escribió:

Are you using the Play Store version or the GitHub version?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kiwibrowser/src.next/issues/326#issuecomment-898952385,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHQXFTO33FPVQJSLJ3FOVODT43C4HANCNFSM5CEN7XDQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

So if you go to the home page and start typing, no suggestions come up?

That is correct, unfortunately. No suggestions, either on the home page or
in the search field when reading a dictionary entry.
El sáb, 14 ago 2021 a las 22:50, DUO Labs @.***>)
escribió:

So if you go to the home page and start typing, no suggestions come up?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kiwibrowser/src.next/issues/326#issuecomment-898957370,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHQXFTMB2V2KSXQ4E24ERCTT43JJRANCNFSM5CEN7XDQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Do you have any settings or extensions that are not the default?

Regarding extensions, the problem persists after disabling them all.
As for the settings, I think I changed something, but not much. I cannot
remember exactly... The built-in adblocker is disabled. If you want me to
check a specific setting, tell me which setting you have in mind.
Regards.

Oh, you're right it does fail. There must have been a regression (I was on the previous version).

I upgraded now, and it still gives me autocomplete. Could you put a short video to show case it? Lite mode isn't on is it?

I am quite busy these days but, anyway, there is nothing to be shown on a video... When I type on the search field, it is static, the typed characters are displayed, but nothing unfolds.
I mean, if you had never used this site, you would not notice anything strange. There is nothing to show on a video: the problem is not something happening, the problem is what does not happen.

Ha, ha, the auto complete fold-up menu shows after disabling the built-in
"hide ads" option in that site.
I have had several rendering issues since I started using Kiwi some months
ago, and I think that all of them have been fixed by disabling this option.
Having uBlock Origin available, and with the built-in ad blocker causing so
many false positives: have you considered disabling the latter by default?
(it is not possible to disable it globally, not even manually, see my
bug #440).
Regards.


Bumps puma from 5.5.1 to 5.6.4.

Bumps puma from 5.5.1 to 5.6.4.

Release notes
Sourced from puma's releases.

5.6.4

Security

Close several HTTP Request Smuggling exploits (CVE-2022-24790)

The 5.6.3 release was a mistake (released the wrong branch), 5.6.4 is correct.
5.6.2 / 2022-02-11

Bugfix/Security

Response body will always be closed. (GHSA-rmj8-8hhh-gv5h, related to #2809)

5.6.1
Bugfixes

Reverted a commit which appeared to be causing occasional blank header values (see issue #2808) (#2809)

Full Changelog: https://github.com/puma/puma/compare/v5.6.0...v5.6.1
5.6.0 - Birdie's Version
Maintainer @nateberkopec had a daughter, nicknamed Birdie:

5.6.0 / 2022-01-25

Features

Support localhost integration in ssl_bind (#2764, #2708)
Allow backlog parameter to be set with ssl_bind DSL (#2780)
Remove yaml (psych) requirement in StateFile (#2784)
Allow culling of oldest workers, previously was only youngest (#2773, #2794)
Add worker_check_interval configuration option (#2759)
Always send lowlevel_error response to client (#2731, #2341)
Support for cert_pem and key_pem with ssl_bind DSL (#2728)

Bugfixes

Keep thread names under 15 characters, prevents breakage on some OSes (#2733)
Fix two 'old-style-definition' compile warning (#2807, #2806)
Log environment correctly using option value (#2799)
Fix warning from Ruby master (will be 3.2.0) (#2785)
extconf.rb - fix openssl with old Windows builds (#2757)
server.rb - rescue handling (Errno::EBADF) for @notify.close (#2745)

Refactor

server.rb - refactor code using @options[:remote_address] (#2742)
[jruby] a couple refactorings - avoid copy-ing bytes (#2730)

5.5.2
Re-allows UTF-8 in HTTP header values

Changelog
Sourced from puma's changelog.

5.6.4 / 2022-03-30

Security

Close several HTTP Request Smuggling exploits (CVE-2022-24790)

5.6.2 / 2022-02-11

Bugfix/Security

Response body will always be closed. (GHSA-rmj8-8hhh-gv5h, related to #2809)

5.6.1 / 2022-01-26

Bugfixes

Reverted a commit which appeared to be causing occasional blank header values (#2809)

5.6.0 / 2022-01-25

Features

Support localhost integration in ssl_bind (#2764, #2708)
Allow backlog parameter to be set with ssl_bind DSL (#2780)
Remove yaml (psych) requirement in StateFile (#2784)
Allow culling of oldest workers, previously was only youngest (#2773, #2794)
Add worker_check_interval configuration option (#2759)
Always send lowlevel_error response to client (#2731, #2341)
Support for cert_pem and key_pem with ssl_bind DSL (#2728)

Bugfixes

Keep thread names under 15 characters, prevents breakage on some OSes (#2733)
Fix two 'old-style-definition' compile warning (#2807, #2806)
Log environment correctly using option value (#2799)
Fix warning from Ruby master (will be 3.2.0) (#2785)
extconf.rb - fix openssl with old Windows builds (#2757)
server.rb - rescue handling (Errno::EBADF) for @notify.close (#2745)

Refactor

server.rb - refactor code using @options[:remote_address] (#2742)
[jruby] a couple refactorings - avoid copy-ing bytes (#2730)

5.5.2 / 2021-10-12

Bugfixes

Allow UTF-8 in HTTP header values

Commits

7add06a 5.6.4
4475a46 5.6.3
5bb7d20 Merge pull request from GHSA-h99w-9q5r-gjq9
c6340d1 5.6.2 (#2821)
e0753de 2.6.1
7008a61 Revert "Always send lowlevel_error response to client (#2731)" (#2809)
61ebbbe 5.6.0
d20915d Fix two 'old-style-definition' compile warning (#2807)
930e5b4 Fix typo in CONTRIBUTING (#2805)
c38d61c CONTRIBUTING: file limits
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
@dependabot use these labels will set the current labels as the default for future PRs for this repo and language
@dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
@dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
@dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

Originally posted by @dependabot in https://github.com/railwayapp/starters/pull/282

I did not find ANY reason why this issue exists. Please close it as soon as you can (or want :-) ).


Pipelines allow unclean go.sum files that block our release pipeline

In neither of our primary pipelines (for PRs, and for releases) do we catch "unclean" go.sum files, where "unclean" is defined as having excess line items that would not be present after running go mod tidy.
We should catch this scenario in our Static Analysis pipeline (which runs for PRs), which is as far upstream we can detect this problem, short of changes to developer environments. We have most of the pieces in place to do this. But since we run our check-go-mod-tidy make target after having run go mod tidy, we aren't catching the problem. To correctly catch the problem in the Static Analysis pipeline, we need to:

[ ] remove the go mod tidy command from the bootstrap step (Note: this leaves go mod download as the last Go command in the bootstrapping process)
[ ] modify go-mod-tidy-check.sh to detect and error out upon finding a diff between "A" and "B", where: "A" is the original go.sum, and "B" is state of go.sum after running go mod tidy.

Corresponds to https://github.com/anchore/grype/issues/358


C++03/move compliance, added better compiler/library detection

Also corrected from previous version: now rejects RTTI if using libc++ (no rtti), utility moved into main area (supplies std::less).
Cheers

Mistake, resubmitting


Added exchange operations + added products level in embed parameters

Too many commits behind. Will resync and republish

Too many commits behind. Will resync and republish